JP2009020904A - System, method and program for providing service - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a service providing system capable of preventing the illegal use of content. <P>SOLUTION: The system includes a client 30 that transmits system information specific to information processing equipment to request to provide content, and a service provider server 20 that transmits the content to the client when the system information transmitted with the request from the client is in accordance with system information acquired from the client in advance. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a service providing system, a service providing method, and a service providing program, and in particular, a service providing system, a service providing method, and a service providing program that use an authentication technique when reproducing content downloaded from a content server via a network. About.

  2. Description of the Related Art Conventionally, a service providing system configured by connecting a service provider server that provides a service and a client that receives the service to the Internet is known. In this service providing system, the client can receive and use various contents provided by the service provider server via the Internet.

  In such a service providing system, a user who receives a service first performs user registration with a service provider server from a client, and acquires an ID and a password. Thereafter, the user requests the service provider server to provide desired content using the acquired ID and password. Upon receiving this request, the service provider server performs user authentication with the ID and password sent from the client, and transmits the content to the user if it is a valid user.

  However, in a conventional service providing system that performs user authentication by the above-described method, a third party can steal an ID and password from a user and impersonate the third party to obtain content. In addition, when a user teaches another user an ID and password or copies content and service execution software for reproducing the content to another user's device, the other user can receive the service illegally. . As a result, there is a problem that the profit of the service provider is impaired.

  The present invention has been made to solve such a problem, and an object of the present invention is to provide a service providing system, a service providing method, and a service providing program capable of preventing unauthorized use of content.

  In order to achieve the above object, a service providing system according to a first aspect of the present invention includes a client that transmits system information unique to an information processing device to request service provision, and a request from the client. And a service provider server that provides a service to the client when the sent system information matches the system information acquired in advance from the client.

  In the service providing system according to the first aspect, the system information includes a hardware serial number and version number, a user name, a company name, a software serial number and version number, and software input when software is installed. It is possible to use at least one of a name and a symbol to be identified, configuration information of an information processing device used as a client, and the like. According to this configuration, since the system information is different even for information processing devices of the same model, impersonation and unauthorized use can be prevented by using this system information for authentication.

  The service providing system according to the second aspect of the present invention provides a client requesting user registration and a user identifier given to the client in response to a user registration request from the client for the same purpose as described above. And a service provider server that transmits the embedded service execution software to the client and causes the user identifier to be registered at a specific location of the client. At this time, the client receives a service from the service provider server when the user identifier embedded in the service execution software received from the service provider server matches the user identifier registered in the specific location.

  The service providing system according to the third aspect of the present invention, for the same purpose as described above, requests user registration and requests a ticket that is a key for executing service execution software, In response to the user registration request, the service execution software embedded with the user identifier to be given to the client is sent to the client, and in response to the ticket request, the user identifier is stored in the ticket and sent to the client Including a provider server. At this time, the client receives a service from the service provider server when the user identifier embedded in the service execution software received from the service provider server matches the user identifier stored in the ticket.

  In addition, the service providing system according to the fourth aspect of the present invention, for the same purpose as described above, requests user registration and requests a ticket which is a key for executing service execution software, A service provider server that registers a user identifier to be given to the client in a specific location of the client in response to the user registration request, stores the user identifier in the ticket in response to the ticket request, and transmits the ticket to the client including. At this time, the client receives a service from the service provider server when the user identifier registered in the specific location matches the user identifier stored in the ticket.

  In addition, the client according to the fifth aspect of the present invention uses the system information and service provision requesting means for requesting the provision of services by transmitting system information unique to the information processing device for the same purpose as described above. Service execution means for executing a service provided by the authentication is included.

  In addition, the client according to the sixth aspect of the present invention includes an identifier registration means for registering a user identifier sent in response to a user registration request in a specific place for the same purpose as described above, and a user registration Service execution software receiving means for receiving service execution software embedded with a user identifier sent in response to a request, and a user identifier registered at a specific location by the identifier registration means and received by the service execution software receiving means Service providing receiving means for receiving a service when the user identifier embedded in the service execution software matches.

  In addition, the client according to the seventh aspect of the present invention, for the same purpose as described above, receives service execution software that is sent in response to a user registration request and receives service execution software embedded with a user identifier. Received by the receiving means, the ticket receiving means for receiving the ticket storing the user identifier sent in response to the request for the ticket which is a key for executing the service execution software, and the service execution software receiving means Service providing receiving means for receiving a service when the user identifier embedded in the service execution software matches the user identifier stored in the ticket received by the ticket receiving means.

  In addition, the client according to the eighth aspect of the present invention includes an identifier registration unit for registering a user identifier sent in response to a user registration request in a specific place for the same purpose as described above, and service execution software A ticket receiving means for receiving a ticket storing a user identifier, which is sent in response to a request for a ticket which is a key for executing, and a user identifier registered at a specific location by the identifier registration means; Service provision receiving means for receiving service provision when the user identifier stored in the ticket received by the ticket receiving means matches.

  The service provider server according to the ninth aspect of the present invention receives a service provision request for receiving a service provision request sent with system information unique to an information processing device for the same purpose as described above. A receiving unit; and a service providing unit that provides a service when the system information received by the service providing request receiving unit matches the system information acquired in advance.

  In addition, the service provider server according to the tenth aspect of the present invention provides a user identifier given to a user registration request source in response to a received user registration request for the same purpose as described above. Identifier registration means for registering at a specific location, and service execution software transmission means for transmitting service execution software embedded with a user identifier to a request source in response to a user registration request.

  In addition, the service provider server according to the eleventh aspect of the present invention is embedded with a user identifier to be given to a user registration request source in response to a received user registration request for the same purpose as described above. In response to the received request for a ticket that is a key for executing the service execution software, the request execution unit transmits a ticket storing a user identifier to the request source. Ticket transmitting means for transmitting to the device.

  In addition, the service provider server according to the twelfth aspect of the present invention provides, for the same purpose as described above, a user identifier given to a user registration request source in response to the received user registration request. An identifier registration unit for registering at a specific location, and a ticket transmission unit for transmitting a ticket storing a user identifier to a request source in response to a received request for a ticket that is a key for executing service execution software And.

  A service providing method according to a thirteenth aspect of the present invention connects a client that receives a service and a service provider server that provides the service for the same purpose as described above, to the information processing device on the client side. The system information sent to the service provider server is sent to the service provider server to request service provision, and the system information sent together with the request from the client on the service provider server side becomes the system information acquired from the client in advance. If they match, it is configured to provide service to the client.

  The service providing method according to the fourteenth aspect of the present invention connects a client that receives a service and a service provider server that provides the service for the same purpose as described above, from the client to the service provider server. In response to a user registration request from the client, the service provider server sends service execution software in which the user identifier to be given to the client is embedded, and sends the user identifier to the client. When the user identifier embedded in the service execution software received from the service provider server on the client side matches the user identifier registered at the specific location on the client side, the service provider server It is configured to receive the offer.

  The service providing method according to the fifteenth aspect of the present invention connects a client that receives a service and a service provider server that provides the service for the same purpose as described above, from the client to the service provider server. Requests user registration, and on the service provider server side, responds to the user registration request from the client, sends the service execution software embedded with the user identifier to be given to the client, and executes the service on the client side Request a ticket, which is a key for executing the software, from the service provider server, and in response to the ticket request from the client, store the user identifier in the ticket and send it to the client. The service received from the service provider server on the client side And a service provider server to receive the service when embedded in executing the software stored in the user identifier and the ticket and the user identifier matches.

  The service providing method according to the sixteenth aspect of the present invention connects, for the same purpose as described above, a client that receives a service and a service provider server that provides the service, from the client to the service provider server. Requests user registration, responds to user registration request from the client on the service provider server side, registers the user identifier given to the client at a specific location of the client, and executes the service execution software on the client side Requesting a ticket, which is the key for the service, storing the user identifier in the ticket in response to the ticket request on the service provider server side, sending it to the client, and registering the client at a specific location on the client side From the service provider server when the identifier matches the user identifier stored in the ticket It is configured to receive the provision of the-bis.

  In addition, the service providing program according to the seventeenth aspect of the present invention provides system information unique to an information processing device when the computer is a client that receives a service from a service provider server for the same purpose as described above. If the computer is a service providing program and the system information sent with the request from the client matches the system information acquired in advance from the client A program for executing a computer so as to provide a service to a client.

  The service providing program according to the eighteenth aspect of the present invention requests the user registration from the service provider server when the computer is a client that receives a service from the service provider server for the same purpose as described above. When the local computer is a service providing program, in response to a user registration request from the client, service execution software in which the user identifier to be given to the client is embedded is transmitted to the client, and the user identifier is sent to a specific location of the client. If registered and the local computer is a client, the service provider server provides a service when the user identifier embedded in the service execution software received from the service provider server matches the user identifier registered at the specific location. So that you can receive Is a program for executing a computer.

  The service providing program according to the nineteenth aspect of the present invention requests a user registration from the service provider server when the computer is a client that receives a service from the service provider server for the same purpose as described above. When the local computer is a service providing program, in response to a user registration request from the client, service execution software embedded with a user identifier to be given to the client is transmitted to the client. Requests a ticket, which is a key for executing the execution software, from the service provider server. If the local computer is a service providing program, the user identifier is stored in the ticket in response to the ticket request from the client. Send it to the client, When the computer is a client, if the user identifier embedded in the service execution software received from the service provider server matches the user identifier stored in the ticket, the service provider server receives the service. Is a program for causing a computer to execute.

  Furthermore, the service providing program according to the twentieth aspect of the present invention requests a user registration from the service provider server when the own computer is a client that receives a service from the service provider server for the same purpose as described above. When the local computer is a service providing program, in response to a user registration request from the client, the user identifier given to the client is registered at a specific location on the client, and when the local computer is the client, the service execution software is executed. If the computer is a service providing program, the user identifier is stored in the ticket and sent to the client in response to the ticket request, and the computer is a client. User identification registered at a specific location From the service provider server when a user identifier stored in the ticket matches to receive the service, which is a program for executing a computer.

  Unauthorized use of content can be prevented.

  Hereinafter, a service providing system, a service providing method, and a service providing program according to embodiments of the present invention will be described in detail with reference to the drawings. In the embodiment described below, “service” refers to a service for viewing content such as a movie, music, or a photo, for example. However, the present invention is not limited to this, and is not limited to these. It can be applied to various services using such information processing equipment.

(Embodiment 1)
FIG. 1 is a diagram showing a configuration of a service providing system according to Embodiment 1 of the present invention. This service providing system includes a service provider server 20 and a client 30 connected to the Internet 10. The service provider server 20 and the client 30 communicate with each other via the Internet 10. 1 shows a configuration in which one client 30 is connected to the service provider server 20 via the Internet 10 in order to simplify the description. However, normally, the service provider server 20 A plurality of clients 30 are connected to each other, and the service provider server 20 provides services to the plurality of clients 30.

  The service provider server 20 includes a content server 21, a ticket server 22, and a management server 23. Each of the content server 21, the ticket server 22, and the management server 23 is composed of an information processing apparatus such as a computer, and operates according to a program built therein.

  The content server 21 stores various information to be provided to the user, for example, information for forming movies, music, photos, and the like as contents. In response to a request from the user, the content server 21 stores these in a “capsule file” and provides them to the user. The capsule file is composed of encrypted content and a content identifier. The content identifier is information attached to the content in order to specify the content.

  The ticket server 22 transmits a ticket to the client 30 in response to a request from the client 30. This ticket is composed of data obtained by encoding an encryption key, a user identifier, and a content identifier. An encryption key is information used to decrypt a cipher. The user identifier is information for specifying a client, and is composed of an ID, a password, and system information.

  The system information is information specific to the information processing device that configures the client 30. The system information includes the hardware serial number and version number, the user name input when installing the software, the company name, the software serial number and version number, the name and symbol for identifying the software, and the client 30. At least one of the configuration information of the information processing apparatus being used can be used. These can be acquired from, for example, an operation system (OS) of the client 30 or a BIOS (Basic Input Output System) installed in an information processing device.

  In response to the user registration request from the client 30, the management server 23 issues an ID and password to the user. Further, the management server 23 performs user authentication processing. That is, although details will be described later, in response to a request for confirmation of registration information from the ticket server 22, it is confirmed whether the user identifier from the user is valid, and the result is reported to the ticket server 22.

  The content server 21, the ticket server 22, and the management server 23 are configured to be independently connected to the Internet 10, but may be configured integrally as the service provider server 20.

  The client 30 is composed of an information processing device such as a personal computer owned by the user, and operates according to a program built therein. The client 30 includes a player 31. The player 31 is service execution software for executing content.

  Next, the operation of the service providing system according to Embodiment 1 of the present invention configured as described above will be described with reference to the sequence diagram shown in FIG.

  In order to receive a service from a service provider, the user first connects the client 30 to the management server 23 of the service provider server 20 via the Internet 10 and performs user registration (step S1). In this user registration, the user notifies the management server 23 of his / her name and contact information from the client 30. Upon receiving this notification, the management server 23 determines the ID and password to be given to the user and sends it to the client 30.

  Next, the management server 23 acquires system information specific to the information processing device that configures the client 30 from the connected client 30 (step S2). For example, the player 31 installed in the client 30 can acquire this system information and send it to the management server 23. Alternatively, it may be acquired from the client 30 through the Internet browser of the client 30 using a program language such as CGI (Common Gateway Interface) or ASP (Active Server Pages) on a home page provided by the management server 23.

  The management server 23 associates the user name and contact information obtained from the client 30 in step S1, the ID and password determined in the management server 23, and the system information obtained in step S2 with the user as user information. Store in a built-in memory (not shown). Of this user information, ID, password and system information are used for user authentication as user identifiers. User information stored in the built-in memory is referred to from other devices as necessary. When the above procedure is completed, the client 30 can send and receive data to and from the service provider server 20 via the Internet 10.

  Next, the user connects the client 30 to the content server 21 and sends a service provision request, that is, a content download request. As a result, the content is downloaded from the content server 21 to the client 30 (step S3). This content is encrypted and provided by being stored in a capsule file. Therefore, it cannot be viewed on the client 30 as it is. In order to retrieve content from a capsule file and view it, it is necessary to obtain a ticket containing an encryption key for decryption.

  Next, the user connects the client 30 to the ticket server 22, inputs the ID and password, and sends a ticket request (step S4). In response to this, the ticket server 22 acquires system information from the client 30 (step S5).

  Next, the ticket server 22 sends the ID, password, and system information of the client 30 that has issued the ticket request to the management server 23 as a user identifier, and requests confirmation of registration information (step S6). Upon receiving this request, the management server 23 compares the user identifier received from the client 30 with the user identifier stored in the internal memory at the time of user registration, and checks whether they match.

  Here, when the management server 23 determines that they match, the management server 23 notifies the ticket server 22 of that (registration information matches) (step S7). In response to this notification, the ticket server 22 encodes the ticket and transmits it to the client 30 (step S8).

  On the other hand, if the management server 23 determines that they do not match, the management server 23 notifies the ticket server 22 of that fact (registration information does not match) (step S9). In response to this notification, the ticket server 22 transmits error information to the client 30 (step S10). Therefore, the ticket server 22 does not pass the ticket to the client 30 unless the user identifier received from the client 30 matches the user identifier stored in the internal memory at the time of user registration.

  The client 30 that has received the ticket decodes the ticket. When the content identifier included in the ticket matches the content identifier stored in the capsule file downloaded in step S3 and stored in the client 30, the ticket including the encryption key is passed to the player 31. (Step S11). Next, the player 31 captures the content, decrypts the encryption key included in the ticket by a predetermined method, and reproduces the captured content using the decrypted key (step S12). Thereby, the user can receive a desired service.

  As described above, according to the service providing system according to the first embodiment of the present invention, the system information basically existing in the information processing device is different even in the information processing device of the same model. Is used in addition to information such as an ID and a password that are specifically given for authentication. Therefore, user authentication can be performed more reliably, and impersonation and unauthorized use can be prevented.

  In the first embodiment described above, three pieces of information such as ID, password, and system information are used as the user identifier. However, it is not always necessary to use these three pieces of information, and at least one of these pieces of information is used. It can also be configured to be used as a user identifier.

(Embodiment 2)
The service providing system according to Embodiment 2 of the present invention prevents unauthorized use of content by embedding a user identifier in service execution software and a ticket.

  The configuration of the service providing system according to the second embodiment is the same as the configuration of the service providing system according to the first embodiment already described with reference to FIG.

  The client 30 is the same as that of the first embodiment described above. FIG. 3 is a block diagram showing the configuration of the client 30 in detail. The client 30 includes a player 31, a specific recording area 32, and an output unit 33.

  The player 31 is service execution software for executing content. The player 31 is installed in the client 30 as a dedicated player from the management server 23. The player 31 includes a capsule reproduction application 310, a ticket receiving unit 311, a capsule decoding unit 312 and a content decoding unit 313.

  The capsule reproduction application 310 instructs the capsule decoding unit 312 to start decoding the capsule file. The capsule playback application 310 stores the user identifier in the specific recording area 32 only when the player 31 is installed from the ticket server 22, and stores the user identifier when the player 31 is copied from another client. do not do. Therefore, the user identifier is not stored in the specific recording area 32 when illegal copying is performed.

  The specific recording area corresponds to a specific location of the present invention. As this specific recording area, for example, a registry can be used. Note that the specific recording area is not limited to the registry, and may be another place where the user cannot easily access.

  The ticket receiving unit 311 acquires a ticket from the ticket server 22 in response to a request from the capsule decoding unit 312. The acquired ticket is sent to the capsule decoding unit 312.

  The capsule decoding unit 312 decodes the capsule file in response to an instruction from the capsule reproduction application 310. If the information in the capsule file specifies that the ticket is necessary, the ticket is obtained via the ticket receiving unit 311. Then, the encrypted content compressed by, for example, the MPEG (Motion Picture Expert Group) method is decrypted using the encryption key stored in the ticket, and sent to the content decoding unit 313.

  The content decoding unit 313 is composed of, for example, an MPEG decoder, and decompresses the content compressed by the MPEG method that has been decoded by the capsule decoding unit 312. The decoding expanded by the content decoding unit 313 is sent to the output unit 33.

  The output unit 33 includes a display device such as a CRT display or a liquid crystal display and a speaker, displays video images from the content decoding unit 313 on the display device, and generates sound from the speaker.

  Next, the operation of the service providing system according to Embodiment 2 of the present invention configured as described above will be described with reference to the sequence diagram shown in FIG.

  In order to receive a service from a service provider, the user first connects the client 30 to the management server 23 of the service provider server 20 via the Internet 10 and performs user registration (step S21). In this user registration, the user notifies the management server 23 of his / her name and contact information from the client 30. Upon receiving this notification, the management server 23 determines the ID and password to be given to the user and sends it to the client 30.

  Next, the management server 23 acquires system information specific to the information processing device constituting the client 30 from the connected client 30 (step S22).

  The management server 23 associates the user name and contact information obtained from the client 30 in step S21, the ID and password determined by the management server 23, and the system information obtained in step S22 with the user as user information. Store in internal memory. Of this user information, ID, password and system information are used for user authentication as user identifiers. User information stored in the built-in memory is referred to from other devices as necessary.

  Next, the management server 23 creates the player 31 based on the user information. At this time, a user identifier including the user ID, password, and system information is encrypted and embedded in the player 31 so that the user cannot easily know it. Then, the player 31 in which the encrypted user identifier is embedded is transmitted to the client 30. The client 30 installs the received player 31 at a predetermined location in the own device (step S23). At the time of this installation, the capsule reproduction application 310 registers the encrypted user identifier included in the player 31 in the registry.

  Next, the user connects the client 30 to the content server 21 and sends a service provision request, that is, a content download request. Thereby, the content is downloaded from the content server 21 to the client 30 (step S24). This content is encrypted and provided by being stored in a capsule file. Therefore, it cannot be viewed on the client 30 as it is. In order to retrieve content from a capsule file and view it, it is necessary to obtain a ticket containing an encryption key for decryption.

  Next, the user connects the client 30 to the ticket server 22, inputs the ID and password, and sends a ticket request (step S25). In response to this, the ticket server 22 acquires system information from the client 30 (step S26).

  Next, the ticket server 22 sends the ID, password, and system information of the client 30 that has issued the ticket request as a user identifier to the management server 23, and requests confirmation of registration information (step S27). Upon receiving this request, the management server 23 compares the user identifier received from the client 30 with the user identifier stored in the internal memory at the time of user registration, and checks whether they match.

  Here, when the management server 23 determines that they match, the management server 23 notifies the ticket server 22 of that (registration information matches) (step S28). In response to this notification, the ticket server 22 uses its own clock if the user has already purchased after executing the purchase procedure (not shown) if the user is a new user. After checking the calculated remaining usage time limit and the remaining usage count, and determining that the check result is valid, the user identifier is embedded in the ticket. Then, the ticket in which the user identifier is embedded is encoded and transmitted to the client 30 (step S29).

  On the other hand, if the management server 23 determines that they do not match, the management server 23 notifies the ticket server 22 of that (registration information does not match) (step S30). In response to this notification, the ticket server 22 transmits error information to the client 30 (step S31). Therefore, the ticket server 22 does not pass the ticket to the client 30 unless the user identifier received from the client 30 matches the user identifier stored in the internal memory at the time of user registration.

  The client 30 that has received the ticket decodes the ticket. When the content identifier included in the ticket matches the content identifier stored in the capsule file downloaded in step S3 and stored in the client 30, the ticket including the encryption key is passed to the player 31. (Step S32). Next, the player 31 takes in content from the stored capsule file (step S33).

  Next, the player 31 compares the user identifier included in the ticket, the user identifier encrypted and stored in the player 31, and the user identifier encrypted and stored in the registry. It is confirmed whether the three parties match (step S34). If they match, the encryption key included in the ticket is decrypted by a predetermined method, and the captured content is reproduced using the decrypted key (step S35). Thereby, the user can receive a desired service. On the other hand, if they do not match, the content cannot be reproduced (step S36).

  Next, how the content is prevented from being illegally used in the configuration described above will be described. In the following, it is assumed that an ID and a password are used as a user identifier, and system information is not used.

  In FIG. 5, the first client 301 is registered as a legitimate user and is properly provided with the service, and the second client 302 is downloaded from the first client 301 by the player 31 dedicated to the first client and the first client 301. It shows a state where the capsule file is illegally copied to try to illegally use the content.

  The second client 302 copies the capsule file downloaded by the first client 301 and the first client 301 and the capsule file downloaded by the first client 301 to its own device. In addition, the second client 302 requests issuance of a ticket using the ID and password of the first client 301. In this case, since the ID and password are valid, the second client 302 can receive a ticket issued from the ticket server 22. However, this ticket is for the first client 301.

  However, since the second client 302 has not performed user registration (step S31), player installation (step S23) has not been performed. Therefore, the user identifier is not registered in the registry, and it is determined that there is a mismatch in the confirmation process of the registry in step S34. As a result, even if the second client 302 can receive a ticket, the content cannot be reproduced, and unauthorized use of the content is prevented.

  In FIG. 6, the first client 301 is registered as a legitimate user and is provided with a service, and the second client 302 is legitimately registered as a user, but falsely claims that the client is the first client 301. This is a state in which an issuance request is made to attempt unauthorized use of content.

  Since the second client 302 is legally registered as a user, a second client dedicated player is installed. A user identifier 2 is registered in the registry. Accordingly, since the user identifier is valid, the second client 302 can receive a ticket issued from the ticket server 22.

  The second client 302 can receive a ticket for the first client from the ticket server 22 when requesting a ticket with the ID and password of the first client 301 falsely assuming the first client 301. However, the user identifier 1 of the first client 301 is embedded in the ticket for the first client. Accordingly, it is determined that there is a mismatch in the confirmation process of the registry or the like in step S34. As a result, even if the second client 302 can receive a ticket, the content cannot be reproduced, and unauthorized use of the content is prevented.

  In the above two examples, in the case of a service providing system in which system information is included in the user identifier, no user authentication is received, so no ticket is issued. Accordingly, the steps after step S32 are not executed, and unauthorized use of content is prevented.

  As described above, according to the service providing system according to the second embodiment, it is possible to prevent a third party from receiving an unauthorized service.

  In the service providing system according to the second embodiment, a user identifier including an ID, a password, and system information is stored in each of the ticket, the player, and the registry. It can be configured to use a user identifier storing one of them. In this case, the accuracy of user authentication is slightly reduced, but there is an advantage that the service providing system is simplified.

  In this case, in a configuration in which only system information is used as a user identifier, the system information is already in a specific location on the client and cannot be changed. Therefore, the service provider server must register the user identifier in the client registry. There is no. In this configuration, for example, the player extracts system information and performs authentication by comparing it with a user identifier embedded in the player. Therefore, the player may be configured to generate a user identifier from the system information or generate system information from the user identifier.

  Further, in the service providing system according to the second embodiment, when the three of the user identifier included in the ticket, the user identifier stored in the player, and the user identifier stored in the registry match, Although the downloaded content can be played back, the content can be played back when two of them match. In this case, although the accuracy of user authentication is slightly reduced, there is an advantage that the service providing system can be configured easily.

  According to the present invention, it is possible to provide a service providing system, a service providing method, and a service providing program that can prevent unauthorized use of content.

  Although the embodiments of the present invention have been described in detail above, the present invention is not limited to the above-described embodiments, and changes in a range not departing from the gist of the present invention are also included in the present invention.

FIG. 1 is a diagram showing a configuration of a service providing system according to Embodiments 1 and 2 of the present invention. FIG. 2 is a sequence diagram showing the operation of the service providing system according to Embodiment 1 of the present invention. FIG. 3 is a block diagram showing a configuration of a client used in the service providing system according to Embodiment 2 of the present invention. FIG. 4 is a sequence diagram showing the operation of the service providing system according to Embodiment 2 of the present invention. FIG. 5 is a diagram for explaining a state in which unauthorized use is prevented in the service providing system according to Embodiment 2 of the present invention. FIG. 6 is a diagram for explaining a state in which other unauthorized use is prevented in the service providing system according to Embodiment 2 of the present invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Internet 20 Service provider server 21 Content server 22 Ticket server 23 Management server 30 Client 301 First client 302 Second client 31 Player 32 Specific recording area 33 Output unit 310 Capsule reproduction application 311 Ticket receiving unit 312 Capsule decoding unit 313 Content decoding Part

Claims (29)

A client requesting user registration;
In response to the user registration request from the client, service execution software in which a user identifier to be given to the client is embedded is transmitted to the client, and the user identifier is registered at a specific location of the client. And server
The client provides a service from the service provider server when a user identifier embedded in the service execution software received from the service provider server matches a user identifier registered in the specific location. Receive service provision system. The service providing system according to claim 1,
The client further requests the service provider server for a ticket that is a key for executing the service execution software,
The service provider server further stores the user identifier in the ticket and transmits it to the client in response to the ticket request,
When the client identifier embedded in the service execution software, the user identifier registered in the specific location, and the user identifier stored in the ticket match, the client receives the request from the service provider server. Service provision system that receives service provision. A client that requests user registration and requests a ticket that is a key for executing the service execution software;
In response to the user registration request from the client, service execution software in which a user identifier to be given to the client is embedded is transmitted to the client, and in response to the ticket request, the user identifier is transmitted to the ticket. A service provider server that stores and transmits to the client,
The client is provided with a service from the service provider server when a user identifier embedded in the service execution software received from the service provider server matches a user identifier stored in the ticket. Service provision system. A client that requests user registration and requests a ticket that is a key for executing the service execution software;
In response to the user registration request from the client, the user identifier given to the client is registered at a specific location of the client, and in response to the ticket request, the user identifier is stored in the ticket. A service provider server for transmitting to the client,
A service providing system in which the client is provided with a service from the service provider server when a user identifier registered in the specific location matches a user identifier stored in the ticket. The service providing system according to any one of claims 2 to 4,
The service provider server further stores the user identifier stored when the ticket request from the client is made within the remaining usage time period calculated using the clock of the service provider server. A service providing system for transmitting a ticket to the client. A service providing system according to any one of claims 2 to 5,
The service providing system, wherein the user identifier is at least one of an ID, a password, and system information unique to the information processing device. An identifier registration means for registering a user identifier sent in response to a user registration request in a specific location;
Service execution software receiving means for receiving service execution software embedded with the user identifier sent in response to the user registration request;
Service provision reception in which service provision is received when the user identifier registered at the specific location by the identifier registration means matches the user identifier embedded in the service execution software received by the service execution software reception means. A client comprising means. The client of claim 7, wherein
Ticket receiving means for receiving the ticket storing the user identifier sent in response to a request for a ticket which is a key for executing the service execution software;
The service provision receiving means includes a user identifier embedded in the service execution software, a user identifier registered in the specific location, and a user identifier stored in the ticket received by the ticket receiving means. Clients that receive service if they match. Service execution software receiving means for receiving service execution software embedded with a user identifier sent in response to a user registration request;
Ticket receiving means for receiving a ticket storing the user identifier sent in response to a request for a ticket which is a key for executing the service execution software;
Service provision for receiving service provision when the user identifier embedded in the service execution software received by the service execution software receiving means matches the user identifier stored in the ticket received by the ticket receiving means A client comprising a receiving means. An identifier registration means for registering a user identifier sent in response to a user registration request in a specific location;
Ticket receiving means for receiving a ticket storing the user identifier, which is sent in response to a request for a ticket which is a key for executing service execution software;
Service provision receiving means for providing a service when the user identifier registered at the specific location by the identifier registration means matches the user identifier stored in the ticket received by the ticket receiving means; Client. A client according to any one of claims 7 to 10,
The user identifier is at least one of an ID, a password, and system information unique to the information processing device. In response to the received user registration request, identifier registration means for registering a user identifier to be given to the user registration request source in a specific location of the request source;
A service provider server comprising service execution software transmission means for transmitting service execution software in which the user identifier is embedded to the request source in response to the user registration request. The service provider server according to claim 12, wherein
In response to the received request for a ticket that is a key for executing the service execution software, the service provider server further includes a ticket transmission unit that transmits the ticket storing the user identifier to the request source. . In response to the received user registration request, service execution software transmission means for transmitting service execution software embedded with a user identifier to be given to the user registration request source to the request source;
In response to the received request for a ticket that is a key for executing the service execution software, the service provider includes a ticket transmission unit that transmits the ticket storing the user identifier to the request source. server. In response to the received user registration request, identifier registration means for registering a user identifier to be given to the user registration request source in a specific location of the request source;
In response to the received request for a ticket that is a key for executing the service execution software, the service provider includes a ticket transmission unit that transmits the ticket storing the user identifier to the request source. server. The service provider server according to any one of claims 13 to 15,
The ticket transmission means, when the request for the ticket from the request source is made within the remaining usage time limit calculated using the clock of the service provider server, the ticket transmitting unit stores the ticket storing the user identifier. Service provider server to send to requester. The service provider server according to any one of claims 12 to 16,
The service provider server, wherein the user identifier is at least one of an ID, a password, and system information unique to the information processing device. Connecting a client that receives a service to a service provider server that provides the service;
Requesting user registration from the client to the service provider server;
On the service provider server side, in response to a user registration request from the client, service execution software in which a user identifier to be given to the client is embedded is transmitted to the client, and the user identifier is transmitted to the client. Registering at a specific location,
On the client side, when the user identifier embedded in the service execution software received from the service provider server matches the user identifier registered at the specific location, the service provider server provides the service. And providing a service. The service providing method according to claim 18, comprising:
The client side further requesting the service provider server for a ticket which is a key for executing the service execution software;
On the service provider server side, further, in response to the request for the ticket, storing the user identifier in the ticket and transmitting it to the client;
On the client side, when the three of the user identifier embedded in the service execution software, the user identifier registered in the specific location, and the user identifier stored in the ticket match, the service provider server Receiving a service from a service providing method. Connecting a client that receives a service to a service provider server that provides the service;
Requesting user registration from the client to the service provider server;
On the service provider server side, in response to the user registration request from the client, transmitting service execution software embedded with a user identifier to be given to the client to the client;
Requesting, on the client side, a ticket, which is a key for executing service execution software, from the service provider server;
On the service provider server side, in response to the request for the ticket from the client, storing the user identifier in the ticket and transmitting it to the client;
On the client side, when the user identifier embedded in the service execution software received from the service provider server matches the user identifier stored in the ticket, service is provided from the service provider server. Receiving the service. Connecting a client that receives a service to a service provider server that provides the service;
Requesting user registration from the client to the service provider server;
On the service provider server side, in response to the user registration request from the client, registering a user identifier to be given to the client in a specific location of the client;
Requesting a ticket which is a key for executing the service execution software on the client side;
On the service provider server side, in response to the ticket request, storing the user identifier in the ticket and transmitting it to the client;
Receiving a service from the service provider server when the user identifier registered at the specific location matches the user identifier stored in the ticket on the client side. The service providing method according to any one of claims 19 to 21, comprising:
On the service provider server side, the user identifier is further stored when a ticket request from the client is made within the remaining usage time period calculated using the clock of the service provider server. A service providing method including the step of transmitting the ticket to the client. The service providing method according to any one of claims 18 to 22,
The service providing method, wherein the user identifier is at least one of an ID, a password, and system information unique to the information processing device. Requesting user registration from the service provider server when the local computer is a client that receives a service from the service provider server;
When the own computer is the service provider server, in response to a user registration request from the client, transmitting service execution software in which a user identifier to be given to the client is embedded to the client; Registering a person identifier at a specific location of the client;
When the own computer is the client, the service provider server when the user identifier embedded in the service execution software received from the service provider server matches the user identifier registered in the specific location Service providing program for causing a computer to execute the step of receiving service provision from a computer. A service providing program according to claim 24, wherein
When the own computer is the client, further requesting the service provider server for a ticket which is a key for executing the service execution software;
If the local computer is the service provider server, further, storing the user identifier in the ticket and transmitting it to the client in response to the ticket request;
When the local computer is the client, the user identifier embedded in the service execution software, the user identifier registered in the specific location, and the user identifier stored in the ticket match. A service providing program for causing a computer to execute a step of receiving service provision from a service provider server. Requesting user registration from the service provider server when the local computer is a client that receives a service from the service provider server;
When the own computer is the service provider server, in response to the user registration request from the client, transmitting service execution software embedded with a user identifier to be given to the client to the client;
If the local computer is the client, requesting the service provider server for a ticket that is a key for executing the service execution software;
If the local computer is the service provider server, in response to the ticket request from the client, storing the user identifier in the ticket and transmitting it to the client;
When the own computer is the client, when the user identifier embedded in the service execution software received from the service provider server matches the user identifier stored in the ticket, the service provider server A service providing program for causing a computer to execute the step of receiving service provision. Requesting user registration from the service provider server when the local computer is a client that receives a service from the service provider server;
If the local computer is the service provider server, in response to the user registration request from the client, registering a user identifier to be given to the client at a specific location of the client;
If the local computer is the client, requesting a ticket that is a key for executing the service execution software;
If the local computer is the service provider server, the user identifier is stored in the ticket in response to the ticket request and transmitted to the client;
When the own computer is the client, the computer receives a service provision from the service provider server when the user identifier registered in the specific location matches the user identifier stored in the ticket. Service provision program to be executed. A service providing program according to any one of claims 25 to 27, wherein
When the local computer is the service provider server, and further when the ticket request from the client is made within the remaining usage time limit calculated using the clock of the service provider server, the user identifier A service providing program for causing a computer to execute a step of transmitting the ticket storing the ticket to the client. A service providing program according to any one of claims 24 to 28, wherein
The service providing program, wherein the user identifier is at least one of an ID, a password, and system information unique to the information processing device.

Images