CN102378150B - Data transmission method and proxy entity - Google Patents

Abstract

The present invention discloses a data transmission method and a proxy entity, comprising: the proxy entity receives an uplink data packet sent by a source IP user equipment, modifies the source address of the uplink data packet into the location identifier of the proxy entity; and When the destination address of the uplink data packet is not the location identifier of the domain router of the domain where the destination user equipment is located, the location identifier of the domain router of the domain where the destination user equipment is located is obtained from the location server according to the user identifier or domain name of the destination user equipment, and the The destination address of the uplink data packet is modified to be the location identifier of the domain router of the domain where the destination user equipment is located, and the modified uplink data packet is sent, implementing the embodiment of the present invention, so that all user equipment that only support the IP protocol can successfully Access to the mobility management system architecture based on user identity improves the mobility management performance of the user equipment, which is beneficial to the realization of the mobility management system architecture.

Description

Data Transfer Methods and Proxy Entities

technical field

The invention relates to the technical field of communication, in particular to a data transmission method and a proxy entity.

Background technique

The IP address currently used in the Internet (Internet) has dual semantics of topological location (Locator) and identifier (Identifier). Among them, from the perspective of network topology, the IP address has the Locator semantics, that is, the IP address represents a topological location when a certain host accesses the network, and when the host moves, the IP address needs to change accordingly; from the perspective of application From the point of view, the IP address has the semantics of the identifier (Identifier), that is, the IP address represents the identity of the host. When communicating between hosts, the IP address is used as an identifier (Identifier) for mutual identification between the two communicating parties. When the application connection is not disconnected In this state, the IP address needs to remain unchanged for as long as possible. At the beginning of the Internet design, the simple design of dual semantics of IP addresses met the needs of the network at that time, and it is one of the important factors for the great success of the Internet today. However, with the increase of Internet users, the rapid development of wireless networks, and the expansion of people's demand for ubiquitous communication, the coupling of locator and identifier of the IP address has caused some problems, among which the poor support for mobility is One of the main problems is that when the host moves, the location where it connects to the network changes, and the IP address needs to be changed accordingly, but at this time the identity of the host has not changed, and the IP address should not change, so a contradiction arises.

On the other hand, mobile communications and the Internet have achieved tremendous development respectively, prompting users to continuously expand their demand for Internet services through mobile devices. When users communicate, they seldom pay attention to where the other party is located and what equipment they use, but mainly focus on who the other party is. Therefore, the future network must be user-centric rather than host-centric. However, the current Internet network architecture is host-centered rather than user-centered, resulting in users not being able to conveniently obtain Internet services anytime and anywhere.

In this way, in order to meet the needs of more and more users to obtain the required information and services from the Internet anytime and anywhere, a mobile management system architecture based on user identity is proposed, so as to solve the dual semantics of the IP address and user identity Centered network architecture issues.

In the proposed mobility management system architecture based on user identity, it is difficult to manage mobility when the location of the user changes.

Contents of the invention

Embodiments of the present invention provide a proxy entity device and method to implement mobility management of terminals of various protocols based on user identity mobility management system architecture.

In order to solve the above technical problems, an embodiment of the present invention provides a data transmission method, including:

The proxy entity receives the uplink data packet sent by the source IP user equipment, where the data packet carries the IP address of the IP user equipment;

Modifying the source address of the data packet to the location identifier of the proxy entity; and when the destination address of the data packet is not the location identifier of the domain router of the domain where the destination user equipment is located, according to the user identifier of the destination user equipment or domain name, obtain the location identifier of the domain router of the domain where the user equipment is located from the location server, and modify the destination address of the data packet to the location identifier;

The proxy entity sends the modified data packet according to the destination address.

Correspondingly, the embodiment of the present invention also provides a data transmission method, including:

receiving the uplink data packet sent by the domain router, the data packet carrying the user identifier of the destination IP user equipment;

Obtaining the IP address of the destination IP user equipment according to the user identifier of the destination IP user equipment, and modifying the destination address of the data packet to the IP address;

sending the data packet according to the IP address.

Correspondingly, the embodiment of the present invention also provides a proxy entity, including:

An obtaining module, configured to obtain, from a location server, the location identifier of the domain router of the domain where the user equipment is located according to the user identifier or domain name of the destination user equipment when the destination address of the data packet is not the location identifier of the destination user equipment;

An update module, configured to modify the source address of the data packet to the location identifier of the proxy entity, and, when the destination address of the data packet is not the location identifier of the destination user equipment, modify the destination address of the data packet to The location identifier queried by the query module;

A sending module, configured to send the modified data packet according to the destination address.

As can be seen from the above, the technical solutions of the embodiments of the present invention have the following beneficial effects:

According to a data transmission method provided by the embodiment of the present invention, by receiving the data packet sent by the source IP user equipment, according to the difference of the destination address of the data packet, by modifying the source address and the destination address of the data packet, the data of the IP user equipment is transferred to The transmission and exchange of packets in the mobility management system based on user identity enables user equipment that does not support the UIP protocol to successfully access the architecture of the mobility management system based on user identity, improving the mobility management performance of user equipment, which is beneficial to Implementation of mobile management system architecture.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the accompanying drawings required in the embodiments. Obviously, the accompanying drawings in the following description are only some of the present invention. Embodiments, for those of ordinary skill in the art, other drawings can also be obtained according to these drawings without paying creative labor.

FIG. 1 is a schematic diagram of a mobility management system architecture based on user identity;

Fig. 2 is a flow chart of the data transmission method provided by the first embodiment of the present invention;

Fig. 3 is a flow chart of a data transmission method provided by the second embodiment of the present invention;

Fig. 4 is a flow chart of a data transmission method provided by a third embodiment of the present invention;

FIG. 5 is a flowchart of a data transmission method provided by a fourth embodiment of the present invention;

Fig. 6 is a schematic structural diagram of a proxy entity provided by a fifth embodiment of the present invention.

Detailed ways

First, a brief introduction is made to the architecture of the mobility management system based on user identity. As shown in Figure 1, wherein, the mobile management system based on user identity divides the entire network into multiple domains, wherein the domains can be divided according to network topology information, operation policies, geographical location information, etc. ; Each domain includes at least one Subscriber Location Server (SLS), and at least one Domain Router (DR). In the mobility management system based on user identity, a Global Subscriber Location Server (Global SLS) independent of each domain may also be included.

Wherein, the Global SLS stores Home Domain information in the Global SLS. The user ID can contain the indication of the user's Home Domain, and the Global SLS can query the corresponding Home Domain information according to the indication of the user's Home Domain contained in the user ID, and then obtain the user's Home SLS. The subscription location server SLS stores the subscription information of its subscribers and the mapping relationship between the user ID of the subscriber and the DR the user is currently connected to. Related information, the subscription information of the user includes user identifier, user context, user profile (profile) and so on. The subscription domain is called the user's home domain (Home Domain). When the user moves out of the home domain and arrives at another domain, the other domain is called the user's visited domain (Visited Domain). In addition, the SLS is also used to assign DRs to users accessing its domain. The domain routing device DR stores the mapping relationship between the user identifier and the user's current local topological location (local locator); the DR is a data plane entity, which is used to process data-related signaling, and is also responsible for data forwarding inside and outside the domain, In addition, when the user's movement requires DR switching and updating, the DR after switching notifies the SLS of the user's DR updating.

It should also be noted that in each domain, a location identifier called a local locator is used to implement the routing of data packets. The local locator does not require global uniqueness, but only requires uniqueness within the domain. However, when network entities belonging to different domains communicate, or network entities within a domain communicate with network entities on the Internet, a location identifier called a global topological location Global locator needs to be used, and the Global locator requires global uniqueness. In this way, it is required that the first-level data rendezvous point DR should have at least one Globallocator.

When an ordinary IP user equipment needs to transmit data packets in the above network architecture, the data packet needs to be forwarded by a proxy entity (User Identity Protocol proxy, UIPproxy) in the domain where the IP user equipment is located, and the ordinary IP user equipment can complete the communication with the IP user equipment. Packet switching of devices in the above network architecture. The data transmission method provided by the embodiment of the present invention is described below.

Embodiment one

The first embodiment of the data transmission method provided by the present invention will be described below. The data transmission method includes:

Step 1101, the proxy entity receives the uplink data packet sent by the source IP user equipment.

The source user equipment needs to exchange data packets with the destination user equipment. When the source user equipment sends the data packet to the destination equipment, the data packet is called an uplink data packet, and the destination user equipment converts the data packet after receiving it. Returning to the source user equipment, during the process of returning the data packet from the destination user equipment to the source user equipment, the data packet is called a downlink data packet. The IP address of the IP user equipment is carried in the data packet.

Step 1102, modify the source address of the uplink data packet to the location identifier of the proxy entity; and when the destination address of the uplink data packet is not the location identifier of the domain router of the domain where the destination user equipment is located, according to the user of the destination user equipment ID or domain name, obtain the location identifier of the domain router of the domain where the user equipment is located from the location server, and modify the destination address of the uplink data packet to the location identifier of the domain router of the domain where the destination user equipment is located.

If the destination address is the domain name or user identifier of the domain where the destination user equipment is located, then according to the user identifier or domain name of the destination user equipment, obtain the location identifier of the domain router of the domain where the user equipment is located from the location server, and modify the destination address of the data packet ID for the location, and modify the source address to the location identifier of the proxy entity itself.

Step 1103, the proxy entity sends the modified data packet according to the destination address.

The source address of the data packet is the location identifier of the proxy entity, and the destination address is the location identifier of the domain router of the domain where the destination user equipment is located. The data packet is sent to the domain router of the source domain, and the source domain router The user ID addressing is forwarded by the domain router in the source domain to the domain router in the destination domain, and then sent to the destination user equipment in the destination domain.

A method of data transmission provided by this embodiment, by receiving the data packet sent by the source IP user equipment, according to the difference of the destination address of the data packet, by modifying the source address and destination address of the data packet, the data packet of the IP user equipment The transmission and exchange in the mobility management system based on user identity enables user equipment that does not support the UIP protocol to successfully access the architecture of the mobility management system based on user identity, improving the mobility management performance of user equipment, which is beneficial to mobile Implementation of the management system architecture.

Embodiment two

The second embodiment of the data transmission method provided by the present invention will be described below. In this embodiment, the data packet exchange between the source IP user equipment and the destination UIP user equipment in different domains is used as an example for illustration. The data transmission method includes :

When the source IP user equipment enters the network, the network side will assign a user ID to the IP user equipment to represent the IP user equipment. After the user equipment access authentication is completed, the network side sends the user ID to the UIP proxy, and the UIP proxy saves the user ID and the correspondence between the user ID and the IP address, and sends the user ID to the location server; or, The DHCP process is initiated by the IP user equipment itself, UIP proxy receives the registration request message of the IP user equipment, and then registers the IP user equipment with the location server, and the location server will assign a user ID to the IP user equipment and send this ID to UIP proxy , after UIP proxy receives the user ID, it saves the user ID and the corresponding relationship between the user ID and the user ID and the IP address; or, the UIP proxy specifies a user ID for the IP user equipment, and can directly specify the IP address as The user ID of the IP user equipment, or, the UIP proxy assigns a unique ID in the domain to the IP user equipment as the user ID to represent the IP user equipment. This ID can be a MAC address or other user equipment as long as it satisfies the unique allocation in the domain. A certain inherent attribute is identified by derivation according to a certain method or algorithm, and then the allocated IP user equipment is notified to the contracted location server and other equipment. In addition, the UIP proxy also stores the IP address and user ID of the IP user device, as well as the correspondence between the two.

Step 1201, the source IP user equipment constructs a data packet according to its own IP address and the location identifier of the domain router of the domain where the destination UIP user equipment is located or the user identifier of the destination UIP user equipment.

The source address of the data packet is the IP address of the source IP user equipment, and the destination address of the data packet may be the location identifier of the domain router of the domain where the destination UIP user equipment is located or the user identifier of the UIP user equipment.

If there is neither the location identifier of the domain router of the domain where the destination UIP user equipment is located on the IP user equipment, the source IP user equipment queries through the UIP proxy. The query process is as follows:

The source IP user equipment sends a query request message, which carries the user identifier of the destination UIP user equipment;

UIP proxy receives the query request message of the source IP user equipment, searches on the location server according to the domain name or the user identification, queries the location identification of the domain router of the domain where the destination UIP user equipment is located, and saves the inquired user identification and the location of the domain router The location and the corresponding relationship between the two, and return the query result to the source IP user equipment.

The source IP user equipment is updated as the destination address of the data packet according to the location identifier of the domain router of the domain where the destination UIP user equipment is located returned by the UIP proxy. The source IP user equipment can also not search for the location identifier by UIPproxy, and just use the user identifier of the destination user equipment as the destination address to construct a data packet and send it to UIP proxy.

Step 1202, UIP proxy receives the data packet sent from the source IP user equipment, the source address of the data packet is the IP address of the source IP user equipment, and the destination address is the location identifier of the domain router of the domain where the destination user equipment is located or the destination user equipment User ID for .

If the destination address is the location identifier of the domain router of the domain where the destination UIP user equipment is located, then go to step 1204; if the destination address is the user identifier of the destination UIP user equipment, go to step 1203.

Step 1203, according to the user identifier of the destination user equipment, obtain the location identifier of the domain router of the domain where the user equipment is located from the location server, and modify the destination address of the data packet to the location identifier. Go to step 1204.

Step 1204, UIP proxy modifies the source address of the data packet to the location identifier of the proxy entity; and adds the user identifier of the IP user equipment and the user identifier of the destination user equipment to the data packet.

When the destination address of the data packet is the user identification of the destination UIP user equipment, the UIP proxy searches the location server for the location identification of the domain router in the domain where the UIP user equipment of the user identification is located according to the user identification of the UIP user equipment, and sends the data packet The destination address of the update said location identifier; Source address is updated to the location identifier of the proxy entity UIP proxy itself; When the destination address of the data packet is the location identifier of the domain router of the domain where the destination user equipment is located, the destination address need not be changed.

According to the corresponding relationship between the stored IP address and the user identifier, the user identifier is searched according to the IP address carried in the data packet, and the user identifier of the source IP user equipment and the destination UIP user identifier are added to the data packet.

In addition, UIP proxy also needs to add an information header to the data packet, which carries the types of the source user equipment and the destination user equipment. This type indicates whether the user equipment is a source IP user equipment supporting the IP protocol or a UIP user supporting the UIP protocol. equipment.

Step 1205, UIP proxy sends the modified data packet to the domain router in the source domain, and the domain router in the source domain replaces the source address with It is the global address of the source domain router, and the destination address is changed to the address of the domain router in the domain where the destination user equipment is located, and the corresponding relationship between the source domain router address and the UIP Proxy address is recorded. In terms of implementation, UIP Proxy can be deployed together with domain routers. Where the packet is sent to the domain router of the domain where the destination user device is located.

Step 1206, the domain router of the destination UIP user equipment receives the data packet, judges that the destination user equipment is a UIP user equipment according to the information carried in the received data packet, and searches for the location of the destination user equipment according to the user identification of the destination user equipment, thereby forwarding data packet to the destination UIP user equipment. The data packet carries the user identifier of the destination user equipment and the user identifier of the source user equipment.

The type of the destination user equipment is UIP user equipment, and the subsequent process of forwarding to the UIP user equipment does not need to go through the UIP proxy, and the forwarding is carried out according to the normal process.

After receiving the data packet, the UIP user equipment modifies the destination address of the data packet to the address of the domain router of the domain where the source IP user equipment is located, and updates the source address to the location identifier of the destination UIP user equipment. Then the data packet is forwarded to the domain router of the domain where the source IP user equipment is located, and the domain router learns that the source user equipment is an IP user equipment according to the type indication of the data packet, and sends the data packet to UIPproxy.

Step 1207, the UIP proxy receives the downlink data packet sent to the source IP user equipment, and the data packet carries the user identifiers of the source IP user equipment and the destination user equipment.

Step 1208, UIP proxy obtains the IP address of the source IP user equipment according to the user identifier of the IP user equipment, modifies the destination address of the data packet to the IP address and sends it to the IP user equipment. Thus, the data packet exchange between the source IP user equipment and the destination UIP user equipment is completed.

In the method and device for data transmission provided by the embodiments of the present invention, under the framework of the mobile management system based on user identity, the device of the proxy entity receives the data packet of the transmitting end with a protocol different from that of the receiving end, and according to the information carried in the data packet, The update data packet is a data packet that can be recognized by the receiving end, so that the transmitting end and the receiving end that support different protocols can perform normal data exchange, which is conducive to the promotion and popularization of the new network based on the mobile management system architecture based on user identity.

Embodiment three

The third embodiment of the data transmission method provided by the present invention will be described below. In this embodiment, IP user equipment and IP user equipment in different domains perform data packet exchange as an example. The data transmission method includes:

Assuming that the IP user equipment has completed the access, first, the source IP user equipment performs the same steps as Step 1201 to Step 1205 in Embodiment 2. After the execution is completed, the follow-up process is as follows:

Step 1301, the domain router of the domain where the destination IP user equipment is located receives the data packet.

Step 1302, the domain router judges that the type of the destination user equipment is an IP user equipment according to the information carried in the data packet, and does not support the UIP protocol, and forwards the data packet to the UIP proxy of the domain where the destination IP user equipment is located.

Step 1303, the UIP proxy in the domain where the destination IP user equipment is located receives the data packet, which carries the user identifiers of the source user equipment and the destination user equipment.

Step 1304, the UIP proxy of the domain where the destination IP user equipment is located searches for the correspondence between the user identifier and the IP address according to the user identifier of the destination user equipment, finds the IP address of the destination user equipment, and updates the destination address of the data packet to be the IP address of the user equipment , and forward the data packet to the destination IP user equipment.

Step 1305, the destination IP user equipment receives the data packet, updates the address of the source IP user equipment to the destination address, updates its own IP address to the source address, and sends the data packet to the UIP proxy of the domain where the destination IP user equipment is located.

Step 1306, the UIP proxy in the domain where the destination IP user equipment is located receives the downlink data packet sent from the destination IP user equipment.

Step 1307, update the source address and destination address of the data packet, specifically: update the source address of the data packet to its own location identifier, and update the destination address to the location identifier of the domain router of the domain where the source IP address is located.

Step 1308, send the data packet to the domain router of the domain where the source IP user equipment is located.

Step 1309, the domain router of the destination domain forwards to the domain router of the domain where the source IP user equipment is located, and the domain router of the source domain forwards the data packet to the UIP proxy of the source domain.

Then, the UIP proxy in the source domain performs a process similar to Step 1207 to Step 1209 in Embodiment 2, specifically: the UIP proxy of the source IP user equipment receives a downlink data packet, and the data packet carries the source IP user equipment and the destination IP user equipment User ID for . The UIP proxy of the source IP user equipment searches for the IP address of the source IP user equipment according to the user identification of the source IP user equipment, updates the IP address as the destination address of the data packet, and then returns the data packet to the source IP user equipment, Thus completing the process of data packet exchange.

A data transmission method provided in this embodiment, by receiving the data packet sent by the source IP user equipment, according to the difference of the destination address of the data packet, by modifying the source address or the destination address of the data packet, the data packet of the IP user equipment The transmission and exchange in the mobility management system based on user identity enables user equipment that does not support the UIP protocol to successfully access the architecture of the mobility management system based on user identity, improving the mobility management performance of user equipment, which is beneficial to mobile Implementation of the management system architecture.

Embodiment Four

The third embodiment of the data transmission method provided by the present invention will be described below. In this embodiment, the data packet exchange between the source UIP user equipment and the destination IP user equipment in different domains is used as an example for illustration. The data transmission method include:

Step 1401, the source UIP user equipment constructs a data packet according to its own location identifier and user identifier, and the user identifier of the destination IP user equipment.

The source address of the data packet is the location identifier of the source UIP user equipment, and the destination address of the data packet may be the user identifier of the destination IP user equipment.

Step 1402, the source UIP user equipment sends the data packet to the domain router of the source domain. The domain router of the domain where the source UIP user equipment is located modifies the destination address of the data packet to the address of the domain router of the domain where the destination IP user equipment is located. And, forward the data packet to the domain router of the domain where the destination IP user equipment is located.

Step 1403, the domain router of the domain where the destination IP user equipment is located receives the data packet, the data packet carries the user identification and location identification of the source UIP user equipment, and the user identification of the destination IP user equipment and the location of the domain router of the domain where the IP user equipment is located. Location ID.

Step 1404, the domain router of the destination domain judges that the type of the destination user equipment is an IP user equipment according to the information carried in the data packet, and does not support the UIP protocol, and forwards the data packet to the UIP proxy of the domain where the destination IP user equipment is located.

Step 1405, the UIP proxy in the domain where the destination IP user equipment is located receives the data packet, which carries the user identifiers of the source UIP user equipment and the destination IP user equipment.

Step 1406, the UIP proxy of the domain where the destination IP user equipment is located searches for the correspondence between the user identifier and the IP address according to the user identifier of the destination user equipment, finds the IP address of the destination user equipment, and updates the destination address of the data packet to be the IP address of the user equipment , and forward the data packet to the destination IP user equipment.

Step 1407, the destination IP user equipment receives the data packet, updates its own IP address to the source address, and sends the data packet to the UIP proxy of the domain where the destination IP user equipment is located.

Step 1408, the UIP proxy of the domain where the destination IP user equipment is located receives the downlink data packet sent from the destination IP user equipment, updates the source address of the data packet to its own location identification, and updates the destination address to the domain of the domain where the source UIP user equipment is located The location identifier of the router, and sends the data packet to the domain router of the domain where the source UIP user equipment is located.

Step 1409, the domain router of the domain where the source UIP user equipment is located receives the downlink data packet sent from the destination IP user equipment, updates the source address of the data packet to its own location identifier, and updates the destination address to the address of the source UIP user equipment, and The data packet is sent to the source UIP user equipment, thereby completing the process of data packet exchange.

A data transmission method provided in this embodiment, by receiving the data packet sent by the source IP user equipment, according to the difference of the destination address of the data packet, by modifying the source address or the destination address of the data packet, the data packet of the IP user equipment The transmission and exchange in the mobility management system based on user identity enables user equipment that does not support the UIP protocol to successfully access the architecture of the mobility management system based on user identity, improving the mobility management performance of user equipment, which is beneficial to mobile Implementation of the management system architecture.

Embodiment five

The following describes the fifth embodiment of the proxy entity provided by the present invention. The proxy entity includes:

A receiving module 51, configured to receive a data packet sent by a source IP user equipment, the data packet carrying the IP address of the IP user equipment;

The obtaining module 52 is configured to obtain, from the location server, the location identifier of the domain router of the domain where the user equipment is located according to the user identifier or domain name of the destination user equipment when the destination address of the data packet is not the location identifier of the destination user equipment;

An update module 53, configured to modify the source address of the data packet to the location identifier of the proxy entity, and, when the destination address of the data packet is not the location identifier of the destination user equipment, modify the destination address of the data packet The location identifier queried by the query module; and, adding the user identifier of the IP user equipment and the user identifier of the destination user equipment to the data packet;

A sending module 54, configured to send the modified data packet according to the destination address.

Specifically, the acquisition module 52 also includes:

The first acquiring unit 521 is configured to, according to the IP address of the source IP user equipment, search for the correspondence between the locally stored IP address and the user identifier, and acquire the user identifier of the source IP user equipment;

The second acquiring unit 522 is configured to acquire the user identifier of the destination user equipment from the location server;

Or, the first acquiring unit 521 is configured to use the IP address of the IP user equipment as the user identifier of the IP user equipment.

Preferably, the proxy entity also includes:

The receiving module 51 is further configured to receive a location query message of a destination user equipment sent by the source IP user equipment, where the query message carries a domain name or a user identifier of the destination user equipment;

The query module 55 is configured to query the user identifier of the user equipment or the location identifier of the domain router of the domain where the destination user equipment is located according to the domain name of the destination user equipment, and send the query result to the IP user equipment, or

The sending module 54 is further configured to query the location identifier of the domain router in the domain where the user equipment is located according to the user identifier of the destination user equipment, and return the query result to the IP user equipment.

Preferably, the proxy entity also includes:

The storage module 56 is configured to store the corresponding relationship between the user identifier of the destination user equipment and the location identifier of the domain router of the domain where the destination user equipment is located.

Preferably, the proxy entity also includes:

The receiving module 51 is further configured to receive a registration request message of the IP user equipment;

The registration module 57 is configured to register the IP user equipment with a location server, and receive the user identification sent by the location server for the IP user equipment.

Preferably, the proxy entity also includes:

The receiving module 51 is further configured to receive a data packet sent to the source IP user equipment, where the data packet carries user identifiers of the source IP user equipment and the destination user equipment;

The acquiring module 52 is further configured to acquire the IP address of the source IP user equipment according to the user identifier of the IP user equipment;

The sending module 54 is further configured to modify the destination address of the data packet to the IP address and send it out.

This proxy entity also includes

The receiving module 51 is configured to receive an uplink data packet, the data packet carrying the user identifier of the destination IP user equipment;

The acquisition module 52 is configured to acquire the IP address of the destination IP user equipment according to the user identifier of the destination IP user equipment;

The update module 53 is configured to modify the destination address of the data packet to the IP address;

The sending module 54 is configured to send the data packet according to the IP address.

Preferably, the proxy entity also includes:

The receiving module 51 is configured to receive a downlink data packet sent by the destination IP user equipment, the data packet carrying the IP address of the destination IP user equipment; the destination address of the data packet is the domain router of the domain where the source user equipment is located location identifier for

The acquiring module 52 is configured to acquire the user identifiers of the source user equipment and the destination IP user equipment,

and adding the user identifiers of the source user equipment and the destination IP user equipment to the data packet;

The sending module 54 is configured to send the modified data packet.

A data transmission method provided in this embodiment, by receiving the data packet sent by the source IP user equipment, according to the difference of the destination address of the data packet, by modifying the source address or the destination address of the data packet, the data packet of the IP user equipment The transmission and exchange in the mobility management system based on user identity enables user equipment that does not support the UIP protocol to successfully access the architecture of the mobility management system based on user identity, improving the mobility management performance of user equipment, which is beneficial to mobile Implementation of the management system architecture.

Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above-mentioned embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium, and the storage medium can include: Read Only Memory (ROM), Random Access Memory (RAM), Magnetic or Optical Disk, etc.

The above is a detailed introduction of a proxy entity and data transmission method provided by the embodiment of the present invention. In this paper, specific examples are used to illustrate the principle and implementation of the present invention. The description of the above embodiment is only used to help understanding The method of the present invention and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation and scope of application. In summary, the content of this specification should not be construed as a limitation of the invention.

Claims (15)

1. a method for transfer of data, is characterized in that, described method comprises:

Agent entity receives the upstream data bag that source IP user's equipment sends;

By the station location marker that the source address modification of described upstream data bag is described agent entity; And when the destination address of described upstream data bag is domain name or the user ID in territory, object subscriber equipment place, according to user ID or the domain name of described object subscriber equipment, obtain the station location marker of the territory router in territory, object subscriber equipment place from location server, the destination address of described upstream data bag is revised as the station location marker of the territory router in territory, described object subscriber equipment place;

Described agent entity sends amended described upstream data bag according to described destination address.

2. data transmission method as claimed in claim 1, is characterized in that, described method also comprised before described agent entity sends amended described upstream data bag according to described destination address:

The user ID of described source IP user's equipment and the user ID of described object subscriber equipment is increased, addressing when the territory router that the user ID of described source IP user's equipment and the user ID of described object subscriber equipment are used for described source IP user's device Domain sends described upstream data bag in described upstream data bag.

3. data transmission method as claimed in claim 2, is characterized in that, also comprise before increasing the user ID of described source IP user's equipment and the user ID of described object subscriber equipment:

According to the IP address of source IP user's equipment, search the local IP address of storage and the corresponding relation of user ID, obtain the user ID of described source IP user's equipment, and the user ID of object subscriber equipment is obtained from location server, wherein said upstream data bag carries the IP address of described source IP user's equipment;

Or using the IP address of object IP user equipment as the user ID of object IP user equipment, wherein said upstream data bag carries the IP address of described source IP user's equipment.

4. data transmission method as claimed in claim 1, is characterized in that, before the packet of described reception source IP user's equipment, also comprise:

Receive the position enquiring message of the object subscriber equipment that described source IP user's equipment sends, described query messages carries domain name or the user ID of object subscriber equipment;

According to the domain name of object subscriber equipment, the station location marker of the user ID of inquiry object subscriber equipment or the territory router in territory, object subscriber equipment place, and Query Result is sent to source IP user's equipment;

Or according to the user ID of described object subscriber equipment, the station location marker of the territory router in inquiry territory, object subscriber equipment place, and Query Result is returned to source IP user's equipment.

5. data transmission method as claimed in claim 1, it is characterized in that, described method also comprises:

Preserve the corresponding relation of the station location marker of the user ID of object subscriber equipment and the territory router in territory, object subscriber equipment place.

6. data transmission method as claimed in claim 5, is characterized in that, in described reception before the query messages of source IP user's equipment, also comprise:

Receive the login request message of described source IP user's equipment;

Register described source IP user's equipment to location server, and receive the user ID that described location server is the IP user's equipment transmission of described source;

Preserve the user ID of described source IP user's equipment and the corresponding relation of IP address.

7. the method for transfer of data as claimed in claim 2, it is characterized in that, described method also comprises:

Receive the downlink data packet sending to described source IP user's equipment, described downlink data packet carries the user ID of source IP user's equipment and object subscriber equipment;

According to the user ID of described source IP user's equipment, obtain the IP address of described source IP user's equipment, the destination address of described downlink data packet is revised as described IP address and sends.

8. an agent entity, is characterized in that, described agent entity comprises:

Receiver module, for receiving the upstream data bag that source IP user's equipment sends;

Acquisition module, during for being domain name or the user ID in territory, object subscriber equipment place at the destination address of described upstream data bag, according to user ID or the domain name of described object subscriber equipment, obtain the station location marker of the territory router in territory, subscriber equipment place from location server;

Update module, for by the source address modification of described upstream data bag being the station location marker of described agent entity, and, when the destination address of described upstream data bag is domain name or the user ID in territory, object subscriber equipment place, the destination address of described upstream data bag is revised as the described station location marker that enquiry module inquires;

Sending module, for sending amended described upstream data bag according to described destination address.

9. agent entity as claimed in claim 8, is characterized in that, described update module is also for the user ID of the user ID and described object subscriber equipment that increase described source IP user's equipment in described upstream data bag.

10. agent entity as claimed in claim 9, it is characterized in that, described acquisition module also comprises:

First acquiring unit, for the IP address according to source IP user's equipment, search the local IP address of storage and the corresponding relation of user ID, obtain the user ID of described source IP user's equipment, wherein said upstream data bag carries the IP address of described source IP user's equipment;

Second acquisition unit, for obtaining the user ID of object subscriber equipment from location server.

11. agent entitys as claimed in claim 10, it is characterized in that, described acquisition module also comprises:

Described first acquiring unit, also for using the IP address of object IP user equipment as the user ID of object IP user equipment.

12. agent entitys as claimed in claim 8, it is characterized in that, described agent entity also comprises:

Described receiver module, also for receiving the position enquiring message of the object subscriber equipment that described source IP user's equipment sends, described query messages carries domain name or the user ID of object subscriber equipment;

Enquiry module, for the domain name according to object subscriber equipment, the station location marker of the user ID of inquiring user equipment or the territory router in territory, object subscriber equipment place, and Query Result is sent to described source IP user's equipment, or

Described sending module, also for the user ID according to described object subscriber equipment, the station location marker of the territory router in territory, inquiring user equipment place, and Query Result is sent to described source IP user's equipment.

13. agent entitys as claimed in claim 8, it is characterized in that, described agent entity also comprises:

Memory module, for the corresponding relation of the station location marker of the territory router of the user ID and territory, object subscriber equipment place of preserving object subscriber equipment.

14. agent entitys as claimed in claim 13, it is characterized in that, described agent entity also comprises:

Described receiver module, also for receiving the login request message of described source IP user's equipment;

Registering modules, for registering described source IP user's equipment to location server, and receives the user ID that described location server is the IP user's equipment transmission of described source.

15. agent entitys as claimed in claim 9, it is characterized in that, described agent entity also comprises:

Described receiver module, also for receiving the downlink data packet sending to described source IP user's equipment, described downlink data packet carries the user ID of source IP user's equipment and object subscriber equipment;

Described acquisition module, also for the user ID according to described source IP user's equipment, obtains the IP address of described source IP user's equipment;

Described sending module, also for the destination address of described downlink data packet being revised as described IP address and sending.