JP4689703B2 - Address management device and location management device - Google Patents

Description

  The present invention relates to an address management device and a location management device used when dynamically assigning an IP (Internet Protocol) host address to a mobile communication terminal.

Generally, in a mobile communication system, an identifier that can be confirmed by a user such as a telephone number is assigned to a mobile communication terminal, and the mobile communication terminals establish communication using the identifier. Yes. Further, the server that manages the user profile manages where the mobile communication terminal is currently located by using the telephone number as an identifier.
In recent years, in IP ² (IP based IMT Network Platform), a technology has been proposed in which an IP host address (hereinafter referred to as “IPha”) is used to serve as information for identifying a mobile communication terminal, which has been conventionally performed using a telephone number. ing. This technical content is described in the specifications of Japanese Patent Application Nos. 2002-276196, 2002-323129, 2003-206339, and the like.

According to the contents described in these specifications, a location management device (Location Manager; hereinafter referred to as “LM”) that manages location information of a mobile communication terminal (Mobile Node; hereinafter referred to as “MN”) It holds the relationship between the assigned IPha and an access router (Access Router; hereinafter referred to as “AR”) that has established a link with the MN. In these documents, only fixed payout is considered, such as IPha set in the MN is set in a service order (SO) by a business operator or the like.
In order to dynamically assign IPha to MN, DHCPv6 server described in “RFC3315 Dynamic Host Configuration Protocol for IPv6 (DHCPv6)” and Dynamic described in “RFC2136 Dynamic Updates in the Domain Name System (DNS UPDATE)” are existing technologies. This can be realized by using DNS or the like.

The problems of the conventional IPha allocation method will be described with reference to FIGS. 15 and 16.
FIG. 15 shows a method for allocating IPha # 1 to MN1 in a fixed manner. As shown in the figure, first, IPha # 1 is paid out in accordance with an instruction from the service order management server (S1001). MN1 obtains IPha # 1 by connecting to the service order management server. IPha # 1 is fixedly set in MN1.
Alternatively, MN1 obtains IPha # 1 by some notification from the service order management server, and IPha # 1 is fixedly set in MN1 by the user (S1002).

In response to the notification from the service order management server, the LM permanently registers (sets) IPha # 1 issued to MN1 in the location management table (S1003).
After IPha # 1 is registered in the MN1 and the LM, a location registration procedure described below in the IP ² is performed.
First, when the power of MN1 is turned on (S1004), an L2 link is set between AR1 and MN1. The MN 1 transmits a location registration message (LR: Location Regstration) including the IPha # 1 set in the MN 1 to the AR 1 (S1005).

The AR1 transmits a location update message (LU: Location Update) including IPha # 1 included in the LR received from the MN1 to the LM (S1006).
When the LM receives the LU from the AR1, the LM registers the identifier of the AR1 that is the LU transmission source in association with the IPha # 1 already registered in the location management table. Then, the LM transmits a location update response message (LUAck: Location Update Acknowledgment) to the AR 1 (S1007).

AR1 transmits a location registration response message (LRAck: Location Registration Acknowledgement) to MN1 (S1008).
At this time, when changing the IPha notified from the service order management server to the MN1, access to the service order management server is required. In order to change the IPha set in the MN1, the user goes to the window of the company that manages the service order management server, calls the NW (network) provider, and requests to change the IPha. , Forced to work. In this method, the IPha assignment procedure and the location registration procedure are performed by independent procedures.

Next, a dynamic IPha allocation method based on application of existing technology will be described with reference to FIG. Here, a DHCPv6 server is used as an example of the IP address management device. The terminal identifier of MN1 in DHCP is DUID (A DHCP Unique Identifier for a DHCP).
First, when MN1 is powered on, an L2 link is set up between AR1 and MN1 (S1011). Since IPha is not set in its own device, MN1 transmits DHCP SOLICIT to the DHCP server in order to acquire IPha (S1012).
AR1 transfers the DHCP SOLICIT received from MN1 to the DHCPv6 server (S1013), and then receives DHCP ADVERTISE from the DHCPv6 server (S1014) and transfers it to MN1 (S1015).

  MN1 receives DHCP ADVERTISE from AR1 and transmits DHCP REQUEST to AR1 (S1016). AR1 transfers the DHCP REQUEST from MN1 to the DHCPv6 server (S1017). The DHCPv6 server registers the DUID that is the terminal identifier of MN1 and the IPha # 1 that has been paid out in the IP address management table (S1018). The DHCPv6 server transmits DHCP REPLY including IPha # 1 (S1019). When AR1 receives the DHCP REPLY from the DHCPv6 server, AR1 transfers it to MN1 (S1020). MN1 receives DHCP REPLY from AR1 and acquires IPha # 1 (S1021).

  After MN1 sets IPha # 1 to MN1, MN1 transmits LR including the paid-out IPha # 1 to AR1 (S1022). When AR1 receives LR from MN1, it sends LU to LM (S1023). After completing the location registration (S1024), the LM transmits LUAck to AR1 (S1025). When AR1 receives LUAck, AR1 transmits LRAck to MN1 (S1026). MN1 receives LRAck from AR1, and the location registration is completed.

In this method, since AR1 only relays between MN1 and the DHCPv6 server, IPha acquisition is performed between MN1 and the DHCPv6 server. In this method, the IPha payout procedure and the location registration procedure are performed independently of each other. For this reason, many messages are exchanged between MN1 and AR1, and as a result, the wireless section is compressed.
As described above, the dynamic IPha allocation by application of the existing technology has a redundant message amount. In addition, in the fixed IPha allocation, in order to avoid a malicious attack to the MN that may occur because the IPha is fixed, the change of the IPha is assumed to be a change in the SO, which places a heavy burden on the user .

Patent Document 1 discloses another method for dynamically assigning an IP address. In Patent Document 1, a wireless base station holds in advance an IP address to be assigned to a mobile communication terminal from a DHCP server. When the mobile communication terminal transmits an IP address assignment request, the radio base station assigns one of the IP addresses held to the mobile communication terminal and transmits it to the mobile communication terminal. .
JP 2001-186573 A (summary)

In the method disclosed in Patent Document 1, the time until a mobile communication terminal requests an IP address assignment and acquires it is reduced by pre-holding an IP address that the radio base station should assign to the mobile communication terminal. The purpose is to do. For this reason, the location registration procedure of the mobile communication terminal is not taken into consideration, and the IP address assignment procedure and the location registration procedure are performed by a procedure independent of each other. Therefore, when considering the total message amount of IP address assignment and location registration, the technique of Patent Document 1 cannot be said to be a technique that can reliably reduce the message amount in the wireless section.
The present invention has been made paying attention to the above problem, and dynamically reduces terminal identification address information for identifying a mobile communication terminal without reducing the wireless section by reducing the amount of messages in the wireless section. An object of the present invention is to provide an address management device and a location management device that are used when assigning and prevent duplicate management of terminal identification address information.

In order to solve the above-mentioned problem, an invention according to claim 1 is directed to an address management apparatus that assigns terminal identification address information for uniquely identifying a mobile communication terminal in a mobile communication network to a mobile communication terminal. Address management means for managing terminal identification address information assigned to the mobile communication terminal, and processing for assigning terminal identification address information different from the terminal identification address information managed by the address management means to the mobile communication terminal Terminal identification address information managed by the address management means in at least one of a case where the validity period associated with the terminal identification address information managed by the address management means has elapsed remove and address deleting means, to the mobile communication terminal, the address pipe Deletion of location information including terminal identification address information that matches the terminal identification address information managed by the address management means when performing processing for assigning terminal identification address information different from the terminal identification address information managed by the means An address management device is provided , comprising: an old address deletion requesting unit that transmits a message requesting a request to a location management device that manages location information of the mobile communication terminal .

According to the first aspect of the present invention, since the address management device includes the address deletion unit that deletes the terminal identification address information managed by the address management unit when a specific event occurs, the terminal identification Duplicate management of address information can be prevented .

Further , when performing processing for assigning terminal identification address information to a mobile communication terminal, the address management device requests deletion of position information including old terminal identification address information that has been assigned to the mobile communication terminal. The location management device can reliably delete the location information including the old terminal identification address information, and the address management device and the location management device can manage the terminal identification address information. Consistency can be maintained.

According to a second aspect of the invention, in the address management apparatus according to claim 1, when a validity period associated with the said terminal identification address information has elapsed, associated with the information representing the valid period It further comprises address reassignment request means for transmitting address reassignment request instruction data for instructing reacquisition of different terminal identification address information to a mobile communication terminal to which terminal identification address information is assigned. To do.
According to the second aspect of the present invention, the address management device detects that the valid period associated with the terminal identification address information has passed, and re-sends different terminal identification address information to the mobile communication terminal. Since the address reassignment request instruction for requesting acquisition is transmitted, the terminal identification address information can be reliably reassigned to the mobile communication terminal.

According to a third aspect of the present invention, in the address management device according to the first or second aspect , a validity check for confirming whether or not the terminal identification address information assigned to the mobile communication terminal is valid Based on the information managed by the address management means, whether the terminal identification address information assigned to the mobile communication terminal is assigned to another mobile communication terminal when the request message is received An address validity evaluation means for determining is further provided.

According to the invention described in claim 3 , the address management device manages whether or not the terminal identification address information assigned to the mobile communication terminal is assigned to another mobile communication terminal by the address management means. Terminal identification address information used by the mobile communication terminal is not properly assigned, or assigned to another mobile communication terminal due to expiration of the validity period, etc. If it is, it can be evaluated that the terminal identification address information used by the mobile communication terminal is not valid.

According to a fourth aspect of the present invention, there is provided a location management device for managing location information of a mobile communication terminal for requesting registration of location information of the mobile communication terminal from a relay device that relays communication of the mobile communication terminal. When a message is received, terminal identification address information for uniquely identifying the mobile communication terminal in the mobile communication network included in the message and the identification information of the relay device are associated with each other and managed as position information Location information management means and an address management device that manages the terminal identification address information assign terminal identification address information different from the terminal identification address information managed by the address management device to the mobile communication terminal. when performing the process, and the terminal identification address information from said address management device are managed by the address management device And when receiving the deletion request matches the terminal identification address information, and if via the relay device from the mobile communication terminal receives a request for deletion of the terminal identification address information, is managed by the position information management means if at least one of a case where the validity period associated with the terminal identification address information have has elapsed, deleting the position information for deleting the location information including the end-terminal identification address information that is managed by the position information management means And a position management device.

According to the invention described in claim 4 , the location management device manages the location information of the mobile communication terminal by the location information management means, and the location information managed by the location information management means in response to various events. Since the address deleting means for deleting is provided, it is possible to avoid duplication of terminal identification address information managed by the position information managing means and manage correct position information with consistency.

  According to the present invention, the address management device and the location management device increase the message amount in the radio section so that the terminal identification address information managed by the own device does not overlap with the dynamic allocation of the terminal identification address information. The terminal identification address information can be deleted and the validity evaluation process can be performed.

Next, the best mode for carrying out the present invention will be described with reference to the drawings. In each drawing referred to in the following description, the same reference numerals are given to the same parts as in the other drawings.
[1. Constitution]
[1.1. overall structure]
FIG. 1 is a block diagram showing a configuration of an entire address dynamic allocation system according to an embodiment of the present invention. This dynamic address allocation system includes a mobile communication terminal (hereinafter referred to as “MN”) 1, an access router (hereinafter referred to as “AR”) 2 connected to MN 1 and relaying message transmission / reception of MN 1, and MN 1 in a mobile communication network. An IP address management device 3 that manages IPha, which is terminal identification address information assigned for uniquely identifying, and a location management device (hereinafter referred to as “LM”) 4 that manages location information of MN1 are configured. . The address management device 3 and the LM 4 constitute an NCPF (Network Control Platform) that manages network control in IP ² . In the figure, only one MN1 and AR2 are shown, but there are actually a plurality of them.
The MN1, AR2, the IP address management device 3 and the LM4 have a hardware configuration of a general computer device, and include a CPU (Central Processing Unit), a memory, and a communication interface. Programs for realizing functions characteristic of the present invention are stored in the memories of these devices.

[1.2. AR]
Next, AR2 will be described. AR2 is a device that performs acquisition of IPha to be assigned to MN1 and location registration of MN1 as a series of processes. The AR2 functions as a proxy server for acquiring the IPha when performing the process of acquiring the IPha of the MN1. The functional configuration of AR2 will be described. The AR2 CPU executes the program stored in the AR2 memory, whereby the functions shown in FIG.
When the address acquisition necessity determination unit 21 receives a location registration message (LR) for requesting registration of location information from MN1, it should be assigned to MN1 based on the IPha information included in the location registration message. It is determined whether it is necessary to acquire IPha.

  Here, “IPha information” included in the LR is information set in a specific area in the location registration message. The “IPha information” is address acquisition necessity information indicating whether or not the IPha to be assigned to the MN 1 needs to be acquired. The address acquisition necessity determination unit 21 determines that it is not necessary to acquire the IPha when a value is set in the IPha information included in the location registration message. On the other hand, when a value is not set in the IPha It is determined that IPha needs to be acquired.

  When the MN 1 reacquires IPha, an area for setting “old IPha information” and “new IPha information” may be provided in the location registration message. In this case, “new IPha information” serves as address acquisition necessity information. The “old IPha information” represents a request to delete the IPha currently assigned to MN1. When MN1 sets the IPha information currently assigned to MN1 in "Old IPha information" and sends a location registration message with "New IPha information" not set, MN1 obtains the new IPha information In addition, the old IPha information managed by the LM4 can be deleted.

The method of expressing the address acquisition necessity information by “IPha information” or “new IPha information” is an example. For example, the MN 1 directly sets information indicating “acquisition required” and “acquisition not required” in the location registration message, and the address acquisition necessity determination unit 21 interprets this information, thereby determining whether the IPha needs to be acquired. You may make it determine.
If the address acquisition necessity determining unit 21 determines that the IPha needs to be acquired, the address acquisition proxy unit 22 acquires the IPha to be assigned to the MN1 from the IP address management device 3 instead of the MN1.

The post-address acquisition location registration unit 23 generates a location update message (LU) including the IPha information acquired by the address acquisition proxy unit 22 and transfers the generated location update message to the LM 4. Thereby, the LM 4 can manage the IPha information of MN1 and the identifier of AR2 in association with each other as location information of MN1.
The allocation address notification unit 24 generates a location registration response message (LRAck) including the IPha acquired by the address acquisition proxy unit 22 and sends it back to the MN1.
The address validity confirmation unit 25 transmits a message for confirming the validity of the IPha assigned to the MN 1 to the IP address management device 3.

[1.3. IP address management device]
Next, the configuration of the IP address management device 3 will be described. The IP address management device 3 is a device that manages the IPha issued to the MN 1 and can use, for example, a DHCPv6 server.
FIG. 3 shows functions characteristic of the present invention that the IP address management device 3 has. The IP address management table 31 shown in the figure is provided in the memory of the IP address management device 3. In the IP address management table 31, information representing the DUID that is the terminal identifier of MN1 and the IPha assigned to MN1 is stored in association with each other. The memory stores information representing the lease period of each IPha information. Here, the lease period represents a valid period during which use is permitted after IPha is assigned to MN1. The IP address management device 3 includes a timer for measuring the lease period.

Further, the following functions shown in FIG. 3 are realized in the IP address management device 3 by the CPU of the IP address management device 3 executing the program stored in the memory. When the address deletion unit 32 detects from the notification from the timer that the lease period stored in the IP address management table 31 has elapsed, the address deletion unit 32 deletes the IPha associated with the information representing the valid period.
The old address deletion request unit 33 transmits a request to the LM 4 to delete the old IPha that has been assigned to the MN 1 until the new IPha is assigned to the MN 1.

The address reassignment request unit 34 re-acquires a different IPha from the MN 1 to which the IPha is assigned when it detects that the lease period of a certain IPha has expired (elapsed) by notification from the timer. Address reassignment request instruction data for requesting is transmitted.
The address validity evaluation unit 35 evaluates the validity of the IPha assigned to the MN1 when receiving a message for confirming whether the IPha assigned to the MN1 is valid from the AR2. . Specifically, the address validity evaluation unit 35 refers to the IP address management table 31 and determines whether the IPha assigned to MN1 is assigned to another MN.

[1.4. LM]
Next, the configuration of the LM4 will be described. FIG. 4 shows functions characteristic of the present invention provided in the LM 4. A location management table 41 is provided in the memory of the LM 4. The location management table 41 includes information for identifying the IPha information assigned to the MN 1 and the AR 2 that has transmitted the location update message (LU). Is stored. The memory stores information indicating the validity period of each piece of position information. The LM 4 includes a timer for measuring each valid period.
Further, when the CPU of the LM 4 executes a program stored in the memory, the position information deletion unit 42 illustrated in FIG. 4 is realized in the LM 4.

  The location information deletion unit 42 deletes location information including the IPha information from the location management table 41 when detecting a request to delete the IPha information assigned to the MN 1. The location information deletion unit 42 deletes location information from the location management table 41 when receiving a deletion request from the IP address management device 3 and receiving the old IPha information assigned to MN1 from MN1 via AR2. There is at least one case in which the valid period measured by the timer included in the LM4 has expired.

[2. Operation]
Next, the operation in the above configuration will be described.
Here, it is assumed that MN1 is connected under AR2. In addition, a DHCPv6 server is used as the IP address management device 3. Hereinafter, the IP address management device 3 will be described as “DHCPv6 server 3”.
[2.1. IPha acquisition procedure when IPha is not set]
First, the IPha acquisition procedure will be described with reference to FIG. In FIG. 5, it is assumed that MN1 starts communication under AR2. At this time, it is assumed that IPha is not set in MN1, and IPha is not yet registered in LM.
When the power of MN1 is turned on (S10), an L2 link is set between AR2 and MN1 (S11). Since MN1 has not been set for IPha, it transmits a location registration message (LR) including information that IPha information is not set to AR2 (S12).

  The AR2 address acquisition necessity determination unit 21 determines whether or not it is necessary to acquire an IPha to be allocated to the MN 1 based on the IPha information included in the LR. If it is confirmed that the IPha information included in the LR received from MN1 is not set, the address acquisition proxy unit 22 performs an IPha acquisition process for MN1 (S13). Specifically, the address acquisition proxy unit 22 transmits DHCP SOLICIT to the DHCPv6 server 3 (S14), and receives DHCP ADVERTISE as a response (S15). Next, the address acquisition proxy unit 22 transmits DHCP REQUEST to the DHCPv6 server 3 (S16).

The DHCPv6 server 3 issues IPha # 1 as the IPha for MN1, and registers the terminal identifier DUID of MN1 and the issued IPha # 1 in association with each other in the IP address management table 31 (S17).
The address acquisition proxy unit 22 of AR2 receives the DHCP REPLY including IPha # 1 (S18). As a result, IPha # 1 paid out for MN1 is notified to AR2. After acquiring the address of AR2, the location registration unit 23 transmits a location update message (LU) including IPha # 1 to the LM4 (S19).

When the LM 4 receives the LU from the AR 2, the LM 4 associates and registers the IPha # 1 and AR2 in the location management table (S20). The LM 4 transmits a location update response message (LUAck) to the AR 2 (S21).
The allocated address notification unit 24 of AR2 transmits a location registration response message (LRAck) including IPha # 1 to MN1 (S22).
MN1 receives LRAck from AR2, and acquisition of IPha # 1 is completed simultaneously with the completion of location registration (S23).

  Here, when MN1 makes an address acquisition request to the DHCPv6 server 3 as shown in FIG. 16, many messages are required between MN1 and AR2. However, in the present invention, the address acquisition proxy unit 22 in AR2 makes an address acquisition request on behalf of MN1, whereby IPha acquisition on the NW side (between AR2 and DHCPv6 server 3) is possible, and MN1 and AR2 Messages other than those required for location registration are unnecessary.

[2.2. Location registration procedure after completion of IPha acquisition]
Next, referring to FIG. 6, the location registration procedure after the completion of IPha acquisition will be described. Hereinafter, only a procedure different from that in FIG. 5 will be described.
Here, it is assumed that MN1 has already acquired IPha # 1, and IPha # 1 is set in MN1. For this reason, MN1 transmits LR including IPha # 1 to AR2 (S32). The address acquisition necessity determination unit 21 of AR2 determines that it is not necessary to acquire IPha because IPha # 1 is set in the LR (S33). For this reason, AR2 transmits the LU including the already issued IPha # 1 to LM4 (S34). When the LM 4 receives the LU from the AR2, the LM 4 associates the IPha # 1 and the identifier of the AR2 with the location management table 41 and registers them as location information (S35), and transmits the LU Ack to the AR2 (S36).

AR2 transmits LRAck including IPha # 1 to MN1 (S37). MN1 receives LRAck from AR2, and completes location registration (S38).
Here, when MN1 takes the initiative in requesting address acquisition as shown in FIG. 16, address acquisition cannot be managed on the NW side, and all address acquisition requests from MN1 are allowed. However, in the procedure illustrated in FIG. 6, the address acquisition necessity determination unit 21 of the AR 2 receives the LR from the MN 1, and determines whether IPha has been paid out to the MN 1, thereby causing unnecessary address acquisition. Absent.

  Furthermore, the present invention is effective for MN1 to acquire IPha again even when MN1 acquires IPha and IPha information is already set in MN1, using FIGS. explain. 7 to 9 are explanatory diagrams of IPha reacquisition led by NW such as DHCPv6 server 3 and LM4, and FIGS. 10 to 12 are explanatory diagrams of IPha reacquisition led by MN1.

[2.3. Nha-led IPha reacquisition procedure (request to delete old IPha from DHCPv6 server)]
With reference to FIG. 7, the IPha reacquisition procedure led by NW in the case of resetting (changing) the IPha of MN1 after IPha acquisition will be described. Here, it is assumed that the LM 4 avoids redundant management of the IPha information of the MN 1 in the location management table 41 based on the old IPha deletion request message from the DHCPv6 server 3. Also, the old IPha information held by MN1 is assumed to be IPha # 1.

  First, when the DHCPv6 server 3 detects that the lease period of IPha # 1 issued to MN1 has expired, the address deletion unit 32 deletes IPha # 1 stored in the IP address management table 31 ( S41). At the same time, the address reassignment request unit 34 activates a program for executing re-payout processing, and transmits DHCP RECONFIGURE for requesting reacquisition of a new IPha to the MN 1 (S42).

When AR2 receives DHCP RECONFIGURE from the DHCPv6 server, AR2 transmits an address reassignment request instruction to MN1 (S43).
When MN1 receives an address reassignment request instruction from AR2, MN1 executes an IPha acquisition procedure similar to the procedure in FIG. 5 (S44 to S57), and acquires IPha # 2.
Here, the difference from the procedure in FIG. 5 is that when the DHCPv6 server 3 receives a DHCP REQUEST from the AR2 (S47), the old address deletion request unit 33 of the DHCPv6 server 3 includes the old IPha deletion request message including IPha # 1. Is transmitted to LM4 (S48).

When the LM 4 receives the old IPha deletion request message, the position information deleting unit 42 of the LM 4 deletes the position information including IPha # 1 stored in the position management table 41 (S49). Thereafter, the LM 4 transmits a delete request response message to the DHCPv6 server 3 (S50).
Further, the DHCPv6 server 3 that has received the DHCP REQUEST (S47) pays out IPha # 2 (S51). The DHCPv6 server 3 registers the paid-out IPha # 2 in the IP address management table 31 in association with the terminal identifier DUID of the MN 1 (S52).
In S50, when the DHCPv6 server 3 receives the deletion request response message from the LM 4, it sends a DHCP REPLY including IPha # 2 to the AR 2 (S53).

  Here, when the address is acquired as shown in FIG. 16, the wireless section is compressed every time the address is acquired. In addition, there is no means for deleting IPha # 1 stored in the location management table 41 in LM4. However, in the procedure shown in FIG. 7, the location information deletion unit 42 of the LM 4 receives the old IPha information (IPha #) stored in the location management table 41 in response to a deletion request from the old address deletion request unit 33 of the DHCPv6 server 3. 1) can be deleted. Since the LM 4 registers the new IPha information (IPha # 2) newly issued in the location management table 41, the location management table 41 can be prevented from managing the IPha information of the MN 1 redundantly. it can.

  According to this method, when the IPha lease period expires, the MN1 can receive an address reassignment request. Therefore, the regular IPha can be used regardless of the IPha lease period used by the MN1. It becomes. Also, AR2 can request reacquisition of IPha without managing the association between MN1 and IPha. Furthermore, since the LM 4 receives the old IPha deletion request message from the DHCPv6 server 3, it is possible to uniquely manage the IPha information in the location management table 41.

[2.4. IPha reacquisition procedure led by NW (Old IPha deletion request from MN)]
In the procedure shown in FIG. 7, the old IPha deletion request message from the old address deletion request unit 33 of the DHCPv6 server 3 is used as an opportunity to avoid duplication in the location management table 41 in the LM4. However, in the procedure shown in FIG. A case where IPha duplication management in the location management table 41 of the LM4 is avoided based on the old IPha information from the MN1 will be described. The old IPha information held by MN1 is assumed to be IPha # 1.

When the DHCPv6 server 3 detects that the lease period of IPha # 1 issued to MN1 has expired, the address deletion unit 32 deletes IPha # 1 stored in the IP address management table 31 (S60). At the same time, the DHCPv6 server 3 starts a program for executing re-payout processing, and transmits DHCP RECONFIGURE to the AR 2 (S61).
When AR2 receives DHCP RECONFIGURE from DHCPv6 server 3, AR2 transmits an address reassignment request instruction from AR2 to MN1 (S62).

When the MN1 receives the address reassignment request instruction from the AR2, the MN1 transmits an LR including the old IPha information (IPha # 1) and the new IPha information (unregistered) to the AR2 (S63).
When the AR 2 receives the LR from the MN 1, the address acquisition necessity determination unit 21 determines whether it is necessary to acquire the IPha to be allocated to the MN 1. Here, since the new IPha information included in the LR is unregistered, the address acquisition proxy unit 22 executes the same IPha acquisition procedure as in FIG. 7 (S64 to S69), and acquires IPha # 2.

Next, the post-acquisition location registration unit 23 of the AR2 transmits the LU including the old IPha information (IPha # 1) and the new IPha information (IPha # 2) to the LM4 (S70).
LM4 receives the LU from AR2. The position information deletion unit 42 of the LM 4 deletes position information including IPha # 1 stored in the position management table 41 based on the old IPha information included in the LU. At the same time, the LM 4 registers IPha # 2 based on the new IPha information included in the LU (S71). Thereafter, the LM 4 transmits LUAck to the AR 2 (S72).

AR2 receives LUAck from LM4. The assigned address notification unit 24 of AR2 transmits LRAck including IPha # 2 as IPha information to MN1 (S73).
When MN1 receives LRAck from AR2, MN1 acquires newly assigned Ipha # 2 included in LRAck and sets it to MN1 (S74).
Here, similar to the effect in the procedure of FIG. 7, the location information deletion unit 42 of the LM 4 receives the old IPha information (IPha # 1) assigned to the MN 1 via the AR 2 from the MN 1 to thereby obtain the location management table. The old IPha information stored in 41 can be deleted. Then, the LM 4 can avoid duplication management of IPha information by registering the new IPha information (IPha # 2) newly assigned to MN1 in the location management table 41.

  According to this procedure, when the IPha lease period expires, MN1 can receive an address reassignment request. Therefore, regardless of the IPha lease period used by MN1, MN1 uses a regular IPha. Is possible. Further, AR2 can request reacquisition of an address without managing the association between MN1 and IPha. Further, based on the old IPha information from MN1, AR2 relays the old IPha information, and LM4 receives the old IPha information and performs a deletion process, whereby unique management of IPha information in the location information management table 41 is possible. It is. In addition, since MN1 notifies AR2 of the old IPha information, AR2 does not need to manage the IPha assigned to MN1.

[2.5. IPha re-acquisition procedure led by NW (timer expiration at LM)]
FIG. 9 shows a procedure when the LM 4 avoids duplication management of the IPha information in the location management table 41 by using a timer associated with the IPha information stored in the location management table 41 of the LM 4. The old IPha information held by MN1 is assumed to be IPha # 1. Here, the lease period of IPha # 1 stored in the IP address management table 31 of the DHCPv6 server 3 and the timer associated with IPha # 1 stored in the location management table 41 of the LM4 expire. It is assumed that the timing to be set is the same.

First, when the LM 4 detects that the valid period counted by the timer associated with IPha # 1 has expired, the position information deletion unit 42 stores the position information including IPha # 1 stored in the position management table 41. Delete (S80).
At the same time, the DHCPv6 server 3 detects that the lease period of IPha # 1 issued to MN1 has expired. Thereby, the address deleting unit 32 of the DHCPv6 server 3 deletes IPha # 1 stored in the IP address management table 31 (S81). At the same time, the address reassignment request unit 34 of the DHCPv6 server 3 transmits to the AR 2 DHCP RECONFIGURE for requesting acquisition of a new IPha to the MN 1 to which the IPha # 1 is assigned (S82).

  When AR2 receives DHCP RECONFIGURE from DHCPv6 server 3, AR2 transmits an address reassignment request instruction to MN1 (S83). When MN1 receives the address reassignment request instruction from AR2, MN1 transmits LR including IPha information (unregistered) to AR2 (S84). When the AR 2 receives the LR from the MN 1, the address acquisition necessity determination unit 21 determines that the acquisition of the IPha is necessary because the IPha information included in the LR is not registered. Thereafter, the address acquisition proxy unit 22 executes the same IPha acquisition procedure as in FIG. 7 (S85 to S90), and acquires IPha # 2.

The post-address acquisition location registration unit 23 of the AR2 transmits the LU including the acquired IPha information (IPha # 2) to the LM4 (S91).
When the LM 4 receives the LU from the AR 2, the LM 4 registers the IPha information (IPha # 2) and the identification information of the AR 2 as position information in the position management table 41 based on the IPha information included in the LU (S92). The LM 4 transmits LUAck to the AR 2 (S93). When AR2 receives LUAck, the allocation address notification unit 24 transmits LRAck including IPha # 2 as IPha information to MN1 (S94).
When MN1 receives LRAck from AR2, MN1 acquires Ipha # 2 included in LRAck and sets it in MN1 (S95).

  As described above, the position information deletion unit 42 deletes the position information including IPha # 1 when a predetermined time elapsed by the timer associated with IPha # 1 stored in the position management table 41 of the LM 4 has elapsed. Thus, duplication with the newly assigned IPha # 2 can be avoided. By matching the timing of deleting the IPha information with the timer of the LM 4 and the timer that manages the lease period in the DHCPv6 server 3, it is possible to avoid the state mismatch as in FIGS.

  According to this method, when the IPha lease period expires, the MN1 can receive an address reassignment request. Therefore, regardless of the IPha lease period used by the MN1, the MN1 uses the regular IPha. Is possible. Further, AR2 can request reacquisition of an address without managing the association between MN1 and IPha. Furthermore, since the old IPha information stored in the location management table 41 managed by the LM4 is deleted by the IPha management timer of the LM4, the IPha information in the location management table 41 can be uniquely managed.

[2.6. IPha reacquisition procedure led by MN (request to delete old IPha of DHCPv6 server)]
Next, an IPha reacquisition procedure led by MN1 when MN1 reconfigures (changes) IPha of MN1 after IPha acquisition will be described with reference to FIG. Here, it is assumed that the LM 4 avoids redundant management of the IPha in the location management table 41 based on the old IPha deletion request message from the DHCPv6 server 3. Also, the old IPha information held by MN1 is assumed to be IPha # 1.

  First, when receiving a trigger for IPha reconfiguration (S101), MN1 transmits an LR for which the IPha information setting value is not set to AR2 (S102). Since the setting value of the IPha information included in the LR received from the MN 1 is not set, the address acquisition necessity determination unit 21 of the AR 2 determines that IPha acquisition is necessary. The address acquisition proxy unit 22 executes an address acquisition procedure for the DHCPv6 server 3 (S103 to S111).

  Specifically, when the DHCPv6 server 3 receives an address acquisition request (S105), it newly pays out IPha # 2 (S106). Then, the address deletion unit 32 of the DHCPv6 server 3 deletes the old IPha information (IPha # 1) in the IP address management table 31. The DHCPv6 server 3 registers the terminal identifier DUID of MN1 and IPha # 2 in association with each other in the IP address management table 31 (S107). At the same time, the old address deletion request unit 33 of the DHCPv6 server 3 transmits an old IPha deletion request message to the LM 4 (S108).

The location information deletion unit 42 of the LM 4 deletes location information including IPha # 1 by the received old IPha deletion request message (S109). The LM 4 transmits an old IPha deletion request response message to the DHCPv6 server 3 (S110). The DHCPv6 server 3 transmits a DHCP REPLY including the newly issued IPha # 2 (S111).
The address acquisition proxy unit 22 of the AR 2 receives the DHCP REPLY from the DHCPv6 server 3. The post-address acquisition location registration unit 23 of the AR 2 generates an LU including the IPha # 2 included in the DHCP REPLY, and transmits the LU to the LM 4 (S112). The LM 4 associates IPha # 2 included in the LU with the identifier of AR2 and registers them in the location management table 41 as location information (S113). The subsequent procedure is the same as the procedure in FIG.

  Here, the address re-acquisition led by MN1 as described above is possible without squeezing the wireless section and without changing the conventional location registration procedure. Further, the location information deletion unit 42 of the LM 4 deletes the location information including the old IPha information (IPha # 1) of the location management table 41 in response to the deletion request from the old address deletion request unit 33 of the DHCPv6 server 3, Since the LM 4 registers the location information including the new IPha information (IPha # 2) by the LU from the AR 2, it is possible to avoid the redundant management of the IPha information of the MN 1 in the location management table 41.

[2.7. MN-led IPha reacquisition procedure (request for deleting old IPha from MN)]
In FIG. 11, the IPha reacquisition procedure led by MN1 when the IPha of MN1 is reset (changed) after IPha acquisition will be described. Here, it is assumed that the LM 4 avoids redundant management of the IPha information of the MN1 in the location management table 41 based on the transmission of the old IPha information from the MN1. Also, the old IPha information held by MN1 is assumed to be IPha # 1.
First, when receiving a trigger for IPha reconfiguration (S120), MN1 transmits to the AR2 an LR in which the set value of the new IPha information is not set and the old IPha information is IPha # 1 (S121).

  Since the new IPha setting value in the LR received from MN1 is not set and the old IPha information is IPha # 1, the address acquisition necessity determination unit 21 of AR2 acquires IPha to be assigned to MN1. Is determined to be necessary. The address acquisition proxy unit 22 executes an address acquisition procedure to the DHCPv6 server 3 (S122 to S127). Specifically, when the DHCPv6 server 3 receives an address acquisition request in S124, it newly pays out IPha # 2 (S125). Then, the address deletion unit 32 of the DHCPv6 server 3 deletes the old IPha information (IPha # 1) in the IP address management table 31. At the same time, the DHCPv6 server 3 associates the terminal identifier DUID of MN1 with IPha # 2 and registers them in the IP address management table 31 (S126). The DHCPv6 server 3 transmits a DHCP REPLY including IPha # 2 to the AR2 (S127).

The address acquisition proxy unit 22 of the AR 2 receives the DHCP REPLY from the DHCPv6 server 3. The post-address acquisition location registration unit 23 of the AR2 generates an LR including the new IPha information (IPha # 2) and the old IPha information (IPha # 1), and transmits the LR to the LM4 (S128).
The location information deletion unit 42 of the LM 4 deletes location information including IPha # 1 from the location management table 41 based on the old IPha information included in the received LU.
Also, the LM 4 associates IPha # 2 with the identifier of AR2 based on the new IPha information included in the LU, and registers it in the location management table 41 as location information (S129). Since the subsequent procedure is the same as that in FIG.

  Here, as in FIG. 10, address re-acquisition led by MN 1 is possible without squeezing the wireless section and without changing the conventional location registration procedure. Further, the AR2 includes the new IPha information and the old IPha information in the LU and transmits to the LM4, whereby the old IPha information (IPha # 1) stored in the location management table 41 in the LM4 is deleted, and New IPha information (IPha # 2) is registered. For this reason, duplication management of the IPha information of MN1 in the location management table 41 can be avoided.

[2.8. IPha re-acquisition procedure led by MN (LM timer expired)]
In FIG. 12, it is assumed that duplication management of the IPha information of MN1 in the location management table 41 is avoided by a timer associated with the location information stored in the location management table 41 of LM4. The old IPha information held by MN1 is assumed to be IPha # 1. Here, it is assumed that the timing at which the LM4 timer expires coincides with the timing at which MN1 receives an IPha change instruction.

  The LM 4 detects that the period timed by the timer associated with IPha # 1 stored in the location management table 41 has expired. Thereby, the position information deletion unit 42 deletes the position information including IPha # 1 stored in the position management table 41 (S140). At the same timing, MN1 receives an IPha change instruction (S141). The subsequent procedure is the same as the flow of the procedure process shown in FIG. 10 except for the timing and the deletion method for deleting the IPha information in the location management table 41, and a duplicate description will be omitted.

  In this way, by matching the timing of deletion due to the expiration of the timer in step S140 and the timing of the IPha reacquisition request from MN1 in step S141, it is possible to avoid a state mismatch as in FIGS. Can be reassigned. As a method of matching, for example, a user who has received a notification that the timer has expired may input a change instruction to MN1 or use the timer of MN1 to match with the timer of LM4. As described above, due to the expiration of the timer associated with the IPha information stored in the position management table 41, the position information including IPha # 1 is deleted, thereby overlapping with the position information including IPha # 2. Management can be avoided.

[2.9. Legitimacy evaluation (when valid)]
Further, the present invention will be described with reference to FIGS. 13 and 14 that the validity of the IPha used by the MN 1 can be evaluated on the NW side during the location registration procedure.
An evaluation method in the case where MN1 is using IPha # 1 that has been properly paid out will be described with reference to FIG. Here, it is assumed that the terminal identifier of MN1 is DUID # 1. Also, it is assumed that DUID # 1 and IPha # 1 are stored in association with each other in the IP address management table 31 of the DHCPv6 server 3.
First, MN1 transmits LR including IPha # 1 to AR2 (S160).

The address validity confirmation unit 25 of the AR2 inquires the DHCPv6 server 3 by a DHCP CONFIRM message including the DUID # 1 and the IPha # 1 in order to confirm the validity of the IPha # 1 included in the LR (S161).
When the DHCPv6 server 3 receives the DHCP CONFIRM message, the address validity evaluation unit 35 of the DHCPv6 server 3 matches the IP address management table 31 (S162). Specifically, the address validity evaluation unit 35 determines based on the IP address management table 31 whether or not IPha # 1 assigned to MN1 is assigned to another MN. Here, since DUID # 1 and IPha # 1 are stored in association with each other in the IP address management table 31, the address validity evaluation unit 35 evaluates that IPha # 1 is a regular payout IPha. .

The DHCPv6 server 3 transmits to the AR 2 a DHCP REPLY for notifying that the IPha # 1 is a regular payout IPha (S163).
The address validity confirmation unit 25 of AR2 confirms that IPha # 1 is a regular payout IPha. The AR 2 transmits the LU including the IPha # 1 of the regular payout to the LM 10 (S164).
The LM 4 that has received the LU registers the IPha # 1 and the identifier of AR2 in association with each other in the location management table 41 (S165), and transmits LUAck to the AR 20 (S166). AR2 transmits LRAck including IPha # 1 to MN1 (S167). Thereby, MN1 completes location registration.
Thus, since IPha # 1 is a regular one, location registration is performed after normality confirmation on the NW side.

[2.10. Validity assessment (if incorrect)]
Next, with reference to FIG. 14, an evaluation method when an illegal IPha is used such that the MN 1 has not been paid out from the DHCPv6 server 3 or the lease period has expired even though it has been paid out. explain. Here, it is assumed that MN1 uses IPha # 2 as an illegal address. The terminal identifier of MN1 is DUID # 1. In addition, it is assumed that DUID # 2 and IPha # 2 are associated with each other and stored in the IP address management table 31 of the DHCPv6 server 3.
First, MN1 transmits LR including IPha # 2 to AR2 (S170).
In order to confirm the validity of the IPha # 1, the AR 2 inquires the DHCPv6 server 3 with a DHCP CONFIRM message including the DUID # 1 and the IPha # 2 (S171).

  When the DHCPv6 server 3 receives the inquiry, the address validity evaluation unit 35 of the DHCPv6 server 3 matches the IP address management table 31 in order to evaluate the validity of IPha # 2 assigned to MN1 (S172). ). Specifically, the address validity evaluation unit 35 determines based on the IP address management table 31 whether or not IPha # 2 assigned to MN1 is assigned to another MN. Here, the IP address management table 31 stores IPha # 2 in association with DUID # 2. This means that another MN is using IPha # 2. Therefore, the address validity evaluation unit 35 evaluates that IPha # 1 used by MN1 is not valid. The DHCPv6 server 3 transmits to the AR 2 a DHCP REPLY notifying that the IPha # 1 used by the MN 1 is illegal (S173).

The address validity confirmation unit 25 of AR2 receives DHCP REPLY and confirms that it is not valid. For this reason, the address acquisition proxy unit 22 of AR2 transmits DHCP REQUEST in order to perform the address acquisition procedure to the DHCPv6 server 3 (S174).
The DHCPv6 server 3 issues a new IPha # 3 to the MN 1 (S175). Then, the DHCPv6 server 3 adds the DUID # 1 and the IPha # 3 that has been normally paid out to the IP address management table 31 (S176). The DHCPv6 server 3 transmits DHCP REPLY including IPha # 3 to the AR 2 (S177).

The post-address acquisition location registration unit 23 of AR2 transmits the LU including IPha # 3 to LM4 (S178).
The LM 4 that has received the LU updates the location management table 41 (S179), and transmits LUAck to the AR 2 (S180).
The allocated address notification unit 24 of AR2 transmits LRAck including IPha # 3 to MN1 (S181). Thereby, the legitimate IPha # 3 is set in the MN1, and the location registration is completed (S182).
Here, since IPha # 2 is illegal, after the validity is confirmed on the NW side, the regular IPha is acquired, and the regular IPha allocation is performed on the MN1 simultaneously with the location registration. In this way, MN1 can always use regular IPha.

  As described above, by having the address acquisition proxy unit 22 in the AR2, the message between the MN1 and the AR2 can be merged with the location registration procedure, and the amount of messages between the MN1 and the AR2 can be suppressed. . At the same time, the location management table 41 of the LM 4 can be updated dynamically. In addition, the reassignment of IPha can always assign a unique IPha to MN1 regardless of whether it is led by NW or MN. Furthermore, it becomes possible for the NW operator to evaluate the validity of the IPha used by the MN 1.

  INDUSTRIAL APPLICABILITY The present invention can be used in the field of dynamically allocating IPha to mobile communication terminals while suppressing the amount of messages in a wireless section and maintaining the consistency of IPha to be managed.

It is a block diagram which shows the whole structure of the address dynamic allocation system which concerns on embodiment of this invention. It is a block diagram which shows the function structure of AR which concerns on the embodiment. It is a block diagram which shows the function structure of the position management apparatus which concerns on the same embodiment. It is a block diagram which shows the function structure of LM based on the embodiment. It is the figure which showed the procedure which united IPha dynamic allocation and location registration which concern on the embodiment. It is the figure which showed the location registration procedure after IPha acquisition which concerns on the embodiment. It is the figure which showed the re-acquisition procedure (update of a location management table triggered by the old IPha deletion message from a DHCPv6 server) by NW after the IPha acquisition which concerns on the same embodiment. It is the figure which showed the re-acquisition procedure (location management table update triggered by transmission of old IPha information from MN to AR) led by NW after IPha acquisition according to the embodiment. It is the figure which showed the re-acquisition procedure (location management table update at the time of timer expiration in LM) led by NW after IPha acquisition according to the same embodiment. It is the figure which showed the re-acquisition procedure (location management table update triggered by the old IPha deletion request message from the DHCPv6 server) by MN after IPha acquisition according to the embodiment. It is the figure which showed the re-acquisition procedure (location management table update triggered by transmission of old IPha information from MN to AR) led by MN after IPha acquisition according to the same embodiment. It is the figure which showed the re-acquisition procedure (location management table update at the time of timer expiration in LM) led by MN after IPha acquisition according to the same embodiment. It is the figure which showed the confirmation procedure (in the case of regular IPha use) of IPha correctness based on the embodiment. It is the figure which showed the confirmation procedure (in the case of unauthorized IPha use) of IPha legitimacy concerning the embodiment. It is the figure which showed the IPha fixed allocation procedure and the location registration procedure in the past. It is the figure which showed the conventional IPha dynamic allocation procedure and location registration procedure.

Explanation of symbols

1 MN (mobile communication terminal)
2 AR (relay equipment)
21 Address acquisition necessity determination unit 22 Address acquisition proxy unit (address acquisition proxy means)
23 Location registration unit after address acquisition 24 Assigned address notification unit 25 Address validity confirmation unit 3 DHCPv6 server (address management device)
31 Address management table (address management means)
32 Address deletion unit 33 Old address deletion request unit 34 Address reassignment request unit 35 Address validity evaluation unit 4 LM (location management device)
41 Location management table (location management means)
42 Location information deletion part

Claims (4)

In an address management device that assigns terminal identification address information for uniquely identifying the mobile communication terminal in the mobile communication network to the mobile communication terminal,
Address management means for managing terminal identification address information assigned to the mobile communication terminal;
Corresponding to the process of assigning terminal identification address information different from the terminal identification address information managed by the address management means to the mobile communication terminal, and the terminal identification address information managed by the address management means Address deletion means for deleting terminal identification address information managed by the address management means in at least one of the cases where the valid period has passed ,
When performing processing for assigning terminal identification address information different from the terminal identification address information managed by the address management means to the mobile communication terminal, it matches the terminal identification address information managed by the address management means Old address deletion request means for transmitting a message requesting deletion of location information including terminal identification address information to a location management device that manages location information of the mobile communication terminal;
Address management apparatus comprising: a. When a valid period associated with the terminal identification address information has passed, a different terminal identification address is assigned to the mobile communication terminal to which the terminal identification address information associated with the information representing the valid period is assigned. 2. The address management apparatus according to claim 1 , further comprising address reassignment requesting means for transmitting address reassignment request instruction data for instructing reacquisition of information. When receiving a validity confirmation request message for confirming whether the terminal identification address information assigned to the mobile communication terminal is valid, the terminal identification address information assigned to the mobile communication terminal is , wherein whether assigned to another mobile communication terminal, in claim 1 or 2, further comprising determining the address validity evaluation means based on the information managed by the address management means Address management device. In a location management device that manages location information of mobile communication terminals,
When a message for requesting registration of location information of the mobile communication terminal is received from a relay device that relays communication of the mobile communication terminal, the mobile communication terminal included in the message is uniquely identified in the mobile communication network. Position information management means for associating the terminal identification address information for identification with the identification information of the relay device and managing it as position information;
When the address management device managing the terminal identification address information performs a process of assigning terminal identification address information different from the terminal identification address information managed by the address management device to the mobile communication terminal, When receiving a terminal identification address information deletion request matching the terminal identification address information managed by the address management device from the address management device, the terminal identification address from the mobile communication terminal via the relay device When at least one of the case where an information deletion request is received and the case where the validity period associated with the terminal identification address information managed by the position information management means has elapsed, the position information management means and a position information deletion means for deleting the location information including the end-terminal identification address information that are managed A location management device characterized by that.

Images