JP7286039B2 - Terminals and programs - Google Patents

Description

The present invention relates to terminal devices and programs.

In the prior art, when a terminal device that cooperates with a broadcast receiver requests activation of a program running on the broadcast receiver, information specifying the resources of the broadcast received by the broadcast receiver and the program to be activated are specified. I checked the consistency of the information.

Section 7.2.3.2.3.3.1 “Activation request” of Non-Patent Document 1 describes activation of the Hybridcast application on the receiver. In the conventional technology, in Hybridcast, which is a broadcast-communication cooperation system, a Hybridcast application on a receiver can be activated from a terminal device, that is, from a smartphone application or the like. Specifically, from the terminal device to the receiver, by transmitting the information of the organization channel of the broadcast to be selected and the URL of the AIT of the Hybridcast application to be started, Hybridcast on the receiver is transmitted. Applications can be started. Note that AIT represents an application information table.

In addition, the receiver that has received the information of the broadcast organization channel and the URL of the AIT of the Hybridcast application to be activated from the terminal device sends the activation command received from the terminal device to the permission determination server device outside the receiver. Send. The propriety determination server device confirms the validity of the combination of the information on the program channel of the broadcast to be selected and the URL of the AIT of the Hybridcast application to be activated. The permission determination server device returns the determination result to the receiver. The receiver selects a channel and activates the Hybridcast application requested by the terminal device only when it receives a valid determination result from the propriety determination server device.

The information on the organization channel of the above broadcast is specified as a combination of an original network ID (original_network_id), a transport stream ID (transport_stream_id), and a service ID (service_id).

According to Non-Patent Document 1, the broadcasting services targeted by Hybridcast are terrestrial broadcasting, BS broadcasting (broadcasting by broadcasting satellite), and broadband CS digital broadcasting.
In Non-Patent Document 2, "Volume 7 Digital Terrestrial Television Broadcast Transmission Operation Regulations", regarding terrestrial broadcasting, the allocation of the above-mentioned original network ID, transport stream ID, and service ID is defined. . Note that these values are calculated based on the value of region identification assigned to each region such as prefectures and the value of local business operator identification. A value from "0" to "15" can be used for each region as the value of the regional operator identification.
In Non-Patent Document 3, "Part 1, Volume 7: BS Digital Broadcast Transmission Operational Regulations", for BS broadcasting, the allocation of the above-mentioned original network ID, transport stream ID, and service ID is defined. .
Non-Patent Document 3, "Part 2, Volume 7 Broadband CS Digital Broadcast Transmission Operation Regulations" defines the allocation of the above-mentioned original network ID, transport stream ID, and service ID for broadband CS digital broadcasting. It is

Note that the original network ID, transport stream ID, and service ID are assigned ID values to each organization channel throughout Japan without duplication. Therefore, the above-mentioned propriety determination server device manages the URL of the AIT of the Hybridcast application that is permitted to be activated by associating it with each program channel, thereby ensuring the independence of the broadcaster while ensuring the validity of the activation of the application. You can guarantee the sex.

On the other hand, in Non-Patent Document 4, "Section 2: Operational Specifications for Independent Broadcasting by Cable Television Operators in Digital Terrestrial Broadcasting Networks", independent broadcasting (so-called community channels) using digital terrestrial broadcasting networks for cable television is also subject to broadcasting. For each composition channel, the assignment of original network ID, transport stream ID and service ID values is defined.

"IPTV Regulations Hybridcast Operational Regulations IPTVFJ STD-0013 Version 2.7", revised on September 21, 2018, IPTV Forum "Digital Terrestrial Television Broadcasting Operation Regulations Technical Data ARIB TR-B14 Version 6.5", revised on January 21, 2019, Association of Radio Industries and Businesses "BS/Broadband CS Digital Broadcasting Operational Regulations Technical Data ARIB TR-B15 Version 7.7", Revised on October 11, 2018, Association of Radio Industries and Businesses "JLabs SPEC-006 Version 2.1 Terrestrial Digital Television Broadcasting Pass-Through and Independent Broadcasting Operational Specifications", March 31, 2014, Japan Cable Lab.

However, with regard to independent broadcasting using the terrestrial digital broadcasting network of cable television, the value of the local operator identification is limited to two, "13" and "15", for each region such as prefectures. As such, only a maximum of two cable television broadcaster programming channels can be identified in each region. Therefore, in areas where there are three or more cable television broadcasters, multiple cable television broadcasters must use the same combination of original network ID, transport stream ID, and service ID. becomes. That is, there may be situations where multiple cable television broadcasters use the same identification information. Therefore, when trying to operate a service using the external activation of the Hybridcast application, the above-mentioned propriety determination server device can manage and guarantee the validity of the activation of the application while ensuring the independence of the broadcaster. The problem arises that you can't. For example, if there are cable television broadcasters A and B that provide independent broadcasting services using the same combination of original network ID, transport stream ID, and service ID values, a viewer may, for example, cable If you bring a smartphone installed with an application that can start the Hybridcast application of TV broadcaster A, move to the broadcasting area of cable television broadcaster B, and execute the external activation of the application, the broadcast of broadcaster B will It is possible that the Hybridcast application of the operator A will be activated by the service. In other words, there arises a problem that consistency between the broadcasting service and the Hybridcast application is not ensured.

The present invention has been made based on the recognition of the above problems. To provide a terminal device and a program capable of assuring consistency between a broadcasting service and a Hybridcast application when the Hybridcast application is externally started.

[1] In order to solve the above problems, a terminal device according to one aspect of the present invention provides, from a receiver for receiving broadcasting, organized channel information including a organized service name, which is the name of a organized channel receivable by the receiver. a programming channel information acquiring unit that acquires the information, a storage unit that stores a specific programming service name in advance, and an activation requesting unit that has a function of requesting the receiver to activate a program associated with the specific programming service name. Then, it is determined whether or not the specific program service name stored in the storage unit is included in the program channel information acquired from the receiver by the program channel information acquisition unit, and based on the result of this determination, The terminal device includes a determination unit that controls whether or not the activation request unit requests activation of the program.

[2] Further, according to one aspect of the present invention, in the terminal device described above, when the specific organization service name is included in the organization channel information acquired from the receiver, the determination unit controlling the activation request unit to issue an activation request, and if the specific organized service name is not included in the organized channel information acquired from the receiver, the activation request is not made to initiate the program. It controls the part.

[3] Further, according to one aspect of the present invention, in the terminal device described above, the organized channel information acquisition unit acquires the organized channel information by calling an application program interface of "channels" of the Hybridcast compatible receiver. It is.

[4] Further, one aspect of the present invention is a program for causing a computer to function as the terminal device according to any one of [1] to [3] above.

According to the present invention, even when there are a plurality of broadcasters using the same combination of original network ID, transport stream ID, and service ID values, when the Hybridcast application is started externally, the broadcast service and hybridcast app.

In addition, in order to ensure such consistency, there is no need to change the operation of judging whether or not to allow activation in the existing Hybridcast application activation procedure. Therefore, it is possible to operate the system while ensuring the independence of broadcasters.

1 is a block diagram showing a schematic functional configuration of a terminal device according to an embodiment of the present invention; FIG. It is a block diagram which shows the structure of the system containing the terminal device and receiver by the same embodiment. FIG. 4 is a sequence diagram showing the procedure of exchange between the terminal device and the receiver in the same embodiment; 4 is a flow chart showing the procedure of processing for the terminal device according to the same embodiment to request activation of the Hybridcast application. 4 is a schematic diagram showing a configuration example of data (organization channel information) acquired from the receiver side by the organization channel information acquisition unit of the terminal device according to the same embodiment; FIG.

An embodiment of the present invention will now be described with reference to the drawings. In the present embodiment, the terminal device 1 acquires information about organized channels from the receiver 2 before requesting the receiver 2 to start the Hybridcast application. The information acquired by the terminal device 1 includes information on a list of organization service names (character strings) relating to all organization channels receivable by the receiver 2 . The terminal device 1 determines whether or not the name of the organization service name stored in advance is included in the list of organization service names acquired from the receiver 2 . The organizing service name pre-stored in the terminal device 1 is the organizing service name of the organizing channel associated with the Hybridcast application to be activated. If the target organization service name is included in the acquired list, the terminal device 1 directly requests the receiver 2 to activate the Hybridcast application. If the target organization service name is not included in the acquired list, the terminal device 1 does not request (cancel) the activation of the Hybridcast application. As a result, even if the specific information of the broadcast resource (original network identifier, transport stream identifier, service identifier) happens to match, it is possible to prevent the Hybridcast application that does not match from being activated.

Terms used in this embodiment will be explained here. "App" means an application program. An "app" may be simply called a "program". An application program that runs on the terminal device and performs processing for cooperating with the receiver is sometimes called a "companion application" or a "companion app." "Hybridcast" is the name of a method or system that links broadcasting and communication. "AIT" means an application information table used in Hybridcast. "PC" is an abbreviation for personal computer. "LAN" is an abbreviation for Local Area Network. "URL" is an abbreviation for Uniform Resource Locator. "HTTP" is an abbreviation for Hyper-text Transfer Protocol. "DBMS" means Database Management System. "JSON" (JavaScript Object Notation) is a notation of data (object) using text ("JavaScript" is a registered trademark).

FIG. 1 is a block diagram showing the functional configuration of a terminal device according to this embodiment. As illustrated, the terminal device 1 includes a communication section 11, an authentication section 12, a storage section 14, a program channel information acquisition section 15, a determination section 16, and an activation request section . Each of these functional units can be realized by, for example, a computer and a program. In addition, each functional unit has storage means as required. The storage means are, for example, program variables and memory allocated by program execution. Also, if necessary, non-volatile storage means such as a magnetic hard disk drive or a solid state drive (SSD) may be used. Also, at least part of the function of each functional unit may be realized as a dedicated electronic circuit instead of a program.

The terminal device 1 has a function of activating a Hybridcast application associated with a specific organization channel on a receiver (television receiver that receives television broadcasts) that cooperates with the terminal device 1 . The terminal device 1 realizes the function of activating the Hybridcast application on the receiver, for example, as an application function. This application runs in a program execution environment (processor, memory, etc.) on the terminal device 1 . The function of each part shown in FIG. 1 is as follows.

The communication unit 11 has a function of communicating with the outside. The communication unit 11 realizes communication by Internet Protocol (IP), for example. The communication unit 11 enables communication with external devices via the Internet using wired or wireless communication means. In addition, the communication unit 11 communicates with the receiver 2 using short-range communication means such as a wireless LAN, as will be described later, to enable cooperative operation. The communication unit 11 performs communication in response to requests from the authentication unit 12, the organized channel information acquisition unit 15, and the activation request unit 18, which are higher-level functions.

The authentication unit 12 performs authentication between the terminal device 1 and the receiver 2 through communication with the receiver 2 . The terminal device 1 and the receiver 2 are paired by the authentication unit 12 performing authentication with the discovered receiver 2 using communication means such as a wireless LAN.

The storage unit 14 stores data. The storage unit 14 particularly stores the organization service name of the organization channel associated with the Hybridcast application activated on the receiver. That is, the storage unit 14 stores a specific organization service name in advance. In the storage unit 14, the place where the above-mentioned organization service name is stored may be, for example, a semiconductor memory or a magnetic disk device. The location where the above organization service name is stored may be a memory space directly accessible from the program, a file on the file system, or stored by a database management system (DBMS) or the like. It may be in a managed database. The place where the above-mentioned organization service name is stored may be, for example, a data area allocated to a variable in the program, a constant area in the program, or in the program code itself. may be a predetermined area.

The organized channel information acquisition unit 15 acquires organized channel information including organized service names, which are the names of organized channels receivable by the receiver 2, from the receiver 2 that receives the broadcast. The organized channel information acquisition unit 15 acquires organized channel information from the receiver 2 through communication. The organized channel information acquisition unit 15 acquires the above organized channel information by calling a predetermined API (application program interface), which will be described later. The organized channel information is information about organized channels receivable by the receiver 2 . The organized channel information includes data of organized service names of organized channels that the receiver 2 can receive. A configuration example of the organized channel information acquired from the receiver 2 by the organized channel information acquisition unit 15 will be described later with reference to FIG.

The determination unit 16 determines whether or not the specific organization service name stored in the storage unit 14 is included in the organization channel information acquired from the receiver 2 by the organization channel information acquisition unit 15, and based on this determination result. , the activation request unit 18 controls whether or not to issue a program activation request. More specifically, the determination unit 16 controls the activation request unit 18 to request activation of the program when the specific organization service name is included in the organization channel information acquired from the receiver 2 . Further, the determination unit 16 controls the activation request unit 18 so as not to request activation of the program when the specific organization service name is not included in the organization channel information acquired from the receiver 2 .

In other words, the determination unit 16 determines whether or not the organization service name previously stored in the storage unit 14 is included in the organization channel information acquired from the receiver 2 . The determination unit 16 controls whether or not to request the receiver 2 to activate the Hybridcast application based on the determination result. When the organization service name stored in the storage unit 14 is included in the organization channel information acquired from the receiver 2, a Hybridcast activation request associated with the organization service name is executed. , the determination unit 16 controls. If the organization service name stored in the storage unit 14 is not included in the organization channel information acquired from the receiver 2, the Hybridcast activation request associated with the organization service name is not issued ( stop).

The activation request unit 18 has a function of requesting the receiver 2 to activate a program associated with a specific organization service name. Specifically, the activation request unit 18 requests the receiver 2 to activate a specific Hybridcast application. However, the activation request unit 18 may cancel the hybridcast application activation request to the receiver 2 depending on the determination result of the determination unit 16 described above. In other words, whether or not the activation request unit 18 executes the Hybridcast application activation request depends on the determination result of the determination unit 16 and the control based on the determination result.

FIG. 2 is a block diagram showing the configuration of the system according to this embodiment. As illustrated, the system 100 includes a terminal device 1 , a receiver 2 , a broadcast transmission device 3 , a permission determination server device 4 and a service server device 5 . In the system 100, the terminal device 1 and the receiver 2 can communicate with each other by short-range communication means such as wireless LAN. The terminal device 1 and the receiver 2 can operate cooperatively while communicating with each other.
The terminal device 1, the receiver 2, the availability determination server device 4, and the service server device 5 are each connected to a communication network such as the Internet 9 or the like. The terminal device 1, the receiver 2, the availability determination server device 4, and the service server device 5 can communicate with each other via this communication network. Also, the broadcast transmission device 3 transmits a broadcast signal. Broadcast signals can be transmitted through transmission media such as the air (space), metal cables, and optical cables. The receiver 2 can receive, demodulate, and decode a broadcast signal sent from the broadcast sending device 3 .

Of the devices shown in FIG. 2, the broadcast transmission device 3, the approval/denial determination server device 4, and the service server device 5 are devices operated by a broadcaster or the like. The terminal device 1 and the receiver 2 are devices held and used by general users (broadcast viewers, etc.).

The terminal device 1 communicates with the receiver 2 via communication means such as a wireless LAN. The terminal device 1 can cooperate with the receiver 2 . The terminal device 1 has an operating environment for running an application. The terminal device 1 can request the receiver 2 to activate a Hybridcast application running on the receiver 2, for example, by using the function of the application. The terminal device 1 can receive, from the service server device 5, the code of the application, the data (such as content) used by the application, and the like, as necessary. Note that the terminal device 1 is specifically implemented using, for example, a smartphone, a tablet terminal device, a wearable terminal device, a PC, or the like.

The receiver 2 is a device that receives television broadcasting. The receiver 2 receives the broadcast signal sent from the broadcast sending device 3, extracts content such as video and audio from the broadcast signal, and presents it to the user. The receiver 2 has a function corresponding to Hybridcast. That is, the receiver 2 has an application operating environment for operating the Hybridcast application. Also, the receiver 2 communicates with the availability determination server device 4 and the service server device 5 via the Internet 9 . In addition, the receiver 2 can communicate with the terminal device 1 via a communication means such as a wireless LAN and operate in cooperation with the terminal device 1 .

The broadcast transmission device 3 is a device that transmits a broadcast signal.

The propriety determination server device 4 receives an inquiry from the receiver 2 via the Internet 9 and transmits the determination result in response to the inquiry to the receiver 2 . Specifically, it is as follows. The inquiry received by the availability determination server device 4 includes identification information for identifying the broadcasting organization service and a URL indicating the location of the AIT of the Hybridcast application running on the receiver 2 . The propriety determination server device 4 determines whether or not the identification information identifying the organization service matches the URL indicating the location of the AIT. That is, the permission determination server device 4 determines whether or not the designated Hybridcast application can be activated on the receiver 2 . The propriety determination server device 4 transmits the information on the propriety of activation, which is the determination result, to the receiver 2 as a response.

The service server device 5 distributes AIT of Hybridcast, application itself (execution code of the application, etc.), and data such as contents used by the application to the terminal device 1 and the receiver 2 via the Internet 9. do.

Internet 9 is a communication network. On the Internet 9, for example, communication using Internet protocol is performed. Communication can be performed between the terminal device 1 and the service server device 5 via the Internet 9 . Further, communication can be performed via the Internet 9 between the receiver 2 and the availability determination server device 4 and the service server device 5 .

FIG. 3 is a sequence diagram showing the procedure of exchange between the terminal device 1 and the receiver 2. As shown in FIG. In the procedure shown here, the terminal device 1 requests activation of the Hybridcast application on the receiver 2 . Each step will be described below along this sequence.

First, in step S1, pairing between the terminal device 1 and the receiver 2 is performed. The pairing in this step is based on the standard "IPTV Regulations, Hybridcast Operational Regulations
IPTVFJ STD-0013 Version 2.7” is based on the terminal authentication method specified in section 7.2.2.

Next, in step S<b>2 , the terminal device 1 acquires organized channel information from the receiver 2 . The processing of this step is performed by the terminal device 1 according to the standard "IPTV Regulations Hybridcast Operational Regulations IPTVFJ STD-0013 Version 2.7", Section 7.2.3.2.3.2.2 "Acquisition of organization channel information". This is done by calling the API "channels" defined in . The URL for calling the API "channels" is "<BaseURL>/channels". Here, "<BaseURL>" is the base URL. By calling the API, the terminal device 1 acquires the JSON data structure. The JSON data structure obtained by the terminal device 1 contains information of all organized services that its receiver 2 can receive. The information of the programming service includes an original network identifier (original_network_id), a transport stream identifier (transport_stream_id), a service identifier (service_id), and a programming service name (broadcast_channel_name) of each programming service. The organization service name is a character string representing the name of the organization service (channel). The terminal device 1 can recognize the provider (cable television provider, etc.) from this organization service name. The value of broadcast_channel_name that the receiver 2 returns to the terminal device 1 is defined in the standard "ARIBTR-B14 Volume 4 Digital Terrestrial Television Broadcast PSI/SI Operational Regulations" section 30.4.2.1. It corresponds to the character string corresponding to the broadcasting station name described in network_name_descriptor. In the case of independent broadcasting of a cable television operator in a terrestrial digital broadcasting network, the organization service name may be the ts_name_char (TS name) in the TS information descriptor of the NIT and the logo_id value in the logo transmission descriptor of the SDT.

Next, in step S3, the terminal device 1 performs determination processing regarding the organization service name. Specifically, the terminal device 1 determines whether or not the specific organization service name stored in advance is the organization service name included in the JSON data structure obtained in step S2.
If the data acquired in step S2 includes the name of a specific organizing service that has been stored in advance, the terminal device 1 requests the activation of the Hybridcast application associated with that organizing service. In other cases (when the name of the specific organization service stored in advance is not included in the data acquired in step S2), the terminal device 1 does not request the activation of the Hybridcast application.

As a result of the determination in step S3, the terminal device 1 performs the processing of the next step S4 only when requesting to start the Hybridcast application. That is, in step S4, the terminal device 1 requests the receiver 2 to start the Hybridcast application. This activation request uses the API "hybridcast" specified in Section 7.2.3.2.3.3.1 "Activation request" of the standard "IPTV Regulations Hybridcast Operation Regulations IPTVFJ STD-0013 Version 2.7". This is done by calling The URL for calling the API "hybridcast" is "<BaseURL>/hybridcast". Here, "<BaseURL>" is the base URL. When calling this API, the terminal device 1 passes the defined JSON data structure. The JSON data structure contains the original network identifier (original_network_id), transport stream identifier (transport_stream_id) and service identifier (service_id) of the orchestration service. Also, the JSON data structure includes the URL of the XML-API of the Hybridcast application to be executed, the provider ID, and the application ID. The receiver 2 that has received the information of this JSON data structure inquires of the permission determination server device 4 to obtain information identifying the organization service and information identifying the Hybridcast application (specifically, for example, Check the consistency with the above XML-API URL). That is, if the organization service and the application match, the receiver 2 activates the Hybridcast application. Conversely, if the organization service and the application do not match, the receiver 2 does not activate the Hybridcast application. Note that the processing of step S4 itself can be performed using existing technology.

FIG. 4 is a flowchart showing the procedure of processing by the terminal device 1. As shown in FIG. Description will be made below along this flow chart. Note that the storage unit 14 of the terminal device 1 stores in advance the organization service name of the broadcast to which the device (own application) should select. The programming service name stored in the storage unit 14 corresponds to the programming service name (broadcast_channel_name) acquired by the programming channel information acquisition API "channels". This API "channels" is defined in section 7.2.3.2.3.2.2 "Obtaining programming channel information" of the standard "IPTV Regulations Hybridcast Operation Regulations IPTVFJ STD-0013 Version 2.7". ing.

In step S<b>21 , the authentication unit 12 of the terminal device 1 performs terminal authentication with the receiver 2 . Thereby, the terminal device 1 and the receiver 2 are paired.

Next, in step S22, the composition channel information acquisition unit 15 of the terminal device 1 obtains the composition channel information from the partner receiver 2 paired in step S21 by calling an API for acquiring composition channel information. get.

Next, in step S23, the organized channel information acquisition unit 15 of the terminal device 1 extracts a list of organized service names from the organized channel information acquired in step S22. The list of organized service names extracted here includes the organized service names of all organized channels that the receiver 2 can receive.

Next, in step S24, the determination unit 16 of the terminal device 1 causes the storage unit 14 to store in advance in the list of the organization service names extracted in step S23 (that is, the organization service names acquired from the receiver 2 side). It is determined whether or not the same service name is included. If it is included (step S24: YES), the process proceeds to the next step S25. If it is not included (step S24: NO), the processing of the next step S25 is skipped, and the processing of the entire flowchart ends.

If the list of organization service names acquired from the receiver 2 contains the same organization service name as the one stored in the storage unit 14 (step S24: YES), the target Hybridcast application is transmitted to the receiver. It means that you can start with 2. If the list of organization service names acquired from the receiver 2 does not include the same organization service name as the one stored in the storage unit 14 (step S24: NO), the target Hybridcast application is transmitted to the receiver. Starting with 2 means that it is inappropriate. However, even in the case of "step S24: NO", if the activation request unit 18 of the terminal device 1 calls the API for requesting activation of the Hybridcast application, information specifying the broadcast resource (original network identifier, If the transport stream identifier, service identifier) happen to match, the Hybridcast application may be activated. That is, there is a possibility that a situation may arise in which the program channel of the broadcast and the content of the Hybridcast application do not match. Branching based on the determination at step S24 prevents such inconsistencies.

Next, when proceeding to step S25, the activation request unit 18 of the terminal device 1 calls the API "hybridcast" for requesting activation of the Hybridcast application. In response to this, the receiver 2 inquires of the acceptance/rejection determination server apparatus 4 about acceptance/rejection. The inquiry about whether or not the decision is made is to confirm whether or not the combination of the information identifying the broadcast resource (original network identifier, transport stream identifier, service identifier) and the URL of the AIT of the Hybridcast application matches. . If the acceptability determination server device 4 returns a positive response to the receiver 2, the receiver 2 activates the designated Hybridcast. Also, the receiver 2 selects the organization service. If the permission determination server device 4 returns a negative response to the receiver 2, the receiver 2 stops starting the Hybridcast application.

FIG. 5 is a schematic diagram showing a configuration example of data acquired by the organized channel information acquisition unit 15 of the terminal device 1 by calling the API "channels" for acquiring organized channel information. The organized channel information acquiring unit 15 acquires the data shown in FIG. 5 through the procedures of step S2 in FIG. 3 and step S22 in FIG.

The data shown in FIG. 5 is data described in JSON format. This data is represented by text having a block structure. In this data, left and right curly braces indicate the beginning and end of blocks, respectively. Note that left and right brackets (brackets, square brackets) denote the beginning and end of enumeration of array elements. In addition, in the figure, line numbers are attached for reference.

The left brace of the first line indicates the beginning of the whole data. The left brace on line 1 corresponds to the right brace on line 34.

The second to fifth lines are the element "head". The element "head" is an object containing HTTP status line information. The element 'head' includes the element 'code' and the element 'message'. The element "code" is the HTTP status code. A value of "200" for the element "code" indicates that the API call was completed successfully. The value "OK" of the element "message" is the descriptive phrase of the above HTTP status code.

The 6th to 33rd lines are the element "body". Element "body" is an object with data returned in response to an API call. The element 'body' includes the element 'created_at' and the element 'media'.

The seventh line represents the element "created_at". The element "created_at" represents the date and time when the receiver 2 responded to the information. The value of the element "created_at" is expressed in the format of "YYYY-MM-DDThh:mm:ssZ" (year/month/day, hour/minute/second) in Coordinated Universal Time (UTC). The value of this element "created_at" is "2020-01-01T09:00:00Z", which represents "January 1, 2020, 9:00:00 (Coordinated Universal Time)".

The 8th to 32nd lines represent the element "media". The element "media" is an array. In the example shown in this figure, this array has only one element. The 9th to 31st lines are the array elements. This element contains the element "type" and the element "channels". The element "type" represents the type of media. In other words, the element “type” is a character string indicating which type of media channel information the data is. The element "type" can take values such as "TD" (representing terrestrial digital), "BS" (representing BS (broadcast satellite)), "CS" (representing CS (communication satellite)). The value of "type" in line 10 is "TD". The 11th to 30th lines are the element "channels". The element "channels" on the 11th to 30th lines corresponds to the element "type" on the 10th line. That is, the element "channels" from the 11th line to the 30th line is an array representing information of a plurality of organized channels belonging to "TD" (digital terrestrial).

The array from line 11 to line 30 has two elements. The first element from the 12th line to the 20th line and the second element from the 21st line to the 29th line. Each of these elements corresponds to an organization channel. Here, for the sake of convenience, reference numerals are used to indicate the contents of the first element as block 901 and the contents of the second element as block 902 . Each of blocks 901 and 902 has an element "logical_channel_number", an element "resource", and an element "broadcast_channel_name". Among these, the element "resource" is an object further having the element "original_network_id", the element "transport_stream_id", and the element "service_id".

The element "logical_channel_number" is a character string representing the logical channel number assigned to the organization channel.
The element "original_network_id" is an integer value (0 or more and 65535 or less) representing an original network identifier.
The element “transport_stream_id” is an integer value (0 or more and 65535 or less) representing a transport stream identifier.
The element "service_id" is an integer value (0 or more and 65535 or less) representing a service identifier.
The element "broadcast_channel_name" is a character string representing the name of the programming service.

Regarding block 901, the value of each element is as follows.
The value of the element "logical_channel_number" is "011".
The value of the element “original_network_id” is 32736.
The value of the element “transport_stream_id” is 32736.
The value of the element “service_id” is 1024.
The value of the element "broadcast_channel_name" is "general TV Tokyo".

Regarding block 902, the value of each element is as follows.
The value of the element "logical_channel_number" is "101".
The value of the element “original_network_id” is 32399.
The value of the element “transport_stream_id” is 32399.
The value of the element “service_id” is 23672.
The value of the element "broadcast_channel_name" is "Shibuya Cable TV".

The data illustrated in FIG. 5 has only information of a plurality of channels whose element "type" is "TD". The data acquired by the terminal device 1 as organized channel information may have information of other media types (“BS” or “CS”).

Information used for determination by the determination unit 16 of the terminal device 1 in this embodiment is information on the program service name (broadcast_channel_name) of each channel in the data shown in FIG. As described in step S23 of FIG. 4, the organized channel information acquisition unit 15 extracts a list of organized service names from the acquired organized channel information. That is, when the organized channel information acquisition unit 15 acquires, for example, the data in FIG. do. In this case, the organized channel information acquisition unit 15 creates a list of "(“General TV Tokyo”, “Shibuya Cable TV")" consisting of two organized service names. The list created in this way is used for the determination process described in step S24 of FIG. For example, when the organization service name stored in the storage unit 14 is "Shibuya Cable TV", "Shibuya Cable TV" is included in the created list "("General TV Tokyo", "Shibuya Cable TV")". Therefore, the terminal device 1 executes an API call requesting activation of the Hybridcast application based on the determination result. Alternatively, for example, when the organization service name stored in the storage unit 14 is "Edogawa Community Channel", "Edogawa Community Channel" is included in the created list "("General TV Tokyo", "Shibuya Cable TV")". Since it is not included, the terminal device 1 does not request (suppresses) activation of the Hybridcast application based on the determination result.

As described above, according to the present embodiment, even in a situation where information specifying broadcast resources (for example, a combination of original network identifiers, transport stream identifiers, and service identifiers) happens to match, it is not consistent with the organization service. Inappropriate apps can be prevented from starting. That is, according to this embodiment, the independence of broadcasters can be ensured. In addition, according to the present embodiment, it is not necessary to change the existing procedure (procedure for making an inquiry to the availability determination server device) in order to prevent the activation of inappropriate applications as described above. In other words, there is no need to change the existing standards regarding the availability determination service.

At least part of the functions of the terminal device, the receiver, the acceptability determination server device, and the like in the above-described embodiments can be realized by a computer. In that case, a program for realizing this function may be recorded in a computer-readable recording medium, and the program recorded in this recording medium may be read into a computer system and executed. It should be noted that the "computer system" referred to here includes hardware such as an OS and peripheral devices. In addition, “computer-readable recording media” refers to portable media such as flexible discs, magneto-optical discs, ROMs, CD-ROMs, DVD-ROMs, USB memories, and storage devices such as hard disks built into computer systems. Say things. In addition, "computer-readable recording medium" means a medium that temporarily and dynamically retains a program, such as a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line. , it may also include something that holds the program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client in that case. Further, the program may be for realizing part of the functions described above, or may be a program capable of realizing the functions described above in combination with a program already recorded in the computer system.

Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design and the like are included within the scope of the gist of the present invention.

For example, the present invention is applicable to industries related to devices such as terminal devices that operate in cooperation with broadcast receivers, industries that manufacture, sell, or distribute applications that run on terminal devices, and distribution of content using a hybridcast system. It can be used in the content providing industry, etc. (including the broadcasting business). However, the scope of application of the present invention is not limited to those exemplified here.

1 Terminal device 2 Receiver 3 Broadcast transmission device 4 Approval determination server device 5 Service server device 9 Internet 11 Communication unit 12 Authentication unit 14 Storage unit 15 Organized channel information acquisition unit 16 Judgment unit 18 Activation request unit 100 System

Claims (2)

an organized channel information acquisition unit for acquiring organized channel information including an organized service name, which is the name of an organized channel receivable by the receiver, from a receiver that receives a broadcast;
a storage unit that stores a specific organization service name in advance;
an activation request unit having a function of requesting the receiver to activate a program associated with the specific organization service name;
Determining whether or not the specific organization service name stored in the storage unit is included in the organization channel information acquired from the receiver by the organization channel information acquisition unit, and based on the determination result, the activation a determination unit that controls whether the request unit requests to start the program;
with
The determination unit controls the activation request unit to request activation of the program when the specific organization service name is included in the organization channel information acquired from the receiver, and controls the activation request unit to request activation of the specific organization service. controlling the activation request unit not to request activation of the program if the name is not included in the organized channel information acquired from the receiver;
Terminal equipment. the computer,
The terminal device according to claim 1,
A program to function as

Images