`

`> ....
`
`0 ....
`..._
`Ul
`0 ....
`N
`rFJ
`c
`
`\0
`-....l
`(.H
`(.H
`0\
`
`-....l
`0 .....
`....
`.....
`rFJ =(cid:173)
`0 ....
`.... ~
`= ....
`2'
`.... 0 =
`.... 0 = '"= = 0" -....
`~ 'e -....
`('D = .....
`'"= ~ .....
`
`~ .....
`
`(')
`
`~ .....
`
`(')
`
`('D
`('D
`
`Ul
`
`N
`
`27
`
`/
`
`Network
`
`Mobile Traffic
`
`~(c
`
`Msbd~
`13bi]
`FIG.l 10,
`
`Sportradar 1015
`Page 2
`
`

`

`

`

`

`

`

`

`

`

`> ....
`
`0 ....
`..._
`Ul
`0 ....
`N
`rFJ
`c
`
`\0
`-....l
`(.H
`(.H
`0\
`
`-....l
`0 .....
`0\
`.....
`rFJ =(cid:173)
`0 ....
`.... ~
`:= ....
`2'
`.... 0 =
`.... 0 = '"= = 0" -....
`~ 'e -....
`('D = .....
`'"= ~ .....
`
`~ .....
`
`(')
`
`~ .....
`
`(')
`
`('D
`('D
`
`Ul
`
`N
`
`FIG. 7
`
`I
`
`I CLOCK4
`
`I CLOCK3 I
`
`VIEW4
`
`VIEW3
`
`I
`
`I CLOCK2
`
`I CLOCK 1 I
`
`VIEW2
`
`VIEW1
`
`I
`
`CLOCK
`MASTER
`
`I
`
`MOSAIC VIEW
`
`I
`
`I CLOCK
`SLAVE
`
`PARAMETERS
`PARAMETERS
`PARAMETERS
`PARAMETERS
`
`ITEM4
`ITEM3
`ITEM2
`ITEM 1
`
`BOARD
`
`I EVENT NAME I
`
`Sportradar 1015
`Page 7
`
`

`

`

`

`US 2015/0163379 AI
`
`Jun. 11, 2015
`
`1
`
`TIME SYNCHRONIZATION OF VIDEO AND
`DATA INSIDE A MOBILE DEVICE
`
`BACKGROUND
`
`[0001]
`In recent years, mobile communication services
`have expanded and increased in popularity around the world.
`Many advanced networks offer wireless mobile communica(cid:173)
`tion service for voice calls, mobile phone messaging services
`(e.g., text and/or multimedia) and data communications. The
`data services, for example, enable surfing the world wide
`web, e.g., via a browser. The speeds of the data communica(cid:173)
`tions services have steadily increased as service providers
`have migrated the networks to newer generation technologies
`with broadband data communication capabilities, and the
`mobile stations have steadily advanced to take advantage of
`the new network technologies. The data communication
`capabilities of the mobile stations and the broadband data
`communication services offered by the networks enable users
`to perform more and more tasks and to access a rapidly
`expanding variety of content, all from their mobile stations.
`Examples of mobile station content items include, without
`limitation, media, games, messaging, social networks, stores,
`and any other applications or information for use on a mobile
`phone or on a tablet computer.
`[0002] Referring to tablet computers, or simply tablets,
`these devices differentiate themselves from mobile phones in
`that they are larger than mobile phones and are used mainly
`for viewing published content from the Internet, such as video
`and news. Mobile developers today are increasingly creating
`applications for use on tablets. These applications are usually
`supplied through online distribution, rather than traditional
`methods of boxed software or direct sales from software
`vendors. These suppliers, knows as "app stores", provide
`centralized catalogues of software from the operating system
`(OS) supplier or device manufacturer, and allow easy instal(cid:173)
`lation and updates via network communication. The app store
`is often shared with smartphones that use the same operating
`system.
`[0003]
`It may be desirable to provide a mobile device, such
`as a tablet, with a capability of receiving multiple sources of
`live information that are related to each other, but are pub(cid:173)
`lished and processed at different rates. For example, it may be
`desirable for a user to view video that is streamed live from the
`Internet to a client player using HTTP Live Streaming (also
`known as HLS) communications protocol. Furthermore, it
`may be desirable for the same user to simultaneously view
`other information, such as meta -data, that provides additional
`information related to the HLS video. Assembling meta-data
`and HLS video (for example), in which each is published and
`processed at a different rate and perhaps from different
`sources, for simultaneous display, in real-time has not as yet
`been implemented.
`[0004] Hence, a need exists for improved technologies for
`synchronizing information (for example, HLS video and
`meta-data) that is published and processed at different rates,
`so that a viewer may comprehend the multiple information
`displayed on a mobile device, or a tablet.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0005] The drawing figures depict one or more implemen(cid:173)
`tations in accord with the present teachings, by way of
`example only, not by way of limitation. In the figures, like
`reference numerals refer to the same or similar elements.
`
`[0006] FIG. 1 is a high-level functional block diagram of an
`example of a system of a network/devices that provides vari(cid:173)
`ous communications for mobile devices and supports an
`example of a system for synchronizing different types of data
`received by a mobile device (or mobile station).
`[0007] FIG. 2 is a high-level functional block diagram of an
`exemplary non-touch type mobile device, as may utilize a
`system for synchronizing different types of data received by a
`mobile device, similar to the system shown in FIG. 1.
`[0008] FIG. 3 is a high-level functional block diagram of an
`exemplary touch screen type mobile device, as may utilize a
`system for synchronizing different types of data received by a
`mobile device, similar to the system shown in FIG. 1.
`[0009] FIG. 4 is a high-level functional block diagram of an
`example of a system of a network that provides communica(cid:173)
`tions for mobile stations and supports an example of a system
`for delivering different types of data to an end user, in which
`the data is obtained from different sources viewing a live
`event, and synchronizing the data, so that the user can view
`the data in a comprehensive and orderly manner.
`[0010] FIG. 5 is simplified functional block diagram of an
`example of a system of a network that provides live video and
`audio data of a live event to a user of a mobile device and also
`provides meta-data of the live event to the user in a synchro(cid:173)
`nized manner for viewing and listening.
`[0011] FIG. 6 is a functional block diagram of a client
`application disposed in a video player that communicates
`with multiple servers and allows the client to select time
`stamped video data and, in response, to receive meta -data that
`is synchronized to the selected time stamped video data.
`[0012] FIG. 7 is an example of a display on a video player
`showing a mosaic view of four different videos of a live event
`and meta-data of multiple parameters that are related to the
`four different videos of the live event.
`[0013] FIG. 8 is a simplified functional block diagram of a
`computer that may be configured as a host or server, for
`example, to function as a server in the system of FIG. 1.
`[0014] FIG. 9 is a simplified functional block diagram of a
`personal computer or other work station, terminal device, or
`computer tablet.
`
`DETAILED DESCRIPTION OF EXAMPLES
`
`[0015]
`In the following detailed description, numerous spe(cid:173)
`cific details are set forth by way of examples in order to
`provide a thorough understanding of the relevant teachings.
`However, it should be apparent that the present teachings may
`be practiced without such details. In other instances, well
`known methods, procedures, components, and/or circuitry
`have been described at a relatively high-level, without detail,
`in order to avoid unnecessarily obscuring aspects of the
`present teachings.
`[0016] The various methods and systems disclosed herein
`relate to acquisition of multiple paths of steaming content to
`a mobile device, such as a smartphone or a tablet. The acqui(cid:173)
`sition of the multiple paths of streaming content includes
`assembling and displaying the different streaming content in
`a synchronous manner. For example, video, audio and meta(cid:173)
`data may be transmitted from a sports venue via different
`communication paths and at different rates. The video and
`audio may originate from a content provider or origin server
`that provides service to another server. The meta-data, how(cid:173)
`ever, may be provided to the other server by a server that is
`different from the content provider/origin server. The origin
`
`Sportradar 1015
`Page 9
`
`

`

`US 2015/0163379 AI
`
`Jun. 11, 2015
`
`2
`
`and meta-data servers may be located more than a mile from
`each other, although they both may be streaming content that
`is related to the same venue.
`[0017] Using an example of a sports venue, the video and
`audio may be transmitted via a satellite network, while the
`meta-data may be transmitted via Internet Protocol (IP)
`packet data communications using terrestrial data communi(cid:173)
`cation transport media. A solutions integrator, which may act
`as an origin server, may receive the digital streams from a
`content provider. The solutions integrator may then ingest,
`process and encode HD (high definition) video and audio
`signals to MPEG-HLS or MPEG-DASH streaming protocols.
`Meta-data may also be ingested utilizing a server and pack(cid:173)
`etized to .Extensible Markup Language (.XML) or .Java
`Script Object Notation (.JSON) type identifier frames. These
`signals traditionally do not transmit as a single cohesive
`stream, where timing or time stamping are wrapped into a
`control header of the transport stream packet ID (PID).
`[0018] As will be described, as an example, the video and
`audio data and the meta-data are both time stamped with
`consistent (e.g., GPS) timing protocols. In this manner, each
`respective data is time-tagged to the same timing signature,
`even though each respective data transmits from different
`physical locations. As a result, the video and audio data are
`time synchronized to the meta -data, so that all the data may be
`displayed in a mobile device (a smartphone or a tablet) in
`correct time sync.
`[0019] Reference is now made in detail to the examples
`illustrated in the accompanying drawings and discussed
`below. FIG. 1 illustrates a system 10 offering a variety of
`mobile communication services, including synchronization
`methods for mobile device users, or mobile station users. The
`example shows simply two mobile stations (MSs) 13a and
`l3b as well as a mobile communication network 15. The
`stations 13a and 13b are examples of mobile stations that may
`be used for the synchronization method. However, the com(cid:173)
`munication network provides similar communications for
`many other similar users, as well as for mobile devices/users
`that do not participate in the synchronization method. The
`network 15 provides mobile wireless communication ser(cid:173)
`vices to those stations as well as to other mobile stations (not
`shown), for example, via a number of base stations (BSs) 17.
`The present techniques may be implemented in any of a
`variety of available mobile networks 15 and/or on any type of
`mobile station compatible with such a network 15. The draw(cid:173)
`ing shows only a very simplified example of a few relevant
`elements of network 15 for purposes of discussion here.
`[0020] The wireless mobile communication network 15
`might be implemented as a network conforming to the long
`term evolution (LTE) standard, the code division multiple
`access (CDMA) IS-95 standard, the 3rd Generation Partner(cid:173)
`ship Project 2 (3GPP2) wireless IP network standard or the
`Evolution Data Optimized (EVDO) standard, the Global Sys(cid:173)
`tem for Mobile (GSM) communication standard, a time divi(cid:173)
`sion multiple access (TDMA) standard or other standards
`used for public mobile wireless communications. The mobile
`stations 13a and 13b are capable of communications through
`network 15, using the synchronization method, typically, or a
`variety of other methods/services. The exemplary devices
`l3a and 13b are capable of data communications through the
`network 15 and the users thereof typically have subscribed to
`data service through the networks.
`[0021] The network 15 allows users of the mobile stations,
`such as 13a and 13b (and other mobile stations not shown), to
`
`initiate and receive telephone calls to each other as well as
`through the public switched telephone network (PSTN) 19
`and telephone stations 21 connected to the PSTN. The net(cid:173)
`work 15 typically offers a variety of data services via a global
`network (e.g., the Internet 23), such as downloads, web
`browsing, email, etc. The mobile stations 13a and 13b may
`receive and execute applications written in various program(cid:173)
`ming languages, as described later.
`[0022] Mobile stations, like 13a and 13b, may take the form
`of portable handsets, smart-phones, personal digital assis(cid:173)
`tants, or tablets although they may be implemented in other
`form factors. Program applications, including an application
`to assist in the synchronization method, may be configured to
`execute on many different types of mobile stations. For
`example, a mobile station application may be written to
`execute on a binary runtime environment for mobile (BREW(cid:173)
`based) mobile station, a Windows Mobile based mobile sta(cid:173)
`tion, Android, iOS iPhone or iPad, Java Mobile, or RIM based
`mobile station such as a BlackBerry, or the like. Some of these
`types of devices may employ a multi-tasking operating sys(cid:173)
`tem.
`[0023] The mobile communication network 15 may be
`implemented by a number of interconnected networks.
`Hence, the overall network 15 may include a number of radio
`access networks (RAN s ), as well as regional ground networks
`interconnecting a number ofRANs and a wide area network
`(WAN) interconnecting the regional gronnd networks to core
`network elements. A regional portion of network 15, such as
`that serving mobile stations 13, may include one or more
`RANs and a regional circuit and/or packet switched network
`and associated signaling network facilities.
`[0024] Physical elements of a RAN operated by one of the
`mobile service providers or carriers, include a number ofbase
`stations represented in the example by the base stations (BSs)
`17. Although not separately shown, such a base station 17
`may include a base transceiver system (BTS), which may
`communicate via an antennae system at the site of the base
`station and over the airlink with one or more of the mobile
`stations 13a and 13b, when the mobile stations are within
`range. Each base station may include a BTS coupled to sev(cid:173)
`eral antennae mounted on a radio tower within a coverage
`area often referred to as a "cell." The BTS is the part of the
`radio network that sends and receives RF signals to/from the
`mobile stations that are served by the base station 17, includ(cid:173)
`ing in the example mobile stations 13a and 13b. Later gen(cid:173)
`eration mobile networks utilize wireless access elements,
`each referred to as an eNodeB, to provide functions similar to
`those of a base station; but for convenience, the discussion
`here will generally include eNodeBs and other network wire(cid:173)
`less access devices under the general term base station.
`[0025] The radio access networks may also include a traffic
`network represented generally by the cloud at 15, which
`carries the user communications and data for the mobile
`stations between the base stations 17 and other elements with,
`or through which the mobile stations communicate. It will be
`understood that the various network elements may commu(cid:173)
`nicate with each other and other networks (e.g., a PSTN 19
`and the Internet 23) either directly or indirectly.
`[0026] Although not shown, the provider or carrier may
`also operate a number of systems that provide ancillary func(cid:173)
`tions in support of the communications services and/or appli(cid:173)
`cation services provided through network 15, and those ele(cid:173)
`ments may communicate with other nodes or elements in
`system 10 via one or more private IP type packet data net-
`
`Sportradar 1015
`Page 10
`
`

`

`US 2015/0163379 AI
`
`Jun. 11, 2015
`
`3
`
`works (sometimes referred to as an Intranet), i.e., a private
`network. Examples of such systems may include one or more
`application servers and related authentication servers.
`[0027] A mobile station may communicate over the air with
`base station 17 and through traffic network 15 for various
`video and audio, and meta-data communications. If the
`mobile service carrier offers the synchronization service, the
`service may be hosted on a synchronization server 31, for
`communication via network 15. Alternatively, programming
`for the synchronization service may be distributed across
`multiple components of system 10. For a given service,
`including the synchronization service, an application pro(cid:173)
`gram within a mobile station 13a or l3b may be considered as
`a 'client' and programming at server 31 may be considered as
`the 'server' application for the particular service. Two addi(cid:173)
`tional servers are shown, namely, server 33 communicating
`through network 29, and server 25 communicating through
`the Internet 23. As part of the synchronization service, server
`25 may provide one type of data, for example, audio and video
`data of a live event; a second type of data for example, meta(cid:173)
`data of the same event, may be provided by server 31. Both
`types of data may flow to a mobile device 13b through one or
`more networks, for example, network 29, Internet 23 and/or
`mobile traffic network 15. The manner in which both of these
`types of data are synchronized for viewing by a user of mobile
`device 13b is described later.
`[0028] Associated synchronization events under consider(cid:173)
`ation here may be delivered to touch screen type mobile
`stations, as well as to non-touch type mobile stations. Hence,
`mobile station (MS) 13a is shown as anon-touch type mobile
`station and mobile station (MS) 13b is shown as a touch
`screen type mobile station. Implementation of the synchro(cid:173)
`nization service may involve some execution of programming
`in the mobile stations, as well as implementation of user
`input/output functions and data communications through net(cid:173)
`work 15 from the mobile stations.
`[0029]
`It may be useful to consider the functional elements/
`aspects of two exemplary mobile stations 13a and 13b, at a
`high-level.
`[0030] For purposes of such a discussion, FIG. 2 is a block
`diagram illustration of an exemplary non-touch type mobile
`station 13a. Although the mobile station 13a may be a smart(cid:173)
`phone or may be incorporated into another device, such as a
`personal digital assistant (PDA) or the like, for discussion
`purposes, the illustration shows the mobile station 13a is in
`the form of a handset. The handset embodiment of the mobile
`station 13a functions as a normal digital wireless telephone
`station. For that function, the station 13a includes a micro(cid:173)
`phone 102 for audio signal input and a speaker 104 for audio
`signal output. The microphone 102 and speaker 104 connect
`to voice coding and decoding circuitry (vocoder) 106. For a
`voice telephone call, for example, the vocoder 106 provides
`two-way conversion between analog audio signals represent(cid:173)
`ing speech or other audio and digital samples at a compressed
`bit rate compatible with the digital protocol of wireless tele(cid:173)
`phone network communications or voice over packet (e.g.,
`Internet Protocol) communications.
`[0031] For digital wireless communications, the handset
`l3a also includes at least one digital transceiver (XCVR) 108.
`Today, the handset 13a would be configured for digital wire(cid:173)
`less communications using one or more of the common net(cid:173)
`work technology types. The concepts discussed here encom(cid:173)
`pass embodiments of mobile station 13a utilizing any digital
`transceivers that conform to current or future developed digi-
`
`tal wireless communication standards. The mobile station
`l3a may also be capable of analog operation via a legacy
`network technology.
`[0032] The transceiver 108 provides two-way wireless
`communication of information, such as vocoded speech
`samples and/or digital information, in accordance with the
`technology of network 15. The transceiver 108 also sends and
`receives a variety of signaling messages in support of the
`various audio and data services provided via the mobile sta(cid:173)
`tion 13a and the communication network. Each transceiver
`108 connects through radio frequency (RF) transmit and
`receive amplifiers (not separately shown) to an antenna 110.
`[0033] The example mobile station 13a includes a display
`118 for displaying messages, menus or the like, call related
`information dialed by the user, calling party numbers, etc. A
`keypad 120 enables dialing digits for voice and/or data calls
`as well as generating selection inputs, for example, as may be
`keyed-in by the user based on a displayed menu or as a cursor
`control and selection of a highlighted item on a displayed
`screen. The display 118 and keypad 120 are the physical
`elements providing a textual or graphical user interface. Vari(cid:173)
`ous combinations of the keypad 120, display 118, micro(cid:173)
`phone 102 and speaker 104 may be used as the physical input
`output elements of the graphical user interface (GUI), for
`multimedia (e.g., audio and/or video) communications. Of
`course other user interface elements may be used, such as a
`trackball, as in some types ofPDAs or smart phones.
`[0034]
`In addition to normal telephone and data communi(cid:173)
`cation related input/output (including message input and
`message display functions), the user interface elements also
`may be used for display of menus and other information to the
`user and user input of selections. For example, the user may
`view a live event on display 118 of mobile device 13a. The
`user may select, by way of keypad 120, specific audio and
`video data for listening and viewing by way of speaker 104
`and display 118, respectively. In addition, the user may select
`specific meta-data associated with the audio and video data.
`The manner in which the audio and video data together with
`the meta-data are synchronized will be described later.
`[0035] A microprocessor 112 serves as a programmable
`controller for the mobile station 13a, in that it controls all
`operations of the mobile station 13a in accord with program(cid:173)
`ming that it executes, for all normal operations, and for opera(cid:173)
`tions involved in the synchronization procedure under con(cid:173)
`sideration here. In the example, the mobile station 13a
`includes flash type program memory 114, for storage of vari(cid:173)
`ous "software" or "firmware" program routines and mobile
`configuration settings, such as mobile directory number
`(MDN) and/or mobile identification number (MIN), etc. The
`mobile station 13a may also include a non-volatile random
`access memory (RAM) 116 for a working data processing
`memory. Of course, other storage devices or configurations
`may be added to or substituted for those in the example. In a
`present implementation, the flash type program memory 114
`stores firmware such as a boot routine, device driver software,
`an operating system, call processing software and vocoder
`control software, and any of a wide variety of other applica(cid:173)
`tions, such as client browser software and short message
`service software. The memories 114, 116 also store various
`data, such as telephone numbers and server addresses, down(cid:173)
`loaded data such as multimedia content, and various data
`input by the user. Programming stored in the flash type pro(cid:173)
`gram memory 114, sometimes referred to as "firmware," is
`loaded into and executed by microprocessor 112.
`
`Sportradar 1015
`Page 11
`
`

`

`US 2015/0163379 AI
`
`Jun. 11, 2015
`
`4
`
`[0036] As outlined above, the mobile station 13a includes a
`processor, and programming stored in the flash memory 114
`configures the processor so that the mobile station is capable
`of performing various desired functions, including the func(cid:173)
`tions involved in the synchronization technique. Such func(cid:173)
`tions may include time-stamping audio and video data of a
`live event; time-stamping meta-data that is associated with
`the same event; and several handshake communications
`between the mobile station and different servers across the
`network. These functions are described later.
`[0037] FIG. 3 is a block diagram illustration of an exem(cid:173)
`plary touch screen type mobile station 13b. Although possibly
`configured somewhat differently, at least logically, a number
`of the elements of the exemplary touch screen type mobile
`station 13b are similar to the elements of mobile station 13a,
`and are identified by like reference numbers in FIG. 3. For
`example, the touch screen type mobile station 13b includes a
`microphone 102, speaker 104 and vocoder 106, for audio
`input and output functions, much like in the earlier example.
`The mobile station 13b also includes at least one digital
`transceiver (XCVR) 108, for digital wireless communica(cid:173)
`tions, although the handset 13b may include an additional
`digital or analog transceiver. The concepts discussed here
`encompass embodiments of the mobile station 13b utilizing
`any digital transceivers that conform to current or future
`developed digital wireless communication standards. As in
`the station 13a, the transceiver 108 provides two-way wire(cid:173)
`less communication of information, such as vocoded speech
`samples and/or digital information, in accordance with the
`technology of network 15. The transceiver 108 also sends and
`receives a variety of signaling messages in support of the
`various audio and data services provided via mobile station
`l3b and the communication network. Each transceiver 108
`connects through RF transmit and receive amplifiers (not
`separately shown) to an antenna 110. The transceiver may
`also support various types ofmobilemessaging services, such
`as short message service (SMS ), enhanced messaging service
`(EMS) and/or multimedia messaging service (MMS).
`[0038] As in the example of station 13a, a microprocessor
`112 serves as a programmable controller for the mobile sta(cid:173)
`tion 13b, in that it controls all operations of the mobile station
`l3b in accord with programming that it executes, for all
`normal operations, and for operations involved in the syn(cid:173)
`chronization procedure under consideration here. In the
`example, mobile station 13b includes flash type program
`memory 114, for storage of various program routines and
`mobile configuration settings. The mobile station 13b may
`also include a non-volatile random access memory (RAM)
`116 for a working data processing memory. Of course, other
`storage devices or configurations may be added to or substi(cid:173)
`tuted for those in the example. Hence, as outlined above, the
`mobile station 13b includes a processor; and programming
`stored in the flash memory 114 configures the processor so
`that the mobile station is capable of performing various
`desired functions, including in this case the functions
`involved in the synchronization technique.
`[0039]
`In the example of FIG. 2, the user interface elements
`include a display and a keypad. The mobile station 13b (of
`FIG. 3) may have a limited number of keys 130, but the user
`interface functions of the display and keypad are replaced by
`a touchscreen display arrangement. At a high level, a touch(cid:173)
`screen display is a device that displays information to a user
`and detects occurrence and location of a touch on the area of
`the display. The touch may be an actual touch of the display
`
`device with a finger, stylus or other object, although at least
`some touchscreens may also sense when the object is in close
`proximity to the screen. Use of a touchscreen display as part
`of the user interface enables a user to interact directly with the
`information presented on the display.
`[0040] Hence, the exemplary mobile station 13b includes a
`display 122, which the microprocessor 112 controls via a
`display driver ( disp. dvr.) 124, to present visible outputs to the
`device user. The mobile station 13b also includes a touch/
`position sensor 126. The sensor 126 is relatively transparent,
`so that the user may view the information presented on the
`display 122. A sense circuit (sense ctlr.) 128 senses signals
`from elements of the touch/position sensor 126 and detects
`occurrence and position of each touch of the screen formed by
`display 122 and sensor 126. The sense circuit 128 provides
`touch position information to microprocessor 112, which
`may correlate that information to information currently dis(cid:173)
`played via display 122, to determine the nature of a user input
`via the screen.
`[0041] The display 122 and touch sensor 126 (and possibly
`one or more keys 130, if included) are the physical elements
`providing the textual and graphical user interface for mobile
`station 13b. The microphone 102 and speaker 104 may be
`used as additional user interface elements, for audio input and
`output, including with respect to some synchronization func(cid:173)
`tions for the user delivered via the mobile station. The syn(cid:173)
`chronization aspects, highlighted previously with respect to
`mobile station 13a, apply similarly to mobile station 13b and
`will be described later in greater detail.
`[0042]
`It will be understood that the structure and operation
`of the mobile stations 13a and 13b, as outlined above, are
`describe by way of example only.
`[0043] Referring now to FIG. 4, a synchronization method
`is incorporated in a system, generally designated as 40, pro(cid:173)
`viding various communications to a mobile device 45, in
`which the mobile device (or mobile station) is shown as part
`of a wireless network 43. The wireless network also includes
`a cell tower 46 and a content delivery network 47. It will be
`appreciated that mobile device 45 may be similar to any of the
`mobile stations discussed above and likely is a tablet that may
`be similar to mobile station 13b shown in FIG. 1. The tablet
`allows a user to view a display including live video (for
`example) and meta-data in the form of text (for example). In
`addition, cell tower 46 and content delivery network 47 may
`be similar to base station 17 and mobile traffic network 15,
`respectively, both shown in FIG. 1.
`[0044] Other portions of system 40 include a content pro(cid:173)
`vider 42 and a solutions integrator 44. Each is described
`below.
`[0045] The content provider 42, in the example shown in
`FIG. 4, is configured to provide video and audio data of an
`event occurring in real time and provide telemetry data (meta(cid:173)
`data) including several parameters changing during the event.
`For example, the event may be an Indianapolis Car Race; the
`video and audio data may be multiple video/audio streams of
`race cars and drivers, as they are imaged at different locations
`on the race track; and the telemetry data (meta-data) may
`include varying parameters regarding the status of each car
`and driver in the race. Such parameters may include, for
`example, lap number, car speed and acceleration, tire pres(cid:173)
`sure, etc. In a car race, there may be as many as 50 different
`parameters that are available for monitoring of each race car,
`in order to assess how well the driver is performing during any
`interval of the race.
`
`Sportradar 1015
`Page 12
`
`

`

`US 2015/0163379 AI
`
`Jun. 11, 2015
`
`5
`
`[0046] Returning to content provider 42, the example
`shows four video/audio streams provided from four different
`imaging sources, namely sources 48a-48d. Any number of
`imaging sources may be available, for example, in which a
`different imaging source may be a camera positioned inside a
`race car (used as an example for explanation purpose). As
`shown, each source provides one video stream and two chan(cid:173)
`nels of audio associated with the respective video. The video
`streams are transmitted to a satellite truck 51 that is located
`adjacent the event (Indy Race, for example). The truck 51 is
`configured to receive the video and audio streams and trans(cid:173)
`mit the same to a transponder disposed in a satellite 50. The
`transmission may be in the form of an asynchronous serial
`interface (ASI) format, which streams data carrying an
`MPEG transport stream (MPEG-TS). Generally the ASI sig(cid:173)
`nal is a final product of video compression techniques. The
`truck 51 and satellite 50 are shown by way of example of one
`form of video and audio data communication technologies for
`communicating multiple video and audio streams, although
`other equipment may be used in place of the truck, and/or
`other non-satellite communication media may be used.
`[0047] Furthermore, content provider 42
`includes an
`Enhanced Result Protocol (ERP) g