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

Abstract

PURPOSE: A mobility management method in a non-encapsulation packet transmission method and mobility management system are provided to transmit and receive packets by converting the address of the packets according to the requirement of a transmission and reception terminal. CONSTITUTION: An M-server updates an MSBIT(Mobility Server Binding Information Table)(701). The M-server transmits a terminal location response message to a first CN(Correspondent Node)(702). The first CN stores mapping information between a first terminal and the first CN in a TUBIT(Terminal and User Binding Information Table)(703). The M-server transmits a terminal location notification message to the first terminal(704). The first terminal stores the mapping information between the first terminal and the first CN in the TUBIT(705). The first CN transmits data packets to the first terminal(706).

Description

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

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

Conventional mobility technologies, including mobile IP (MIP), which have been conducted around terminal mobility, deliver packets using tunneling techniques to maintain session continuity regardless of the movement of the terminal during data transmission. The tunneling technique causes an increase in packet overhead and packet transmission delay due to encapsulation and decapsulation operations at the transmitting and receiving terminals, which causes service interruption. Therefore, a new attempt to improve transmission efficiency is required. In addition, since interest in user mobility and service mobility has recently increased, studies on various mobility management methods that are independent of a mobile subject are required, away from the research on terminal mobility.

MIP is a method introduced to freely transmit data even when the terminal in use is moved using IP. The MIP performs a routing function of transmitting a packet to a temporary address estimated to be where the terminal moves from the mobility management agent to transmit data regardless of the IP address. In addition, the MIP can transmit and receive data while maintaining a connection even when the terminal moves, and maintains the IP address regardless of the location and manages the terminal's location information data.

In packet forwarding, MIP uses a tunneling technique for communication between mobile stations. The packet is transmitted to the home agent (HA) of the other party, and the received HA checks the destination address of the packet and encapsulates a new address field in the original packet to the network area where the current terminal exists. To pass. 1 shows an address form of a packet transmitted through tunneling during data transmission in MIP. This tunneling technique causes packet overhead by adding an address field in addition to the original packet, and includes a problem in that handover delay increases due to delay of packet transmission.

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

The prior art 'Non-Encapsulation Mobile IP' may be effective in solving the problem of packet forwarding by the tunneling technique, but also like other technologies including the conventional MIP, mobility management limited to terminal mobility I still have the problem of how.

Accordingly, an object of the present invention for solving the above problems is to manage the mobility of the terminal and user to enable packet transmission while maintaining the session without using tunneling regardless of the change of the location of the mobile subject when providing mobility in the IP-based network environment The present invention provides a mobility management method and a mobility management system in an unencapsulated packet transmission method.

In addition, another object of the present invention is to solve the problem of mobility management research focused on the increase in packet overhead and handover delay and terminal mobility due to the packet transmission by the tunneling technique described through the problems of the prior art, Mobility management in the unencapsulated packet transmission method that can manage the mobility of the terminal and the user so that the session can be maintained without tunneling technique by changing the address of the packet as necessary and transmitting or receiving the packet when transmitting. To provide a method and a mobility management system.

In addition, another object of the present invention is to provide mobility management and packet transmission in case of user mobility along with terminal mobility, thereby providing mobility management method and mobility in an unencapsulated packet transmission method that can broaden the range of mobility types to which the technology is applied. To provide a management system.

The mobility management system in the non-encapsulated packet transmission method according to the present invention for achieving the above objects, unencapsulated packet transmission in an IP (Internet Protocol) -based network environment that provides mobility control between homogeneous or heterogeneous networks In a mobility management system including a mobility server, an access router, and a terminal for terminal and user mobility management in a scheme, the mobility server configures a mobility server binding information table (MSBIT) for each terminal for terminal and user mobility management. Alternatively, binding information is managed for each user, and the MSBIT is associated with the terminal's second layer address (L2 ID), permanent third layer address (PA), temporary third layer address (TA), and the terminal to manage the mobility of the terminal. Store and manage the mapping relationship with the terminal, and user identifier (UID), user key (U-) for the user mobility management Key), a user address (UIP), a routing identifier (RID), and a mapping relationship between a corresponding user and a counterpart user.

In addition, the mobility management system in the non-encapsulated packet transmission method according to the present invention, a terminal and a user in an unencapsulated packet transmission method in an IP (Internet Protocol) -based network environment that provides mobility control function between homogeneous networks or heterogeneous networks. In a mobility management system including a mobility server, an access router, and a terminal for mobility management, the terminal configures the terminal and a user binding information table (TUBIT) to transmit an unencapsulated packet. The session information is managed according to the mobility of the terminal and the mobility of the user. The TUBIT stores and manages binding information of two terminals communicating for the terminal mobility management, and the two users communicating for the user mobility management. And store and manage binding information.

In addition, the mobility management system in the non-encapsulated packet transmission method according to the present invention, a terminal and a user in an unencapsulated packet transmission method in an IP (Internet Protocol) -based network environment that provides mobility control between homogeneous or heterogeneous networks. A mobility management system for mobility management, comprising: a mobility server configured to manage mobility information for each terminal and user by configuring a mobility server binding information table (MSBIT) for the terminal and user mobility management; And a terminal and a user binding information table (TUBIT) for transmitting an unencapsulated packet, storing a mapping relationship with a corresponding node for terminal mobility management, and corresponding user for managing user mobility and A terminal that stores a mapping relationship with a node and changes the address of the packet according to a case of transmitting and receiving a data packet, sends and recognizes the packet, and manages session information according to the case of terminal mobility and user mobility. It is characterized by.

In addition, the mobility management method in the non-encapsulated packet transmission method according to the present invention for achieving the above objects, the encapsulation in an IP (Internet Protocol) -based network environment that provides the mobility control function between homogeneous networks or heterogeneous networks A terminal mobility management method of a mobility management system including a mobility server, an access router, and a terminal for packet and user mobility management in a packet transmission method, comprising: an initial terminal registration process in which the terminal is registered with the mobility server for the first time; An initial data transmission process of first transmitting data to the registered terminal; Moving the terminal to handover to a new access router; And a control unit.

In this case, the initial terminal registration process of the mobility management method in the non-encapsulated packet transmission method according to the present invention, the terminal transmitting a terminal registration request message to the mobility server; Generating, by the mobility server, a terminal information record for the terminal; And transmitting, by the mobility server, a terminal registration request response message to the terminal. Characterized in that it comprises a.

In addition, the mobility management method in the non-encapsulated packet transmission method according to the present invention, in the step of the terminal transmitting a terminal registration request message to the mobility server, the mobility server generates a record for the mobility management of the terminal; It further comprises.

In addition, the initial data transmission process of the terminal of the mobility management method in the unencapsulated packet transmission method according to the present invention, if the terminal is in the home network during the initial data transmission from the corresponding node to the terminal, the corresponding node Transmitting a terminal location request message to the mobility server; Retrieving and updating a terminal information record on a mobility server binding information table (MSBIT) configured by the mobility server for mobility management of the terminal and the user; Sending, by the mobility server, a terminal registration request response message to the corresponding node; Storing mapping information between the terminal and the corresponding node through a terminal and a user binding information table (TUBIT) configured by the corresponding node to transmit unencapsulated packets; Establishing, by the corresponding node, a session for communication with the terminal; Transmitting, by the mobility server, a terminal location notification message to the terminal; Storing, by the terminal, mapping information between the terminal and the corresponding node through the TUBIT; Establishing, by the terminal, a session for communication with the corresponding node; Configuring, by the corresponding node, a packet in which a destination address and a source address are set to a terminal-permanent address (PA) and a corresponding node-PA, respectively; Transmitting, by the corresponding node, a packet to the terminal; And receiving, by the terminal, the packet. Characterized in that it comprises a.

In addition, in the method for managing mobility in an unencapsulated packet transmission method according to the present invention, the correspondent node transmits a terminal location request message together with a layer 2 address of the terminal to the mobility server, wherein the mobility server permanently stores the terminal. It is characterized in that it further comprises providing any information related to the terminal, such as a three-layer address and a temporary three-layer address.

In addition, the step of the mobility server of the mobility management method in the non-encapsulated packet transmission method according to the present invention to transmit the terminal location notification message to the terminal, the mobility server foresee communication between the corresponding node and the terminal and the terminal By using the terminal location notification message to the address of the three-layer address of the corresponding node in advance.

In addition, the initial data transmission process of the terminal of the mobility management method in the unencapsulated packet transmission method according to the present invention, when the terminal is in the external network during the initial data transmission from the corresponding node to the terminal, the corresponding node Constructing a packet in which a destination address and a source address are set to a terminal-permanent address (PA) and a corresponding node-PA, respectively; The destination node and the source address of the packet are configured by the corresponding terminal-TA (Temporary Address) and the corresponding terminal according to the binding information of the terminal and the User Binding Information Table (TUBIT) configured by the corresponding node to transmit the unencapsulated packet. Changing to -TA; Transmitting, by the corresponding node, a packet to the terminal; Changing, by the terminal, a destination address and a source address of a packet transmitted from the corresponding node according to the binding information of the TUBIT to a terminal-PA and a corresponding node-PA; And receiving, by the terminal, the packet. Characterized in that it comprises a.

In addition, the process of the terminal of the mobility management method in the non-encapsulated packet transmission method according to the present invention to move and handover to a new access router, when the terminal and the corresponding node is in communication with each other and the session is connected Sending, by the terminal, a terminal location update request message to the mobility server; Retrieving and updating a terminal information record on a mobility server binding information table (MSBIT) configured by the mobility server for mobility management of the terminal and the user; Sending, by the mobility server, a terminal location update request response message to the terminal; Updating mapping information between the terminal and the corresponding node through a terminal and a user binding information table (TUBIT) configured for the terminal to transmit an unencapsulated packet; Sending, by the mobility server, a terminal location update notification message to the corresponding node; Updating, by the corresponding node, mapping information between the terminal and the corresponding node through the TUBIT; Configuring, by the corresponding node, a packet in which a destination address and a source address are set to a terminal-permanent address (PA) and a corresponding node-PA, respectively; Changing, by the corresponding node, a destination address and a source address of a packet to a terminal-TA (Temporary Address) and a corresponding node-TA according to the binding information of the TUBIT; Transmitting, by the corresponding node, a packet to the terminal; Changing, by the terminal, a destination address and a source address of a packet transmitted from the corresponding node according to the binding information of the TUBIT to a terminal-PA and a corresponding node-PA; And receiving, by the terminal, the packet. Characterized in that it comprises a.

In addition, the mobility management method in the non-encapsulated packet transmission method according to the present invention further comprises the step of the mobile server to update the mobility management record of the terminal in the step of the terminal transmitting a terminal location update request message to the mobility server. It is characterized by including.

In addition, the mobility management method in the non-encapsulated packet transmission method according to the present invention in the step of transmitting the terminal location update notification message to the corresponding node that the mobility server is communicating with the terminal according to the location update request transmitted from the terminal The method may further include informing the mobility information of the updated terminal in advance.

In addition, the mobility management method in the unencapsulated packet transmission method according to the present invention, a terminal and a user in an unencapsulated packet transmission method in an IP (Internet Protocol) -based network environment that provides mobility control function between homogeneous networks or heterogeneous networks. A user mobility management method of a mobility management system including a mobility server, an access router, and a terminal for mobility management, the method comprising: an initial user registration process in which a user of the terminal is first registered with the mobility server; An initial data transmission process of first transmitting data to the registered user; And handing over to the user by moving to a new terminal. And a control unit.

The method of claim 14, wherein the initial user registration process comprises: a user accessing the terminal using a user identifier (UID). Requesting; The terminal recognizing the user through the user identifier and converting the user identifier into a user key (U-Key); Sending, by the terminal, a user registration request message including the user key and a three-layer address of the terminal, which is a routing identifier (RID) of the user, to the mobility server; The mobility server recognizes an initial registration request for the user through a search of a mobility server binding information table (MSBIT) configured for mobility management of the terminal and the user by using the user key. Creating a user information record for the user; The mobile server assigning a permanent three layer address for the user; Storing, by the mobility server, user mobility management information in the user record of the MSBIT; Transmitting, by the mobility server, a user registration request response message together with a user address (UIP) to the terminal; And storing mapping information between the user and the terminal in the user record of the terminal and a user binding information table (TUBIT) configured by the terminal for unencapsulated packet transmission. Characterized in that it comprises a.

Further, all user identifiers associated with the user of the mobility management method in the unencapsulated 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 for them on a user-by-user basis. It is characterized by doing.

In addition, in the method for managing mobility in an unencapsulated packet transmission method according to the present invention, in the step of the terminal transmitting a user registration request message to the mobility server, the mobility server recognizes a user through the user key information, In case of registration, assign a user address, create a mobility management record for the user for the initial registration of the connecting user, and update the user mobility management record if the mobility information of the connected user is already registered. It further comprises.

In addition, the initial data transmission process of the first data is transmitted to the registered user of the mobility management method in the non-encapsulated packet transmission method according to the present invention, the first terminal and the second terminal is configured for the unencapsulated packet transmission The terminal (second terminal) of the second user who manages mapping information between the user and the terminal in each terminal and user binding information table (TUBIT), respectively, is the terminal of the first user. Transmitting a user location request message to the mobility server by the second terminal when the data packet is first transmitted to the mobile station; Search and update the record of the first user in a mobility server binding information table (MSBIT) configured by the mobility server for mobility management of the terminal and the user using the user key; Writing the record number of the second user in a binding information record number field; Sending, by the mobility server, a user location request response message to the second terminal; Storing, by the second terminal, mapping information between the first user and the second user through the TUBIT; Establishing, by the second terminal to which the second user is connecting, a session for communication with the first user; Sending, by the mobility server, a user location notification message to the first terminal; Storing, by the first terminal, mapping information between the first user and the second user through TUBIT; Establishing a session in preparation for communication with the second user of the first terminal to which the first user is connecting; Configuring, by the second terminal, a packet in which a destination address and a source address are set to a first user address and a second user address, respectively; Changing, by the second terminal, an address change operation of the packet according to the binding information of the TUBIT to change the destination address and the source address of the packet into a first routing identifier and a second routing identifier; Forwarding the packet sent from the second terminal to the first terminal; Changing, by the first terminal, an address change operation of a packet transmitted from the second terminal according to the binding information of the TUBIT to change a destination address and a source address of the packet into a first user address and a second user address, respectively; And receiving, by the terminal, the packet. Characterized in that it comprises a.

In the non-encapsulated packet transmission method according to the present invention, the second terminal transmits a user location request message together with the user identifier to the mobility server, wherein the mobility server responds to the request through the user identifier. Provide arbitrary information related to the user, such as the permanent three-layer address of the user and the three-layer address of the terminal being accessed as a routing identifier, foresee communication between the two users, and communicates through the user location notification message to the first terminal. It further comprises informing the information such as the user identifier and the routing address of the.

In addition, the process of the user of the mobility management method in the method of the non-encapsulated packet transmission according to the present invention to move to a new terminal and handover, the first user and the second user is in communication with each other, the terminal of the second user ( The second terminal) is the first user in the case of a handover as the first user moves to the second terminal in another access router while maintaining a session for communication with the first user. Requesting a user connection to the second terminal using the first user identifier; The second terminal recognizing the first user through the first user identifier and converting the first user identifier to the first user key; Sending, by the second terminal, a user registration request message to the mobility server; Recognize that the mobility server is a location update request for the first user through a Mobility Server Binding Information Table (MSBIT) search configured for the mobility management of the terminal and the user by using the first user key. Updating a user information record for the first user; Sending, by the mobility server, a user registration request response message to the second terminal with a first user address; Storing mapping information between a user and the terminal in the first user record of each terminal and a user binding information table (TUBIT) configured by the second terminal for transmitting an unencapsulated packet; Storing, by the second terminal, mapping information between the first user and the second user through the TUBIT; Establishing, by the first terminal to which the first user is connecting, a session for communication with the second user via a first user address and a second user address; Sending, by the mobility server, a user location update message to the second terminal; Updating, by the second terminal, mapping information between the first user and the second user through the TUBIT; Configuring, by the second terminal, a packet in which a destination address and a source address are set to a first user address and a second user address, respectively; Changing, by the second terminal, an address change operation of the packet according to the binding information of the TUBIT to change the destination address and the source address of the packet into a first routing identifier and a second routing identifier; Forwarding the packet sent from the second terminal to the first terminal; The first terminal performs an address change operation of a packet transmitted from the second terminal according to the binding information of the TUBIT, and changes a destination address and a source address of the packet into a first user address and a second user address, respectively; step; And the first terminal receiving the packet; Characterized in that it comprises a.

In addition, in the method for managing mobility in an unencapsulated packet transmission method according to the present invention, in the step of the second terminal transmitting a user registration request message to the mobility server, the mobility server of the corresponding user who is communicating with the user The method further includes informing the user of the updated mobility information of the user in advance through the user location update notification message.

As described above, the present invention provides a tunneling scheme by transmitting or receiving a packet by changing the address of a packet as necessary in a terminal for providing unencapsulated packet transmission in an IP-based network and transmitting / receiving terminal during data transmission for user mobility management. The effect is that the session can be maintained without

In addition, the present invention has the advantage of extending the range of mobility types to which the technology is applied by proposing a mobility management and packet transmission method in the case of user mobility with the terminal mobility.

In addition, the present invention, by changing the access terminal using the UID and the user address in the case of user mobility and maintains the session of the user to use the service, the transmission packet size is reduced compared to the prior art using the tunneling technique for data transmission Due to this, packet overhead resolution and handover delay can be reduced.

In addition, the present invention has the advantage of configuring the session maintenance scheme through mobility management and data transmission in the case of user mobility as well as the terminal.

1 is a view showing the format of a transmission packet when transmitting data using MIP according to the prior art,
2 is a diagram illustrating a format of a delivery packet in data transmission using the prior art;
3 is a basic network configuration to which the mobility management method in the unencapsulated packet transmission scheme proposed in the present invention is applied;
4 is a diagram illustrating a network configuration showing a position change according to movement of a terminal in the case of terminal mobility proposed by the present invention;
5 is a diagram illustrating a network configuration showing movement according to a change of a user's access terminal in the case of user mobility proposed by the present invention;
6 is a procedure showing an initial terminal registration process in case of terminal mobility according to the present invention;
7A is a procedure diagram illustrating an initial packet transmission process in which data is first transmitted to a terminal when the terminal is located in a home network in the case of terminal mobility proposed in the present invention.
7b is a procedure illustrating an initial packet transmission process in which data is first transmitted to a terminal when the terminal is located in an external network in the case of terminal mobility proposed in the present invention.
8 is a procedure for handover procedure in which a terminal moves to a new access network in the case of terminal mobility proposed in the present invention;
9 is a procedure showing an initial user registration process in the case of user mobility proposed in the present invention,
10 is a procedure 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 by the present invention;
11 is a procedure for handover procedure in which a user moves to a new terminal located in another access network in case of user mobility proposed by the present invention;
12A and 12B are diagrams illustrating a packet address configuration by a packet address change operation in a terminal in case of terminal mobility proposed by the present invention;
13A and 13B are packet address configuration diagrams by a packet address change operation in a terminal in case of user mobility proposed by the present invention;
14 is a diagram illustrating a terminal mobility management information table managed by a mobility server in case of terminal mobility proposed by the present invention;
15 is a configuration diagram of a user mobility management information table managed by a mobility server in case of user mobility proposed by the present invention;
16 is a block diagram of a terminal communication information binding table managed by a terminal in case of terminal mobility proposed by the present invention;
17 is a diagram illustrating a configuration of a terminal and a user communication information binding table managed by a terminal in case of user mobility proposed by the present invention.

In order to solve the problem of mobility management research focused on packet mobility and handover delay increase and terminal mobility due to packet transmission by the tunneling technique described above, the present invention relates to the above issues. To provide mobility in IP-based networks, we propose a terminal and user mobility management scheme that transmits packets while maintaining a session without tunneling regardless of the change of location of the mobile subject. That is, the present invention allows a session to be maintained without a tunneling technique by changing the address of a packet as necessary in a transmitting / receiving terminal during data transmission to send or receive the packet.

In addition, the present invention intends to broaden the range of mobility types to which the technology is applied by proposing a mobility management and packet transmission method in case of user mobility along with terminal mobility. To this end, the mobility server of the network uses terminal-specific information as terminal-specific information in the case of terminal mobility, as a layer 2 address (hereinafter referred to as L2 ID), a permanent layer 3 address (PA), and a temporary layer 3 (Temporary Address, TA). Store and manage the information of the terminal has been made. User mobility stores and manages user identifier (UID), user key (User-Key, U-Key), user address (User IP, UIP), and routing identifier (RID) as user-specific information. do.

Accordingly, the proposed scheme provides an initial registration process, an initial data packet transmission process, and a handover process according to whether a mobile entity is a terminal or a user. And to implement the proposed scheme, it provides the function of operation in network and terminal in each mobility management process. At this time, network entities or communication terminals configure a binding table to manage related information for mobility support and unencapsulated 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.

3 is an exemplary configuration of a network environment to which a mobility management method in an unencapsulated packet transmission method according to the present invention is applied, and FIGS. 4 and 5 illustrate a case of terminal mobility and a case of user mobility in the network environment of FIG. 3. 4 is a diagram illustrating a case where a terminal is handed over to a new access network, and FIG. 5 is a case where a user is handed over to a new terminal in another access network.

3 to 5 is a network structure in which IP mobility control function is provided between homogeneous networks or heterogeneous networks, and the mobility management system according to the present invention provides a mobility server for managing terminal and user mobility. 400, Mobility Server, M-Server) and the access router (300, 310, 320, Access Router, AR) and the terminal 200, 210 and the corresponding node 220. The terminals 200 and 210 include both fixed and mobile nodes.

The M-Server 400 manages binding information for each terminal or user for terminal and user mobility management. To this end, the M-Server 400 internally includes a mobility server binding information table (MSBIT). Detailed configurations of the mobility server binding information table are shown in FIGS. 14 and 15.

14 and 15 are diagrams illustrating a structure of a terminal mobility management information table managed by a mobility server in case of terminal mobility and user mobility proposed in the present invention, respectively.

First, as shown in FIG. 14, for supporting mobility of a terminal, MSBIT is a temporary two-layer address (TA) according to a terminal's second-layer address (L2 ID), a permanent three-layer address (PA), and a terminal's location. Stores and manages the mapping relationship with the corresponding node communicating with the terminal. The layer 2 addresses of the terminals may be MAC addresses, for example, and the layer 3 addresses PA and TA may be IP addresses, 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.

On the other hand, as shown in Figure 15, MSBIT for the user mobility support MSID, user key (U-Key), user address (UIP), routing identifier (RID) and mapping relationship with the user in communication Store and manage it. UIDs can accept a wide range of user identification information, including e-mail addresses (eg, aaa@realm.com), network access identifiers (NAIs), telephone numbers, and radio frequency identification (RFID) values. It is not specific. The U-Key is a user key recognizable in the network and can be expressed by converting the UID by various methods such as a hashing function.

The M-Server 400 identifies a user by using a U-Key when determining a user registration request and determines UIP allocation. The UIP may be an IP address as a permanent three-layer address (PA) for a particular user. The M-Server 400 can function as a Dynamic Host Configuration Protocol (DHCP) server or a Domain Name Server (DNS), or can be assigned to UIP in conjunction with a DHCP server or DNS. The address can be assigned in advance. The RID is information indicating the actual routing location of the user and may be considered as the third layer address of the terminal to which the user is currently accessing. The mapping relationship with the communicating user may be expressed by inputting a record number in the MSBIT of the user corresponding to the communicating user binding information field.

The ARs 300, 310, and 320 are network access routers connected to the terminals 200 and 210 and the corresponding nodes 220. According to an embodiment of the unencapsulated data packet transmission according to the present invention, the ARs 300, 310, and 320 do not need to maintain and manage binding information tables for terminals and users in order to support terminal and user mobility.

The terminals 200 and 210 and the corresponding node 220 basically have a function of accommodating a plurality of three-layer addresses, such as three-layer addresses (PA, TA) of the terminal or UIP of the access user. In addition, the terminals 200 and 210 and the corresponding node 220 manage a terminal and a user binding information table (TUBIT) to support the terminal and user mobility. Detailed configurations of the terminal and the user binding information table are illustrated in FIGS. 16 and 17.

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

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

Subsequently, the terminal T # 1 200 transmits a terminal registration request message to the M-Server 400 (500). In this case, the L2 ID and the PA of the terminal T # 1 200 are transmitted together. The M-Server 400 searches for the MSBIT using the L2 ID of the terminal T # 1 200 and recognizes that it is an initial registration request for the terminal T # 1 200, and thus records the information for the terminal T # 1 200. Generate 501. The M-Server 400 stores [L2 ID: PA] information as the 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 terminal for the first time when the terminal is located in a home network and when the terminal is located in an external network in case of terminal mobility according to the present invention. The procedure diagram shown. 7A and 7B, an initial packet transmission procedure will be described when the corresponding node CN # 1 220 first transmits data to the terminal T # 1 200. FIG. 7A illustrates an initial packet transmission process when the terminal is in a home network, and FIG. 7B is divided into a case in an external network. In the present invention, the corresponding node CN # 1 220 is considered to be located in the home network. When the corresponding node CN # 1 220 is located in the external network, the procedure is the same and there is only a difference in the mobility information.

Referring to FIGS. 7A and 7B, the corresponding node CN # 1 220 moves to the M-Server 400 to find location information of the terminal T # 1 200 for data transmission to the terminal T # 1 200. The terminal location request message is transmitted (600, 700). At this time, the L2 ID of the terminal T # 1 is transmitted together. Accordingly, the M-Server 400 searches for and updates MSBIT by using the L2 ID of the terminal T # 1 200 (601, 701), thereby relating to the terminal such as the three-layer address of the terminal T # 1 200. You can respond to any information.

When the terminal T # 1 200 is in the home network as shown in FIG. 7A, the M-Server 400 extracts the PA of the terminal T # 1 as a result of the terminal location request. The M-Server 400 also predicts the communication between the terminal T # 1 200 and the corresponding node CN # 1 220 through the terminal location request message and records each other's record numbers in the communication terminal binding information field on the record of each terminal. Update MSBIT by writing 601.

The M-Server 400 transmits a terminal location response message to the corresponding node CN # 1 220. At this time, the PA of the terminal T # 1 200 is transmitted (602). Corresponding node CN # 1 220 receiving this information maps information between UE T # 1 200 and corresponding node CN # 1 220 in TUBIT ([T # 1-PA: @ CN # 1-PA:]). Store (603). In addition, a session is established through a PA of the terminal T # 1 200 and a PA of the corresponding node CN # 1 220 for communication with the terminal T # 1 200.

In addition, the M-Server 400 responds to the terminal location request to the corresponding node CN # 1 220 and simultaneously transmits a terminal location notification message to the terminal T # 1 200. At this time, the PA of the corresponding node CN # 1 220 is transmitted together (604). This is to inform the terminal T # 1 (200) of information for communication with the corresponding node CN # 1 (220) so that the terminal can prepare for communication with the corresponding terminal before the packet arrives. Upon receipt of this, the terminal T # 1 200 sends mapping information ([T # 1-PA: @ CN # 1-PA:]) of the terminal T # 1 200 and the corresponding node CN # 1 220 to TUBIT. Save (605). Then, a session is established through the PA of the terminal T # 1 200 and the PA of the corresponding node CN # 1 220 for communication with the corresponding node CN # 1 220.

Subsequently, the corresponding node CN # 1 220 configures a destination address and a source address of the packet header as T # 1-PA and CN # 1-PA, respectively, for data transmission to the terminal T # 1 200. Send to T # 1 100 (606). Since the terminal T # 1 200 is located in the home network, the corresponding packet is directly transmitted to the terminal T # 1 200 without any additional processing. The packet address changing format according to the address changing operation in the terminal during data packet delivery is shown in FIG. 12A.

Next, when the terminal T # 1 (200) in the external network as shown in Figure 7b, the M-Server 400 extracts the binding information of the PA and TA of the terminal T # 1 as a result of the terminal location request. In addition, 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).

Subsequently, the M-Server 400 transmits a terminal location response message to the corresponding node CN # 1 220 (702). At this time, the PA and the TA of the UE T # 1 200 are transmitted together. Corresponding node CN # 1 220 receiving this information maps information between UE T # 1 200 and corresponding node CN # 1 220 in TUBIT ([T # 1-PA: T # 1-TA @ CN # 1 -PA:]) is stored (703). In addition, a session is established through a PA of the terminal T # 1 200 and a PA of the corresponding node CN # 1 220 for communication with the terminal T # 1 200.

In addition, the M-Server 400 responds to the terminal location request to the corresponding node CN # 1 220 and simultaneously transmits the terminal location notification message to the terminal T # 1 200 (704). At this time, the PA of the corresponding node CN # 1 220 is transmitted together. Upon receipt of this, the terminal T # 1 200 receives mapping information of the terminal T # 1 200 and the corresponding node CN # 1 220 in TUBIT ([T # 1-PA: T # 1-TA @ CN # 1-). PA:]) is stored (705). Then, a session is established through the PA of the terminal T # 1 200 and the PA of the corresponding node CN # 1 220 for communication with the corresponding node CN # 1 220.

The corresponding node CN # 1 220 configures a destination address and a source address of the packet header as T # 1-PA and CN # 1-PA, respectively, for data transmission to the terminal T # 1 200. FIG. At this time, the corresponding node CN # 1 220 before the data is sent internally performs an address translation operation according to the binding information of the TUBIT. This is a function proposed by the present invention for sending data packets to their destinations 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 the packet is transmitted from the corresponding node CN # 1 220, the terminal T # 1 200 performs the address change operation again with reference to the previously configured binding information of TUBIT and receives the packet. 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.

12A and 12B illustrate a packet address change format according to an address change operation in a terminal when the corresponding node CN # 1 220 transmits an initial data packet to T # 1 200 located in an external network. 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. Corresponding node CN # 1 (220) constructs a packet whose destination address and source address are T # 1-PA and CN # 1-PA in the packet header, and the destination address and source address of the packet header by the address change operation before sending. To T # 1-TA and CN # 1-PA to transmit to T # 1 (200). 12B shows the address format of the packet received from the CN # 1 220 and the address format finally received by the address change operation. When the packet arrives in the form of the destination address and the source address of the packet header T # 1-TA and CN # 1-PA, the T # 1 200 sets the destination address and the source address of the packet header by the address change operation. Change to # 1-PA and CN # 1-PA to receive the packet.

8 is a flowchart illustrating a process of handing over a terminal to a new access network in the case of terminal mobility according to the present invention. Referring to FIG. 8, a handover procedure will be described in detail 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. The terminal T # 1 200 and the corresponding node CN # 1 210 are in a communication state and are 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 the TA of the terminal T # 1 200 are transmitted together. The M-Server 400 searches for the MSBIT using the L2 ID of the terminal T # 1 200, recognizes that the location update request for the terminal T # 1 200, and records information of the terminal T # 1 200. ([L2 ID: PA: CoA]) is updated (801). Subsequently, the M-Server 400 transmits a terminal location update response message to the terminal T # 1 200 (802). Upon receipt of this, the terminal T # 1 200 receives mapping information between the terminal T # 1 200 on the TUBIT and the corresponding node CN # 1 220 ([T # 1-PA: T # 1-TA @ CN # 1- PA:]) is updated (803).

In addition, the M-Server 400 responds to the terminal location update request to the terminal T # 1 200 and simultaneously transmits the terminal location update notification message to the corresponding node CN # 1 220 (804). At this time, the TA of the terminal T # 1 200 is transmitted together. The corresponding node CN # 1 220 receiving this information is mapping information between the terminal T # 1 200 on the TUBIT and the corresponding node CN # 1 220 ([T # 1-PA: T # 1-TA @ CN # 1 -PA:]) is updated (805).

At this time, since the terminal T # 1 200 and the corresponding node CN # 1 220 are in communication, the corresponding node CN # 1 220 includes a PA of the terminal T # 1 200 and a corresponding node CN # 1 220. Session through PA is being established and maintained. Accordingly, the corresponding node CN # 1 220 configures a destination address and a source address of the packet header as T # 1-PA and CN # 1-PA, respectively, for data transmission to the terminal T # 1 (200). Before sending, the corresponding node CN # 1 220 performs an address change operation internally according to the binding information of 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 the packet is transmitted from the corresponding node CN # 1 220, the terminal T # 1 200 performs the address change operation again with reference to the previously configured binding information of TUBIT 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 case of user mobility according to the present invention. Referring to FIG. 9, when the User # A 100 accesses a network through the terminal T # 1 200, an initial user registration procedure will be described in detail. All UIDs related to User # A 100 are registered in advance in the M-Server 400 on the network, and the M-Server 400 manages UIDs for them by user.

First, User # A 100 attempts a user connection to terminal T # 1 200 using UID # A (900). The terminal T # 1 200 recognizes the User # A 100 through the UID # A and converts the UID # A in order to register the access of the User # A100 to the network. Generate U-Key # A (901).

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

The M-Server 400 searches for MSBIT using U-Key # A and recognizes that it is an initial registration request for User # A 100, and generates a user information record for User # A 100 (903). . The preconfigured user address information is allocated to the UIP of User # A 100 (904). Thereafter, the M-Server 400 stores [UID # A: U-Key # A: UIP # A: RID # A] information in MSBIT as information of User # A (905). At this time, RID # A is a three-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). Upon receiving this, the terminal T # 1 200 stores mapping information between the user and the terminal ([UIP # A: RID # A (T # 1 IP)]) in the User # A (100) record of the TUBIT (907). .

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

First, the terminal CN # 1 220 transmits a user location request message to the M-Server 400 to find 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 may respond to any information related to the user, such as UIP # A or RID # A (three-layer address of the terminal T # 1) using the UID # A.

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

Subsequently, 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 which receives this stores the mapping information ([UIP # A: RID # A @ UIP # B: RID # B]) of User # A 100 and User # B 110 in TUBIT. (1003). CN # 1 220, which is an access terminal of User # B 110, establishes a session through UIP # A and UIP # B for communication with User # A 100 (1004).

In addition, the M-Server 400 responds to the user location request to the terminal CN # 1 220 and simultaneously transmits a user location notification message to the terminal T # 1 200 (1005). At this time, UIP # A, UIP # B, and RID # B (CN # 1 IP) are transmitted together. This informs T # 1 (200), the access terminal of User # A (100), of information for communication with User # B (110) to prepare for communication with the corresponding user before the packet actually arrives. To do this.

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

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. Before sending, the terminal CN # 1 220 internally performs an address change operation according to the binding information of the TUBIT (1008). This is to send the data packet to the destination without encapsulation. Through the address change operation, the destination address and the source address of the packet are changed to RID # A (T # 1 IP) and RID # B (CN # 1 IP), respectively, and the terminal T # 1 (200) of User # A (100). (1009).

When the packet is transmitted from the terminal CN # 1 220, the terminal T # 1 200 performs an address change operation again with reference to the previously configured binding information of TUBIT and receives the 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. 13A and 13B illustrate a packet address change format according to an address change operation in a terminal during data packet delivery.

In the case of the user mobility, the packet address change format according to the address change operation in the terminal during data packet transmission is illustrated 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 # B110 configures a packet having UIP # A and UIP # B as the destination address and the source address of the packet header, and the destination address of the packet header by the address change operation before sending. The source address is changed to T # 1 IP and CN # 1 IP and transmitted to terminal T # 1 200 of User # A 100. FIG. 13B shows the address format of the terminal T # 1 200 of User # A 100 and the address format finally received by the address change operation. When the packet arrives in the form of the destination address and the source address of the T # 1 IP and the CN # 1 IP, the terminal T # 1 200 of the User # A 100 receives the destination of the packet header by the address change operation. Change the address and source address to UIP # A and UIP # B to receive the packet.

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

User # A (100) attempts a user connection to 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 user # A 100's connection to the network. Generate Key # A (1101).

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

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

In addition, the M-Server 400 responds to the user registration request to the T # 2 (210) and simultaneously transmits a user location update notification message to the terminal CN # 1 (220) (1108). At this time, UIP # B, UIP # A, and RID # A (T # 2 IP) are transmitted together. This informs the terminal CN # 1 220 of the changed information of the User # A 100, so that the terminal CN # 1 220 repeatedly sends the M-Server 400 to the user User # A 100 for data transmission. This is to avoid having to request the location again. CN # 1 220 receiving this updates the mapping information ([UIP # A: RID # A @ UIP # B: RID # B]) of User # A 100 and User # B 110 to TUBIT. (1109). Since User # A 100 and User # B 110 are communicating, sessions through UIP # A and UIP # B are established and maintained in CN # 2 210.

Subsequently, the terminal CN # 1 220 configures a destination address and a source address of the packet header as UIP # A and UIP # B, respectively, for data transmission to the User # A 100. Before sending data, the terminal CN # 1 220 internally performs an address change operation according to the binding information of the TUBIT (1110). Through the address change operation, the destination address and the source address of the packet are changed to RID # A (T # 2 IP) and RID # B (CN # 1 IP), respectively, and T # 2 (210) of User # A (100). Is sent to 1111. When the packet is transmitted from the terminal CN # 1 220, the T # 2 210 performs the address change operation again by referring to the binding information of TUBIT, which is configured in advance, 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, a mobility management method and a mobility management system in an unencapsulated packet transmission method according to the present invention, a terminal for providing unencapsulated packet transmission in an IP-based network and a transmission and reception terminal during data transmission for user mobility management The session can be maintained without a tunneling technique by changing the address of the packet as needed in 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 can broaden the range of mobility types to which the technology is applied by proposing a mobility management and packet transmission method in case of user mobility along with terminal mobility. have.

In addition, the mobility management method and mobility management system in the non-encapsulated packet transmission method according to the present invention, in the case of user mobility, the mobility to maintain the session of the user to change the access terminal using the UID and the user address to use the service You can configure session persistence techniques through management and data transfer.

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 only implemented through the apparatus and / or method, but also through a program for realizing a function corresponding to the configuration of the present invention, a recording medium on which the program is recorded, and the like. Implementation can be easily implemented by those skilled in the art from the description of the above-described embodiments.

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)

A mobility management system including a mobility server, an access router, and a terminal for managing terminal and user mobility in an unencapsulated packet transmission method in an IP (Internet Protocol) based network environment that provides mobility control between homogeneous or heterogeneous networks. In
The mobility server configures a mobility server binding information table (MSBIT) for terminal and user mobility management, and manages binding information for each terminal or user.
The MSBIT stores and manages the second layer address (L2 ID), the permanent three layer address (PA), the temporary three layer address (TA), and the mapping relationship between the terminal and the counterpart terminal for mobility management of the terminal. And storing and managing a user identifier (UID), a user key (U-Key), a user address (UIP), a routing identifier (RID), and a mapping relationship between the corresponding user and the corresponding user for managing the user mobility. A mobility management system in an unencapsulated packet transmission scheme. A mobility management system including a mobility server, an access router, and a terminal for managing terminal and user mobility in an unencapsulated packet transmission method in an IP (Internet Protocol) based network environment that provides mobility control between homogeneous or heterogeneous networks. In
The terminal configures the terminal and user binding information table (TUBIT) for uncapsulated packet transmission to manage session information according to the mobility of the terminal and the mobility of the user user,
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 terminal and user mobility management in an unencapsulated packet transmission method in an IP (Internet Protocol) based network environment that provides mobility control between homogeneous networks or heterogeneous networks,
A mobility server configured to manage a binding information for each terminal and a user by configuring a mobility server binding information table (MSBIT) for managing the terminal and user mobility; And
Configure terminal and user binding information table (TUBIT) for unencapsulated packet transmission, store mapping relationship with corresponding node for terminal mobility management, and corresponding user and node for user mobility management And a terminal for storing the mapping relationship with the terminal and managing the session information according to the case of the terminal mobility and the user mobility by changing the address of the packet according to the case of transmitting and receiving the data packet. A mobility management system in a non-encapsulated packet transmission method. A mobility management system including a mobility server, an access router, and a terminal for terminal and user mobility management in an unencapsulated packet transmission method in an IP (Internet Protocol) based network environment that provides mobility control between homogeneous or heterogeneous networks. In the terminal mobility management method,
An initial terminal registration process in which the terminal is registered with the mobility server for the first time;
An initial data transmission process of first transmitting data to the registered terminal; And
Moving the terminal to handover to a new access router; The mobility management method in an unencapsulated packet transmission method comprising a. The method of claim 4, wherein the initial terminal registration process,
Sending, by the terminal, a terminal registration request message to the mobility server;
Generating, by the mobility server, a terminal information record for the terminal; And
Transmitting, by the mobility server, a terminal registration request response message to the terminal; Mobility management method in an unencapsulated packet transmission method comprising a. The method of claim 5, wherein the terminal transmits a terminal registration request message to the mobility server.
The mobility server further comprises generating a record for the mobility management of the terminal mobility management method in a non-encapsulated packet transmission method. The method of claim 4, wherein the initial data transmission process of the terminal,
When the terminal is in the home network during initial data transmission from the corresponding node to the terminal,
Sending, by the corresponding node, a terminal location request message to the mobility server;
Retrieving and updating a terminal information record on a Mobility Server Binding Information Table (MSBIT) configured by the mobility server for mobility management of the terminal and the user;
Sending, by the mobility server, a terminal registration request response message to the corresponding node;
Storing mapping information between the terminal and the corresponding node through a terminal and a user binding information table (TUBIT) configured by the corresponding node to transmit unencapsulated packets;
Establishing, by the corresponding node, a session for communication with the terminal;
Transmitting, by the mobility server, a terminal location notification message to the terminal;
Storing, by the terminal, mapping information between the terminal and the corresponding node through the TUBIT;
Establishing, by the terminal, a session for communication with the corresponding node;
Configuring, by the corresponding node, a packet in which a destination address and a source address are respectively set to a terminal-permanent address (PA) and a corresponding node-PA;
Transmitting, by the corresponding node, a packet to the terminal; And
Receiving, by the terminal, a corresponding packet; Mobility management method in an unencapsulated packet transmission method comprising a. 8. The method of claim 7, wherein the corresponding node transmits a terminal location request message along with a layer 2 address of the terminal to the mobility server.
The mobility server further comprises providing arbitrary information related to the terminal, such as a permanent three-layer address and a temporary three-layer address of the terminal. The method of claim 7, wherein the mobility server transmits a terminal location notification message to the terminal.
The mobility server predicts communication between the corresponding node and the terminal and informs the terminal of the layer 3 address of the corresponding node through a terminal location notification message in advance. The method of claim 4, wherein the initial data transmission process of the terminal,
If the terminal is in an external network during initial data transmission from the corresponding node to the terminal,
Configuring, by the corresponding node, a packet in which a destination address and a source address are set to a terminal-permanent address (PA) and a corresponding node-PA, respectively;
The destination node and the source address of the packet are configured by the corresponding terminal-TA (Temporary Address) and the corresponding terminal according to the binding information of the terminal and the User Binding Information Table (TUBIT) configured by the corresponding node to transmit the unencapsulated packet. Changing to -TA;
Transmitting, by the corresponding node, a packet to the terminal;
Changing, by the terminal, a destination address and a source address of a packet transmitted from the corresponding node according to the binding information of the TUBIT to a terminal-PA and a corresponding node-PA; And
Receiving, by the terminal, the packet; Mobility management method in an unencapsulated packet transmission method comprising a. The process of claim 4, wherein the mobile station moves to handover to a new access router.
When the terminal and the corresponding node are in communication with each other and the session is connected,
Sending, by the terminal, a terminal location update request message to the mobility server;
Retrieving and updating a terminal information record on a mobility server binding information table (MSBIT) configured by the mobility server for mobility management of the terminal and the user;
Sending, by the mobility server, a terminal location update request response message to the terminal;
Updating mapping information between the terminal and the corresponding node through a terminal and a user binding information table (TUBIT) configured for the terminal to transmit an unencapsulated packet;
Sending, by the mobility server, a terminal location update notification message to the corresponding node;
Updating, by the corresponding node, mapping information between the terminal and the corresponding node through the TUBIT;
Configuring, by the corresponding node, a packet in which a destination address and a source address are set to a terminal-permanent address (PA) and a corresponding node-PA, respectively;
Changing, by the corresponding node, a destination address and a source address of a packet to a terminal-TA (Temporary Address) and a corresponding node-TA according to the binding information of the TUBIT;
Transmitting, by the corresponding node, a packet to the terminal;
Changing, by the terminal, a destination address and a source address of a packet transmitted from the corresponding node according to the binding information of the TUBIT to a terminal-PA and a corresponding node-PA; And
Receiving, by the terminal, a corresponding packet; Mobility management method in an unencapsulated packet transmission method comprising a. The method of claim 11, wherein the terminal transmits a terminal location update request message to the mobility server.
And the mobility server further updates the mobility management record of the terminal. The method of claim 11, wherein the mobility server transmits a terminal location update notification message to the corresponding node in communication with the terminal according to the location update request transmitted from the terminal.
The mobility server further comprises informing of the mobility information of the updated terminal in advance in mobility management method in a non-encapsulated packet transmission method. A mobility management system including a mobility server, an access router, and a terminal for terminal and user mobility management in an unencapsulated packet transmission method in an IP (Internet Protocol) based network environment that provides mobility control between homogeneous or heterogeneous networks. In the user mobility management method,
An initial user registration process in which a user of the terminal is first registered with the mobility server;
An initial data transmission process of first transmitting data to the registered user; And
The user moving to a new terminal and handing over; The mobility management method in an unencapsulated packet transmission method comprising a. The method of claim 14, wherein the initial user registration process,
Requesting, by the user, a user connection to the terminal using a user identifier (UID);
The terminal recognizing the user through the user identifier and converting the user identifier into a user key (U-Key);
Sending, by the terminal, a user registration request message including the user key and a three-layer address of the terminal, which is a routing identifier (RID) of the user, to the mobility server;
The mobility server recognizes an initial registration request for the user through a search of a mobility server binding information table (MSBIT) configured for mobility management of the terminal and the user by using the user key. Creating a user information record for the user;
The mobile server assigning a permanent three layer address for the user;
Storing, by the mobility server, user mobility management information in the user record of the MSBIT;
Transmitting, by the mobility server, a user registration request response message together with a user address (UIP) to the terminal; And
Storing mapping information between the user and the terminal in the user record of the terminal and a user binding information table (TUBIT) configured by the terminal for unencapsulated packet transmission; Mobility management method in an unencapsulated packet transmission method comprising a. 16. The method of claim 15,
All user identifiers associated with the user are registered in advance in the mobility server on the network, and the mobility server manages user identifiers for them for each user. The method of claim 15, wherein the terminal transmits a 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 case of initial registration of the connecting user, and And updating the user mobility management record when the mobility information is pre-registered. The initial data transmission process of claim 14, wherein the initial data transmission to the registered user comprises:
The second terminal manages mapping information between the user and the terminal in each terminal and user binding information table (TUBIT) configured for the unencapsulated packet transmission. When the terminal (second terminal) of the first transmission of the data packet to the terminal (first terminal) of the first user,
Sending, by a second terminal, a user location request message to the mobility server together with the user identifier;
Search and update the record of the first user in a mobility server binding information table (MSBIT) configured by the mobility server for mobility management of the terminal and the user using the user key; Writing the record number of the second user in a binding information record number field;
Sending, by the mobility server, a user location request response message to the second terminal;
Storing, by the second terminal, mapping information between the first user and the second user through the TUBIT;
Establishing, by the second terminal to which the second user is connecting, a session for communication with the first user;
Sending, by the mobility server, a user location notification message to the first terminal;
Storing, by the first terminal, mapping information between the first user and the second user through TUBIT;
Establishing a session in preparation for communication with the second user of the first terminal to which the first user is connecting;
Configuring, by the second terminal, a packet in which a destination address and a source address are set to a first user address and a second user address, respectively;
Changing, by the second terminal, an address change operation of the packet according to the binding information of the TUBIT to change the destination address and the source address of the packet into a first routing identifier and a second routing identifier;
Forwarding the packet sent from the second terminal to the first terminal;
Changing, by the first terminal, an address change operation of a packet transmitted from the second terminal according to the binding information of the TUBIT to change a destination address and a source address of the packet into a first user address and a second user address, respectively; And
Receiving, by the terminal, a corresponding packet; Mobility management method in an unencapsulated packet transmission method comprising a. 19. The method of claim 18, wherein the second terminal sends a user location request message to the mobility server together with the user identifier.
The mobility server provides arbitrary information related to the user, such as the permanent three-layer address of the user and the three-layer address of the terminal being accessed as a routing identifier, for the request through the user identifier, foreseeing communication between two users, 1. The mobility management method of the non-encapsulated packet transmission method of claim 1, further comprising informing the user of the communication user, such as a user identifier and a routing address. The process of claim 14, wherein the user moves to a new terminal and performs handover.
The first user and the second user are in communication with each other, and the terminal (second terminal) of the second user maintains a session for communication with the first user, so that the first user is in another access router. In case of handover by moving to the second terminal,
Requesting, by the first user, a user connection to the second terminal using the first user identifier;
The second terminal recognizing the first user through the first user identifier and converting the first user identifier to the first user key;
Sending, by the second terminal, a user registration request message to the mobility server;
Recognize that the mobility server is a location update request for the first user through a Mobility Server Binding Information Table (MSBIT) search configured for the mobility management of the terminal and the user by using the first user key. Updating a user information record for the first user;
Sending, by the mobility server, a user registration request response message to the second terminal with a first user address;
Storing mapping information between a user and the terminal in the first user record of each terminal and a user binding information table (TUBIT) configured by the second terminal for transmitting an unencapsulated packet;
Storing, by the second terminal, mapping information between the first user and the second user through the TUBIT;
Establishing, by the first terminal to which the first user is connecting, a session for communication with the second user via a first user address and a second user address;
Sending, by the mobility server, a user location update message to the second terminal;
Updating, by the second terminal, mapping information between the first user and the second user through the TUBIT;
Configuring, by the second terminal, a packet in which a destination address and a source address are set to a first user address and a second user address, respectively;
Changing, by the second terminal, an address change operation of the packet according to the binding information of the TUBIT to change the destination address and the source address of the packet into a first routing identifier and a second routing identifier;
Forwarding the packet sent from the second terminal to the first terminal;
The first terminal performs an address change operation of a packet transmitted from the second terminal according to the binding information of the TUBIT, and changes a destination address and a source address of the packet into a first user address and a second user address, respectively; step; And
The first terminal receiving the packet; Mobility management method in an unencapsulated packet transmission method comprising a. The method of claim 20, wherein the second terminal transmits a user registration request message to the mobility server.
The mobility server further comprises informing the user of the corresponding terminal of the user in communication with the user through the user location update notification message of the updated mobility information of the user in advance, the mobility management in the non-encapsulated packet transmission method Way.

Images