WO2008026617A1 - Système de fourniture de service - Google Patents

Système de fourniture de service Download PDF

Info

Publication number
WO2008026617A1
WO2008026617A1 PCT/JP2007/066718 JP2007066718W WO2008026617A1 WO 2008026617 A1 WO2008026617 A1 WO 2008026617A1 JP 2007066718 W JP2007066718 W JP 2007066718W WO 2008026617 A1 WO2008026617 A1 WO 2008026617A1
Authority
WO
WIPO (PCT)
Prior art keywords
electronic device
transfer
title
friendly
password
Prior art date
Application number
PCT/JP2007/066718
Other languages
English (en)
Japanese (ja)
Inventor
Kohtaro Fukui
Original Assignee
Panasonic Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Panasonic Corporation filed Critical Panasonic Corporation
Publication of WO2008026617A1 publication Critical patent/WO2008026617A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2823—Reporting information sensed by appliance or service execution status of appliance services in a home automation network
    • H04L12/2827—Reporting to a device within the home network; wherein the reception of the information reported automatically triggers the execution of a home appliance functionality

Definitions

  • the present invention relates to a service providing system, an operation method of the service providing system, and the like.
  • the present invention relates to a system in which services are provided to an authenticated electronic device after device authentication of the electronic device is performed.
  • a service providing system using device authentication is already known! /, E.g. (for example, Patent Document 1 and Non-Patent Document 1).
  • device authentication uses an ID unique to an electronic device to confirm that the electronic device is illegal, such as impersonation, and that it is an electronic device. To do.
  • device authentication technology is used for mobile phones, digital TVs, and the like.
  • Patent Document 1 Japanese Patent Laid-Open No. 2002-271248 (for example, paragraph 0020)
  • Non-Patent Document 1 http: / / k— tai. Impress, co. Jp / cda / article / news— toppag e / 18103. Html
  • the device is subject to authentication!
  • the device user uses a device owned by someone else such as an acquaintance or friend
  • the service that can be received by the devices that the device has cannot be received For this reason, in order for other people to learn how to use the service, etc., it is necessary to let other people touch the devices they have, and there are cases where they can not bear trouble and can not stand emotionally. is there.
  • the present invention has been conceived in view of power and the actual situation.
  • the electronic device transmits a device ID when communicating with the server device, and the server device itself has the right to receive service provision to other electronic devices.
  • Send a relocation processing start request which is the start of relocation processing. It is the ID entered on the work screen provided in response to the processing start request and sends the friendly ID that is the public ID of other electronic devices, and the server device performs service based on the reception of the device ID.
  • a friendly ID is received while the device ID and friendly ID that identify the same electronic device are associated with each other, and the work screen is transmitted in response to the transfer processing start request received.
  • the device ID of the electronic device that is the transfer destination of the title associated with the ID is extracted, and the device ID and the device ID of the electronic device that is the transfer source of the title that sent the friendly ID via the transmitted work screen Associating and holding.
  • the electronic device that is the transfer destination of the title receives the title transfer acceptance confirmation screen, and accepts the acceptance permission information input from the user on the title transfer acceptance confirmation screen to the server device.
  • the server device receives the acceptance permission information, and if the information is the information that acceptance is permitted, the service provided to the transfer source electronic device to the transfer destination electronic device I'm going to offer you, I'll do it.
  • the server device when the server device receives the friendly ID received via the transmitted work screen, the server device generates a password, the device ID of the electronic device that is the transfer destination of the title, and the transfer source of the title.
  • the friendly ID may be stored in association with the electronic device, and transmitted to the electronic device that transmitted the friendly ID, and received by the electronic device.
  • the service provided to the electronic device from which the title is transferred is transferred to the electronic device to which the title is transferred and provided. To do The effect that it becomes possible is demonstrated.
  • FIG. 8 is a functional block diagram of the service providing system according to the first embodiment.
  • FIG. 18 is a flowchart of processing in the server device 802.
  • FIG. 19 is a flowchart of processing in the server device 802.
  • FIG. 21 Sequence diagram of the process in which services originally provided to electronic device 1 are provided to electronic device 2.
  • FIG. 22 is a functional block diagram of the service providing system according to the second embodiment.
  • FIG. 23 is a flowchart of processing of the electronic device.
  • FIG. 25 is a flowchart of processing of the server device.
  • FIG. 26 is an overall sequence diagram of processing in embodiment 2.
  • FIG. 27 is a functional block diagram of the service providing system according to the third embodiment.
  • FIG. 28 An example of a table managed by the relocation relation holding unit
  • FIG. 29 is an overall sequence diagram of processing in the third embodiment.
  • FIG. 1 describes an overview of a service providing system according to the present invention.
  • the service providing system includes a server device 101 and a plurality of electronic devices 102 and 103.
  • the server apparatus 101 and the plurality of electronic devices 102 and 103 are connected by a communication network typified by the Internet or the like, and can perform one-way or two-way communication. Examples of electronic devices include mobile phones, digital television receivers, portable game devices, and home appliances.
  • the server device is realized using, for example, a computer.
  • the electronic device ID 104 is added to the request.
  • the electronic device ID 104 is an identifier that uniquely identifies the electronic device 102.
  • the server device 101 receives a service transmitted from the electronic device 102.
  • the validity of the electronic device ID 104 added to the request for the service is verified, and the electronic device 102 is authenticated using the verification result. For example, it is verified that the electronic device ID 104 is composed of a combination of valid numbers. If the authentication of the electronic device ID 104 is successful in the server device 101, the service 105 for the electronic device 102 is provided to the electronic device 102 from the server device 101 or from another server device via the server device 101.
  • the service 105 includes, for example, provision of a portal screen defined for the electronic device ID 102. Content download and viewing are also included in Service 105. If the content is charged, the electronic device ID 104 is used for charging.
  • the electronic device ID 106 is added to the request or the like. If the electronic device 102 and the electronic device 103 are different, the electronic device ID 106 and the electronic device ID 104 are different.
  • the server device 101 verifies the validity of the electronic device ID 106 added to the service request transmitted from the electronic device 103, and authenticates the electronic device 103 using the verification result. When the authentication is completed, a service 107 for the electronic device 103 is provided to the electronic device 103 from the server device 101 or from another server device or the like via the server device 101.
  • the electronic device is authenticated by the server device using the electronic device ID. Therefore, for example, even if the user power of the electronic device 102 is used, only the service provided to the electronic device 103 can be received, and the service provided to the electronic device 102 can be received. There were problems such as not being.
  • the present invention solves this problem and the like as follows.
  • FIG. 2 illustrates a first step group in the present invention.
  • a server apparatus 201 and electronic devices 202 and 203.
  • the user of the electronic device 202 desires to receive the service provided to the electronic device 202 from the electronic device 203 as well.
  • a transfer process start request is transmitted from the electronic device 202 to the server device 201.
  • the transfer processing start request is a request to start processing for providing a service provided to the electronic device 202 to other electronic devices.
  • the process of transferring the authority of the electronic device 202 to another electronic device is started.
  • a confirmation screen is transmitted from the server apparatus 201 to the electronic device 202 in response to the transfer processing start request.
  • the confirmation screen is a screen that confirms whether or not the transfer process can be started.
  • confirmation information as the step (3) is transmitted from the electronic device 202 to the server apparatus 201.
  • the server device 201 checks the confirmation information. For example, it is checked whether the service of starting the transfer process is one of the services provided to the electronic device 202.
  • a friendly ID input screen is transmitted from the server apparatus 201 to the electronic device 202 as step (5).
  • the friendly ID here is an identifier that has been made public to identify electronic devices. Since the electronic device ID is an identifier for authenticating the electronic device, its structure is generally complicated and cannot be easily stored by humans. Also, if the electronic device ID is leaked, problems such as impersonation occur. Therefore, in order for a user to specify an electronic device, an identifier that can be easily stored is used. This identifier is called a friendly ID. For example, a friendly ID is equivalent to a fully qualified domain name (FQDN) on the Internet.
  • FQDN fully qualified domain name
  • the service provided to the electronic device 202 is the friendly ID of another electronic device to be provided. That is, the friendly ID of the electronic device to which the authority of the electronic device 202 is transferred.
  • the user of the electronic device 202 desires to receive the service provided to the electronic device 202 even with the electronic device 203, and the friendly ID of the electronic device 203 is cde. Enter cde as the step.
  • the server apparatus 201 receives the friendly ID input on the friendly ID input screen transmitted to the electronic device 202 and checks the friendly ID. For example, if there is an electronic device with that friendly ID and if the electronic device to which the user wants to transfer the service provided by the electronic device 202 has been specified (for example, If it is specified at the time of contract for the title to receive service with the electronic device 202, or if it is specified by entering a friendly ID on another screen, etc.), it checks whether it matches any of them. . Check succeeded Then, as step (8), for example, abc, which is the friendly ID of the electronic device 202, is added to the device usage permission list having cde as the friendly ID.
  • abc which is the friendly ID of the electronic device 202
  • the server device 201 issues a password to the electronic device 202 as step (9).
  • This password is input to the electronic device 203 when, for example, the electronic device 202 transfers the right to receive the service provided to the electronic device 203 and receives the service provided originally to the electronic device 202. Is.
  • the server device 201 it is confirmed by the server device 201 that the user who performed the transfer process in the electronic device 202 is using the electronic device 203, and the service originally provided to the electronic device 202 is transferred to the electronic device 202. It can be confirmed that there is no problem even if it is provided to 203.
  • FIG. 3 and 4 are diagrams for explaining the device use permission list.
  • the device usage permission list is assigned to an entry managed by the server device for each electronic device. Such an entry is secured in the storage area of the server device.
  • Figure 3 illustrates the entries managed by the server device for each electronic device.
  • An entry 301 indicates an entry corresponding to the electronic device 202, and holds the electronic device ID and friendly ID of the electronic device 202.
  • information on the user of the electronic device 202, a charging method, an upper limit of charging, an identifier of a service that can be provided to the electronic device 202, and the like are held.
  • the entry 302 indicates an entry corresponding to the electronic device 203.
  • step (8) abc is added to the device usage permission list with friendly ID cde, so the device usage permission list is given to entry 302, which is the entry of electronic device 203, and the device Abc is stored in the permission list.
  • FIG. 4 shows an example of a state in which the device usage permission list 303 holding abc is assigned to the entry 302.
  • the device use permission list 303 includes abc as a friendly ID, and this device use permission list is given by associating it with the entry 302, so that the service capability originally provided to the electronic device 202 is provided. S, it is expressed that the transfer processing that should be provided to the electronic device 203 has been performed.
  • the device usage permission list 303 holds information such as the password issued in step (9) (for example, “secret” as shown) and acceptance. “Acceptable” means that the user power of the electronic device 203 is provided to the electronic device 203 with the service originally provided to the electronic device 202. Indicates whether or not the force allowed to be
  • FIG. 5 shows a step group (second step group) for allowing the user of the electronic device 203 to be provided with the service provided to the electronic device 202.
  • a request for the transfer request electronic device list is transmitted from the electronic device 203 to the server device 201.
  • the transfer request electronic device list means a list of electronic devices that have been processed to transfer the right to receive service to the electronic device 203. This list can be generated by referring to the device usage permission list given to the entry 302. In the case of FIG. 4, since only the electronic device 202 has performed the service provision transfer process, the list includes only the abc of the friendly ID.
  • this list is transmitted to the electronic device 203.
  • the electronic device 203 sends permission for acceptance of abc.
  • the device usage permission is obtained as step (4). Change the Acceptable value in Listing 303 from NO to YES. As a result, the data structure illustrated in FIG. 4 is changed as shown in FIG. That is, the acceptance value in the device usage permission list 303 is YES.
  • FIG. 7 shows a processing step group (third step group) for receiving a service provided to the electronic device 202 using the electronic device 203.
  • a transfer processing request is transmitted from the electronic device 203 to the server apparatus 201.
  • the transfer processing request is a request for using the electronic device 203 to receive a service originally provided to another electronic device.
  • the server apparatus 201 transmits a friendly ID input screen.
  • the friendly ID input screen here is a screen for entering a friendly ID that identifies other electronic devices for which the service is originally provided.
  • abc is input as the friendly ID of the electronic device 202 (step (3)).
  • a password input screen is transmitted from the server apparatus 201.
  • This password entry screen is a screen for confirming whether or not the user who performed the transfer process of the service using the electronic device 202 is in front of the electronic device 203.
  • step (5) the secret shown in Fig. 4 is entered.
  • step (6) in the server device 201, (3) Check the friendly ID entered in step (5) and the password entered in step (5). If this check is successful, as step (7), the server apparatus 201 provides the electronic device 203 with a service originally provided to the electronic device 202.
  • the electronic device 203 With the steps of the first, second, and third steps, it is possible to provide the electronic device 203 with a service that is originally provided to the electronic device 202.
  • the service used by the electronic device 202 can be used using the electronic device 203.
  • the questioner can receive guidance on how to use the service.
  • the elderly person or the like was receiving the service at the electronic device 202. For example, he / she visited the home of the child of the person, and the electronic device 203 and the electronic device 202 You can receive the continuation of the service that you received at, and you will receive input on behalf of your child.
  • Embodiment 1 in a service providing system including an electronic device and a server device, the electronic device transmits a device ID when communicating with the server device, and receives the service provided by the server device. This is an ID that is input to the work screen that is sent in response to the transfer process start request, and is transmitted to the other electronic device.
  • the server device sends a friendly ID that is a public ID of the server, and the server device provides a service based on the reception of the device ID, holds the device ID that identifies the same electronic device in association with the friendly ID, and performs a transfer process.
  • FIG. 8 illustrates a functional block diagram of the service providing system according to the first embodiment.
  • the service providing system includes an electronic device 801 and a server device 802. Although only one electronic device is illustrated in FIG. 8, a plurality of electronic devices can be connected to the server device 802.
  • the electronic device 801 includes a device ID transmission unit 803, a transfer process start request transmission unit 804, and a friendly ID transmission unit 805.
  • “Device ID transmission unit” 803 holds the device ID and transmits the device ID when communicating with server device 802.
  • the “device ID” is an ID that is disclosed only to the server apparatus 802 in order to receive authentication of the right to receive services via the server apparatus 802.
  • Public only to the server device 802 means that it is kept secret among the operators of the server device 802 and cannot be made public.
  • the device ID transmission unit 803 preferably stores the device ID in a non-volatile memory such as a flash memory, and particularly preferably holds it in the tamper resistant area.
  • the device ID is an ID that can be associated with the Friendship ID described below. This association is managed mainly by the server device.
  • the device ID transmission unit 803 transmits a device ID when communicating with the server device 802.
  • a packet of a lower layer is generated for a packet performed in communication of an upper layer (for example, an application layer) of a communication layer (for example, a physical layer) handled by the device ID transmission unit 803, and the header of the packet is generated.
  • Protocol processing at the lower layer is performed, such as adding a device ID to the device.
  • Figure 9 illustrates this.
  • the device ID transmitter When upper layer communication data is received by the device ID transmitter, the device ID transmitter generates a lower layer packet and adds the device ID to the header of the packet.
  • the device ID here is held by the device ID transmission unit and can also be an identifier for identifying the electronic device 801.
  • “Transfer process start request transmission unit” 804 transmits a transfer process start request to server apparatus 802.
  • the “transfer process start request” is information indicating a request to start a process for transferring the right to receive the service to itself (electronic device 801) S, server device 802, etc. to another electronic device. is there. That is, the transfer processing start request is sent from the electronic device 801 to the service.
  • This information represents a request for starting a process for allowing a service received from the device 802 to be received by another electronic device. Information representing such a request can be expressed using, for example, Hyper Text Transfer Protocol.
  • the electronic device 801 is capable of performing processing to allow the service received from the server device 802 to be received by another electronic device.
  • FIG. 10 shows an example of a screen for transmitting a transfer process start request.
  • a button 1002 indicating “start of transfer processing” is displayed.
  • a transfer processing start request is transmitted from the electronic device 801 to the server device 802. Further, using voice recognition or the like, an effect similar to that of pressing a button may be brought about. Since the transfer processing start request is transmitted via the device ID transmission unit 803, the device ID of the electronic device 801 is added to the packet including the transfer processing start request. As a result, the server apparatus 802 can know from which electronic device the request is transmitted.
  • “Friendly ID transmission unit” 805 transmits to the server device 802 friendly IDs of other electronic devices input by the user on the work screen.
  • a “friendly ID” is a public ID (public identifier) that identifies itself.
  • Shelf means the electronic device 801.
  • Public ID means not kept secret.
  • the friendly ID is described with alphabets and numbers like the FQDN of the electronic device 801, and an existing word or concept can be expressed by using such alphabets and numbers. This makes it easier for humans to remember. In addition, input errors can be reduced.
  • the “work screen” is a screen provided by the server device 802 in response to the transfer processing start request transmitted by the transfer processing start request transmission unit 804, for transferring the title provided from the server device 802. It is a screen.
  • the title provided by server device 802 is This means the title that allows the service provided by the server device 802 to be received.
  • the work screen can be described in, for example, HyperText Mark-up Language.
  • the work screen format is stored in the hard disk memory or the like in association with the screen identifier in the electronic device 801, and transmission of the work screen is realized by transmitting the screen identifier from the server device 802. You can also.
  • the friendly ID input to the work screen is a friendly ID of another electronic device, and it is assumed that it is desired to transfer the title provided from the server apparatus 802 to the electronic device.
  • the device ID transmission unit 803 From the description of the device ID transmission unit 803, when the friendly ID transmission unit 805 transmits a friendly ID, the device ID transmission unit 803 performs protocol processing and the like in a lower layer of the transmission, and the friendly ID transmission unit 803 transmits the friendly ID.
  • the device ID is added to the header of the packet that includes the ID. With this added device ID, it is possible to lose the power of sending the friendly ID by any electronic device.
  • FIG. 11 shows an example of a work screen.
  • a field 1102 for inputting a friendly ID
  • the user of the electronic device 801 inputs a friendly ID of another electronic device using a keyboard or voice recognition means.
  • an OK button 1103 is pressed.
  • the friendly ID transmission unit 805 reads the friendly ID input in the field 1102 and temporarily stores it in a memory or the like, and stores a predetermined protocol (for example, HyperText Transfer Protocol). To send. For example, information such as a friendly ID to be transmitted is passed to the application interface of the software module that implements the device ID transmission unit 803.
  • a predetermined protocol for example, HyperText Transfer Protocol
  • step S1204 the work screen is displayed on the display unit, and in step S1205, the process waits until a friendly ID is input.
  • the friendly ID is entered in the column 1102, and the WAI is written until an electrical signal indicating that the OK button 1103 is pressed is detected. If it is detected that the friendly ID has been input, the process proceeds to step S1206, and the input friendly ID is transmitted.
  • the server device 802 includes a service providing unit 806, an ID association holding unit 807, a work screen transmission unit 808, and a transfer relationship holding unit 809.
  • Service providing unit 806 provides a service based on the authentication of the received device ID! .
  • it can be realized by the following software module. That is, using a software module that receives a packet including information transmitted from an electronic device, the device ID added to the header of the packet is acquired. Next, authentication is performed by verifying whether the acquired device ID is valid. For example, it is verified whether it matches one of the device IDs stored in the server device in advance. If the authentication is successful, the electronic device having the device ID provides the service to the electronic device, assuming that it has the right to receive services associated with the device ID.
  • FIG. 13 shows an example in which the service providing unit 1301 manages a table 1302 in which an electronic device ID and a service identifier are associated with each other.
  • the table 1302 is managed in a hard disk device included in the server device using a database management system or the like or an ISAM file.
  • an electronic device having an electronic device ID of device ID 1 should be provided with a service identified by a service identifier such as service 113 or service 1056, or such a service can be provided.
  • a service identifier such as service 113 or service 1056
  • FIG. 14 shows an example of a service structure.
  • the electronic device When communication with the server device is started, for example, when the electronic device is turned on, the electronic device requests a portal screen including a list of services having the right to receive provision (such portals).
  • the provision of screens is also one of the services! /, Even! /,).
  • the electronic device can transition to a screen of another service having the right to receive provision.
  • a screen of another service having the right to receive provision.
  • One such service can also include the initiation of relocation processing.
  • ID association holding unit 807 associates and holds a device ID that identifies the same electronic device and a friendly ID. “Identify the same electronic device” means that the electronic device identified by the device ID held in association with the electronic device identified by the friendly ID is the same electronic device. Means that. Such association can be realized using a table, for example.
  • FIG. 15 shows a table in which the ID association holding unit 1501 associates friendly IDs with device IDs.
  • the tape and tape 1502 can be managed on the hard disk device provided in the server device using a database management system, an I SAM file, or the like.
  • the friendly ID abc is associated with the device ID 04 0167B.
  • the electronic device identified by abc and the electronic device identified by 04 0167B are the same. (For example, the device ID 040167B and the device ID illustrated in FIG. 13 may be the same)
  • “Work screen transmission unit” 808 transmits a work screen in response to the received transfer processing start request. For example, when a transfer process start request is received from an electronic device, an HTML description of the work screen is read from a hard disk device or the like, temporarily stored in memory, and directed to the electronic device that transmitted the transfer process start request. Send.
  • the “relocation relation holding unit” 809 uses the ID relation holding unit 80 7 to transmit the device ID of the electronic device that is the transfer destination of the title associated with the friendly ID received via the transmitted work screen.
  • the extracted device ID and (C) the device ID of the electronic device that is the transfer source of the title that sent the friendly ID via the work screen are stored in association with each other. For example, it is assumed that a friendly ID abc is received from an electronic device having 284729R as an electronic device ID via a work screen. At this time, the electronic device identified by the friendly ID abc becomes the transfer destination of the title. Also, referring to the association held in the ID association holding unit 807, the device ID 040167B associated with abc is extracted from abc.
  • the electronic device identified by 284729R is used as the transfer source of the title, and 040 167B as the transfer destination of the title is associated and held.
  • the server device 802 manages that the electronic device identified by 284729R should be provided to the electronic device identified by the service power 040167B originally provided.
  • FIG. 16 illustrates processing in the transfer relationship holding unit 809.
  • a packet 1601 including friendly D for example, abc
  • the packet 1601 is used to identify the electronic device to which the title is transferred.
  • the device ID ′ 1602 (for example, 040167B) associated with the friendly ID ′ 1602 is retrieved with reference to the ID-related holding unit. Accordingly, the device ID 1604 included in the packet 1601 is used as the transfer source of the title, and the extracted device ID '1603 is associated as the device ID as the transfer destination of the title.
  • the association held in the transfer relationship holding unit 809 can be realized using a table or the like.
  • the transfer relationship holding unit 1701 includes a table including an electronic device ID column of the transfer source electronic device and an electronic device ID column of the transfer destination electronic device. to manage.
  • FIG. 17 for example, it is expressed that the service provided to the electronic device identified by the device ID “ID1234” is provided to the electronic device identified by the device ID “ID9876”.
  • FIG. 18 and FIG. 19 exemplify flowcharts for explaining the processing flow in the server apparatus 802.
  • FIG. 18 describes the flow of processing for providing a service.
  • the device ID is received. That is, a service request packet transmitted from an electronic device is received, and a device ID attached to the packet is acquired.
  • the acquired device ID is authenticated. For example, a process for determining whether or not the device ID is stored in advance in the table of the server device 802 is performed.
  • step S 1803 it is determined whether authentication is OK. If it is OK, the process proceeds to step S1804, and the service is provided to the electronic device assuming that the electronic device has the right to receive the service. If the authentication is not OK, The process proceeds to step S 1805 to notify an error or the like.
  • FIG. 19 illustrates a processing flow from reception of the transfer processing start request to associating the device ID of the electronic device that is the transfer source of the title with the device ID of the electronic device that is the transfer destination of the title.
  • step S 1901 wait until a transfer processing start request is received.
  • the electronic device 801 waits until an electrical signal indicating reception of a transfer processing start request packet is detected.
  • the work screen is transmitted in step S 1902.
  • the work screen transmission unit 808 reads a description in HTML of the work screen from a hard disk device or the like, temporarily stores it in a memory, and sends it to an electronic device. This is realized by passing it to the application interface of the software module for communication.
  • step S 1903 the process waits until a friendly ID is received. For example, it waits until an electrical signal indicating reception of a friendly ID packet is detected. If the friendly ID is received, the process proceeds to step S1904, and the device ID associated with the friendly ID is taken out from the ID related holding unit 807. In step S 1905, the extracted device ID is stored in association with the device ID that is the transfer source of the title.
  • FIG. 20 illustrates a conceptual diagram of a packet including information indicating acceptance of the title.
  • the title transfer has been performed with the electronic device having the device ID “device” as the transfer source of the title and the electronic device having the device ID “device ID '” as the transfer destination of the title. .
  • information that allows the acceptance of the title is transmitted from the electronic device having the device ID ′ to the server device.
  • FIG. 20 illustrates a packet including information indicating acceptance of the title in such a case.
  • Information such as a packet indicating acceptance of the title 2001 has the device ID 'in the header portion 2002, and the payload etc. includes information that allows the acceptance of the title with the device ID as the transfer source. .
  • server apparatus 802 When server apparatus 802 receives the packet as shown in FIG. 20, in order to know which electronic device accepts the title, it reads part 2002, obtains device ID ′, and obtains device D. Detects that the relocation is permitted. As to which electronic device is the transfer source, for example, the payload part of the packet 2001 is read to obtain the friendly ID of the electronic device that is the transfer source, and referring to the ID-related holding unit 807, Get the device ID. If the device ID and device ID ′ are held in association with the transfer relationship holding unit 809, the table is managed by the service providing unit and is provided to the electronic device originally identified by the device ID. Processing is performed so as to provide the service to the electronic device identified by the device ID '.
  • the information stored in the transfer relationship holding unit 809 is read, and an electronic circuit that generates an electrical signal that transitions from High to Low is configured. With a transition from High to Low, the right It can be realized by an electronic circuit that detects the transfer of the original, reads the information held in the transfer relationship holding unit 809, etc., and transfers the provision of the service.
  • FIG. 21 shows that when there are two electronic devices, that is, electronic device 1 and electronic device 2, and they can communicate with the server device, a transfer process start request is transmitted from electronic device 1. Sequence for explaining the flow of processing in which the service provided to the electronic device 1 is provided to the electronic device 2 from the electronic device 2 as shown in FIG. FIG.
  • step S 2101 a transfer processing start request is transmitted from electronic device 1 to the server device.
  • step S2102 a work screen is transmitted from the server device to the electronic device 1 in response to the transfer processing start request.
  • the friendly ID of the electronic device 2 is input on the work screen, and the friendly ID is transmitted from the electronic device 1 to the server device in step S2103.
  • the server device stores that the service that should originally be provided to the electronic device 1 should be provided to the electronic device 2.
  • step S2104 a packet indicating acceptance of transfer of title as exemplified in FIG. 20 is transmitted from the electronic device 2 to the server device, and the server device receives data such as FIG. 4 and FIG.
  • the server device receives data such as FIG. 4 and FIG.
  • services that should originally be provided to electronic device 1 are provided to electronic device 2.
  • the packet received from the electronic device 2 is disguised as received from the electronic device 1 by rewriting the header, etc., and is provided to the electronic device 1 when transmitting the packet.
  • the server apparatus includes a rewriting means for rewriting the header of the packet received from the electronic device 2 in the packet receiving unit, and the device ID of the electronic device 1 stored in the packet header or the like is assigned to the device of the electronic device 2. Second rewriting means to rewrite to ID Comes to be equipped in the packet transmitter.
  • the electronic device 2 can be used to inquire about how to use the service on the electronic device 1. Also, elderly people were receiving services with electronic device 1, but for reasons such as losing the input method, they visited their children's children's homes, and electronic devices 2 You can receive the continuation of the service you received in step 1, and you can have the child continue to input the continuation of input.
  • an electronic device that is a transfer destination of a title receives a title transfer acceptance confirmation screen, and receives information on acceptance permission / inhibition input from the user on the title transfer acceptance confirmation screen.
  • the server device receives the acceptance permission information and the information is information that the acceptance is permitted, the server device sends the information to the electronic device that is the transfer destination. Describes the service provision system that provides the services provided.
  • FIG. 22 illustrates a functional block diagram of the service providing system according to the second embodiment.
  • the service providing system includes the same electronic device 2201 and server device 2202 as those in the first embodiment. In FIG. 22, only one electronic device is illustrated, but a plurality of electronic devices can be connected to the server apparatus 2202 as in the first embodiment.
  • the electronic device 2201 includes a title transfer acceptance confirmation screen receiving unit 2203 and an acceptance permission / rejection transmitting unit 2204.
  • the electronic device 2201 includes a device ID transmission unit, a transfer process start request transmission unit, and a friendly ID transmission unit as in the first embodiment, but these are not shown.
  • “Right title transfer acceptance confirmation screen receiving unit” 2203 receives the title transfer acceptance confirmation screen transmitted from the server device 2202.
  • the “title transfer acceptance confirmation screen” refers to the electronic device that is the transfer destination of the title held by the transfer relationship holding unit of the server device 2202, and the electronic device that is the transfer source of the title is This is a screen for notifying the user and entering permission / denial of the title.
  • “Acceptance Acceptance Sending / Receiving Unit” 2204 sends to the server apparatus 2202 acceptance acceptance / rejection information in which the user input is also input to the received title transfer acceptance confirmation screen. Acceptance permission / inhibition information power This information indicates the above-mentioned “permission permission / inhibition of title”.
  • the friendly ID of the electronic device from which the title is transferred For example, on the screen for confirming the transfer of title, the friendly ID of the electronic device from which the title is transferred, the name of the user, and a photo of the user's face are displayed.
  • the permission of acceptance of the title is entered using a check box displayed on the title transfer acceptance confirmation screen, and the acceptance permission transmission unit 2204 receives the input result from the server device 2 202 Send to.
  • FIG. 23 illustrates a flowchart for explaining the flow of processing of the electronic device 2201.
  • step S 2301 wait until the title transfer acceptance confirmation screen is received.
  • the title transfer acceptance confirmation screen may be displayed every time a friendly ID is transmitted from another electronic device to the server device 2202 for making the electronic device 2201 the transfer destination of the title.
  • a request for a transfer of ownership transfer confirmation screen may be transmitted from the electronic device 2202 to the server device 2201 and received as a reply.
  • transmission of the title transfer acceptance confirmation screen may be one of the services provided to the electronic device 2201.
  • step S 2302 a title transfer acceptance confirmation screen is displayed on the display unit.
  • step S 2303 the process waits until acceptance permission / denial information is input. When input is made, the process proceeds to step S 2304, and acceptance permission / denial information is transmitted to server apparatus 2202.
  • FIG. 24 shows an example of the title transfer acceptance confirmation screen.
  • the title transfer acceptance confirmation screen 2401 displays fgh, jkl, etc. as the friendly ID of the electronic device whose title is transferred to the electronic device on which it is displayed.
  • Select 02 and 2403 specify an electronic device that can accept the transfer of title, and press the send button 2404.
  • acceptance permission / rejection transmission unit 2204 generates acceptance permission / rejection information and transmits it.
  • Server apparatus 2202 includes title transfer acceptance confirmation screen transmitter 2205, acceptance permission / refusal information receiver 2206, and transfer destination service provider 2207.
  • the server apparatus 2202 includes a service providing unit, an ID related holding unit, a work screen transmitting unit, and a transfer relationship holding unit as in the first embodiment, but these are omitted (particularly, Service provider and transfer The destination service provider 2207 becomes one part! /, Even! /,).
  • “Transfer of title transfer acceptance confirmation screen” 2205 transmits the title transfer acceptance confirmation screen based on the device ID of the electronic device that is the transfer destination of the title held in the transfer relationship holding unit! To do.
  • the transfer relationship holding unit obtains the device ID (that is, the transfer source of the title) of the electronic device associated with the electronic device 2201 as the transfer destination of the title, and whether or not the transfer of the title is permitted. Is configured so that the screen illustrated in FIG. 24 can be displayed using HTML or the like, and the configured screen is transmitted.
  • “Acceptance acceptance / rejection information receiving unit” 2306 receives acceptance acceptance / rejection information returned in response to transmission of the title transfer acceptance confirmation screen.
  • the check box input on the screen 2401 receives the input status to the radio buttons 2402 and 2403.
  • "Relocation destination service providing unit" 2307 if the acceptance permission / rejection information received by acceptance permission / rejection information receiving unit 2306 is information that is acceptable, that is, is permitted, The service to be provided based on the device ID of the electronic device from which the title is transferred is provided to the electronic device 2201 to which the title is transferred. For example, if a check is entered in the check box 2402 on the screen 2401 and information indicating that acceptance from fgh is permitted is received, the service providing unit will originally provide the electronic device having fgh as a friendly ID. Transfers the provided service to the electronic device 2201.
  • FIG. 25 illustrates a flowchart for explaining the flow of processing of the server apparatus 2202.
  • step 2501 a title transfer acceptance confirmation screen is transmitted to the electronic device.
  • step S2502 the process waits until reception acceptance / rejection information is received. If received, the process proceeds to step S2503, and the transfer destination service providing unit provides the electronic device 2201 with a service that should originally be provided to another electronic device.
  • FIG. 26 illustrates an overall sequence diagram of processing in the second embodiment. Steps S26 01 and S2603 up to step S2603 are the same as those described in steps S2101 and S2103 of FIG.
  • step S 2604 a title transfer acceptance confirmation screen is transmitted from the server device to electronic device 2.
  • step S2605 refer to the title transfer acceptance confirmation screen
  • the acceptance permission / prohibition information input through the above is transmitted from the electronic device 2 to the server device.
  • the service originally provided to the electronic device 1 is provided to the electronic device 2 as in step S2105 of FIG.
  • the present embodiment it is possible to transfer and provide a service in accordance with the intention of the person who has the transfer destination electronic device. For example, it is possible to prevent the provision of adult information services such as pornographic images and sex store information to electronic devices that may be viewed by minors.
  • adult information services such as pornographic images and sex store information to electronic devices that may be viewed by minors.
  • Embodiment 3 when the server device receives the friendly ID received via the transmitted work screen, the server device generates a password, and the device ID of the electronic device that is the transfer destination of the title and the transfer source of the title A service providing system that stores the information in association with the device ID of the electronic device to be transmitted, transmits the friendly ID to the electronic device that has transmitted, and is received by the electronic device will be described.
  • FIG. 27 illustrates a functional block diagram of the service providing system according to the third embodiment.
  • the service providing system is composed of the same server device 2701 and electronic device 2 702 as in the first or second embodiment. Although only one electronic device is illustrated in FIG. 27, a plurality of electronic devices can be connected to the server apparatus 2701 as in the first or second embodiment.
  • the server device 2701 includes a transfer relationship holding unit 2703, a password association unit 2704, and a password transmission unit 2705.
  • the server device further includes a service providing unit, an ID-related holding unit, and a work screen transmission unit, as in the first embodiment, but these drawings are omitted.
  • you may have a title transfer acceptance confirmation screen transmission part, an acceptance permission / refusal information reception part, and a transfer destination service provision part.
  • the "password association part" 2704 sends the transfer relation holding part 2703 to the transfer destination device ID that is the device ID of the electronic device that is the transfer destination of the title and the device of the electronic device that is the transfer source of the title. If the transfer source device ID, which is an ID, is stored in association with each other, a password required to start providing services to the electronic device to which the authority is transferred is generated, and the transfer destination device ID is generated. Associate with. For example, the transfer relationship holding unit is set so that the device ID of the electronic device as the transfer destination is ID 12 34 and the device ID of the electronic device as the transfer source is ID9876. If a device ID is stored in association with the device, a password is issued for the association and further associated.
  • FIG. 28 illustrates a table 2802 managed by the transfer relationship holding unit 2801 in the third embodiment. This corresponds to FIG. 17 described in the first embodiment. However, in FIG. 17, the column of passwords is a force not shown, and the resultant force is shown in FIG.
  • Password transmission unit 2705 transmits the password to the electronic device identified by the transfer source device ID.
  • the “password” is a password generated by the password association unit 2704 and associated with the transfer relationship holding unit 2703.
  • passwordOl is transmitted to the electronic device identified by ID9876
  • password02 is transmitted to the electronic device identified by ID7654. This transmission may be sent to the electronic device immediately after the friendly ID is entered via the work screen, or may be sent later by e-mail addressed to the user of the electronic device. It may be.
  • the electronic device 2702 includes a password receiving unit 2706.
  • the electronic device 2702 includes the same device ID transmission unit, transfer processing start request transmission unit, and friendly ID transmission unit as in the first embodiment, but these are not shown. Further, as in the second embodiment, it may have a title transfer acceptance confirmation screen reception unit and an acceptance permission / rejection transmission unit.
  • “Password receiver” 2706 receives a password transmitted from server apparatus 2701. For example, a password that is returned immediately after the friendly ID is transmitted via the work screen is received. Alternatively, a password transmitted by means such as e-mail is received. The received password is displayed on the display unit or printed on a printer connected to the electronic device 2701. It can also be transferred to a PDA (Personal Digital Assistance) connected to the electronic device 2701!
  • PDA Personal Digital Assistance
  • FIG. 29 illustrates an overall sequence diagram of processing in the third embodiment. Steps S2901 and S2903 up to step S2903 are the same as those described as steps S2101 and S2103 of FIG. In the present embodiment, it is shown that after a friend ID 'is transmitted from the electronic device 1 to the server device, a pass word is generated by the server device and returned to the electronic device 1 in step S2904.
  • the electronic device 2 receives the service originally provided to the electronic device 1.
  • the password in step S2904 is transmitted to the server apparatus.
  • the server device determines the suitability of the password, and if so, provides the service originally provided to the electronic device 1 to the electronic device 2 in step S2906.
  • the acceptance of the transfer of title and the transmission of the password can be performed in several steps as illustrated in FIG. 7 as illustrated in FIG. That is, first, a transfer processing request is transmitted from the electronic device 2 to the server device.
  • the server device transmits a list of electronic devices that have transmitted the friendly ID with electronic device 2 as the transfer destination of the title.
  • the list of electronic devices is a list of friendly IDs of the electronic devices.
  • the list may include acceptance permission / rejection information transmitted from the electronic device 2 to the server device for each electronic device.
  • the user of the electronic device 2 selects one friendly ID of the electronic device from the list, and transmits the selected friendly ID to the server device.
  • the part that performs this transmission can be called the transfer-source friendly ID transmission part.
  • the server device checks the selected friendly ID. It is also possible to check whether the friendly ID of the electronic device is acceptable based on acceptance permission information of two electronic devices. If the check result is OK, the server device sends a screen requesting a password to the electronic device 2.
  • the user of electronic device 2 (which may be a user of electronic device 2 or a user of electronic device 1) receives the password request screen in step S2103. Enter the entered password and send it to the server device.
  • the part that performs this transmission can be referred to as a nose transmission part.
  • the server device receives the friendly ID and password.
  • the part that performs this reception can be called the transfer-source friendly ID 'password receiving part.
  • the password is searched by using the electronic device ID of the transfer source electronic device and the electronic device ID of the transfer destination electronic device, and the received password and Check whether the searched passwords are the same If the check is SOK, the service originally provided to the electronic device 1 is provided to the electronic device 2.
  • the service originally provided to the electronic device that is the transfer source of the title is provided to the other electronic device that is the transfer destination of the title on condition that the password is entered and checked.
  • the service can be prevented from being provided to other electronic devices to which the title is transferred against the intention of the user of the electronic device from which the title is transferred.

Abstract

Le problème à résoudre dans le cadre de l'invention est tel que, selon la technique d'authentification conventionnelle, un utilisateur d'un dispositif ne peut pas recevoir le service qui peut être reçu par son dispositif lors de l'utilisation d'un dispositif appartenant à une autre personne comme un ami ou une relation. Le moyen de résoudre le problème consiste à fournir un système comprenant un dispositif électronique et un dispositif de serveur qui passent par les étapes suivantes : - un dispositif électronique qui transmet une requête pour démarrer le procédé afin de transférer le droit de recevoir le service fourni du serveur à un autre dispositif électronique de sorte que la requête soit entrée dans un écran de travail pour la requête et transmet un identifiant public de l'autre dispositif électronique, - le dispositif de serveur corrèle l'identifiant du dispositif pour identifier le même dispositif électronique avec l'identifiant public à détenir, il transmet l'écran de travail conformément à la réception de la requête, extrait l'identifiant du dispositif électronique comme destination de transfert du droit associé à l'identifiant public reçu via l'écran de travail transmis, corrèle l'identifiant du dispositif avec l'identifiant du dispositif électronique qui a transmis l'identifiant public via l'écran de travail et le conserve.
PCT/JP2007/066718 2006-08-30 2007-08-29 Système de fourniture de service WO2008026617A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2006-234564 2006-08-30
JP2006234564A JP2008059222A (ja) 2006-08-30 2006-08-30 サービス提供システム

Publications (1)

Publication Number Publication Date
WO2008026617A1 true WO2008026617A1 (fr) 2008-03-06

Family

ID=39135899

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2007/066718 WO2008026617A1 (fr) 2006-08-30 2007-08-29 Système de fourniture de service

Country Status (2)

Country Link
JP (1) JP2008059222A (fr)
WO (1) WO2008026617A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109951436B (zh) 2014-10-24 2021-04-27 创新先进技术有限公司 一种可信终端验证方法、装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002163353A (ja) * 2000-08-16 2002-06-07 Mitsubishi Electric Research Laboratories Inc エンティティを識別するコンピュータ化された方法及びエンティティを識別する通信ネットワーク
JP2002314533A (ja) * 2001-04-12 2002-10-25 Mitsunori Honma 著作物の使用権及び認証機器管理方法
JP2004265334A (ja) * 2003-03-04 2004-09-24 Sony Corp 情報処理装置および方法、並びにプログラム
JP2005322070A (ja) * 2004-05-10 2005-11-17 Sega Corp 会員登録されたユーザを起点に会員未登録の他のユーザに会員サービスを提供するシステム、サーバ、サービス提供方法およびプログラム

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002163353A (ja) * 2000-08-16 2002-06-07 Mitsubishi Electric Research Laboratories Inc エンティティを識別するコンピュータ化された方法及びエンティティを識別する通信ネットワーク
JP2002314533A (ja) * 2001-04-12 2002-10-25 Mitsunori Honma 著作物の使用権及び認証機器管理方法
JP2004265334A (ja) * 2003-03-04 2004-09-24 Sony Corp 情報処理装置および方法、並びにプログラム
JP2005322070A (ja) * 2004-05-10 2005-11-17 Sega Corp 会員登録されたユーザを起点に会員未登録の他のユーザに会員サービスを提供するシステム、サーバ、サービス提供方法およびプログラム

Also Published As

Publication number Publication date
JP2008059222A (ja) 2008-03-13

Similar Documents

Publication Publication Date Title
US9203825B2 (en) Method of authenticating a user of a peripheral apparatus, a peripheral apparatus, and a system for authenticating a user of a peripheral apparatus
JP4301997B2 (ja) 携帯電話による情報家電向け認証方法
JP4892011B2 (ja) クライアント装置、鍵装置、サービス提供装置、ユーザ認証システム、ユーザ認証方法、プログラム、記録媒体
JP4800377B2 (ja) 認証システム、ｃｅ機器、携帯端末、鍵証明発行局および鍵証明取得方法
JP5790653B2 (ja) サービス提供システム
JP2007102778A (ja) ユーザ認証システムおよびその方法
WO2006073008A1 (fr) Systeme d’authentification d’une camera de reseau
JP5462021B2 (ja) 認証システム、認証方法および認証プログラム
JP2007102777A (ja) ユーザ認証システムおよびその方法
JP2006302292A (ja) 動的認証方法、動的認証システム、制御プログラム、および、物理キー
JP2005521964A (ja) 異種通信網を用いたインスタントログイン利用者認証及び決済方法並びにそのシステム
JP4960738B2 (ja) 認証システム、認証方法および認証プログラム
JP2005527909A (ja) 電子メールアドレスとハードウェア情報とを利用したユーザ認証方法及びシステム
JP2008065584A (ja) 電子機器の認証に関する識別管理のためのシステム
JP2007133743A (ja) サービス提供サーバおよび認証システム
JP2009118110A (ja) 認証システムのメタデータプロビジョニング方法、システム、そのプログラムおよび記録媒体
WO2015136728A1 (fr) Système de gestion d'informations d'authentification, dispositif de gestion d'informations d'authentification, programme, support d'enregistrement et procédé de gestion d'informations d'authentification
JP4005596B2 (ja) 認証装置および認証方法
JP2009075987A (ja) ネットワークコンテンツ管理方法、コンテンツサーバ、再生機器、認証サーバおよび認証端末
JP2012005037A (ja) Ｗｅｂサイトログイン方法及びＷｅｂサイトログインシステム
JP5485063B2 (ja) 認証システム
JP2007115226A (ja) ユーザ認証システム
JP6325654B2 (ja) ネットワークサービス提供装置、ネットワークサービス提供方法、及びプログラム
JP2002245006A (ja) 認証システム、認証方法、プログラム及びその記録媒体
WO2008026617A1 (fr) Système de fourniture de service

Legal Events

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

Ref document number: 07806195

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

122 Ep: pct application non-entry in european phase

Ref document number: 07806195

Country of ref document: EP

Kind code of ref document: A1