[go: up one dir, main page]

WO2017007260A1 - Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion - Google Patents

Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion Download PDF

Info

Publication number
WO2017007260A1
WO2017007260A1 PCT/KR2016/007375 KR2016007375W WO2017007260A1 WO 2017007260 A1 WO2017007260 A1 WO 2017007260A1 KR 2016007375 W KR2016007375 W KR 2016007375W WO 2017007260 A1 WO2017007260 A1 WO 2017007260A1
Authority
WO
WIPO (PCT)
Prior art keywords
app
message
information
service
emergency alert
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2016/007375
Other languages
English (en)
Korean (ko)
Inventor
양승률
고우석
홍성룡
문경수
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Publication of WO2017007260A1 publication Critical patent/WO2017007260A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/438—Interfacing the downstream path of the transmission network originating from a server, e.g. retrieving encoded video stream packets from an IP network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/61—Network physical structure; Signal processing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/64—Addressing
    • H04N21/6405—Multicasting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/81—Monomedia components thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/85—Assembly of content; Generation of multimedia applications
    • H04N21/858—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot

Definitions

  • the present invention relates to a broadcast signal transmission apparatus, a broadcast signal reception apparatus, and a broadcast signal transmission and reception method.
  • the digital broadcast signal may include a larger amount of video / audio data than the analog broadcast signal, and may further include various types of additional data as well as the video / audio data.
  • the digital broadcasting system may provide high definition (HD) images, multichannel audio, and various additional services.
  • HD high definition
  • data transmission efficiency for a large amount of data transmission, robustness of a transmission / reception network, and network flexibility in consideration of a mobile receiving device should be improved.
  • the present invention provides a system and an associated signaling scheme that can effectively support next-generation broadcast services in an environment that supports next-generation hybrid broadcasting using terrestrial broadcasting networks and Internet networks. Suggest.
  • the present invention proposes a method for efficiently providing a hybrid broadcast using both a broadcasting network and an internet network.
  • the present invention proposes a method for providing an app-based enhancement based on an app for a basic broadcast service.
  • the present invention proposes a method of providing app-based enhancement to a broadcast service in sync.
  • the present invention proposes an architecture according to various protocols between a PD and a CD, and proposes a communication scheme between a PD and a CD, an app, and an app according to the architecture.
  • the present invention proposes an architecture and signaling scheme for effectively delivering information such as ESG and EAS from the PD side to the CD side.
  • FIG. 1 is a diagram illustrating a protocol stack according to an embodiment of the present invention.
  • FIG. 2 is a diagram illustrating a service discovery process according to an embodiment of the present invention.
  • LLS low level signaling
  • SLT service list table
  • FIG. 4 illustrates a USBD and an S-TSID delivered to ROUTE according to an embodiment of the present invention.
  • FIG. 5 is a diagram illustrating a USBD delivered to MMT according to an embodiment of the present invention.
  • FIG. 6 illustrates a link layer operation according to an embodiment of the present invention.
  • FIG. 7 illustrates a link mapping table (LMT) according to an embodiment of the present invention.
  • FIG. 8 shows a structure of a broadcast signal transmission apparatus for a next generation broadcast service according to an embodiment of the present invention.
  • FIG 9 illustrates a writing operation of a time interleaver according to an embodiment of the present invention.
  • FIG. 10 is a block diagram of an interleaving address generator composed of a main-PRBS generator and a sub-PRBS generator according to each FFT mode included in a frequency interleaver according to an embodiment of the present invention.
  • FIG. 11 is a flowchart illustrating a broadcast system according to an embodiment of the present invention.
  • FIG. 12 is a diagram illustrating information related to an emergency alert message subscription request according to an embodiment of the present invention.
  • FIG. 13 is a diagram illustrating information related to an emergency alert message subscription response according to an embodiment of the present invention.
  • FIG. 14 is a diagram illustrating information related to an emergency alert message subscription response according to an embodiment of the present invention.
  • 15 is a diagram illustrating information related to an emergency alert message subscription update request according to an embodiment of the present invention.
  • 16 is a diagram illustrating information related to an emergency alert message subscription cancellation request according to an embodiment of the present invention.
  • 17 is a diagram illustrating information related to an emergency alert message subscription update response according to an embodiment of the present invention.
  • 18 is a diagram illustrating information related to an emergency alert message subscription update response according to an embodiment of the present invention.
  • 19 is a diagram illustrating information related to an emergency alert message subscription cancellation response according to an embodiment of the present invention.
  • 20 is a diagram illustrating a response message to an emergency alert message notification message according to an embodiment of the present invention.
  • FIG. 21 shows a configuration of a broadcast reception device according to an embodiment of the present invention.
  • 22 is a block diagram of a broadcast receiving device according to another embodiment of the present invention.
  • FIG. 23 illustrates a process of generating an emergency alert and transmitting it through a broadcasting network according to an embodiment of the present invention.
  • 24 is a view illustrating an example of extracting and displaying an emergency alert signaled through a broadcast network by a broadcast reception device according to an embodiment of the present invention.
  • FIG. 25 is a view illustrating a service type of an emergency alert service signaled by a broadcast reception device, a service identifier, a variable representing a state of an emergency alert, an action for an emergency alert, and an argument of an action according to an embodiment of the present invention.
  • FIG. 26 is a ladder diagram illustrating an operation of signaling an emergency alert to a companion device by a broadcast reception device according to an embodiment of the present invention.
  • FIG. 27 is a ladder diagram illustrating an operation in which a broadcast reception device signals an emergency alert to a companion device according to another embodiment of the present invention.
  • FIG. 28 is a ladder diagram illustrating an operation of signaling an emergency alert by a broadcast reception device to a companion device according to another embodiment of the present invention.
  • 29 is a ladder diagram illustrating an operation of signaling an emergency alert by a broadcast reception device to a companion device according to another embodiment of the present invention.
  • FIG. 30 is a ladder diagram illustrating an operation in which a broadcast reception device signals an emergency alert to a companion device according to another embodiment of the present invention.
  • 31 is a ladder diagram illustrating an operation of signaling an emergency alert to a companion device by a broadcast receiving device according to an embodiment of the present invention.
  • FIG. 32 is a diagram illustrating a broadcast system according to an embodiment of the present invention.
  • FIG 33 illustrates a Websocket-based PD-CD architecture according to an embodiment of the present invention.
  • FIG. 34 illustrates a Websocket-based PD-CD architecture according to another embodiment of the present invention.
  • 35 is a diagram illustrating a Websocket-based PD-CD architecture according to another embodiment of the present invention.
  • FIG. 36 illustrates App to app communication in a Websocket based PD-CD architecture according to an embodiment of the present invention.
  • FIG. 37 illustrates an HTTP-based PD-CD architecture according to an embodiment of the present invention.
  • FIG. 39 illustrates a PD-CD architecture based on Websocket & HTTP according to an embodiment of the present invention.
  • FIG. 40 is a diagram illustrating a discovery process of a Websocket endpoint or HTTP service URL using a device description document (DDD) according to an embodiment of the present invention.
  • DDD device description document
  • FIG. 41 is a diagram illustrating a discovery process of a Websocket endpoint or HTTP service URL using a response header for a DDD request according to an embodiment of the present invention.
  • FIG. 42 is a diagram illustrating a discovery process of a Websocket endpoint or HTTP service URL using a URL of a response header for a DDD request according to an embodiment of the present invention.
  • FIG. 43 is a diagram illustrating a Websocket-based handshake & connection process according to an embodiment of the present invention (after discovery).
  • FIG. 44 is a diagram illustrating a handshake & connection process for websocket-based app-to-app communication according to an embodiment of the present invention (after discovery).
  • 45 is a diagram illustrating a two-way communication process based on Websockets (after connection) according to an embodiment of the present invention.
  • FIG. 46 is a diagram illustrating a websocket based App to App 2 way communication process according to an embodiment of the present invention (after connection / CD to PD).
  • FIG. 47 is a view illustrating a websocket based App to App 2 way communication process according to an embodiment of the present invention (after connection / PD to CD).
  • FIG. 48 is a diagram illustrating an HTTP-based Request-Response process according to an embodiment of the present invention (after discovery).
  • FIG. 49 illustrates an architecture for an emergency alert (EA) between a receiver (PD) and a CD according to an embodiment of the present invention.
  • EA emergency alert
  • FIG. 50 is a diagram illustrating an architecture of a process of executing a CD application according to an embodiment of the present invention.
  • FIG. 51 is a diagram illustrating an architecture for communication between an app and an app according to an embodiment of the present invention.
  • FIG. 52 is a diagram illustrating an architecture for communicating from a CD app to a PD app according to an embodiment of the present invention.
  • FIG. 53 illustrates a message structure for communication between a CD app and a PD according to an embodiment of the present invention.
  • FIG. 54 illustrates a format of a service / content identification message according to an embodiment of the present invention.
  • 55 is a diagram illustrating a current service information message format according to an embodiment of the present invention.
  • FIG. 57 illustrates a media playback state message format according to an embodiment of the present invention.
  • FIG. 58 is a diagram illustrating an EA message according to an embodiment of the present invention.
  • FIG. 59 is a diagram illustrating a subscription related message and a notification message of a web socket protocol according to an embodiment of the present invention in a JSNO schema.
  • 60 is a diagram illustrating a method of processing a broadcast service in a PD according to an embodiment of the present invention.
  • 61 is a diagram illustrating a broadcast service processing apparatus operating as a PD according to an embodiment of the present invention.
  • the present invention provides an apparatus and method for transmitting and receiving broadcast signals for next generation broadcast services.
  • the next generation broadcast service includes a terrestrial broadcast service, a mobile broadcast service, a UHDTV service, and the like.
  • a broadcast signal for a next generation broadcast service may be processed through a non-multiple input multiple output (MIMO) or MIMO scheme.
  • the non-MIMO scheme according to an embodiment of the present invention may include a multiple input single output (MISO) scheme, a single input single output (SISO) scheme, and the like.
  • MISO multiple input single output
  • SISO single input single output
  • the present invention proposes a physical profile (or system) that is optimized to minimize receiver complexity while achieving the performance required for a particular application.
  • FIG. 1 is a diagram illustrating a protocol stack according to an embodiment of the present invention.
  • the service may be delivered to the receiver through a plurality of layers.
  • the transmitting side can generate service data.
  • the delivery layer on the transmitting side performs processing for transmission to the service data, and the physical layer encodes it as a broadcast signal and transmits it through a broadcasting network or broadband.
  • the service data may be generated in a format according to ISO BMFF (base media file format).
  • the ISO BMFF media file may be used in broadcast network / broadband delivery, media encapsulation and / or synchronization format.
  • the service data is all data related to the service, and may include a concept including service components constituting the linear service, signaling information thereof, non real time (NRT) data, and other files.
  • the delivery layer will be described.
  • the delivery layer may provide a transmission function for service data.
  • the service data may be delivered through a broadcast network and / or broadband.
  • the first method may be to process service data into Media Processing Units (MPUs) based on MPEG Media Transport (MMT) and transmit the data using MMM protocol (MMTP).
  • MPUs Media Processing Units
  • MMT MPEG Media Transport
  • MMTP MMM protocol
  • the service data delivered through the MMTP may include service components for linear service and / or service signaling information thereof.
  • the second method may be to process service data into DASH segments based on MPEG DASH and transmit it using Real Time Object Delivery over Unidirectional Transport (ROUTE).
  • the service data delivered through the ROUTE protocol may include service components for the linear service, service signaling information and / or NRT data thereof. That is, non-timed data such as NRT data and files may be delivered through ROUTE.
  • Data processed according to the MMTP or ROUTE protocol may be processed into IP packets via the UDP / IP layer.
  • a service list table (SLT) may also be transmitted through a broadcasting network through a UDP / IP layer.
  • the SLT may be included in the LLS (Low Level Signaling) table and transmitted. The SLT and the LLS table will be described later.
  • IP packets may be treated as link layer packets at the link layer.
  • the link layer may encapsulate data of various formats delivered from an upper layer into a link layer packet and then deliver the data to the physical layer. The link layer will be described later.
  • At least one or more service elements may be delivered via a broadband path.
  • the data transmitted through the broadband may include service components in a DASH format, service signaling information and / or NRT data thereof. This data can be processed via HTTP / TCP / IP, passed through the link layer for broadband transmission, and delivered to the physical layer for broadband transmission.
  • the physical layer may process data received from a delivery layer (upper layer and / or link layer) and transmit the data through a broadcast network or a broadband. Details of the physical layer will be described later.
  • the service may be a collection of service components that are shown to the user as a whole, the components may be of different media types, the service may be continuous or intermittent, the service may be real time or non-real time, and the real time service may be a sequence of TV programs. It can be configured as.
  • the service may be a linear audio / video or audio only service that may have app-based enhancements.
  • the service may be an app-based service whose reproduction / configuration is controlled by the downloaded application.
  • the service may be an ESG service that provides an electronic service guide (ESG).
  • ESG electronic service guide
  • EA Emergency Alert
  • the service component may be delivered by (1) one or more ROUTE sessions or (2) one or more MMTP sessions.
  • the service component When a linear service with app-based enhancement is delivered through a broadcast network, the service component may be delivered by (1) one or more ROUTE sessions and (2) zero or more MMTP sessions.
  • data used for app-based enhancement may be delivered through a ROUTE session in the form of NRT data or other files.
  • linear service components (streaming media components) of one service may not be allowed to be delivered using both protocols simultaneously.
  • the service component may be delivered by one or more ROUTE sessions.
  • the service data used for the app-based service may be delivered through a ROUTE session in the form of NRT data or other files.
  • some service components or some NRT data, files, etc. of these services may be delivered via broadband (hybrid service delivery).
  • the linear service components of one service may be delivered through the MMT protocol.
  • the linear service components of one service may be delivered via a ROUTE protocol.
  • the linear service component and NRT data (NRT service component) of one service may be delivered through the ROUTE protocol.
  • linear service components of one service may be delivered through the MMT protocol, and NRT data (NRT service components) may be delivered through the ROUTE protocol.
  • some service component or some NRT data of a service may be delivered over broadband.
  • the data related to the app-based service or the app-based enhancement may be transmitted through a broadcast network according to ROUTE or through broadband in the form of NRT data.
  • NRT data may also be referred to as locally cashed data.
  • Each ROUTE session includes one or more LCT sessions that deliver, in whole or in part, the content components that make up the service.
  • an LCT session may deliver an individual component of a user service, such as an audio, video, or closed caption stream.
  • Streaming media is formatted into a DASH segment.
  • an LCT session For delivery of NRT user service or system metadata, an LCT session carries a file based content item.
  • These content files may consist of continuous (timed) or discrete (non-timed) media components of an NRT service, or metadata such as service signaling or ESG fragments.
  • Delivery of system metadata, such as service signaling or ESG fragments, can also be accomplished through the signaling message mode of the MMTP.
  • the tuner can scan frequencies and detect broadcast signals at specific frequencies.
  • the receiver can extract the SLT and send it to the module that processes it.
  • the SLT parser can parse the SLT, obtain data, and store it in the channel map.
  • the receiver may acquire bootstrap information of the SLT and deliver it to the ROUTE or MMT client. This allows the receiver to obtain and store the SLS. USBD or the like can be obtained, which can be parsed by the signaling parser.
  • the broadcast stream delivered by the broadcast signal frame of the physical layer may carry LLS (Low Level Signaling).
  • LLS data may be carried through the payload of an IP packet delivered to a well known IP address / port. This LLS may contain an SLT depending on its type.
  • LLS data may be formatted in the form of an LLS table. The first byte of every UDP / IP packet carrying LLS data may be the beginning of the LLS table. Unlike the illustrated embodiment, the IP stream carrying LLS data may be delivered to the same PLP along with other service data.
  • the SLT enables the receiver to generate a service list through a fast channel scan and provides access information for locating the SLS.
  • the SLT includes bootstrap information, which enables the receiver to obtain Service Layer Signaling (SLS) for each service.
  • SLS Service Layer Signaling
  • the bootstrap information may include destination IP address and destination port information of the ROUTE session including the LCT channel carrying the SLS and the LCT channel.
  • the bootstrap information may include a destination IP address and destination port information of the MMTP session carrying the SLS.
  • the SLS of service # 1 described by the SLT is delivered via ROUTE, and the SLT includes bootstrap information (sIP1, dIP1, dPort1) for the ROUTE session including the LCT channel to which the SLS is delivered. can do.
  • SLS of service # 2 described by the SLT is delivered through MMT, and the SLT may include bootstrap information (sIP2, dIP2, and dPort2) for an MMTP session including an MMTP packet flow through which the SLS is delivered.
  • the SLS is signaling information describing characteristics of a corresponding service and may include information for acquiring a corresponding service and a service component of the corresponding service, or may include receiver capability information for reproducing the corresponding service significantly. Having separate service signaling for each service allows the receiver to obtain the appropriate SLS for the desired service without having to parse the entire SLS delivered in the broadcast stream.
  • the SLS When the SLS is delivered through the ROUTE protocol, the SLS may be delivered through a dedicated LCT channel of a ROUTE session indicated by the SLT.
  • the SLS may include a user service bundle description (USBD / USD), a service-based transport session instance description (S-TSID), and / or a media presentation description (MPD).
  • USBD / USD user service bundle description
  • S-TSID service-based transport session instance description
  • MPD media presentation description
  • USBD to USD is one of the SLS fragments and may serve as a signaling hub for describing specific technical information of a service.
  • the USBD may include service identification information, device capability information, and the like.
  • the USBD may include reference information (URI reference) to other SLS fragments (S-TSID, MPD, etc.). That is, USBD / USD can refer to S-TSID and MPD respectively.
  • the USBD may further include metadata information that enables the receiver to determine the transmission mode (broadcast network / broadband). Details of the USBD / USD will be described later.
  • the S-TSID is one of the SLS fragments, and may provide overall session description information for a transport session carrying a service component of a corresponding service.
  • the S-TSID may provide transport session description information for the ROUTE session to which the service component of the corresponding service is delivered and / or the LCT channel of the ROUTE sessions.
  • the S-TSID may provide component acquisition information of service components related to one service.
  • the S-TSID may provide a mapping between the DASH Representation of the MPD and the tsi of the corresponding service component.
  • the component acquisition information of the S-TSID may be provided in the form of tsi, an identifier of an associated DASH representation, and may or may not include a PLP ID according to an embodiment.
  • the component acquisition information enables the receiver to collect audio / video components of a service and to buffer, decode, and the like of DASH media segments.
  • the S-TSID may be referenced by the USBD as described above. Details of the S-TSID will be described later.
  • the MPD is one of the SLS fragments and may provide a description of the DASH media presentation of the service.
  • the MPD may provide a resource identifier for the media segments and may provide contextual information within the media presentation for the identified resources.
  • the MPD may describe the DASH representation (service component) delivered through the broadcast network, and may also describe additional DASH representations delivered through the broadband (hybrid delivery).
  • the MPD may be referenced by the USBD as described above.
  • the SLS When the SLS is delivered through the MMT protocol, the SLS may be delivered through a dedicated MMTP packet flow of an MMTP session indicated by the SLT.
  • packet_id of MMTP packets carrying SLS may have a value of 00.
  • the SLS may include a USBD / USD and / or MMT Package (MP) table.
  • USBD is one of the SLS fragments, and may describe specific technical information of a service like that in ROUTE.
  • the USBD here may also include reference information (URI reference) to other SLS fragments.
  • the USBD of the MMT may refer to the MP table of the MMT signaling.
  • the USBD of the MMT may also include reference information on the S-TSID and / or the MPD.
  • the S-TSID may be for NRT data transmitted through the ROUTE protocol. This is because NRT data can be delivered through the ROUTE protocol even when the linear service component is delivered through the MMT protocol.
  • MPD may be for a service component delivered over broadband in hybrid service delivery. Details of the USBD of the MMT will be described later.
  • the MP table is a signaling message of the MMT for MPU components and may provide overall session description information for an MMTP session carrying a service component of a corresponding service.
  • the MP table may also contain descriptions for assets delivered via this MMTP session.
  • the MP table is streaming signaling information for MPU components, and may provide a list of assets corresponding to one service and location information (component acquisition information) of these components. Specific contents of the MP table may be in a form defined in MMT or a form in which modifications are made.
  • Asset is a multimedia data entity, which may mean a data entity associated with one unique ID and used to generate one multimedia presentation. Asset may correspond to a service component constituting a service.
  • the MP table may be used to access a streaming service component (MPU) corresponding to a desired service.
  • the MP table may be referenced by the USBD as described above.
  • MMT signaling messages may be defined. Such MMT signaling messages may describe additional information related to the MMTP session or service.
  • ROUTE sessions are identified by source IP address, destination IP address, and destination port number.
  • the LCT session is identified by a transport session identifier (TSI) that is unique within the scope of the parent ROUTE session.
  • MMTP sessions are identified by destination IP address and destination port number.
  • the MMTP packet flow is identified by a unique packet_id within the scope of the parent MMTP session.
  • the S-TSID, the USBD / USD, the MPD, or the LCT session carrying them may be called a service signaling channel.
  • the S-TSID, the USBD / USD, the MPD, or the LCT session carrying them may be called a service signaling channel.
  • the S-TSID, the USBD / USD, the MPD, or the LCT session carrying them may be called a service signaling channel.
  • the MMT signaling messages or packet flow carrying them may be called a service signaling channel.
  • one ROUTE or MMTP session may be delivered through a plurality of PLPs. That is, one service may be delivered through one or more PLPs. Unlike shown, components constituting one service may be delivered through different ROUTE sessions. In addition, according to an embodiment, components constituting one service may be delivered through different MMTP sessions. According to an embodiment, components constituting one service may be delivered divided into a ROUTE session and an MMTP session. Although not shown, a component constituting one service may be delivered through a broadband (hybrid delivery).
  • LLS low level signaling
  • SLT service list table
  • An embodiment t3010 of the illustrated LLS table may include information according to an LLS_table_id field, a provider_id field, an LLS_table_version field, and / or an LLS_table_id field.
  • the LLS_table_id field may identify a type of the corresponding LLS table, and the provider_id field may identify service providers related to services signaled by the corresponding LLS table.
  • the service provider is a broadcaster using all or part of the broadcast stream, and the provider_id field may identify one of a plurality of broadcasters using the broadcast stream.
  • the LLS_table_version field may provide version information of a corresponding LLS table.
  • the corresponding LLS table includes the above-described SLT, a rating region table (RRT) including information related to a content advisory rating, a SystemTime information providing information related to system time, and an emergency alert. It may include one of the CAP (Common Alert Protocol) message that provides information related to. According to an embodiment, other information other than these may be included in the LLS table.
  • RRT rating region table
  • CAP Common Alert Protocol
  • One embodiment t3020 of the illustrated SLT may include an @bsid attribute, an @sltCapabilities attribute, a sltInetUrl element, and / or a Service element.
  • Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
  • the @bsid attribute may be an identifier of a broadcast stream.
  • the @sltCapabilities attribute can provide the capability information required to decode and significantly reproduce all services described by the SLT.
  • the sltInetUrl element may provide base URL information used to obtain ESG or service signaling information for services of the corresponding SLT through broadband.
  • the sltInetUrl element may further include an @urlType attribute, which may indicate the type of data that can be obtained through the URL.
  • the service element may be an element including information on services described by the corresponding SLT, and a service element may exist for each service.
  • the Service element contains the @serviceId property, the @sltSvcSeqNum property, the @protected property, the @majorChannelNo property, the @minorChannelNo property, the @serviceCategory property, the @shortServiceName property, the @hidden property, the @broadbandAccessRequired property, the @svcCapabilities property, the BroadcastSvcSignaling element, and / or the svcInetUrl element. It may include.
  • the @serviceId attribute may be an identifier of a corresponding service, and the @sltSvcSeqNum attribute may indicate a sequence number of SLT information for the corresponding service.
  • the @protected attribute may indicate whether at least one service component necessary for meaningful playback of the corresponding service is protected.
  • the @majorChannelNo and @minorChannelNo attributes may indicate the major channel number and the minor channel number of the corresponding service, respectively.
  • the @serviceCategory attribute can indicate the category of the corresponding service.
  • the service category may include a linear A / V service, a linear audio service, an app-based service, an ESG service, and an EAS service.
  • the @shortServiceName attribute may provide a short name of the corresponding service.
  • the @hidden attribute can indicate whether the service is for testing or proprietary use.
  • the @broadbandAccessRequired attribute may indicate whether broadband access is required for meaningful playback of the corresponding service.
  • the @svcCapabilities attribute can provide the capability information necessary for decoding and meaningful reproduction of the corresponding service.
  • the BroadcastSvcSignaling element may provide information related to broadcast signaling of a corresponding service. This element may provide information such as a location, a protocol, and an address with respect to signaling through a broadcasting network of a corresponding service. Details will be described later.
  • the svcInetUrl element may provide URL information for accessing signaling information for a corresponding service through broadband.
  • the sltInetUrl element may further include an @urlType attribute, which may indicate the type of data that can be obtained through the URL.
  • the aforementioned BroadcastSvcSignaling element may include an @slsProtocol attribute, an @slsMajorProtocolVersion attribute, an @slsMinorProtocolVersion attribute, an @slsPlpId attribute, an @slsDestinationIpAddress attribute, an @slsDestinationUdpPort attribute, and / or an @slsSourceIpAddress attribute.
  • the @slsProtocol attribute can indicate the protocol used to deliver the SLS of the service (ROUTE, MMT, etc.).
  • the @slsMajorProtocolVersion attribute and @slsMinorProtocolVersion attribute may indicate the major version number and the minor version number of the protocol used to deliver the SLS of the corresponding service, respectively.
  • the @slsPlpId attribute may provide a PLP identifier for identifying a PLP that delivers the SLS of the corresponding service.
  • this field may be omitted, and the PLP information to which the SLS is delivered may be identified by combining information in the LMT to be described later and bootstrap information of the SLT.
  • the @slsDestinationIpAddress attribute, @slsDestinationUdpPort attribute, and @slsSourceIpAddress attribute may indicate the destination IP address, the destination UDP port, and the source IP address of the transport packet carrying the SLS of the corresponding service, respectively. They can identify the transport session (ROUTE session or MMTP session) to which the SLS is delivered. These may be included in the bootstrap information.
  • FIG. 4 illustrates a USBD and an S-TSID delivered to ROUTE according to an embodiment of the present invention.
  • One embodiment t4010 of the illustrated USBD may have a bundleDescription root element.
  • the bundleDescription root element may have a userServiceDescription element.
  • the userServiceDescription element may be an instance of one service.
  • the userServiceDescription element may include an @globalServiceID attribute, an @serviceId attribute, an @serviceStatus attribute, an @fullMPDUri attribute, an @sTSIDUri attribute, a name element, a serviceLanguage element, a capabilityCode element, and / or a deliveryMethod element.
  • Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
  • the @globalServiceID attribute is a globally unique identifier of the service and can be used to link with ESG data (Service @ globalServiceID).
  • the @serviceId attribute is a reference corresponding to the corresponding service entry of the SLT and may be the same as service ID information of the SLT.
  • the @serviceStatus attribute may indicate the status of the corresponding service. This field may indicate whether the corresponding service is active or inactive.
  • the @fullMPDUri attribute can refer to the MPD fragment of the service. As described above, the MPD may provide a reproduction description for a service component delivered through a broadcast network or a broadband.
  • the @sTSIDUri attribute may refer to the S-TSID fragment of the service.
  • the S-TSID may provide parameters related to access to the transport session carrying the service as described above.
  • the name element may provide the name of the service.
  • This element may further include an @lang attribute, which may indicate the language of the name provided by the name element.
  • the serviceLanguage element may indicate the available languages of the service. That is, this element may list the languages in which the service can be provided.
  • the capabilityCode element may indicate capability or capability group information of the receiver side necessary for significantly playing a corresponding service. This information may be compatible with the capability information format provided by the service announcement.
  • the deliveryMethod element may provide delivery related information with respect to contents accessed through a broadcasting network or a broadband of a corresponding service.
  • the deliveryMethod element may include a broadcastAppService element and / or a unicastAppService element. Each of these elements may have a basePattern element as its child element.
  • the broadcastAppService element may include transmission related information on the DASH presentation delivered through the broadcast network.
  • These DASH representations may include media components across all periods of the service media presentation.
  • the basePattern element of this element may represent a character pattern used by the receiver to match the segment URL. This can be used by the DASH client to request segments of the representation. Matching may imply that the media segment is delivered over the broadcast network.
  • the unicastAppService element may include transmission related information on the DASH representation delivered through broadband. These DASH representations may include media components across all periods of the service media presentation.
  • the basePattern element of this element may represent a character pattern used by the receiver to match the segment URL. This can be used by the DASH client to request segments of the representation. Matching may imply that the media segment is delivered over broadband.
  • An embodiment t4020 of the illustrated S-TSID may have an S-TSID root element.
  • the S-TSID root element may include an @serviceId attribute and / or an RS element.
  • Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
  • the @serviceId attribute is an identifier of a corresponding service and may refer to a corresponding service of USBD / USD.
  • the RS element may describe information on ROUTE sessions through which service components of a corresponding service are delivered. Depending on the number of such ROUTE sessions, there may be a plurality of these elements.
  • the RS element may further include an @bsid attribute, an @sIpAddr attribute, an @dIpAddr attribute, an @dport attribute, an @PLPID attribute, and / or an LS element.
  • the @bsid attribute may be an identifier of a broadcast stream through which service components of a corresponding service are delivered. If this field is omitted, the default broadcast stream may be a broadcast stream that includes a PLP that carries the SLS of the service. The value of this field may be the same value as the @bsid attribute of SLT.
  • the @sIpAddr attribute, the @dIpAddr attribute, and the @dport attribute may indicate a source IP address, a destination IP address, and a destination UDP port of the corresponding ROUTE session, respectively. If these fields are omitted, the default values may be the source IP address, destination IP address, and destination UDP port values of the current, ROUTE session carrying that SLS, that is, carrying that S-TSID. For other ROUTE sessions that carry service components of the service but not the current ROUTE session, these fields may not be omitted.
  • the @PLPID attribute may indicate PLP ID information of a corresponding ROUTE session. If this field is omitted, the default value may be the PLP ID value of the current PLP to which the corresponding S-TSID is being delivered. According to an embodiment, this field is omitted, and the PLP ID information of the corresponding ROUTE session may be confirmed by combining information in the LMT to be described later and IP address / UDP port information of the RS element.
  • the LS element may describe information on LCT channels through which service components of a corresponding service are delivered. Depending on the number of such LCT channels, there may be a plurality of these elements.
  • the LS element may include an @tsi attribute, an @PLPID attribute, an @bw attribute, an @startTime attribute, an @endTime attribute, an SrcFlow element, and / or a RepairFlow element.
  • the @tsi attribute may represent tsi information of a corresponding LCT channel. Through this, LCT channels through which a service component of a corresponding service is delivered may be identified.
  • the @PLPID attribute may represent PLP ID information of a corresponding LCT channel. In some embodiments, this field may be omitted.
  • the @bw attribute may indicate the maximum bandwidth of the corresponding LCT channel.
  • the @startTime attribute may indicate the start time of the LCT session, and the @endTime attribute may indicate the end time of the LCT channel.
  • the SrcFlow element may describe the source flow of ROUTE.
  • the source protocol of ROUTE is used to transmit the delivery object, and can establish at least one source flow in one ROUTE session. These source flows can deliver related objects as an object flow.
  • the RepairFlow element may describe the repair flow of ROUTE. Delivery objects delivered according to the source protocol may be protected according to Forward Error Correction (FEC).
  • FEC Forward Error Correction
  • the repair protocol may define a FEC framework that enables such FEC protection.
  • FIG. 5 is a diagram illustrating a USBD delivered to MMT according to an embodiment of the present invention.
  • One embodiment of the illustrated USBD may have a bundleDescription root element.
  • the bundleDescription root element may have a userServiceDescription element.
  • the userServiceDescription element may be an instance of one service.
  • the userServiceDescription element may include an @globalServiceID attribute, an @serviceId attribute, a Name element, a serviceLanguage element, a content advisoryRating element, a Channel element, an mpuComponent element, a routeComponent element, a broadbandComponent element, and / or a ComponentInfo element.
  • Each field may be omitted or may exist in plurality, depending on the value of the illustrated Use column.
  • the @globalServiceID attribute, the @serviceId attribute, the Name element and / or the serviceLanguage element may be the same as the corresponding fields of the USBD delivered to the above-described ROUTE.
  • the contentAdvisoryRating element may indicate the content advisory rating of the corresponding service. This information may be compatible with the content advisory rating information format provided by the service announcement.
  • the channel element may include information related to the corresponding service. The detail of this element is mentioned later.
  • the mpuComponent element may provide a description for service components delivered as an MPU of a corresponding service.
  • This element may further include an @mmtPackageId attribute and / or an @nextMmtPackageId attribute.
  • the @mmtPackageId attribute may refer to an MMT package of service components delivered as an MPU of a corresponding service.
  • the @nextMmtPackageId attribute may refer to an MMT package to be used next to the MMT package referenced by the @mmtPackageId attribute in time.
  • the MP table can be referenced through the information of this element.
  • the routeComponent element may include a description of service components of the corresponding service delivered to ROUTE. Even if the linear service components are delivered in the MMT protocol, the NRT data may be delivered according to the ROUTE protocol as described above. This element may describe information about such NRT data. The detail of this element is mentioned later.
  • the broadbandComponent element may include a description of service components of the corresponding service delivered over broadband.
  • some service components or other files of a service may be delivered over broadband. This element may describe information about these data.
  • This element may further include the @fullMPDUri attribute. This attribute may refer to an MPD that describes service components delivered over broadband.
  • the element when the broadcast signal is weakened due to driving in a tunnel or the like, the element may be needed to support handoff between the broadcast network and the broadband band. When the broadcast signal is weakened, while acquiring the service component through broadband, and when the broadcast signal is stronger, the service continuity may be guaranteed by acquiring the service component through the broadcast network.
  • the ComponentInfo element may include information on service components of a corresponding service. Depending on the number of service components of the service, there may be a plurality of these elements. This element may describe information such as the type, role, name, identifier, and protection of each service component. Detailed information on this element will be described later.
  • the aforementioned channel element may further include an @serviceGenre attribute, an @serviceIcon attribute, and / or a ServiceDescription element.
  • the @serviceGenre attribute may indicate the genre of the corresponding service
  • the @serviceIcon attribute may include URL information of an icon representing the corresponding service.
  • the ServiceDescription element provides a service description of the service, which may further include an @serviceDescrText attribute and / or an @serviceDescrLang attribute. Each of these attributes may indicate the text of the service description and the language used for that text.
  • the aforementioned routeComponent element may further include an @sTSIDUri attribute, an @sTSIDDestinationIpAddress attribute, an @sTSIDDestinationUdpPort attribute, an @sTSIDSourceIpAddress attribute, an @sTSIDMajorProtocolVersion attribute, and / or an @sTSIDMinorProtocolVersion attribute.
  • the @sTSIDUri attribute may refer to an S-TSID fragment. This field may be the same as the corresponding field of USBD delivered to ROUTE described above. This S-TSID may provide access related information for service components delivered in ROUTE. This S-TSID may exist for NRT data delivered according to the ROUTE protocol in the situation where linear service components are delivered according to the MMT protocol.
  • the @sTSIDDestinationIpAddress attribute, the @sTSIDDestinationUdpPort attribute, and the @sTSIDSourceIpAddress attribute may indicate a destination IP address, a destination UDP port, and a source IP address of a transport packet carrying the aforementioned S-TSID, respectively. That is, these fields may identify a transport session (MMTP session or ROUTE session) carrying the aforementioned S-TSID.
  • the @sTSIDMajorProtocolVersion attribute and the @sTSIDMinorProtocolVersion attribute may indicate a major version number and a minor version number of the transport protocol used to deliver the aforementioned S-TSID.
  • ComponentInfo element may further include an @componentType attribute, an @componentRole attribute, an @componentProtectedFlag attribute, an @componentId attribute, and / or an @componentName attribute.
  • the @componentType attribute may indicate the type of the corresponding component. For example, this property may indicate whether the corresponding component is an audio, video, or closed caption component.
  • the @componentRole attribute can indicate the role (role) of the corresponding component. For example, this property can indicate whether the main audio, music, commentary, etc., if the corresponding component is an audio component. If the corresponding component is a video component, it may indicate whether it is primary video. If the corresponding component is a closed caption component, it may indicate whether it is a normal caption or an easy reader type.
  • the @componentProtectedFlag attribute may indicate whether a corresponding service component is protected, for example, encrypted.
  • the @componentId attribute may represent an identifier of a corresponding service component.
  • the value of this attribute may be a value such as asset_id (asset ID) of the MP table corresponding to this service component.
  • the @componentName attribute may represent the name of the corresponding service component.
  • FIG. 6 illustrates a link layer operation according to an embodiment of the present invention.
  • the link layer may be a layer between the physical layer and the network layer.
  • the transmitter may transmit data from the network layer to the physical layer
  • the receiver may transmit data from the physical layer to the network layer (t6010).
  • the purpose of the link layer may be to compress all input packet types into one format for processing by the physical layer, to ensure flexibility and future scalability for input packet types not yet defined. have.
  • the link layer may provide an option of compressing unnecessary information in the header of the input packet, so that the input data may be efficiently transmitted. Operations such as overhead reduction and encapsulation of the link layer may be referred to as a link layer protocol, and a packet generated using the corresponding protocol may be referred to as a link layer packet.
  • the link layer may perform functions such as packet encapsulation, overhead reduction, and / or signaling transmission.
  • the link layer ALP may perform an overhead reduction process on input packets and then encapsulate them into link layer packets.
  • the link layer may encapsulate the link layer packet without performing an overhead reduction process.
  • the use of the link layer protocol can greatly reduce the overhead for data transmission on the physical layer, and the link layer protocol according to the present invention can provide IP overhead reduction and / or MPEG-2 TS overhead reduction. have.
  • the link layer may sequentially perform IP header compression, adaptation, and / or encapsulation. In some embodiments, some processes may be omitted.
  • the RoHC module performs IP packet header compression to reduce unnecessary overhead, and context information may be extracted and transmitted out of band through an adaptation process.
  • the IP header compression and adaptation process may be collectively called IP header compression.
  • IP packets may be encapsulated into link layer packets through an encapsulation process.
  • the link layer may sequentially perform an overhead reduction and / or encapsulation process for the TS packet. In some embodiments, some processes may be omitted.
  • the link layer may provide sync byte removal, null packet deletion and / or common header removal (compression).
  • Sync byte elimination can provide overhead reduction of 1 byte per TS packet. Null packet deletion can be performed in a manner that can be reinserted at the receiving end. In addition, common information between successive headers can be deleted (compressed) in a manner that can be recovered at the receiving side. Some of each overhead reduction process may be omitted. Thereafter, TS packets may be encapsulated into link layer packets through an encapsulation process.
  • the link layer packet structure for encapsulation of TS packets may be different from other types of packets.
  • IP header compression will be described.
  • the IP packet has a fixed header format, but some information required in a communication environment may be unnecessary in a broadcast environment.
  • the link layer protocol may provide a mechanism to reduce broadcast overhead by compressing the header of the IP packet.
  • IP header compression may include a header compressor / decompressor and / or adaptation module.
  • the IP header compressor (RoHC compressor) may reduce the size of each IP packet header based on the RoHC scheme.
  • the adaptation module may then extract the context information and generate signaling information from each packet stream.
  • the receiver may parse signaling information related to the packet stream and attach context information to the packet stream.
  • the RoHC decompressor can reconstruct the original IP packet by recovering the packet header.
  • IP header compression may mean only IP header compression by a header compressor, or may mean a concept in which the IP header compression and the adaptation process by the adaptation module are combined. The same is true for decompressing.
  • the adaptation function may generate link layer signaling using context information and / or configuration parameters.
  • the adaptation function may periodically send link layer signaling over each physical frame using previous configuration parameters and / or context information.
  • the context information is extracted from the compressed IP packets, and various methods may be used according to the adaptation mode.
  • Mode # 1 is a mode in which no operation is performed on the compressed packet stream, and may be a mode in which the adaptation module operates as a buffer.
  • Mode # 2 may be a mode for extracting context information (static chain) by detecting IR packets in the compressed packet stream. After extraction, the IR packet is converted into an IR-DYN packet, and the IR-DYN packet can be transmitted in the same order in the packet stream by replacing the original IR packet.
  • context information static chain
  • Mode # 3 t6020 may be a mode for detecting IR and IR-DYN packets and extracting context information from the compressed packet stream.
  • Static chains and dynamic chains can be extracted from IR packets and dynamic chains can be extracted from IR-DYN packets.
  • the IR and IR-DYN packets can be converted into regular compressed packets.
  • the switched packets can be sent in the same order within the packet stream, replacing the original IR and IR-DYN packets.
  • the remaining packets after the context information is extracted may be encapsulated and transmitted according to the link layer packet structure for the compressed IP packet.
  • the context information may be transmitted by being encapsulated according to a link layer packet structure for signaling information as link layer signaling.
  • the extracted context information may be included in the RoHC-U Description Table (RTT) and transmitted separately from the RoHC packet flow.
  • the context information may be transmitted through a specific physical data path along with other signaling information.
  • a specific physical data path may mean one of general PLPs, a PLP to which LLS (Low Level Signaling) is delivered, a dedicated PLP, or an L1 signaling path. path).
  • the RDT may be signaling information including context information (static chain and / or dynamic chain) and / or information related to header compression.
  • the RDT may be transmitted whenever the context information changes.
  • the RDT may be transmitted in every physical frame. In order to transmit the RDT in every physical frame, a previous RDT may be re-use.
  • the receiver may first select PLP to acquire signaling information such as SLT, RDT, LMT, and the like. When the signaling information is obtained, the receiver may combine these to obtain a mapping between the service-IP information-context information-PLP. That is, the receiver can know which service is transmitted to which IP streams, which IP streams are delivered to which PLP, and can also obtain corresponding context information of the PLPs. The receiver can select and decode a PLP carrying a particular packet stream. The adaptation module can parse the context information and merge it with the compressed packets. This allows the packet stream to be recovered, which can be delivered to the RoHC decompressor. Decompression can then begin.
  • signaling information such as SLT, RDT, LMT, and the like.
  • the receiver may combine these to obtain a mapping between the service-IP information-context information-PLP. That is, the receiver can know which service is transmitted to which IP streams, which IP streams are delivered to which PLP, and can also obtain corresponding context information of the PLPs.
  • the receiver detects the IR packet and starts decompression from the first received IR packet according to the adaptation mode (mode 1), or detects the IR-DYN packet to perform decompression from the first received IR-DYN packet.
  • the link layer protocol may encapsulate all types of input packets, such as IP packets and TS packets, into link layer packets. This allows the physical layer to process only one packet format independently of the protocol type of the network layer (here, consider MPEG-2 TS packet as a kind of network layer packet). Each network layer packet or input packet is transformed into a payload of a generic link layer packet.
  • Segmentation may be utilized in the packet encapsulation process. If the network layer packet is too large to be processed by the physical layer, the network layer packet may be divided into two or more segments.
  • the link layer packet header may include fields for performing division at the transmitting side and recombination at the receiving side. Each segment may be encapsulated into a link layer packet in the same order as the original position.
  • Concatenation may also be utilized in the packet encapsulation process. If the network layer packet is small enough that the payload of the link layer packet includes several network layer packets, concatenation may be performed.
  • the link layer packet header may include fields for executing concatenation. In the case of concatenation, each input packet may be encapsulated into the payload of the link layer packet in the same order as the original input order.
  • the link layer packet may include a header and a payload, and the header may include a base header, an additional header, and / or an optional header.
  • the additional header may be added depending on the chaining or splitting, and the additional header may include necessary fields according to the situation.
  • an optional header may be further added to transmit additional information.
  • Each header structure may be predefined. As described above, when the input packet is a TS packet, a link layer header structure different from other packets may be used.
  • Link layer signaling may operate at a lower level than the IP layer.
  • the receiving side can acquire the link layer signaling faster than the IP level signaling such as LLS, SLT, SLS, and the like. Therefore, link layer signaling may be obtained before session establishment.
  • Link layer signaling may include internal link layer signaling and external link layer signaling.
  • Internal link layer signaling may be signaling information generated in the link layer.
  • the above-described RDT or LMT to be described later may correspond to this.
  • the external link layer signaling may be signaling information received from an external module, an external protocol, or an upper layer.
  • the link layer may encapsulate link layer signaling into a link layer packet and deliver it.
  • a link layer packet structure (header structure) for link layer signaling may be defined, and link layer signaling information may be encapsulated according to this structure.
  • FIG. 7 illustrates a link mapping table (LMT) according to an embodiment of the present invention.
  • the LMT may provide a list of higher layer sessions carried by the PLP.
  • the LMT may also provide additional information for processing link layer packets carrying higher layer sessions.
  • the higher layer session may be called multicast.
  • Information on which IP streams and which transport sessions are being transmitted through a specific PLP may be obtained through the LMT. Conversely, information on which PLP a specific transport session is delivered to may be obtained.
  • the LMT may be delivered to any PLP identified as carrying an LLS.
  • the PLP through which the LLS is delivered may be identified by the LLS flag of the L1 detail signaling information of the physical layer.
  • the LLS flag may be a flag field indicating whether LLS is delivered to the corresponding PLP for each PLP.
  • the L1 detail signaling information may correspond to PLS2 data to be described later.
  • the LMT may be delivered to the same PLP together with the LLS.
  • Each LMT may describe the mapping between PLPs and IP address / port as described above.
  • the LLS may include an SLT, where these IP addresses / ports described by the LMT are all IP addresses associated with any service described by the SLT forwarded to the same PLP as that LMT. It can be / ports.
  • the PLP identifier information in the above-described SLT, SLS, etc. may be utilized, so that information on which PLP the specific transmission session indicated by the SLT, SLS is transmitted may be confirmed.
  • the PLP identifier information in the above-described SLT, SLS, etc. may be omitted, and the PLP information for the specific transport session indicated by the SLT, SLS may be confirmed by referring to the information in the LMT.
  • the receiver may identify the PLP to know by combining LMT and other IP level signaling information.
  • PLP information in SLT, SLS, and the like is not omitted, and may remain in the SLT, SLS, and the like.
  • the LMT according to the illustrated embodiment may include a signaling_type field, a PLP_ID field, a num_session field, and / or information about respective sessions.
  • a PLP loop may be added to the LMT according to an embodiment, so that information on a plurality of PLPs may be described.
  • the LMT may describe PLPs for all IP addresses / ports related to all services described by the SLTs delivered together, in a PLP loop.
  • the signaling_type field may indicate the type of signaling information carried by the corresponding table.
  • the value of the signaling_type field for the LMT may be set to 0x01.
  • the signaling_type field may be omitted.
  • the PLP_ID field may identify a target PLP to be described. When a PLP loop is used, each PLP_ID field may identify each target PLP. From the PLP_ID field may be included in the PLP loop.
  • the PLP_ID field mentioned below is an identifier for one PLP in a PLP loop, and the fields described below may be fields for the corresponding PLP.
  • the num_session field may indicate the number of upper layer sessions delivered to the PLP identified by the corresponding PLP_ID field. According to the number indicated by the num_session field, information about each session may be included. This information may include an src_IP_add field, a dst_IP_add field, a src_UDP_port field, a dst_UDP_port field, a SID_flag field, a compressed_flag field, a SID field, and / or a context_id field.
  • the src_IP_add field, dst_IP_add field, src_UDP_port field, and dst_UDP_port field are the source IP address, destination IP address, source UDP port, destination UDP port for the transport session among the upper layer sessions forwarded to the PLP identified by the corresponding PLP_ID field. It can indicate a port.
  • the SID_flag field may indicate whether a link layer packet carrying a corresponding transport session has an SID field in its optional header.
  • a link layer packet carrying an upper layer session may have an SID field in its optional header, and the SID field value may be the same as an SID field in an LMT to be described later.
  • the compressed_flag field may indicate whether header compression has been applied to data of a link layer packet carrying a corresponding transport session.
  • the existence of the context_id field to be described later may be determined according to the value of this field.
  • the SID field may indicate a sub stream ID (SID) for link layer packets carrying a corresponding transport session.
  • SID sub stream ID
  • These link layer packets may include an SID having the same value as this SID field in the optional header.
  • the context_id field may provide a reference to a context id (CID) in the RDT.
  • the CID information of the RDT may indicate the context ID for the corresponding compressed IP packet stream.
  • the RDT may provide context information for the compressed IP packet stream. RDT and LMT may be associated with this field.
  • each field, element, or attribute may be omitted or replaced by another field, and additional fields, elements, or attributes may be added according to an embodiment. .
  • service components of one service may be delivered through a plurality of ROUTE sessions.
  • the SLS may be obtained through the bootstrap information of the SLT.
  • the SLS's USBD allows the S-TSID and MPD to be referenced.
  • the S-TSID may describe transport session description information for other ROUTE sessions to which service components are delivered, as well as a ROUTE session to which an SLS is being delivered.
  • all service components delivered through a plurality of ROUTE sessions may be collected. This may be similarly applied when service components of a service are delivered through a plurality of MMTP sessions.
  • one service component may be used simultaneously by a plurality of services.
  • bootstrapping for ESG services may be performed by a broadcast network or broadband.
  • URL information of the SLT may be utilized. ESG information and the like can be requested to this URL.
  • one service component of one service may be delivered to the broadcasting network and one to the broadband (hybrid).
  • the S-TSID may describe components delivered to a broadcasting network, so that a ROUTE client may acquire desired service components.
  • USBD also has base pattern information, which allows you to describe which segments (which components) are to be routed to which path. Therefore, the receiver can use this to know what segment to request to the broadband server and what segment to find in the broadcast stream.
  • scalable coding for a service may be performed.
  • the USBD may have all the capability information needed to render the service. For example, when a service is provided in HD or UHD, the capability information of the USBD may have a value of “HD or UHD”.
  • the receiver may know which component should be played in order to render the UHD or HD service using the MPD.
  • app components to be used for app-based enhancement / app-based service may be delivered through a broadcast network or through broadband as an NRT component.
  • app signaling for app-based enhancement may be performed by an application signaling table (AST) delivered with SLS.
  • an event which is a signaling of an operation to be performed by the app, may be delivered in the form of an event message table (EMT) with SLS, signaled in an MPD, or in-band signaled in a box in a DASH representation. . AST, EMT, etc. may be delivered via broadband.
  • App-based enhancement may be provided using the collected app components and such signaling information.
  • a CAP message may be included in the aforementioned LLS table for emergency alerting. Rich media content for emergency alerts may also be provided. Rich media may be signaled by the CAP message, and if rich media is present it may be provided as an EAS service signaled by the SLT.
  • the linear service components may be delivered through a broadcasting network according to the MMT protocol.
  • NRT data for example, an app component
  • data on the service may be delivered through a broadcasting network according to the ROUTE protocol.
  • data on the service may be delivered through broadband.
  • the receiver can access the MMTP session carrying the SLS using the bootstrap information of the SLT.
  • the USBD of the SLS according to the MMT may refer to the MP table so that the receiver may acquire linear service components formatted with the MPU delivered according to the MMT protocol.
  • the USBD may further refer to the S-TSID to allow the receiver to obtain NRT data delivered according to the ROUTE protocol.
  • the USBD may further reference the MPD to provide a playback description for the data delivered over the broadband.
  • the receiver may transmit location URL information for obtaining a streaming component and / or a file content item (such as a file) to the companion device through a method such as a web socket.
  • An application of a companion device may request the component, data, and the like by requesting the URL through an HTTP GET.
  • the receiver may transmit information such as system time information and emergency alert information to the companion device.
  • FIG. 8 shows a structure of a broadcast signal transmission apparatus for a next generation broadcast service according to an embodiment of the present invention.
  • a broadcast signal transmission apparatus for a next generation broadcast service includes an input format block 1000, a bit interleaved coding & modulation (BICM) block 1010, and a frame building block 1020, orthogonal frequency division multiplexing (OFDM) generation block (OFDM generation block) 1030, and signaling generation block 1040. The operation of each block of the broadcast signal transmission apparatus will be described.
  • BICM bit interleaved coding & modulation
  • OFDM generation block orthogonal frequency division multiplexing
  • signaling generation block 1040 The operation of each block of the broadcast signal transmission apparatus will be described.
  • IP streams / packets and MPEG2-TS may be main input formats, and other stream types are treated as general streams.
  • the input format block 1000 can demultiplex each input stream into one or multiple data pipes to which independent coding and modulation is applied.
  • the data pipe is the basic unit for controlling robustness, which affects the quality of service (QoS).
  • QoS quality of service
  • One or multiple services or service components may be delivered by one data pipe.
  • a data pipe is a logical channel at the physical layer that carries service data or related metadata that can carry one or multiple services or service components.
  • the BICM block 1010 may include a processing block applied to a profile (or system) to which MIMO is not applied and / or a processing block of a profile (or system) to which MIMO is applied, and for processing each data pipe. It may include a plurality of processing blocks.
  • the processing block of the BICM block to which MIMO is not applied may include a data FEC encoder, a bit interleaver, a constellation mapper, a signal space diversity (SSD) encoding block, and a time interleaver.
  • the processing block of the BICM block to which MIMO is applied is distinguished from the processing block of BICM to which MIMO is not applied in that it further includes a cell word demultiplexer and a MIMO encoding block.
  • the data FEC encoder performs FEC encoding on the input BBF to generate the FECBLOCK procedure using outer coding (BCH) and inner coding (LDPC).
  • Outer coding (BCH) is an optional coding method.
  • the bit interleaver interleaves the output of the data FEC encoder to achieve optimized performance with a combination of LDPC codes and modulation schemes.
  • Constellation Mapper uses QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, NUQ-1024) or non-uniform constellation (NUC-16, NUC-64, NUC-256, NUC-1024)
  • the cell word from the bit interleaver or cell word demultiplexer can then be modulated to provide a power-normalized constellation point.
  • NUQ has any shape, while QAM-16 and NUQ have a square shape. Both NUQ and NUC are specifically defined for each code rate and are signaled by the parameter DP_MOD of PLS2 data.
  • the time interleaver may operate at the data pipe level. The parameters of time interleaving can be set differently for each data pipe.
  • the time interleaver of the present invention may be located between a BICM chain block and a frame builder.
  • the time interleaver according to the present invention may selectively use a convolution interleaver (CI) and a block interleaver (BI) according to a physical layer pipe (PLP) mode, or both.
  • PLP according to an embodiment of the present invention is a physical path used in the same concept as the above-described DP, the name can be changed according to the designer's intention.
  • the PLP mode according to an embodiment of the present invention may include a single PLP mode or a multiple PLP mode according to the number of PLPs processed by the broadcast signal transmitter or the broadcast signal transmitter.
  • time interleaving using different time interleaving methods according to the PLP mode may be referred to as hybrid time interleaving.
  • the hybrid time deinterleaver may perform an operation corresponding to the reverse operation of the aforementioned hybrid time interleaver.
  • the cell word demultiplexer is used to separate a single cell word stream into a dual cell word stream for MIMO processing.
  • the MIMO encoding block can process the output of the cell word demultiplexer using the MIMO encoding scheme.
  • the MIMO encoding scheme of the present invention may be defined as full-rate spatial multiplexing (FR-SM) to provide capacity increase with a relatively small complexity increase at the receiver side.
  • MIMO processing is applied at the data pipe level.
  • NUQ e 1, i and e 2, i
  • the MIMO encoder output pair g1, i and g2, i. Is transmitted by the same carrier k and OFDM symbol l of each transmit antenna.
  • the frame building block 1020 may map data cells of an input data pipe to OFDM symbols and perform frequency interleaving for frequency domain diversity within one frame.
  • a frame according to an embodiment of the present invention is divided into a preamble, one or more frame signaling symbols (FSS), and normal data symbols.
  • the preamble is a special symbol that provides a set of basic transmission parameters for efficient transmission and reception of a signal.
  • the preamble may signal a basic transmission parameter and a transmission type of the frame.
  • the preamble may indicate whether an emergency alert service (EAS) is provided in the current frame.
  • EAS emergency alert service
  • the main purpose of the FSS is to carry PLS data. For fast synchronization and channel estimation, and fast decoding of PLS data, the FSS has a higher density pilot pattern than normal data symbols.
  • the frame building block adjusts the timing between the data pipes and the corresponding PLS data so that a delay compensation block is provided at the transmitter to ensure co-time between the data pipes and the corresponding PLS data.
  • a cell mapper and a frequency interleaver for mapping a PLS, a data pipe, an auxiliary stream, and a dummy cell to an active carrier of an OFDM symbol in a frame.
  • the frequency interleaver may provide frequency diversity by randomly interleaving data cells received from the cell mapper.
  • the frequency interleaver uses a different interleaving seed order to obtain the maximum interleaving gain in a single frame.
  • the frequency interleaver uses a single symbol or data corresponding to an OFDM symbol pair consisting of two sequential OFDM symbols. Operate on corresponding data.
  • OFDM generation block 1030 modulates the OFDM carrier, inserts pilots, and generates time-domain signals for transmission by the cells generated by the frame building block. In addition, the block sequentially inserts a guard interval and applies a PAPR reduction process to generate a final RF signal.
  • the signaling generation block 1040 may generate physical layer signaling information used for the operation of each functional block.
  • Signaling information may include PLS data.
  • PLS provides a means by which a receiver can connect to a physical layer data pipe.
  • PLS data consists of PLS1 data and PLS2 data.
  • PLS1 data is the first set of PLS data delivered to the FSS in frames with fixed size, coding, and modulation that convey basic information about the system as well as the parameters needed to decode the PLS2 data.
  • PLS1 data provides basic transmission parameters including the parameters required to enable reception and decoding of PLS2 data.
  • PLS2 data carries more detailed PLS data about the data pipes and systems and is the second set of PLS data sent to the FSS.
  • PLS2 signaling further consists of two types of parameters: PLS2 static data (PLS2-STAT data) and PLS2 dynamic data (PLS2-DYN data).
  • PLS2 static data is PLS2 data that is static during the duration of a frame group
  • PLS2 dynamic data is PLS2 data that changes dynamically from frame to frame.
  • the PLS2 data may include FIC_FLAG information.
  • FIC Fast Information Channel
  • the FIC_FLAG information is a 1-bit field and indicates whether a fast information channel (FIC) is used in the current frame group.If the value of this field is set to 1, the FIC is provided in the current frame. If the value of the field is set to 0, the FIC is not transmitted in the current frame.
  • the BICM block 1010 may include a BICM block for protecting PLS data
  • the BICM block for protecting PLS data is a PLS FEC encoder. , Bit interleaver, and constellation mapper.
  • the PLS FEC encoder performs external encoding on scrambled PLS 1,2 data using a scrambler for scrambling PLS1 data and PLS2 data, shortened BCH code for PLS protection, and a BCH for inserting zero bits after BCH encoding.
  • An encoding / zero insertion block, an LDPC encoding block for performing encoding using an LDPC code, and an LDPC parity puncturing block may be included.
  • the output bits of zero insertion can be permutated before LDPC encoding.
  • the bit interleaver interleaves the respective shortened and punctured PLS1 data and PLS2 data, and the constellation mapper bit interleaves.
  • the PLS1 data and the PLS2 data can be mapped to the constellation.
  • the broadcast signal receiving apparatus for the next generation broadcast service may perform a reverse process of the broadcast signal transmitting apparatus for the next generation broadcast service described with reference to FIG. 8.
  • An apparatus for receiving broadcast signals for a next generation broadcast service includes a synchronization and demodulation module for performing demodulation corresponding to a reverse process of a procedure executed by a broadcast signal transmitting apparatus and an input signal.
  • a frame parsing module for parsing a frame, extracting data on which a service selected by a user is transmitted, converting an input signal into bit region data, and then deinterleaving the bit region data as necessary, and transmitting efficiency
  • a demapping and decoding module for performing demapping on the mapping applied for decoding, and correcting an error occurring in a transmission channel through decoding, of various compression / signal processing procedures applied by a broadcast signal transmission apparatus.
  • Demodulated by an output processor and a synchronization and demodulation module that executes the inverse process It may include a signaling decoding module for obtaining and processing the PLS information from the signal.
  • the frame parsing module, the demapping and decoding module, and the output processor may execute the function by using the PLS data output from the signaling decoding module.
  • a time interleaving group according to an embodiment of the present invention is directly mapped to one frame or spread over P I frames.
  • Each time interleaving group is further divided into one or more (N TI ) time interleaving blocks.
  • each time interleaving block corresponds to one use of the time interleaver memory.
  • the time interleaving block in the time interleaving group may include different numbers of XFECBLOCKs.
  • the time interleaver may also act as a buffer for data pipe data prior to the frame generation process.
  • the time interleaver according to an embodiment of the present invention is a twisted row-column block interleaver.
  • the twisted row-column block interleaver according to an embodiment of the present invention writes the first XFECBLOCK in the column direction to the first column of the time interleaving memory, the second XFECBLOCK to the next column and the remaining XFECBLOCKs in the time interleaving block in the same manner. You can fill in these. And in an interleaving array, cells can be read diagonally from the first row to the last row (starting from the leftmost column to the right along the row).
  • the interleaving array for the twisted row-column block interleaver may insert the virtual XFECBLOCK into the time interleaving memory to achieve a single memory deinterleaving at the receiver side regardless of the number of XFECBLOCKs in the time interleaving block.
  • the virtual XFECBLOCK must be inserted in front of the other XFECBLOCKs to achieve a single memory deinterleaving on the receiver side.
  • FIG 9 illustrates a writing operation of a time interleaver according to an embodiment of the present invention.
  • the block shown on the left side of the figure represents a TI memory address array, and the block shown on the right side of the figure shows that virtual FEC blocks are placed at the front of the TI group for two consecutive TI groups. It represents the writing operation when two and one are inserted respectively.
  • the frequency interleaver may include an interleaving address generator for generating an interleaving address for applying to data corresponding to a symbol pair.
  • FIG. 10 is a block diagram of an interleaving address generator composed of a main-PRBS generator and a sub-PRBS generator according to each FFT mode included in a frequency interleaver according to an embodiment of the present invention.
  • the interleaving process for an OFDM symbol pair uses one interleaving sequence and is described as follows.
  • x m, l, p is the p th cell of the l th OFDM symbol in the m th frame
  • N data is the number of data cells.
  • H l (p) is an interleaving address generated based on the cyclic shift value (symbol offset) of the PRBS generator and the sub-PRBS generator.
  • FIG. 11 is a flowchart illustrating a broadcast system according to an embodiment of the present invention.
  • the broadcast system may include at least one of a broadcast transmission device C530010, a broadcast reception device C530100 and PD, and / or a companion screen device C530200 or CD.
  • the contents of the components of the broadcast system according to an embodiment of the present invention may include all the contents of the components of the broadcast system described above.
  • the broadcast reception device C530100 may receive an emergency alert message and notify the companion screen device C530200.
  • the broadcast reception device C530100 may transmit an emergency alert message to the companion screen device C530200 using WebSocket and / or Multicast.
  • the PD may receive broadcast service and / signaling data (CS530010).
  • the PD and CD may create a pairing session for bidirectional communication (CS530020).
  • the PD and the CD may generate a pairing session using the UPnP protocol.
  • both the PD application and the CD application can send multicast discovery messages that search and / or advertise their presence and ATSC 3.0 service support.
  • the PD may then receive an emergency alert message subscription request from the CD requesting an emergency alert message (CS530030).
  • the PD may send an emergency alert message subscription response to the CD (CS530040).
  • the PD may receive an emergency alert message subscription update / cancellation request from the CD (CS530050).
  • the PD may transmit an emergency alert message subscription update / cancellation response to the CD (CS530060).
  • the PD may then receive an emergency alert message (CS530070).
  • the PD may notify the CD of the emergency alert message (CS530080).
  • the PD may receive a response from the CD in response to the notification of the emergency alert message (CS530090).
  • FIG. 12 is a diagram illustrating information related to an emergency alert message subscription request according to an embodiment of the present invention.
  • the companion screen device CD may transmit a subscription request to the broadcast reception device CD.
  • the companion screen device CD may transmit an emergency alert message subscription request to the broadcast reception device CD.
  • the CD joins the network and the EAM function is activated (or when the CD application starts)
  • the CD may send an emergency alert message subscription request to the PD to receive the EAM.
  • the emergency alert message subscription request may include at least one of a SubscriptionCallbackURL element, a SubscriptionDuration element, a Geo-loc element, a CDDevID element, a CDAppID element, and / or a CDAppVersion element.
  • the SubscriptionCallbackURL element may indicate Uniform Resource Locator (URL) information for receiving an emergency alert message.
  • URL Uniform Resource Locator
  • the SubscriptionDuration element may indicate the requested period of time before the emergency alert message subscription expires.
  • the requested time period may be in seconds. If the value of the SubscriptionDuration element is a particular value (eg, "-1"), the requested period may indicate an infinite period.
  • the Geo-loc element may indicate a geographical location where an emergency alert message is requested.
  • the CDDevID element may indicate a device identifier for the companion screen device.
  • the CDAppID element may indicate an application identifier for the companion screen device.
  • the CDAppVersion element may indicate version information of an application for the companion screen device.
  • the companion screen device may transmit the emergency alert message subscription request to the broadcast reception device using a specific address (for example, SubscriptionURL).
  • a specific address for example, SubscriptionURL
  • FIG. 13 is a diagram illustrating information related to an emergency alert message subscription response according to an embodiment of the present invention.
  • the broadcast reception device PD may transmit a subscription response to the companion screen device CD.
  • the broadcast reception device may transmit an emergency alert message subscription response to the companion screen device.
  • the broadcast reception device may transmit an emergency alert message subscription response to the companion screen device.
  • the emergency alert message subscription response may include at least one of a StatusCode element, a StatusString element, a SubscriptionID element, a SubscriptionTimeoutDuration element, a PDDevID element, and / or a PDVersion element.
  • the StatusCode element may indicate that the request has been successfully approved. For example, if the StatusCode element has a predetermined value (eg, "aaa”), it can indicate that the request was successfully approved.
  • aaa a predetermined value
  • the StatusString element may indicate a success / failure indication status string of the request.
  • the SubscriptionID element may indicate a subscription identifier for the current emergency alert message subscription.
  • the SubscriptionID element may be used to uniquely identify a subscription from the companion screen device to the broadcast receiving device.
  • the SubscriptionTimeoutDuration element may indicate the actual duration of the expiration of the emergency alert message subscription. For example, the duration may be in seconds. If the value of the SubscriptionTimeoutDuration element is a specific value (eg, "-1"), the actual period when the subscription expires may indicate an infinite period of time.
  • the PDDevID element may indicate a device identifier for the broadcast reception device.
  • the PDVersion element may indicate version information for the broadcast reception device.
  • FIG. 14 is a diagram illustrating information related to an emergency alert message subscription response according to an embodiment of the present invention.
  • the emergency alert message subscription response may include at least one of a StatusCode element and / or a StatusString element.
  • the StatusCode element may indicate a failure status code that explains why the request was not approved. For example, if the StatusCode element has a predetermined value (eg, "xxx"), it can indicate that the SubscriptionCallbackURL element does not exist or is invalid. In addition, if the StatusCode element has a predetermined value (eg, "yyy”), it may indicate that the subscription request cannot be approved.
  • the StatusString element may indicate a success / failure indication status string of the request.
  • 15 is a diagram illustrating information related to an emergency alert message subscription update request according to an embodiment of the present invention.
  • the companion screen device CD may transmit a subscription update request to the broadcast reception device PD.
  • the companion screen device CD may transmit an emergency alert message subscription update request to the broadcast reception device.
  • the companion screen device may send an emergency alert message subscription update request to the broadcast receiving device.
  • the emergency alert message subscription update request may include at least one of a SubscriptionID element, a SubscriptionDuration element, a CDDevID element, a CDAppID element, and / or a CDAppVersion element.
  • the SubscriptionID element may indicate a subscription identifier for the current emergency alert message subscription.
  • the SubscriptionID element may be used to uniquely identify a subscription from the companion screen device to the broadcast receiving device.
  • the SubscriptionDuration element may indicate the requested period of time before the emergency alert message subscription expires.
  • the requested time period may be in seconds. If the value of the SubscriptionDuration element is a particular value (eg, "-1"), the requested period may indicate an infinite period.
  • the CDDevID element may indicate a device identifier for the companion screen device.
  • the CDAppID element may indicate an application identifier for the companion screen device.
  • the CDAppVersion element may indicate version information of an application for the companion screen device.
  • 16 is a diagram illustrating information related to an emergency alert message subscription cancellation request according to an embodiment of the present invention.
  • the companion screen device CD may transmit a subscription cancel request to the broadcast reception device. For example, at any time to cancel a subscription, the companion screen device may send an emergency alert message unsubscribe request to the broadcast reception device.
  • a subscription cancel request (or emergency subscription unsubscribe request) for canceling the companion screen device CD from receiving an emergency alert message from the broadcast receiving device PD and / or The parameters are shown.
  • the emergency alert message subscription cancellation request may include at least one of a SubscriptionID element, a CDDevID element, a CDAppID element, and / or a CDAppVersion element.
  • the SubscriptionID element may indicate a subscription identifier for the current emergency alert message subscription.
  • the SubscriptionID element may be used to uniquely identify a subscription from the companion screen device to the broadcast receiving device.
  • the CDDevID element may indicate a device identifier for the companion screen device.
  • the CDAppID element may indicate an application identifier for the companion screen device.
  • the CDAppVersion element may indicate version information of an application for the companion screen device.
  • 17 is a diagram illustrating information related to an emergency alert message subscription update response according to an embodiment of the present invention.
  • the broadcast reception device PD may transmit a subscription update response to the companion screen device CD. For example, as soon as the subscription update request is received, the broadcast reception device may transmit an emergency alert message subscription update response to the companion screen device.
  • the emergency alert message subscription update response may include at least one of a StatusCode element, a StatusString element, a SubscriptionID element, a SubscriptionTimeoutDuration element, a PDDevID element, and / or a PDVersion element.
  • the StatusCode element may indicate that the request has been successfully approved. For example, if the StatusCode element has a predetermined value (eg, "aaa”), it can indicate that the request was successfully approved.
  • aaa a predetermined value
  • the StatusString element may indicate a success / failure indication status string of the request.
  • the SubscriptionID element may indicate a subscription identifier for the current emergency alert message subscription.
  • the SubscriptionID element may be used to uniquely identify a subscription from the companion screen device to the broadcast receiving device.
  • the SubscriptionTimeoutDuration element may indicate the actual duration of the expiration of the emergency alert message subscription. For example, the duration may be in seconds. If the value of the SubscriptionTimeoutDuration element is a specific value (eg, "-1"), the actual period when the subscription expires may indicate an infinite period of time.
  • the PDDevID element may indicate a device identifier for the broadcast reception device.
  • the PDVersion element may indicate version information for the broadcast reception device.
  • 18 is a diagram illustrating information related to an emergency alert message subscription update response according to an embodiment of the present invention.
  • the emergency alert message subscription update response may include at least one of a StatusCode element and / or a StatusString element.
  • the StatusCode element may indicate a failure status code that explains why the request was not approved. For example, if the StatusCode element has a predetermined value (eg, "xxx"), it can indicate that the SubscriptionCallbackURL element does not exist or is invalid. In addition, if the StatusCode element has a predetermined value (eg, "yyy”), it may indicate that the subscription request cannot be approved.
  • the StatusString element may indicate a success / failure indication status string of the request.
  • 19 is a diagram illustrating information related to an emergency alert message subscription cancellation response according to an embodiment of the present invention.
  • the broadcast reception device PD may transmit a subscription cancellation response to the companion screen device CD. For example, as soon as the subscription cancellation request is received, the broadcast reception device may transmit an emergency alert message subscription cancellation response to the companion screen device.
  • the emergency alert message unsubscribe response may include at least one of a StatusCode element, a StatusString element, a PDDevID element, and / or a PDVersion element.
  • the StatusCode element may indicate a success / failure indication status code indicating a status of a subscription cancellation request. For example, if the StatusCode element has a predetermined value (eg, "aaa”), it can indicate that the unsubscribe request was successfully approved. In addition, if the StatusCode element has a predetermined value (eg, "yyy”), it may indicate that the subscription cancel request (or subscription renewal request) cannot be approved.
  • the StatusString element may indicate a success / failure indication status string of the request.
  • the PDDevID element may indicate a device identifier for the broadcast reception device.
  • the PDVersion element may indicate version information for the broadcast reception device.
  • 20 is a diagram illustrating a response message to an emergency alert message notification message according to an embodiment of the present invention.
  • the companion screen device CD may transmit a response message to the broadcast reception device. For example, when receiving an emergency alert message notification message from the broadcast receiving device, the companion screen device may transmit a response message to the emergency alert message notification message to the broadcast receiving device.
  • the response message to the emergency alert message notification message may include at least one of a StatusCode element, a StatusString element, a SubscriptionID element, and / or an EAMID element.
  • the StatusCode element may indicate a success / failure status code indicating the reception status of the notification message. For example, if the StatusCode element has a predetermined value (eg, "aaa”), it can indicate that the notification message has been successfully received. In addition, if the StatusCode element has a predetermined value (eg, "yyy”), it may indicate that a notification message cannot be received.
  • the StatusString element may indicate a success / failure indication status string of the request.
  • the SubscriptionID element may indicate a subscription identifier for the current emergency alert message subscription.
  • the SubscriptionID element may be used to uniquely identify a subscription from the companion screen device to the broadcast receiving device.
  • the EAMID element may indicate an identifier of an emergency alert message. This identifier can uniquely identify the emergency alert message.
  • FIG. 21 shows a configuration of a broadcast reception device according to an embodiment of the present invention.
  • the broadcast reception device 100 includes a broadcast reception unit 110, an Internet Protocol (IP) communication unit 130, and a control unit 150.
  • IP Internet Protocol
  • the broadcast receiver 110 includes a channel synchronizer 111, a channel equalizer 113, and a channel decoder 115.
  • the channel synchronizer 110 synchronizes the symbol frequency and timing to enable decoding in a baseband that can receive a broadcast signal.
  • the channel equalizer 113 compensates for the distortion of the synchronized broadcast signal.
  • the channel equalizer 113 compensates for the distortion of the synchronized broadcast signal due to the multipath and the Doppler effect.
  • the channel decoder 115 decodes the broadcast signal whose distortion is compensated for.
  • the channel decoder 115 extracts a transport frame from a broadcast signal whose distortion is compensated.
  • the channel decoder 115 may perform forward error correction (FEC).
  • FEC forward error correction
  • the IP communication unit 130 receives and transmits data through the internet network.
  • the control unit 150 includes a signaling decoder 151, a transport packet interface 153, a broadband packet interface 155, a baseband operation control unit 157, a common protocol stack 159, and a service map database 161. ), A service signaling channel processing buffer and parser 163, an A / V processor 165, a broadcast service guide processor 167, an application processor 169, and a service guide database 171. do.
  • the signaling decoder 151 decodes signaling information of a broadcast signal.
  • the transport packet interface 153 extracts a transport packet from a broadcast signal.
  • the transport packet interface 153 may extract data such as signaling information or an IP datagram from the extracted transport packet.
  • the broadband packet interface 155 extracts an IP packet from data received from the Internet.
  • the broadband packet interface 155 may extract signaling data or IP datagram from the IP packet.
  • the baseband operation control unit 157 controls an operation related to receiving broadcast information reception information from the baseband.
  • the common protocol stack 159 extracts audio or video from the transport packet.
  • a / V processor 547 processes the audio or video.
  • the service signaling channel processing buffer and parser 163 parses and buffers signaling information signaling a broadcast service.
  • the service signaling channel processing buffer and parser 163 may parse and buffer signaling information signaling a broadcast service from an IP datagram.
  • the service map database 165 stores a broadcast service list including information on broadcast services.
  • the service guide processor 167 processes terrestrial broadcast service guide data for guiding a program of a terrestrial broadcast service.
  • the application processor 169 extracts and processes application related information from a broadcast signal.
  • the service guide database 171 stores program information of a broadcast service.
  • 22 is a block diagram of a broadcast receiving device according to another embodiment of the present invention.
  • the broadcast reception device 100 includes a broadcast reception unit 110, an Internet Protocol (IP) communication unit 130, and a control unit 150.
  • IP Internet Protocol
  • the broadcast receiver 110 performs one or more processors to perform each of a plurality of functions performed by the broadcast receiver 110. It may include one or more circuits and one or more hardware modules.
  • the broadcast receiving unit 110 may be a system on chip (SOC) in which various semiconductor components are integrated into one.
  • the SOC may be a semiconductor in which various multimedia components such as graphics, audio, video, and modem, and a semiconductor such as a processor and a DRAM are integrated into one.
  • the broadcast receiving unit 110 may include a physical layer module 119 and a physical layer IP frame module 117.
  • the physical layer module 119 receives and processes a broadcast related signal through a broadcast channel of a broadcast network.
  • the physical layer IP frame module 117 converts a data packet such as an IP datagram obtained from the physical layer module 119 into a specific frame.
  • the physical layer module 119 may convert the IP datagram and the like into RS Fraem or GSE.
  • IP communication unit 130 is one or a plurality of processors to perform each of a plurality of functions performed by the IP communication unit (130). It may include one or more circuits and one or more hardware modules.
  • the IP communication unit 130 may be a System On Chip (SOC) in which various semiconductor components are integrated into one.
  • SOC System On Chip
  • the SOC may be a semiconductor in which various multimedia components such as graphics, audio, video, and modem, and a semiconductor such as a processor and a DRAM are integrated into one.
  • the IP communication unit 130 may include an internet access control module 131.
  • the internet access control module 131 controls an operation of the broadcast reception device 100 for acquiring at least one of service, content, and signaling data through an internet communication band.
  • the controller 150 is one or a plurality of processors to perform each of a plurality of functions that the controller 150 performs. It may include one or more circuits and one or more hardware modules.
  • the controller 150 may be a system on chip (SOC) in which various semiconductor components are integrated into one.
  • the SOC may be a semiconductor in which various multimedia components such as graphics, audio, video, and modem, and a semiconductor such as a processor and a DRAM are integrated into one.
  • the controller 150 may include the signaling decoder 151, the service map database 161, the service signaling channel parser 163, the application signaling parser 166, the alert signaling parser 168, the targeting signaling parser 170, and the targeting.
  • Processor 173 A / V Processor 161, Alert Processor 162, Application Processor 169, Scheduled Streaming Decoder 181, File Decoder 182, User Request Streaming Decoder 183, File Database 184, the component synchronizer 185, the service / content acquisition controller 187, the redistribution module 189, the device manager 193, and the data sharing unit 191.
  • the service / content acquisition control unit 187 controls an operation of a receiver for acquiring signaling data related to a service, content, service, or content acquired through a broadcasting network or an internet communication network.
  • the signaling decoder 151 decodes the signaling information.
  • the service signaling parser 163 parses the service signaling information.
  • the application signaling parser 166 extracts and parses signaling information related to the service.
  • the signaling information related to the service may be signaling information related to the service scan.
  • the time-running information related to the service may be signaling information related to content provided through the service.
  • Alert signaling parser 168 extracts and parses alerting related signaling information.
  • the targeting signaling parser 170 extracts and parses information for signaling a targeting information or information for personalizing a service or content.
  • the targeting processor 173 processes the information for personalizing the service or the content.
  • the alerting processor 162 processes the signaling information related to alerting.
  • the application processor 169 controls the application related information and the execution of the application. Specifically, the application processor 169 processes the status and display parameters of the downloaded application.
  • the A / V processor 161 processes an audio / video rendering related operation based on decoded audio or video, application data, and the like.
  • the scheduled streaming decoder 181 decodes the scheduled streaming, which is the content that is streamed on a schedule determined by a content provider such as a broadcaster in advance.
  • the file decoder 182 decodes the downloaded file.
  • the file decoder 182 decodes the file downloaded through the Internet communication network.
  • the user request streaming decoder 183 decodes on demand content provided by the user request.
  • File database 184 stores the file.
  • the file database 184 may store a file downloaded through an internet communication network.
  • the component synchronizer 185 synchronizes content or services.
  • the component synchronizer 185 may decode content decoded by at least one of the scheduled streaming decoder 181, the file decoder 182, and the user request streaming decoder 183.
  • the service / content acquisition control unit 187 controls an operation of a receiver for obtaining at least one of service, content, service, or signaling information related to the content.
  • the redistribution module 189 When the redistribution module 189 fails to receive a service or content through a broadcasting network, the redistribution module 189 performs an operation for supporting at least one of service, content, service-related information, and content-related information.
  • an external management device 300 may request at least one of a service, content, service-related information, and content-related information.
  • the external management device 300 may be a content server.
  • the device manager 193 manages interoperable external devices.
  • the device manager 193 may perform at least one of adding, deleting, and updating an external device.
  • the external device may be able to connect and exchange data with the broadcast receiving device 100.
  • the data sharing unit 191 performs a data transmission operation between the broadcast receiving device 100 and an external device and processes exchange related information.
  • the data sharing unit 191 may transmit A / V data or signaling information to an external device.
  • the data sharing unit 191 may receive A / V data or signaling information from an external device.
  • the broadcast reception device 100 may receive an emergency alert for a disaster situation such as a natural disaster, terrorism, or war through a broadcast network.
  • the broadcast reception device 100 may notify the user of this. This allows many people to quickly and efficiently learn about national disasters. However, unless the user keeps an eye on the broadcast receiving device 100, such an emergency alert may not be noticed. Even if the user does not constantly watch the broadcast receiving device 100, the user has a high probability of always carrying the companion device 200 such as a mobile phone or a tablet. Therefore, if the broadcast reception device 100 may transmit an emergency alert to the companion device 200 and the companion device 200 may display an emergency alert, the broadcast disaster prevention apparatus 100 may notify a user of a national disaster situation quickly and efficiently.
  • FIG. 23 illustrates a process of generating an emergency alert and transmitting it through a broadcasting network according to an embodiment of the present invention.
  • An alert system that manages emergency alerts through broadcast services is provided by government authorities authorized to issue emergency alerts through the Integrated Public Alert & Warning System (IPWS) to enter emergency situations or through other sources. Receive messages according to the Common Alerting Protocol (CAP). The alert system determines if the CAP message corresponds to the current region. If the CAP message corresponds to the current region, the CAP message is inserted into the broadcast signal. Therefore, the CAP message is to be transmitted through the broadcast signal. The operation of receiving the broadcast signal by the broadcast reception device 100 and transmitting an emergency alert to a user will be described.
  • IPWS Integrated Public Alert & Warning System
  • 24 is a view illustrating an example of extracting and displaying an emergency alert signaled through a broadcast network by a broadcast reception device according to an embodiment of the present invention.
  • the broadcast transmission device 200 may extract an emergency alter table (EAT) based on a broadcast signal and extract a CAP message from the EAT.
  • the broadcast transmission device 200 may obtain additional information related to the emergency alert based on the non-real-time service identifier included in the EAT.
  • the broadcast reception device 200 may obtain additional information related to an emergency alert based on the EAS_NRT_service_id field included in the EAT.
  • the broadcast reception device 200 may obtain information on a FLUTE session for transmitting additional information related to an emergency alert from a table signaling a non-real-time service based on a non-real-time service identifier included in the EAT.
  • the table signaling the NRT service may be a service map table (SMT).
  • the broadcast receiving device 200 may receive additional information related to an emergency alert from the corresponding FLUTE session based on the information about the FLUTE session.
  • the broadcast reception device 200 may display an emergency alert in a service guide that receives an emergency alert and displays information about a broadcast service and a program of a broadcast service.
  • the broadcast receiving device 200 may extract a service identifier from a guide access table (GAT), and extract information corresponding to the service identifier from a table signaling a non-real-time service to receive an emergency alert. .
  • GAT guide access table
  • the broadcast reception device 200 may obtain information about a FLUTE session of a service corresponding to a service identifier extracted from the GAT. Thereafter, the broadcast reception device 200 may receive an emergency warning message based on the information on the FLUTE session, and display the emergency warning message in the service guide.
  • FIG. 25 is a view illustrating a service type of an emergency alert service signaled by a broadcast reception device, a service identifier, a variable representing a state of an emergency alert, an action for an emergency alert, and an argument of an action according to an embodiment of the present invention.
  • the broadcast reception device 100 may transmit an emergency alert message to the companion device 200.
  • the method and the broadcast reception device 100 may transmit the message received by the broadcast reception device 100 to the companion device 200. There may be a method of transmitting only some of the received messages to the companion device 200.
  • the UPnP device type according to the embodiment of the present invention is reported as “urn: atsc.org” device: atsc3.0rcvr, and the service type of the EAS UPnP service that can receive EAS data is "urn: atsc.org: service: atsc3 .0: eas: 1 ".
  • a service type of an emergency alert service signaled to a companion device by a broadcast reception device is a value of atsc3.0: atsc3.0eas: 1.
  • the service ID information may have a value of urn: atsc.org: service: atsc3.0eas.
  • a method of delivering an emergency alert message received by a broadcast reception device to a companion device may transmit all received messages to the companion device.
  • the companion device needs to parse the message according to the Emergency Alert Message Type.
  • FIG. 25 illustrate state variables, actions, and arguments belonging to the EAS UPnP service of the first embodiment.
  • the state variable may include a variable indicating emergency alert and an emergency alert property.
  • EmergencyAlert is an essential string type state variable and may be prepared in the form of xml or JSON in which elements such as (c) of FIG. 25 are the same.
  • EmergencyAlert may include received time information, type information of a message, and version information.
  • the received time information may be expressed as ⁇ dateTime>, and may store time information when the broadcast receiving device receives the emergency message.
  • the type information of the message may be expressed as a ⁇ messageType> and may indicate whether the message is in a CAP type or a CMAS type.
  • Version information may be expressed as ⁇ version> and may display version information for each message type.
  • the broadcast reception device may receive an emergency alert message and then parsing it to notify the companion device of the EmergencyAlert state variable in the form of data as described above in an eventing manner.
  • the companion device may parse by emergency message type.
  • EmergencyAlertProperty state variable is an essential string type state variable and can be expressed in XML or JSON format.
  • EmergencyAlertProperty may have information on an Emergency Alert Property of a corresponding Emergency Alert Service. That is, in addition to the type information of the message handled in the above-described embodiment of the emergency alert message format, the EmergencyAlertProperty may have actual emergency alert message content information.
  • EmergencyAlertProperty When EmergencyAlertProperty is delivered to the companion device, it may or may not use an eventing scheme.
  • the Action of the first embodiment may include an action for requesting all emergency alert attributes.
  • This action can be expressed as GetAllEmergencyAlertProperty. This action is required. This action is for getting all the messages in an emergency alert. This action may be used to obtain a modified Emergency Alert Property. Since the action requesting all the emergency alert properties can obtain the content information of the emergency alert message, in this case, the name of the action may be expressed as GetAllEmergencyAlertMessage.
  • the argument for the action of the first embodiment may include an emergency alert attribute factor. This may be expressed as an EmergencyAlertProperty argument.
  • the aforementioned GetAllEmergencyAlertMessage may have an EmergencyAlertProperty argument.
  • the companion device uses the GetAllEmergencyAlertMessage action to obtain emergency alert message content information received by the broadcast reception device, the broadcast reception device may return emergency alert message content information through an EmergencyAlertProperty argument.
  • FIG. 26 is a ladder diagram illustrating an operation of signaling an emergency alert to a companion device by a broadcast reception device according to an embodiment of the present invention.
  • the broadcast reception device 100 and the companion device 200 generate a pairing session in operation S2101.
  • the broadcast receiving device 100 may generate a pairing session with the companion device 200 through the IP communication unit 130.
  • the companion device 200 may generate a pairing session with the broadcast reception device 100 through a communication unit.
  • the broadcast reception device 100 and the companion device 200 may generate a pairing session for bidirectional communication.
  • operations of the broadcast reception device 100 and the companion device 200 may be identical to those of the embodiment of FIG. 208.
  • the companion device 200 requests an emergency alert reception notification from the broadcast reception device 100 in operation S2103.
  • the companion device 200 may request an emergency alert reception notification from the broadcast reception device 100 through a control unit.
  • the companion device 200 may request an emergency alert reception notification from the broadcast reception device 100 using the UPnP protocol.
  • the companion device 200 may request a subscription of an event for an emergency alert reception notification from the broadcast reception device 100 based on an eventing protocol. This is to be notified when a change occurs in an emergency alert state variable of the emergency alert service.
  • the broadcast reception device 100 receives a message including an emergency alert from the broadcast transmission device 300 in operation S2105.
  • the broadcast reception device 100 may receive an emergency alert message from the broadcast transmission device 300 through the broadcast reception unit 110.
  • the broadcast reception device 100 notifies the companion device 200 of the information on the emergency alert message based on the emergency alert message (S2107).
  • the broadcast receiving device 100 may notify the companion device 200 the information on the broadcast emergency alert message based on the emergency information message through the control unit 150.
  • the broadcast receiving device 100 may inform the companion device 200 of the information on the emergency alert message through a parameter representing the information on the emergency alert message.
  • the variable representing the information on the emergency alert message may be EmergencyAlert.
  • the companion device 200 requests information on an emergency alert from the broadcast reception device 100 in operation S2109.
  • the companion device 200 may request an emergency alert from the broadcast reception device 100 through a control unit.
  • the companion device 200 may request an emergency alert through an action for requesting an emergency alert.
  • the action for requesting an emergency alert may be GetAllEmergencyAlertMessage.
  • the broadcast reception device 100 notifies the companion device 200 of information on an emergency alert including all emergency alert messages in operation S2111.
  • the broadcast receiving device 100 may inform the companion device 200 information about an emergency alert including all emergency alert messages through the control unit 150.
  • all emergency alert messages since all emergency alert messages must be transmitted, it may act as a load on the operations of the broadcast receiving device 100 and the companion device 200. Therefore, there is a need for a method for efficiently transmitting an emergency alert message to the companion device 200.
  • the broadcast receiving device 100 may extract and transmit necessary information to the companion device 200 from an emergency alert message.
  • the broadcast reception device 100 may identify an emergency alert from an emergency alert message, information indicating a category of an emergency alert, information indicating a description of an emergency alert, information indicating a region corresponding to an emergency alert, and emergency. At least one of information indicating the urgency of the alarm, information indicating the severity of the disaster that caused the emergency alert, and information indicating the probability of occurrence of the disaster that caused the emergency alert may be extracted.
  • the broadcast reception device 100 corresponds to an identifier that identifies an emergency alert from an emergency alert message, a category that indicates an category of an emergency alert, a description that indicates an explanation for an emergency alert, and an emergency alert.
  • identifier that identifies an emergency alert from an emergency alert message
  • category that indicates an category of an emergency alert
  • a description that indicates an explanation for an emergency alert
  • an emergency alert At least one of areaDesc, which represents an area, urgency, which represents the urgency of an emergency alert, severity, which represents the severity of the disaster that caused the emergency alert, and certainity, which represents the probability of occurrence of the disaster that caused the emergency alert. Can be extracted.
  • FIG. 27 is a ladder diagram illustrating an operation in which a broadcast reception device signals an emergency alert to a companion device according to another embodiment of the present invention.
  • the broadcast receiving device 100 and the companion device 200 generate a pairing session in operation S2121.
  • the broadcast receiving device 100 may generate a pairing session with the companion device 200 through the IP communication unit 130.
  • the companion device 200 may generate a pairing session with the broadcast reception device 100 through a communication unit.
  • the broadcast reception device 100 and the companion device 200 may generate a pairing session for bidirectional communication.
  • operations of the broadcast reception device 100 and the companion device 200 may be the same as the first embodiment described above.
  • the companion device 200 requests an emergency alert reception notification from the broadcast reception device 100 in operation S2123.
  • the companion device 200 may request an emergency alert reception notification from the broadcast reception device 100 through a control unit. This is to be notified when an emergency alert state variable occurs.
  • operations of the companion device 200 may be identical to those of the first embodiment described above.
  • the broadcast receiving device 100 receives an emergency alert message including an emergency alert on the basis of a broadcast service in operation S2125.
  • the broadcast reception device 100 may receive an emergency alert message including an emergency alert from the broadcast transmission device 300 through the broadcast reception unit 110.
  • the broadcast reception device 100 notifies the companion device 200 of the information on the emergency alert message based on the emergency alert message (S2127).
  • the broadcast receiving device 100 may notify the companion device 200 the information on the emergency alert message based on the emergency alert message through the control unit 150.
  • the broadcast reception device 100 may notify the companion device 200 of emergency alert message information through a parameter representing information on the emergency alert message.
  • the broadcast receiving device 100 may inform the companion device 200 of the information on the emergency alert message through a parameter representing the information on the emergency alert message.
  • the variable representing the emergency alert message may be EmergencyAlert.
  • the companion device 200 requests specific information on an emergency alert from the broadcast reception device 100 in operation S2129.
  • the companion device 200 may request specific information on an emergency alert from the broadcast reception device 100 through a control unit.
  • the specific information on the emergency alert may be information on an emergency alert necessary for the companion device 200 to provide an additional function related to the emergency alert.
  • the companion device 200 corresponds to an identifier for identifying an emergency alert from an emergency alert message, information indicating a category of an emergency alert, information indicating a description of an emergency alert, and an emergency alert to the broadcast reception device 100.
  • At least one of the information indicating the area, the information indicating the urgency of the emergency alert, the information indicating the severity of the disaster causing the emergency alert, and the information indicating the probability of occurrence of the disaster causing the emergency alert may be requested.
  • the companion device 200 may identify the emergency alert message from the emergency alert message to the broadcast reception device 100, an identifier indicating an emergency alert category, a category indicating an emergency alert category, a description indicating an emergency alert description, and an emergency alert.
  • AreaDesc an element representing the area corresponding to an alarm, urgency, an element representing the urgency of an emergency alert, severity, an element representing the severity of the disaster that caused an emergency alert, and certainity, an element representing the probability of occurrence of a disaster that caused an emergency alert.
  • the companion device 200 may request specific information about an emergency alert from the broadcast reception device 100 using the aforementioned GetEmergencyAlertMessage action and EmergencyAlertField.
  • a companion device performs a GetEmergencyAlertMessage action by inserting a desired field name in an input parameter as GetEmergencyAlertMessage ("identifier, category, urgency, severity, certainty, description"); can do.
  • the companion device may perform the GetEmergencyAlertMessage action without input parameter such as GetEmergencyAlertMessage (""); to request the entire emergency alert message from the broadcast reception device. In other words, you can use an empty string.
  • the broadcast receiving device 100 extracts specific information on an emergency alert based on the emergency alert message in operation S2131. In more detail, the broadcast receiving device 100 may extract specific information about an emergency alert on the basis of an emergency alert message through the control unit 150. In more detail, the broadcast receiving device 100 may extract specific information on an emergency alert from an emergency alert message through the control unit 150. When the companion device requests all of the emergency alert message, the broadcast reception device may not perform a separate specific information extraction step.
  • the broadcast reception device 100 notifies the companion device 200 of a specific property of an emergency alert in operation S2133.
  • the broadcast receiving device 100 may notify the companion device 200 a specific property of an emergency alert through the control unit 150.
  • the broadcast reception device 100 may notify a specific property of an emergency alert based on a request of the companion device 200. That is, in response to GetEmergencyAlertMessage (), which is a request for information on an emergency alert of the companion device 200, the broadcast reception device may transmit all or part of an emergency alert message content to the companion device in response.
  • GetEmergencyAlertMessage which is a request for information on an emergency alert of the companion device 200
  • the broadcast reception device may transmit all or part of an emergency alert message content to the companion device in response.
  • the case where the broadcast reception device returns the entire emergency alert message is the same as that in the above-described first embodiment.
  • FIG. 28 is a ladder diagram illustrating an operation of signaling an emergency alert by a broadcast reception device to a companion device according to another embodiment of the present invention. That is, a diagram illustrating an operation method of a broadcast reception device and a companion device for receiving an emergency alert state variable corresponding to the third embodiment described above.
  • the broadcast receiving device 100 may generate a pairing session through discovery and pairing with the companion device 200 such as a mobile phone (DS1421). Discovery and pairing may be the same as in the above-described embodiment.
  • the companion device 200 such as a mobile phone (DS1421). Discovery and pairing may be the same as in the above-described embodiment.
  • the companion device 200 may request the broadcast reception device 100 to subscribe for an emergency alert service (DS1422).
  • the companion device may request the broadcast reception device to notify the companion device when a change in the emergency alert state variable of the emergency alert service occurs.
  • the broadcast transmission device 300 may notify the broadcast reception device 100 of the emergency alert message (DS1423).
  • the notified broadcast reception device 100 may notify the companion device 200 of an emergency alert state variable (DS1424).
  • the broadcast reception device 100 may notify the emergency alert state variable according to an 'eventing' protocol.
  • the emergency alert state variable may include a message identifier messageId, a service identifier ServiceId, and message location information messageURL as described above.
  • the companion device 200 may request additional information stored in the broadcast reception device 100 using the received messageId and / or ServiceId (DS1425). In addition, the companion device 200 may request additional information through the URL of the content server 400 using the received messageURL (DS1426).
  • the companion device 200 may transmit the additional information related to the emergency alert message through the URL on the content server 400 or the URI in the broadcast reception device 100 may be the same as the above-described embodiment.
  • FIG. 29 is a ladder diagram illustrating an operation of signaling an emergency alert by a broadcast reception device to a companion device according to another embodiment of the present invention.
  • the broadcast reception device 100 and the companion device 200 generate a pairing session in operation S2161.
  • the broadcast receiving device 100 may generate a pairing session with the companion device 200 through the IP communication unit 130.
  • the companion device 200 may generate a pairing session with the broadcast reception device 100 through a communication unit.
  • the broadcast reception device 100 and the companion device 200 may generate a pairing session for bidirectional communication.
  • the companion device 200 requests an emergency alert reception notification from the broadcast reception device 100 in operation S2163.
  • the companion device 200 may request an emergency alert reception notification from the broadcast reception device 100 through a control unit. This is for the companion device to be notified when a change occurs in a state variable indicating an emergency alert of the emergency alert service.
  • the broadcast receiving device 100 receives an emergency alert message including an emergency alert on the basis of a broadcast service in operation S2165.
  • the broadcast reception device 100 may receive an emergency alert message including an emergency alert from the broadcast transmission device 300 through the broadcast reception unit 110.
  • the broadcast receiving device 100 notifies the companion device 200 of the information on the emergency alert message and the UI information on the emergency alert based on the emergency alert message (S2167).
  • the broadcast receiving device 100 may notify the companion device 200, via the control unit 150, of the information on the emergency alert message and the UI information on the emergency alert based on the emergency alert message.
  • the UI information on the emergency alert may include a list of UIs for the emergency alert.
  • the companion device 200 requests the UI for the emergency alert from the broadcast reception device 100 based on the UI information on the emergency alert in operation S2169.
  • the companion device 200 may request a UI for emergency alert from the broadcast reception device 100 through the control unit based on the UI information on the emergency alert.
  • the broadcast reception device 100 transmits a URI for obtaining a UI for emergency alert to the companion device 200 based on a request of the companion device 200 in operation S2171.
  • the broadcast reception device 100 may transmit a URI for obtaining a UI for emergency alert to the companion device 200 based on a request of the companion device 200 through the controller 150.
  • the companion device 200 displays the UI for emergency alert on the basis of the URI for obtaining the UI for emergency alert in operation S2173.
  • the companion device 200 may display the UI for the emergency alert based on a URI for obtaining the UI for the emergency alert through the control unit.
  • the companion device 200 may obtain a UI based on a URI for obtaining a UI for an emergency alert.
  • the companion device 200 may obtain a UI for emergency alert from an external server.
  • the companion device 200 may receive at least one of an image file, an HTML file, and an XML file for the UI for emergency alert from an external server.
  • the external server may be the content / signaling server 400.
  • the companion device 200 may store a UI for an emergency alert in advance, and bring up a UI corresponding to a URI among the stored UIs.
  • the companion device 200 may display a UI for an emergency alert obtained through such an operation. Through this operation, the companion device 200 may process an emergency alert, thereby reducing the load of the companion device 200.
  • a parser for parsing an emergency message is required in the companion device, but the companion device used in the fourth embodiment does not need a parser for parsing an emergency message. This is because the companion device receives a UI reconstructed from the parsed emergency message from the outside.
  • FIG. 30 is a ladder diagram illustrating an operation in which a broadcast reception device signals an emergency alert to a companion device according to another embodiment of the present invention.
  • the ladder diagram according to the case of using the GetEmergencyAlertURI action in the fourth embodiment described above.
  • the broadcast receiving device 100 and the companion device 200 generate a pairing session (DS1461).
  • the broadcast receiving device 100 may generate a pairing session with the companion device 200 through the IP communication unit 130.
  • the companion device 200 may generate a pairing session with the broadcast reception device 100 through a communication unit.
  • the broadcast reception device 100 and the companion device 200 may generate a pairing session for bidirectional communication.
  • the companion device 200 requests an emergency alert reception notification from the broadcast reception device 100 in operation DS1462.
  • the companion device 200 may request an emergency alert reception notification from the broadcast reception device 100 through a control unit. This is for the companion device to be notified when a change occurs in a state variable indicating an emergency alert of the emergency alert service.
  • the broadcast receiving device 100 receives an emergency alert message including an emergency alert on the basis of a broadcast service (DS1463).
  • the broadcast reception device 100 may receive an emergency alert message including an emergency alert from the broadcast transmission device 300 through the broadcast reception unit 110.
  • the broadcast reception device may change an emergency alert state after receiving an emergency alert message including an emergency alert (DS1464). After receiving a message including an emergency alert, the broadcast reception device may configure a UI that expresses an emergency alert message and related additional information using a Remote UI Service. As another example of the present scheme, there may be a scheme using a UPnP Remote UI service. The broadcast reception device may inform the companion device that an emergency alert has occurred by changing the emergency alert state.
  • the broadcast reception device 100 may notify the companion device 200 of the information on the emergency alert message and the URI information on the emergency alert based on the emergency alert message (DS1465).
  • the broadcast receiving device 100 may notify the companion device 200, via the control unit 150, the information on the emergency alert message and the URI information on the emergency alert based on the emergency alert message.
  • the companion device 200 displays the UI for the emergency alert based on the URI for obtaining the UI for the emergency alert (DS1466).
  • the companion device 200 may display the UI for the emergency alert based on a URI for obtaining the UI for the emergency alert through the control unit.
  • the companion device 200 may obtain a UI based on a URI for obtaining a UI for an emergency alert.
  • the companion device 200 may obtain a UI for emergency alert from an external server.
  • the companion device 200 may receive at least one of an image file, an HTML file, and an XML file for the UI for emergency alert from an external server.
  • the external server may be the content / signaling server 400.
  • the companion device 200 may store a UI for an emergency alert in advance, and bring up a UI corresponding to a URI among the stored UIs.
  • the companion device 200 may display a UI for an emergency alert obtained through such an operation. Through this operation, the companion device 200 may process an emergency alert, thereby reducing the load of the companion device 200.
  • a parser for parsing an emergency message is required in the companion device, but the companion device used in the fourth embodiment does not need a parser for parsing an emergency message. This is because the companion device receives a UI reconstructed from the parsed emergency message from the outside.
  • 31 is a ladder diagram illustrating an operation of signaling an emergency alert to a companion device by a broadcast receiving device according to an embodiment of the present invention.
  • the broadcast reception device 100 or C100 receives an emergency alert message from the broadcast transmission device 300 through a broadcast network (broadcast method), and receives the received emergency alert message (emergency). All attributes and / or some attributes of the alert message may be delivered to the at least one companion device 200, C200, or companion screen device C200 in a multicast manner.
  • the broadcast reception device 100 does not make a subscription request for an emergency alert message, but does not request at least one companion device 200 in a multicast manner. ) Can be delivered.
  • the broadcast reception device 100 according to an embodiment of the present invention may multi-cast all attributes and / or some attributes of an emergency alert message to at least one companion device 200 in a multicast manner. ) Can be delivered.
  • the multicast method is a method in which one broadcast receiving device 100 simultaneously transmits data (or datagrams) to a plurality of companion devices 200 connected to a network through an internet network. For example, one broadcast reception device 100 may transmit data to at least one companion device 200 of a selected specific group. Multicasting allows data to be unidirectionally forwarded to one-to-many specific devices. In contrast, the broadcast method differs from the multicast method in that data is unidirectionally transmitted to all unspecified multiple devices. Thus, the multicast scheme can simultaneously deliver data to at least one device connected to the network.
  • the broadcast receiving device 100 transmits an emergency alert message to the at least one companion device 200 in a multicast manner so that the at least one companion device 200 transmits the broadcast alert device 100. It is possible even if the pairing is not performed, and even if pairing is performed, even without a subscription request for the emergency alert service of the broadcast receiving device 100.
  • the broadcast receiving device 100 and the at least one companion device 200 according to an embodiment of the present invention are connected to a network for multicast.
  • the at least one companion device 200 connected to the network always listens to a multicast address (IP & port) for a predefined emergency alert message (CS1105). ). For example, the at least one companion device 200 prepares to receive an emergency alert multicast message including an emergency alert message through a predefined multicast address (eg, 239.255.255.251:1900).
  • a predefined multicast address eg, 239.255.255.251:1900.
  • the broadcast reception device 100 receives a broadcast signal including an emergency alert message from the broadcast transmission device 300 in operation CS1110.
  • the broadcast reception device 100 may receive a broadcast signal including at least one of an emergency alert message and / or signaling information from the broadcast transmission device 300 by using the broadcast reception unit 110 or the broadcast interface C110. Can be.
  • the broadcast signal may include an emergency alter table (EAT), and the emergency alert table may include an emergency alert message.
  • the emergency alert message may include an emergency alert.
  • the broadcast signal may include signaling information
  • the signaling information may include a service map table (SMT)
  • the service map table may include additional information about an emergency alert message.
  • the additional information about the emergency alert message may include a ServiceId indicating an identifier of a service being serviced by the broadcast receiving device 100, a MessageId indicating an identifier of an emergency alert message received by the broadcast receiving device 100, and / or associated with an emergency alert. It may include at least one of a Content Server in which the additional information is located and / or a MessageURI indicating an address in the broadcast reception device 100.
  • the broadcast reception device 100 may generate an emergency alert multicast message including information related to an emergency alert message based on the emergency alert message.
  • the broadcast receiving device 100 may generate an emergency alert multicast message including all attributes and / or some attributes of the emergency alert message based on the emergency alert message using the controller 150.
  • the broadcast receiving device 100 may generate an emergency alert multicast message including additional information on the emergency alert message based on the additional information on the emergency alert message by using the controller 150.
  • the broadcast reception device 100 may generate a user interface (UI) to be shown to a user after receiving an emergency alert message.
  • the broadcast reception device 100 may generate user interface information on an emergency alert by using the controller 150.
  • the user interface information may indicate an attribute for the user interface.
  • the user interface information for the emergency alert may include information about a service identifier, a message identifier, and a location list for the emergency alert.
  • the service identifier may be expressed as ⁇ ServiceId> and may indicate an identifier for a service being serviced by the broadcast reception device.
  • the message identifier may be expressed as ⁇ MessageId> and may indicate an identifier of an emergency alert message received by the broadcast reception device.
  • the location list may be expressed as ⁇ URIList> and may indicate a list of URIs indicating locations of html pages constituting the UI by using an emergency alert message received by the broadcast reception device.
  • the location information included in the location list may be represented by ⁇ URI> and may indicate the location of the html page configuring the UI by using the emergency alert message received by the broadcast reception device.
  • the location information may be included in the ⁇ URIList> and may be one or more. Thereafter, the broadcast reception device 100 may generate an emergency alert multicast message including UI information on an emergency alert by using the controller 150.
  • the broadcast reception device 100 notifies (or multicasts) an emergency alert multicast message to a predefined multicast address in a multicast manner (CS1120).
  • the broadcast reception device 100 may include at least one of all and / or some attributes of an emergency alert message, additional information on an emergency alert message, and / or UI information on an emergency alert.
  • the message can be multicasted (or multicasted) to a predefined multicast address.
  • the predefined multicast address may be a multicast address for transmission of an emergency alert multicast message within a network for multicast.
  • the broadcast reception device 100 may notify the at least one companion device 200 connected to the network by using the control unit 150, an emergency alert multicast message.
  • the companion device 200 may receive an emergency alert multicast message in a multicasting manner (CS1130).
  • the companion device 200 may include an emergency alert multicast message including at least one of all attributes and / or some attributes of the emergency alert message, additional information on the emergency alert message, and / or UI information on the emergency alert. Can be received through a predefined multicast address in the network for multicast.
  • the companion device 200 may process an emergency alert multicast message. For example, the companion device 200 may display all attributes and / or some attributes of the emergency alert message by using the controller. In addition, the companion device 200 may request additional information stored in the broadcast reception device 100 based on the messageId and / or ServiceId received using the controller. In addition, the companion device 200 may request additional information through the URL of the content server 400 based on the messageURL received using the controller. In addition, the companion device 200 may request the user interface for emergency alert from the broadcast reception device 100 based on the user interface information for the emergency alert using the control unit. In addition, the companion device 200 displays a user interface for an emergency alert based on a URI for obtaining a user interface for an emergency alert using a control unit.
  • the companion device 200 may display the interface for the emergency alert based on a URI for obtaining the interface for the emergency alert through the control unit.
  • the companion device 200 may obtain an interface for emergency alert from an external server.
  • the companion device 200 may receive at least one of an image file, an HTML file, and an XML file for an interface to an emergency alert from an external server.
  • the external server may be the content / signaling server 400.
  • the companion device 200 may pre-store an interface for an emergency alert and call up an interface corresponding to a URI among the stored interfaces.
  • the companion device 200 may display an interface for an emergency alert obtained through such an operation.
  • FIG. 32 is a diagram illustrating a broadcast system according to an embodiment of the present invention.
  • the broadcast system may include a broadcast transmission device C2760010, a broadband server C2760020, a broadcast reception device C2760100, and / or a companion screen device C2760200.
  • the broadcast transmission device C2760010 may provide a broadcast service.
  • the broadcast transmission device C2760010 may include at least one of a controller (not shown) and / or a transmitter (not shown).
  • the broadcast transmission device C2760010 may be represented by a transmitter.
  • the broadcast service may include at least one of content (or linear service), application (or non-linear service), and / or signaling information.
  • the broadcast service may include an electronic service guide (ESG), an emergency alert message, and / or media playback status information. Details of the broadcast service may include all of the above descriptions.
  • the broadcast transmission device C2760010 may transmit a broadcast stream including a broadcast service using at least one of satellite, terrestrial wave, and cable broadcast network.
  • the broadband server C2760020 may receive a request from the broadcast receiving device C2760100 and / or the companion screen device C2760200 through an internet network and provide a broadcast service through the internet network in response.
  • the broadband server C2760020 may include various data including content.
  • the broadband server C2760020 may include the aforementioned content server.
  • the broadcast receiving device C2760100 may receive a broadcast service through a broadcast network and / or an internet network. Thereafter, the broadcast reception device C2760100 may connect with the companion screen device C2760200. Thereafter, the broadcast reception device C2760100 may transmit a broadcast service to the companion screen device C2760200.
  • the broadcast service may include at least one of content (or linear service), application (or non-linear service), and / or signaling information.
  • the broadcast service may include an electronic service guide (ESG), an emergency alert message, and / or media playback status information.
  • ESG electronic service guide
  • the broadcast reception device C2760100 may be expressed as a receiver, a first receiver, a first screen device, a master device (MD), and / or a primary device (PD).
  • the broadcast receiving device C2760100 may include a broadcast interface C2760110 (or a broadcast receiver), a broadband interface C2760130 (or an IP transceiver), a companion screen interface C2760140 (or an App transceiver), a decoder (not shown), a display (not shown). H), and / or the controller C410150.
  • the broadcast interface C2760110 may receive a broadcast stream including a broadcast service.
  • the broadcast stream may be transmitted using at least one of satellite, terrestrial wave, and cable broadcasting network.
  • the broadcast interface C2760110 may include at least one of a satellite tuner, a terrestrial tuner, and a cable tuner to receive a broadcast stream.
  • the broadband interface C2760130 may request a broadcast service from the broadband server C2760020.
  • the broadband interface C2760130 may receive a broadcast service from the broadband server C2760020.
  • the companion screen interface C2760140 may transmit and / or receive broadcast service and / or signaling data to the primary device interface C2760240 of the companion screen device C2760200.
  • a decoder (not shown) may decode the broadcast service.
  • the display (not shown) may display a broadcast service.
  • the controller C2760150 may control operations of the broadcast interface C2760100, the broadband interface C2760130, the companion screen interface C2760140, a decoder, and / or a display.
  • the broadcast receiving device C2760100 may be connected to the companion screen device C2760200 using the controller C2760150.
  • the controller C2760150 may include a primary device network processor C2760153 and a primary device application processor C2760155.
  • the information about the primary device network processor C2760153 may include all the information about the network processor included in the above-described broadcast receiving apparatus.
  • the contents of the primary device application processor C2760155 may include all the contents of the application processor included in the above-described broadcast receiving apparatus.
  • the primary device application processor C2760155 may directly and / or indirectly communicate with the companion screen interface C2760140 of the broadcast reception device C2760100. In addition, the primary device application processor C2760155 may externally communicate directly and / or indirectly with the primary device interface C2760240 of the companion screen device C2760200. In addition, the primary device application processor C2760155 may externally communicate directly and / or indirectly with the companion screen application processor C2760255 of the companion screen device C2760200.
  • the primary device application processor C2760155 may request a connection with the companion screen device C2760200 to the primary device network processor C2760153.
  • the primary device network processor C2760153 may connect the primary device application processor C2760155 and the companion screen device C2760200 that have requested the connection.
  • the primary device application processor C2760155 may be an application module and an application browser. Or, it may be an HbbTV application.
  • the primary device network processor C2760153 may be implemented as a network module. Alternatively, the primary device network processor C2760153 may be a WebSocket Server.
  • the primary device application processor C2760155 and the companion screen device C2760200 may be regarded as one client. Alternatively, the first client and the second client may each be called a peer.
  • the primary device application processor C2760155 may transmit host request header information indicating broadcast reception device information or companion screen device information operating in the primary device network processor C2760153 to the primary device network processor C2760153.
  • the primary device network processor C2760153 may generate a stream head of the primary device application processor C2760155 and include the stream head in the stream head group when the primary device application processor C2760155 requests a connection.
  • the primary device network processor C2760153 receives a connection request from the companion screen device C2760200
  • the primary device network processor C2760153 generates a stream head of the companion screen device C2760200 and matches the stream head of the primary device application processor C2760155.
  • the primary device network processor C2760153 may remove the stream head of the matched primary device application processor C2760155 or the stream head of the companion screen device C2760200 from the stream head group.
  • the primary device application processor C2760155 may transmit an IP address of the companion screen device C2760200 to be connected, and each primary device application processor C2760155 and / or applications may use the same port.
  • the companion screen device C2760200 may receive a broadcast service from the broadband server C2760020 through an internet network.
  • the companion screen device C2760200 may be represented as a second broadcast receiving device, a second receiver, a second screen device, a slave device (SD), and / or a companion device (CD). have.
  • the companion screen device C2760200 may include a broadband interface C2760230 (or an IP transceiver), a primary device interface C2760240 (or an App transceiver), a decoder (not shown), a display (not shown), and / or a controller (C2760250). It may include at least one of.
  • the number of companion screen devices C2760200 may be plural.
  • the broadband interface C2760230 may request a broadcast service from the broadband server C2760020 and receive a broadcast service from the broadband server C2760020. In addition, the broadband interface C2760230 may receive a broadcast service from the broadcast receiving device C2760100.
  • the primary device interface C2760240 may transmit and / or receive a broadcast service and / or service data through the companion screen interface C2760140 of the broadcast receiving device C2760100.
  • a decoder (not shown) may decode the broadcast service.
  • the display (not shown) may display a broadcast service.
  • the controller C2760250 may control operations of the broadband interface C2760230, the primary device interface C2760240, the decoder, and / or the display.
  • the controller C2760250 may further include a companion screen application processor C2760255.
  • the contents of the companion screen application processor C2760255 may include all the contents of the aforementioned application processor.
  • the companion screen application processor C2760255 may internally communicate directly and / or indirectly with the primary device interface C2760240 of the companion screen device C2760200. In addition, the companion screen application processor C2760255 may directly and / or indirectly communicate with the companion screen interface C2760140 of the C2760100 of the broadcast reception device. In addition, the companion screen application processor C2760255 may directly and / or indirectly communicate with the primary device application processor C2760155 of the broadcast reception device C2760100.
  • FIG 33 illustrates a Websocket-based PD-CD architecture according to an embodiment of the present invention.
  • a Websocket-based architecture communication can be performed between the PD and the app running on the CD side.
  • the PD can include a Websocket server, and a CD can contain individual apps. Each app on the CD can be called a Websocket client.
  • the Websocket Server in the PD may have endpoints for each of the operations / functions provided by the PD. Endpoints can be connected to a CD-side app to deliver an ESG, a media timeline, or a communication between a PD-side app and a CD-side app.
  • a discovery process may be performed between the PD and an app running on the CD side. This discovery process will be described later.
  • information about the websocket server's endpoints can be passed to the CD-side app.
  • the app on the CD side and the websocket server on the PD side can perform a handshake process.
  • the websocket server can send a response to it. This allows the websocket server and the app on the CD side to connect through the endpoint.
  • the CD-side app may request the termination of the connection to the corresponding endpoint (Disconnect Request).
  • the Websocket server responds to the request (Disconnect Response), and the connection with the endpoint can be terminated. Termination of the connection may be performed first at the PD side, or may be automatically terminated in various situations.
  • the above-described process may be a process of interacting with one websocket endpoint. If there are a plurality of endpoints, the above-described process can be performed separately for each endpoint, thereby activating each required endpoint. This process may be performed simultaneously or sequentially on the plurality of endpoints.
  • the websocket server may have a respective endpoint for each function provided. That is, one endpoint may be provided for one function.
  • Endpoints include Service / Content Identification Endpoints, ESG Information Endpoints, Service / Show / Segment Data Endpoints, and Media Timeline Ends Points may be Media Timeline Endpoints, Media Playback State Endpoints, EAS Endpoints, and / or ApptoApp Endpoints.
  • the service / content identification endpoint may be an endpoint that is currently playing at the PD or performs a function of delivering information for identifying a service / content to be played. This endpoint allows the CD-side app to receive that information.
  • the ESG Information Endpoint may be an endpoint on which the CD can be used to receive the ESG. This allows the CD-side app to receive the ESG.
  • the service / show / segment data endpoint may be an endpoint that receives various data about a service.
  • the media timeline endpoint may be an endpoint for delivering media time information of the current time and the currently playing service / content.
  • the above-described service time information or the like may be transmitted through this endpoint.
  • the media playback state endpoint may be an endpoint for delivering playback related information of a service / content currently playing.
  • the playback related information may refer to information such as whether the service / content currently being played is being played at a normal speed, fast-forwarding at 3x speed, or rewinding.
  • the above-mentioned playback status information and the like can be delivered to the CD side app via this endpoint.
  • the EAS endpoint may be an endpoint for delivering EAS information to the CD side.
  • the TV receiver receives the EAS information, it transmits this information to the CD side, so that the risk situation can be notified more efficiently.
  • App-to-App Endpoint This may be an endpoint for communication between an app running on the PD side and an app running on the CD side. Using this endpoint, the PD side app and the CD side app can exchange information by exchanging messages in two ways.
  • the CD-side app accesses each endpoint and performs the connection process, and obtains desired information and communicates with the PD-side app through the endpoint. can do.
  • websocket-based architecture embodiment # 1 Such an architecture may be referred to as websocket-based architecture embodiment # 1.
  • This embodiment can be combined with various embodiments of UPnP-based, HTTP-based architecture, as well as other websocket-based architectures.
  • FIG. 34 illustrates a Websocket-based PD-CD architecture according to another embodiment of the present invention.
  • no endpoint may be provided for each of the functions.
  • one endpoint is provided in the websocket server on the PD side, and that endpoint can perform all the functions described above.
  • This endpoint can be called a companion endpoint.
  • the configuration of other other websocket architectures may be the same as in the embodiments described above.
  • This one endpoint may be an endpoint capable of performing all of the functions performed by the various endpoints in the embodiments described above.
  • this endpoint can perform all the roles that the endpoints, such as the service / content identification endpoint, the ESG information endpoint, and the service / show / segment data endpoint described above. Therefore, by simply connecting to this endpoint, the CD-side app can perform all operations such as receiving ESG, receiving media time information, and communicating with the PD-side app. In this case, however, the CD-side app and the websocket server must be able to identify which function the message is sent to, so that it can contain more specific information or can be extended.
  • this companion endpoint performs all functions, all functions can be performed when connected to this endpoint.
  • the process of connecting to this endpoint may be the same as the process of connecting to the general endpoint described above. In this case, since there is only one endpoint, even if access to any one function is unnecessary, the connection of the endpoint cannot be partially terminated. Conversely, even if only one function is needed, you may have to connect to this companion endpoint.
  • websocket-based architecture embodiment # 2 such an architecture may be referred to as websocket-based architecture embodiment # 2.
  • This embodiment can be combined with various embodiments of UPnP-based, HTTP-based architecture, as well as other websocket-based architectures.
  • 35 is a diagram illustrating a Websocket-based PD-CD architecture according to another embodiment of the present invention.
  • n endpoints are provided, which can perform a total of m functions.
  • n may be less than or equal to m, and both n and m may be integers. That is, in this case, one endpoint may perform one or more functions, and a plurality (n) of these endpoints may be provided.
  • endpoints that perform functions such as service / content identification, ESG delivery, and the like are provided as companion endpoints, while at the same time, the endpoints that perform app-to-app functions are separate “app-to-app endpoints”. It can be provided as.
  • the architecture of this embodiment can be seen as a combination of the above-described websocket-based architectures # 1 and # 2.
  • Various architectures can be configured according to the values of n and m.
  • Various numbers of endpoints are provided, and each endpoint can provide various numbers of functionality.
  • connection to and termination of the connection may be to be performed at each endpoint. That is, the process may have to be performed n times for n endpoints.
  • websocket-based architecture embodiment # 3 Such an architecture may be referred to as websocket-based architecture embodiment # 3.
  • This embodiment can be combined with various embodiments of UPnP-based, HTTP-based architecture, as well as other websocket-based architectures.
  • FIG. 36 illustrates App to app communication in a Websocket based PD-CD architecture according to an embodiment of the present invention.
  • App-to-app communication may be possible between an app running on a PD and an app running on a CD.
  • each app can communicate through a weboscket server.
  • the above-described App to App endpoint may be utilized.
  • companion endpoints that combine app-to-app communication and other functions may be utilized.
  • the CD-side app can connect to the app-to-app communication endpoint of the weboscket server through the same process described above.
  • Apps running on the PD side are also websocket clients, which can also connect to app-to-app communication endpoints on the websocket server.
  • the websocket server may send and receive messages by connecting both sides when a connection request matching each other is received.
  • a websocket server can relay messages from one side to another.
  • FIG. 37 illustrates an HTTP-based PD-CD architecture according to an embodiment of the present invention.
  • communication can be performed between the PD and the app running on the CD side.
  • the PD may include an HTTP server, and the CD may contain individual apps. Each app on the CD can also be called an HTTP client.
  • the HTTP server in the PD may be a server for performing various operations / functions. In order to access each function of this server, you may need the service URL for that service.
  • the CD side app may receive desired information by sending a request to the corresponding service URL.
  • a discovery process may be performed between the PD and an app running on the CD side.
  • information about the URLs of the HTTP server can be delivered to the CD side app.
  • the HTTP clients of the CD side may access the URL and receive necessary information by using the received URL information.
  • the HTTP server may have different URLs for each function. That is, one URL may be provided for one function.
  • Services provided through these service URLs may be similar to the functions provided by the websocket server described above.
  • the CD-side app may receive information for identifying a service / content currently being played or scheduled to be played in the PD. That is, the CD-side app may request service / content identification information with a service / content identification service URL, and the HTTP server of the PD side may deliver the requested information to the CD-side app.
  • ESG information services, media timeline services, and the like may be defined, such as the functionality provided by the aforementioned ESG information endpoints, media timeline endpoints, and the like.
  • the CD-side app can receive desired information by requesting each service URL.
  • each service URL is provided for each service
  • the CD-side app needs to know each URL information and access the corresponding URL to obtain desired information or communicate with the PD-side app.
  • HTTP embodiment # 1 such an architecture may be referred to as HTTP embodiment # 1.
  • This embodiment can be combined with various embodiments of UPnP-based, websocket-based architectures, as well as other HTTP-based architectures.
  • FIG. 38 is a diagram illustrating an HTTP-based PD-CD architecture according to another embodiment of the present invention.
  • the service URL may not be provided for each service.
  • one service URL is provided in the HTTP server of the PD side, and the service URL can perform all the functions described above.
  • This service URL may be called a companion service URL.
  • the configuration of other other HTTP architectures may be the same as in the above-described embodiment.
  • This one service URL may be a service URL capable of performing all the functions performed by the various service URLs in the above-described embodiment. That is, the service URL may perform all the roles played by the service URLs such as the above-described service / content identification service URL, ESG information service URL, and service / show / segment data service URL. Therefore, the CD-side app can receive the ESG or media time information by simply sending a request to the service URL.
  • the request message when sending a request to an HTTP server, the request message may be extended, such as appending a new variable to the query term. This is because it needs to be identified what information is being sent to the companion service URL in order to receive it.
  • the HTTP server can parse the request and deliver the information the CD-side app wants.
  • HTTP embodiment # 2 such an architecture may be referred to as HTTP embodiment # 2.
  • This embodiment can be combined with various embodiments of UPnP-based, Websocket-based architectures, as well as other HTTP-based architectures.
  • FIG. 39 illustrates a PD-CD architecture based on Websocket & HTTP according to an embodiment of the present invention.
  • a PD can have both an HTTP server and a Websocket server.
  • the PD may have an HTTP server and a Websocket server, and may also act as a controlled device on the UPnP architecture.
  • the combined UPnP architecture may be one of the first, second, and third embodiments of the aforementioned UPnP architecture.
  • the websocket architecture that is combined may be one of websocket based architectures # 1, # 2, and # 3
  • the HTTP architecture may be one of HTTP-based architectures # 1, # 2.
  • the PD has an HTTP server and a Websocket server at the same time.
  • the HTTP architecture may be HTTP-based architecture # 2 and the Weboscket architecture may be websocket-based architecture # 3. That is, one service URL address may perform a plurality of functions in the HTTP server.
  • the websocket server provides n endpoints, and these n endpoints can perform multiple functions. Specifically, in the present embodiment, two endpoints are provided, one endpoint serves as an endpoint for app-to-app communication, and the other endpoint serves as an endpoint performing all other functions. have.
  • the respective functions may be shared by an HTTP server and a Websocket server. That is, an HTTP server can be used to perform certain functions so that a single service URL in HTTP can be used to receive a request to perform those functions.
  • the Websocket Server can also provide endpoints for performing other functions.
  • HTTP can be used for asynchronous communication
  • websockets can be used for synchronous communication.
  • the ESG information delivery function, the service / show / segment data delivery function, etc. may be performed by HTTP. That is, by sending a request to the service URL of the HTTP server, information such as ESG or service data can be obtained.
  • the service / content identification function, the media playback status function, the app-to-app communication function, and the like may be performed by the websocket.
  • the websocket server can provide companion endpoints that can perform service / content identification, media playback status, and app-to-app endpoints that can perform app-to-app communication.
  • the media timeline function may be performed by HTTP and / or websocket.
  • the function may be provided by both or by either.
  • the EAS information transfer function may be performed through weboscket or by a multicast sender in the PD. If a multicast sender is utilized, the multicast sender in the PD may multicast the EAS information to the devices in the multicast group.
  • FIG. 40 is a diagram illustrating a discovery process of a Websocket endpoint or HTTP service URL using a device description document (DDD) according to an embodiment of the present invention.
  • DDD device description document
  • the PD may multicast a discovery message advertising itself or send a response message to the CD in response to the received M-SEARCH message.
  • the CD side app can obtain the URL from the LOCATION header of the response message for the multicasted discovery message or the M-SEARCH message.
  • This URL may be a URL from which a Device Description Document (DDD) can be obtained.
  • the CD side app can use this URL to obtain a DDD to obtain device description information and the like.
  • DDD Device Description Document
  • the PD may multicast a discovery message for advertising through the NOTIFY method.
  • the URL information for obtaining the DDD can be delivered to the app running on the CD.
  • the PD may send a response message to the CD.
  • URL information for obtaining DDD may be delivered to the CD app (t417010).
  • the CD-side app can request DDD using HTTP GET with the obtained URL.
  • the PD may transmit the DDD to the CD side app through an HTTP response message (t417020).
  • the body of this response message may include a DDD.
  • the addresses of websocket endpoints can be provided to the CD-side app.
  • addresses of service URLs of the HTTP architecture may be provided to a CD-side app through DDD. If an architecture of a combination of two or more protocols is used, the address of the websocket endpoint and / or the address of the service URLs of HTTP may be provided via DDD to the CD side app.
  • FIG. 41 is a diagram illustrating a discovery process of a Websocket endpoint or HTTP service URL using a response header for a DDD request according to an embodiment of the present invention.
  • the PD may multicast a discovery message advertising itself or send a response message to the CD in response to the received M-SEARCH message.
  • the CD side app can obtain the URL from the LOCATION header of the response message for the multicasted discovery message or the M-SEARCH message.
  • This process t421010 may be the same as in the above-described embodiment.
  • This URL is a URL for obtaining DDD, and the CD app can send a message requesting DDD using HTTP GET.
  • the DDD is transmitted through the body of the response message so that the CD-side app can obtain device description information and the like (t421020).
  • the address information of the websocket endpoint or the HTTP service URL has been delivered through the DDD of the response message.
  • the corresponding address information may be delivered through the header of the response message.
  • the body of the response message may be empty and may not transmit any information, or may include a DDD.
  • FIG. 42 is a diagram illustrating a discovery process of a Websocket endpoint or HTTP service URL using a URL of a response header for a DDD request according to an embodiment of the present invention.
  • the PD may multicast a discovery message advertising itself or send a response message to the CD in response to the received M-SEARCH message.
  • the CD side app can obtain the URL from the LOCATION header of the response message for the multicasted discovery message or the M-SEARCH message.
  • This URL is a URL for obtaining DDD, and the CD-side app can send an HTTP GET request to the URL.
  • This process (t423010, t423020) may be the same as in the above-described embodiment.
  • a response message may be received in response to the HTTP GET request.
  • the address information is delivered through the DDD or the response message header of the response message body.
  • a URL for obtaining address information may be delivered through this response message header.
  • the body of the response message may be empty and may not transmit any information, or may include a DDD (t423020).
  • the CD side app can request the address information by sending an HTTP GET request as a URL for the received address information.
  • the PD can send a response message to the CD side app.
  • the address information may be transmitted to the CD side through this response message (t423030). This address information may be delivered through the body of the response message. In some embodiments, the address information may be delivered through a header of the response message.
  • FIG. 43 is a diagram illustrating a Websocket-based handshake & connection process according to an embodiment of the present invention (after discovery).
  • the PD may serve as a websocket server, and the CD may correspond to a websocket client.
  • the PD may include a websocket server and / or companion service module.
  • the companion service module may be a module that provides information necessary for a companion device in a TV receiver or the like, or performs overall management related to a companion service.
  • the companion service module may be a hardware module.
  • the PD side websocket server may provide websocket endpoints.
  • An app that can be used in the CD-side web browser may be running.
  • the web browser can also provide a websocket client.
  • the companion service module on the PD side may request the websocket server to create a websocket endpoint (t426010).
  • a websocket endpoint t426010
  • requests in the form of @ServerEndpoint (/ WS_AA) in Java format can be passed.
  • "/ WS_AA” may mean a related URL. This allows websocket endpoints to be created on the websocket server.
  • the CD-side app can call the API for creating a websocket object (t426020).
  • This API is named newWebsocket and can take the address of a websocket endpoint as its variable.
  • This process creates a websocket object on the CD side.
  • the handshake between the endpoint of the PD websocket server and the CDso websocket object may be performed (t426030).
  • the CD-side app can call an API for adding an OpenEventHandler (t426040).
  • This API can be WebSocketObject.onopen ().
  • a handler can be added in the same way as ex_websocket.onopen.
  • the weboscket server and the client may be connected (t426050).
  • the Websocket client may inform the CD side app that the connection has been opened (t426060).
  • FIG. 44 is a diagram illustrating a handshake & connection process for websocket-based app-to-app communication according to an embodiment of the present invention (after discovery).
  • app-to-app communication may be possible between an app running on the PD side and an app running on the CD side.
  • the websocket server can relay messages, data, etc. between the two.
  • the PD side app can call the API to create a new websocket object on the websocket client within the PD.
  • the newWebsocket API described above may be utilized.
  • a websocket object for the PD side app may be created.
  • the companion service module on the PD side can create a websocket endpoint by calling an API to the websocket server (t427020, t427030). This process is as described above. In this case, since an endpoint for app-to-app communication must be created, a URL (for example, / ApptoApp) related to app-to-app communication can be used as a variable. Thereafter, the local websocket client and the websocket server of the PD may perform the handshake process (t427040).
  • the CD-side app can also create a websocket object (t427050).
  • the websocket server of the PD and the websocket object of the CD side may perform a handshake process (t427060).
  • the websocket client on the PD side and the websocket client on the CD side can call the API to add an OpenEventHandler (t427091, t427090). This process is as described above. Through this, each websocket client can be connected to the websocket server (t427070, t427100). Once connected, each websocket client can notify each app as an event that the connection has been opened (t427080, t427110).
  • the CD side app and the PD side app may communicate with each other (t427120). Both apps can pass messages from one side to the other via a websocket server. In other words, a websocket server can relay messages from one client to another. This two-way communication process will be described later in detail.
  • 45 is a diagram illustrating a two-way communication process based on Websockets (after connection) according to an embodiment of the present invention.
  • the CD-side app and the PD-so websocket server are connected through the above-described processes (t428010).
  • the websocket client may inform the CD-side app that the connection has been opened (t428020).
  • the companion service module may call an API to receive a message (t428030).
  • APIs such as Java's @OnMessage can be utilized. This allows the websocket server to be ready to receive messages.
  • the CD-side app can call the API for adding a MessageEventHandler (t428040).
  • an API such as WebSocketObject.onmessage () can be called.
  • an API may be called in the same manner as ex_websocket.onmessage. This process allows the CDso websocket client to be ready to send and receive messages.
  • the CD-side app can call an API to send a message (t428050).
  • an API such as WebSocketObject.send (message1) can be called.
  • an API may be called in the same manner as ex_websocket.send (message1).
  • a message may be delivered to the weboscket server (t428060).
  • the weboscket server may deliver the received message (message 1) to the companion service module (t428070).
  • the companion service module may transmit a message (message 2) corresponding thereto (t428080, t428090, t428100).
  • the companion service module may call an API for sending a message (t428080).
  • a Java API such as session.getBasicRemote (). SendText (message2) or session.getBasicRemote (). SendObject (message2) can be called.
  • FIG. 46 is a diagram illustrating a websocket based App to App 2 way communication process according to an embodiment of the present invention (after connection / CD to PD).
  • CD-side app the PD-side websocket server, and the app running on the PD side are connected through the above-described processes.
  • Each app may be in an event that a connection is opened from a websocket client.
  • the companion service module may call an API to receive a message, through which the websocket server may be ready to receive the message (t429030).
  • the PD side app calls the API to add a MessageEventHandler, and the PD side websocket client can also be ready to receive the message (t429040).
  • the CD-side app can also make the websocket client ready for receiving messages via API calls (t429020). The detailed procedure is as described above.
  • the CD-side app can call the API to send a message (t429050).
  • This may be utilized as the above-described API, for example, remote_websocket.send (message1). This allows the message to be delivered to the websocket server (t429060).
  • the websocket server may send this message (message 1) to the companion service module (t429070).
  • the companion service module can search the local websocket session to forward it to the local websocket client on the PD side. If the companion service module finds a local websocket session, it can call the API to deliver a message (message 1) (t429080). At this time, as described above, in order to transmit an object in a text or JSON format, a Java API such as session.getBasicRemote (). SendText (message1) or session.getBasicRemote (). SendObject (message1) may be called.
  • a Java API such as session.getBasicRemote (). SendText (message1) or session.getBasicRemote (). SendObject (message1) may be called.
  • the websocket server forwards this message (message 1) to the websocket client (t429090), and the websocket client may forward it back to the PD side app (t429100).
  • FIG. 47 is a view illustrating a websocket based App to App 2 way communication process according to an embodiment of the present invention (after connection / PD to CD).
  • CD-side app the PD-side websocket server, and the app running on the PD side are connected through the above-described processes.
  • Each app may be in an event that a connection is opened from a websocket client.
  • the websocket server and each websocket client may be ready to send / receive a message by the same process as described above.
  • the PD side app can call the API to send a message (t430010).
  • This may be utilized as the above-described API, for example, local_websocket.send (message2).
  • the message may be delivered to the websocket server (t430020).
  • the websocket server may deliver this message (message 2) to the companion service module (t430030).
  • the companion service module can search the remote websocket session to forward it to the remote websocket client on the CD side.
  • the companion service module may call an API to deliver a message (t2) (t430040).
  • a Java API such as session.getBasicRemote (). SendText (message2) or session.getBasicRemote (). SendObject (message2) may be called.
  • the websocket server may deliver this message (message 2) to the websocket client (t430050), and the websocket client may pass it back to the CD-side app (t430060).
  • FIG. 48 is a diagram illustrating an HTTP-based Request-Response process according to an embodiment of the present invention (after discovery).
  • the CD side app may call an API to the HTTP client to send a message request (t431020).
  • the HTTP client may send a message request to an appropriate URL according to the request among the HTTP service URLs learned in the discovery process (t431030).
  • the message request can be sent to one companion service URL according to the above-described embodiment.
  • the content of the request may be identified by the query term of the request.
  • the HTTP server may transmit a request message to the companion service module in the PD (t431040).
  • the companion service module may call an API to deliver the requested message message1 to the CD side (t431050).
  • the HTTP server accordingly transmits the message (message 1) to the HTTP client (t431060), and the HTTP client may deliver the message to the CD-side app (t431070).
  • FIG. 49 illustrates an architecture for an emergency alert (EA) between a receiver (PD) and a CD according to an embodiment of the present invention.
  • EA emergency alert
  • the PD may receive an EAM (EA Message) and deliver it to the CD (s) in a multicast manner.
  • EA Message EA Message
  • the multicast method there may be no or no prior process for delivering EA messages.
  • the PD can repeatedly multicast the EAM.
  • the PD can receive the EAM and deliver it to the CD (s) using the WebSocket protocol.
  • the reliability of the delivery can be increased.
  • a preliminary process may be necessary to deliver EAM and the like.
  • This preprocess may include device discovery, running a CD app, establishing a websocket connection, and the like.
  • the EAM can be delivered only after the websocket connection is established through the preprocess. This can be a disadvantage for EA, where speed is important.
  • a PD may simultaneously support EAM delivery based on a multicast scheme and a web socket scheme. That is, in this architecture, PD can deliver EAM according to multicast method, EAM according to WebSocket protocol, or EAM using both methods at the same time.
  • the PD may first deliver the received EAM to the CD (s) via a multicast scheme.
  • the PD can then deliver the EAM to the CD (s) via the websocket connection after performing the necessary preprocessing.
  • the second EAM delivery over the websocket may be performed for all CDs or only for CDs that have not received a multicast EAM.
  • the EAM can be delivered to the CD quickly without losing low latency, and at the same time, the reliability of the EAM can be secured.
  • FIG. 50 is a diagram illustrating an architecture of a process of executing a CD application according to an embodiment of the present invention.
  • the PD is a primary receiver and can be used to play primary content.
  • the CD may communicate with the PD to provide the same content or supplemental content associated therewith with the content being provided by the PD.
  • the CD may include a laptop, a tablet, a smartphone, and the like.
  • the CD may be used as a receiving device for displaying primary content.
  • the CD may access TV-related content regardless of the PD.
  • Various embodiments may exist in a method of providing a broadcast service and related content through communication between a PD and a CD.
  • the pop-up notification of the TV may inform that the alternative camera view of the concert is available through the CD.
  • the user can run the application, and the application can inform that close-ups of the respective musicians can be provided.
  • the viewer can enjoy the broadcast content by watching a close-up of the guitarist during the guitar solo.
  • the main content of the TV and the additional content of the CD can be synchronized and rendered.
  • each user may be provided with desired additional contents through his CD.
  • User # 1 finds a variety of audio tracks through the application of his CD, selects a video description for visually impaired, and can be provided on his CD.
  • User # 2 can find a variety of closed captions through the application of his CD, select an audio description for hearing impaired, and display it on his CD.
  • User # 3 can convert Spanish subtitles to English dubbing (audio) via his CD application, which can be provided through headphones connected to his CD.
  • the user may also receive a pop-up notification that the game show can be played along the tablet.
  • the user can run an app on the tablet and play along with the game show in real time.
  • each quiz can be provided on the user's tablet, and the quiz can be answered with the participants of the game show.
  • the user's score can be tracked by the application to compare the ranking among different viewers.
  • the app can request information for the user's personalization and provide program recommendation.
  • the PD app may suggest a CD app for facilitating entry of personalized information, and a user may input information through this.
  • Users can receive program recommendations through on-demand apps, and select and watch programs through CD apps. Or you can make the recommended program available on CD.
  • the user may be provided with the content provided in the TV through the CD.
  • the user may continue watching on the CD without missing content.
  • EA Emergency Alert
  • an EA message or a video related thereto may be provided through a CD even if the user is not near the TV.
  • the PD may comprise a web browser and / or a CD manager.
  • the web browser can run a PD application (app).
  • the PD app can include HTML5 and / or related web technologies.
  • the CD manager may be located in the PD to discover CDs on which the launcher is running and send app launch / app install information to these launcher.
  • the CD manager can also be called the companion manager.
  • the CD may include a launcher.
  • the launcher can communicate with the CD manager of the PD. This allows the launcher to launch or install a CD app.
  • the CD app may be a web app by a web browser or a native app.
  • the launchCSApp (Integer enum_id, String payload, function onCSLaunch) method can be utilized.
  • the payload of launchCSApp can specify the endpoint of the websocket server.
  • this payload may also include information about the web server endpoint.
  • This payload may have the following form as an embodiment.
  • the CD manager can request to run the CD app, which can be done by sending an HTTP POST request to the application URL of the CD's launcher.
  • the application URL may be obtained during the device discovery process.
  • the BODY data of the HTTP POST request may contain the payload of launchCSApp.
  • This payload may indicate a CD app to be executed using "launchURL” or the like in one embodiment of the payload described above.
  • the type of CD app to be executed may be indicated using "applicationType” or the like in the above-described embodiment of the payload.
  • FIG. 51 is a diagram illustrating an architecture for communication between an app and an app according to an embodiment of the present invention.
  • the PD may comprise a web browser, CD manager and / or websocket server.
  • the web browser is as described above.
  • the CD manager may provide service endpoints for app to app communication.
  • the websocket server may be located within the PD to handle websocket connections between the PD app and the CD app.
  • the CD may include a launcher.
  • the launcher is not shown.
  • the launcher can communicate with the CD manager of the PD. This allows the launcher to launch or install a CD app.
  • the CD app may be a web app by a web browser or a native app.
  • the location information of the service endpoint can be passed to the CD app as one of the launch parameters of the launchCSApp method.
  • launchCSApp is a method that launches the app on the CD, and its payload can contain service endpoint location information. That is, the corresponding information may be transferred to the CD side in the process of executing the CD app.
  • the service endpoint location information may refer to an endpoint URL of a web socket server (or web server).
  • the endpoint of the websocket server delivered here may be a remote endpoint.
  • FIG. 52 is a diagram illustrating an architecture for communicating from a CD app to a PD app according to an embodiment of the present invention.
  • the PD may comprise a CD manager, a web server and / or a websocket server.
  • the CD manager may respond to the discovery request of the CD app and also provide a service endpoint of the web server and / or web socket server.
  • the web server can be located within the PD to handle HTTP requests from the CD app and respond to the request using the PD's service, content information.
  • the websocket server can be located in the PD to handle websocket connections from the CD app and respond to the request using the PD's service and content information.
  • the CD app may discover the PD and obtain service, content information from the PD via HTTP and / or WebSocket protocol.
  • the CD app can establish communication with the servers serving the PD.
  • the service may mean functions such as ESG delivery, EA delivery, service identification, and app-to-app communication provided by a web server or a web socket server.
  • the CD app can first discover the PD.
  • the CD app may acquire remote endpoints of the web server and / or web socket server.
  • the CD app can obtain service and content information through a websocket server or through an HTTP GET request to the webserver.
  • the CD app may first establish a websocket connection and request service / content information through the websocket connection.
  • the CD app may issue an HTTP GET request, receive an HTTP response, and obtain corresponding information.
  • elements included in the PD or CD in the architecture according to each embodiment are presented as an embodiment, and each element may be added / omitted / changed.
  • the PD or CD may include all or part of each element that has been introduced.
  • Both PD and CD apps can send multicast discovery messages. This discovery message may search for and / or advertise their presence.
  • the CD app can also receive discovery messages from multiple PDs. In this case, the CD app can ask the user which PD to interact with. Here, the information in the discovery message can be displayed to the user to help the user's decision. The reverse process may be performed even if there are a plurality of CDs on the home network.
  • a CD app multicasts a search request message for PD discovery and the PD responds.
  • the location related information of the service endpoint provided by the PD may be delivered as a parameter of the launchURL described above.
  • the CD app may need to discover the endpoint location of the PD's web server or websocket server. In this case, it may be necessary to obtain endpoint information (URL, etc.) separately.
  • the web server endpoint URL and the web socket server endpoint URL can be passed to the CD app during the discovery of the PD and the PD's service endpoint.
  • the CD app can initiate device discovery. This may be started by performing an M-SEARCH using the SSDP protocol with a Search Target header (ST).
  • ST Search Target header
  • the M-SEARCH device discovery request may be as follows.
  • the PD may respond with an LOCATION header, ST, along with HTTP / 1.1 OK.
  • this response message may be of the form: LOCATION may include URL information for a device description.
  • the CD app may request a device description file.
  • This request is an HTTP GET request, which can be requested with the LOCATION URL provided in the response message.
  • This request can be of the form:
  • the PD may respond with an HTTP / 1.1 OK header including the application URL.
  • This application URL can be used as the PD's web server endpoint.
  • This response may be of the form:
  • the application URL may appear as htttp: //xx.xx.xx.xx: yyyy / applications.
  • HTTP GET message may be sent to xx.xx.xx.xx, port yyyy.
  • This HTTP GET message may be of the form:
  • HTTP response can be returned.
  • ⁇ X_ATSC_App2AppURL> can be used as the WebSocket endpoint of the PD.
  • ⁇ X_ ATSC_UserAgent> Value of ATSC Terminal UA header ⁇ / X_ATSC_UserAgent>
  • the PD advertisement message is multicasted.
  • the PD can multicast the SSDP message.
  • This message may be to advertise itself as a PD.
  • the PD may periodically send an advertisement multicast message.
  • the multicast advertisement message may be sent, for example, at 239.255.255.250:1900. This value may vary depending on the embodiment.
  • the advertisement message may include PD device type information, PD identifier, expiration date information, additional information related to the PD, and the like.
  • the PD multicast advertisement message may be in the following form.
  • NT urn: schemas-atsc.org: device: primaryDevice: 1.0
  • NTS ssdp: alive
  • the device may be signaled in an NT (Notification Type) header that the device is of type “urn: schemas-atsc.org: device: primaryDevice: 1.0” (PD device type information).
  • PD device type information PD device type information
  • the identifier of the corresponding PD may be signaled in a unique service name (USN) header that is “uuid: ⁇ device uuid>: urn: schemas-atsc.org: device: primaryDevice: 1.0” (PD identifier).
  • the duration in which the corresponding advertisement message is valid may be signaled in the CASCHE-CONTROL header (valid information).
  • additional information related to the corresponding PD may be signaled in the LOCATION header.
  • a CD advertisement message (multicast).
  • the SSDP message can be multicasted. This message may be sent periodically and may be sent to a preset address.
  • the CD advertisement message may include CD device type information, a CD identifier, an expiration date information, additional information related to the CD, and the like, as described above with the PD advertisement message.
  • the CD multicast advertisement message may be in the following form.
  • NT urn: schemas-atsc.org: device: companionDevice: 1.0
  • NTS ssdp: alive
  • the PD may transmit an SSDP multicast search M-SEARCH request.
  • This request may for example be sent to (239.255.255.250:1900).
  • the search request message may be in the following form.
  • the ST header of the search request message may be set to the following CD device type.
  • the maximum response delay in seconds that the CD can respond can be indicated in the MX header.
  • the CD When the CD receives the above-mentioned search request message from the PD, the CD can respond by sending a unicast search response message.
  • This response message may need to be sent within the maximum response delay indicated in the MX header of the search request message.
  • the search response message may be in the following form.
  • a human-friendly CD device name may be provided in the form of ⁇ DevName> in the message body of the search response message.
  • the payload of the launchCSApp method described above may provide the remote endpoint of the websocket server and / or the multicast address endpoint of the multicast group.
  • the CD app can use these endpoints to receive information from the PD app.
  • app-to-app communication may be performed through a websocket server.
  • FIG. 53 illustrates a message structure for communication between a CD app and a PD according to an embodiment of the present invention.
  • Communication from the CD app to the PD may be performed in the following order.
  • the CD app can discover the PD.
  • the CD app can also obtain the PD's web server and web socket server endpoints.
  • CD apps can request information via HTTP or WebSocket service endpoints. Requests using HTTP can be sent to the web server endpoint URL.
  • the PD can pass that information to the CD app via an HTTP response or WebSocket service endpoint.
  • the HTTP response may be a response to an HTTP request.
  • HTTP can use one service endpoint for asynchronous communication
  • WebSocket can use another endpoint for synchronous communication.
  • communication for ESG delivery and / or service information, service, show and segment data delivery may be performed using HTTP.
  • service and content identification, media playback state delivery, and the like may be performed via a websocket.
  • Communication for media timeline information transfer may be performed over both HTTP and / or websockets.
  • the CD app can send an HTTP GET request to the PD.
  • ATSCCS_PDURL is a URL obtained during the discovery process and may be a web server endpoint URL.
  • ServiceName may indicate a name of a service related to information to request.
  • atsc3.csservice.esg.1 may be a service name for receiving an Electronic Service Guide (ESG)
  • ESG Electronic Service Guide
  • atsc3.csservices.mt.1 may be a service name for receiving media timeline information. If the request URL includes a web server endpoint URL and a ServiceName identifying the ESG service, this may mean that the CD app has requested delivery of ESG information to the web server endpoint.
  • This response may contain a body containing an ATSCCS_Message element, a ServiceName element, and / or a MessageBody element with an HTTP status code.
  • the ServiceName element may include name information of the requested service, and the MessageBody element may include requested information.
  • the PD can receive a WebSocket subscription from the CD app. Upon receipt of this, and if the subscription is valid (not expired or canceled), the PD can send a websocket message to the CD app.
  • the websocket message is delivered via a websocket connection and may need to be delivered to the CD app whenever the information in the message is updated. This websocket message may be called a notification message.
  • the illustrated embodiment t53010 may be a subscription message transmitted by a CD app.
  • the subscription related message between the PD and the CD may have the same format as the illustrated embodiment.
  • the subscription message may include a PDCDMessageVersion element, a PDCDServiceName element, a PDCDMessageType element, a PDCDRespCode element, and / or a PDCDSubDuration element.
  • the PDCDMessageVersion element may indicate a version of a corresponding subscription message. Alternatively, this element may indicate a version of the corresponding subscription message structure. The upper 6 bits may represent a major version and the lower 2 bits may represent a minor version. The version of the subscription message structure may be 0x004, that is, version 1.0.
  • the PDCDServiceName element may indicate a service name associated with a corresponding subscription message. This name may be a name that uniquely identifies a service between PD-CDs. For example, atsc3.services.esg.1 may be a name representing a service for ESG delivery, and atsc3.services.mps.1 is a service for delivering media playback state information. Messages with a PDCDServiceName element value that do not correspond to this service name may be ignored.
  • the PDCDMessageType element may identify the type of the corresponding subscription message.
  • the type of subscription message is illustrated in the embodiment t53020.
  • the subscription message type may include a request message type and a response message type.
  • the request message type may correspond to a message transmitted from CD to PD
  • the response message type may correspond to a message transmitted from PD to CD.
  • the request message type may be a subscribe, cancel and / or renew type.
  • Each message type may be a message type for requesting a subscription, canceling a subscription, or renewing a subscription.
  • the response message type may include a subscribe response, a cancel response, and / or a renew response.
  • Each message type may be a response message type for a message of a subscribed, canceled, or renewed type, respectively.
  • the PDCDRespCode element may include a success or failure code for the request of the message. This element may be included in messages of a response message type among the subscription-related messages described above.
  • the PDCDSubDuration element may indicate the duration of a subscription. When included in a message sent from CD to PD, this element may indicate the duration of the requested subscription. When included in a message sent from the PD to the CD, this element may indicate the duration of the subscription. This element may be included in all types of subscription-related messages except subscription cancellation messages or response messages for subscription cancellations.
  • the illustrated embodiment t53030 may represent the above-described notification message or web socket message.
  • the notification message is transmitted from the PD to the CD and may have the same structure as the illustrated embodiment.
  • the notification message may include a PDCDMessageVersion element, a PDCDServiceName element, and / or a PDCDMessageBodyData element.
  • the PDCDMessageVersion element may indicate the version of the notification message. Alternatively, this element may indicate a version of the notification message structure. The upper 6 bits may represent a major version and the lower 2 bits may represent a minor version. The version of the notification message structure may be 0x004 or version 1.0.
  • the PDCDServiceName element may indicate a service name related to the notification message. This name may be a name that uniquely identifies a service between PD-CDs. For example, atsc3.services.esg.1 may be a name representing a service for ESG delivery, and atsc3.services.mt.1 is a service for delivering media timeline information. Messages with a PDCDServiceName element value that do not correspond to this service name may be ignored.
  • the PDCDMessageBodyData element may contain data elements that are specific to the message.
  • the syntax of this element may follow a separate message structure associated with each PD-CD service.
  • Such individual messages may include service / content identification messages, media timeline messages, media playback state messages, and the like. The individual message structure will be described later.
  • FIG. 54 illustrates a format of a service / content identification message according to an embodiment of the present invention.
  • the present invention proposes a method in which a broadcast receiver (PD) provides various data to a CD (Companion Device) in a next generation hybrid broadcasting environment based on interworking terrestrial broadcasting network and Internet network.
  • PD broadcast receiver
  • CD Compaction Device
  • the CD-side application running on the CD or CD side can also communicate with the PD side.
  • the PD and CD can send and receive various kinds of data.
  • the services of the above-described web socket endpoints, services provided by the HTTP service URL, and the like may be utilized.
  • the service here refers to a companion service between PD-CDs and is different from broadcast service.
  • the PD may transmit information on a broadcast service (channel) or content (program of a channel) that is currently provided or may be provided in the PD on a CD.
  • the PD may also deliver an electronic service guide (ESG) or an emergency alert message (EAM) to a CD.
  • ESG electronic service guide
  • EAM emergency alert message
  • the PD may transmit playback state information of a service being played in the PD or timeline information of the PD to the CD.
  • the EAM is an alert message for notifying an emergency situation or an emergency disaster situation, and may be received by the PD and transmitted to the CD side.
  • the playback state information may mean information such as a playback speed, fast forward, rewind, and the like for a service such as a broadcast service provided by the PD.
  • the timeline information may include media time information and / or UTC absolute time pair for a service such as a broadcast service provided by the PD.
  • the present invention proposes an architecture that supports communication between PD-CDs based on a web socket and supports communication between PD-CDs based on HTTP Request / Response.
  • a communication method according to the websocket or HTTP may be selected.
  • the present invention may enable a flexible architecture configuration and ensure efficiency in communication between PD-CDs.
  • websocket-based communication may be responsible for communication regarding service / content identification and communication regarding playback status.
  • communication by HTTP-based web server can be in charge of communication about ESG delivery and service / show / segment related data delivery.
  • Communication regarding media timeline information delivery may be performed by both websocket and HTTP.
  • the service / content identification for the currently airing service may be performed by HTTP-based communication.
  • a broadcast receiver directly provided an additional service for a broadcast service.
  • related information may cause a problem of covering the broadcast program.
  • the present invention makes it possible to display related information on a user's CD, so that it is possible to provide an additional service that is more convenient to use by taking advantage of a CD device without disturbing viewing or more convenient operation.
  • the present invention proposes a protocol and PD-CD architecture, a service / content identification message format delivered to CD, and the like.
  • the present invention proposes a method in which a CD or a CD-side app accesses a service / content that is being provided or may be provided by a PD using a service / content identification message. Through this, the CD can acquire information on a broadcast service / content in advance, thereby providing an efficient additional service.
  • the present invention proposes a method of providing a hierarchical location URL structure in a service / content identification message so that information on a service / content can be efficiently obtained on a CD side.
  • the present invention proposes a method for efficiently performing the above-described process by utilizing both Websocket and HTTP.
  • additional services that are more convenient to use may be provided without causing inconvenience to viewing the service / content of the PD.
  • the CD side acquires and plays a service / content, obtains and provides additional information related to the service / content, provides an additional service related to the service / content, or pre-processes to efficiently perform such a service. Can be performed.
  • the PD may deliver a service / content identification message to the CD or CD side app.
  • a web socket connection may be established during the discovery process. This process has been described above.
  • the PD's websocket server may receive a subscription message of a companion service for receiving a service / content identification message from a CD side app.
  • the CD side app may be subscribed to the companion service.
  • This companion service may be renewed or unsubscribed.
  • This companion service may be called an ESG service.
  • the websocket server may transmit the changed service / content identification message to the corresponding CD-side app.
  • This service / content identification message may correspond to one type of notification message.
  • This notification message may have a message body with information indicating which companion service the notification message is.
  • the message body may include information corresponding to the service / content identification message.
  • the CD side app can obtain this information and perform the additional actions required.
  • the CD-side app can also receive information about the services / content currently provided by the PD using HTTP. This process can be performed by the HTTP GET message and the corresponding HTTP Response.
  • the CD side app may send an HTTP GET message to the HTTP service URL for identifying the PD's web server or web server's service / content.
  • the PD's web server can then send a response message to the CD-side app.
  • the response message may include information related to the service / content.
  • the above-described service / content related information delivery by the websocket delivers information related to the entire service / content which is being provided or can be provided by the PD, and corresponds to delivering comprehensive information in the form of notification. Can be.
  • the above-described service / content related information delivery by HTTP delivers information on a service / content currently provided by the PD, and the delivery may be performed by a request of a CD-side app.
  • WebSocket is a comprehensive and total information delivery. When there is a big change such as ESG update, it is provided to the CD side without any request from the CD side to enable efficient service / content identification. In this case, the same method as WebSocket is more appropriate, so the PD of the present invention supporting both WebSocket / HTTP can use this information delivery using WebSocket.
  • delivery by HTTP is a delivery that allows the CD side to simply obtain the relevant information by request / response when it is necessary to obtain information on the service / content currently being reproduced on the PD side.
  • the request / response method by HTTP GET is more appropriate, the PD of the present invention may utilize the HTTP protocol.
  • the CD side may receive the service / content identification message by the websocket, and then additionally receive an HTTP response message for the current service / content as needed.
  • the service / content identification message may include ESG information, or may include processing information obtained from the ESG. Also, according to an embodiment, the service / content identification message may borrow the information structure of the ESG.
  • One embodiment of the depicted service / content identification message may include a Service element and / or a Content element. At least one Service element may be included (1... N), and the Content element may include at least zero (0... N).
  • the service element may describe information about a broadcast service of the PD.
  • the information on the service may be obtained from the ESG data model.
  • the Service element may include an id element, a SerivceType element, a Name element, a Description element, and / or a TargetUserProfile element.
  • the id element may indicate an identifier of the corresponding service.
  • the ServiceType element may indicate a service type of a corresponding service.
  • the Name element may indicate the name of the service.
  • the Description element may include a description of the service.
  • the TargetUserProfile element may indicate a user profile targeted by the corresponding service.
  • the Content element may describe information about the content of the PD. If the broadcast service is a channel, the content may mean a program.
  • the content element may include a Programid element, a Name element, a Description element, a TargetUserProfile element, a CARatings element, a Capabilities element, a Component element, a FileContentItem element, a TimelineInfo element, and / or a Location element.
  • the Programid element, the Name element, the Description element, and the TargetUserProfile element may each include an identifier, name, description, and target user profile information of the corresponding content.
  • the CARatings element may include content advisory information of the corresponding content.
  • the Capabilities element is capability information related to the corresponding content, and may indicate capability information necessary for significantly playing the corresponding content.
  • the component element may include information related to a component included in the corresponding content.
  • the Component element may include information related to a continuous component of the corresponding content.
  • the continuous component may mean a presentable component.
  • the audio / video / caption component may correspond to this.
  • the app-based enhancement component or the app component may correspond to this.
  • the @componentType attribute may indicate the type of the corresponding component. For example, when a corresponding property has a value of 0, 1, 2, and 3, the corresponding component may have an audio component, a video component, a closed caption component, and an application component type, respectively. The remaining values can be reserved for future use.
  • the @componentRole attribute can indicate the role or type of the component.
  • the @componentName attribute may indicate the name of the corresponding component. This name may be a human readable name.
  • the @componentLocation attribute may include URL information that can access the component. The CD-side app can obtain the corresponding component through this URL.
  • the FileContentItem element may include information related to a file content item included in the corresponding content.
  • the FileContentITem element may include additional information (Adjuct Data) of the corresponding content.
  • the additional information may include various information.
  • the app-based enhancement component or the app component may correspond to this.
  • a plurality of FileContentITem elements may exist and may be omitted.
  • the FileContentITem element may include @FileContentItemLocation, @FileContentItemName, @FileContentItemID, @FileContentItemType, and / or @FileContentItemEncoding attributes.
  • the @FileContentItemLocation attribute may include URL information for accessing the file content item.
  • the CD-side app can obtain the corresponding file content item through this URL.
  • the @FileContentItemName attribute may indicate a human readable name of the corresponding file content item (Human Readable Name).
  • the @FileContentItemID attribute may indicate an identifier of a corresponding file content item.
  • the @FileContentItemType attribute may indicate the type of the corresponding file content item.
  • the @FileContentItemEncoding attribute may indicate an encoding method of a corresponding file content item.
  • the TimelineInfo element may include timeline related information of the corresponding content.
  • the timeline information may be delivered by HTTP GET or by a separate web socket service, but may be included in a service / content identification message.
  • the TimelineInfo element may further include a currentTime element.
  • the currentTime element may indicate current time information of the corresponding content.
  • the Location element may include URL information that can access the content.
  • the CD-side app can obtain the corresponding content through this URL.
  • this element may be URL information that can access the entire content.
  • a query term when sending a request for acquisition using the URL information of this element, a query term may be additionally added to acquire only necessary components or file content items.
  • the service / content identification message may additionally include a Show element and a Segment element. For each Show element and Segment element, an element / attribute included in the above-described Service element and Content element may be defined.
  • the service / content identification message may further include information indicating information on which part of the current PD, Service, Show, Segment, and Content based on Service, Show, Segment, and Content.
  • the service / content identification message may further include a logo or other ESG information, features (size, codec, bit rate, aspect ratio, required / desired capability) for each service, content, and the like.
  • the service / content identification message may further include filtering Criteria information for determining whether each service, content, and the like meets specific personalization criteria.
  • the above-mentioned URLs of location information may be a URL of a PD (or PD's server) for acquiring corresponding information in the PD, a URL of the Internet for acquiring directly from the Internet, or any remote. It can also be the URL of a server.
  • the service / content identification message may further include information indicating whether subscription or one-off may be performed to receive each service, content, and the like.
  • the CD-side app can send an HTTP GET message to the PD's HTTP-based web server.
  • This HTTP GET message may be requested as service URL information of the companion service.
  • the HTTP GET message may include corresponding service URL information and corresponding companion service (companion service for obtaining current service / content related information).
  • An HTTP GET message may have a further query term, which shows what information is requested.
  • the CD-side app can request information about the service / content currently provided by the PD.
  • Information about service content that may be requested includes the current show's ESG information, currently available component information, currently available file or non-real-time data and / or current timeline location. Information).
  • the PD to PD's web server can forward the requested information to the CD-side app via an HTTP response message.
  • This may include the requested information, and may not include the information if there is no requested information.
  • the HTTP response message may further include information indicating whether corresponding information is included.
  • the information requested and delivered here may correspond to the information of the aforementioned service / content identification message.
  • the ESG information may correspond to the above-described Service element and its sub-elements, the above-described Content element and its sub-elements, such as id, Name, Descrption, and CAratings elements.
  • the component information may correspond to the above-described Component element and its sub-elements.
  • the file or non-real-time data information may correspond to the aforementioned FileContentItem element and its subelements.
  • the timeline position information may correspond to the above-described TimelineInfo element and its subelements.
  • 55 is a diagram illustrating a current service information message format according to an embodiment of the present invention.
  • the request for current service information may be performed according to HTTP.
  • the CD may send an HTTP GET request to the PD to request information related to the current service.
  • the current service may mean a service or content currently provided by the PD.
  • the request URL may be ⁇ PD Host URL> / atsc3.csservices.esg.1? ⁇ Query>.
  • the PD Host URL is a web server endpoint URL, and atsc3.csservices.esg.1 may be a name of a service for delivering current service information.
  • the ⁇ Query> parameter contains a variety of values that allow you to specify an HTTP request.
  • Parameters included in ⁇ Query> may include a ServiceInfoType parameter.
  • the ServiceInfoType parameter is a 32-bit field and may indicate the type of the requested current service information.
  • the current service information may include the ESG information of the current show, the available components of the current show, the position on the current timeline within the current show, the file of the current show or the non-real time (NRT) content, etc. Can be.
  • NRT non-real time
  • the show may mean a content, a program, or a scene on a broadcast service or a broadcast service.
  • ServiceInfoType [n] When ServiceInfoType [n] is referred to as the nth bit of the ServiceInfoType parameter, the value of each bit can be interpreted as follows. If ServiceInfoType [0] is 1, this may indicate that the ESG information of the current show is requested. If ServiceInfoType [1] is 1, this may indicate that it is requesting an available component of the current show. If ServiceInfoType [2] is 1, this may indicate that the current file is requesting available files or NRT content. If ServiceInfoType [3] is 1, this may indicate that the current timeline location of the current show is requested. For each bit, a bit value of zero may indicate that the corresponding information is not requested. ServiceInfoType [4]-ServiceInfoType [31] may be reserved for future use.
  • the PD may transmit the requested type of information to the CD.
  • the PD may include the requested type of information in the HTTP response message.
  • the PD may not include information not requested from the CD in the response message.
  • the response message format for the current service information is shown.
  • the body portion of the HTTP response may be in JSON format and may conform to a JSON schema.
  • the HTTP response may include a ServiceName element and / or a MessageBody element.
  • the ServiceName element may indicate the name of the PD-CD service. In this case, since the current service information delivery service, this element may have a value of atsc3.csservices.esg.1.
  • the MessageBody element may include a response message body for the current service information request.
  • the MessageBody element may include a ServiceInfoRespType element, an ESGInfo element, a Components element, a FileContentITem element, and / or a TimelineInfo element.
  • the ServiceInfoRespType element is a 32-bit field and may indicate the type of current service information returned as a response.
  • the type of ESG information or the like may be indicated.
  • ServiceInfoRespType [n] is the nth bit of the ServiceInfoRespType element, the value of each bit can be interpreted as follows.
  • ServiceInfoRespType [0] this may indicate that ESG information of the current show is included in this response message. If ServiceInfoRespType [1] is 1, this may indicate that information related to the available components of the current show is included in this response message. If ServiceInfoRespType [2] is 1, this may indicate that information about available files or NRT content of the current show is included in this response message. If ServiceInfoRespType [3] is 1, this may indicate that information about the current timeline location of the current show is included in this response message. For each bit, a bit value of zero may indicate that the corresponding information is not included in this response message. ServiceInfoRespType [4]-ServiceInfoRespType [31] may be reserved for future use.
  • the ESGInfo element may be the same as the Service element and its subelements of the above-described service / content identification message and the id, Name, Description, and CARatings subelements of the Content element.
  • This element may be an element containing the requested ESG information.
  • the Components element may be the same as the Components element of the service / content identification message described above and its subelements. This element may be an element that contains the requested component related information.
  • the FileContentITem element may be the same as the FileContentItem element of the service / content identification message described above and its subelements. This element may be an element including the requested file or NRT content information.
  • the TimelineInfo element may be the same as the TimelineInfo element of the above-described service / content identification message and its subelements. This element may be an element that contains the requested timeline related information.
  • the request for ESG information may be performed according to HTTP.
  • the CD may request full ESG or partial ESG information by sending an HTTP GET request to the PD.
  • the request URL may be something like ⁇ PD Host URL> / atsc3.csservices.esg.2? ⁇ Query>.
  • the PD Host URL is a web server endpoint URL, and atsc3.csservices.esg.2 may be a name of a service for delivering ESG information.
  • the ⁇ Query> parameter contains a variety of values that allow you to specify an HTTP request.
  • Parameters included in ⁇ Query> may include an ESGRequesttype parameter.
  • ESG information about the current show may be a concept including Service, Schedule, Content fragments of the ESG for the current show.
  • the show may mean broadcast content or a program.
  • the ESGRequesttype parameter value is 1, it may mean that only ESG information for the current service is requested.
  • the ESG information on the current service may be a concept including Service, Schedule, and Content fragments of the ESG for the current virtual channel.
  • all ESG information may be a concept including Service, Schedule, and Content fragments of ESG of all virtual channels through which ESG can be transmitted.
  • the PD When receiving a request for ESG information from the CD, the PD may deliver the ESG information of the type to the CD.
  • the PD may include the requested type of ESG information in the HTTP response message.
  • the response message format for ESG information is shown.
  • the HTTP response may include an ESGResponseType element, a PDService element, a PDSchedule element, and / or a PDContent element.
  • the ESGResponseType element may indicate the type of requested information returned as a response. If the element value is 0, this may indicate that only ESG information about the current show is included in the response message. When the element value is 1, it may indicate that only ESG information about the current service is included in the response message. If the element value is 2, this may indicate that ESG information for all services is included in the response message. Each may be information corresponding to the aforementioned ESGRequesttype parameter.
  • the PDService element may be a container for a service fragment of the ESG information and its subelements with respect to the ESG type indicated by the ESGResponseType element. It can contain a Service element of ESG information.
  • the PDSchedule element may be a container for the Schedule fragment of the ESG information and its subelements, for the ESG type indicated by the ESGResponseType element. Can contain Schedule element of ESG information.
  • the PDContent element may be a container for a Content fragment of the ESG information and its subelements with respect to the ESG type indicated by the ESGResponseType element. Can contain Content element of ESG information.
  • the request of service / show / segment data may be performed according to HTTP.
  • service components such as broadcast service or content, information such as file content item, and the like may be delivered to the CD.
  • Continuous or presentable components may be accessed via the URL of the ComponentLocation element of the service / content identification message described above.
  • the CD app can obtain the corresponding component or component related information by performing an HTTP GET request with this URL.
  • Adjunct data ie files or data components
  • the CD app can make an HTTP GET request with this URL to obtain the file, data, etc.
  • this request may be performed through a URL indicated by the Location element of the above-described service / content identification message.
  • the request for media timeline information may be performed via HTTP and / or websocket.
  • the response message of HTTP or the notification message of the websocket may include absoluteTime information and / or mediaTime information.
  • the absoluteTime information may mean current UTC time information, and the mediaTime information may indicate media time at current UTC time.
  • FIG. 57 illustrates a media playback state message format according to an embodiment of the present invention.
  • the media playback state related information can be delivered to the CD side via a websocket connection.
  • the illustrated message body format may be included in the message body portion of the notification message format of the websocket and transmitted from the PD to the CD.
  • the media playback state related information may include an MPState element, an MPSpeed element, and / or a MediaID element.
  • the MPState element may indicate the current media playback state of the media.
  • the media may be media identified by a MediaID element to be described later or media currently provided by the PD.
  • the value of this element may be one of "PLAYING", “PAUSED”, “STOPPED”, “BUFFERING” and "UNKNOWN”.
  • the "STOPPED” state may mean the end of the media stream.
  • the MPSpeed element may indicate the current playback speed of the media in comparison to the normal speed. If the value of this element is positive, this may indicate that it is playing in the forward direction. Forward playback may mean that the media timeline position increases as the wall-clock time increases. If the value of this element is negative, this may indicate that it is playing in the reverse direction. Reverse playback may mean that the media timeline position decreases as the wall-clock time decreases.
  • this element When the value of this element is 1, it may mean that the media is played at normal speed in the forward direction. When played forward at normal speed, the media timeline may increase by the same amount as the wall clock time increases. If the value of this element is -1, it may mean that the media is played in normal speed in the reverse direction. When played in reverse at normal speed, the media timeline may be reduced by the same amount as the wall clock time is reduced.
  • this element is X and X is not 0 or 1, it may mean that the media is played at the speed of X times normal speed.
  • the media timeline may increase X times more than the wall clock time (if X is positive) or decrease X times more (if X is negative).
  • this element is 0 and the current MPState is "PLAYING", this may mean UNKNOWN playback speed. If MPState is any state other than "PLAYING", the value of this element may be zero.
  • this element may be inferred to be having a value of 1.
  • MPState is any state other than "PLAYING", and this element does not exist, this element may be inferred to be inferred. This element may need to be included in the response message if the PD supports the PVR function.
  • the MediaID element is an identifier of the media and may identify a target media for which media playback state information is requested. This identifier may uniquely identify the media in the PD for which media playback state information was requested. If this element has a value of "CURRENT", this may mean that information on the main media currently being played in the PD is requested.
  • one or more sets of ⁇ MPState, MPSpeed, MediaID ⁇ may be included in the MessageBody.
  • FIG. 58 is a diagram illustrating an EA message according to an embodiment of the present invention.
  • the EAM (EA Message) may be received by the PD and rendered by the control function of the PD.
  • the EAM may be received through a broadcast network or broadband.
  • the received EAM can be delivered via the local area network to the CD. This delivery process may include the PD app of the PD launching the CD app on the CD and delivering the EAM to this CD app (s) for rendering.
  • the EAM can be delivered by websocket and / or multicast when delivered to a CD.
  • the PD may include a PD App, CD Manager, WebSocket Server, and / or Multicast Sender.
  • the PD app can serve to deliver the EAM to available CD (s) in the local area network.
  • the CD manager is the same as the CD manager described above, and may play a role of discovering a CD on which the launcher is running and delivering execution information to the launcher to execute an EA CD app.
  • the websocket server is the same as the above-described websocket server, and can handle websocket communication (connection) between the PD app and the executed EA CD app.
  • the multicast sender may play a role of transmitting a multicast message from the PD app within the PD.
  • the CD may include a launcher and / or an EA CD app.
  • the launcher is as described above, and may play a role of communicating with the CD manager of the PD and executing the EA CD app of the CD.
  • the EA CD app may be a CD app that serves to receive the EAM from the PD and display it to the user.
  • the PD may receive an EAM while executing an internal control function.
  • an internal control function can launch an embedded PD app.
  • the PD app can render this EA and manage the process by which CD (s) in the local network render the EA.
  • the PD apps can find all the CDs the launcher is available to via the discoverCSLauncher () method. This may be to run the CD app to receive and render the EAM. If no CD with the launcher is found, the PD app can terminate itself. If a CD with the launcher is found, the PD app can find the local endpoint of the PD WebSocket Communication Service through the getApp2AppLocalBaseURL () method. In addition, the PD app can find the remote endpoint of the PD WebSocket communication service through the getApp2AppRemoteBaseURL () method.
  • endpoints of the websocket communication service may refer to endpoints of the websocket server.
  • the PD app can launch the EA CD app via the launchCSApp () method.
  • the EA CD app to be run can be identified via LaunchURL.
  • the remote endpoint of the websocket communication service may also need to be identified.
  • Each launched EA CD app can access the URL of the remote endpoint of the PD WebSocket Communication Service.
  • the EA CD app to be run can be identified and launched via LaunchURL.
  • the remote endpoint information may be delivered to the CD side.
  • the PD app can be attached to the local endpoint of the websocket communication service, and the EA CD app can be connected to the remote endpoint. This allows a websocket connection to be established between the PD app and the EA CD app. If the connection is established, the PD app can deliver the received EAM to the EA CD app. EA CD apps can handle and render this.
  • This section describes the process of delivering EAM from the PD app to the EA CD app using multicast.
  • the PD apps can find all the CDs the launcher is available to via the discoverCSLauncher () method. For each found CD, the PD app can launch the EA CD app via the launchCSApp () method. In this process, the EA CD app related information and / or multicast information identified by LaunchURL may be delivered to the CD side.
  • the multicast information may include multicast group address and / or multicast port information. Depending on the context, multicast group address and multicast port information may be combined and called as a multicast group address. Each launched EA CD app can access the multicast group address.
  • the launched EA CD app can check whether it has multicast group information for the EA. If the EA CD app does not have such information, the EA CD app can send a request to the PD's known endpoint. The PD may send the aforementioned multicast information in response. If the EA CD app has multicast information, the EA CD app can join a multicast group for the EA. Multicast group addresses can be used in this process.
  • the PD app can send the EAM to the multicast group address using the multicast sender. This allows EAM to be delivered to the EA CD app.
  • the EA CD app can receive the EAM, process it, and render it.
  • the PD app can terminate all EA CD apps by sending a termination request to the multicast group address. The PD app can then shut itself down.
  • One embodiment of an EAM is shown.
  • the EAM may be delivered to the CD side.
  • the subscription ID, the initial content of the EAM, the characteristic information of the EAM initial content, and additional content may be delivered to the CD side with the EAM.
  • the characteristics of the EAM initial content may mean whether the EAM is a new message, a continuous message, and / or a one-time message.
  • the EAM initial content may also include whether rich media is included in addition to the text.
  • a plurality of EAMs may be delivered to the CD at one time, depending on the embodiment. That is, the EAMNotification element may include a plurality of EAM elements.
  • EAM elements include the EAMID attribute, the SentTimestamp attribute, the ExpiredTimestamp attribute, the Category attribute, the Urgency attribute, the Severity attribute, the Geo-loc attribute, the NewMsg attribute, the OneTimeMsg attribute, the EAMContent element, the AddlEAMURL element, the EAMContentAccessibilityURL element, the AddlEAMPhone element, or the ContactEmail element. It may include an element.
  • the EAMID attribute may indicate an identifier of the corresponding EA message (EAM). This identifier can uniquely identify the EA message.
  • the SentTimestamp attribute may indicate the date and / or time when the corresponding EA message was generated.
  • the SentTimestamp attribute may indicate the first moment when the EA message becomes valid.
  • the ExpiredTimestamp attribute may indicate the last moment (date and / or time) at which the corresponding EA message becomes valid.
  • the Category attribute may indicate a category of the corresponding EA message.
  • the Category attribute may indicate at least one of Geo, Met, Safety, Rescue, Fire, Health, Env, Transport, Infra, and / or CBRNE.
  • Urgency attribute may indicate the urgency of the EA message.
  • the Urgency attribute may indicate at least one of Immediate, Expected, Future, and / or Past.
  • the Severity attribute may indicate the severity of the corresponding EA message.
  • the Severity attribute may indicate at least one of Extreme, Severe, Moderate, and / or Minor.
  • the geo-loc attribute may indicate a geographical location to which the corresponding EA message is applicable.
  • the NewMsg attribute may indicate whether the corresponding EA message is a new message. If the value of the NewMsg attribute is "true”, this EA message may be a new message. If the value of the NewMsg attribute is "false”, this EA message may be a repetition of a previous EA message.
  • the OneTimeMsg attribute may indicate whether the corresponding EA message is transmitted only once. If the value of the OneTimeMsg attribute is "true”, this EA message may only be sent once and may not be repeated. If the value of the OneTimeMsg attribute is "false", this EA message can be repeated at least once.
  • the EAMContent element may include the message content of the corresponding EA message.
  • the EAMContent element may further include a ContentFormat attribute.
  • the ContentFormat property may indicate the type of content of the corresponding EA message included in the EAMContent element.
  • the AddlEAMURL element may indicate a URL that provides additional information about the corresponding EA message. This URL can provide more information than the information contained in the EAMContent element. Through this, additional content for an emergency alert may be obtained.
  • the EAMContentAccessibilityURL element may indicate a URL for providing initial emergency alert message content for accessibility. This may be a URL for obtaining information for quick alerts, in addition to the main content for the EA. According to an embodiment, the element may indicate an URL for providing a secondary audio stream for facilitating provision of information according to EA and EA. This may be done according to the manner required by the FCC rules.
  • the AddlEAMPhone element may indicate a telephone number for obtaining more information about the corresponding EA message.
  • the ContactEmail element may indicate an email address that provides more information about the EA message.
  • the EAMNotification element may further include a SubscriptionID element, a PDDevID element, and / or a PDVersion element.
  • the SubscriptionID element may indicate a subscription identifier for a corresponding EA message subscription.
  • the SubscriptionID element may be used to uniquely identify the subscription from the CD to the PD.
  • the PDDevID element may be a device identifier of the PD.
  • the PDVersion element may indicate version information of the PD.
  • the EAM can be in XML format or JSON format.
  • the EAM may be changed to an XML format, and the changed XML schema may be defined according to standard XML conventions according to the above-described elements / properties.
  • the PD app and the CD app may operate simultaneously in tandem.
  • communication between the PD app and the CD app may be performed, and a protocol such as a web socket may be utilized.
  • the discovery process may be used as well as the above-described method, such as DIAL, SSDP, UPnP.
  • FIG. 59 is a diagram illustrating a subscription related message and a notification message of a web socket protocol according to an embodiment of the present invention in a JSNO schema.
  • a subscription related message from PD to CD or CD to PD is shown (t59010).
  • the illustrated format may be expressed in a JSON format or an XML format according to an embodiment.
  • a notification message from the PD to the CD is shown (t59020).
  • the illustrated format may be expressed in a JSON format or an XML format according to an embodiment.
  • 60 is a diagram illustrating a method of processing a broadcast service in a PD according to an embodiment of the present invention.
  • a method of processing a broadcast service in a PD includes receiving an EA message through a broadcasting network or broadband, executing a PD application, rendering a received EA message, and CD. Finding, executing the first CD app, and / or transmitting the received EA message to the multicast group address to deliver to the first CD app.
  • the receiving component of the PD may receive the EA message through a broadcast network or broadband.
  • the reception component is a hardware element and may include a tuner for receiving a broadcast stream and / or a network interface for receiving a broadband.
  • the PD may be executing an internal control device.
  • PD may be a broadcast receiver.
  • the PD's internal control device can run the PD app.
  • the internal control device may be a hardware element as the internal control function described above.
  • the PD app may correspond to the aforementioned PD app.
  • the executed PD app can render the received EA message and show it to the user watching the PD. This can effectively provide an Emergency Alert (EA) to the user. This step may be omitted depending on the embodiment.
  • EA Emergency Alert
  • the companion manager can find, by the PD app, a CD that has a launcher for running the CD app. This process has been described above.
  • CD apps There may be various types of CD apps, but the first CD app of the CD apps may be an app for receiving an EA message from the corresponding CD and rendering it.
  • the companion manager may correspond to the above-described CD manager and may be a hardware element.
  • the companion manager may execute the first CD app by the PD app.
  • the process of executing the CD app in the PD has been described above.
  • the step of executing the first CD app may further include transmitting the multicast information including the multicast group address to the first CD app. That is, this process may correspond to an embodiment of delivering an EAM to a CD through a multicast scheme.
  • the multicast information may include the aforementioned multicast group address.
  • the multicast group address may also include multicast port information.
  • the first CD app may join the multicast group for the EA using the same.
  • the multicast sender may then transmit, by the PD app, the received EA message to the multicast group address so that the EAM can be delivered to the first CD app.
  • the multicast sender may be a hardware element of the PD.
  • the PD app may find a local endpoint and / or a remote endpoint of the PD's websocket server.
  • the websocket server may be a hardware element in the aforementioned PD.
  • the companion manager may find a CD having a launcher for executing the CD app by the PD app.
  • the second CD app may be an app for receiving and rendering an EA message.
  • the second CD app and the first CD app may be the same or different.
  • the first CD app and the second CD app may correspond to the aforementioned EA CD app.
  • the companion manager may execute the second CD app by the PD app.
  • the URL of the websocket server endpoint can be delivered to the second CD app. This may correspond to the embodiment for delivering the above-described EAM to the CD app through the websocket protocol.
  • the PD app can be attached to the local endpoint, and the second CD app can be connected to the remote endpoint so that a websocket connection between the PD app and the second CD app can be established.
  • the websocket server can manage this websocket connection.
  • the websocket server may transmit, by the PD app, the received EAM to the second CD app via the websocket connection.
  • the above-described EA message includes ID information identifying the corresponding EA message, transmission time information indicating the time at which the corresponding EA message was generated, and the corresponding EA message. It may include expiration time information indicating the expiration time, category information indicating the type of emergency alert indicated by the corresponding EA message, and / or emergency alert content information for the corresponding emergency alert.
  • ID information identifying the corresponding EA message
  • transmission time information indicating the time at which the corresponding EA message was generated
  • the corresponding EA message It may include expiration time information indicating the expiration time, category information indicating the type of emergency alert indicated by the corresponding EA message, and / or emergency alert content information for the corresponding emergency alert.
  • the above-described EA message includes new message information indicating whether the corresponding EA message is a new EA message or a repetition of a previous EA message, and the EA message is only once. It may further include one-time message information indicating whether the EA message is transmitted and / or URL information providing initial emergency alert content for the corresponding emergency alert.
  • new message information indicating whether the corresponding EA message is a new EA message or a repetition of a previous EA message
  • the EA message is only once. It may further include one-time message information indicating whether the EA message is transmitted and / or URL information providing initial emergency alert content for the corresponding emergency alert.
  • the PD may further include a web server having a web server endpoint.
  • the web server may be a hardware element in the aforementioned PD.
  • the companion manager may perform a discovery process with a third CD app among CD apps running on the CD. This discovery process has been described above. During discovery, the URL of the PD's web server endpoint may be delivered to the third CD app.
  • the third CD app may be a general CD app, not an EA CD app. Of course, in some embodiments, the role of the first, second, and third CD apps may be performed in one CD app.
  • the web server may receive an HTTP GET message from a third CD app via a web server endpoint.
  • This HTTP GET message may be a message for requesting information on the current broadcast content currently provided by the PD.
  • the HTTP GET message may request at least one of ESG information of the current broadcast content, content component related information of the current broadcast content, file or NRT content related information of the current broadcast content, and / or timeline related information of the current broadcast content.
  • the web server may transmit an HTTP response message including information on the requested current broadcast content to the third CD app.
  • This embodiment may correspond to the above-described current service information delivery request and response through HTTP.
  • the web server may receive an HTTP GET message requesting ESG information from the third CD app through the web server endpoint.
  • This HTTP GET message contains partial ESG information for broadcast content currently being provided by the PD, partial ESG information for the broadcast service currently being provided by the PD and / or full ESG for the available broadcast services. You can request at least one of the information. This has been described above.
  • the web server may send an HTTP response message including the requested ESG information to the third CD app. This embodiment may correspond to the above-described ESG information delivery request and response through HTTP.
  • a method of processing a broadcast service in a CD includes: receiving a launch message from a CD launcher by a PD, launching a corresponding CD app using the launch message of the CD;
  • the CD app may be an EA CD app for receiving and rendering an EA message, and the CD's internal control unit joins the multicast group for the EA using the multicast information received from the PD in the execution phase of the EA CD app. And / or receiving an EAM from the PD side via a multicast group address.
  • Methods of processing a broadcast service in a CD may correspond to the methods of processing a broadcast service in a PD according to the embodiments of the present invention described above.
  • Methods of processing broadcast services in a CD include modules used in the method of processing broadcast services in a PD (eg, companion manager, web socket server, web server, multicast sender, internal controller, receiving component, etc.). It may be performed by hardware modules corresponding to the.
  • the method of processing a broadcast service in a CD may have embodiments corresponding to embodiments of the method of processing a broadcast service in the aforementioned PD.
  • 61 is a diagram illustrating a broadcast service processing apparatus operating as a PD according to an embodiment of the present invention.
  • the broadcast service processing apparatus operating as a PD may include the aforementioned companion manager, web socket server, web server, multicast sender, internal controller, and / or receiving component.
  • Each element, block, and module is as described above.
  • the broadcast service processing apparatus and its internal modules / blocks operating as a PD may perform the above-described embodiments of the method for processing a broadcast service in the PD of the present invention.
  • a broadcast service processing apparatus operating as a CD according to an embodiment of the present invention will be described. This device is not shown in the figure.
  • the broadcast service processing apparatus operating as a CD may include the above-described launcher, an internal control apparatus, a memory, a receiving component, and the like. Each element, block, and module is as described above.
  • the broadcast service processing apparatus and its internal modules / blocks operating as a CD may perform the above-described embodiments of the method for processing a broadcast service in a CD of the present invention.
  • the above-described blocks / modules in the device may be processors for executing consecutive processes stored in a memory, and according to embodiments, may be hardware elements located in / outside the device.
  • the above-described modules may be omitted or replaced by other modules performing similar / same operations according to the embodiment.
  • the module or unit may be processors that execute successive procedures stored in a memory (or storage unit). Each of the steps described in the above embodiments may be performed by hardware / processors. Each module / block / unit described in the above embodiments can operate as a hardware / processor.
  • the methods proposed by the present invention can be executed as code. This code can be written to a processor readable storage medium and thus read by a processor provided by an apparatus.
  • Apparatus and method according to the present invention is not limited to the configuration and method of the embodiments described as described above, the above-described embodiments may be selectively all or part of each embodiment so that various modifications can be made It may be configured in combination.
  • the processor-readable recording medium includes all kinds of recording devices that store data that can be read by the processor.
  • Examples of the processor-readable recording medium include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like, and may also be implemented in the form of a carrier wave such as transmission over the Internet.
  • the processor-readable recording medium can also be distributed over network coupled computer systems so that the processor-readable code is stored and executed in a distributed fashion.
  • the present invention is used in the field of providing a series of broadcast signals.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

La présente invention concerne un procédé d'émission d'un signal de radiodiffusion. Le procédé d'émission d'un signal de radiodiffusion selon la présente invention concerne un système qui peut prendre en charge un service de radiodiffusion de nouvelle génération dans un environnement prenant en charge une radiodiffusion hybride de nouvelle génération au moyen d'un réseau de radiodiffusion terrestre et d'un réseau Internet. Par ailleurs, la présente invention concerne un système de signalisation efficace qui couvre à la fois le réseau de radiodiffusion terrestre et le réseau Internet dans l'environnement prenant en charge la radiodiffusion hybride de nouvelle génération.
PCT/KR2016/007375 2015-07-08 2016-07-07 Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion Ceased WO2017007260A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201562189756P 2015-07-08 2015-07-08
US62/189,756 2015-07-08
US201562211851P 2015-08-30 2015-08-30
US62/211,851 2015-08-30

Publications (1)

Publication Number Publication Date
WO2017007260A1 true WO2017007260A1 (fr) 2017-01-12

Family

ID=57685857

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2016/007375 Ceased WO2017007260A1 (fr) 2015-07-08 2016-07-07 Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion

Country Status (1)

Country Link
WO (1) WO2017007260A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018155798A1 (fr) * 2017-02-22 2018-08-30 엘지전자 주식회사 Procédé et dispositif de transmission et de réception de signal multidiffusion

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014119961A1 (fr) * 2013-02-03 2014-08-07 엘지전자 주식회사 Appareil pour fournir un service d'alarme urgente par le biais d'un système de diffusion et procédé associé
WO2014148813A1 (fr) * 2013-03-19 2014-09-25 엘지전자 주식회사 Appareil d'émission de signal, procédé d'émission de signal et système d'émission et de réception de signal
WO2015041494A1 (fr) * 2013-09-23 2015-03-26 삼성전자 주식회사 Procédé et dispositif pour l'exécution d'une application dans un système de communication sans fil
WO2015072763A1 (fr) * 2013-11-13 2015-05-21 엘지전자(주) Procédé et appareil pour gérer une connexion entre un dispositif de réception de diffusion et un autre dispositif connecté par réseau
US20150189486A1 (en) * 2014-01-02 2015-07-02 Lg Electronics Inc. Broadcast receiving device and operating method thereof

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014119961A1 (fr) * 2013-02-03 2014-08-07 엘지전자 주식회사 Appareil pour fournir un service d'alarme urgente par le biais d'un système de diffusion et procédé associé
WO2014148813A1 (fr) * 2013-03-19 2014-09-25 엘지전자 주식회사 Appareil d'émission de signal, procédé d'émission de signal et système d'émission et de réception de signal
WO2015041494A1 (fr) * 2013-09-23 2015-03-26 삼성전자 주식회사 Procédé et dispositif pour l'exécution d'une application dans un système de communication sans fil
WO2015072763A1 (fr) * 2013-11-13 2015-05-21 엘지전자(주) Procédé et appareil pour gérer une connexion entre un dispositif de réception de diffusion et un autre dispositif connecté par réseau
US20150189486A1 (en) * 2014-01-02 2015-07-02 Lg Electronics Inc. Broadcast receiving device and operating method thereof

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018155798A1 (fr) * 2017-02-22 2018-08-30 엘지전자 주식회사 Procédé et dispositif de transmission et de réception de signal multidiffusion

Similar Documents

Publication Publication Date Title
WO2016140478A1 (fr) Dispositif d'émission et de réception de signal de diffusion, et procédé d'émission et de réception de signal de diffusion
WO2016114559A1 (fr) Dispositif de transmission de signal de diffusion, dispositif de réception de signal de diffusion, procédé de transmission de signal de diffusion et procédé de réception de signal de diffusion
WO2016140479A1 (fr) Dispositif d'émission et de réception de signal de radiodiffusion, et procédé d'émission et de réception de signal de radiodiffusion
WO2016140483A1 (fr) Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2016153326A1 (fr) Dispositif d'émission de signal de diffusion, dispositif de réception de signal de diffusion, procédé d'émission de signal de diffusion et procédé de réception de signal de diffusion
WO2017007224A1 (fr) Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2016140477A1 (fr) Appareil de transmission de signaux de diffusion, appareil de réception de signaux de diffusion, procédé de transmission de signaux de diffusion, procédé de réception de signaux de diffusion
WO2017014586A1 (fr) Dispositif et procédé d'émission et de réception de signal de radiodiffusion
WO2017204546A1 (fr) Dispositif et procédé d'émission/réception de signaux de diffusion
WO2016111526A1 (fr) Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2016186407A1 (fr) Appareil et procédé d'émission ou de réception de signal de diffusion
WO2016163772A2 (fr) Appareil d'émission de signal de diffusion, appareil de réception de signal de diffusion, procédé d'émission de signal de diffusion, et procédé de réception de signal de diffusion
WO2017061792A1 (fr) Dispositif et procédé d'émission/réception de signal de diffusion
WO2016068564A1 (fr) Appareil et procédé d'émission de signal de diffusion, appareil et procédé de réception de signal de diffusion
WO2016036077A1 (fr) Appareil de réception de diffusion générale, procédé d'exploitation d'un appareil de réception de diffusion générale, appareil imbriqué s'imbriquant avec un appareil de réception de diffusion générale, et procédé d'exploitation d'un appareil imbriqué
WO2016153241A1 (fr) Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion et procédé de réception de signal de radiodiffusion
WO2017209514A1 (fr) Dispositif et procédé d'émission et de réception de signal de diffusion
WO2016028052A2 (fr) Appareil de transmission de signal de diffusion, appareil de réception de signal de diffusion, procédé de transmission de signal de diffusion, et procédé de réception de signal de diffusion
WO2016190662A1 (fr) Dispositif de transmission de signal de diffusion, dispositif de réception de signal de diffusion, procédé de transmission de signal de diffusion, et procédé de réception de signal de diffusion
WO2016122269A1 (fr) Dispositif de transmission de signaux de radiodiffusion, dispositif de réception de signaux de radiodiffusion, procédé de transmission de signaux de radiodiffusion et procédé de réception de signaux de radiodiffusion
WO2016178549A1 (fr) Dispositif d'émission de signaux de diffusion, dispositif de réception de signaux de diffusion, procédé d'émission de signaux de diffusion, et procédé de réception de signaux de diffusion
WO2018101566A1 (fr) Dispositif et procédé d'émission/réception de signal de radiodiffusion
WO2017014553A1 (fr) Appareil d'émission de signal de diffusion, appareil de réception de signal de diffusion, procédé d'émission de signal de diffusion et procédé de réception de signal de diffusion
WO2016190720A1 (fr) Dispositif d'émission et de réception de signal de radiodiffusion, et procédé d'émission et de réception de signal de radiodiffusion
WO2016171528A1 (fr) Appareil de transmission d'un signal de radiodiffusion, appareil de réception d'un signal de radiodiffusion, procédé de transmission d'un signal de radiodiffusion, et procédé de réception d'un signal de radiodiffusion

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16821666

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16821666

Country of ref document: EP

Kind code of ref document: A1