KR101529175B1 - Method and system for managing mobility in non-encapsulation packet transmission - Google Patents

Abstract

The present invention relates to a mobility management method and a mobility management system in a non-encapsulation packet transmission scheme in an Internet Protocol (IP) -based network, and more particularly, to a mobility management system and a mobility management system in a non- A mobility management system for managing a terminal and a user mobility in a non-encapsulated packet transmission system in an Internet Protocol (IP) based network environment, the system comprising: a Mobility Server Binding Information Table (MSBIT) A mobility server configured to manage binding information for each terminal and each user; And a terminal and a user binding information table (TUBIT) for non-encapsulated packet transmission. The terminal and the user binding information table (TUBIT) are used for storing the mapping relation with the corresponding node for terminal mobility management, And a terminal for managing the session information according to the case of the terminal mobility and the user mobility by changing the address of the packet, sending and recognizing the packet according to the case of transmitting and receiving the data packet, The present invention provides a mobility management system in a non-encapsulated packet transmission system and a mobility management method in a non-encapsulated packet transmission system using the system.

Description

TECHNICAL FIELD [0001] The present invention relates to a non-encapsulation packet transmission method and a mobility management method,

The present invention relates to a terminal and a user mobility management technique, and more particularly, to a mobility management method and a mobility management system in a non-encapsulated packet transmission scheme in an Internet Protocol (IP) based network.

Conventional mobility technologies including Mobile IP (MIP), which has been centered on terminal mobility, transmit a packet using a tunneling technique to maintain session continuity regardless of the movement of the terminal during data transmission. The tunneling technique causes packet overhead and packet transmission delay due to encapsulation and decapsulation at the transmitting and receiving terminals during packet transmission, which causes service disconnection. Therefore, new attempts to improve transmission efficiency are required. Recently, there is a growing interest in user mobility and service mobility. Therefore, it is necessary to study various mobility management methods that are independent of mobile agents and deviate from mobility - oriented research.

The MIP is a method introduced to freely transmit data even when a mobile terminal in use moves using IP. In order to transmit data regardless of an IP address, the MIP performs a routing function to transmit a packet to a temporary address estimated as a location where the mobile terminal moves in the mobility management agent. In addition, the MIP maintains the connection even when the mobile terminal moves, and the mobile terminal maintains the IP address regardless of the location, and manages the location information data of the mobile terminal.

In packet forwarding, MIP uses tunneling technique for communication between mobile terminals. The packet is transmitted to the home agent (HA) of the other party. Upon receiving the packet, the HA confirms the destination address of the packet and encapsulates a new address field in the original packet, . 1 shows an address form of a packet transmitted through tunneling when data is transmitted in an MIP. This tunneling technique introduces packet overhead by adding an address field in addition to the original packet, and includes a problem of delay in handover due to delay in packet transmission.

Non-Encapsulation Mobile IP (US Patent No. 6,842,456 B1) is proposed to solve problems such as packet overhead and handover delay caused by transmission of a packet through a tunneling technique in MIP As a method, 'Non-Encapsulation Mobile IP' at the time of packet transfer transmits a packet to the HA of the other party like the MIP in case of data transmission. The HA changes the destination address of the packet from the home address (HoA) of the mobile terminal to the care of address (CoA), and delivers the packet to the network area where the current terminal exists. The foreign agent (FA) which receives the packet transmitted from the HA changes the destination address of the packet back to the HoA and delivers it to the mobile terminal. FIG. 2 shows an address form of a packet transmitted through an address change in the HA and FA when data is transmitted in the 'Non-Encapsulation Mobile IP' of the prior art.

Although the prior art 'Non-Encapsulation Mobile IP' may be effective in solving the problem of packet transmission by the tunneling technique, it is also considered that the mobility management limited to the terminal mobility, like other technologies including the conventional MIP There is still a problem with the method.

Accordingly, it is an object of the present invention to solve the above-mentioned problems, and it is an object of the present invention to provide a method and apparatus for managing the mobility of a terminal and a user so that a packet can be transmitted while maintaining a session without using tunneling, And a mobility management system in a non-encapsulated packet transmission system capable of performing mobility management.

Another object of the present invention is to solve the problem of mobility management research concentrated on increase of packet overhead and handover delay due to packet transmission by the tunneling technique and terminal mobility described above, Encapsulation in non-encapsulated packet transmission method that can manage mobility of terminal and user so that session can be maintained without tunneling by changing the address of packet at sending and receiving terminal as needed at sending and sending or receiving packet Method and a mobility management system.

Still another object of the present invention is to provide a mobility management method and a mobility management method in a non-encapsulated packet transmission method that can broaden a range of mobility types to which a technology is applied by suggesting a mobility management and a packet transmission method in the case of user mobility together with terminal mobility Management system.

According to another aspect of the present invention, there is provided a mobility management system in a non-encapsulated packet transmission scheme, including: a non-encapsulated packet transmission method in an IP (Internet Protocol) based network environment providing mobility control between homogeneous networks or heterogeneous networks; (MSBIT) for managing a terminal and a user mobility, the mobility management system comprising a mobility server, an access router, and a terminal for managing mobility of a terminal and a user in a mobility management system (BS) of the MS, and the MSBIT manages binding information for each user. The MSBIT includes a Layer 2 address (L2 ID), a permanent Layer 3 address (PA), a Temporary Layer 3 Address (UID), a user key (U-UID), and a user key (UID) for managing the user mobility. Key, a user address (UIP), a routing identifier (RID), and a mapping relation between the corresponding user and the counterpart user.

In addition, the mobility management system in the non-encapsulated packet transmission scheme according to the present invention can be applied to a terminal and a user in a non-encapsulated packet transmission scheme in an IP (Internet Protocol) based network environment providing a mobility control function between homogeneous networks or heterogeneous networks. A mobility management system including a mobility server, an access router, and a terminal for mobility management, the mobility management system comprising: a terminal and a user binding information table (TUBIT) The TUBIT manages session information according to the mobility of the terminal and the mobility of the user. The TUBIT stores and manages the binding information of the two terminals communicating for terminal mobility management, And stores and manages the binding information.

In addition, the mobility management system in the non-encapsulated packet transmission scheme according to the present invention can be applied to a terminal and a user in a non-encapsulated packet transmission scheme in an IP (Internet Protocol) based network environment providing a mobility control function between homogeneous networks or heterogeneous networks. 1. A mobility management system for managing mobility, the mobility server comprising: a mobility server for managing binding information for each terminal and each user by configuring a mobility server binding information table (MSBIT) for managing the terminal and user mobility; And a terminal and a user binding information table (TUBIT) for non-encapsulated packet transmission. The terminal and the user binding information table (TUBIT) are used for storing the mapping relation with the corresponding node for terminal mobility management, And a terminal for managing the session information according to the case of the terminal mobility and the user mobility by changing the address of the packet, sending and recognizing the packet according to the case of transmitting and receiving the data packet, .

According to another aspect of the present invention, there is provided a method for managing mobility in a non-encapsulated packet transmission system, the method comprising: An apparatus for managing terminal mobility in a mobility management system including a mobility server, an access router, and a terminal for managing terminal and user mobility in a packet transmission system, the method comprising: initial terminal registration processing in which the terminal is first registered in the mobility server; An initial data transmission process in which data is initially transmitted to the registered terminal; And a step of the mobile station moving and handing over to a new access router; And a control unit.

The initial terminal registration process of the mobility management method in the non-encapsulated packet transmission method according to the present invention includes: transmitting the terminal registration request message to the mobility server by the terminal; The mobility server generating a terminal information record for the terminal; And the mobility server transmitting a terminal registration request response message to the terminal; And a control unit.

The mobility management method in the non-encapsulated packet transmission method according to the present invention is characterized in that, in the step of the terminal transmitting the terminal registration request message to the mobility server, the mobility server generates a record for managing mobility of the terminal . ≪ / RTI >

Also, the initial data transmission process of the UE in the mobility management method in the non-encapsulated packet transmission method according to the present invention is characterized in that when the UE is in the home network when initial data is transmitted from the corresponding node to the UE, Transmitting a terminal location request message to the mobility server; Searching and updating the terminal information record on the Mobility Server Binding Information Table (MSBIT) configured for the mobility management of the terminal and the user by the mobility server; The mobility server sending a terminal registration request response message to the corresponding node; Storing mapping information of the UE and the correspondent node through a terminal and a user binding information table (TUBIT) configured by the correspondent node for non-encapsulation packet transmission; The correspondent node establishing a session for communication with the terminal; The mobility server transmitting a terminal location notification message to the terminal; Storing the mapping information of the terminal and the correspondent node through the TUBIT; Establishing a session for the terminal to communicate with the correspondent node; The correspondent node configuring a packet in which a destination address and a source address are set as a permanent address (PE) and a correspondent node (PA), respectively; The correspondent node sending a packet to the terminal; And receiving the packet by the terminal; And a control unit.

The mobility management method in the non-encapsulated packet transmission method according to the present invention is characterized in that in the step of the correspondent node transmitting the terminal location request message together with the layer 2 address of the terminal to the mobility server, Such as a 3-tier address and a temporary 3-tier address.

In the mobility management method in the non-encapsulated packet transmission method according to the present invention, the mobility server transmits a terminal location notification message to the terminal, the mobility server predicts communication between the correspondent node and the terminal, Layer address of the correspondent node in advance through a terminal location notification message.

Also, the initial data transmission process of the UE in the mobility management method in the non-encapsulated packet transmission method according to the present invention is characterized in that when the UE is in the external network when initial data is transmitted from the corresponding node to the UE, Configuring a packet in which a destination address and a source address are set as a permanent address (PE) and a correspondent node (PA), respectively; (Destination address and source address) of the packet according to the binding information of the terminal and the user binding information table (TUBIT) of the terminal configured for the non-encapsulation packet transmission by the correspondent node, -TA; The correspondent node sending a packet to the terminal; Changing a destination address and a source address of a packet transmitted from the correspondent node to a correspondent node-PA according to the binding information of the TUBIT; And receiving, by the terminal, the packet; And a control unit.

Also, in the mobility management method in the non-encapsulated packet transmission method according to the present invention, the UE moves and handover to a new access router is performed when the UE and the corresponding node are communicating with each other and a session is established , The terminal transmitting a terminal location update request message to the mobility server; Searching and updating the terminal information record on the Mobility Server Binding Information Table (MSBIT) configured for the mobility management of the terminal and the user by the mobility server; The mobility server transmitting a terminal location update request response message to the terminal; Updating the mapping information between the terminal and the correspondent node through a terminal and a user binding information table (TUBIT) configured by the terminal for non-encapsulation packet transmission; The mobility server sending a terminal location update notification message to the corresponding node; The correspondent node updating the mapping information between the terminal and the corresponding node through the TUBIT; The correspondent node configuring a packet in which a destination address and a source address are set as a permanent address (PE) and a correspondent node (PA), respectively; The correspondent node changing a destination address and a source address of a packet to a Temporary Address and a corresponding node -TA according to the binding information of the TUBIT; The correspondent node sending a packet to the terminal; Changing a destination address and a source address of a packet transmitted from the correspondent node to a correspondent node-PA according to the binding information of the TUBIT; And receiving the packet by the terminal; And a control unit.

The mobility management method in the non-encapsulated packet transmission method according to the present invention further includes the step of the mobility server updating the mobility management record of the terminal in the step of the terminal transmitting the terminal location update request message to the mobility server .

In addition, the mobility management method in the non-encapsulated packet transmission method according to the present invention includes a step in which the mobility server transmits a terminal location update notification message to the correspondent node, which is in communication with the terminal, according to a location update request transmitted from the terminal And informing the mobility server of the updated mobility information of the terminal in advance.

In addition, the mobility management method in the non-encapsulated packet transmission method according to the present invention is a method for managing mobility in a non-encapsulated packet transmission system in an IP (Internet Protocol) based network environment providing a mobility control function between homogeneous networks or heterogeneous networks, 1. A method for managing mobility of a mobility management system including a mobility server, an access router, and a terminal for mobility management, the method comprising: initial user registration process in which a user of the terminal is first registered in the mobility server; An initial data transmission process in which data is initially transmitted as the registered user; And a step of the user moving to a new terminal for handover; And a control unit.

In addition, in the mobility management method in the non-encapsulated packet transmission method according to the present invention, in the initial user registration process, the user accesses the terminal using a user identifier (UID) Requesting; Recognizing the user through the user identifier and converting the user identifier into a user key (U-Key); Transmitting the user registration request message including the user's key and a 3-tier address of the user terminal, which is a routing identifier (RID) of the user, to the mobility server; The mobility server recognizes that it is an initial registration request for the user through a search of a Mobility Server Binding Information Table (MSBIT) configured for mobility management of the MS and the user using the user key, Generating a user information record for the user; Assigning a permanent three-tier address for the user to the mobility server; The mobility server storing user mobility management information in the user record of the MSBIT; The mobility server transmitting a user registration request response message to the terminal together with a user address (UIP); Storing the mapping information between the user and the terminal in the user record of the terminal and the user binding information table (TUBIT) configured by the terminal for non-encapsulation packet transmission; And a control unit.

Also, all the user identifiers related to the user of the mobility management method in the non-encapsulated packet transmission method according to the present invention are registered in advance in the mobility server on the network, and the mobility server manages user identifiers .

Also, in the mobility management method in the non-encapsulated packet transmission method according to the present invention, in the step of transmitting the user registration request message to the mobility server, the mobility server recognizes the user through the user key information, Assigns a user address in the case of registration, creates a mobility management record for the user in the case of initial registration of the user who is connected, and updates the user mobility management record when the mobility information of the connected user is already registered . ≪ / RTI >

Also, an initial data transmission process in which data is initially transmitted to the registered user of the mobility management method in the non-encapsulated packet transmission method according to the present invention is characterized in that the first terminal and the second terminal are configured for non- (Second terminal) managing the mapping information between the user and the terminal in each terminal and the user binding information table (TUBIT) The first terminal transmits a user location request message to the mobility server together with the user identifier; The mobility server retrieves and updates the first user's record in a Mobility Server Binding Information Table (MSBIT) configured for mobility management of the terminal and the user using the user key, Recording the record number of the second user in the binding information record number field; The mobility server sending a user location request response message to the second terminal; Storing the mapping information between the first user and the second user through the TUBIT; Establishing a session for communication with the first user by the second terminal to which the second user is connected; The mobility server transmitting a user location notification message to the first terminal; Storing the mapping information between the first user and the second user through the TUBIT; Establishing a session in preparation for communication with the second user of the first terminal to which the first user is connected; The second terminal configuring a packet having a destination address and a source address set to a first user address and a second user address, respectively; Changing the destination address and the source address of the packet to a first routing identifier and a second routing identifier by performing an address change operation of the packet according to the binding information of the TUBIT; Transmitting a packet sent from the second terminal to the first terminal; Changing the destination address and the source address of the packet to a first user address and a second user address, respectively, by performing an address changing operation of a packet transmitted from the second terminal according to the binding information of the TUBIT; And receiving the packet by the terminal; And a control unit.

The mobility management method in the non-encapsulated packet transmission method according to the present invention is characterized in that in the step of the second terminal transmitting the user location request message together with the user identifier to the mobility server, Such as a permanent 3-tier address of the user and a 3-tier address of the terminal being connected, which is a routing identifier, for example, and predicts communication between the two users, And information such as a user identifier and a routing address of the mobile terminal in advance.

Also, in the mobility management method in the non-encapsulated packet transmission method according to the present invention, the process of moving from the user to a new terminal and performing a handover may be such that the first user and the second user are communicating with each other, In the case of handover as the first user moves to the second terminal in another access router while a session for communication with the first user is being performed, Requesting user access to the second terminal using the first user identifier; Recognizing the first user through the first user identifier and converting the first user identifier into the first user key; The second terminal transmitting a user registration request message to the mobility server; The mobility server determines whether it is a location update request for the first user through a search of a Mobility Server Binding Information Table (MSBIT) configured for mobility management of the MS and the user using the first user key Updating a user information record for the first user; The mobility server transmitting a user registration request response message to the second terminal together with a first user address; Storing mapping information between a user and a terminal in the first user record of each terminal and a user binding information table (TUBIT) configured for non-encapsulated packet transmission by the second terminal; Storing the mapping information between the first user and the second user through the TUBIT; Establishing a session for the first terminal with which the first user is connected to communicate with the second user via a first user address and a second user address; The mobility server sending a user location update message to the second terminal; Updating the mapping information between the first user and the second user through the TUBIT; The second terminal configuring a packet having a destination address and a source address set to a first user address and a second user address, respectively; Changing a destination address and a source address of the packet to a first routing identifier and a second routing identifier by performing an address changing operation of the packet according to the binding information of the TUBIT; Transmitting a packet sent from the second terminal to the first terminal; The first terminal performs an address change operation of the packet transmitted from the second terminal according to the binding information of the TUBIT and changes the destination address and the source address of the packet to the first user address and the second user address, respectively step; And receiving, by the first terminal, the packet; And a control unit.

The mobility management method in the non-encapsulated packet transmission method according to the present invention is characterized in that, in the step of the second terminal transmitting a user registration request message to the mobility server, the mobility server transmits the user registration request message to the corresponding user And informing the user of the updated mobility information of the user in advance through the user location update notification message.

As described above, according to the present invention, a terminal providing non-encapsulated packet transmission in an IP-based network and a tunneling method by transmitting or receiving a packet by changing the address of a packet, So that the session can be maintained.

In addition, the present invention has an advantage of widening the range of mobility types to which the technology is applied by suggesting mobility management and packet transmission methods in the case of user mobility together with terminal mobility.

In addition, in the case of user mobility, in the case of user mobility, the session of the user who intends to use the service is changed by changing the access terminal by using the UID and the user address, so that compared to the conventional technique using the tunneling technique during data transmission, The packet overhead can be solved, and the handover delay can be reduced.

In addition, the present invention is advantageous in that, in the case of user mobility as well as the terminal, a mobility management and a session maintenance technique through data transmission can be configured.

FIG. 1 is a diagram illustrating a format of a forwarding packet in data transmission using a conventional MIP,
2 is a diagram illustrating a format of a forwarding packet in data transmission using a prior art,
FIG. 3 is a basic network configuration diagram to which the mobility management method in the non-encapsulated packet transmission scheme proposed by the present invention is applied,
FIG. 4 is a network configuration diagram illustrating a location change according to movement of a terminal in the case of the terminal mobility proposed in the present invention;
FIG. 5 is a network configuration diagram illustrating movement according to a change of a user's access terminal in the case of user mobility proposed in the present invention;
6 is a flowchart illustrating an initial terminal registration process in the case of terminal mobility according to the present invention;
FIG. 7A is a flowchart illustrating an initial packet transmission process in which data is initially transmitted to a terminal when the terminal is located in a home network in the case of the terminal mobility proposed in the present invention; FIG.
7B is a flowchart illustrating an initial packet transmission process in which data is initially transmitted to a terminal when the terminal is located in an external network in the case of the terminal mobility proposed in the present invention.
FIG. 8 is a flowchart illustrating a handover procedure in which a terminal moves to a new access network in the case of the terminal mobility proposed in the present invention.
9 is a flowchart illustrating an initial user registration process in the case of user mobility proposed in the present invention.
10 is a flowchart illustrating an initial packet transmission process in which data is first transmitted to an access terminal after user registration in the case of user mobility proposed in the present invention.
11 is a flowchart illustrating a handover procedure in which a user moves to a new terminal located in another access network in the case of user mobility proposed in the present invention,
12A and 12B are diagrams showing a packet address configuration by a packet address change operation in a terminal in the case of the terminal mobility proposed in the present invention,
13A and 13B are diagrams showing a packet address configuration according to the packet address change operation in the UE in the case of the user mobility proposed in the present invention,
FIG. 14 is a block diagram of a terminal mobility management information table managed by the mobility server in the case of the terminal mobility proposed in the present invention;
FIG. 15 is a configuration diagram of a user mobility management information table managed by the mobility server in the case of the user mobility proposed in the present invention;
16 is a block diagram of a terminal communication information binding table managed by a terminal in the case of the terminal mobility proposed in the present invention;
FIG. 17 is a block diagram of a terminal and a user communication information binding table managed by a terminal in the case of user mobility proposed in the present invention; FIG.

In order to solve the problem of the mobility management research concentrated on the increase of the packet overhead and the handover delay due to the packet transmission by the tunneling technique described above and the terminal mobility described above, In this paper, we propose a user mobility management scheme for a mobile terminal that does not use tunneling and maintains a session while providing mobility in IP based network. That is, according to the present invention, at the time of data transmission, the transmitting and receiving terminal changes the address of a packet as needed and sends or receives a packet so that a session can be maintained without a tunneling technique.

In addition, the present invention proposes mobility management and packet transmission methods for user mobility as well as terminal mobility, thereby widening the range of mobility types to which the technology is applied. To this end, the mobility server in the network uses the L2 ID, permanent Permanent Address (PA), and temporary Temporary Address (TA) And stores and manages information of the terminal. In the case of user mobility, it is possible to store and manage User Identifier (UID), User Key (U-Key), User Address (User IP) and Routing Identifier (UID) do.

Accordingly, the present invention provides an initial registration process, an initial data packet transmission process, and a handover process according to whether the mobile terminal is a terminal or a user. And, in order to implement the proposed scheme, each mobility management process provides network and terminal operation functions. At this time, a network entity or a communication terminal manages related information by constructing a binding table for mobility support and non-encapsulation packet transmission.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, a detailed description of preferred embodiments of the present invention will be given with reference to the accompanying drawings. It should be noted that the same configurations of the drawings denote the same reference numerals as possible whenever possible. Specific details are set forth in the following description, which is provided to provide a more thorough understanding of the present invention. In the following description of the present invention, detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

FIG. 3 is a diagram illustrating an overall configuration of a network environment to which a mobility management method in a non-encapsulated packet transmission method according to the present invention is applied. FIGS. 4 and 5 are diagrams illustrating the case of terminal mobility and the case of user mobility in the network environment of FIG. FIG. 4 shows a case where a terminal performs handover to a new access network, and FIG. 5 shows a case where a user performs a handover to a new terminal of another access network.

The network according to the present invention shown in FIGS. 3 to 5 is a network structure in which a control function of IP mobility between the same kind of networks or heterogeneous networks is provided. The mobility management system according to the present invention includes a mobility server 400, a Mobility Server, and an M-Server), access routers (300, 310, 320, Access Router, AR), terminals (200, 210) and corresponding nodes (220). The terminals 200 and 210 include both fixed and mobile nodes (Fixed / Mobile Nodes).

The M-Server 400 manages binding information for each terminal or each user to manage terminal and user mobility. To this end, the M-Server 400 internally includes a Mobility Server Binding Information Table (MSBIT). The detailed configuration of the mobility server binding information table is shown in FIGS. 14 and 15. FIG.

FIG. 14 and FIG. 15 are views showing the terminal mobility management information table configuration managed by the mobility server in the case of the terminal mobility proposed by the present invention and the case of the user mobility, respectively.

14, in order to support terminal mobility, the MSBIT includes a 2-layer address (L2 ID) of the MS, a permanent 3-layer address (PA) and a temporary 3-layer address TA according to the location of the MS, And stores and manages a mapping relationship between the terminal and a corresponding node in communication. For example, the second layer address of the UEs may be a MAC address, and the third layer address (PA, TA) may be an IP address, for example. The mapping relationship with the corresponding node can be expressed by inputting the record number in the MSBIT of the corresponding node communicating in the communication terminal binding information field.

15, in order to support user mobility, the MSBIT includes a UID, a U-Key, a UIP, a routing identifier (RID), and a mapping relationship with a user in communication . The UID is user identification information which can accommodate a wide variety of forms, for example, an e-mail address (e.g., aaa@realm.com), a Network Access Identifier (NAI), a telephone number and a Radio Frequency Identification (RFID) It does not specify. U-Key is a network-aware user key that can be expressed by transforming the UID by various methods such as a hashing function.

The M-Server 400 identifies the user using the U-Key when the user registration is requested and determines the UIP allocation. A UIP can be an IP address as a permanent three-tier address (PA) for a particular user. The M-Server 400 may function as a Dynamic Host Configuration Protocol (DHCP) server or a Domain Name Server (DNS), or may be a 3-tier Addresses can be preallocated. The RID is information indicating the actual routing position of the user and can be considered as the 3-tier address of the terminal currently connected to the user. The mapping relationship with the user in communication can be expressed by inputting the record number in the MSBIT of the user corresponding to the communication user binding information field.

The AR 300, 310, and 320 are network access routers connected to the terminals 200 and 210 and the corresponding node 220. According to the embodiment of the non-encapsulated data packet transmission according to the present invention, the ARs 300, 310, and 320 do not need to maintain and manage the binding information table for the terminal and user in order to support the terminal and the user mobility.

The terminals 200 and 210 and the correspondent node 220 basically have a function of accepting a plurality of 3-tier addresses such as a 3-tier address (PA, TA) of a terminal and a UIP of a connected user. Also, the terminals 200 and 210 and the corresponding node 220 manage the terminal and the user binding information table (TUBIT) to support the terminal and user mobility. The detailed configuration of the terminal and user binding information table is shown in Figs.

TUBIT manages binding information according to session information set up on the basis of communication terminals to support terminal mobility and manages binding information according to session information set up based on communication users for user mobility support.

6 is a flowchart illustrating an initial terminal registration process in the case of terminal mobility according to the present invention. Referring to FIG. 6, an initial terminal registration procedure when the terminal T # 1 200 accesses the network for the first time will be described. Upon accessing the network, the terminal T # 1 200 requests the access network for the 3-layer address configuration or performs its own address configuration operation to acquire PA and TA.

Then, the terminal T # 1 200 transmits a terminal registration request message to the M-Server 400 (500). At this time, the L2 ID and the PA of the terminal T # 1 200 are transmitted together. The M-Server 400 searches MSBIT using the L2 ID of the terminal T # 1 200 and recognizes that it is an initial registration request for the terminal T # (501). Then, the M-Server 400 stores [L2 ID: PA] information as information of the terminal T # 1 200 in the MSBIT (501). Thereafter, the M-Server 400 transmits a terminal registration response message to the terminal T # 1 200 (502).

7A and 7B illustrate an initial packet transmission process in which a corresponding node transmits data to a mobile station for the first time when the mobile station is located in the home network and when the mobile station is located in the external network, Fig. 7A and 7B, an initial packet transmission procedure when the correspondent node CN # 1 220 first transmits data to the terminal T # 1 200 will be described. FIG. 7A shows an initial packet transmission process by dividing the case where the terminal is in a home network and FIG. 7B is an external network. In the present invention, the correspondent node CN # 1 (220) is considered to be located in the home network. The procedure when the correspondent node CN # 1 (220) is located in the external network is the same and there is only difference in the mobility information to be transmitted.

Referring to FIGS. 7A and 7B, the correspondent node CN # 1 220 transmits the location information of the terminal T # 1 200 to the M-Server 400 in order to transmit data to the terminal T # And transmits a terminal location request message (600, 700). At this time, the L2 ID of the terminal T # 1 is transmitted together. Accordingly, the M-Server 400 searches and updates 601 and 701 the MSBIT using the L2 ID of the terminal T # 1 200, Any information can be answered.

As shown in FIG. 7A, when the terminal T # 1 200 is located in the home network, the M-Server 400 extracts the PA of the terminal T # 1 as a result of the terminal location request. Also, the M-Server 400 predicts communication between the terminal T # 1 200 and the correspondent node CN # 1 220 through the terminal location request message, The MSBIT is updated (601).

The M-Server 400 transmits a terminal location response message to the correspondent node CN # 1 (220). At this time, the PA of the terminal T # 1 200 is transmitted (602). The correspondent node CN # 1 220 receives the mapping information ([T # 1-PA: @ CN # 1-PA:]) between the terminal T # 1 200 and the correspondent node CN # (603). In order to communicate with the terminal T # 1 (200), a session is established through the PA of the terminal T # 1 (200) and the PA of the correspondent node CN # 1 (220).

Also, the M-Server 400 transmits a terminal location notification message to the terminal T # 1 200 while responding to the terminal location request to the correspondent node CN # 1 (220). At this time, the PA of the correspondent node CN # 1 (220) is also transmitted (604). This is for informing the terminal T # 1 200 of information for communication with the correspondent node CN # 1 (220) so that communication with the corresponding terminal can be prepared in advance before a packet actually arrives. (T # 1-PA: @ CN # 1-PA:) of the terminal T # 1 200 and the correspondent node CN # 1 220 to the TUBIT (605). Then, a session is established through the PA of the terminal T # 1 (200) and the PA of the correspondent node CN # 1 (220) for communication with the correspondent node CN # 1 (220).

Next, the correspondent node CN # 1 (220) configures the destination address and the source address of the packet header as T # 1-PA and CN # 1-PA, respectively, for data transmission to the terminal T # To the T # 1 (100) (606). Since the terminal T # 1 200 is located in the home network, the packet is directly transmitted to the terminal T # 1 200 without any processing. The packet address change format according to the address change operation in the terminal when the data packet is transferred is shown in FIG. 12A.

When the terminal T # 1 200 is located in the external network as shown in FIG. 7B, the M-Server 400 extracts the binding information between the PA and the TA of the terminal T # 1 as a result of the terminal location request. Also, as shown in FIG. 7A, the M-Server 400 updates the MSBIT by writing the record numbers of each other in the communication terminal binding information field on the record of each terminal (701).

Then, the M-Server 400 transmits a terminal location response message to the correspondent node CN # 1 (220) (702). At this time, the PA and TA of the terminal T # 1 (200) are transmitted together. The correspondent node CN # 1 220 receives the mapping information ([T # 1-PA: T # 1-TA @ CN # 1 (220)) between the terminal T # 1 (200) -PA:]) is stored (703). In order to communicate with the terminal T # 1 (200), a session is established through the PA of the terminal T # 1 (200) and the PA of the correspondent node CN # 1 (220).

Also, the M-Server 400 transmits a terminal location notification message to the terminal T # 1 200 while responding to the terminal location request to the correspondent node CN # 1 220 (704). At this time, the PA of the correspondent node CN # 1 (220) is also transmitted. (T # 1-PA: T # 1-TA @ CN # 1) 200 of the correspondent node CN # 1 (220) to the terminal T # PA:]) (705). Then, a session is established through the PA of the terminal T # 1 (200) and the PA of the correspondent node CN # 1 (220) for communication with the correspondent node CN # 1 (220).

The correspondent node CN # 1 (220) configures the destination address and the source address of the packet header as T # 1-PA and CN # 1-PA, respectively, for data transmission to the terminal T # 1 (200). At this time, the correspondent node CN # 1 (220) before data transmission internally performs an address translation operation according to the binding information of TUBIT. This is a function suggested by the present invention to transmit data packets to a destination without encapsulation. Through the address change operation, the destination address and the source address of the packet are changed to T # 1-TA and CN # 1-TAPA, respectively, and sent to the terminal T # 1 200 (706).

When a packet is received from the correspondent node CN # 1 (220), the terminal T # 1 (200) performs an address change operation and receives a packet by referring to binding information of a previously configured TUBIT. At this time, the destination address and the source address of the packet are changed from T # 1-TA and CN # 1-TAPA to T # 1-PA and CN # 1-PA, respectively, and return to the original packet address configuration.

The packet address change format according to the address change operation in the terminal when the correspondent node CN # 1 (220) transfers the initial data packet to the T # 1 (200) located in the external network is shown in FIGS. 12A and 12B. 12A shows the original address format of the packet sent from the correspondent node CN # 1 (220) and the address format after the address change operation. The correspondent node CN # 1 (220) configures a packet in which the destination address and the source address of the packet header are T # 1-PA and CN # 1-PA, and transmits the destination address and the source address 1 to the T # 1-TA and the CN # 1-PA, and transmits them to the T # 1 (200). 12B shows an address format of the packet received from the CN # 1 (220) by the T # 1 (200) and an address format finally received by the address changing operation. When the destination address and the source address of the packet header arrive in the form of T # 1-TA and CN # 1-PA, the T # 1 200 transmits the destination address and the source address of the packet header as T # 1-PA and CN # 1-PA to receive the corresponding packet.

FIG. 8 is a flowchart illustrating a handover procedure of a UE to a new access network in the case of UE mobility according to the present invention. Referring to FIG. 8, the handover procedure when the terminal T # 1 200 moves from the network area of the AR # 1 300 to the network area of the AR # 2 310 will be described in detail. The terminal T # 1 (200) and the correspondent node CN # 1 (210) are in communication and connected to each other through a session.

First, the terminal T # 1 200 transmits a terminal location update request message to the M-Server 400 (800). At this time, the L2 ID and TA of the terminal T # 1 200 are transmitted together. The M-Server 400 searches the MSBIT using the L2 ID of the terminal T # 1 200 and recognizes that it is a location update request for the terminal T # 1 200, ([L2 ID: PA: CoA]) (801). Then, the M-Server 400 transmits a terminal location update response message to the terminal T # 1 200 (802). (T # 1-PA: T # 1-TA @ CN # 1) 200 between the terminal T # 1 200 on the TUBIT and the correspondent node CN # PA:]) (803).

Also, the M-Server 400 transmits a terminal location update notification message to the correspondent node CN # 1 (220) while responding to the terminal location update request to the terminal T # 1 (200) (804). At this time, the TA of the terminal T # 1 (200) is also transmitted. The correspondent node CN # 1 220 receives the mapping information ([T # 1-PA: T # 1-TA @ CN # 1) 220 between the terminal T # 1 200 on the TUBIT and the correspondent node CN # -PA:]) (805).

At this time, since the terminal T # 1 200 and the correspondent node CN # 1 220 are in communication, the PA of the terminal T # 1 200 and the correspondent node CN # 1 220 A session via the PA is established and maintained. Accordingly, the correspondent node CN # 1 (220) configures the destination address and the source address of the packet header as T # 1-PA and CN # 1-PA, respectively, for data transmission to the terminal T # The pre-sending correspondent node CN # 1 (220) internally performs an address changing operation according to the binding information of the TUBIT (806). Through the address change operation, the destination address and the source address of the packet are changed to T # 1-TA and CN # 1-TA, respectively, and sent to the terminal T # 1 200 (807).

When a packet is received from the correspondent node CN # 1 (220), the terminal T # 1 200 refers to the binding information of the previously configured TUBIT, performs the address change operation again, and receives the packet (808). At this time, the destination address and the source address of the packet are changed from T # 1-TA and CN # 1-TA to T # 1-PA and CN # 1-PA, respectively, and return to the original packet address configuration.

9 is a flowchart illustrating an initial user registration process in the case of user mobility according to the present invention. Referring to FIG. 9, the initial user registration procedure when the User # A 100 accesses the network via the terminal T # 1 200 will be described in detail. All the UIDs related to the User # A 100 are registered in the M-Server 400 on the network in advance, and the M-Server 400 manages UIDs for the users.

First, the User # A (100) attempts to access a user to the terminal T # 1 (200) using UID # A (900). The terminal T # 1 200 recognizes the User # A 100 through the UID # A and converts UID # A to register the connection of the User # A 100 with the network so that the terminal T # U-Key # A is generated (901).

Then, the terminal T # 1 200 transmits a user registration request message to the M-Server 400 (902). At this time, the 3-layer address of the terminal T # 1 (200) is transmitted together with the RID of the U-Key #A and the User # A (100). The 3-tier address of the terminal considered as RID information is related to the geographical location of the terminal currently connected to the user.

The M-Server 400 searches MSBIT using U-Key #A and recognizes that it is an initial registration request for User # A 100 to generate a user information record for User # A 100 (903) . Then, the pre-configured user address information is allocated to the UIP of the User # A (100) (904). Then, the M-Server 400 stores [UID # A: U-Key # A: UIP # A: RID # A] information in the MSBIT as information of User # A (905). At this time, the RID # A is the 3-layer address of the terminal T # 1 (200).

The M-Server 400 transmits a user registration response message to the terminal T # 1 200 together with the UIP # A (906). (UEIP # A: RID # A (T # 1 IP)) is stored in the User # A (100) record of the TUBIT (907) .

10 is a flowchart illustrating an initial packet transmission process in which a first user transmits data to a first user according to the present invention. 10, an initial packet transmission procedure in which an access terminal CN # 1 (220) of User # B 110 first transmits data to access terminal T # 1 (200) of User # A 100 is described in detail do.

First, the terminal CN # 1 220 transmits a user location request message to the M-Server 400 in order to check the location information of the User # A 100 in order to transmit data to the User # A 100 1000). At this time, UID # A is transmitted together. The M-Server 400 can use UID # A to respond to any information related to the user such as UIP # A or RID # A (3-layer address of terminal T # 1).

Accordingly, the M-Server 400 extracts the binding information of the UIP # A and the RID # A (T # 1 IP) as a result of the user location request. Also, the M-Server 400 predicts communication between the User # A 100 and the User # B 110 via the user location request message, records the record number of each user in the communication user binding information field on each user record, (1001).

Then, the M-Server 400 transmits a user location response message to the terminal CN # 1 (220). At this time, UIP # B, UIP # A, and RID # A (T # 1 IP) are transmitted together. The terminal CN # 1 220 receives the mapping information ([UIP # A: RID # A @ UIP # B: RID # B]) of the User # A 100 and User # B 110 in the TUBIT (1003). The CN # 1 220, which is the access terminal of the User # B 110, establishes a session through UIP # A and UIP # B for communication with the User # A 100 (1004).

The M-Server 400 also transmits a user location notification message to the terminal T # 1 200 while responding to the user location request to the terminal CN # 1 (220) (1005). At this time, UIP # A, UIP # B and RID # B (CN # 1 IP) are transmitted together. This allows the T # 1 (200), which is an access terminal of the User # A (100), to provide information for communication with the User # B (110) so that the user can prepare for communication with the corresponding user .

The terminal T # 1 (200) receiving this information stores the mapping information ([UIP # A: RID # A @ UIP # B: RID # B]) of User # A 100 and User # B 110 in TUBIT (1006). Then, a session is established through UIP # A and UIP # B for communication with User # B 110 (1007).

The terminal CN # 1 (220) configures the destination address and the source address of the packet header as UIP # A and UIP # B, respectively, for data transmission to the User # A (100). The pre-sending terminal CN # 1 (220) internally performs an address changing operation according to the binding information of the TUBIT (1008). This is to transmit the data packet to the destination without encapsulation. The destination address and the source address of the packet are changed to RID # A (T # 1 IP) and RID # B (CN # 1 IP) (1009).

When a packet is received from the terminal CN # 1 (220), the terminal T # 1 200 refers to binding information of a pre-configured TUBIT, performs an address change operation, and receives a packet (1010). At this time, the destination address and the source address of the packet are changed from RID # A (T # 1 IP) and RID # B (CN # 1 IP) to UIP # A and UIP # B, respectively, and return to the original packet address configuration. The packet address change format according to the address change operation in the terminal when the data packet is transferred is shown in FIGS. 13A and 13B.

In the case of the user mobility, a packet address change format according to an address change operation in a terminal when transferring a data packet is shown in FIGS. 13A and 13B. 13A shows the original address format of the packet sent from the terminal CN # 1 220 of the User B 110 to the terminal T # 1 200 of the User A 100 and the address format after the address change operation. The terminal CN # 1 (220) of the user #B 110 configures a packet having a destination address and a source address of the packet header as UIP # A and UIP # B, and changes the destination address of the packet header And changes the source address to T # 1 IP and CN # 1 IP to transmit to the terminal T # 1 200 of the User # A 100. 13B shows the address format of the packet received from the CN # 1 (220) by the terminal T # 1 (200) of the User # A (100) and the address format finally received by the address changing operation. When the packet arrives in the form of T # 1 IP and CN # 1 IP, the terminal T # 1 200 of the user # A 100 sets the destination of the packet header by the address change operation, And changes the address and the source address to UIP # A and UIP # B to receive the packet.

FIG. 11 is a flowchart illustrating a process of handover from a user to a new terminal located in another access network in the case of user mobility according to the present invention. Referring to FIG. 11, a handover procedure when the User # A 100 moves and changes the access terminal from the terminal T # 1 200 to the T # 2 210 will be described. The user #A 100 is communicating with the User # B 110 and the CN # 1 220 serving as the access terminal of the User # B 110 maintains a communication session with the User # A 100 .

User # A 100 attempts to access a new terminal T # 2 210 using UID # A (1100). T # 2 210 recognizes User # A 100 through UID # A and converts UID # A to register the connection of User # A 100 with the network to generate U -Key # A is generated (1101).

T # 2 210 transmits a user registration request message to M-Server 400 (1102). At this time, the 3-layer address of T # 2 (210) is transmitted together with the RID of U-Key # A and User # A (100). The M-Server 400 searches MSBIT using U-Key #A and recognizes that it is a user location update request for User # A 100, and updates record information of User # A 100 (1103). At this time, RID # A is updated to the 3-layer address of T # 2 (210).

Then, the M-Server 400 transmits a user registration response message to the T # 2 210 together with the UIP # A, UIP # B, and RID # B (CN # 1 IP) (1104). (2105) stores the mapping information ([UIP # A: RID # A (T # 2 IP)] between the user and the terminal in the User # A (100) record of the TUBIT, ([UIP # A: RID # A @ UIP # B: RID # B]) of User # A 100 and User # B 110 (1106). Then, T # 2 210, which is an access terminal of User # A 100, establishes a session through UIP # A and UIP # B for communication with User # B 100 (1107).

Also, the M-Server 400 transmits a user location update notification message to the terminal CN # 1 220 while responding to the user registration request to the T # 2 210 (1108). At this time, UIP # B, UIP # A, and RID # A (T # 2 IP) are transmitted together. This informs the changed information of the User # A 100 to the terminal CN # 1 220 so that the terminal CN # 1 220 repeatedly transmits the information of the User # A 100 to the M- So that there is no need to re-request the location. The CN # 1 220 updates the mapping information ([UIP # A: RID # A @ UIP # B: RID # B]) of User # A 100 and User # B 110 to TUBIT (1109). Since the User # A 100 and User B 110 are communicating, a session through UIP # A and UIP # B is established and maintained in CN # 2 210. [

Next, the terminal CN # 1 (220) configures the destination address and the source address of the packet header as UIP # A and UIP # B, respectively, for data transmission to the User # A (100). The terminal CN # 1 (220) before the data transmission internally performs an address change operation according to the binding information of the TUBIT (1110). The destination address and the source address of the packet are changed to RID # A (T # 2 IP) and RID # B (CN # 1 IP) (1111). When a packet is delivered from the terminal CN # 1 (220), the T # 2 210 refers to the pre-configured binding information of the TUBIT, performs the address change operation, and receives the packet (1112). At this time, the destination address and the source address of the packet are changed from RID # A (T # 2 IP) and RID # B (CN # 1 IP) to UIP # A and UIP # B, respectively, and return to the original packet address configuration.

As described above, the mobility management method and the mobility management system in the non-encapsulated packet transmission method according to the present invention include a terminal providing non-encapsulated packet transmission in an IP-based network and a terminal providing non- The session can be maintained without tunneling by changing the address of the packet as needed and sending or receiving the packet.

In addition, the mobility management method and the mobility management system in the non-encapsulated packet transmission method according to the present invention propose mobility management and packet transmission methods in the case of user mobility together with terminal mobility, thereby widening the range of mobility types to which the technology is applied have.

In addition, the mobility management method and the mobility management system in the non-encapsulated packet transmission method according to the present invention are characterized in that, in case of user mobility, Management and data transmission.

While the present invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not limited to the disclosed embodiments, but is capable of various modifications within the scope of the invention. In particular, the present invention described above is not implemented only by the apparatus and / or method, but may be implemented through a program for realizing functions corresponding to the configuration of the present invention, a recording medium on which the program is recorded, The embodiments can be easily implemented by those skilled in the art from the description of the embodiments described above.

Therefore, the scope of the present invention should not be limited by the described embodiments, but should be determined by the scope of the appended claims and equivalents thereof.

Claims (21)

In a mobility management system including a mobility server, an access router, and a terminal for managing terminal and user mobility in a non-encapsulated packet transmission scheme in an IP (Internet Protocol) -based network environment providing mobility control between homogeneous networks or heterogeneous networks As a result,
The mobility server configures a mobility server binding information table (MSBIT) to manage terminal and user mobility, manages binding information for each terminal or each user,
The MSBIT stores and manages the L2 layer address (L2 ID), the persistent Layer 3 address (PA), the temporary 3-layer address (TA), and the mapping relationship between the terminal and the counterpart terminal And stores and manages a mapping relationship between a user identifier (UID), a user key (U-Key), a user address (UIP), a routing identifier (RID) A mobility management system in a non-encapsulated packet transmission scheme. In a mobility management system including a mobility server, an access router, and a terminal for managing terminal and user mobility in a non-encapsulated packet transmission scheme in an IP (Internet Protocol) -based network environment providing mobility control between homogeneous networks or heterogeneous networks As a result,
The UE configures the Terminal and User Binding Information Table (TUBIT) for non-encapsulated packet transmission to manage session information according to the mobility of the UE and the mobility of the user,
Wherein the TUBIT stores and manages binding information of two terminals communicating for terminal mobility management and stores and manages binding information of two users communicating for user mobility management. Management system. A mobility management system for managing a terminal and a user mobility in a non-encapsulated packet transmission scheme in an IP (Internet Protocol) -based network environment providing mobility control between homogeneous networks or heterogeneous networks,
A mobility server that manages binding information for each terminal and each user by configuring a Mobility Server Binding Information Table (MSBIT) for managing the terminal and user mobility; And
The terminal and the user binding information table (TUBIT) are configured to transmit the non-encapsulated packet, the mapping relation with the corresponding node is stored for terminal mobility management, and the corresponding user and node And a terminal for managing the session information according to the case of the terminal mobility and the user mobility by changing the address of the packet, sending and recognizing the packet according to the transmission and reception of the data packet A mobility management system in a non-encapsulated packet transmission system. A mobility management system including a mobility server, an access router, and a terminal for managing terminal and user mobility in a non-encapsulated packet transmission system in an Internet Protocol (IP) based network environment providing mobility control between homogeneous networks or heterogeneous networks A method for managing terminal mobility,
An initial terminal registration process in which the terminal is first registered in the mobility server;
An initial data transmission process in which data is initially transmitted to the registered terminal; And
The mobile station moves to a new access router; / RTI >
The initial data transmission process of the UE includes:
When the terminal is in the home network when transmitting initial data from the corresponding node to the terminal,
The correspondent node sending a terminal location request message to the mobility server;
Searching and updating the terminal information record on the Mobility Server Binding Information Table (MSBIT) configured for the mobility management of the terminal and the user by the mobility server;
The mobility server sending a terminal registration request response message to the corresponding node;
Storing mapping information of the UE and the correspondent node through a terminal and a user binding information table (TUBIT) configured by the correspondent node for non-encapsulation packet transmission;
The correspondent node establishing a session for communication with the terminal;
The mobility server transmitting a terminal location notification message to the terminal;
Storing the mapping information of the terminal and the correspondent node through the TUBIT;
Establishing a session for the terminal to communicate with the correspondent node;
The correspondent node configuring a packet in which a destination address and a source address are set as a permanent address (PE) and a correspondent node (PA), respectively;
The correspondent node sending a packet to the terminal; And
Receiving the packet by the terminal; And transmitting the mobility management information to the non-encapsulated packet transmission method. 5. The method of claim 4,
Transmitting the terminal registration request message to the mobility server;
The mobility server generating a terminal information record for the terminal; And
The mobility server transmitting a terminal registration request response message to the terminal; And transmitting the mobility management information to the non-encapsulated packet transmission method. 6. The method of claim 5, wherein, in the step of transmitting the terminal registration request message to the mobility server,
Further comprising: the mobility server generating a record for mobility management of the mobile station. delete 5. The method of claim 4, wherein the correspondent node transmits a terminal location request message together with a layer 2 address of the terminal to the mobility server,
Further comprising the mobility server providing any information related to the terminal, such as a persistent 3-tier address and a temporary 3-tier address of the terminal. 5. The method of claim 4, wherein the mobile server transmits a terminal location notification message to the terminal,
Wherein the mobility server anticipates communication between the correspondent node and the terminal and informs the terminal of the 3-layer address of the corresponding node in advance through the terminal location notification message. 5. The method of claim 4,
When the terminal is in an external network when initial data is transmitted from the corresponding node to the terminal,
The correspondent node configuring a packet in which a destination address and a source address are set as a permanent address (PE) and a correspondent node (PA), respectively;
(Destination address and source address) of the packet according to the binding information of the terminal and the user binding information table (TUBIT) of the terminal configured for the non-encapsulation packet transmission by the correspondent node, -TA;
The correspondent node sending a packet to the terminal;
Changing a destination address and a source address of a packet transmitted from the correspondent node to a correspondent node-PA according to the binding information of the TUBIT; And
Receiving the packet by the terminal; And transmitting the mobility management information to the non-encapsulated packet transmission method. 5. The method of claim 4, wherein the step of the mobile station moving to a new access router comprises:
When the terminal and the correspondent node are communicating with each other and a session connection is established,
The terminal transmitting a terminal location update request message to the mobility server;
Searching and updating the terminal information record on the Mobility Server Binding Information Table (MSBIT) configured for the mobility management of the terminal and the user by the mobility server;
The mobility server transmitting a terminal location update request response message to the terminal;
Updating the mapping information between the terminal and the correspondent node through a terminal and a user binding information table (TUBIT) configured by the terminal for non-encapsulation packet transmission;
The mobility server sending a terminal location update notification message to the corresponding node;
The correspondent node updating the mapping information between the terminal and the corresponding node through the TUBIT;
The correspondent node configuring a packet in which a destination address and a source address are set as a permanent address (PE) and a correspondent node (PA), respectively;
The correspondent node changing a destination address and a source address of a packet to a Temporary Address and a corresponding node -TA according to the binding information of the TUBIT;
The correspondent node sending a packet to the terminal;
Changing a destination address and a source address of a packet transmitted from the correspondent node to a correspondent node-PA according to the binding information of the TUBIT; And
Receiving the packet by the terminal; And transmitting the mobility management information to the non-encapsulated packet transmission method. 12. The method of claim 11, wherein, in the step of the terminal transmitting the terminal location update request message to the mobility server,
Further comprising: the mobility server updating the mobility management record of the terminal. ≪ RTI ID = 0.0 > 11. < / RTI > 12. The method of claim 11, wherein, in response to a location update request transmitted from the terminal, the mobility server transmits a terminal location update notification message to the correspondent node,
Further comprising informing the mobility server of mobility information of the updated terminal in advance. ≪ RTI ID = 0.0 > 18. < / RTI > A mobility management system including a mobility server, an access router, and a terminal for managing terminal and user mobility in a non-encapsulated packet transmission system in an Internet Protocol (IP) based network environment providing mobility control between homogeneous networks or heterogeneous networks A method for managing user mobility,
An initial user registration process in which a user of the terminal is first registered in the mobility server;
An initial data transmission process in which data is initially transmitted as the registered user; And
A process in which the user moves to a new terminal and performs a handover; The method of claim 1, wherein the mobility management method is a non-encapsulated packet transmission method. 15. The method of claim 14,
The user requesting a user access to the terminal using a user identifier (UID);
Recognizing the user through the user identifier and converting the user identifier into a user key (U-Key);
Transmitting the user registration request message including the user's key and a 3-tier address of the user terminal, which is a routing identifier (RID) of the user, to the mobility server;
The mobility server recognizes that it is an initial registration request for the user through a search of a Mobility Server Binding Information Table (MSBIT) configured for mobility management of the MS and the user using the user key, Generating a user information record for the user;
Assigning a permanent three-tier address for the user to the mobility server;
The mobility server storing user mobility management information in the user record of the MSBIT;
The mobility server transmitting a user registration request response message to the terminal together with a user address (UIP); And
Storing the mapping information between the user and the terminal in the user record of the terminal and the user binding information table (TUBIT) configured for the non-encapsulation packet transmission by the terminal; And transmitting the mobility management information to the non-encapsulated packet transmission method. 16. The method of claim 15,
Wherein all user identifiers associated with the user are pre-registered in the mobility server on the network, and the mobility server manages user identifiers for each user on a user-by-user basis. 16. The method of claim 15, wherein, in the step of transmitting the user registration request message to the mobility server,
The mobility server recognizes the user through the user key information, assigns a user address in the case of initial registration, creates a mobility management record for the user in the case of initial registration of the user in connection, Further comprising updating the user mobility management record if the mobility information is pre-registered. ≪ Desc / Clms Page number 19 > The method as claimed in claim 15, wherein the initial data transmission process,
The first terminal and the second terminal are connected to each terminal configured for non-encapsulation packet transmission and a second user terminal (not shown) managing user-terminal mapping information in a user binding information table (TUBIT) (The second terminal) transmits the data packet to the terminal of the first user (the first terminal) first,
The second terminal transmitting the user location request message to the mobility server together with the user identifier;
The mobility server retrieves and updates the first user's record in a Mobility Server Binding Information Table (MSBIT) configured for mobility management of the terminal and the user using the user key, Recording the record number of the second user in the binding information record number field;
The mobility server sending a user location request response message to the second terminal;
Storing the mapping information between the first user and the second user through the TUBIT;
Establishing a session for communication with the first user by the second terminal to which the second user is connected;
The mobility server transmitting a user location notification message to the first terminal;
Storing the mapping information between the first user and the second user through the TUBIT;
Establishing a session in preparation for communication with the second user of the first terminal to which the first user is connected;
The second terminal configuring a packet having a destination address and a source address set to a first user address and a second user address, respectively;
Changing the destination address and the source address of the packet to a first routing identifier and a second routing identifier by performing an address change operation of the packet according to the binding information of the TUBIT;
Transmitting a packet sent from the second terminal to the first terminal;
Changing the destination address and the source address of the packet to a first user address and a second user address, respectively, by performing an address changing operation of a packet transmitted from the second terminal according to the binding information of the TUBIT; And
Receiving the packet by the terminal; And transmitting the mobility management information to the non-encapsulated packet transmission method. 19. The method of claim 18, wherein the second terminal transmits a user location request message with the user identifier to the mobility server,
The mobility server provides any information related to the user, such as the user's permanent 3-tier address and routing identifier, the 3-tier address of the connected terminal, for the request over the user identifier, Further comprising informing, in advance, information such as a user identifier and a routing address of a communication user through a user location notification message to the terminal. The method as claimed in claim 18, wherein the step of the user moving to a new terminal and handing over comprises:
Wherein the first user and the second user are in communication with each other and the terminal of the second user (second terminal) maintains a session for communication with the first user, In case of handover due to movement to the second terminal,
The first user requesting a user access to the second terminal using a first user identifier;
Recognizing the first user through the first user identifier and converting the first user identifier into the first user key;
The second terminal transmitting a user registration request message to the mobility server;
The mobility server determines whether it is a location update request for the first user through a search of a Mobility Server Binding Information Table (MSBIT) configured for mobility management of the MS and the user using the first user key Updating a user information record for the first user;
The mobility server transmitting a user registration request response message to the second terminal together with a first user address;
Storing mapping information between a user and a terminal in the first user record of each terminal and a user binding information table (TUBIT) configured for non-encapsulated packet transmission by the second terminal;
Storing the mapping information between the first user and the second user through the TUBIT;
Establishing a session for the first terminal with which the first user is connected to communicate with the second user via a first user address and a second user address;
The mobility server sending a user location update message to the second terminal;
Updating the mapping information between the first user and the second user through the TUBIT;
The second terminal configuring a packet having a destination address and a source address set to a first user address and a second user address, respectively;
Changing a destination address and a source address of the packet to a first routing identifier and a second routing identifier by performing an address changing operation of the packet according to the binding information of the TUBIT;
Transmitting a packet sent from the second terminal to the first terminal;
The first terminal performs an address change operation of the packet transmitted from the second terminal according to the binding information of the TUBIT and changes the destination address and the source address of the packet to the first user address and the second user address, respectively step; And
The first terminal receiving the packet; And transmitting the mobility management information to the non-encapsulated packet transmission method. The method as claimed in claim 20, wherein, in the step of the second terminal transmitting a user registration request message to the mobility server,
Wherein the mobility server further informs the user of the corresponding mobility information communicating with the user of the updated mobility information of the user through a user location update notification message in advance. Way.

Images