JP2005109660A - Service providing method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problems that a load required for access authentication and permission of a provided service or the like is very heavy in the case of a connection request from a terminal to a server and operations are very complicated in the case of services and addition of applications after purchase of the terminal. <P>SOLUTION: In the case that a terminal service management server 7 provides a service to an IPv6 compatible terminal 1 connected to a LAN 29, the IPv6 compatible terminal 1 converts a first address into a second address when the first address in response to the service received from the terminal service management server 7 is in duplicate with an address in the LAN 29 to which the IPv6 compatible terminal 1 is connected. The terminal service management server 7 provides the service to the IPv6 compatible terminal 1 when a sender address of a service request is the first address and the second address. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a service providing method.

In recent years, terminal devices have accessed a server via the Internet, browsed content on the server via browser software, and downloaded software on the server (for example, Patent Document 1).
JP 11-0665828 A

  However, when there is a connection request from the terminal device to the server, the access authentication, the license of the service to be provided, etc., is performed by the application installed on the client terminal negotiating with the server at the application protocol level. Since this has been realized, the application implemented in the terminal device becomes complicated. In particular, the load on the terminal device operating as a thin client is very heavy.

  In addition, services and applications added after purchase of terminal equipment must be downloaded and installed by the customer who purchased the terminal equipment using the application of the terminal equipment. For customers who are not familiar with the installation operation, It was a complicated operation, and it was difficult to upgrade the application version of the terminal device.

  The service providing method of the present invention is a service providing method in which a first device provides a service to a second device, and the second device has a first address corresponding to the service received from the first device. When there is an overlap in the network to which the second device is connected, the first address is converted to the second address, and the first device has the source address of the service request as the first address And the service is provided to the second device when the address is the second address.

  According to the present invention, a service can be provided without causing a customer to perform a complicated installation process of an application service regardless of the state of a network to which the apparatus is connected.

  In addition, it is possible to reduce the processing load of the terminal device in the login process to the application and the authentication process.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is an overall system configuration diagram according to an embodiment of the present invention.

  In FIG. 1, 5 is a terminal manufacturing factory site, 6 is a terminal service providing site, 16 is a sales management site operated by a dealer, 30 is an Internet service provider, 29, 31 and 33 are LANs, and 100 is the Internet.

  In the terminal service providing site 6, 7 is a terminal service management server. In the sales management site 16, 1A is an IPv6 (Internet Protocol Version 6) compatible terminal device, 2A is an IPv6 compatible router, 17 is a customer terminal database, 19 is a client terminal, and 36 is a terminal sales management server. The client terminal 19 inputs customer information and service information at the time of sale. The IPv6-compatible terminal device 1A is connected to the LAN 29 after being sold. The client terminal 19 and the terminal sales management server 36 have a known computer configuration.

  The ISP 30 is a site that provides a service for connecting the LANs 29, 31, and 33 to the Internet 100. A gateway server 25 has a function of managing and monitoring the connection between the ISP 30 and the Internet 100. A router 26 has a routing function for transferring IP packets to a destination in response to a request from a terminal connected to a customer network 29, 31, 33.

  The router 26 is connected to a plurality of networks (subnets) for each customer. Each customer forms a small subnet such as LANs 29, 31, and 33. For example, an IP packet transmitted from the terminal device 1 (shown in FIG. 2) connected to this subnet (LAN 29) is sent to the router 26. To the Internet 100 from the gateway server 25.

  FIG. 2 is a configuration diagram showing details of the LAN 29 of FIG.

  In the LAN 29 shown in FIG. 2, reference numerals 1, 33, 35, and 136 are IPv6-compatible terminal devices, and 34 is an IPv6-compatible router.

  The IPv6 compatible terminal device 1 is the same as the IPv6 compatible terminal device 1A in the sales management site 16 shown in FIG. 1, and the IPv6 compatible terminal device 1A connected to the sales destination LAN 29 is connected to the IPv6 compatible terminal device 1. Express.

  The IPv6-compatible router 34 is connected to the IPv6-compatible router 26 in the Internet service provider (ISP) 30. The LANs 31 and 33 are also connected to the IPv6-compatible router 26 in the Internet service provider 30 in the same manner as the LAN 29.

  FIG. 3 is a block diagram of the terminal service providing site 6 shown in FIG.

  The terminal service management server 7 has a known computer configuration as shown below.

  In FIG. 3, 302 is a CPU that controls the entire terminal service management server 7, and provides various functions by executing arithmetic processing based on a control program stored in the ROM 304. That is, as will be described below, the CPU 302 authenticates the terminal device 1 (confirms address matching) and provides a service to the terminal device 1 based on a control program stored in the ROM 304.

  Reference numeral 306 denotes a common bus line for signals required by each unit in the terminal service management server 7. A RAM 303 functions as a main memory of the CPU 302 and as a work area and a temporary standby area for an execution program.

  A ROM 304 stores operation processing procedures of the CPU 302. The ROM 304 stores a system program that controls the function of the terminal service management server 7, a program that is represented by a process follow described later, and data that is necessary for operating the system.

  Reference numeral 305 denotes a network interface. The server 7 accesses the Internet 100 via the LAN, which is a network in the terminal service providing site 6, and transfers data (information) with the server at each site in FIG. Communication processing such as (transmission / reception) is executed.

  Reference numeral 307 denotes a video RAM, and 310 denotes a CRT 310. Reference numeral 308 denotes a keyboard controller for controlling an input signal from the external input device 311. Reference numeral 311 denotes an external input device for accepting an operation, such as a keyboard or a pointing device. A disk controller 309 controls a removable disk 312 such as a hard disk or a floppy (R) disk. The removable disk 312 includes a zero-conf module 12, a service module 13, a customer-specific terminal service database 14, and a service identification ID database 502.

  FIG. 4 is a hardware configuration diagram of the IPv6 compatible terminal device 1. The IPv6-compatible terminal device 1 is an IPv6-compatible terminal 1A when connected to the sales management site 16.

  In FIG. 4, a CPU 216 controls the entire terminal device 1, and provides various functions by executing arithmetic processing based on a control program stored in the ROM 218. Reference numeral 220 denotes a common bus line for signals required by each unit in the terminal device 1. Reference numeral 217 denotes a RAM which functions as a main memory of the CPU 216 and as a work area and a temporary standby area for an execution program.

  Reference numeral 218 denotes a ROM that stores the operation processing procedure of the CPU 216. The ROM 218 stores a system program that controls the function of the terminal device 1, a program that is represented by a process follow described later, and data that is necessary for operating the system.

  Reference numeral 221 denotes a network interface. The terminal device 1 uses this interface to access the Internet 100 via the IPv6-compatible router 34 (LAN 29) or the IPv6-compatible router 2 (terminal manufacturing factory site 5), and the terminal management service server 7 Communication processing such as data transfer is executed.

  222 is a video RAM and 225 is a CRT. Reference numeral 223 denotes a keyboard controller for controlling an input signal from the external input device 226. Reference numeral 226 denotes an external input device for accepting an operation, for example, a keyboard or a pointing device.

  Next, the configuration of the IP address in the IPv6 protocol will be described.

  The IPv6 address has an identification ID composed of a 128-bit binary number.

  Among 128 bits, the previous 64 bits are a network address part. The network address is called a prefix. This network address is an address for identifying a network to which an IPv6 compatible terminal device is connected, and is notified from a router (for example, the router 34, 2) in the link of the network (a range in which communication is possible in the data link layer). Earn this.

  Of 128 bits, the last 64 bits are the host address. The host address is called an alias interface ID.

[Service ID issued]
In this embodiment, a host address identification ID generated based on a service identification ID for identifying a “service provided from the server 7” used in a contract at the time of sale is used for the host address portion of the IP address. Customer information and service information managed by the terminal sales management server 36 are transmitted to the terminal service providing site 6, and the terminal service management server 7 issues a service identification ID based on the information. The customer-specific terminal service DB 14 manages terminal IDs, customer information, and service identifier ID related information. The service identification ID is transmitted to the terminal sales management server 38 and written in the memory (RAM 217) of the IPv6 compatible terminal device 1A via the IPv6 compatible router 2A.

  FIG. 5 shows a service identification ID issuing process for identifying a service contracted at the time of sale.

  In “acquisition of attribute information of terminal purchase customer” in S150, when selling the IPv6 compatible terminal device 1A, the store operator uses the client terminal 19 to sell the terminal ID and user attribute information (name, address, telephone number). Number, Email address, etc.) and the terminal sales management server 36 receives this.

  In “send terminal & customer information” in S 151, the terminal ID, terminal information, and customer information acquired by the terminal sales management server 36 are transmitted to the terminal service management server 7.

  Upon receiving this information, the terminal service management server 7 uses the terminal ID and customer attribute information transmitted from the terminal sales management server 36 in “registration in the customer-specific terminal service DB” in S154, as the customer of the customer-specific terminal service DB 14. Register in the separate terminal service attribute table. At the stage where the terminal ID and customer attribute information are registered, the terminal service management server 7 transmits a request for determining the service used by the customer to the terminal sales management server 36 in S155.

  Receiving this, the terminal sales management server 36 requests the operator to determine the service to be provided to the user via the client terminal 19. When the user determines the service and the contract is established, the operator notifies the terminal sales management server 36 of the termination of the service contract from the client terminal 19, and the terminal sales management server 36 permits the IPv6-compatible terminal device 1 in S152. Determine the service.

  In the service identification ID issue request in S153, the license service of the IPv6-compatible terminal device 1A is identified, and a service identification ID issue request used for host address generation is transmitted to the terminal service management server 7. Receiving this, the terminal service management server 7 refers to the service identification ID database 502 in S156. The free ID designated from the service identification ID database 502 in the confirmation of the free ID in S157 is determined as the service identification ID in S158.

  In S159, the IPv6-compatible terminal device 1A selects a conversion function to be used when generating a host address from this service identification ID. When the IPv6-compatible terminal device 1 is connected to the destination network (LAN 29), a host address is generated from the service identification ID. If the same host address exists, the host address is again converted by the conversion function. To a new host address identification ID.

  By performing such processing, if the host address generated from the service identification ID distributed from the terminal service management server 7 already exists in the destination network (hereinafter, such a state is duplicated). It is possible to avoid duplication and generate a host address.

  In “execute ID conversion process at duplication” in S160, the terminal service management server 7 actually executes the conversion process assuming the duplication time. In “161 ID conversion at duplication OK?” In S161, after conversion. It is confirmed that the generated host address identification ID does not exist in the service identification ID database 502.

  If there is a duplication in the service identification ID database 502, the process returns to “Select a conversion function for duplication processing” in S159, selects a new conversion function, and “ID conversion for duplication” in S160. In “Execute process”, a new host address identification ID is generated with a new conversion function for the service identification ID, and “ID conversion at duplication?” Is checked in S161.

  When the confirmation that there is no duplication in the host address identification ID after the conversion processing is completed in the service identification ID database 502 by “ID conversion OK? At duplication” in S161, the service identification ID (and the service in S162 is completed). The service to be provided corresponding to the identification ID) and the conversion function number are registered in the customer-specific terminal service DB 14 and the service identification ID database 502, and the service identification ID, conversion function, and conversion function number are registered in the terminal sales management server 36. Send to.

  The terminal sales management server 36 sets the determined service identification ID, conversion function, and conversion function number in the RAM (memory) 217 of the IPv6 compatible terminal device 1A in “set service identification ID and conversion function in terminal” in S163. Write.

  Through this series of processing, the terminal service management server 7 and the IPv6-compatible terminal device 1A hold the common service identification ID, conversion function, and conversion function number in their respective memories (customer-specific terminal service DB 14 and RAM 217). Thereafter, using this information, terminal authentication and service provision are performed by negotiation at the IP layer level.

[Global address generation process at user site]
The IPv6 compatible terminal device 1 stores the service identification ID, the conversion function, and the conversion function number in the RAM 217 at the stage where the user uses the network LAN 29, and uses the service identification ID, the conversion function, and the conversion function number. IPv6 global IP address is automatically generated.

  FIG. 6 is a process flow diagram of global IP address generation in the user network.

  In RS (Router Solicitation) transmission in S164, the IPv6 compatible terminal device 1 inquires of the network address to the IPv6 compatible router 34 existing in the same link.

  The IPv6-compatible router 34 receives this message by RS reception in S165, and notifies the IPv6-compatible terminal device 1 of the network address, which is the network identifier, by RA (Router Advertisement) transmission in S166.

  In step S167, the IPv6-compatible terminal apparatus 1 acquires a network address from the RA message. Next, a host address identifier is generated using the service identification ID and the conversion function previously distributed from the terminal service management server 7.

  FIG. 7 is a configuration diagram of the IPv6 host address part generated from the service identification ID. Reference numeral 41 denotes a host address part of an IPv6 address. In the flag of 60, duplication occurs when a service identification ID is generated, and the number of times a new service identification ID is generated by a conversion function is set to avoid duplication. In Fmun 61, the number of the conversion function received from the terminal service management server 7 by the IPv6-compatible terminal device 1 is set. As the S-ID 62, a host address identification ID generated based on the service identification ID received from the terminal service management server 7 is set.

  In S168, the variable N that stores the number of conversion processes at the time of duplication is reset to zero. In S <b> 169, N is set in “Flag” 60. In S170, “Fmun” 61 and “S-ID” 62 are set in the host address portion. In S171, a host address composed of “Flag” 60, “Fmun” 61, and “S-ID” 62 is created, and a global IP address is generated together with the network address acquired in S167.

  The IPv6-compatible terminal device 1 that has generated the global IP address transmits the global IP address to the IPv6-compatible router 34 in S171. The IPv6-compatible router 34 that has received the global IP address checks for duplicate host addresses in the same link network, and transmits the result to the IPv6-compatible terminal device 1. If there is no duplication in the duplication check in S173, in S174, the global IP address composed of the currently set host address is determined as the global IP address of the IPv6-compatible terminal device 1. Note that this duplication check may be made without confirming to the IPv6-compatible router 34, that the IPv6-compatible terminal 1 autonomously confirms whether there is a device using the same address in the LAN 29.

  In the duplication check in S173, if there is duplication, S-ID62 is converted by the conversion function in S175, a new service identification ID is generated, and in S176, 1 is added to the number of conversions N, and the process returns to S169. The routine for global IP address generation is entered again. By repeating this routine several times, the global IP address into which the service identification ID is inserted can be set. The conversion function used at the time of duplication may be a function linked to the terminal service management server 7. For example, there is a process of adding or subtracting a predetermined number to a service identification ID.

[Service Usage Protocol]
FIG. 8 is a diagram illustrating a service use protocol using a service identification ID.

  This is a protocol showing a procedure for the IPv6 compatible terminal device 1 to use the service of the terminal service management server 7 using the host address generated from the service identification ID.

  In step S177, the IPv6-compatible terminal device 1 whose global IP address has been determined transmits an IPv6 packet requesting service use to the terminal service management server 7 in step S178.

  In S179, the terminal service management server 7 checks the source address of the transmitted IPv6 packet, receives only the packet of the host address generated from the registered service identification ID, and receives a session with the destination terminal. Establish communication. That is, first, in S180, the conversion count value set in Flag60 is detected. When Flag = 0, the service corresponding to the service identification ID set in the S-ID 62 is detected from the customer-specific terminal service database 14.

  The service detected in the “corresponding application activation” of S182 is activated, and the port number to be used is notified to the IPv6 compatible terminal device 1. The IPv6-compatible terminal device 1 that has received the notification of the port number establishes TCP session communication for the designated port number in “use service” in S189, and uses the service application of the terminal service management server 7. .

  If Flag = 0 in S180 (when the IPv6-compatible terminal device 1 generates a host address, duplication occurs and one or more service identification ID conversion processes are performed based on the service identification ID) In S183, the conversion function number is obtained from “Fnum” 61 of the host address part. In S184, the inverse conversion function finv of the conversion function f corresponding to the corresponding conversion function number is obtained. In S185, the number of conversions is set. The set value of the flag being set is set in the variable Count. Since the inverse conversion process is performed as many times as the number of conversions, the inverse conversion process is repeated until the variable Count becomes zero. If the conversion function f is a process of adding a predetermined number to a service identification ID, the inverse conversion function finv is a process of subtracting a predetermined number of a constant from the service identification ID.

  In S186, the value obtained by converting the current S-ID 62 to be subjected to the inverse conversion process with the inverse conversion function finv is set in the S-ID. Once the inverse transformation process is performed, the variable Count is decremented. This process is repeated until the variable Count becomes zero. If the variable Count is not zero in S188, the process returns to the inverse conversion process in S186 and this routine is repeated. If the variable Count is zero in S188, the process returns to the inverse conversion process routine.

  At this stage, the reversely converted service identification ID is the service identification ID first distributed to the IPv6-compatible terminal device 1 by the terminal service management server 7. After searching from the separate terminal service database 14, as described above, the states of S182 and S189 are changed to provide the IPv6 compatible terminal device 1 with a service that can be used with a contract at the time of sale. If the corresponding service is not registered in the customer-specific terminal service database 14, the session is disconnected.

  The second device (IPv6-compatible terminal device 1) is generated based on the first address (service ID set in S163 in FIG. 5) corresponding to the service received from the first device (terminal service management server 7). Is duplicated in the network (LAN 29) to which the second device (IPv6-compatible terminal device 1) is connected (S173 in FIG. 6), the first address is changed to the second address by the above conversion function. The address is converted (S175). When the source address of the service request is the first address and when the first device (terminal service management server 7) is the second address, the first device (IPv6-compatible terminal device 1) Service). The first device (terminal service management server 7) stores the service ID and the corresponding service in the terminal service DB. When the source address of the service request is the second address converted by the above conversion function, the first device (terminal service management server 7) converts the above address into the second address. And a service corresponding to the first address is provided to the second device (IPv6 compatible terminal device 1).

  The terminal service management server 7 is a service providing device, and when the source address of the service request is the second address converted from the first address, the terminal service management server 7 converts the second address to the reverse of the conversion. Inverse conversion means (CPU 302) for performing conversion, and provision means (network interface 305) for providing a service corresponding to the first address obtained by the reverse conversion.

  As described above, when the IPv6 compatible terminal 1 connected to the LAN 29 sets its own IP address, if the IP address to be used is duplicated, the IP address (service identification ID included in the IP address) is included. Is converted using a predetermined conversion function. If the converted IP address is duplicated, the IPv6 compatible terminal 1 converts the IP address again. The IPv6-compatible terminal 1 includes data indicating the number of times the IP address has been converted (number of conversions 60) in the IP address.

  The terminal service management server 7 provides a service corresponding to the transmission source address of the service request packet received from the IPv6 compatible terminal 1 to the IPv6 compatible terminal 1. The terminal service management server 7 provides the same service to the IPv6-compatible terminal 1 even when the IP address is converted using the above-described conversion function. The terminal service management server 7 specifies a service to be provided to the IPv6-compatible terminal 1 based on the number of conversions 60 included in the transmission source address.

  Next, Example 1 will be described. In the present embodiment, the IPv6 compatible terminal device 1 includes a manufacturer identification ID for identifying the manufacturer of the manufacturer and a device identification ID for identifying the terminal device 1 in the IP address, and the terminal service management server 7 includes the manufacturer identification ID, the device The received packet is filtered based on the identification ID.

  In the present embodiment, the configuration of the terminal service providing site 6, the sales management site 16, the Internet service provider 30, and the LAN 29 is the same as that shown in FIG.

  FIG. 9 is a configuration diagram showing details of the terminal manufacturing factory site 5.

  In the terminal manufacturing factory site 5 shown in FIG. 9, 1B is an IPv6-compatible terminal device, 2 is an IPv6-compatible router, 3 is a terminal manufacturing management server, and 4 is a terminal device attribute database. The terminal manufacturing factory site 5 is connected to the Internet 100 via the router 2. The terminal manufacturing management server 3 is configured by a known computer and is connected to the terminal device attribute database 4. The terminal manufacturing management server 3 (and the terminal device attribute database 4) may be connected to the IPv6 compatible device 1B side of the IPv6 compatible router 2.

  9 is connected to the sales management site 16 of FIG. 1 as the IPv6 compatible terminal device 1A at the time of sale.

  FIG. 10 is a configuration diagram of the IPv6 host address portion of the IPv6-compatible terminal 1 generated from the manufacturer identification ID, device identification ID, and service identification ID. Reference numeral 41 denotes a host address part of an IPv6 address, and in the flag of 60, the number of times that a new service identification ID is generated by a conversion function is set to avoid duplication when the service identification ID is generated. In Fmun 61, the number of the conversion function received from the terminal service management server 7 by the IPv6-compatible terminal device 1 is set. In the M-ID 63, a manufacturer identification ID for identifying the manufacturer of the manufacturer is set. The 64 D-ID is set with a device identification ID for identifying the terminal device 1. As the S-ID 62, a service identification ID generated based on the service identification ID received from the terminal service management server 7 is set.

[M-ID: D-ID setting process]
FIG. 11 is a drawing showing a processing flow for setting M-ID (maker identification ID) and D-ID (device identification ID) at the time of manufacturing at the terminal manufacturing factory site 5.

  In the manufacturing process of the IPv6-compatible terminal device 1B at the terminal manufacturing factory site 5, the IPv6-compatible terminal device 1B connected to the IPv6-compatible router 2 supports IPv6 existing in the same link by RS (Router Solicitation) transmission of S100. A network address inquiry is made to the router 2.

  The IPv6-compatible router 300 receives this message by the RS reception of S102, and notifies the IPv6-compatible terminal device 1B of the network address, which is the network identifier, by RA (Router Advertisement) transmission of S103. In S104, a network address is acquired from the RA message.

  Next, the IPv6 compatible terminal device 1B generates a host address from the distributed M-ID (maker identification ID) and D-ID (corresponding to the device identification ID and terminal ID) from the terminal manufacturing management server 3. In order to receive the M-ID and D-ID, the IPv6 compatible terminal device 1B generates a temporary address based on the MAC address of the network interface 221 and accesses the terminal manufacturing management server 3 using the temporary address. To do. The D-ID is a serial number, and different numbers are assigned to all devices manufactured by the manufacturer. Note that M-ID and D-ID may be written in the ROM 218 at the time of manufacture.

  In S105, the IPv6-compatible terminal device 1B that has received the manufacturer identification ID stores the manufacturer identification ID as an M-ID in the RAM (memory) 217 and sets it in the M-ID portion 63 of the host address of the IPv6-compatible terminal device 1B. To do. In S106, the IPv6-compatible terminal device 1B that has received the device identification ID stores the device identification ID as a D-ID in the RAM 217 and sets it in the D-ID portion 64 of the host address of the IPv6-compatible terminal device 1B.

  In S107, the Flag 60, Fmun 61, and S-ID 62 determined after the sale of the IPv6-compatible terminal device 1B are reset to zero and set to the initial state. In S108, an IPv6 global IP address is generated from the host address part set in S105, S106, 107 and the network address of the user network acquired in S104, and transmitted to the IPv6-compatible router 2.

  In response to the address duplication check in S109, the IPv6-compatible router 2 confirms that there is no duplication of the host address in the same link of the user network, and if there is no duplication, it indicates that there is no duplication. Notify

  The IPv6-compatible terminal 1B transmits a registration packet to the terminal service management server 7 in S110. The source address is the global IP address generated in S108. Receiving this, the IPv6-compatible router 2 transfers the registration packet to the terminal service management server 7 in S111.

  The terminal service management server 7 receives this registration packet, and in S112, extracts the source address (including M-ID and D-ID) of the received registration packet and sets it as the default host address of the IPv6-compatible terminal device 1B. To do. In S113, the set default host address (including M-ID and D-ID) is registered in the manufacturing terminal host address list 8.

  The registration packet may be transmitted by the terminal device manufacturing server 3. The IPv6-compatible terminal 1B transmits the registration packet to the terminal manufacturing management server 3, and the terminal manufacturing management server 3 stores the terminal device attribute information in the terminal device attribute table in the bay load part of the IPv6 packet, and the IPv6 host of the terminal 1B. The address part (including M-ID and D-ID) is set to the source address of the IPv6 header, and is transmitted to the terminal service providing site 6 as a terminal registration IPv6 packet. The terminal service providing site 6 receives this, extracts the host address (including M-ID and D-ID) from the transmission source address of the received terminal registration IPv6 packet, and extracts terminal attribute information from the bay load section. And stored in the terminal-specific host address list 8. The terminal manufacturing management server 3 stores the IPv6 host address of the terminal device 1B in the terminal device attribute database 4 as a terminal device attribute table in association with the terminal device ID (D-ID) and the terminal attribute information.

  Thus, in the pre-shipment stage, the IPv6 host address, the terminal ID, and the terminal attribute information of the IPv6 compatible terminal device 1 generated from the manufacturer identification ID and the device identification ID are notified and registered in the terminal service providing site 6.

[Service ID issued]
In this embodiment, the service ID issuing process for identifying the service contracted at the time of sale is the same as that shown in FIG. 5 except for S154 described below. That is, the terminal service management server 7 sends the terminal ID (which is the same as D-ID 64 in this embodiment) and customer attribute information transmitted from the terminal sales management server 36 to the customer-specific terminal service DB 14 in S154. While registering, the default host address (including M-ID 63) of the IPv6 compatible terminal device 1B corresponding to the terminal ID is extracted from the manufacturing terminal host address list 8 and associated with the terminal ID and customer information in the customer-specific terminal service DB 14 Store.

  In the service identification ID issuing process described above, the terminal service management server 7 and the IPv6 compatible terminal device 1A share the Fnum 61, M-ID 63, D-ID 64, and S-ID 62.

[Global address generation process at user site]
The IPv6 compatible terminal device 1 is M-ID (manufacturer identification ID), D-ID (device identification ID), S-ID (service identification ID), Fnum (conversion function) at the stage where the network LAN 29 is used by the user. Number) and f (conversion function) information is stored in the RAM 217, and an IPv6 global IP address is automatically generated using the service identification ID, conversion function, and conversion function number.

  In this embodiment, the global address generation processing at the user site is as shown in FIG. 6 except for S167 described below. That is, when the IPv6-compatible device 1 acquires the network address from the RA message in S167, the M-ID (maker identification ID) and D-ID (device identification ID) registered in the RAM 217 in advance are set to the host address 41. set.

[Service use protocol using service identification ID]
The service use protocol using the service identification ID is the same as that shown in FIG. 8 except for S179 described below. That is, in S179, the terminal service management server 7 extracts the source address from the IPv6 packet for which a connection request has been made, and performs M-ID filtering and D-ID filtering. Note that the global IP address determined in S177 has the configuration shown in FIG. 41 and includes M-ID 63 and D-ID 64.

  In the M-ID filtering, the M-ID 63 of the extracted transmission source address is extracted, and it is confirmed whether it is a connection request from the terminal of the manufacturer of the company. When the M-ID 63 matches the ID of the manufacturer, the primary authentication approval is completed and D-ID filtering is performed. If the ID of the manufacturer is not matched by M-ID filtering, primary authentication is rejected, access to the terminal service management server 7 is denied, and a communication session is sent to the IPv6-compatible terminal device 1 that is notified of access denial. finish.

  When primary authentication of M-ID filtering is completed, D-ID 64 is extracted from the extracted transmission source address, and secondary authentication approval processing is performed using a device identification ID for service use. This approval process is used for efficient guidance to services that can be used for each terminal and for setting access authority for services that can be used for each terminal category. Secondary authentication is rejected for terminals for which D-ID 64 is not registered by D-ID filtering, and terminals that do not have access authority, and are notified to IPv6-compatible terminal apparatus 1, which receives this. End the communication session. The D-ID is registered in the terminal service DB 11.

  When the secondary authentication is approved from the D-ID by the D-ID filtering, the IPv6 compatible terminal device 1 permits the login to the corresponding service directory having the access right and the use right.

  At the stage where the session with the IPv6-compatible terminal device 1 is established, the conversion count value set in the Flag 60 is first detected from the source address in S180.

  The second device (IPv6-compatible terminal device 1) is generated based on the first address (service ID set in S163 in FIG. 5) corresponding to the service received from the first device (terminal service management server 7). Is duplicated in the network (LAN 29) to which the second device (IPv6-compatible terminal device 1) is connected (S173 in FIG. 6), the first address is changed to the second address by the above conversion function. The address is converted (S175). When the source address of the service request is the first address and when the first device (terminal service management server 7) is the second address, the first device (IPv6-compatible terminal device 1) Service). The first device (terminal service management server 7) stores the service ID and the corresponding service in the terminal service DB. When the source address of the service request is the second address converted by the above conversion function, the first device (terminal service management server 7) converts the above address into the second address. And a service corresponding to the first address is provided to the second device (IPv6 compatible terminal device 1).

  The first address and the second address include predetermined values (M-ID, D-ID), and the first device (terminal service management server 7) has the address of the transmission source of the service request The service is provided after confirming that a predetermined value (M-ID, D-ID) is included.

  Next, Example 2 will be described. In this embodiment, the IPv6 compatible terminal device 1 accesses the terminal service management server 7 from the sales management site 16 or the user site (LAN 29), and determines a service ID corresponding to the service received from the terminal service management server 7.

  In the present embodiment, the configuration of the terminal service providing site 6, the sales management site 16, the Internet service provider 30, and the LAN 29 is the same as that shown in FIG. The configuration of the terminal manufacturing factory site 5 is the same as that shown in FIG.

[Host address registration process generated from MAC address]
FIG. 12 shows a registration process of the host address generated from the MAC address of the IPv6-compatible terminal device 1B (IPv6-compatible terminal device 1 at the terminal manufacturing site 5) in the terminal service management server 7 in the manufacturing process at the terminal manufacturing factory site 5. It is drawing which shows.

  In the manufacturing process of the IPv6-compatible terminal device 1B at the terminal manufacturing factory site 5, the IPv6-compatible terminal device 1B connected to the IPv6-compatible router 2 supports IPv6 existing in the same link by RS (Router Solicitation) transmission of S100. A network address inquiry is made to the router 2.

  The IPv6-compatible router 2 receives this message by the RS reception of S102, and notifies the IPv6-compatible terminal device 1B of the network address, which is the network identifier, by RA (Router Advertisement) transmission of S103.

  In step S104, the IPv6-compatible terminal 1B acquires a network address from the RA message. Next, in S105, the IPv6 compatible terminal device 1B generates an EUI-64 code from the MAC address of the network interface 221 of the IPv6 compatible terminal device 1B, sets the EUI-64 code in the host address part in S106, and in S108. The IPv6 global IP address is generated from the host address that has been set and the network address acquired in 104.

  The IPv6 compatible terminal device 1B transmits the generated IPv6 global IP address to the IPv6 compatible router 2, and checks whether there is the same host address in the same network in the address duplication check in S109. The IPv6-compatible terminal device 1B that has confirmed that there is no address duplication transmits a registration packet to the terminal service management server 7 in S110. The global IP address generated in S108 is set as the source address of the registration packet. The IPv6-compatible router 2 transfers the registration packet to the terminal service management server 7 in S111.

  Upon receiving this registration packet, the terminal service management server 7 extracts the source address using the network interface 305, and uses the source address extracted in S112 (the global IP address generated in S108) as the IPv6-compatible terminal device. 1B is set as the default host address, and the set host address (the host address generated in S106) is registered in the default host address list 10 in S113.

  The host address configuration in this embodiment and the service host address registration process at the terminal manufacturing factory site are the same as the host address configuration in FIG. 10 and the M-ID and D-ID setting processes in FIG. After completing the host address registration process (FIG. 12) generated from the MAC address, the IPv6 compatible terminal device 1B performs the processes after S105 in FIG. 11, and in S113, sets the M-ID and D-ID as the host address for each terminal. Register in Listing 8.

[Registration by default host address at customer management site]
FIG. 13 shows a terminal service management server 7 for customer information using a default host address generated from the MAC address of the IPv6 compatible terminal device 1A (IPv6 compatible terminal 1 in the sales management site 16) at the time of sales at the sales management site 16. It is drawing which shows the registration process.

  When selling the IPv6 compatible terminal device 1A at the terminal sales site 6, the IPv6 compatible terminal device 1A connected to the IPv6 compatible router 2A transmits the IPv6 compatible router 2A existing in the same link by S600 RS (Router Solicitation) transmission. Inquire about the network address.

  The IPv6-compatible router 2A receives this message by the RS reception in S601, and notifies the IPv6-compatible terminal device 1A of the network address, which is the network identifier, by sending an RA (Router Advertisement) in S602.

  In step S603, the IPv6-compatible terminal apparatus 1A acquires a network address from the RA message. Next, in step S604, the IPv6 compatible terminal device 1 generates an EUI-64 code from the MAC address of the network interface 221 of the IPv6 compatible terminal device 1A. In step S605, the EUI-64 code is set in the host address part. The IPv6 global IP address is generated from the set host address and the network address acquired in S603.

  The IPv6 compatible terminal device 1A transmits the generated IPv6 global IP address to the IPv6 compatible router 2A, and checks whether there is the same host address in the same network in the address duplication check of S607.

  The IPv6-compatible terminal device 1A that has confirmed that there is no address duplication sets customer information in the bay load unit in the terminal service management server 7 in S608, and transmits a registration packet in S609. In step S610, the IPv6-compatible router 2A transfers this packet to the terminal service management server 7.

  Receiving this, the terminal service management server 7 confirms the source address of the received packet by the default AD filtering of S611. The terminal service management server 7 rejects login for host addresses that are not registered in the default host address list 10 (default host addresses registered in S113 in FIG. 12), and notifies the IPv6 compatible terminal device 1A of login rejection. . In response to this, in step S614, the IPv6 compatible terminal device 1A confirms that exception processing has not been registered, and ends the job.

  If the source address is in the default host address list 10 in the default AD filtering of S611, login is permitted, and in S612, the default host address (global IP address generated in S606) and customer information are stored in the terminal service database for each customer. In step S613, the corresponding service host address is registered in the customer-specific terminal service database 14.

[Specified service host address issue processing]
Next, the registration of the service host address in S613 in FIG. 13 will be described in detail.

  FIG. 14 is a flowchart of designated service host address issuing processing at the sales management site. The service host address may be registered at the user site (LAN 29).

  In S319, the terminal service management server 7 activates the service setting program, and in the “service designation request” in S320, of the services that the terminal service management server 7 can provide to the IPv6 compatible terminal device 1A, Request specification.

  Receiving this message, the IPv6 compatible terminal device 1A determines the service to be used in “Accept license service” in S321, and requests the service host address to be issued for the established service in “Service identification ID issue request” in S322. .

  Receiving this, the terminal service management server 7 refers to the service identification ID database 502 in S156. In the confirmation of the free ID in S157, the free ID designated from the service identification ID database 502 is confirmed, and in S157, the free ID is determined as the service identification ID. In S159, the IPv6 compatible terminal device 1A selects a conversion function to be used when the host address is generated from the service identification ID.

  When the IPv6 compatible terminal device 1A is connected to the destination network (LAN 29), a host address is generated from the service identification ID. If the same host address exists, the host address is converted to a new one using a conversion function. Convert to host address identification ID. By performing such processing, if the host address generated from the service identification ID distributed from the terminal service management server 7 already exists in the destination network (hereinafter, such a state is duplicated). It is possible to avoid duplication and generate a host address.

  In “execute ID conversion process at duplication” in S160, the terminal service management server 7 actually executes the conversion process assuming the duplication time. In “161 ID conversion at duplication OK?” In S161, after conversion. It is confirmed that the generated host address identification ID does not exist in the service identification ID database 502. If there is a duplication in the service identification ID database 502, the process returns to “Select a conversion function for duplication processing” in S159, selects a new conversion function, and “ID conversion for duplication” in S160. In “Execute process”, a new host address identification ID is generated with a new conversion function for the service identification ID, and “ID conversion at duplication?” Is checked in S161.

  When the confirmation that there is no duplication in the host address identification ID after the conversion processing is completed in the service identification ID database 502 by “ID conversion OK? At duplication” in S161, the service identification ID (and the service in S162 is completed). The service to be provided corresponding to the identification ID) and the conversion function number are registered in the customer-specific terminal service DB 14 and the service identification ID database 502. In S325, the service host address list 8 is referred to, and the service identification ID, conversion function, and conversion function number set in S326 using the manufacturer identification ID and device identification ID registered in the address list 8. Generate an address. The terminal service management server 7 transmits the service identification ID, the conversion function, and the conversion function number to the IPv6 compatible terminal device 1A, and “installs the service identification ID and conversion function in the terminal” in S163, the memory of the IPv6 compatible terminal device 1A. (RAM 217).

  14 may be performed after a global IP address based on the EUI-64 code is generated in a state where the IPv6-compatible terminal 1 is connected to the user site (LAN 29).

  The global address generation process at the user site and the service use protocol using the service host address are the same as those in the first embodiment. That is, as described in the first embodiment, each is common to FIG. 6 except for S167, and common to FIG. 8 except for S179.

  The second device (IPv6-compatible terminal device 1) is generated based on the first address (service ID set in S163 in FIG. 5) corresponding to the service received from the first device (terminal service management server 7). Is duplicated in the network (LAN 29) to which the second device (IPv6-compatible terminal device 1) is connected (S173 in FIG. 6), the first address is changed to the second address by the above conversion function. The address is converted (S175). When the source address of the service request is the first address and when the first device (terminal service management server 7) is the second address, the first device (IPv6 compatible terminal device 1) Service). The first device (terminal service management server 7) stores the service ID and the corresponding service in the terminal service DB. When the source address of the service request is the second address converted by the above conversion function, the first device (terminal service management server 7) converts the above address into the second address. And a service corresponding to the first address is provided to the second device (IPv6 compatible terminal device 1).

  The second device (IPv6 compatible terminal device 1) has a third address (an address generated based on the MAC address), and the first device (terminal service management server 7) for determining the first address. When communicating with, the third address is used as the source address.

  Next, Example 3 will be described. In this embodiment, the IPv6-compatible terminal 1 receives a new service ID from the terminal service management server 7 when the addresses generated from the service IDs corresponding to the services received from the terminal service management server 7 are duplicated.

  In the present embodiment, the configuration of the terminal service providing site 6, the sales management site 16, the Internet service provider 30, and the LAN 29 is the same as that shown in FIG. The configuration of the terminal manufacturing factory site 5 is the same as that shown in FIG.

  The host address configuration generated from the service identification ID in this embodiment is the same as that in FIG. 10 except that there is no Flag 60 or Fmun 61. That is, the host address generated from the service identification ID in this embodiment includes a manufacturer identification ID (M-ID) 63 that identifies the manufacturer of the manufacturer, a device identification ID (D-ID) 63 that identifies the terminal device, and a terminal service. The service identification ID (S-ID) 62 received from the management server 7 is included.

  The M-ID: D-ID setting process is the same as that in FIG. 11 except that there is no zero reset of Flag 60, Fmun 61, and S-ID 62 in S107.

  In the present embodiment, in the sales process of the IPv6-compatible terminal device 1 at the terminal sales site 6, host address registration processing generated from the MAC address is performed. The host address registration process generated from the MAC address is the same as that shown in FIG. 12 except that it is performed at the terminal sales site 6. In addition, you may carry out in the terminal manufacture factory site 5 similarly to FIG.

[Service ID issued]
In this embodiment, the service ID issuing process for identifying the service contracted at the time of sale is the same as that shown in FIG. 5 except for the following points.

  That is, the terminal service management server 7 sends the terminal ID (which is the same as D-ID 64 in this embodiment) and customer attribute information transmitted from the terminal sales management server 36 to the customer-specific terminal service DB 14 in S154. While registering, the default host address (host address generated from the MAC address) of the IPv6 compatible terminal device 1B corresponding to the terminal ID is extracted from the default address list 10 and associated with the terminal ID and customer information in the customer-specific terminal service DB 14 Store.

  Further, S159, S160, and S161 are not necessary. After determining the service identification ID in S158, the service identification ID is registered in the customer-specific terminal service DB 14 and the service identification ID database 502 in S162. Is transmitted to the terminal sales management server 36. The terminal sales management server 36 writes the determined service identification ID in the memory (RAM 217) of the IPv6-compatible terminal device 1A in “set service identification ID to terminal” in S163.

  The service identification ID may be received from the terminal service management server 7 by the IPv6 compatible terminal device 1 accessing the terminal service management server 7 as shown in FIG. However, in this case, after the registration process of FIG. 13 is performed and the service identification ID is determined in S158 of FIG. 14, S159 to S162 are omitted, the service host address list 8 is referred to in S325, and “service” in S326 is determined. The service host address of the service designated by “Generate Host Address” is generated and notified to the IPv6 compatible terminal device 1. In S163, the IPv6-compatible terminal device 1 stores the received service host address in the memory (RAM 217). That is, when the second device (IPv6 compatible terminal device 1) communicates with the first device (terminal service management server 7) to determine the first address (to obtain the service identification ID), the third device An address (an address generated based on the MAC address) is used as a transmission source address.

[Global address generation process at user site]
FIG. 15 is a flowchart of global IP address generation at the user site.

  In RS (Router Solicitation) transmission in S164, the IPv6 compatible terminal device 1 inquires of the network address to the IPv6 compatible router 34 existing in the same link. The IPv6-compatible router 34 receives this message by RS reception in S165, and notifies the IPv6-compatible terminal device 1 of the network address, which is the network identifier, by RA (Router Advertisement) transmission in S166.

  In S167, the IPv6-compatible terminal apparatus 1 acquires a network address from the RA message. In S170, the service identification ID is set in the host address part, and in S171, a global IP address is generated together with the network address acquired in S167. In S172, the IPv6-compatible router 34 confirms address duplication and returns the result to the IPv6-compatible terminal device 1.

  If there is no address duplication in the “duplication check” in S173, the IPv6 compatible terminal device 1 determines the global IP address generated in S171 as the global IP address for service use of the terminal service management server 7 in S174. If there is an address overlap, an EUI-64 code is generated from the MAC address of the network interface 221 in S400, and a host address is generated from the generated EUI-64 code in S401. Combined with the network address acquired in S167, a global IP address is generated in S402. In S403, the IPv6-compatible router 34 confirms address duplication. In S404, the source address is set to the global IP address determined in S402, and a reissue request for the service identification ID is issued to the terminal service management server 7.

  Receiving this, the terminal service management server 7 extracts the global IP address (default address) generated in S402 from the source address in S405, performs authentication by comparing with the default address list 10, and in S406. Referring to the terminal service database 14, the service associated with the host address of the global IP address is specified, and the service identification ID is reissued. In step S407, the service identification ID database 502 is referred to. In step S408, a free ID is issued. In step S409, the issued free ID and the reissue service identification ID corresponding to the target service are determined. The issued service identification ID is registered in the customer-specific terminal service database 14 and the service identification ID database 502.

  The reissue service identification ID for which registration has been completed is transmitted from the terminal service management server 7 to the IPv6 compatible terminal device 1, and the reissue service identification ID is written in the memory (RAM 217) of the terminal 1 in S411. Using the reissue service identification ID, the IPv6 compatible terminal device 1 sets the service identification ID to the host address in S170, and starts the process of generating a global IP address from the service identification ID again.

  As a result of the above global address generation processing, the IPv6 compatible terminal device 1 enables a new service if the global IP address generated based on the service identification ID registered at the sales site 16 is duplicated in the user site (LAN 19). The identification ID is received from the terminal service management server 7, and a global IP address that does not overlap is generated.

[Service use protocol using service identification ID]
The service use protocol using the service identification ID is the same as that shown in FIG. 8 except for the following points.

  That is, in S179, as in the first embodiment, the terminal service management server 7 extracts the source address from the IPv6 packet for which a connection request has been made, and performs M-ID filtering and D-ID filtering.

  Further, S180, S183 to S188 in FIG. 8 are unnecessary, and when the secondary authentication is approved from the D-ID by the D-ID filtering, the login to the corresponding service directory having the usage authority is permitted. In S181, the corresponding service is searched from the customer-specific terminal service database 14, and thereafter, as described above, the states of S182 and S189 are changed, and the service available to the IPv6-compatible terminal device 1 by the contract at the time of sale. I will provide a.

  The second device (IPv6-compatible terminal device 1) is configured such that the first address corresponding to the service received from the first device (terminal service management server 7) overlaps in the network to which the second device is connected. (S173 in FIG. 15), in order to determine a second address that does not overlap, the third address (address generated based on the MAC address) is used as the source address to communicate with the first device (S404). , S411). When the source address of the service request is the first address and when the first device (terminal service management server 7) is the second address, the first device (IPv6-compatible terminal device 1) ).

1 is an overall system configuration diagram according to an embodiment of the present invention. 2 is a configuration diagram of a LAN 29. FIG. It is a block diagram of the terminal service provision site 6. FIG. It is a block diagram of the IPv6 corresponding | compatible terminal device 1. FIG. It is a protocol figure of service ID issue processing. It is a production | generation flowchart of the global address in a user site. It is a block diagram of the IPv6 host address part produced | generated from service ID. It is a service utilization protocol figure using service identification ID. It is a block diagram of a terminal manufacturing factory site. It is a host address block diagram of an Example. It is a processing flow figure of M-ID and D-ID setting in the terminal manufacture factory site in Example 1. FIG. It is a flowchart of the registration process of the default host address in the terminal manufacture factory site in Example 2. It is a flowchart of the customer information registration process by the default host address in the sales management site in Example 2. FIG. 10 is a flowchart of designated service host address issuing processing in the second embodiment. FIG. 10 is a flowchart of global address generation at a user site in the third embodiment.

Explanation of symbols

1 IPv6 compatible terminal device 6 Terminal service providing site 7 Terminal service management server

Claims (6)

A service providing method in which a first device provides a service to a second device,
The second device converts the first address to the second address when the first address corresponding to the service received from the first device is duplicated in the network to which the second device is connected. ,
The first apparatus provides the service to the second apparatus when the source address of the service request is the first address and the second address. Method.   2. The method of claim 1, wherein the first address and the second address include predetermined values, and the first device is confident that the address of a service request transmission source includes the predetermined value. A service providing method characterized by providing the service.   2. The first device according to claim 1, wherein the second device has a third address, and uses the third address as a source address when communicating with the first device to determine the first address. A service providing method characterized by the above. A service providing method in which a first device provides a service to a second device,
When the first address corresponding to the service received from the first device is duplicated in the network to which the second device is connected, the second device determines the second address that is not duplicated. Communicate with the first device using the address of 3 as the source address,
The first apparatus provides the service to the second apparatus when the source address of the service request is the first address and the second address. Method.   2. The service providing method according to claim 1, wherein the second device uses the third address as a source address when communicating with the first device to determine a first address. . A service providing device,
A reverse conversion means for performing reverse conversion of the second address when the source address of the service request is the second address converted from the first address;
A service providing apparatus comprising: providing means for providing a service corresponding to the first address obtained by the reverse conversion.

Images