JP4374302B2 - Data communication device - Google Patents

Description

  The present invention relates to a data communication apparatus and access server used in a packet communication system and a mobile communication system, and a computer program.

  In recent years, in mobile communication, data communication such as transmission / reception of mail using a mobile terminal, access to the Internet, and Web browsing has been actively performed. In order to realize such data communication, Pont is standardized by RFC1661 as disclosed in Non-Patent Document 1 for data communication between a mobile radio terminal and a data communication device (hereinafter referred to as PDSN). It is known that the to Point Protocol (hereinafter referred to as PPP) is used. PPP consists of functions for negotiating settings necessary for data communication, authentication of users to access, and notification of IP addresses and DNS addresses.

  In addition, Internet Protocol (hereinafter referred to as IP) is used as a network layer to be transferred by PPP, and currently used IP is IPv4, and a 32-bit address (IP address) is used as a source / destination. ing. In Internet communication, a global IP address that uniquely assigns a 32-bit IP address to each source / destination is adopted, and each source / destination is determined according to the IP address. However, the Internet world is rapidly expanding, and the limited address space of IPv4, that is, the exhaustion of global addresses has become a problem. To solve this problem, the Internet Engineering Task Force (hereinafter referred to as IETF) has proposed a new Internet Protocol version 6 (hereinafter referred to as IPv6) that expands the IP address space from 32 bits to 128 bits as the next generation IP address. Yes.

  FIG. 12 is a diagram showing the format of the IPv6 address. The upper 64 bits of the IPv6 address are path information (network prefix: hereinafter referred to as Prefix) 1110, and the lower 64 bits are an interface for identifying the network interface of the node in the subnetwork to which the node is connected. This is an identifier (hereinafter referred to as Interface ID) 1120. Of Prefix 1110, the upper 48 bits are called Public Topology 1111 and are used for the Internet provider route, and the lower 16 bits are called Site Topology 1112 and used for local routing. The interface identifier 1120 is unique within the subnetwork, and a MAC address or the like is used as the interface identifier.

  IPv6 communication using PPP is performed using the IPv6CP procedure defined in RFC2472, as disclosed in Non-Patent Document 2. This IPv6CP procedure defines a procedure for notifying the communication partner of the Interface-ID 1120 of the IPv6 address.

  In the X.S0011-C reference model of 3rd Generation Partnership Project 2 (hereinafter referred to as 3GPP2), a mobile terminal, a radio network that is wirelessly connected to the mobile terminal, a PDSN that is PPP-connected to the mobile terminal, and a RADIUS that PDSN accesses during authentication, Consists of an Internet provider and an IP network connected to the Internet. When the PPP connection is completed between the mobile terminal and the PDSN, the mobile terminal can connect to the IP network via the provider network and the PDSN 200 to perform Internet communication and content browsing. When performing IPv6 connection, it is known that the PDSN must make the prefix assigned to the mobile terminal unique for each PPP ring, and the prefix notifies the mobile terminal by router advertisement (hereinafter referred to as Router Advertisement). Is also known.

  As an IP address assignment in a system to which the 3GPP2 (CDMA200) model is applied, Japanese Patent Application Laid-Open No. 2004-104800 “IP Address Assignment Method for Terminal in Code Division Multiple Access System” is disclosed as Patent Document 1, but regarding IPv6 address assignment, Not mentioned.

Japanese Patent Application Laid-Open No. 2004-104800 “IP Address Assignment Method for Terminal in Code Division Multiple Access System” 3GPP2 X. S0011-C cdma2000 Wireless IP network Standard RFC1661 Point to Point Protocol RFC2472 IP Version 6 over PPP RFC2865 Remote Authentication Dial In User Service (RADIUS) RFC3315 Dynamic Host Configuration Protocol for IPv6 (DHCPv6)

  In the conventional network connection method shown in Non-Patent Document 1 described above, it is defined that the prefix of the mobile terminal for each PPP link is uniquely assigned. This is because the PDSN needs to identify a PPP link using a prefix when forwarding an IPv6 packet. Further, Non-Patent Document 1 stipulates that a prefix assigned to a mobile terminal is included as a Framed-IPv6-Prefix in an Access-Accept transmitted from Home-RADIUS to the PDSN. Access-Accept is an interface defined in IETF RFC2865 as disclosed in Non-Patent Document 3, and uses the format shown in FIG. Furthermore, the PDSN extracts the prefix from the Access-Accept Framed-IPv6-Prefix received from Home-RADIUS, and notifies the mobile terminal by including it in the Router Advertisement message. The mobile terminal that has received the notification can generate an IPv6 global address and can perform IPv6 communication to the IP Network.

  However, if this procedure is used, in order to make the prefix unique for each PPP link, it is necessary to manage the prefix so that it is unique for each PPP ring in Home-RADIUS. In addition, Home-RADIUS may be installed for each 3rd vendor, and a plurality of Home-RADIUS exist in different 3rd vendors. In this case, it is difficult in operation to set a plurality of Home-RADIUS so that prefixes do not overlap. Further, since the 64-bit prefix assigned to the mobile terminal is different for each PPP link, the route information of the IPv6 router in the IP Network connected to the PDSN is the route corresponding to the number of PPP links as shown in FIG. Information is required, and routes that are characteristic of IPv6 cannot be aggregated.

  FIG. 14 is a route table necessary for determining a route from the IPv6 router in the IP Network to the PDSN, and stores information on the destination prefix 401 and the next transfer destination next hop 402. The destination prefix 401 stores the 64-bit prefix 403 assigned to the mobile terminal, and the IPv6 address of the PDSN is stored in the next hop, so that the IPv6 packet addressed to the mobile terminal is transferred from the IP network to the mobile terminal via the PDSN. can do.

  An object of the present invention is to eliminate the above-mentioned drawbacks of the conventional techniques, to make it easy for Home-RADIUS to manage the operation of a prefix without being aware of the uniqueness of each PPP link, and a data communication apparatus notifies a mobile terminal. By providing an apparatus for generating a prefix, uniqueness for each PPP link is ensured. In addition, the present invention provides an IPv6 address assignment method with enhanced route aggregation effect.

  In order to achieve the above object, the first invention of the present invention performs the connection approval of the communication terminal device to the authentication server using the PPP (Point to Point Protocol) via the provider network, and the connection approval. A data communication device that connects the communication terminal device to the IP network later, an extraction unit that extracts a prefix notified from the authentication server, a first generation unit that generates a device management identifier, and a second that generates a PPP identifier. A third generation unit that generates one prefix by combining the generation unit, the prefix extracted by the extraction unit, the device management identifier generated by the first generation unit, and the PPP identifier generated by the second generation unit; Notification means for notifying the mobile terminal of the prefix generated by the third generation means.

  As described above, by using the means for solving the problem, it is possible to generate an IPv6 address prefix that satisfies the uniqueness of each PPP ring in the data communication apparatus. As a result, Home-RADIUS can manage the Prefix assigned to the mobile terminal without considering uniqueness. In addition, the data communication apparatus can reduce the number of route information of the IPv6 router by generating and notifying the prefix having the route aggregation effect.

Hereinafter, the configuration and operation of the data communication device of the present invention and the IP address management method will be described in detail with reference to the drawings.
FIG. 1 is a network configuration diagram showing a configuration example of a mobile communication system to which the present invention is applied.
The mobile communication system includes a mobile terminal 100 or 110, a base station 120 connected to the mobile terminals 100 and 110 via a radio link, a radio management apparatus 130 that performs radio management, and a data communication apparatus according to the present invention that is PPP-connected to the mobile terminal 100. (Hereinafter, referred to as PDSN) 200 or 300, PDSN 200 or 300, Home-RADIUS 600 or 650 accessed via Proxy-RADIUS 500 at the time of user authentication, and IP Network 700.

  The IP Network 700 performs IPv6 communication, and IP packets are transferred by a plurality of IPv6 routers (not shown). When the PPP connection 106 is completed, the mobile terminal 100 is connected to the IP Network 700 (for example, the Internet) via the device management apparatus 130, the PDSN 200, and the IPv6 router 400, and can perform Internet communication and content browsing. The provider network 140 is a network managed by a general service provider, and the PDSN 200 and the Proxy-RADIUS 500 are often managed by the service provider. The mobile terminal 100 starts the PPP connection establishment 106 with respect to the PDSN 200 by performing a connection start operation, and can transmit and receive data after the PPP connection is completed.

  FIG. 2 is a functional configuration diagram of the PDSN 200. The PDSN 200 includes a network unit 210 or 220 having an external interface with the provider network 140, a control unit 240 that performs protocol processing such as PPP, and a data storage unit 230 that stores necessary information such as statistical information and billing information.

  The network unit 210 includes a transmission path interface 211 and a bus controller 212, and has a function of transferring data received from the outside to the control unit 240 via the device bus 234. In addition, when data transmitted from the control unit 240 is transmitted to the external interface, the data is transferred via the network unit 210. The network unit 210 has one or a plurality of 220, and can select to separate or share the external interface for the provider network 140 and the IP network 700.

  The control unit 240 stores a bus controller 242 that performs access arbitration between the device bus 234 and the processor bus 235, a processor 243 that operates software, a work area necessary for software operation, table storage, program storage, and externally received packets. A memory 241 for improving the processor capacity, a cache memory 244 for improving the processor capacity, and a processor bus 235 for connecting them. The data storage unit 230 includes a bus controller 231 that performs access arbitration with the device bus 234, a hard disk or flash memory 232 that stores programs, and a disk control 233 that controls the hard disk or flash memory 232.

  FIG. 3 is a block diagram showing a software configuration 2000 that operates on the processor 243, and the RP that establishes the PPP processing 2100, the radio management apparatus 130, and the RP session 132 that performs PPP negotiation on the operation system (hereinafter referred to as OS) 2800. Session processing 2400, authentication processing 2200 for performing authentication processing, charging processing 2300 for collecting charging information, IP processing 2500 for performing Router Advertisement processing, and Mobile IP processing 2600 for performing FA (Foreign Agent) processing are operating. The PPP process 2100 has the call management table shown in FIG. 9 in order to manage information on mobile terminals. This management table stores information necessary for connection. For example, a network access identifier (hereinafter referred to as NAI) 2111 of the mobile terminal, and an international mobile subscriber identity (hereinafter referred to as IMSI) as the wireless management information 2112 or the like. Stored. The number of rows in the table matches the number of PDSN mobile terminals connected. This table can be accessed by other processes such as the RP session process 2400.

  The software in FIG. 3 performs processing according to the flow procedure in FIG. 4 as connection with the mobile terminal. This flow starts from Step 2001 when there is an R-P session 132 request from the radio management apparatus 130, and proceeds to Step 2401. In step 2401, the RP session processing 2400 checks whether the PDSN 200 has a free capacity for accepting the connection of the mobile terminal 100 which is a new connection. The RP session processing 2400 searches the call management table of FIG. 9 as an empty capacity check to determine whether there is an empty line. If there is an empty line as a search result, the acceptance is made possible and the process goes to Step 2402, and if there is no empty line, the acceptance is refused and the process goes to Step 2403. In step 2403, a process (Re-Direct) is performed to notify the radio management apparatus 130 that there is no free space in the PDSN 200, and the process proceeds to step 2002 and ends.

  On the other hand, if the process proceeds to step 2402, the connection process is started, and the RP process 2402 is repeated until the RP session is established in step 2404. When the establishment is completed, the process proceeds to step 2101. In step 2101, PPP processing 2100 starts, and LCP negotiation 101 is first started. When the LCP negotiation 101 is completed, the process proceeds to the authentication process 2200 in step 2201. In the authentication process 2200, an authentication request is sent to the Home-RADIUS 600 via the Proxy-RADIUS 500, and the process proceeds to Step 2202. If the authentication result is successful, the process proceeds to Step 2102. If authentication fails in step 2202, the process proceeds to step 2203 and disconnection or reconnection occurs, and the process proceeds to step 2002. Whether to disconnect or reconnect is selected by the device management 2700. In step 2102, the process returns to the PPP processing 2100 and the IPv6CP negotiation 104 starts. When the IPv6CP negotiation 104 is completed, the process proceeds to step 2501. The IP process 2500 performs a process of transmitting the Router Advertisement 105 to the mobile terminal, and the process proceeds to step 2002 to complete the connection.

  Next, the operation will be described in detail with reference to the connection sequence of the mobile terminal 100 in FIG. The mobile terminal 100 first establishes a radio session 131 with the base station 120 and the radio management apparatus 130 when there is a connection request from the user. When the radio management apparatus 130 establishes the radio session 131, connection of the RP session 132 is started with the PDSN 200. The radio session 131 and the RP session 132 are dedicated signaling necessary for mobile communication.

  When the PDSN 200 receives a request for establishing the RP session 132 from the radio management apparatus 130 from the external interface, the PDSN 200 passes through the network unit 210 and is stored in the memory 241 via the apparatus bus 234. After the storage, the packet is decoded and processed by the software 2000 running on the processor 243. If it is determined that the request is for establishing the RP session 132 as a result of the decryption, the connection flow of FIG. As described above, in step 2401, the free space of the PDSN is checked, so that the RP session processing 2400 searches for a free line in the call management table of FIG. As a result of the search, when it is determined that the row with No 1 is empty, the wireless management information included in the request for establishing the RP session 132 is stored in the row 2121 with No 1.

  When the storage is completed, the RP session processing 2400 transmits an acceptance permission response to the radio base station 130 via the control unit 240, the device bus 234, and the network unit 210, and proceeds to step 2101. In step 2101, the PPP processing 2100 transmits the LCP negotiation packet 101 to the mobile terminal 100. In other words, it is the start of PPP negotiations.

  On the other hand, when the mobile terminal 100 establishes the radio session 131, the mobile terminal 100 starts PPP negotiation and transmits the LCP negotiation packet 101 to the PDSN 200. In the LCP negotiation 101, authentication types such as MRU (Maximum-Receive-Unit), CHAP, and PAP necessary for connection are determined. When the LCP negotiation 101 is completed, the mobile terminal 100 transmits an authentication request 102 to the PDSN 200.

  The PDSN 200 transfers the received authentication request 102 to the memory 241 in the same manner as described above, and performs analysis / processing by the software 2000 operating on the processor 243. This processing proceeds from step 2101 to step 2201 in the flow of FIG.

  The authentication process is a connection permission approval of the mobile terminal 100, and a RADIUS interface defined by IETF RFC2865 is used between the PDSN 200 and the Proxy-RADIUS 500 or Home-RADIUS 600, 650. The RADIUS interface includes an authentication request Access-Request and an authentication response Access-Accept or Access-Reject, and uses the format shown in FIG. In this figure, Code 510 is a field for distinguishing packet types such as Access-Request and Access-Accept, Identifier 511 is used for binding Access-Request and Access-Accept, and Attribute 514 is information necessary for authentication. This is a field for storing (for example, NAI or password).

  The authentication process 2200 creates an Access-Request, and transmits an Access-Request 501 to the Proxy-RADIUS 500 in a system where Proxy-RADIUS exists. In some systems, Proxy-RADIUS 500 does not exist and only Home-RADIUS is available. In this case, an Access-Request is transmitted to Home-RADIUS 600 or 650.

  The Proxy-RADIUS 500 that has received the Access-Request 501 relays the received Access-Request 501 to the appropriate Home-RADIUS 600 or 650. The Home-RADIUS 600 or 650 decodes the Access-Request 502 received from the Proxy-RADIUS 500 and determines whether to permit access of the mobile terminal 100.

  If the Home-RADIUS 600 or 650 determines to permit, the Home-RADIUS 500 or 650 includes information necessary for connection, for example, a prefix or Interface-ID necessary for generating an IPv6 global address in the Access-Accept 503 and transmits the information to the Proxy-RADIUS 500. At this time, the Prefix is called Framed-IPv6-Prefix and is stored in the Access-Accept Attribute 514.

  FIG. 7 shows the format of Framed-IPv6-Prefix. There is a Prefix-Length field 521 indicating the length of the Prefix, and the Prefix 520 can be stored in a variable manner. A 48-bit prefix is stored in this prefix field. Further, depending on the system, a 64-bit prefix may be stored.

  After receiving Access-Accept 503, Proxy-RADIUS 500 relays to PDSN 200 that is the source of Access-Request 501. After the PDSN 200 transfers the Access-Accept 504 to the memory 241, the authentication processing 2200 analyzes it.

  If the authentication response is an authentication success, the authentication processing 2200 transmits an authentication success 103 to the mobile terminal 100 and proceeds to step 2102 in FIG. Also, the authentication process 2200 acquires and holds a 48-bit prefix 1101 from the Framed-IPv6-Prefix 520 included in the Access-Accept 504. In the next step 2102, IPv6CP processing is performed and IPC6CP negotiation 104 is performed with the mobile terminal 100. In IPv6CP negotiation 104, the header compression type, Interface-ID, and the like are determined.

  On the other hand, the mobile terminal 100 starts the IPv6CP negotiation 104 after receiving the authentication success 103. When the IPv6 CP negotiation 104 is completed, the PDSN 200 proceeds to step 2501 and the IP processing 2500 generates a prefix to be notified by the Router Advertisement 105 in the flow of FIG.

  Next, the flow of FIG. 11 will be described. In step 2511, the prefix 1101 held in the authentication processing 2200 in step 2201 in FIG. 4 is acquired. Next, in step 2512, the bit length of the prefix 1101 is checked. As a result of checking, if it is 48 bits or less, the process proceeds to step 2513. If it exceeds 48 bits, the process proceeds to PDS step 2518. In step 2513, padding processing is performed when the number of bits is less than 48 bits. Padding is performed until 48 bits are satisfied with a value determined in advance by the system, and the process proceeds to step 2514. If the prefix length is 48 bits, the process proceeds to step 2514 without padding. In step 2518, 481 bits 1101 are extracted from the prefix exceeding 48 bits, and the process proceeds to step 2514.

  In step 2514, the device identifier 1102 is acquired from the device management 2700 and held. For example, the device identifier uses PDSN 200 with a number such as (0001) bit and PDSN 300 with a number (0010) bit. The device identifier 1102 managed by the device management 2700 may be set in advance or downloaded from the maintenance center. After obtaining the device identifier 1102, the IP processing 2500 proceeds to step 2515.

  In step 2515, the PPP identifier 1103 is acquired from the PPP processing 2100. The PPP identifier 1103 is a number equal to No in the call management table of FIG. 9 managed by the PPP processing 2100. No is a unique number that does not overlap and can be used as the PPP identifier 1103. After obtaining the PPP identifier 1103, the process proceeds to step 2516.

  In step 2516, the prefix 1101 acquired in step 2511, the device identifier 1102 acquired in step 2514, and the PPP identifier 1103 acquired in step 2515 are combined to generate the 64-bit prefix of FIG. This Prefix is given to the mobile terminal 100. In the above-described embodiment, 4 bits are provided as the device identifier 1102 and 12 bits are provided as the PPP identifier 1103. However, the ratio can be determined by the system.

  The Router Advertisement 105 has a role of notifying the mobile terminal 100 of the Prefix. FIG. 8 shows a format of the Prefix option notified by the Router Advertisement 105. The Prefix field 1100 stores the 64-bit Prefix generated in Step 2516 of FIG.

  When the mobile terminal 100 receives the prefix 1100 by the router advertisement 105, the mobile terminal 100 can generate the 128-bit global IPv6 address 108 together with the interface-ID 1120 determined by the IPv6CP negotiation 104, and can perform IPv6 communication through the PPP communication 106.

  On the other hand, the PDSN 200 performs path information exchange 701 with an IPv6 router in the IP Network 700. At this time, the PDSN 200 notifies the prefix of the mobile terminal 100 as 52 bits of Home-RADIUS notification Prefix 1101 + device identifier 1102 on the route information.

  FIG. 13 is a route table of an IPv6 router in the IP Network 700. When the path information 701 is received from the PDSN 200, the 52 bits 411 of the Home-RADIUS notification prefix 1101 + device identifier 1102 are registered in the destination IPv6 Prefix 410, and the IPv6 address 413 of the PDSN 200 is registered as the next hop 412, thereby accommodating the PDSN 200. Route information addressed to a plurality of PPP links can be realized by a single piece of route information. These pieces of route information can be notified using a dynamic route protocol such as RIPng, or preset as static settings.

  As described above, the Home-RADIUS 600 or 650 only needs to manage the 48 bits 1111 of the Public Topology portion as a prefix. The device identifier 1102 is notified to the prefix 1101 notified from the Home-RADIUS 600 by the PDSN 200, and a PPP that is different for each PPP link. By assigning the identifier 1103, a 64-bit prefix that guarantees the uniqueness of each PPP link can be generated. As a result, even when there are multiple Home-RADIUS, it is no longer necessary to manage with the awareness of each other's prefix. In addition, since the upper 52 bits of the mobile terminals 100 and 110 and a plurality of prefixes are common with the Home-RADIUS notification prefix 1101 + device identifier 1102, the IP Network 700 can communicate if the IPv6 packet is routed to the PDSN 200 based on the 52 bits. Can do. This means that the route concentration effect has increased.

  FIG. 15 is a network configuration diagram showing another configuration example of a mobile communication system including the data communication apparatus of the present invention. The system is characterized in that a DHCP server 900 is added to the system of FIG.

  The configuration of the PDSN 200 or 300 is the same as that in FIG. 2, and the software configuration that operates in the processor 243 is as shown in FIG. This is different in that DHCP-Relay 2900 is added to the configuration of FIG. The DHCP-Relay 2700 is software having an IETF RFC3315 DHCP-Reply-Agent function as disclosed in Non-Patent Document 4, and has a relay function for a DHCP request from the mobile terminal 100 to the DHCP server.

  Next, the connection sequence of the mobile terminal 100 will be described with reference to FIG. The mobile terminal 100 first establishes a radio session 131 with the base station 120 and the radio management apparatus 130 when there is a connection request from the user, and then starts an LCP negotiation 101 with respect to the PDSN 200. Thereafter, the connection is made in the same sequence as in the prior art until the PPP communication 106 becomes possible.

  When the PPP connection is completed, the mobile terminal 100 acquires an IPv6 Prefix using DHCPv6. At the time of acquisition, the mobile terminal 100 transmits DHCPv6 Solicit 910 to the PDSN 200.

  The PDSN 200 performs processing specified by RFC 3315 in the DHCP Relay 2900, and transfers the DHCPv6 Solicit to the DHCP server 900. Upon receiving the DHCPv6 Solicit 911, the DHCP server 900 transmits a DHCPv6 Advertisement 912 to the mobile terminal 100 via the PDSN 200.

  Upon receiving the DHCPv6 Advertisement 913, the mobile terminal 100 transmits a DHCPv6 Request 914 to the DHCP server 900 via the PDSN 200. The DHCP server 900 puts a 48-bit prefix 1104 managed by the system into the DHCP-Reply 916 and transmits it to the PDSN 200.

  The PDSN 200 that has received the DHCP-Reply 916 combines the device identifier 1102 and the PPP identifier 1103 with the Prefix 1104 included in the DHCP-Reply 916 to generate the 64-bit Prefix in FIG. Thereafter, the prefix is entered in the DHCP-Reply 917 and transmitted to the mobile terminal 100. When receiving the DHCPv6-Reply 917, the mobile terminal 100 generates an IPv6 global address 918. When the mobile terminal 100 generates the IPv6 global address, the mobile terminal 100 can perform IPv6 communication via the PDSN 100.

  As described above, the DHCP server can manage the Prefix without being aware of the uniqueness of the PPP link. Further, since the prefix configuration is similar to the system of FIG. 1 described above, there is also an effect of route concentration.

It is a network block diagram showing the structure of the mobile communication system to which this invention is applied. It is a block diagram of a data communication apparatus (PDSN). It is a software block diagram implemented in the data communication apparatus. It is the connection processing flow of the software mounted in the data communication apparatus. It is a connection sequence diagram of a mobile communication system to which the present invention is applied. It is a format diagram of Access-Request and Access-Accept packets. It is a format diagram of Framed-IPv6-Preefix included in Access-Accept. It is a format diagram of the Prefix option included in Router Advertisement. It is a block diagram of the call management table used by the software mounted in the data communication apparatus. It is a block diagram of Prefix produced | generated with a data communication apparatus. It is a production | generation flowchart of Prefix produced | generated with a data communication apparatus. It is a block diagram of the IPv6 address prescribed | regulated by the IETF recommendation. It is the routing table of the external IPv6 router produced | generated by the data communication apparatus. It is the routing table of the external IPv6 router produced | generated by the conventional data communication apparatus. It is a network block diagram showing another structure of the mobile communication system to which this invention is applied. FIG. 16 is a connection sequence diagram illustrating the operation of the system of FIG. 15. It is a block diagram which shows another structure of the software mounted in a data communication apparatus. It is a block diagram which shows another structure of Prefix which a data communication apparatus produces | generates.

Explanation of symbols

100: Mobile terminal 120: Base station 130: Radio management device
140: Provider network 200, 300: Data communication device (PDSN)
500: Proxy RADIUS, 600, 650: Home RADIUS,
700: IP Network 1102: Device identifier generated by the data communication device,
1103: PPP identifier generated by the data communication apparatus 2000: Software configuration of the data communication apparatus

Claims (4)

It has a plurality of data communication devices that perform connection approval of the communication terminal device by inquiring to the authentication server using PPP (Point to Point Protocol) via the provider network, and connect the communication terminal device to the IP Network after connection approval. The data communication device in a communication system ,
Extraction means for extracting the first prefix notified from the authentication server;
First generation means for generating a device management identifier of the data communication device ;
Second generation means for generating a PPP identifier composed of a number uniquely assigned to each PPP link ;
A IPv6 address prefix is generated by combining the first prefix extracted by the extracting means, the device management identifier generated by the first generating means, and the PPP identifier generated by the second generating means. Generating means;
A data communication apparatus comprising: a notification unit configured to notify the communication terminal apparatus of a prefix of the IPv6 address generated by the third generation unit. 2. The data communication apparatus according to claim 1, wherein the first prefix extracted by the extracting means is a prefix notified by an Access-Accept Framed-IPv6-Prefix. 3. The data communication device according to claim 1, wherein the device management identifier generated by the first generation unit is configured with a number different for each data communication device. A first Prefix extracted by the extraction means, that the first value is generated unit combines the generated device management identifier, notifies the external IPv6 router as a route information of the client devices connected by PPP data communication apparatus according to any one of claims 1 to 3, characterized.

Images