3D球场项目 (三)

Sat, 30 May 2026 17:30:28 +0800

在3D球场项目 (二)中，我们梳理了视频弹幕引擎的整体架构、引擎初始化流程。现在，3D 球场部分基本已经探索完毕，我们接下来就是要解决这个项目的数据驱动部分了。

我们现在研究一下下发数据的来源：Opta，它是全球顶级的体育数据公司，1996 年创立于英国伦敦，现隶属于 Stats Perform，是行业公认的足球数据金标准。

覆盖：20+ 运动、3900+ 赛事、每年 6 万 + 场比赛
规模：7.2PB 历史数据、年采集超 10 亿数据点
精度：单场足球2 万 + 事件点，事件识别准确率 99.8%

腾讯体育采买了 Opta WTA 网球比赛的数据，我们可以通过 Opta 的 API 来获取数据。

根据他们官网的介绍，一个 MA3 网球赛事数据中 typeId 对应的意义如下：

点击展开 / 折叠 Event TypeId 完整对照表

Event TypeId	Event Name	Description
20	STOP_GAME	Indicates that the game has finished.
41	START_SET_1	Start 1st Set
42	START_SET_2	Start 2nd Set
43	START_SET_3	Start 3rd Set
44	START_SET_4	Start 4th Set
45	START_SET_5	Start 5th Set
46	STOP_SET	Stop Set
47	T_WO1	w.o. Player 1
48	T_WO2	w.o. Player 2
128	SAFE	Safe (No longer used)
129	DANGER	Danger (Technical/connection issue at venue)
132	INJ_BREAK	Game suspended - Player injured
133	PLAYERS_COMING_OUT	Players coming out
141	GAME_ABOUT_TO_START	Game about to start
149	GAME_SUSPENDED	Game suspended
160	PLAYERS_WARMING_UP	Players warming up
162	SHAKE_HANDS_WITH_REFEREE	Players shake hands with referee
163	COIN_FLIPPING_FOR_FIRST_SERVER	Coin flip to choose first server
164	PLAYERS_TALKING_TO_REFEREE	Player(s) talking to the referee
165	REFEREE_CHECKING_POINTMARK	Referee checking pointmark
166	BOTH_PLAYERS_SEATED	Both players seated
167	PLAYER1_RECEIVING_TREATMENT	Player 1 receiving treatment
168	PLAYER2_RECEIVING_TREATMENT	Player 2 receiving treatment
169	PLAYERS_GOING_TO_COURT	Players going back to court
170	NEXT_GAME_ABOUT_TO_START	Next game is about to start
180	T_MORE_THAN_5	Rally, over five shots
181	T_MORE_THAN_10	Rally over ten shots
182	T_MORE_THAN_15	Rally over fifteen shots
187	T_POINT_UNDER_INVESTIGATION	Point under investigation
188	T_START_TIE_BREAK	Start tie break
191	T_POINT_STOPPED_BY_REF	Point stopped by referee
197	UPDATE_SCORE_START	Start score update
198	UPDATE_SCORE_FINISHED	Score update finished
200	SIDE_CHANGE	Side change
206	SHOT_CNT	Shot count
216	STATISTIC_VERIFICATION	Statistics confirmation
240	NEW_BALLS	New balls
241	UMPIRE_ON_COURT	UMPIRE ON COURT
242	WARMING_UP_VOLLEY	Warming up - volley
243	WARMING_UP_SERVICE	Warming up - service
244	ONE_MINUTE	One minute
245	TIME	Time
246	SHOT_DETAILS	Shot details
256	CLS	Cancel last sent event
257	CLR	Clear events
258	GCC	Game conditions changed.
261	SCORER	Event details for %RELATED_EVENT% in the %MIN%. minute changed
262	BP	Ball position event
264	ODD	Odds event (deprecated)
266	TIME_CORRECTION_EVENT	Correct timestamp for a missed event
276	START_GAME_CLOCK	The (stopped) game clock is (re)started the game is running
277	STOP_GAME_CLOCK	The game clock is stopped. Time will not change until Start Game Clock is sent again
278	ADJUST_GAME_CLOCK	Game clock value is adjusted manually
279	CSTAT	A statistical value is cleared and an additional event with the correct action is sent (e.g. an invalid Ace Home event is replaced by a Service Winner Home)
280	CONF_PERIOD_SCORE	Period score confirmed
282	TIME_ADAPTION	Time for event %RELATED_EVENT% was adapted by %SEC% seconds
285	PLAYER_DATA_CONFIRMED	Player data for %RELATED_EVENT% in the %MIN% confirmed
513	SYS_MSG	System Message
514	SCOUT_IN_STADION	Scout in Stadium
515	CONNECTION_PROBLEMSSCOUT_OFFLINE	Connection problems Scout offline
516	CONNECTION_PROBLEMS	Connection problems
517	TRANSMISSION_ONLINE	Transmission online
520	LINEUP_CHANGED	Line-up changed
524	JERSEY_CHANGED	Jersey colors updated
782	GAME CANCELLED	Automatic “Game cancelled” event after first “cancellation” System message is sent
1152	T_SERVE1	Service Player 1
1153	T_1ST_SERVICE1	1st service Player 1
1154	T_2ND_SERVICE1	2nd service Player 1
1155	T_NA1	Net approach player 1
1156	T_W_FH1	Winner (forehand) Player 1
1157	T_W_BH1	Winner (backhand) Player 1
1158	T_FE_FH1	Forced error (forehand) Player 1
1159	T_FE_BH1	Forced error (backhand) Player 1
1160	T_UE_FH1	Unforced error (forehand) Player 1
1161	T_UE_BH1	Unforced error (backhand) Player 1
1162	T_HE1	Hawkeye Player 1
1163	T_WBR1	Warning by referee Player 1
1164	T_CBR1	Cautioned by referee Player 1
1165	T_SRV_NET1	Net Player 1
1166	T_SRV_OUT1	Out Player 1
1167	T_SRV_FF1	Foot fault Player 1
1168	T_SRV_DF1	Double fault Player 1
1169	T_SRV_A1	Ace Player 1
1170	T_SRV_SW1	Service winner Player 1
1171	T_SRV_RW_FH1	Return winner (forehand) Player 1
1172	T_SRV_IN1	Serve in Player 1
1173	T_POINT1	Point Player 1
1174	T_CONF1	Confirm Point Player 1
1175	T_GAME1	Game Player 1
1176	T_SET1	Set Player 1
1177	T_BL1	Baseline Player 1
1178	T_SRV_NR1	Net/Retake Player 1
1179	T_W1	Winner Player 1
1180	T_FE1	Forced error Player 1
1181	T_UE1	Unforced error Player 1
1182	T_SRV_RW_BH1	Return winner (backhand) Player 1
1183	T_V_FH1	Volley (forehand) Player 1
1184	T_V_BH1	Volley (backhand) Player 1
1185	T_BB1	Break ball Player 1
1186	T_B1	Break Player 1
1187	T_HES1	Hawk eye successful Player 1
1188	T_ITO1	Injury Timeout Player 1
1189	T_START_SRV1	Start Service Player 1
1190	T_WARNING1	1st offence - warning Player 1
1191	T_PENALTY_POINT1	2nd offence - penalty point Player 1
1192	T_PENALTY_GAME1	3rd offence - penalty game Player 1
1193	T_DISQUALIFICATION1	Disqualification Player 1
1194	T_UE_NET1	Unforced error net Player 1
1195	T_FE_NET1	Forced error net Player 1
1196	T_SUCCESSFUL_NET_APPROACH1	Successful net approach Player 1
1197	T_TIME_VIOLATION1	Time violation Player 1
1198	T_PENALTY_POINT1 T_UNSUCCESSFUL_NET_APPROACH1	Unsuccessful net approach Player 1
1199	T_AT_NET1	At net Player 1
1200	T_AT_BASELINE1	At baseline Player 1
1201	T_SET_BALL1	Set ball Player 1
1202	T_MATCH_BALL1	Match ball Player 1
2176	T_SERVE2	Service Player 2
2177	T_1ST_SERVICE2	1st service Player 2
2178	T_2ND_SERVICE2	2nd service Player 2
2179	T_NA2	Net approach player 2
2180	T_W_FH2	Winner (forehand) Player 2
2181	T_W_BH2	Winner (backhand) Player 2
2182	T_FE_FH2	Forced error (forehand) Player 2
2183	T_FE_BH2	Forced error (backhand) Player 2
2184	T_UE_FH2	Unforced error (forehand) Player 2
2185	T_UE_BH2	Unforced error (backhand) Player 2
2186	T_HE2	Hawkeye Player 2
2187	T_WBR2	Warning by referee Player 2
2188	T_CBR2	Cautioned by referee Player 2
2189	T_SRV_NET2	Net Player 2
2190	T_SRV_OUT2	Out Player 2
2191	T_SRV_FF2	Foot fault Player 2
2192	T_SRV_DF2	Double fault Player 2
2193	T_SRV_A2	Ace Player 2
2194	T_SRV_SW2	Service winner Player 2
2195	T_SRV_RW_FH2	Return winner (forehand) Player 2
2196	T_SRV_IN2	Serve in Player 2
2197	T_POINT2	Point Player 2
2198	T_CONF2	Confirm Point Player 2
2199	T_GAME2	Game Player 2
2200	T_SET2	Set Player 2
2201	T_BL2	Baseline Player 2
2202	T_SRV_NR2	Net/Retake Player 2
2203	T_W2	Winner Player 2
2204	T_FE2	Forced error Player 2
2205	T_UE2	Unforced error Player 2
2206	T_SRV_RW_BH2	Return winner (backhand) Player 2
2207	T_V_FH2	Volley (forehand) Player 2
2208	T_V_BH2	Volley (backhand) Player 2
2209	T_BB2	Break ball Player 2
2210	T_B2	Break Player 2
2211	T_HES2	Hawk eye successful Player 2
2212	T_ITO	Injury Timeout Player 2
2213	T_START_SRV2	Start Service Player 2
2214	T_WARNING2	1st offence - warning Player 2
2215	T_PENALTY_POINT2	2nd offence - penalty point Player 2
2216	T_PENALTY_GAME2	3rd offence - penalty game Player 2
2217	T_DISQUALIFICATION2	Disqualification Player 2
2218	T_UE_NET2	Unforced error net Player 2
2219	T_FE_NET2	Forced error net Player 2
2220	T_SUCCESSFUL_NET_APPROACH2	Successful net approach Player 2
2221	T_TIME_VIOLATION2	Time violation Player 2
2222	T_AT_NET2	Unsuccessful net approach Player 2
2223		At net Player 2
2224	T_AT_BASELINE2	At baseline Player 2
2225	T_SET_BALL2	Set ball Player 2
2226	T_MATCH_BALL2	Match ball Player 2

PBP = Play-by-Play（逐回合 / 逐事件数据），就是把一场比赛里每一次事件都按时间线秒级记录下来的最细粒度原始数据流。口语里也叫 “逐帧数据 / 流水账数据”。网球赛事的数据，都是以这个形式下发的，一段数据可能下发的数据是这样的：

3D球场项目 (四)

Sat, 30 May 2026 20:23:44 +0800

项目终于来到了落地环节。在3D球场项目 (三)里，我们用一段离线 PBP 数据 + 一次 LLM 调用，把"导演 Agent"的雏形跑了起来。Demo 阶段的脚本是离线生成、整段导入的；那时的 LLM 既负责"想象画面"，又顺手把动作、镜头、音效、解说词都打包了。

但项目一旦从 Demo 推到线上，导演 Agent 立刻面对三件事：

Opta 数据是按 Point 持续推过来的，不会一次性把一场比赛喂给大模型；
大模型 会失败、会延迟，一旦卡住，球员就只能停在 idle；
客户端会断流、会重连，需要一个"刚才那一拍发生了什么"的回放接口。

上一章末尾提到的三个坑——player 卡 idle、两人一直来回发球、长链断了客户端不知道怎么补——本质都来自这三件事。线上版本的 livecast 服务（基于 tRPC-Go）做了一次完整的工程化：导演 Agent 不再是单一 LLM，而是 确定性脚本层 + LLM 解说层 + 双重下发保险 的组合。本篇就讲这套组合怎么搭起来。

一、网球数据是怎么进来的

NBA 那边的 PBP 是单条投递：上游每发生一个篮球事件，就经 Kafka 推一条消息过来。但网球数据天然是 按回合聚合 的——Opta 在一个 Point（一个回合）结束之后才会一次性把这一拍涉及的所有事件下发，所以服务端也用了批量消费通道：

Kafka topic: pbp_flow
 └─ FlowConsumer.BatchHandle(msgs []*sarama.ConsumerMessage)
 └─ livecastSvc.ProcessBatchPBPFlow(payloads [][]byte)

进入 ProcessBatchPBPFlow 之后，先按 mid（match id）做二级分组、过滤掉非网球的批次，再交给真正的 pipeline。两道闸门决定一场比赛的事件能不能走 3D 流水线：

Opta on Last Stand

3D球场项目 (三)

3D球场项目 (四)

一、网球数据是怎么进来的