JP6070182B2 - Terminal device, content server, content browsing system, browsing history management method and program - Google Patents

Description

  The present invention relates to a terminal device, a content server, a content browsing system, a browsing history management method, and a program.

There has been known a content browsing system in which a terminal device acquires content from a content server via a network and displays the content so that a user can browse the content. In such a content browsing system, for example, there may be a business model in which a reward is exchanged between a content server operator and a content server operator.
As an example, the following configuration is known as a content providing system in which content stored on a server is shared and used by a plurality of terminals connected via a network. That is, the server of the content providing system stores the content provider, and calculates points for each content provider according to the frequency of use of the content. The server of the content providing system intends to distribute profits to the content provider according to the calculated points.

JP 2005-275676 A

  For example, there is a content browsing system in which content can be browsed by accessing a content server by an operation on a specific content browsing application installed in a terminal device. In such a content browsing system, in order for as many users as possible to browse the content, it is necessary to have as many users as possible know the existence of the application and install it on the terminal device. .

Therefore, for example, as a content server operator, it is conceivable to adopt a business model in which an alliance contract is made with a terminal device manufacturer, an application download site operator, etc. for providing a content browsing application to a user.
As an example, when the alliance contractor is a terminal device manufacturer, the content server operator cooperates in providing the content browsing application to the user of the manufacturer's terminal device. As an example of cooperation, a content browsing application is preinstalled in a terminal device sold by a manufacturer. Alternatively, the content browsing application is posted on an application download site that can be accessed only by the terminal device of the manufacturer that is operated by the manufacturer of the terminal device.
Then, when the content is browsed by the content browsing application provided by the alliance contractor as in the above example, the profit is distributed from the content server operator to the manufacturer according to the number of content browsing. . Similarly, when content is browsed by a content browsing application downloaded from an application download site accessible only by the terminal device of the manufacturer itself, profits are distributed to the manufacturer according to the number of content browsing. Is.

  Under the alliance contract business model as described above, it is necessary to count the number of content views for each alliance contractor. For this purpose, in the case of an alliance contract as described above, for example, every time the content browsing application accesses the content on the content server, the alliance contractor who provided the access source content browsing application can be recognized. It will be necessary.

In the case of Patent Document 1, the profit is distributed to the content provider who provides the content stored in the content server. In this case, at the stage where the content is provided to the content server, the content server associates the content with the content provider. Therefore, it is particularly difficult to manage the content usage frequency and the content provider in association with each other. Absent.
For this reason, in Patent Document 1, it is not necessary to recognize an access source application for content browsing. Therefore, with the technique of Patent Document 1, although it is possible to calculate the profit to be distributed to the content provider, it is difficult to calculate the profit to be distributed to the alliance contractor who cooperates with the provision of the content browsing application.

  The present invention has been made in view of such circumstances, and makes it possible for a content server to recognize an alliance contractor who has cooperated in providing a content browsing application that has accessed the content server for browsing content. For the purpose.

  In order to solve the above-described problems, a terminal device according to an aspect of the present invention is contracted for providing a communication unit that performs communication with a content server via a network and provision of a content browsing application for browsing content. The content information includes alliance information including one or more pieces of alliance information by contract in which a communication environment for performing communication for browsing content provided by the content server is associated with one alliance contract identifier indicating an alliance contract. An alliance information acquisition unit acquired from a server, and an alliance information identifier acquired by the alliance information acquisition unit, and an alliance contract identifier associated with the communication environment of the own device when performing communication for browsing content Contract identifier acquisition unit and container Respect browse request for browsing by specifying the tree, by adding the alliance agreement identifier acquired by the alliance agreement identifier acquiring unit and a browsing request transmitting unit that transmits to the content server.

  Further, according to one aspect of the present invention, in the above terminal device, the alliance contract identifier acquisition unit includes an alliance contract identifier associated with a communication environment of the own device when performing communication for browsing content. If there are a plurality of alliance information in the alliance information including the alliance contract identifier indicating the alliance contract associated with the communication environment based on the priority set in the alliance information by contract included in the alliance information Thus, the alliance contract identifier included in the alliance information by contract with the highest priority may be acquired.

  Further, according to one aspect of the present invention, in the above terminal device, the alliance contract identifier acquisition unit is associated with a combination of a plurality of different types of communication environments when the device performs communication for browsing content. An alliance contract identifier indicating the alliance contract may be acquired.

In addition, the content server as one aspect of the present invention includes a communication unit that communicates with a terminal device via a network, and an alliance contract that is contracted to provide a content browsing application for browsing content. Alliance information transmission for transmitting, to the terminal device, alliance information including one or more pieces of alliance information by contract in which a communication environment for performing communication for browsing content provided by the content server is associated with the alliance contract identifier. A content transmission unit that transmits the content specified by the browsing request to the terminal device that is the transmission source of the browsing request in response to reception of the browsing request that requests browsing of the content, and the received browsing request specifies Allian attached to the content and the received browsing request Generated for any user requesting browsing history including the content associating the contract identifier is received, and a browsing history management unit to be stored in the browsing history storage unit.

  The content browsing system as one aspect of the present invention includes a terminal device and a content server connected to the terminal device through communication via a network, and the terminal device is a content browsing for browsing content. One or more pieces of alliance information by contract in which a communication environment for performing communication for browsing the content provided by the content server is associated with one alliance contract identifier indicating an alliance contract contracted for application provision. An alliance information acquisition unit that acquires alliance information including the content information from the content server, and an alliance associated with the communication environment of the device itself when performing communication for browsing content from the alliance information acquired by the alliance information acquisition unit Acquire contract identifier An Alliance Contract Identifier Acquiring Unit, and a browsing request transmitting unit that adds an Alliance Contract Identifier acquired by the Alliance Contract Identifier Acquiring Unit to a browsing request for browsing by designating content and transmits it to the content server; The content server includes an alliance information transmitting unit that transmits alliance information to the terminal device, and transmits the content specified by the browsing request to the terminal device that is the browsing request transmission source in response to receiving the browsing request. Each time a browsing request is received, a browsing history including content that associates the content specified by the received browsing request with the content specified by the received browsing request and the alliance contract identifier added to the received browsing request is generated. A browsing history management unit that is stored in the browsing history storage unit.

  In addition, the browsing history management method as one aspect of the present invention shows an alliance contract that is contracted to provide a communication step for communicating with a content server via a network and provision of a content browsing application for browsing content. An alliance for acquiring from the content server alliance information including one or more pieces of alliance information by contract, which associates a communication environment for performing communication for browsing content provided by the content server with respect to one alliance contract identifier. An information acquisition step; an alliance contract identifier acquisition step for acquiring an alliance contract identifier associated with the communication environment of the device itself when performing communication for viewing content from the alliance information acquired by the alliance information acquisition step; Respect browse request for browsing by specifying the content and by adding a alliance agreement identifier acquired by the alliance agreement identifier acquisition step and a browsing request transmitting step of transmitting to the contents server.

  In addition, the program as one aspect of the present invention indicates an alliance contract that is contracted for providing a communication step for performing communication with a content server via a network and provision of a content browsing application for browsing the content. An alliance for acquiring from the content server alliance information including one or more pieces of alliance information by contract, which associates a communication environment for performing communication for browsing content provided by the content server with respect to one alliance contract identifier. An alliance contract identifier for acquiring an alliance contract identifier associated with the communication environment of the device itself when performing communication for viewing content from the alliance information acquired by the information acquisition step and the alliance information acquisition step In order to execute a browsing request for transmitting a request to the content server by adding the alliance contract identifier acquired in the alliance contract identifier acquiring step to the browsing request for browsing by specifying the content belongs to.

  As described above, according to the present invention, the content server can recognize the alliance contractor who cooperated with the provision of the content browsing application that has accessed the content server for browsing the content. can get.

It is a figure which shows the structural example of the content browsing system in 1st Embodiment. It is a figure which shows the structural example of the terminal device and content server in 1st Embodiment. It is a figure which shows the example of the content of the alliance information corresponding to 1st Embodiment. It is a figure which shows the structural example of a browsing history table. It is a figure which shows the example of a process sequence which the terminal device and content server in 1st Embodiment perform in relation to acquisition of alliance information and acquisition of an alliance contract identifier. It is a figure which shows the example of a process sequence which the terminal device and content server in 1st Embodiment perform corresponding to management of browsing history. It is a figure which shows the example of the content of the alliance information corresponding to 2nd Embodiment. It is a figure which shows the example of a process sequence for the terminal device in 2nd Embodiment to acquire an alliance contract identifier. It is a figure which shows the structural example of the terminal device and content server in a modification. It is a figure which shows the example of a process sequence which the terminal device and content server in a modification perform in relation to switching of a content browsing application.

  Hereinafter, a content browsing system, a terminal device, a content server, and a content browsing method according to an embodiment of the present invention will be described with reference to the drawings.

<First Embodiment>
[Configuration example of content browsing system]
FIG. 1 shows a configuration example of a content browsing system in the present embodiment.
The content browsing system in the present embodiment is configured by connecting a plurality of terminal devices 100 and a content server 200 via a network NW.
Each terminal device 100 has a content browsing application installed therein. The terminal device 100 activates an installed content browsing application in response to a user operation.
The terminal device 100 on which the content browsing application operates accesses content in the content server 200 in accordance with, for example, a user operation. That is, the terminal device 100 transmits a content request specifying specific content to the content server 200. Then, the terminal device 100 displays the content received from the content server 200 in response to the content request on the screen. Thereby, the user can browse the content selected according to his operation on the screen of the terminal device 100, for example.

  In addition, the terminal device 100 of this embodiment should just be information terminals, such as a mobile telephone, a smart phone, a personal computer, for example.

  The content server 200 is a server that provides the terminal device 100 with content to be browsed. That is, the content server 200 stores content. In response to receiving the content request from the terminal device 100, the content server 200 searches the stored content for the content specified by the received content request, and searches the searched content for the content request transmission source. It transmits to the terminal device 100.

  The type of content in the present embodiment is not particularly limited, but in the following description, an example is an electronic leaflet. An electronic leaflet is a digitalized version of a so-called folded leaflet that is folded into a newspaper, for example.

In addition, the content browsing system of the present embodiment is related to the content server operator 1, the content provider 2, and the alliance contractor 3.
The content server operator 1 is a trader such as a company that operates the content server 200.
Each content provider 2 is a trader as a content provider. Each content provider 2 has a contract with the content server operator 1.
The content provider 2 transmits and registers content as an electronic flyer, which is an advertisement of, for example, its own company or its own store, to the content server 200 as appropriate. The content registered in this way is stored in the content server 200.
The content provided by the content provider 2 is determined for each access (one page view), for example, according to a contract with the content server operator 1. That is, the unit price of the advertising fee is determined according to the user browsing the advertisement as an electronic leaflet once with the terminal device 100.
For example, the content provider 2 pays an advertisement fee to the content server operator 1 in accordance with the number of the provided content accessed by the terminal device 100 (that is, the number of browsing (page views) by the user).

Each of the alliance contractors 3 is a contractor who has an alliance contract with the content server operator 1 regarding cooperation for providing the content browsing application to the user.
The content server operator 1 wants as many users as possible to view the electronic leaflet, but this requires that as many users as possible install the content browsing application in the terminal device 100. . For example, the content server operator 1 uploads the content browsing application to an application download site or the like, but the content browsing application is recognized by the users and downloaded to the terminal device 100 more efficiently. If it becomes, it is preferable.
Therefore, the content server operator 1 asks the alliance contractor 3 as another supplier to cooperate in providing the content browsing application. Instead, according to the number of contents browsed using the content browsing application provided by the alliance contractor 3, the content server operator 1 has a certain ratio among the advertising fees received from the content provider 2. Pay the amount to Alliance Contractor 3. The content server operator 1 and the alliance contractor 3 have an alliance contract regarding the provision of such a content browsing application.

[Configuration of terminal device]
FIG. 2 shows a configuration example of the terminal device 100 and the content server 200 in the first embodiment. The terminal device 100 illustrated in FIG. 2 includes a communication unit 101, a storage unit 102, a control unit 103, an operation unit 104, and a display unit 105.

  The communication unit 101 executes communication with the content server 200 via the network NW. In this figure, illustration of the network NW shown in FIG. 1 is omitted.

  The storage unit 102 stores various information used by the terminal device 100. The storage unit 102 illustrated in FIG. 2 includes a content browsing application storage unit 121, a communication environment information storage unit 122, a reception alliance information storage unit 123, and an alliance contract identifier storage unit 124.

  The content browsing application storage unit 121 stores a content browsing application installed in the terminal device 100. As described above, the content browsing application is application software used to browse content as an electronic leaflet registered in the content server 200.

The content browsing application stored in the content browsing application storage unit 121 is obtained by installing the content browsing application provided by the alliance contractor 3.
As an example, the content browsing application is stored in the content browsing application storage unit 121 when the user downloads it from an application download site operated by an alliance contractor. Alternatively, the content browsing application is stored in the content browsing application storage unit 121 when the manufacturer of the terminal device 100 is preinstalled in the terminal device 100.

The communication environment information storage unit 122 stores communication environment information indicating a communication environment when the terminal device 100 communicates via the network NW.
The communication environment information includes, for example, a model number assigned to a model as the terminal device 100 by a manufacturer that manufactured the terminal device 100. The communication environment information includes various parameters indicating the network environment when communicating with the content server 200 via the network NW.

The reception alliance information storage unit 123 stores alliance information received from the content server 200.
The alliance information includes one or more contract-specific alliance information. One alliance information by contract is one alliance that uniquely identifies the communication environment of the terminal device 100 when performing communication for browsing the content provided by the content server 200 and the alliance contract signed by the alliance contractor 3. This information is associated with a contract identifier.

FIG. 3 shows an example of alliance information. The alliance information shown in FIG. 3 has a format as an XML (Extensible Markup Language) file.
One or more alliance information by contract is described (marked up) between the tags <alliance_list> and </ alliance_list> in FIG. Specifically, in FIG. 3, two pieces of alliance information als1 and als2 are described. Hereinafter, the alliance information als1 and als2 by contract is described as the alliance information als by contract unless otherwise distinguished.

In the alliance information by contract als1, the description of <id> makerA </ id> indicates that the alliance contract identifier is “makerA”. That is, the character string described between the tags <id> and </ id> indicates the corresponding alliance contract identifier. The alliance contractor 3 of the alliance contract indicated by the alliance contract identifier “makerA” is, for example, the manufacturer of the terminal device 100.
The next tag in the same hierarchy as the tags <id> and </ id> indicates the type of communication environment associated with the alliance contract identifier. The tags on the next line in the same hierarchy as the tags <id> and </ id> in the contract-based alliance information als1 are <devices> and </ devices>. Tags <devices> and </ devices> indicate that a terminal device is defined as a type of communication environment.

Here, in the agreement-specific alliance information als1, two lines of <device_id> A-05D </ device_id> and <device_id> A-06D </ device_id> exist between the tags <devices> and </ devices>. It has been described. Tags <device_id> and </ device_id> are tags for describing the model number of the terminal device. In other words, the alliance information by contract als1 indicates that two model numbers “A-05D” and “A-06D” are associated with one alliance contract identifier “makerA”.
The contents of the alliance contract to which this alliance information by als1 corresponds is, for example, an alliance with the alliance contract identifier “makerA” when the content is browsed by a terminal device of “model numbers“ A-05D ”and“ A-06D ”. Profit is distributed to the alliance contractor 3 who has a contract.

Next, in the alliance information als2 by contract, <id> catv01 </ id> is described, which indicates that the alliance contract identifier is “catv01”. The alliance contractor 3 of the alliance contract with the alliance contract identifier “catv01” is, for example, a certain cable television company.
In the alliance information als2 by contract, the tags on the next line in the same hierarchy as the tags <id> and </ id> are also <devices> and </ devices>, and the terminal device is defined as the type of communication environment It shows that. <Device_id> makerS Tablet01 </ device_id> is described between the tags <devices> and </ devices>.

  The content of the alliance contract corresponding to the alliance information by the contract als2 is, for example, an alliance contractor who has an alliance contract with the alliance contract identifier “catv01 when viewing content with a terminal device of model number“ makereS Tablet01 ” The profit is distributed to 3 ”.

  Returning to FIG. The alliance contract identifier storage unit 124 stores the alliance contract identifier acquired from the alliance information by the alliance contract identifier acquisition unit in the control unit 103.

The control unit 103 controls each unit in the terminal device 100. The control unit 103 includes, for example, a CPU (Central Processing Unit) as hardware, and can execute a program as a content browsing application stored in the content browsing application storage unit 121, for example.
The control unit 103 has the following functions by executing a program as a content browsing application. That is, the control unit 103 includes an alliance information acquisition unit 131, an alliance contract identifier acquisition unit 132, a browsing request transmission unit 133, and a display control unit 134.

The alliance information acquisition unit 131 acquires alliance information from the content server 200.
Specifically, the alliance information acquisition unit 131 determines whether or not alliance information is stored in the reception alliance information storage unit 123 in response to activation of the content browsing application storage unit 121. When the alliance information is stored in the reception alliance information storage unit 123, the reception alliance information storage unit 123 does not particularly perform a process for acquiring the alliance information.
On the other hand, when the alliance information is not stored in the reception alliance information storage unit 123, the alliance information acquisition unit 131 requests the alliance information from the content server. When the alliance information acquired by the content server 200 in response to the request is received by the communication unit 101, the alliance information acquisition unit 131 stores the received alliance information in the received alliance information storage unit 123.

  The alliance information once stored in the reception alliance information storage unit 123 is continuously stored without being erased even after the content browsing application is terminated, for example. Therefore, when the content browsing application is activated next time, there is no need to execute processing for acquiring alliance information from the content server 200. Thereby, for example, the activation time of the content browsing application can be shortened and the communication load for initial setting at the time of activation can be reduced.

  Note that the alliance information acquisition unit 131 may acquire alliance information from the content server 200 each time the content browsing application is activated and sequentially store it in the reception alliance information storage unit 123. In this case, for example, when the alliance information is updated by the content server operator 1, the updated content can be reflected quickly.

The alliance contract identifier acquiring unit 132 acquires an alliance contract identifier indicating an alliance contract associated with a communication environment when the terminal device 100 performs communication for browsing content from the alliance information.
In other words, the alliance contract identifier acquisition unit 132 reads the alliance information stored in the reception alliance information storage unit 123. Further, the alliance contract identifier acquisition unit 132 reads the communication environment information from the communication environment information storage unit 122.

Then, the alliance contract identifier acquisition unit 132 acquires the alliance contract identifier associated with the communication environment information read from the communication environment information storage unit 122 by interpreting the alliance information.
Here, the alliance information acquisition unit 131 acquires the alliance information shown in FIG. 3 and stores it in the reception alliance information storage unit 123, and the communication environment information storage unit 122 sets the model number of the terminal device 100 as the communication environment. As an example, the communication environment information indicating “device_id = A-05D” is stored. The terminal device 100 in this case is a device having a model number “A-05D”.

  The alliance contract identifier acquisition unit 132 sequentially reads and interprets the XML format alliance information shown in FIG. 3 from the first line, while the communication environment information indicates “A” between the tags <device_id> and </ device_id>. -05D "is searched.

In the case of the example of FIG. 3, <device_id> “A-05D” </ device_id>, which is a communication environment that matches the communication environment information, is described in the seventh line by the search by the alliance contract identifier acquisition unit 132. Is identified. Therefore, the alliance contract identifier acquisition unit 132 includes a contract including <device_id> “A-05D” </ device_id> as the alliance contract identifier associated with the description of <device_id> “A-05D” </ device_id>. The alliance contract identifier described in the separate alliance information als1 is specified.
That is, the alliance contract identifier obtaining unit 132 includes elements <id> and </ id> described between tags <alliance> and </ alliance> including <device_id> “A-05D” </ device_id>. Get the contents of. In this case, since it is described as <id> makerA </ id>, the alliance contract identifier acquiring unit 132 acquires “id = makerA” as the alliance contractor identifier as the alliance contract identifier.
The alliance contract identifier acquisition unit 132 stores the acquired alliance contract identifier in the alliance contract identifier storage unit 124.

The browsing request transmission unit 133 adds the alliance contract identifier acquired by the alliance contract identifier acquisition unit 132 to the browsing request for browsing by specifying the content, and transmits it to the content server.
The user can perform an operation (viewing instruction operation) for instructing browsing by specifying content by operating the terminal device 100 in which the content browsing application is operating. In response to the browsing instruction operation, the browsing request transmission unit 133 reads out the alliance contract identifier acquired by the alliance contract identifier acquiring unit 132 and stored in the alliance contract identifier storage unit 124, and adds it to the browsing request.
The browsing request transmission unit 133 causes the communication unit 101 to transmit the browsing request with the alliance contract identifier added thereto to the content server 200.

The content server 200 that has received the browsing request transmits the content specified by the browsing request to the terminal device 100. The transmitted content is received by the communication unit 101 of the terminal device 100.
The display control unit 134 causes the display unit 105 to display the received content. Thereby, the user can browse the content designated for browsing.

The operation unit 104 collectively indicates operators and operation devices provided in the terminal device 100. Note that the touch panel is also included in the operation unit 104 when a touch panel integrated with the display unit 105 is provided and an operation by touching the display unit 105 with an operation body such as a finger or a stylus pen is possible.
The display unit 105 displays an image including content, for example, under the control of the display control unit 134.

[Content Server Configuration]
Next, a configuration example of the content server 200 will be described with reference to the same FIG.
The content server 200 illustrated in FIG. 2 includes a communication unit 201, a storage unit 202, and a control unit 203.
The communication unit 201 performs communication with the terminal device 100 via the network NW.

  The storage unit 202 stores various types of information used by the content server 200. The storage unit 202 illustrated in FIG. 2 includes a content storage unit 221, a transmission alliance information storage unit 222, and a browsing history storage unit 223.

  The content storage unit 221 stores content as an electronic leaflet provided by a content provider. The content as an electronic flyer has, for example, a valid period in which browsing is possible, and is not presented as a browsing candidate in periods before and after the valid period, for example. The content storage unit 221 stores, for example, each content in association with a content identifier.

The transmission alliance information storage unit 222 stores alliance information to be transmitted in response to a request from the terminal device 100.
The alliance information stored in the transmission alliance information storage unit 222 is created so that the content server operator 1 appropriately updates according to the current contract status with each alliance contractor 3.

The browsing history storage unit 223 stores the browsing history generated by the browsing history management unit 233.
The browsing history is information that is generated each time a browsing request is received, and includes content that associates the content specified by the received browsing request with the alliance contract identifier that was added to the received browsing request. .
In response to receiving the browsing request, the content server 200 transmits the content specified by the browsing request to the terminal device 100 that is the browsing request transmission source. The user browses the content by displaying the content received by the terminal device 100 that is the browsing request transmission source. Therefore, the reception of a single browsing request corresponds to the content specified by the browsing request being browsed once. The browsing history storage unit 223 stores the browsing history in the browsing history table.

FIG. 4 shows an example of the structure of the browsing history table stored in the browsing history storage unit 223.
One record in the browsing history table shown in FIG. 4 is a browsing history corresponding to reception of one browsing request.
The browsing history has a structure in which, for example, a browsing date and time, a user identifier, and an alliance contract identifier are associated with a content identifier.
The content identifier is an identifier that uniquely identifies the content specified by the corresponding browsing request.

The browsing date and time indicates the date and time when the corresponding content was browsed. Specifically, the date and time when the corresponding content was browsed may be the date and time when the corresponding browsing request was received or the date and time when the content was transmitted to the browsing request transmission source terminal device 100 in response to the corresponding browsing request. That's fine.
The user identifier is an identifier that uniquely identifies the user who is the sender of the corresponding browsing request. For example, the terminal device 100 adds and transmits information (user information) about a user registered as a user of the content browsing application to the browsing request. The user information includes a user identifier. User information including a user identifier is used for user authentication and the like.

The alliance contract identifier is information added to the corresponding browsing request.
The alliance contract identifier stored in the browsing history table indicates an alliance contract corresponding to the communication environment of the terminal device that has transmitted the corresponding browsing request. That is, the alliance contract identifier stored in the browsing history table indicates the alliance contract with the alliance contractor 3 to which the profit of the advertising fee generated in response to the browsing of the content by the corresponding browsing request should be distributed.

Returning to FIG. In the content server 200 of FIG. 2, the control unit 203 controls each unit in the content server 200. The control unit 203 includes, for example, a CPU as hardware.
When the CPU in the control unit 203 executes the program, the control unit 203 has the following functions. That is, the control unit 203 includes an alliance information transmission unit 231, a content transmission unit 232, and a browsing history management unit 233.

  The alliance information transmission unit 231 transmits alliance information to the terminal device 100. That is, as described above, the terminal device 100 transmits an alliance information request when the alliance information is not stored in the reception alliance information storage unit 123. The alliance information transmission unit 231 reads the alliance information from the transmission alliance information storage unit 222 in response to the alliance information request received by the communication unit 201, and transmits the read alliance information to the terminal device 100 that is the request transmission source. To do.

In response to receiving the browsing request, the content transmitting unit 232 transmits the content specified by the browsing request to the terminal device 100 that is the browsing request transmission source.
That is, the browsing request includes a content identifier as information for specifying the content, for example. The content transmission unit 232 searches the content storage unit 221 for the content with the content identifier included in the received browsing request, and transmits the searched content to the terminal device 100 that is the source of the request for idempotency.
The browsing history management unit 233 generates a browsing history every time a browsing request is received, and stores the browsing history in the browsing history storage unit 223.

[Example of processing procedure]
As described above, the terminal device 100 determines whether the alliance information is stored in the reception alliance information storage unit 123 at the timing when the content browsing application is activated. Then, the terminal device 100 acquires the alliance information from the content server 200 when the alliance information is not stored.
In addition, when the content browsing application is activated, the terminal device 100 acquires an alliance contract identifier using the alliance information. The alliance contract identifier acquired in this way is added to a browsing request for browsing the content and transmitted to the content server 200, and used by the content server 200 to generate a browsing request history.

  An example of a processing procedure executed by the terminal device 100 and the content server 200 according to the first embodiment in association with acquisition of alliance information and acquisition of an alliance contract identifier will be described with reference to the flowchart of FIG.

In the terminal device 100, the control unit 103 reads and activates the content browsing application stored in the content browsing application storage unit 121 (step S101).
After the content browsing application is activated, the alliance information acquisition unit 131 of the control unit 103 determines whether the alliance information is stored in the reception alliance information storage unit 123 (step S102).
When alliance information is stored (step S102—YES), the alliance information acquisition unit 131 skips steps S103 and S104 and proceeds to step S105.
On the other hand, when alliance information is not stored (step S102—NO), the alliance information acquisition unit 131 transmits an alliance information request to the content server 200 (step S103).

  The alliance information acquisition unit 131 receives the alliance information transmitted by the content server 200 in response to the transmission of the alliance information request, and stores the received alliance information in the reception alliance information storage unit 123 (step S104).

Next, the alliance contract identifier acquisition unit 132 reads the alliance information from the reception alliance information storage unit 123 (step S105). Further, the alliance contract identifier acquisition unit 132 reads the communication environment information from the communication environment information storage unit 122 (step S106).
The alliance contract identifier acquisition unit 132 starts to interpret the alliance information read in step S105 (step S107). For example, when the alliance information is in the XML format as shown in FIG. 3, reading is started from the first line and the contents of the elements defined by the tags are recognized.

In the process of proceeding with the interpretation of the alliance information after step S107, the alliance contract identifier obtaining unit 132 executes the following processing. That is, the alliance contract identifier acquisition unit 132 determines whether there is a description that matches the communication environment indicated by the communication environment information read in step S106 among the communication environments described in the alliance information (step S108). ).
If there is a description that matches the communication environment indicated by the communication environment information (YES in step S108), the alliance contract identifier acquisition unit 132 acquires the alliance contract identifier associated with the communication environment that matches the communication environment information from the alliance information. (Step S109).
The alliance contract identifier acquisition unit 132 stores the acquired alliance contract identifier in the alliance contract identifier storage unit 124 (step S110).
If there is no description that matches the communication environment indicated by the communication environment information (NO in step S108), the alliance contract identifier acquisition unit 132 skips steps S109 and S110 and ends the process of FIG.

Further, the alliance information transmission unit 231 in the content server 200 waits for the alliance information request transmitted from the terminal device 100 to be received (step S201—NO).
In response to the reception of the alliance information request (step S202—YES), the alliance information transmission unit 231 reads the alliance information stored in the transmission alliance information storage unit 222. Then, the alliance information transmitting unit 231 transmits the read alliance information to the terminal device 100 that has requested the alliance information (step S202).

Next, an example of a processing procedure executed by the terminal device 100 and the content server 200 corresponding to browsing history management will be described with reference to the flowchart of FIG. Note that the processing shown in this figure is executed under the state where the content browsing application is operating on the terminal device 100.
In the terminal device 100, the browsing request transmission unit 133 waits for an operation (browsing instruction operation) for instructing browsing of content to the content browsing application by the user (step S301-NO, step S312). Processing for returning to step S301 with -NO).
Then, in response to the browsing instruction operation, the browsing request transmission unit 133 adds the alliance contract identifier read from the alliance contract identifier storage unit 124 to the browsing request (step S302). Note that the browsing request includes the content identifier of the content specified as the browsing target by the browsing instruction operation.
The browsing request transmission unit 133 transmits the browsing request with the alliance contract identifier added in step S302 to the content server 200 (step S303).

  In response to the transmission of the browsing request in step S303, the content server 200 transmits the content designated as the browsing target by the browsing request. The transmitted content is received by the communication unit 101 of the terminal device 100. The display control unit 134 displays the content image received by the communication unit 101 on the display unit 105 (step S304).

  The control unit 103 determines whether or not an operation for terminating the content browsing application has been performed (step S305). When the operation for terminating the content browsing application has not been performed (step S305—NO), the control unit 103 returns the process to step S301. On the other hand, when an operation for terminating the content browsing application is performed (YES in step S305), the control unit 103 terminates the content browsing application. At this time, for example, the alliance contract identifier stored in the alliance contract identifier storage unit 124 may be deleted.

In addition, the content transmission unit 232 in the content server 200 is on standby for receiving a browsing request transmitted from the terminal device 100 (step S401—NO).
In response to receiving the browse request (step S401—YES), the content transmission unit 232 searches the content storage unit 221 for the content with the content identifier specified by the received browse request (step S402).
The content transmission unit 232 transmits the content searched in step S402 to the terminal device 100 that is the browsing request transmission source (step S403).

Also, the browsing history management unit 233 generates a browsing history including the alliance information added to the browsing request received this time (step S404).
That is, the browsing history management unit 233 acquires a content identifier and a user identifier included in the browsing request received this time. Moreover, the alliance contract identifier added to the browse request received this time is acquired. Also, the date and time when the current browsing request is received (or the date and time when content is transmitted in response to the browsing request) is acquired as the browsing date and time. The browsing history management unit 233 generates a browsing history based on the acquired content identifier, user identifier, browsing date and time, and alliance contract identifier.

  The browsing history management unit 233 stores the browsing history generated in step S404 in the browsing history storage unit 223 (step S405). At this time, the browsing history management unit 233 stores the browsing history in the browsing history storage unit 223 so as to newly register the browsing history in, for example, the browsing history table shown in FIG.

Thus, in the present embodiment, the browsing history is managed in the content server. Depending on the browsing history of this embodiment, an alliance contract identifier is associated. In other words, depending on the browsing history of the present embodiment, an alliance agreement regarding cooperation in providing a content browsing application in which content is browsed is shown for each browsing of content.
Therefore, by counting the browsing history of this embodiment for each alliance contract identifier, it is possible to obtain the number of browsing contents (number of page views) corresponding to each alliance contract. Thereby, in this embodiment, the number of browsing of the content for every alliance contract can be calculated | required correctly, and the profit distribution with respect to the alliance contractor 3 can be performed appropriately.

  It should be noted that, for example, the content server 200 may perform the summation of the number of browsing contents for each alliance contract, the calculation of the amount to be distributed to the alliance contractor 3, and the process for profit sharing.

For example, as another method for obtaining a browsing history including an alliance contract identifier, a content browsing application including the alliance contract identifier in setting information or the like may be created and distributed.
However, according to this method, it is necessary to create a content browsing application that stores setting information including different alliance contract identifiers for each alliance contract, which makes it difficult to create and maintain the content browsing application. For example, in the case of version upgrade, it is necessary to upgrade for each content browsing application with a different alliance contract identifier added, so it is difficult to cope with the version upgrade.

On the other hand, in the case of the present embodiment, for example, the alliance contract identifier corresponding to the communication environment of the terminal device 100 is obtained by using the alliance information in which alliance-specific alliance information als corresponding to all alliance contracts is described. Can be obtained.
Thereby, in this embodiment, since the content browsing application can be shared among alliance contractors, the creation and maintenance management of the content browsing application can be simplified.

Furthermore, in the alliance information in the present embodiment, a plurality of different model numbers can be associated with one alliance contract identifier as shown in the alliance information als1 by contract in FIG. That is, in the alliance information of the present embodiment, when any of a plurality of different communication environments may correspond to one alliance contract identifier, these communication environments are associated with a common alliance contract identifier. It has a structure.
Therefore, in the present embodiment, for example, even if the terminal device 100 has a different communication environment, if the corresponding alliance contract is common, the same alliance contract identifier is transmitted from each terminal device 100 to the content server 200. can do.

For example, the terminal device 100 may transmit the browsing request with communication environment information added thereto, and the content server 200 may specify an alliance contract identifier corresponding to the received communication environment information and manage the browsing history. it can. However, in the case of this configuration, every time the content server 200 receives a browsing request, it is necessary to execute a process for specifying an alliance contract identifier from the communication environment information, which increases the processing load.
On the other hand, in the present embodiment, since the alliance contract identifier specified by the terminal device 100 can be acquired by the content server 200, there is no increase in processing load as described above.

<Second Embodiment>
[Overview]
Next, the second embodiment will be described. For example, as the number of alliance contracts increases, there is a possibility that the communication environment when browsing content using the content browsing application corresponds to a plurality of alliance information als in the alliance information. . As an example, the model number of a terminal device 100 of a certain user corresponds to the communication environment of a certain contract-based alliance information als in the alliance information, and a modem operator used at home by the same user has another alliance by contract. The situation corresponds to the information als.
As an example, such a situation can be made by combining a plurality of communication environments that can be handled by the company in order to allow as many users as possible to use the content browsing application by one manufacturer or communication carrier. This is likely to occur if you have an alliance agreement.

As described above, when the communication environment of one user corresponds to a plurality of alliance-specific alliance information als in the alliance information, in the second embodiment, for example, an alliance contract identifier is acquired as follows.
That is, in the alliance information, the priority order is set in advance in the alliance information als by contract.
When there are a plurality of alliance agreement identifiers associated with the communication environment indicated by the communication environment information of the terminal device 100 in the alliance information, the terminal device 100 determines that the alliance information by contract is based on the priority set in the alliance information. Get the contract identifier. That is, the terminal device 100 includes the alliance information by contract with the highest priority among the alliance information by contract including the alliance contract identifier indicating the alliance contract associated with the communication environment indicated by the communication environment information of the own device. Get an alliance contract identifier.

  Further, in the alliance information of FIG. 3, one type of communication environment information is associated with one alliance contract identifier. Specifically, in the alliance information als1 and als2 by contract in FIG. 3, only the communication environment information as the model number of the terminal device 100 is associated with each other. In the alliance information als1 by contract, two pieces of communication environment information as model numbers are described, but there is only one type of model number as the type of communication environment information.

However, for example, depending on the contents of the alliance contract, the alliance contract cannot be established unless the terminal device 100 having a specific model number passes through the access point of a specific network communication provider and accesses the content server 200. A situation can arise.
That is, there may be a case where a combination (logical product) of a plurality of different types of communication environment information should be associated with one alliance contract identifier.
Therefore, in the second embodiment, the terminal device 100 can acquire an alliance contract identifier corresponding to a combination (logical product) of a plurality of different types of communication environment information.

[Alliance information example]
With reference to FIG. 7, an example of the content of the alliance information corresponding to the second embodiment will be described.
In the alliance information shown in FIG. 7, alliance information als11 to als16 by contract is described. The alliance information in the XML format in the second embodiment has a higher priority as the contracted alliance information als is closer to the head of the described line.
In the alliance information in FIG. 7, the alliance information als11 by contract, the alliance information als12, als13, als14, als15, and als16 are described in order from the top to the bottom of the line. Therefore, in the alliance information of FIG. 7, the priority order of the alliance information by contract als11 is the highest, and thereafter, the priority order becomes lower in the order of alliance information by contracts als12, als13, als14, als15, als16.

  The contract-specific alliance information als11 shows the same contents as the contract-specific alliance information als1 shown in FIG.

The contract-based alliance information als12 indicates that the alliance contract identifier is “CATV01”. Communication environment information is described by tags <networkinfo> and </ networkinfo>. Tags <networkinfo> and </ networkinfo> indicate that the type of communication environment information is network information related to the network. <Macaddress> xxxxxxx </ macaddress> and <macaddress> xxyyxyx </ macaddress> are described between the tags <networkinfo> and </ networkinfo>. Tags <macaddress> and </ macaddress> are tags that define MAC (Media Access Control) addresses. In other words, the alliance information by contract als12 indicates the MAC address as the network information.
The contents of the alliance contract corresponding to the alliance information by the license alls12 is “when the content is viewed by the terminal device 100 with the MAC address“ xxxxxxx ”or“ xxyyxyx ”, the alliance contract identifier“ CATV01 ”is concluded. The profit is distributed to the alliance contractor 3 ”.

The alliance information als13 by contract indicates that the alliance contract identifier is “phone-provider01_sim”. Communication environment information is described by tags <siminfo> and </ siminfo>. Tags <siminfo> and </ siminfo> indicate that the type of communication environment information is a SIM (Subscriber Identity Module) card. <Sim> 44010 </ sim> is described between the tags <siminfo> and </ siminfo>. Tags <sim> and </ sim> are tags defining SIM card numbers.
Therefore, the contents of the alliance contract corresponding to the alliance information by contract 13 is “if the content is viewed by the terminal device 100 with the SIM card number“ 44010 ”, the alliance contract with the alliance contract identifier“ phone-provider01_sim ”is Profit will be distributed to alliance alliance contractor 3 ".

The alliance information als14 by contract indicates that the alliance contract identifier is “phone-provider01_sqmode”. In addition, tags <networkinfo> and </ networkinfo> are described in the communication environment information. <Apn> sqmode.ne.jp </ apn> is described between the tags <networkinfo> and </ networkinfo>. Tags <apn> and </ apn> are tags that define Internet connection services for smartphones. <apn> sqmode.ne.jp </ apn> indicates “sqmode.ne.jp” which is one of Internet connection services for smartphones.
Therefore, the contents of the alliance contract to which the alliance information by contract als13 corresponds is the alliance agreement identifier “phone-provider01_sqmode” when the content is viewed via the Internet connection service “sqmode.ne.jp”. Profit is distributed to the alliance contractor 3 who has a contract.

The alliance information als15 by contract indicates that the alliance contract identifier is “phone-provider01_other”. In addition, tags <networkinfo> and </ networkinfo> are described in the communication environment information. <Apn> aaaa.net </ apn> is described between the tags <networkinfo> and </ networkinfo>. <apn> sqmode.ne.jp </ apn> represents “aaaa.net” which is one of the Internet connection services for smartphones.
Therefore, the contents of the alliance contract corresponding to the alliance information by the alls 13 is that when the content is viewed via the “aaaa.net” Internet connection service, the alliance contract with the alliance contract identifier “phone-provider01_others” is used. Profit will be distributed to alliance alliance contractor 3 ".

The alliance information als16 by contract indicates that the alliance contract identifier is “catv01_makerS”.
In addition, in the alliance information als16 by contract, another type of communication environment information indicated by tags <networkinfo> and </ networkinfo> is described following the communication environment information indicated by tags <devices> and </ devices>. Is done. That is, in the alliance information als16 by contract, two different types of communication environment information, that is, a communication environment as terminal device information and a communication environment as network information are described in parallel.
The alliance-by-contract alliance information als16 having this structure includes a combination of a communication environment described by tags <devices> and </ devices> and a communication environment described by tags <networkinfo> and </ networkinfo> “catv01_makerS”. This is an alliance contract with the alliance contract identifier.
In the case of FIG. 7, <device_id> makerS Tablet01 </ device_id> is described between the tags <devices> and </ devices>. Further, <macaddress> xxxxxxx </ macaddress> and <macaddress> xxyyxyx </ macaddress> are described between the tags <networkinfo> and </ networkinfo>.
The contents of the alliance contract corresponding to the alliance information by the als 16 are “the alliance contract when the model number of the terminal device 100 is“ makerS Tablet01 ”and the MAC address is either“ xxxxxxx ”or“ xxyyxyx ”. The profit is distributed to the alliance contractor 3 who has an alliance contract with the identifier “catv01_makerS”.

In the alliance information of FIG. 7, alliance information als13, als14, and als15 by contract corresponds to an alliance contract in which the same telecommunications carrier indicated by “phone-provider01” is the alliance contractor 3. For this reason, when using the terminal device 100 of the telephone carrier indicated by “phone-provider01”, the communication environment indicated by the communication environment information of the terminal device 100 is the alliance information als13, als14 by contract. , There is a possibility that it matches the communication environment of two or more of als15. In such a case, the alliance contract identifier acquiring unit 132 may select the highest priority among the alliance information by contract that matches the communication environment, and acquire the alliance contract identifier of the selected alliance information by contract. .
Specifically, the case where the communication environment indicated by the communication environment information of the terminal device 100 among the alliance information by the contract als13, als14, and als15 matches the two communication environments of the alliance information by contract als13 and als14 will be described as an example. . In this case, the contract-specific alliance information als13 precedes the contract-specific alliance information als14, and therefore the contract-specific alliance information als13 has a higher priority than the contract-specific alliance information als14. Therefore, in this case, the alliance contract identifier acquisition unit 132 acquires the alliance contract identifier of “phone-provider01_sim” described in the alliance information by license als13.

[Example of processing procedure]
With reference to the flowchart of FIG. 8, an example of a processing procedure for the terminal device 100 according to the second embodiment to acquire an alliance contract identifier will be described. In FIG. 8, steps that are the same as those in FIG. 5 are denoted by the same reference numerals, and description thereof is omitted. Further, the configurations of the terminal device 100 and the content server 200 in the second embodiment may be the same as those in FIG.

In FIG. 8, the processing of steps S101 to S105 may be the same as in FIG.
The alliance contract identifier acquisition unit 132 reads the communication environment information from the communication environment information storage unit 122. However, in the second embodiment, the communication environment information storage unit 122 may store the communication environment information in a plurality of combinations. In this case, the alliance contract identifier acquisition unit 132 reads a plurality of pieces of communication environment information from the communication environment information storage unit 122 (step S106A).
Next, the alliance contract identifier acquiring unit 132 starts processing for interpreting the alliance information by contract described in the alliance information read out in step S105 in accordance with a predetermined priority order (step S10 7 A). Note that the processing in step S10 7 A is the same processing as step S10 7 in FIG. 5 because when the alliance information is in the XML format, reading is performed from the first line and the analysis processing is executed. . However , in the second embodiment, the processing for executing the interpretation according to the priority order is realized by interpreting the alliance information in the XML format from the top line.

In step S108, the alliance contract identifier acquisition unit 132 determines whether the alliance information includes a description of the communication environment that matches the communication environment information read in step S106.
However, in the second embodiment, the alliance contract identifier acquisition unit 132 may read a plurality of different types of communication environment information in step S106A. When a plurality of different types of communication environment information are read, the alliance contract identifier acquisition unit 132 determines whether there is a description of the communication environment that matches the combination of the plurality of different types of communication environment information.

As a specific example, the alliance information read out in step S105 has the contents shown in FIG. 7. The communication environment information read out in step S106A includes the model number (device_id) of “makerS Tablet01” and the MAC address of “xxxxxxx”. Give an example of a combination.
In this case, in the process in which the alliance contract identifier acquiring unit 132 interprets the alliance information from the top line, the communication environment information does not match up to the alliance information by the contract als11 to als15. Then, at the stage where the contract-specific alliance information als16 is interpreted, the communication information matches.
Steps S109 and S110 in FIG. 8 are the same as those in FIG.

As described above, the processing shown in FIG. 8 is executed in the terminal device 100, so that, for example, even when the communication environment information of the terminal device 100 corresponds to the communication environment of the plurality of alliance information als by contract, 1 One alliance contract identifier can be obtained.
That is, in the alliance information, the priority order of the alliance information als by contract is set in advance. As a result, the alliance contract identifier acquisition unit 132 selects the alliance contract identifier of the alliance information als by contract with the highest priority among the plurality of alliance information als by contract to which the communication environment indicated by the communication environment information of the terminal device 100 corresponds. Can be obtained.

<Modification>
[Overview]
The content browsing application in the first and second embodiments is supplied to the alliance contractor 3 by the content server operator 1, but the provider to the user is the alliance contractor 3. That is, the content browsing application according to the first and second embodiments is uploaded to a download site of an application operated by the alliance contractor 3 or preinstalled in the terminal device 100 sold by the alliance contractor 3. It is.
Hereinafter, the content browsing application provided by the alliance contractor 3 as a provider to the user as described above is also referred to as an allied content browsing application.
On the other hand, for example, the content server operator 1 can directly provide a user with a content browsing application for an application download site that is not related to the alliance contractor 3. In this case, the provider of the content browsing application to the user is the content server operator 1. The content browsing application provided by the content server operator 1 as a provider to the user is also referred to as a content browsing application that does not support the alliance.

Here, in the case of a content browsing application that does not support the alliance, even if the content is browsed, it is not necessary to count the alliance contract identifiers in correspondence with the alliance contract.
Accordingly, it is not necessary to acquire alliance information and an alliance contract identifier for a content browsing application that does not support the alliance.
Therefore, as a content browsing application that does not support the alliance, for example, the function of acquiring the alliance information and the alliance contract identifier may be omitted, and the content browsing application corresponding to the alliance may be created as a separate application.

However, when content browsing applications that are alliance-compatible and non-alliance-compatible are provided as individual applications, the user is provided with an environment in which any content browsing application can be installed.
As an example, the content browsing application corresponding to the alliance is uploaded to an application download site operated by the manufacturer of the terminal device 100 and accessible only by the terminal device 100 of the company. In parallel with this, the content server operator 1 is also an environment in which an application that does not support an alliance is uploaded to a download site of another application that does not have an alliance contract.

In such an environment, the user of the terminal device 100 can download and install an allied content browsing application from an application download site operated by the manufacturer of the terminal device 100. Further, the user of the terminal device 100 can download and install a content browsing application that does not support an alliance from a download site of another application that does not have an alliance contract.
For this reason, the state where the content browsing application corresponding to the alliance and the content browsing application not corresponding to the alliance are installed together in the terminal device 100 may occur.

The operation of the content browsing application as seen by the user is the same between the content browsing application compatible with the alliance and the content browsing application not compatible with the alliance. For this reason, in the case where an alliance-compatible content browsing application and a non-alliance-compatible content browsing application are installed side by side, it is left to the user to decide which one to activate and use when browsing content.
For this reason, for example, the user may start and use only a content browsing application that does not support the alliance.

  However, for example, in the case of the terminal device 100 described above, it is preferable to preferentially start the content browsing application corresponding to the alliance, for example, for consideration of the alliance contractor 3. It is thought that there is also.

Therefore, in the modified example, when the content browsing application corresponding to the alliance and the content browsing application not supporting the alliance are installed in the terminal device 100, the following operation is realized.
In other words, when an operation for starting a content browsing application that does not support an alliance is performed, the content browsing application that supports an alliance is started instead of the content browsing application that does not support an alliance. Thereby, even if the user is not particularly conscious, the user can preferentially use the content browsing application that does not support the alliance.

[Configuration example of terminal device]
FIG. 9 shows a configuration example of the terminal device 100 and the content server 200 in the modification. In FIG. 9, the same parts as those in FIG.
With reference to FIG. 9, the structural example of the terminal device 100 in a modification is demonstrated first. In the terminal device 100 illustrated in FIG. 9, the storage unit 102 further includes a content browsing application storage unit 121 </ b> A and an installation history information storage unit 125 with respect to the configuration illustrated in FIG. 2.

The content browsing application storage unit 121A stores a content browsing application that does not support the alliance.
Note that the content browsing application storage unit 121 in FIG. 9 stores the same content browsing application as in FIG. That is, the content browsing application storage unit 121 stores an alliance-compatible content browsing application.

  The installation history information storage unit 125 stores installation history information. The installation history information indicates an application that has been installed in the terminal device 100 so far, for example, by an application identifier.

In the terminal device 100 of FIG. 9, the control unit 103 further includes an application switching control unit 135.
The application switching control unit 135 is a functional unit that operates in response to activation of a content browsing application that does not support the alliance. If an alliance-compatible content browsing application is installed, the application switching control unit 135 terminates the activated alliance-incompatible content browsing application and instructs the alliance-compatible content browsing application to start. Thereby, in the terminal device 100, the content browsing application corresponding to the alliance operates.

For example, the application switching control unit 135 may determine whether or not an alliance-compatible browsing application is installed as follows.
The application switching control unit 135 acquires application registration information from the content server 200 in response to activation of a content browsing application that does not support the alliance. The application registration information indicates an alliance-compatible content browsing application provided at the present time, for example, by an application identifier.

The application switching control unit 135 determines whether or not the application indicated by the application registration information is included in the installation history information stored in the installation history information storage unit 125. At this time, the application switching control unit 135 may determine whether or not the application identifier indicated by the application registration information is included in the installation history information, for example.
If the application indicated by the application registration information is included in the installation history information, the application switching control unit 135 determines that an alliance-compatible content browsing application is installed. On the other hand, if it is not included in the installation history information, the application switching control unit 135 may determine that the alliance-compatible content browsing application is not installed.

  In addition, when an alliance-compatible content browsing application is not installed, the application switching control unit 135 continues to start the content browsing application that does not support the alliance. Thereby, in the terminal device 100, the content browsing application that does not support the alliance is activated.

When a content browsing application that does not support an alliance is operating, it is not necessary to acquire alliance information and an alliance contract identifier as described above. For this reason, when the content browsing application that does not support the alliance is operating, the functions of the alliance information acquisition unit 131 and the alliance contract identifier acquisition unit 132 in the control unit 103 are invalidated. When a content browsing application that does not support an alliance is operating, the browsing request transmission unit 133 transmits a browsing request without adding an alliance contract identifier.
As can be understood from the above description, the application switching control unit 135 is a functional unit obtained by activating an allied content browsing application. Therefore, when starting a content browsing application that does not support the alliance, the application switching control unit 135 may not function.

[Content server configuration example]
With reference to the same FIG. 9, the structural example of the content server 200 corresponding to a modification is demonstrated.
The storage unit 202 in the content server 200 illustrated in FIG. 9 further includes an application registration information storage unit 224 in addition to the configuration illustrated in FIG. The application registration information storage unit 224 stores application registration information.
Further, the control unit 203 in the content server 200 illustrated in FIG. 9 further includes an application registration information transmission unit 234 with respect to the configuration illustrated in FIG. In response to the application registration information request transmitted from the terminal device 100, the application registration information transmission unit 234 transmits the application registration information stored in the application registration information storage unit 224 to the terminal device 100 that is the application registration information request transmission source. To do.

[Example of processing procedure]
The flowchart in FIG. 10 illustrates an example of a processing procedure executed by the terminal device 100 and the content server 200 in connection with switching of activation from a content browsing application that does not support an alliance to a content browsing application that supports an alliance.
In response to the operation for starting the content browsing application not supporting the alliance being performed, the control unit 103 starts the content browsing application not supporting the alliance stored in the content browsing application storage unit 121A (step S501). ).
The application switching control unit 135 is activated in the control unit 103 in response to activation of a content browsing application that does not support the alliance. The application switching control unit 135 transmits an application registration information request to the content server 200 (step S502).

In response to the application registration information request, the content server 200 transmits the application registration information. The transmitted application registration information is received by the communication unit 101 of the terminal device 100.
As described above, the application registration information includes, for example, the application identifier of the content browsing application corresponding to the alliance as information indicating the content browsing application corresponding to the alliance distributed so far.
Further, the installation history information stored in the installation history information storage unit 125 includes, for example, an application identifier for each installed application as information indicating an application installed in the terminal device 100 so far.

  The application switching control unit 135 searches the installation history information for the content browsing application indicated by the application registration information (step S503). For this purpose, for example, the application switching control unit 135 may search for the application identifier indicated by the application registration information from the application identifiers included in the installation history information.

The application switching control unit 135 determines whether or not an alliance-compatible content browsing application is installed based on the search result in step S503 (step S504).
If a content browsing application indicated by the application registration information is found in step S503, the application switching control unit 135 determines that an allied content browsing application is installed. On the other hand, if the content browsing application indicated by the application registration information is not found in step S503, the application switching control unit 135 determines that the alliance-compatible content browsing application is not installed.

If it is determined that an alliance-compatible content browsing application is installed (YES in step S504), the application switching control unit 135 performs the following processing.
That is, the application switching control unit 135 executes control for starting the installed content browsing application corresponding to the alliance (step S505). At this time, the application switching control unit 135 may specify the application identifier of the content browsing application corresponding to the alliance searched from the installation history information in step S503, for example, to instruct activation.

Next, the application switching control unit 135 ends the content browsing application that does not support the alliance activated in step S501 (step S506).
Through the processing in steps S505 and S506, an alliance-compatible content browsing application is automatically activated instead of the alliance-noncompatible content browsing application.

If it is determined that an alliance-compatible content browsing application is not installed (step S504—NO), the application switching control unit 135 skips steps S505 and S506 and ends the processing shown in FIG.
In this case, the content browsing application that does not support the alliance activated in step S501 continues to operate on the terminal device 100 as it is.

  In addition, the application registration information transmission unit 234 in the content server 200 waits for reception of an application registration information request transmitted from the terminal device 100 (step S601—NO). In response to the reception of the application registration information request (step S601—YES), the application registration information transmission unit 234 reads the application registration information from the application registration information storage unit 224, and the terminal device 100 that is the application registration information request transmission source. (Step S602).

Instead of acquiring the application registration information from the content server 200, the application registration information may be included in the setting information of the content browsing application that does not support the alliance.
In this case, the application switching control unit 135 can acquire application registration information from the setting information stored in the content browsing application storage unit 121A, and execute switching control of the content browsing application. Therefore, the terminal device 100 in this case does not need to execute communication for acquiring application registration information from the content server 200.
On the other hand, when the application registration information is obtained from the content server 200, the application registration information can be updated on the content server 200 side. Therefore, the distribution status of the latest alliance-compatible content browsing application is always provided. It can correspond to.

  Note that, contrary to the above description, the application switching control unit 135 can control to start a content browsing application that does not support the alliance instead of starting the content browsing application that supports the alliance. is there.

  Note that a program for realizing the functional units shown in FIGS. 2 and 9 is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into a computer system and executed. You may manage alliance agreements. Here, the “computer system” includes an OS and hardware such as peripheral devices.

Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used.
The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Further, the “computer-readable recording medium” refers to a volatile memory (RAM) in a computer system that becomes a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. In addition, those holding programs for a certain period of time are also included. The program may be a program for realizing a part of the functions described above, and may be a program capable of realizing the functions described above in combination with a program already recorded in a computer system.

  As mentioned above, although embodiment of this invention was explained in full detail with reference to drawings, the concrete structure is not restricted to this embodiment, The design etc. of the range which does not deviate from the summary of this invention are included.

DESCRIPTION OF SYMBOLS 100 Terminal device 101 Communication part 102 Storage part 103 Control part 104 Operation part 105 Display part 131 Alliance information acquisition part 132 Alliance contract identifier acquisition part 133 Browse request transmission part 134 Display control part 135 Application switching control part 200 Content server 201 Communication part 202 Storage unit 203 Control unit 231 Alliance information transmission unit 232 Content transmission unit 233 Browsing history management unit 234 Application registration information transmission unit

Claims (7)

A communication unit that communicates with the content server via the network;
Corresponding communication environment for performing communication for browsing content provided by the content server to one alliance contract identifier indicating an alliance contract contracted for providing a content browsing application for browsing content An alliance information acquisition unit that acquires alliance information including one or more alliance information by contract from the content server;
An alliance contract identifier acquiring unit that acquires an alliance contract identifier associated with the communication environment of the device itself when performing communication for browsing content from the alliance information acquired by the alliance information acquiring unit;
A terminal device comprising: a browsing request transmitting unit that adds an alliance contract identifier acquired by the alliance contract identifier acquiring unit to a browsing request for browsing by specifying content and transmits the request to the content server. The alliance contract identifier acquisition unit
The priority set in the alliance information by contract included in the alliance information when there are multiple alliance agreement identifiers in the alliance information associated with the communication environment of the own device when performing communication for viewing content The alliance contract identifier included in the alliance information by contract having the highest priority is acquired from the alliance information by contract including the alliance contract identifier indicating the alliance contract associated with the communication environment. The terminal device described. The alliance contract identifier acquisition unit
The terminal device according to claim 1, wherein the terminal device according to claim 1 or 2 acquires an alliance contract identifier indicating an alliance contract associated with a combination of a plurality of different types of communication environments when performing communication for browsing content. A communication unit that communicates with a terminal device via a network;
A communication environment for performing communication for browsing the content provided by the content server is associated with one alliance contract identifier indicating an alliance contract with which a content browsing application for browsing content is provided. An alliance information transmitting unit that transmits alliance information including one or more pieces of alliance information by contract to the terminal device;
In response to receiving a browsing request that requests browsing of content, a content transmission unit that transmits the content specified by the browsing request to the terminal device that is the browsing request transmission source;
A browsing history storage unit that generates a browsing history including content that associates the content specified by the received browsing request with the alliance contract identifier added to the received browsing request, and receives the browsing request A content server comprising a browsing history management unit stored in A terminal device, and a content server connected to the terminal device by communication via a network,
The terminal device
Corresponding communication environment for performing communication for browsing content provided by the content server to one alliance contract identifier indicating an alliance contract contracted for providing a content browsing application for browsing content An alliance information acquisition unit that acquires alliance information including one or more alliance information by contract from the content server;
An alliance contract identifier acquiring unit that acquires an alliance contract identifier associated with the communication environment of the device itself when performing communication for browsing content from the alliance information acquired by the alliance information acquiring unit;
A browsing request transmission unit that adds an alliance contract identifier acquired by the alliance contract identifier acquisition unit to a browsing request for browsing by designating content, and transmits to the content server;
The content server
An alliance information transmitting unit for transmitting alliance information to the terminal device;
In response to receiving the browsing request, a content transmitting unit that transmits the content specified by the browsing request to the terminal device of the browsing request transmission source;
A browsing history storage unit that generates a browsing history including content that associates the content specified by the received browsing request with the alliance contract identifier added to the received browsing request, and receives the browsing request A content browsing system comprising: a browsing history management unit stored in A communication step for communicating with the content server via the network;
Corresponding communication environment for performing communication for browsing content provided by the content server to one alliance contract identifier indicating an alliance contract contracted for providing a content browsing application for browsing content Alliance information acquisition step of acquiring alliance information including one or more alliance information by contract from the content server;
An alliance contract identifier acquisition step for acquiring an alliance contract identifier associated with the communication environment of the own device when performing communication for viewing content from the alliance information acquired by the alliance information acquisition step;
A browsing history management method comprising: a browsing request transmission step of adding an alliance contract identifier acquired by the alliance contract identifier acquiring step to a browsing request for browsing by specifying content and transmitting the browsing request to the content server. On the computer,
A communication step for communicating with the content server via the network;
Corresponding communication environment for performing communication for browsing content provided by the content server to one alliance contract identifier indicating an alliance contract contracted for providing a content browsing application for browsing content Alliance information acquisition step of acquiring alliance information including one or more alliance information by contract from the content server;
An alliance contract identifier acquisition step for acquiring an alliance contract identifier associated with the communication environment of the own device when performing communication for viewing content from the alliance information acquired by the alliance information acquisition step;
A program for executing a browsing request transmission step of adding an alliance contract identifier acquired in the alliance contract identifier acquiring step to a browsing request for browsing by specifying content and transmitting the browsing request to the content server.

Images