JP6504609B2 - Address generation method and apparatus, program, and address delivery method - Google Patents

Description

  The present invention relates to a technology for generating an address to be assigned to a packet in packet communication.

  In the current carrier network, there is a problem that different addresses are delivered to the terminals each time the terminals connect to different carrier networks or different access networks. As a result, the application provided via the network needs to store and manage the IP (Internet Protocol) address of the terminal, and the session is maintained when the terminal is switched to a different carrier network or a different access network. There is a problem such as disappearing.

R. Droms, "Dynamic Host Configuration Protocol", RFC 2131, IETF, March 1997, [online], [search on January 6, 2016], Internet <URL: https://tools.ietf.org/ html / rfc2131> "Guidelines for 64-bit Global Identifier (EUI-64) Registration Authority", IEEE, [online], [search on January 6, 2016], Internet <URL: http://standards.ieee.org/regauth/ oui / tutorials / EUI64.html> R. Hinden, 1 other person, "IP Version 6 Addressing Architecture", RFC 4291, IETF, February 2006, [online], [Search on January 6, 2016], Internet <URL: https: // tools .ietf.org / html / rfc4291> "Network architecture", 3GPP TS 23.002, 3GPP Std., Rev. 13.3.0, September 2015 "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access", 3GPP TS 23.401, 3GPP Std., Rev. 13.4.0, September 2015 "Numbering, addressing and identification", 3GPP TS 23.003, 3GPP Std., Rev. 13.3.0, September 2015 R. Hinden, 1 other person, "Unique Local IPv6 Unicast Addresses", RFC 4193, IETF, October 2005, [online], [search on January 6, 2016], Internet <URL: https: // tools .ietf.org / html / rfc4193>

  Although DHCP (Dynamic Host Configuration Protocol) is known as an existing technology for address delivery (see Non-Patent Document 1), when delivering a fixed address to a terminal, the MAC (Media Access Control) address of the terminal and the fixed delivery There is a problem that the association information of the IP address has to be held, and in the case where different carrier networks or access networks issue the same address, the association information has to be shared in advance.

  In the IPv6 link local address, there is an EUI-64 method that determines a stateless address based on the MAC address (see Non-Patent Document 2 and Non-Patent Document 3), but the MAC address of the terminal may be changed. There is a problem that inconsistencies occur when there are duplicate addresses.

  The present invention has been made in view of the above circumstances, and an object thereof is to provide an address generation method, apparatus and program for generating stateless and unique addresses on a network in a stateless manner, and an address delivery method. It is in.

In order to achieve the above object, according to the present invention, in a network environment in which a subscriber's terminal is connected to any carrier network among a plurality of carrier networks , an address generation function unit is common among a plurality of carrier networks. A subscriber identifier or terminal identifier to be used is acquired from the terminal for which uniqueness is secured even among different carriers, and common among the plurality of carrier networks based on the acquired subscriber identifier or terminal identifier To generate an immutable and unique IP address that can be used for

  Furthermore, in the present invention, a second identifier address based on a subscriber identifier acquired from a terminal or a carrier network based on a terminal identifier, and a second address based on an identifier identifying an arbitrary group and an invariant and unique first address portion. And generating an IP address having an address section.

  Further, the present invention is characterized in that the terminal authentication means or connection processing means pays out the IP address generated as described above to the terminal at the time of terminal authentication or connection processing by the carrier network.

  According to the present invention, since it is based on a terminal identifier and a subscriber identifier that are commonly used among carrier networks and guaranteed to ensure uniqueness, there is no invariance that is not affected by the carrier network of the connection destination Unique IP address can be generated. Further, in addition to the above, it is possible to generate a subnettable invariable and unique IP address required for a Closed User Group (CUG), a Virtual Private Network (VPN), a route control, and the like. In addition, when connecting a terminal to a carrier network, in conjunction with terminal authentication or connection processing by the carrier network, an address can be generated by the address generation method, and unchanged and unique IP addresses can be paid out even in different carrier networks. .

Basic configuration of network system Basic configuration of network system according to another example Diagram explaining the operation of the address generation function Example of generated IP address (IPv6 unique local address) Example of generated IP address (IPv6 global address) Example of IP address generated from IMSI in mobile network (IPv6 unique local address) IP address delivery procedure example (generated dynamically in HSS) Detailed sequence diagram of IP address issuing procedure (generated dynamically in HSS) Example of IP address delivery procedure (pre-stored in HSS) IP address delivery procedure example (generated dynamically in MME) Example of IP address delivery procedure (generated dynamically in S-GW) Example of IP address delivery procedure (generated dynamically at P-GW) IP address delivery procedure example (generated dynamically in PDN)

  A network system according to an embodiment of the present invention will be described with reference to the drawings. In the present embodiment, the case where the present invention is applied to a mobile network adopting an LTE (Long Term Evolution) architecture as an example of a network system will be described.

  First, a basic configuration of a network system according to the present embodiment will be described with reference to FIG. In the LTE architecture, a subscriber information management function unit 110 called HSS (Home Subscriber Server) which stores subscriber information and performs terminal authentication in a carrier network 100, and MME (Mobility Management Entity) is called a terminal (UE: A mobility management function unit 120 that performs mobility management of the User Equipment) 10, a relay node 130 called an S-GW (Serving-Gateway) and relaying communication of the terminal (UE) 10, and a P-GW (Packet data network- A gateway 140, called a gateway, terminates the communication of a terminal (UE) 10 and relays it to a packet data network (PDN) 200 such as the Internet, and a base transceiver station (BTS) calls a terminal (UE) 10 in a wireless section. A base station 150 is provided. For details of the LTE architecture, refer to Non-Patent Documents 4 to 6.

  In the above, for one carrier network 100, a terminal (UE) 10, a base station (BTS) 150, a mobility management function unit (MME) 120, a subscriber information management function unit (HSS) 110, a relay node ( Two or more S-GWs 130 and two gateways (P-GW) 140 may be provided. Also, the carrier network 100 may also be two or more. Each of the functional units may be implemented as hardware, or a program may be installed and implemented on general-purpose hardware.

  The terminal (UE) 10 has a function of communicating with a base station (BTS) and requesting attachment to the carrier network 100. Also, the terminal (UE) 10 is equipped with a SIM (Subscriber Identity Module) card specified by the carrier, and the SIM card is a subscriber identifier IMSI (International Mobile Subscriber Identity), an APN for selecting a connection destination. Information such as (Access Point Name) is stored. Here, the subscriber identifier, IMSI, is an identifier that identifies the subscriber worldwide. Further, since the SIM card is constituted by an IC card having high tamper resistance, IMSI is suitable as an input identifier (described later) of the present invention. The terminal (UE) 10 also stores IMEI (International Mobile Equipment Identity), which is a terminal-specific identifier preset by the manufacturer, and this terminal identifier is used as an input identifier (described later) of the present invention. You may use. The subscriber identifier and the terminal identifier are commonly used among carrier networks, and uniqueness is secured even for different carriers.

  The subscriber information management function unit (HSS) 110 has information on the subscriber who has contracted with the carrier, and information on which group the subscriber has joined. The mobility management function unit (MME) 120 has a function of inquiring the subscriber information management function unit (HSS) 110 of the terminal (UE) 10 that has requested attachment, and requesting group authentication if necessary. The relay node (S-GW) 130 has a function of transferring communication from the base station (BTS) 150 to the gateway (P-GW) 140. The gateway (P-GW) has a function of transferring communication from the relay node (S-GW) to a packet data network (PDN) 200 such as the Internet. The base station (BTS) 150 communicates with the terminal 10, and has a function of notifying the mobility management function unit (MME) of an attach request of the terminal 10, and a function of transferring the communication of the terminal 10 to the relay node (S-GW). Have.

  FIG. 2 shows a basic configuration of a network system according to a modification of the present embodiment. The basic configuration of FIG. 2 integrates the relay node (S-GW) 130 and the gateway (P-GW) into a single entity as an integrated gateway (S / P-GW) 160. The integrated gateway (S / P-GW) 160 is an entity having the functions of both the relay node (S-GW) 130 and the gateway (P-GW) 140, and in this embodiment, the relay node (S-GW) Integrated gateway (S / P-GW) 160 performs the roles of both 130 and gateway (P-GW). Other configurations and their functions are the same as the basic configuration of FIG.

  A characteristic feature of the present invention is that, in the network system described above with reference to FIG. 1 and FIG. 2, fixed and unchanged fixed by different carrier networks with subscriber identifier (IMSI) or terminal identifier (IMEI) as an input identifier. An address generation function unit (ADGen) 170 is provided to generate an IP address statelessly. Although various forms can be considered about the mounting position and operation | movement of an address production | generation function part (ADGen) 170, this is mentioned later.

  First, the function of the address generation function unit (ADGen) 170 will be described in detail with reference to FIG. As shown in FIG. 3, the address generation function unit (ADGen) 170 takes a subscriber identifier (IMSI) or a terminal identifier (IMEI) as a required input identifier, and optionally makes a subnet address identifier an arbitrary input identifier, and does not change. And a unique fixed IP address, here an IPv6 address is generated. Here, any subnet address identifier can be used. For example, in LTE, there is a group identifier called IMSI-Group-ID, which can be used as a subnet address identifier.

  The address generation function unit (ADGen) 170 generates a prefix based on a predetermined bit string based on the input identifier, a Subnet ID (subnet portion) based on a bit string generated based on the subnet address identifier, and the input identifier based on the input identifier. A fixed IP address having an Interface ID (interface unit) composed of a bit string is generated.

  More specifically, the address generation function unit (ADGen) 170 has (1) only a subscriber identifier, (2) only a terminal identifier, (3) a subscriber identifier + a subnet identifier, and (4) a terminal identifier + a subnet. There are four operation modes according to the four cases of the identifier.

  The fixed IP address generated by the address generation function unit (ADGen) 170 is (1) in the case of only the subscriber identifier, the interface unit corresponds to the subscriber identifier 1: 1 and (2) in the case of only the terminal identifier. If the interface unit corresponds to the terminal identifier 1: 1 and (3) the subscriber identifier + subnet identifier, the interface unit corresponds to the subscriber identifier 1: 1 and the subnet unit corresponds to the subnet identifier (4) In the case of terminal identifier + subnet identifier, the interface unit corresponds to the terminal identifier 1: 1 and the subnet unit corresponds to the subnet identifier.

  Next, an example of an algorithm for generating a subnet unit and an interface unit of an IP address from an input identifier by the address generation function unit (ADGen) 170 will be described in detail. Such an algorithm is roughly divided into (A) that does not perform any conversion processing on the input identifier, and (B) that that performs some conversion processing on the input identifier. Each algorithm will be described in detail below.

(A) Direct Embedding (i) Method The identifier is used as an address without conversion.
(Ii) When the identifier bit length> the embedding destination bit length: A part of the digits of the identifier is deleted and adjusted to the embedding destination bit length. In this case, uniqueness is lost. It is desirable to decide in advance which digit to delete.
(Iii) When identifier bit length <embedding destination bit length Allocate an identifier from the beginning and fill the end with an optional value, such as 0 at the end. Alternatively, an identifier is assigned starting from the Nth bit from the beginning, and the part to which the identifier is not assigned is filled with an arbitrary value, such as 0. However, in order to secure uniqueness and invariance, it is desirable to determine in advance what kind of value to fill in.

(B1) Conversion using a one-way function such as a hash function (i) Method An identifier is converted using a hash function, and the conversion result is embedded in an address. The hash function uses an existing one and is not defined in this patent. However, in order to secure uniqueness and invariance, it is desirable to decide in advance which function to use. A one-way function other than the hash function may be used.
(Ii) When the identifier bit length> the embedding destination bit length The output bit length of the hash function is aligned with the embedding destination bit length. In this case, although uniqueness is lost, the possibility of collision of generated addresses is small.
(Iii) When identifier bit length <embedding destination bit length The output bit length of the hash function is aligned with the embedding destination bit length. Alternatively, fill in the shortfall with any value. However, in order to secure uniqueness and invariance, it is desirable to determine in advance what kind of value to fill in.

(B2) Linear conversion (i) method The identifier is converted using a linear conversion function, and the conversion result is embedded in the address. A linear transformation is guaranteed to be generated 1: 1 from the identifier. The linear transformation function uses an existing one and is not defined in this patent. However, in order to secure uniqueness and invariance, it is desirable to decide in advance which function to use. Instead of linear transformation, an encryption function may be used.
(Ii) When the identifier bit length> the embedding destination bit length: A part of the digits of the output of the linear conversion function is deleted to match the embedding destination bit length. In this case, uniqueness is lost. It is desirable to decide in advance which digit to delete.
(Iii) When identifier bit length <embedding destination bit length Align the output of the linear conversion function with the embedding destination bit length. Alternatively, fill in the shortfall with any value. However, in order to secure uniqueness and invariance, it is desirable to determine in advance what kind of value to fill in.

(B3) Prime factorization conversion, compression conversion (i) Method The result of the factorization of the identifier is bit stringed by an arbitrary method and embedded in the address. Alternatively, the bit string obtained by compressing the identifier by an arbitrary compression algorithm is embedded in the address. It is guaranteed that the identifier is generated 1: 1. It is desirable to determine in advance how to make the result a bit string. There is no limitation on the method of factoring.
(Ii) When the bit length of the output of the above conversion> the bit length of the embedding destination A part of the digits of the output of the above conversion are deleted to match the embedding bit length. In this case, uniqueness is lost. It is desirable to decide in advance which digit to delete.
(Iii) When the bit length of the output of the above conversion <the embedding destination bit length The output of the above conversion is aligned with the embedding destination bit length. Alternatively, fill in the shortfall with any value. However, in order to secure uniqueness and invariance, it is desirable to determine in advance what kind of value to fill in.

(B4) Linear transformation by digit shuffling (i) Method The task of exchanging bits of any two digits of the identifier is repeated any number of times. It is desirable to determine in advance how many pairs of digits should be exchanged. Since this transformation is a linear transformation, it is guaranteed to be generated 1: 1 from the identifier.
(Ii) When the identifier bit length> the embedding destination bit length A part of the output of the digit shuffle is deleted and adjusted to the embedding destination bit length. In this case, uniqueness is lost. It is desirable to decide in advance which digit to delete.
(Iii) When identifier bit length <embedding destination bit length Align the output of digit shuffle with the embedding destination bit length. Alternatively, fill in the shortfall with any value. However, in order to secure uniqueness and invariance, it is desirable to determine in advance what kind of value to fill in.

  An example of the IP address generated by the address generation function unit (ADGen) 170 is shown in FIGS. FIG. 4 is a format example when generating an IPv6 unique local address. FIG. 5 is a format example when generating an IPv6 global address. FIG. 6 shows an example of the format for generating an IPv6 unique local address from the terminal identifier IMSI. For details of the IPv6 unique local address, refer to Non-Patent Document 7.

  4 to 6, "line type" identifies the type of access line used when the terminal (UE) 10 of the address delivery destination connects to the network, for example, "fixed", "moving", "others" Set a predetermined value that means any of. In addition, the format illustrated in FIG.4 and FIG.5 can be produced | generated even if it is any algorithm of said (A), (B1)-(B4). On the other hand, the format illustrated in FIG. 6 is generated by the algorithm (A).

  Further, in FIG. 5, the column "Already in advance as an address band used in the system of this patent" is reserved in advance to use this patent as a global unicast address, such as IANA (Internet Assigned Numbers Authority) etc. GRP (Global Routing Prefix) of the address band given by.

  Next, an example of a sequence for delivering the IP address generated by the address generation function unit (ADGen) 170 to the terminal (UE) 10 will be described with reference to FIG. 7 shows an example of dynamically generating an address in the subscriber information management function unit (HSS) 110, FIG. 8 is a detailed sequence diagram thereof, and FIG. 9 generates an address in advance, and the subscriber information management function unit (HSS) FIG. 10 shows an example of dynamically generating an address in mobility management function unit (MME) 120, and FIG. 11 shows an example of dynamically generating an address in relay node (S-GW) 130. FIG. 12 shows an example of dynamically generating an address in the gateway (P-GW) 140, and FIG. 13 shows an example of dynamically generating an address in the PDN 200 to which the terminal (UE) is connected.

  In each example, a terminal (UE) 10, a base station (BTS) 150, a mobility management function unit (MME) 120, a subscriber information management function unit (HSS) 110, and a relay node for one carrier network 100. Two or more (S-GW) 130 and two or more gateways (P-GW) 140 may be provided. Also, the carrier network 100 may also be two or more. Also, as shown in FIG. 2, the relay node (S-GW) 130 and the gateway (P-GW) may be a single entity.

  As shown in FIG. 7, first, the terminal (UE) 10 attaches to the carrier network 100 (step S1). The base station (BTS) 150 notifies the mobility management function unit (MME) 120 of an attach request for the terminal (UE) 10 (step S2). The mobility management function unit (MME) 120 requests the subscriber information management function unit (HSS) 110 for group authentication and location registration (step S3). The subscriber information management function unit (HSS) 110 performs terminal authentication and executes address generation by the address generation function unit (ADGen) 170, and notifies the mobility management function unit (MME) 120 of the authentication result and the generated address. (Step S4). The mobility management function unit (MME) 120 instructs the relay node (S-GW) 130 to connect to the gateway (P-GW) 140, and pays the terminal (UE) 10 the address generated in the connection instruction. It notifies as an address to be issued (step S5). The relay node (S-GW) 130 requests the gateway (P-GW) 140 for connection and notifies an address to be paid out (step S6). The gateway (P-GW) 140 terminates the communication bearer from the terminal (UE) 10 and connects it to the PDN 200, and assigns the notified address to the terminal (UE) 10 (step S7). The terminal (UE) can communicate with the PDN 200 using the issued address (step S8).

  The detailed sequence of the above process will be described with reference to FIG.

  First, the terminal (UE) 10 transmits an attach request to the mobility management function unit (MME) 120 (step S101). Here, the attach request includes information on the terminal / radio (including IMSI and APN). Authentication, concealment, and integrity control are performed between the terminal (UE) 10 and the mobility management function unit (MME) 120.

  Next, the mobility management function unit (MME) 120 transmits a location registration request including the IMSI, the MME identifier, and the like to the subscriber information management function unit (HSS) 110 (step S102). The subscriber information management function unit (HSS) 110 stores location registration information, specifically, the location MME of the terminal (UE) 10 (step S103). Next, the subscriber information management function unit (HSS) identifies the group identification, specifically, the IMSI-Group-ID of the group to which the terminal (UE) 10 belongs using the IMSI of the terminal 10 as a key, as necessary ( Step S104). Next, the subscriber information management function unit (HSS) 110 requests the address generation function unit (ADGen) 170 to generate an address (step S105). This address generation request includes an IMSI and, if necessary, an IMSI-Group-ID. Then, when the subscriber information management function unit (HSS) 110 receives the IP address of the generation result from the address generation function unit (ADGen) 170 (step S106), the subscriber information management function unit (HSS) 110 sends a location registration response to the mobility management function unit (MME) 120. Is sent (step S107). This location registration response includes subscription information (generated IP address, contract APN, etc.).

  Next, the mobility management function unit (MME) 120 selects the relay node (S-GW) 130 and the gateway (P-GW) 140 (step S108). Specifically, based on the APN notified by the terminal (UE) 10 or the contract APN indicated by the subscriber information management function unit (HSS) 110, the relay node (S-GW) 130 and the gateway (P-GW) 140 are select.

  Next, the mobility management function unit (MME) 120 transmits a bearer setting request to the selected relay node (S-GW) 130 (step S109). The bearer setting request includes the generated IP address and information of the gateway (P-GW) 140 selected in step S108.

  Next, the relay node (S-GW) 130 transmits a path setting request to the gateway (P-GW) 140 selected in step S108 (step S110). The path setting request includes the generated IP address and information of the PDN 200 of the connection destination. The gateway (P-GW) 140 performs PDN connection processing, more specifically, connects the bearer from the relay node (S-GW) 130 to the PDN 200, and sets the generated IP address as an IP address to be delivered ((4) Step S111). Then, the gateway (P-GW) 140 transmits a route setting response to the relay node (S-GW) 130 (step S112). This routing response includes the IP address issued. The relay node (S-GW) 130 performs radio access bearer preparation processing (step S113), and transmits a bearer setting response to the mobility management function unit (MME) 120 (step S114). The bearer setting response includes transfer information for the base station (BTS) 150 (including the IP address paid out, the information paid out by the relay node (S-GW) 130, and the like).

  Next, the mobility management function unit (MME) 120 transmits a context setting request to the base station (BTS) 150 (step S115). The context setting request includes transmission information from the relay node (S-GW) 130 and an attach acceptance signal. The base station (BTS) 150 transmits a radio access bearer setting request and an attach acceptance signal to the terminal (UE) 10 (step S116). Then, upon receiving the radio access bearer setting response from the terminal (UE) 10 (step S117), the base station (BTS) 150 transmits a context setting response to the mobility management function unit (MME) 120 (step S118). On the other hand, the terminal (UE) 10 transmits an attach completion response to the mobility management function unit (MME) 120 (step S119). Through the above processing, connection of uplink user packet data is completed (for terminal (UE) 10 → PDN 200).

  Next, the mobility management function unit (MME) 120 transmits a bearer update request to the relay node (S-GW) 130 (step S120). The relay node (S-GW) 130 updates the radio access bearer in the direction from the relay node (S-GW) 130 to the base station (BTS) 150 (step S121), and transmits a bearer update response to the mobility management function unit (MME) 120. Send to By the above processing, connection of downlink user packet data is completed (PDN 200 → for terminal (UE) 10).

  FIG. 9 is an example in which an address is generated in advance and stored in the subscriber information management function unit (HSS) 110.

  First, the subscriber information management function unit (HSS) 110 or the operator of the operator performs the address generation for all the subscribers by the address generation function unit (ADGen) 170 in advance, and the subscriber information management function unit It stores in (HSS) (step S10).

  The terminal (UE) 10 attaches to the carrier network 100 (step S11). The base station (BTS) 150 notifies the mobility management function unit (MME) 120 of an attach request for the terminal (UE) 10 (step S12). The mobility management function unit (MME) 120 requests the subscriber information management function unit (HSS) 110 for group authentication and location registration (step S13). The subscriber information management function unit (HSS) 110 performs terminal authentication, and the mobility management function unit (MME) 120 as an address for delivering the address generated in advance by the address generation function unit (ADGen) 170 to the terminal (UE) 10. (Step S14). The mobility management function unit (MME) 120 instructs the relay node (S-GW) 130 to connect to the gateway (P-GW) 140 and notifies an address to be paid out (step S15). The relay node (S-GW) 130 requests the gateway (P-GW) 140 for connection and notifies an address to be paid out (step S16). The gateway (P-GW) 140 terminates the communication bearer from the terminal (UE) 10 and connects it to the PDN 200, and assigns the notified address to the terminal (UE) 10 (step S17). The terminal (UE) can communicate with the PDN 200 using the issued address (step S18).

  FIG. 10 is an example in which the mobility management function unit (MME) 120 dynamically generates an address.

  The terminal (UE) 10 attaches to the carrier network 100 (step S21). The base station (BTS) 150 notifies the mobility management function unit (MME) 120 of an attach request for the terminal (UE) 10 (step S22). The mobility management function unit (MME) 120 requests the subscriber information management function unit (HSS) 110 for group authentication and location registration (step S23). The subscriber information management function unit (HSS) 110 performs terminal authentication (step S24). The mobility management function unit (MME) 120 generates an address to be paid out to the terminal (UE) 10 by the address generation function unit (ADGen) 170, and transmits the relay node (S-GW) 130 to the gateway (P-GW) 140. The connection is instructed, and the address to be paid out is notified (step S25). The relay node (S-GW) 130 requests the gateway (P-GW) 140 for connection and notifies an address to be paid out (step S26). The gateway (P-GW) 140 terminates the communication bearer from the terminal (UE) 10 and connects it to the PDN 200, and assigns the notified address to the terminal (UE) 10 (step S27). The terminal (UE) can communicate with the PDN 200 using the issued address (step S28).

  FIG. 11 is an example in which the relay node (S-GW) 140 dynamically generates an address.

  The terminal (UE) 10 attaches to the carrier network 100 (step S31). The base station (BTS) 150 notifies the mobility management function unit (MME) 120 of an attach request for the terminal (UE) 10 (step S32). The mobility management function unit (MME) 120 requests the subscriber information management function unit (HSS) 110 for group authentication and location registration (step S33). The subscriber information management function unit (HSS) 110 performs terminal authentication (step S34). The mobility management function unit (MME) 120 instructs the relay node (S-GW) 130 to connect to the gateway (P-GW) 140 (step S35). The relay node (S-GW) 130 generates an address to be delivered to the terminal (UE) by the address generation function unit (ADGen) 170, requests connection to the gateway (P-GW) 140, and notifies the address to be delivered. (Step S36). The gateway (P-GW) 140 terminates the communication bearer from the terminal (UE) 10 and connects it to the PDN 200, and assigns the notified address to the terminal (UE) 10 (step S37). The terminal (UE) can communicate with the PDN 200 using the issued address (step S38).

  FIG. 12 is an example in which the gateway (P-GW) 140 dynamically generates an address.

  The terminal (UE) 10 attaches to the carrier network 100 (step S41). The base station (BTS) 150 notifies the mobility management function unit (MME) 120 of an attach request for the terminal (UE) 10 (step S42). The mobility management function unit (MME) 120 requests the subscriber information management function unit (HSS) 110 for group authentication and location registration (step S43). The subscriber information management function unit (HSS) 110 performs terminal authentication (step S44). The mobility management function unit (MME) 120 instructs the relay node (S-GW) 130 to connect to the gateway (P-GW) 140 (step S45). The relay node (S-GW) 130 requests the gateway (P-GW) 140 for connection (step S46). The gateway (P-GW) 140 terminates the communication bearer from the terminal (UE) 10, connects to the PDN 200, generates an address by the address generation function unit (ADGen) 170, and gives it to the terminal (UE) 10 (step S47). The terminal (UE) can communicate with the PDN 200 using the issued address (step S48).

  FIG. 13 is an example of dynamically generating an address in the PDN 200 to which a terminal (UE) is connected. In this example, as shown in FIG. 13, the address generation function unit (ADGen) 170 is characterized in that it is disposed in the PDN 200 instead of the carrier network 100.

  The terminal (UE) 10 attaches to the carrier network 100 (step S51). The base station (BTS) 150 notifies the mobility management function unit (MME) 120 of an attach request for the terminal (UE) 10 (step S52). The mobility management function unit (MME) 120 requests the subscriber information management function unit (HSS) 110 for group authentication and location registration (step S53). The subscriber information management function unit (HSS) 110 performs terminal authentication (step S54). The mobility management function unit (MME) 120 instructs the relay node (S-GW) 130 to connect to the gateway (P-GW) 140 (step S55). The relay node (S-GW) 130 requests the gateway (P-GW) 140 for connection (step S56). The gateway (P-GW) 140 terminates the communication bearer from the terminal (UE) 10, connects to the PDN 200, and inquires of the PDN 200 about an address to be delivered to the terminal (UE) 10 (step S57). An address is generated by the address generation function unit (ADGen) 170, and an address to be paid out to the terminal (UE) 10 is paid out to the terminal (UE) 10 via the gateway (P-GW) 140, and the terminal (UE) is paid out address It is possible to communicate with the PDN 200 using (step S58).

  As described above, according to the embodiment of the present invention, by using a terminal identifier and a subscriber identifier that are commonly used among the carrier networks 100 and guaranteed to ensure uniqueness, A permanent and unique IP address that is not affected by the connection destination carrier network 100 can be generated statelessly. Further, in addition to the above, it is possible to generate a subnettable invariable and unique IP address required for CUG, VPN, and routing control. Furthermore, when connecting the terminal 10 to the carrier network 100, in conjunction with terminal authentication or connection processing by the carrier network 100, an address is generated by the address generation method, and an unchanged and unique IP address is paid out even in different carrier networks. be able to.

  As mentioned above, although this invention was explained in full detail about one embodiment, the present invention is not limited to this. For example, in the above embodiment, the carrier network has been exemplified in the LTE architecture. Accordingly, IMSI has been described as a subscriber identifier which is a mandatory input identifier, and IMEI as a terminal identifier. However, the invention can be practiced with carrier networks of other architectures, and other input identifiers can be used. For example, there is a MSISN (Mobile Subscriber ISDN Number). Further, the present invention can be practiced not only in mobile networks but also in fixed networks.

10: Terminal (UE)
100 Carrier network 110 Subscriber information management function unit (HSS)
120: Mobility management function unit (MME)
130: Relay node (S-GW)
140: Gateway (P-GW)
150: Base station (BTS)
160: Integrated gateway (S / P-GW)
170: Address generation function unit 200: PDN

Claims (7)

In a network environment in which a subscriber's terminal is connected to one of a plurality of carrier networks ,
The address generation function unit acquires, from the terminal, a subscriber identifier or terminal identifier commonly used among a plurality of carrier networks, with which even if they are different carriers, uniqueness is secured, from the terminal An address generation method comprising: generating an invariant and unique IP address that can be commonly used by the plurality of carrier networks based on an identifier or a terminal identifier. The address generation function unit generates an invariant and unique IP address from the subscriber identifier or terminal identifier regardless of the carrier network in which it is deployed or the carrier network connected to the external network in which it is deployed. Do
The address generation method according to claim 1, characterized in that: The address generation function unit is an identifier for identifying an arbitrary group and an invariable and unique first address unit commonly usable in the plurality of carrier networks based on a subscriber identifier or a terminal identifier acquired from a terminal. The address generation method according to claim 1 or 2, further comprising: generating an IP address having a second address section based on the address. The address generation function unit is disposed in a carrier network to which a terminal is connected or an external network connected to the carrier network,
The IP address generated by the address generation function unit is paid out to the terminal connected to the carrier network.
The address generation method according to any one of claims 1 to 3, characterized in that: In a network environment in which a subscriber's terminal is connected to one of a plurality of carrier networks ,
A subscriber identifier or terminal identifier commonly used among a plurality of carrier networks, which are different carriers but whose uniqueness is secured, is acquired from the terminal, and based on the acquired subscriber identifier or terminal identifier An address generation apparatus comprising an address generation function unit for generating an invariable and unique IP address that can be commonly used by the plurality of carrier networks. An address generation program characterized by causing a computer to function as the address generation device according to claim 5 . In a network environment in which a subscriber's terminal is connected to one of a plurality of carrier networks ,
The address generation function unit acquires, from the terminal, a subscriber identifier or terminal identifier commonly used among a plurality of carrier networks, with which even if they are different carriers, uniqueness is secured, from the terminal Generating an invariant and unique IP address that can be commonly used by the plurality of carrier networks based on an identifier or a terminal identifier,
An address delivery method characterized in that the terminal authentication means or connection processing means pays out the generated IP address to the terminal at the time of terminal authentication or connection processing by the carrier network.

Images