JP2748871B2 - Location registration method and location registration method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a location registration system in a computer network, and more particularly to a computer network in which a plurality of sub-networks are connected to each other by a repeater, and a mobile terminal moves between the plurality of sub-networks. , A location registration method required to support a mobile terminal.

[0002]

2. Description of the Related Art Conventionally, in a computer network of this kind, in order to support a mobile terminal, an address (logical address) for identifying the terminal itself irrespective of the terminal position and an address (position address) depending on the terminal position are known. ) Are known (for example, Fumio Teraoka, Yasuhiko Yokote, and Mario Tokoro, "Transmission of Hosts in Wide Area Networks", Computer Software, Vol. 9, No. 3 (1992), pp50-6
4).

Conventionally, in a computer network using two addresses as described above, when a mobile terminal moves, the mobile terminal moves to a sub-network before the movement, and the position address used before the movement is completed is completed. A disconnection procedure is performed to notify the sub-network before moving that it is unusable.

FIG. 9 is a flowchart showing a processing procedure of the disconnection procedure in the mobile terminal.

It is always checked whether there is a power-off interrupt (step 200). When moving, the connected network is monitored (step 201), and it is confirmed whether the connected network changes (step 202). If the connection network does not change, the process returns to step 200 and the above operation is repeated. If the connection network changes, a disconnection procedure for notifying the pre-movement network that the previously used location address is unusable is performed (step 20).
3) A connection procedure for notifying a logical address is performed on the moved network to which a new location address is assigned (step 204).

[0009] In the case of the procedure shown in FIG. 9, information on which subnetwork the mobile terminal is currently connected to and information on whether the mobile terminal has moved to another subnetwork are required. The mobile terminal can know the currently connected sub-network and that the movement has been performed, for example, by monitoring the physical line, detect the movement in this way, and further detect the detection result. Perform a disconnection procedure for the sub-network before and after the sub-network.

[0007]

However, when the mobile terminal detects that it has moved to a new sub-network, for example, when the mobile terminal is connected via a wireless line,
It may not be possible to connect to the sub-network before the move. In such a case, there is a problem that the conventional method as described above cannot normally perform a disconnection procedure in the network before moving.

SUMMARY OF THE INVENTION The present invention has been made in view of the above-mentioned problems of the prior art, and is intended to reliably register a location of a mobile terminal even if the mobile terminal moves between sub-networks. An object of the present invention is to realize a location registration method that can be performed.

[0009]

[0010]

[0011]

[0012]

[0013]

[0014]

According to the position registration method of the present invention, in a network in which a plurality of sub-networks are interconnected by a repeater and a mobile terminal moves between the plurality of sub-networks, the first sub-network A location registration method performed when an existing mobile terminal moves to a second sub-network, the mobile terminal comprising: a) means for detecting that the mobile terminal has moved to the second sub-network; Means for performing a connection procedure for notifying a movement notification message to a second sub-network; c) sending a movement completion message to the first sub-network before the movement via the second sub-network; Means for performing a disconnection procedure for notification; d) the mobile terminal moves between a plurality of sub-networks independently of the location of the mobile terminal. No change when moving
E) a second terminal identifier that changes as the mobile terminal moves between a plurality of sub-networks, and the detection is performed using each of these identifiers. F) means for receiving a movement notification message from the mobile terminal; g) means for receiving a movement completion message from the mobile terminal; h) for the mobile terminal that transmitted the movement notification message, Means for newly assigning a terminal identifier; i) means for transmitting the movement completion message based on the movement notification message upon receiving the movement notification message; and j) means for completing the movement when receiving the movement completion message. Means for releasing the assignment of the second terminal identifier based on the message. .

[0015] Further, the means for notifying the subnetwork identifier includes: a) as the subnetwork identifier of each subnetwork, a pair of the subnetwork identifier and the identifier of the terminal identifier management server that manages each subnetwork. Is also good.

Also, the movement notification message may include: a) a first terminal identifier; b) a second terminal identifier; c) a subnetwork identifier for identifying a first subnetwork; And an identifier of the terminal identifier management server existing in the network.

Further, means for performing cutting procedure, a) the terminal management server for managing the second subnetwork to the terminal identifier management server which manages a first sub-network, and notifies the movement completion message, it It may be.

Further, the movement completion message may include: a) a subnetwork identifier for identifying a second subnetwork; and b) a first mobile terminal identifier.

[0019]

According to the present invention, when a mobile terminal moves to a different subnetwork, a disconnection procedure for the subnetwork before the movement is performed via the subnetwork after the movement.
For this reason, even when the terminal moves and the mobile terminal cannot communicate with the subnetwork before the movement, the disconnection procedure in the subnetwork before the movement can be performed normally.

[0020]

FIG. 1 is a flowchart showing the operation of a mobile terminal according to an embodiment of the present invention. The operation of this embodiment will be described with reference to FIG.

In FIG. 1, step 100 is a mobile terminal power-off interruption detecting step, step 101 is a connected network monitoring step, step 102 is a connected network change detecting step, step 103 is a step of connecting to a subnetwork after moving, step 104.
Is a disconnection step to the pre-movement sub-network.

In a power off interruption detecting step 100, it is detected whether or not the power of the mobile terminal is turned off.
When the power of the mobile terminal is turned off, the communication is terminated and all the flows are terminated. If it is confirmed in the power off interrupt detection step 100 that no power off interrupt occurs, the network monitor step 1
01, the network is monitored to obtain information on which subnetwork the mobile terminal is currently connected to.

Here, the mobile terminal has two identifiers, an identifier (location identifier) dependent on the subnetwork to which the mobile terminal is currently connected and an identifier (logical identifier) independent of the subnetwork currently connected. .

Assuming that an identifier based on the Internet Protocol (IP) hierarchized in the network identification unit and the terminal identification unit is used as the two identifiers, for example, as shown in FIG. The mobile terminal location identifier 300 is composed of a currently connected subnetwork address 302 and a host address 303 for identifying the terminal in the subnetwork, and the logical identifier 301 is a subnetwork (home network) that manages the mobile terminal. Address 304 and host address 305 for identifying the mobile terminal in the home network
Can be composed of

The network monitor step 10
1 can be realized as follows by using the network model shown in FIG. 3, for example. In FIG. 3, reference numerals 400 to 402 denote bus-like sub-networks,
Reference numerals 3 and 404 denote repeaters for connecting the sub-networks 400 to 402, and reference numerals 405 to 407 denote sub-networks 400 to 402.
Reference numeral 402 denotes a subnetwork identifier notifying server that periodically notifies each of the subnetwork identifiers, and periodically broadcasts the subnetwork identifier to the subnetwork 400 to 402. 408 is a mobile terminal, and 409 to 411 are subnetwork identifiers notified by the subnetwork identifier notification server by 405 to 407.

As the subnetwork identifiers 409 to 411, the connected subnetwork address 302 of FIG. 2 defined by the subnetwork 400 to 402 can be used. The mobile terminal 408 connected to the subnetwork 401 can identify the currently connected subnetwork by receiving the subnetwork identifier 410 broadcast by the subnetwork 401.

In the model shown in FIG. 3, when the mobile terminal 408 connected to the subnetwork 401 moves to another subnetwork, for example, the subnetwork 400, the mobile terminal 408 detects the change of the connected network shown in FIG. Step 102 detects that the connected subnetwork has changed.

The connection network detecting step 102 in the mobile terminal can be realized based on the flowchart shown in FIG.

FIG. 4A is a flowchart showing the operation of the mobile terminal 408 in the initial state, and FIG. 4B is a flowchart showing the operation of the mobile terminal 408 in the steady state.

First, the operation of the mobile terminal 408 in the initial state will be described with reference to FIG.

The mobile terminal 408 is connected to the subnetwork 40
0, the sub-network 40
Monitor the received signal flowing to 0 (step 501),
It is checked whether a subnetwork identifier has been received from the subnetwork identifier notification server 405 (step 502). If the reception of the subnetwork identifier is confirmed, the subnetwork identifier is stored as the currently connected subnetwork (step 503). As described above, when the current connection subnetwork identifier is stored, the mobile terminal enters the steady state operation shown in the flowchart of FIG.

In the steady state, when the mobile terminal 408 has completed the initial state in the subnetwork 400 and is connected as it is, the mobile terminal 408 monitors a signal flowing to the subnetwork 400 (step 511), and receives a signal from the subnetwork identifier notification server 405. It is confirmed whether or not the subnetwork identifier is received (step 51).
2). When the reception of the subnetwork identifier is confirmed, it is confirmed whether or not the received subnetwork identifier is the same as the stored subnetwork identifier (step 513).
Operations 1 to 513 are repeated. If the received subnetwork identifier is different from the stored subnetwork identifier, the stored subnetwork identifier is updated to a new subnetwork identifier (step 514), and the process ends.

The operation of the mobile terminal that operates according to the above-described flowchart will be specifically described with reference to FIG.

When the mobile terminal 408 is connected to the subnetwork 401
Then, the mobile terminal 408 cannot receive the subnetwork identifier broadcast from the subnetwork identifier broadcast server 405, and receives the subnetwork identifier broadcast from the subnetwork identifier broadcast server 406. At this time, the subnetwork identifier from the subnetwork identifier notification server 406 received by the mobile terminal 408 is different from the stored subnetwork identifier. The mobile terminal 408 transmits the stored subnetwork identifier to the subnetwork identifier notification server 406.
Update to the new subnetwork identifier obtained from
Judge that it has moved to a different subnetwork.

As described above, when it is detected that the mobile terminal has moved to a different subnetwork, the mobile terminal connects to the subnetwork after the movement in step 103 (FIG. 1).
), The sub-network after the movement is notified of the movement, and connection to the sub-network after the movement is performed.

The step 103 for connecting to the sub-network after the movement can be realized as follows, for example, by using the network model shown in FIG.

In FIG. 5, 600 to 602 are bus-like sub-networks, 603 and 604 are transponders for connecting the sub-networks, and 605 to 607 periodically notify the sub-network identifiers of the sub-networks 600 to 602. Subnetwork identifier notification server,
608 is a mobile terminal, 609 to 611 are broadcast subnetwork identifiers, 612 to 614 are terminal identifier management servers, 615 is a movement notification message, and 616 is a connection completion message.

The mobile terminal 608 is connected to the subnetwork 601
Will be described as an example.

Subnetwork identifier notification server 606
Broadcasts the subnetwork identifier for identifying the subnetwork 602 and the identifier of the terminal identifier management server 614 as one subnetwork identification message. The mobile terminal 608 communicates with the subnetwork identifier notification server 6
When the subnetwork identification message is received from 06, the connection network detecting means 102 knows that the mobile station has moved to the subnetwork 602 and the identifier of the terminal identifier management server 614.

The mobile terminal 608 requests the position identifier 300 (see FIG. 2) of the subnetwork 602 depending on the subnetwork by transmitting the movement notification message 615 to the terminal identifier management server 614. Movement notification message 615 from mobile terminal 608
The terminal identifier management server 614 that has received the ID selects a subnetwork-dependent identifier that is not currently used, notifies the subnetwork-dependent location identifier 300 to the mobile terminal 608 as a connection completion message 616, and A set of a logical identifier 301 that does not depend on the currently connected subnetwork and a position identifier 300 that depends on the subnetwork notified to the mobile terminal 608 is stored. The mobile terminal 608 receives a connection completion message 616 from the terminal identifier management server 614.
Is received, the mobile terminal 608 updates the subnetwork-dependent identifier 300 of the subnetwork 601 that the mobile terminal 608 had before moving, and performs a connection procedure to the subnetwork 602.

As described above, after the connection to the sub-network after the movement is completed, the connection to the sub-network before the movement is cut by the disconnection step 104 (see FIG. 1) to the sub-network before the movement. Then, the location registration of the mobile terminal is completed.

The step 104 for disconnecting from the sub-network before moving can be realized as follows, for example, by using a network model shown in FIG.

In FIG. 6, 700 to 702 are bus-shaped sub-networks, 703 and 704 are transponders connecting the sub-networks, and 705 to 707 periodically notify the sub-network identifiers of the sub-networks 700 to 702. Subnetwork identifier notification server,
708 is a mobile terminal, 709 to 711 are subnetwork identifiers to be broadcast, 712 to 714 are terminal identifier management servers, 715 is a movement completion message, 716 is a movement notification message, 716 is a connection completion message, and 718 is a confirmation message. The mobile terminal 708 sends the movement notification message 716 as:
1) Identifier • Terminal identifier management server 7 of sub-network before moving
13 The terminal identifier management server 714 is notified of a message including the logical identifier 301 of the mobile terminal 708 that does not depend on the currently connected subnetwork. FIG. 7 is a state transition diagram showing an embodiment of the terminal identifier management servers 712 to 714, and the operation of disconnecting to the pre-move subnetwork will be described with reference to FIGS.

The terminal identifier management server 714 is in the reception waiting state (800), and receives the movement notification message 716 (transition 804 by receiving the movement notification message).
And the location identifier 300 depending on the subnetwork in the subnetwork 702 of the mobile terminal 708,
For example, referring to the terminal identifier management table 900 as shown in FIG. 8, an identifier depending on a subnetwork not currently used in the subnetwork 702 is assigned (80
1). Further, the terminal identifier management server 713 in the subnetwork 701 in which the mobile terminal 708 existed before the movement,
2) Identifier Mobile terminal 70 selected by terminal identifier management server 714
8 transmits a move completion message 715 including the currently connected subnetwork-dependent logical identifier 301 of the mobile terminal 708 in the subnetwork 702 of the No. 8 (the move completed) Transition 808 due to message transmission). When the terminal identification management server 713 receives the movement completion message 715 (transition 806 due to reception of the movement completion message), the mobile terminal 708 determines whether the mobile terminal 708 has a sub-network based on the identifier 301 which is not dependent on the currently connected sub-network. The identifier 301 dependent on the sub-network used when existing in the network 701 is detected, and the identifier determined by the terminal identification management server 714 included in the move completion message 715 is selected as the identifier dependent on the detected sub-network. The terminal 300 updates the identifier 300 depending on the currently connected subnetwork in the subnetwork 702 of the terminal 708 (terminal identification table update 802). When this update operation ends, the terminal identifier management server 713
Sends a confirmation message 718 containing the logical identifier 301 of the mobile terminal 708 that does not depend on the currently connected subnetwork to the terminal identifier management server 714.
5 (transition 807 by confirmation message transmission). The terminal identifier management server 714 receives the confirmation message 718 (transition 808 due to reception of the confirmation message), thereby knowing that the disconnection of the mobile terminal 708 in the sub-network before the movement has been completed. In the management table 900,
The identifier assigned in the assignment state 801 of the terminal identifier 2 (the location identifier 300 depending on the subnetwork of the mobile terminal 708 in the subnetwork 702) and the logical identifier 301 of the mobile terminal 708 that does not depend on the currently connected subnetwork. Set pairs. Further, the terminal identifier management server 714 sends the confirmation message 7
After receiving the connection request message 18, the mobile station 708 transmits a connection completion message 717 to the mobile terminal 708, and transitions to the reception waiting state (800).

In the above-described embodiment, the terminal ID management server 714 notifies the terminal ID management server 713 of the movement completion message. However, the mobile terminal 708 may notify the terminal ID management server 713. It is possible.

[0046]

Since the present invention is configured as described above, even if a mobile terminal moves between sub-networks in a network in which a plurality of sub-networks are interconnected by repeaters, the mobile terminal There is an effect that the location registration can be performed normally.

[Brief description of the drawings]

FIG. 1 is a flowchart showing the operation of an embodiment of the present invention.

FIG. 2 is a diagram showing an example of an address for identifying a mobile terminal.

FIG. 3 is a diagram showing a network model for explaining an embodiment of a network monitor means.

FIGS. 4A and 4B are flowcharts illustrating operations of the mobile terminal according to the embodiment of the present invention.

FIG. 5 is a diagram showing a configuration of a network model for describing an operation of connecting to a subnetwork after movement.

FIG. 6 is a diagram showing a configuration of a network model for explaining a disconnection operation to a subnetwork after movement.

FIG. 7 is a state transition diagram illustrating an operation of the terminal identifier management server in one embodiment.

FIG. 8 is a table showing an example of a terminal identifier management table.

FIG. 9 is a flowchart showing the operation of the conventional example.

[Explanation of symbols]

100 to 104 Step 300 Location identifier 301 Logical identifier 302 Address of the currently connected subnetwork 303 Address for identifying the terminal in the currently connected subnetwork 304 Sub that the terminal is to be home without depending on the connected subnetwork Network address 305 Address for identifying a terminal in the home subnetwork 400 to 402 Subnetwork 403,404 Repeater 405 to 407 Subnetwork identifier notification server 408 Mobile terminal 409 to 411 Subnetwork identifier 501 to 503, 511 to 514 Step 600 602 Sub-network 603 604 Repeater 605-607 Sub-network identifier notification server 608 Mobile terminal 609-611 Sub-network identifier 612-61 Terminal identifier management server 615 Movement notification message 616 Connection completion message 700-702 Subnetwork 703, 704 Repeater 705-707 Subnetwork identifier notification server 708 Mobile terminal 709-711 Subnetwork identifier 712-714 Terminal identifier management server 715 Movement completion message 716 Movement notification message 717 Connection completion message 718 Confirmation message 800 Reception waiting state 801 Terminal identifier 2 allocation state 802 Terminal identifier management table update state 803 Confirmation message waiting state 804 Transition due to reception of movement notification message 805 Transmission of movement completion message to mobile station 806 Transition due to movement completion message reception 807 Transition due to confirmation message transmission 808 To another terminal identification management server Transition According have sent movement completion message

 ──────────────────────────────────────────────────続 き Continuation of the front page (56) References Hirata et al., “Automatic roaming method between mobile communication networks”, IEICE Spring Conference 1991, Paper No. B-348, March 1991, IEICE , "Automobile Phone", 2nd Edition, Corona, August 1985, pp. 185-191 (parts related to "9.3 Location Registration")

Claims (5)

(57) [Claims] 1. A network in which a plurality of sub-networks are interconnected by a repeater and a mobile terminal moves between the plurality of sub-networks, wherein a mobile terminal existing in a first sub-network moves to a second sub-network. A mobile terminal, wherein the mobile terminal comprises: a) means for detecting that the mobile terminal has moved to the second sub-network; and b) transmitting a movement notification message to the second sub-network. Means for performing a connection procedure for notifying; c) means for performing a disconnection procedure for notifying a movement completion message to the first sub-network before the movement via the second sub-network; Independent of the location of the mobile terminal, which does not change when the mobile terminal moves between a plurality of sub-networks;
And e) a second terminal identifier that changes as the mobile terminal moves between a plurality of sub-networks, and detection is performed using each of these identifiers. F) means for receiving a movement notification message from the mobile terminal; g) means for receiving a movement completion message from the mobile terminal; h) for the mobile terminal that transmitted the movement notification message, Means for newly assigning a terminal identifier; i) means for transmitting the movement completion message based on the movement notification message upon receiving the movement notification message; and j) means for completing the movement when receiving the movement completion message. Means for releasing the assignment of the second terminal identifier based on the message; and a terminal identifier management server comprising: Location registration method that. 2. The location registration method according to claim 1, wherein the means for notifying the subnetwork identifier includes: a) a subnetwork identifier as a subnetwork identifier of each subnetwork and a terminal identifier management server for managing each of the subnetworks. A location registration method characterized in that a pair of identifiers is reported as a pair. 3. The location registration method according to claim 1, wherein the movement notification message comprises: a) a first terminal identifier; b) a second terminal identifier; c) a first sub-network. And d) an identifier of a terminal identifier management server existing in the first sub-network. 4. The location registration method according to claim 1, wherein the means for performing a disconnection procedure includes: a) a terminal management server that manages the second sub-network connects the first sub-network; A location registration method for notifying a terminal identification management server to be managed of a movement completion message. 5. The location registration method according to claim 2, wherein the movement completion message includes: a) a subnetwork identifier for identifying a second subnetwork; and b) a first mobile terminal. A location registration method comprising: an identifier;