WO2011041972A1 - 一种数据报文主动推送的实现方法及系统 - Google Patents

一种数据报文主动推送的实现方法及系统 Download PDF

Info

Publication number
WO2011041972A1
WO2011041972A1 PCT/CN2010/076902 CN2010076902W WO2011041972A1 WO 2011041972 A1 WO2011041972 A1 WO 2011041972A1 CN 2010076902 W CN2010076902 W CN 2010076902W WO 2011041972 A1 WO2011041972 A1 WO 2011041972A1
Authority
WO
WIPO (PCT)
Prior art keywords
host node
data packet
node
identity
forwarding plane
Prior art date
Application number
PCT/CN2010/076902
Other languages
English (en)
French (fr)
Inventor
符涛
沈岷
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2011041972A1 publication Critical patent/WO2011041972A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1859—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast adapted to provide push services, e.g. data channels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/54—Store-and-forward switching systems 
    • H04L12/56—Packet switching systems

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and system for implementing active push of data packets.
  • a large number of service servers are deployed on the existing Internet to provide rich and colorful services for the majority of Internet users.
  • a web server that provides news
  • a game server that provides connected games
  • a search server that provides massive search services, and so on.
  • These services are generally provided by the user to obtain the service actively, that is: the user uses various terminals (PC, personal digital assistant (PDA), smart phone, etc., hereinafter referred to as user terminals) connected to the Internet to actively
  • a specific service server on the Internet establishes a communication connection, sends a specific service request to the service server, and then obtains a service response from the service server, and the service response includes various types of information required by the user.
  • This type of service delivery is not suitable for certain services.
  • the weather forecast service the user wants the service server to actively push the user after obtaining the latest weather forecast information, without waiting for the user to actively access the service server for acquisition, which will affect the timeliness of the weather forecast information.
  • the existing Internet does not support such a function that the service server actively pushes information to the user (hereinafter referred to as the PUSH function).
  • the reason is that the communication on the Internet uses the IP address to identify the transceiver end of the data message.
  • the IP address of the service server can be obtained through the DNS function.
  • the IP address obtained when the user terminal connects to the Internet is dynamically allocated by the Internet access operator. If the user terminal does not actively connect to the service, the service is not provided.
  • the service server cannot obtain the IP address of the user terminal of the specific user, and cannot actively send the data (including the specific information) to the user terminal.
  • a compromise solution in the existing Internet technology is: After the user terminal connects to the Internet, it sends a login request to a specific service server, and the service server records the IP address currently used by the user terminal; The information pushed to the user, that is, the data message is transmitted using the recorded user terminal IP address.
  • the disadvantage of this solution is: If the user has many services that need to actively push data packets (provided by different service servers), then the user terminal needs to send login messages to different service servers after connecting to the Internet (which also Involved in authentication and other processes); Once the user accidentally drops the network and reconnects, the IP address changes, you need to re-login; If the service server is abnormal during the user's network connection, and the user terminal IP address information is lost, PUSH cannot be used. Work
  • the root cause of the above problem lies in the semantic overload defect of the IP address.
  • the IP address in the TCP/IP (Transmission Control Protocol/Internet Protocol) protocol widely used on the Internet has a dual function, which serves as the location of the network terminal's communication terminal host network interface in the network topology.
  • the identity which is also the identity of the transport layer host network interface.
  • the TCP/IP protocol was not designed with host mobility in mind. Once the location of the communication host changes, the IP address may change, causing the identity to change. When communication host mobility becomes more and more common, the semantic overload defect of such an IP address becomes increasingly apparent. For example, as mentioned above, the IP address of the user terminal of a specific user is variable, and the service server can only implement the PUSH function by knowing the current IP address of the user terminal at any time.
  • the industry has proposed the idea of identity and location separation, separating the original dual functions of IP addresses, using different identifiers for location identifiers and identity identifiers.
  • location identifiers still use IP addresses, identity identifiers.
  • the location identifier may change with the access point location, access time and other factors, but its identity may remain unchanged.
  • the service layer only uses the identity of the communication host to establish end-to-end communication, and does not care about the location. The change in identity. In this way, the service server can push the data packet to the user terminal as long as it knows the identity of the user terminal of the specific user. How the data message is sent to the correct location of the user terminal is implemented by a specific solution of identity identification and location separation.
  • the main protocol in the host-based implementation scheme is the Host Identity Protocol (HIP).
  • the main protocol in the router-based implementation scheme is the Locator/ID Separation Protocol (LISP). Wait.
  • HIP is a host mobility association protocol. HIP separates IP addresses into end identifiers and location labels. Knowledge. The basic idea of HIP is to introduce a 3.5-layer Host Identity Layer (HIL) between the Layer 3 network layer and the Layer 4 transport layer, that is, the host identifier is introduced between the domain name space and the IP address space. Host Identity, HI) space.
  • HIL Host Identity Layer
  • HI Host Identity
  • the host identification layer separates the originally tightly coupled transport layer from the network layer. The IP address no longer plays the role of the identity host. It is only responsible for the routing and forwarding of data packets, that is, it is only used as a locator.
  • the host name is represented by the host identifier. .
  • the host identification layer is logically located between the network layer and the transport layer.
  • the transport layer uses the transport layer identifier, and the host identifier layer completes the host identifier and IP address translation in the data message.
  • the network layer is shielded from the transport layer, and any changes in the network layer (for example, changes in the host IP address during communication) do not affect the transport layer link unless the quality of service changes.
  • the transport layer connection is established on top of the host identifier, and the IP address can only be used for network layer routing and is no longer used to identify the host identity.
  • the key idea of HIP is to disconnect the tight coupling between the network layer and the transport layer, so that the connection between the application layer and the transport layer is not affected by the change of the IP address.
  • HI remains unchanged, thereby ensuring uninterrupted connectivity.
  • the IP address is only used for routing and addressing functions, and HI is used to identify the end host to which a connection corresponds, instead of the IP address used in the connection socket.
  • HIP is a host protocol.
  • the main problem is: The premise of the deployment is that the terminal hosts (including the user terminal and the service server) that need to participate in the communication support the HIP protocol synchronously, and need to make major changes to the terminal host or even the upper layer application.
  • the HIP protocol cannot implement anonymous communication.
  • LISP reuses routing technology and has made some changes to the existing routing topology. Combined with the existing transport network, it optimizes the existing routing technology with minimal transformation.
  • the host uses an IP address (called an End Identifier (EID) in the LISP system) to track sockets, establish connections, send and receive data messages. Routers pass data packets based on IP destination addresses (called Routing Locations (RLOCs) in LISP systems).
  • EID End Identifier
  • RLOCs Routing Locations
  • Tunnel routing is introduced in the LISP system.
  • the ITR (Tunnel Ingress Router) is the starting end of the tunnel, and the ETR (Tunnel Exit Router) is the terminating end of the tunnel.
  • the host After the host sends a data message, it is encapsulated by the ITR as a LISP data message, and the LISP data message is decapsulated by the ETR before the LISP data message is finally delivered to the destination.
  • the IP address of the "outer header" in the LISP data message is RLOCs.
  • the ITR encapsulates a new LISP header for each packet and performs an EID-to-RLOC lookup to determine the routing path to the ETR.
  • ETR uses RLOC as its own address.
  • the core router between the ITR and the ETR is only responsible for the routing of the RLOC, and does not have to care about the routing of the EID.
  • LISP reduces the number of routing table entries in the core router.
  • the main solution is the problem of excessive network size.
  • the problem of mobility has not been solved. That is, when the same host moves across subnets, its EID is possible. If the change occurs, the EID is not sufficient as the identity of the user terminal when moving. Therefore, for the PUSH function, LISP has a similar problem to the existing Internet, that is, the service server needs to obtain the current EID of the user terminal by other means.
  • the present invention provides a method and system for implementing active push of data packets, which solves the problem that the service server actively pushes data packets to the user terminal.
  • the present invention provides a method for implementing active push of data packets, including:
  • the first host node sends the data packet to be sent to the second host node to the first access service node where the first host node is located, where the data packet includes the identity identifier of the second host node;
  • the location identifier After the first access service node receives the data packet, if the location identifier corresponding to the identity of the second host node is locally queried, the location identifier is added to the data packet. And sending the data packet to the generalized forwarding plane; if the location identifier corresponding to the identity of the second host node is not queried locally, the data packet is encapsulated and sent to the mapping forwarding plane, where After receiving the data packet, the mapping forwarding plane queries the location identifier corresponding to the identity identifier of the second host node, adds the location identifier to the data packet, and forwards the data packet to the generalized Forwarding plane;
  • the generalized forwarding plane forwards the data packet to a second access service node where the second host node is located, and the second access service node sends the data packet to the second host node .
  • the method may further include: when the first access service node does not query the location identifier corresponding to the identity of the second host node locally, initiate a mapping query request to the mapping forwarding plane; After mapping the location identifier corresponding to the identity of the second host node returned by the mapping forwarding plane, the mapping record of the identity identifier and the location identifier of the second host node is locally added.
  • the first host node may further carry the identifier of the first host node in the data packet sent by the first access service node where the first host node is located; the method may further include: the first access service node to the generalized forwarding plane or Before the mapping forwarding plane sends the data packet, the identity of the first host node carried in the data packet is anonymized.
  • the method may further include: acquiring, by the first host node, the identity of the second host node by: when the second host node actively connects to the first host node, recording the identity of the second host node, or The middle query obtains the identity of the second host node.
  • the method may further include: before adding the location identifier to the data packet, determining, by the first access service node, whether the second host node is under the first access service node, and if yes, forwarding the data packet to the second The host node, if not, adds the location identifier to the data packet and sends the data packet to the generalized forwarding plane.
  • the first host node may be a user terminal or a service server
  • the second host node may be a user terminal or a service server.
  • the present invention further provides an implementation system for actively pushing data packets, including a first host node, a second host node, a first access service node, a second access service node, a mapping forwarding plane, and a generalized forwarding plane, where:
  • the first host node is configured to send the data packet to be sent to the second host node to the first access service node where the first host node is located, where the data packet includes the identity of the second host node ;
  • the first access service node is configured to: after the data packet is received, if the location identifier corresponding to the identity of the second host node is locally queried, the location identifier is added to the data And sending, in the packet, the data packet to the generalized forwarding plane; if the location identifier corresponding to the identity of the second host node is not queried locally, the data packet is encapsulated and sent to the mapping forwarding plane. ;
  • the mapping forwarding plane is configured to: after receiving the data packet, query a location identifier corresponding to the identity identifier of the second host node, and add the location identifier to the data packet, Forwarding the data packet to a generalized forwarding plane;
  • the generalized forwarding plane is configured to forward the data message to a second access service node where the second host node is located; the second access service node is configured to send the data message to the The second host node.
  • the first access service node may be further configured to: when the location identifier corresponding to the identity of the second host node is not queried locally, initiate a mapping query request to the mapping forwarding plane; and receive the second returned by the transmitting forwarding plane After the location identifier corresponding to the identity of the host node, the mapping record of the identity identifier and the location identifier of the second host node is locally added.
  • the first host node may be further configured to carry the identity of the first host node in the data packet sent to the first access service node where the first access node is located; the first access service node may also be configured to extend to the generalized forwarding plane or mapping Before sending the data packet, the forwarding plane anonymizes the identity of the first host node carried in the data packet.
  • the first host node may be further configured to obtain the identity of the second host node by: when the second host node actively connects to the first host node, recording the identity of the second host node, or querying in the user management database Obtain the identity of the second host node.
  • the first access service node may be further configured to: determine whether the second host node is under the first access service node before adding the location identifier corresponding to the identity of the second host node that is locally queried to the data packet If yes, the data packet is directly forwarded to the second host node. If not, the location identifier is added to the data packet, and the data packet is sent to the generalized forwarding plane.
  • the first host node may be a user terminal or a service server
  • the second host node may be a user terminal as a service server.
  • the present invention supports the service server to actively push data packets to the user terminal, and does not require the user terminal to log in to the service server in advance, thereby facilitating the PUSH service (that is, the service that needs to support the PUSH function).
  • the launch is, the request.
  • the present invention can be compatible with various types of service servers and user terminals, and can implement anonymous data packet push.
  • the present invention directly uses the unique and unchanging identifier of the user to perform data packet push, and does not need to obtain the dynamically variable EID of the user through other mechanisms.
  • FIG. 1 is a schematic diagram of a network topology based on an identity identifier and a location separation architecture according to the present invention
  • FIG. 2 is a schematic diagram of related interfaces based on an identity identifier and a location separation architecture according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of an embodiment of a service server pushing a data packet to a mobile user terminal;
  • FIG. 4 is a schematic diagram of an embodiment of pushing a data packet when the service server and the user terminal are located under the same access service node.
  • the invention is based on the idea of identity identification and location separation, and proposes an identity identification and location separation architecture that facilitates the implementation of the PUSH function.
  • the core idea is to divide the network into an access layer and a core layer for each user in the network ( Including the business server and user terminal) assign a unique host identity (AID: Access Identifier), the host identity is unique, and remains unchanged during the move; there are two types of identity in the network: host identity and location RID: Routing Identifier, where the user identity can only be used at the access layer, and the location route identifier can only be used at the core layer.
  • the topology diagram of the network architecture proposed by the present invention is shown in FIG. 1.
  • the network is divided into an access network and a backbone network, and the backbone network is further divided into two logically independent functional planes: a mapping forwarding plane and a generalized forwarding plane, mainly
  • the host nodes responsible for accessing through different access networks including user terminals and service servers, which can be divided into fixed nodes, nomadic nodes and mobile nodes according to mobility, and service servers are generally fixed nodes
  • the access network is located at the edge of the backbone network and is responsible for access to all host nodes.
  • the access service node is located at the demarcation point between the backbone network and the access network, and interfaces with the access network and the backbone network respectively to provide access services for various types of host nodes, maintain host node connections, and forward host node data. There is no overlap between the access network and the backbone network in the topology relationship. Various types of host nodes Communication only needs to be done using the identity of the peer host node.
  • the host node including the mobile node, the fixed node, and the nomadic node, may be a service server or a user terminal.
  • the access network is responsible for providing and maintaining the Layer 2 link between the host node and the ASN; in the access network part, the host node uses the AID for addressing.
  • the access network may be a system such as a BSS (Base Station Subsystem), a RAN (Radio Access Network), an eNodeB (evolved Node B), or an xDSL. (Digital Subscriber Line, Digital Subscriber Line), AP (Access Point, Wireless Access Point), etc.
  • the access service node is mainly responsible for maintaining the connection relationship between the host node and the network, assigning the RID to the host node, processing the registration process, charging, authenticating, and maintaining and querying the AID-RID mapping relationship of the communication peer.
  • the ASN is responsible for encapsulating, routing, and transmitting data packets sent by the host node or the host node; when receiving the data packet sent by the host node, the ASN queries the AIDc of the communication host node according to the communication in the packet.
  • the AID-RID mapping relationship table in the CACHE finds the corresponding AIDc-RIDc mapping entry, encapsulates the RIDc in the packet header and forwards it to the generalized forwarding plane; if the corresponding AIDc-RIDc mapping entry is not found, Then, the data packet is forwarded to the mapping forwarding plane, and the process of querying the AIDc-RIDc mapping relationship is initiated to the mapping forwarding plane.
  • the ILR Identity Location Register
  • PTF Packet Transfer Function
  • the mapping forwarding plane After receiving the data packet sent by the ASN, the mapping forwarding plane performs routing according to the AID in the data packet and routes to the corresponding ILR/PTF node.
  • the data packet header encapsulates the RID information and forwards it to the generalized forwarding plane, and routes to the communication peer host through the generalized forwarding plane.
  • the main function of the generalized forwarding plane is to select and forward data packets according to the RID in the data packet.
  • the generalized forwarding plane includes a general switch router (GSR), which is mainly used for routing and forwarding data packets with the RID as the destination address.
  • GSR general switch router
  • Sl and D1 are control signaling and user data interfaces between the host node and the ASN, respectively.
  • S1 is a signaling interface for host node access management
  • D1 is an interface for data forwarding and reception.
  • the format of the data packet on the D1 interface is:
  • D3 is the external interface with the generalized forwarding plane.
  • the format of the data packet on the D3 interface is:
  • S4 is a signaling interface between the ASN and the mapping forwarding plane. It is used to query and maintain the AID-RID mapping relationship.
  • D4m is the data forwarding interface between the ASN and the mapping forwarding plane.
  • the format of the data packet on the D4m interface is:
  • the source RID corresponds to the source AID, and the RIDm is in the mapping forwarding plane connected to the ASN.
  • the routing address of the ILR/PTF which is configured on each ASN.
  • the user terminal is a mobile node as an example, and the method for implementing the service data push message to the user terminal in the network architecture is described.
  • Step 301 The user terminal (the host identity is AID1) is connected to the access service node ASN1 after being powered on, and the ASN1 allocates the location routing identifier RID1 to the user terminal, initiates a registration process to the ILR in the mapping forwarding plane, and the ILR processes the registration process of the user terminal. And save the mapping relationship of AID1-RID1 in the registration information.
  • Step 302 The service server (the host identity is AIDs) is connected to the access service node ASN2, and the ASN2 allocates the location route identifier RIDs to the service server, and initiates a registration process to the ILR in the mapping forwarding plane, and the ILR saves the AIDs-RIDs in the registration information. Mapping relations.
  • Step 303 When the service server needs to actively push the data packet to the user terminal (AID1), the service server encapsulates the data packet, sets the destination address to be AID1, and the source address is AIDs, and then sends the data packet to ASN2. .
  • the method for the service server to obtain the AID of the user terminal may be: when the user terminal actively connects to the service server to register and use a certain PUSH service, the service server may record the AID used by the user terminal for subsequent use; or, the service server passes Other ways (such as querying into a centralized user management database) get the AID of a particular user terminal.
  • Step 304 After receiving the data packet with the AID1 as the destination address (subject to the D1 interface data packet format), the ASN2 queries the local cache mapping table according to the destination AID1:
  • the RID1 information (as the destination route) and the RIDs information (as the source route) are added to the data packet, and the data packet is converted into the D3 interface packet format and sent to the generalized forwarding.
  • Plane forwarding
  • ASN2 adds mapping forwarding plane routing information in the data packet header (that is, the routing address RIDm of the ILR/PTF connected to ASN2 in the mapping forwarding plane).
  • the data packet is converted to the D4m interface packet format, and then sent to the mapping forwarding plane for processing; the mapping forwarding plane performs routing and forwarding data packets according to the destination AID1 in the received data packet, in the data packet.
  • the data packet is sent to the generalized forwarding plane for forwarding by replacing the AID1 with the RID1 or by encapsulating the RID1.
  • the ASN2 may send a mapping request to the mapping forwarding plane through the S4 interface while the data packet is encapsulated and sent to the mapping forwarding plane.
  • the mapping forwarding plane After receiving the mapping query request, the mapping forwarding plane sends the AID1-RID1 mapping relationship saved in the ILR to ASN2, and ASN2 locally adds the mapping record of AID1-RID1.
  • Step 305 after receiving the data packet, the generalized forwarding plane uses the destination RID1 in the data packet as the routing identifier, and sends the data packet to the ASN1 where the user terminal is located;
  • Step 306 After receiving the data packet sent by the generalized forwarding plane, the ASN1 strips the outer RID information (including RID1 and RIDs) and sends the data to the user terminal.
  • the user terminal moves, its identity location mapping will also change as the location changes. For example, after the user terminal moves to access the ASN3, the location route identifier assigned by the ASN3 is RID2, and the ASN3 initiates a registration process to the ILR in the mapping forwarding plane, so that the mapping relationship recorded by the ILR is updated to AID1 - RID2.
  • the service server When the data packet needs to be actively pushed to the user terminal (AID1), the service server encapsulates the data packet, and still sets the destination address to AID1, the source address to AIDs, and then sends the data packet to ASN2.
  • the ASN2, the mapping forwarding plane, and the generalized forwarding plane finally send the data to the ASN3 after the encapsulation of the data (the outer destination address is RID2 and the source address is RIDs), and the RID information of the outer layer is stripped by ASN3. After that, it is sent to the user terminal.
  • the ASN2 before the ASN2 encapsulates the data packet sent by the service server and sends it to the general forwarding plane or the mapping forwarding plane, the ASN2 can anonymize the AIDs in the data packet, so that the user terminal finally receives the datagram.
  • the source address in the text is an anonymous AID, and the real identity of the business server is hidden from the user. This feature can be applied to certain special services.
  • ASN2 anonymizes the message sent by the service server and completes it by other mechanisms (such as configuration in ASN2) is not considered in the scope of the present invention.
  • the service server and the terminal are located under different access service nodes, and if the service server and the terminal are located under the same access service node (as shown in FIG. 4, the service server and the user terminal are both located in ASN1), the service server
  • the process of actively pushing data packets to the user terminal is as follows:
  • Step 401 The user terminal (the host identity is AID1) is connected to the access service node after being powered on.
  • ASN1 and ASN1 allocate a location route identifier RID1 to the user terminal, and initiate a registration process to the ILR in the mapping forwarding plane.
  • the ILR processes the registration process of the user terminal and saves the mapping relationship of AID1-RID1 in the registration information.
  • Step 402 The service server (the host identity is AIDs) is connected to the access service node ASN1, and the ASN1 allocates the location route identifier RIDs to the service server, and initiates a registration process to the ILR in the mapping forwarding plane, and the ILR saves the AIDs-RIDs in the registration information. Mapping relations.
  • step 401 and step 402 are not limited;
  • Step 403 When the service server needs to actively push the data packet to the user terminal (AID1), the service server encapsulates the data packet, sets the destination address to be AID1, and the source address is AIDs, and then sends the data packet to ASN1.
  • Step 404 After receiving the data packet sent by the service server with the AID1 as the destination address (subject to the D1 interface data packet format), the ASN1 can query the mapping relationship of the local cache according to the destination AID1, and can find the mapping relationship of AID1-RID1. And the user terminal identified by the AID1 is located in the local ASN1. Therefore, the ASN1 directly forwards the PUSH data packet sent by the service server to the user terminal (AID1), and does not need to encapsulate and decapsulate the data packet.
  • the existing IPv4 or IPv6 user terminal and service server can be directly used for the system architecture and the PUSH function process without modifying the protocol stack.
  • the user terminal and the service server have equal status in the network architecture, and are all located in the host node of the access network, and there is no difference in the processes of accessing, registering, and transmitting and receiving data messages. Therefore, the architecture and the process of the present invention are not only applicable to the service server actively pushing data packets to the user terminal, but also applicable to the user terminal pushing data packets to the service server, or data packets between the service servers and the user terminals. Pushing is also applicable to push data packets between other host nodes in the network.
  • the present invention further provides an implementation system for actively pushing data packets, including a first host node, a second host node, a first access service node, a second access service node, a mapping forwarding plane, and a generalized forwarding plane, where:
  • the first host node is configured to send the data packet to be sent to the second host node to the first access service node where the second host node is located, where the data packet includes the identity identifier of the second host node;
  • An access service node is configured to: after receiving the data packet, if the location identifier corresponding to the identity of the second host node is locally queried, the location identifier is added to The data packet is sent to the generalized forwarding plane; if the location identifier corresponding to the identity of the second host node is not queried locally, the data packet is encapsulated and sent to Mapping the forwarding plane;
  • the mapping forwarding plane is configured to: after receiving the data packet, query a location identifier corresponding to the identity identifier of the second host node, and add the location identifier to the data packet, and forward the Data message to generalized forwarding plane;
  • the generalized forwarding plane is configured to forward the data message to a second access service node where the second host node is located; the second access service node is configured to send the data message to the The second host node.
  • the first access service node is further configured to: when the location identifier corresponding to the identity of the second host node is not queried locally, initiate a mapping query request to the mapping forwarding plane; After mapping the location identifier corresponding to the identity of the second host node returned by the forwarding plane, the mapping record of the identity identifier and the location identifier of the second host node is locally added.
  • the first host node is further configured to: carry the identity identifier of the first host node in a data packet sent by the first access service node where the first access node is located;
  • the identity of the first host node carried in the data packet is anonymized.
  • the first host node is further configured to: obtain the identity of the second host node by: when the second host node actively connects the first host node, record the identity of the second host node, or And obtaining, in the user management database, the identity of the second host node.
  • the first access service node is further configured to: after receiving the data packet, if the location identifier corresponding to the identity of the second host node is locally queried, determine whether the second host node is located If the data packet is forwarded to the second host node, if not, the location identifier is added to the data packet, and the data packet is sent.
  • the text is sent to the generalized forwarding plane.
  • the first host node is a user terminal or a service server
  • the second host node is a user terminal or a service server.
  • the present invention supports the service server to actively push data packets to the user terminal, and does not require the user terminal to log in to the service server in advance, thereby facilitating the PUSH service (that is, the service that needs to support the PUSH function).
  • the launch is, the request.
  • the present invention can be compatible with various types of service servers and user terminals, and can implement anonymous data packet push.
  • the present invention directly uses the user's unique and unchanging identifier to perform data message push without obtaining other mechanisms to obtain the user's dynamically variable EID.
  • the present invention has the following beneficial effects: facilitating the development of the PUSH service, and being compatible with the existing various types of service servers and user terminals, and enabling anonymous data packet push, which can directly use the user only,
  • the invariant identifier is used for data message push, and there is no need to use other mechanisms to obtain the user's dynamically variable EID.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明提供一种数据报文主动推送的实现方法和系统，该系统包括：第一主机节点、第二主机节点、第一接入服务节点、第二接入服务节点、映射转发平面及广义转发平面；与现有技术相比，本发明的方法和系统可以兼容现有的各类业务服务器和用户终端，可以实现匿名的数据报文推送，并且可以直接使用用户唯一的、不变的标识进行数据报文推送，而不需要通过其他机制去获取用户动态可变的EID。

Description

一种数据报文主动推送的实现方法及系统
技术领域
本发明涉及通信技术领域， 尤其涉及一种数据报文主动推送的实现方法 及系统。
背景技术
在现有因特网上部署着大量的业务服务器， 为广大因特网用户提供丰富 多彩的业务。 例如： 提供新闻资讯的 WEB服务器， 提供联网游戏的游戏服务 器， 提供海量搜索服务的搜索服务器， 等等。 这些业务的提供方式一般都是 由用户主动去获取服务， 即： 用户使用连接在因特网上的各类终端 （PC机、 个人数字助理（PDA ) 、 智能手机等， 以下简称为用户终端）主动与因特网 上的特定的业务服务器建立通讯连接， 向业务服务器发送特定的业务请求， 然后从业务服务器得到业务响应，业务响应中包含了用户所需要的各类信息。
这种服务提供方式对某些业务是不合适的。 例如： 天气预报业务， 用户 希望业务服务器在获得最新的天气预报信息后能主动推送给用户， 而不需要 等到用户主动去访问业务服务器以获取，这样会影响天气预报信息的及时性。
现有因特网对这种由业务 Λ良务器主动向用户推送信息的功能（以下简称 为 PUSH功能）是不支持的， 其原因在于因特网上的通信是用 IP地址来标识 数据报文的收发端，用户访问业务服务器时可通过 DNS功能获取业务服务器 的 IP地址， 但用户终端连接因特网时获取到的 IP地址是由因特网接入运营 商动态分配的， 若用户终端没有主动去连接业务 Λ良务器， 则业务 Λ良务器无法 获得特定用户的用户终端的 IP地址， 无法主动向用户终端发送数据 ^文（包 含特定信息 ) 。
现有因特网技术中一种折中的解决方案是： 用户终端连入因特网后， 即 向特定的业务服务器发送登录请求， 由业务服务器记录下用户终端当前所用 的 IP地址； 一旦业务服务器有需要主动向用户推送的信息， 即使用所记录的 用户终端 IP地址进行数据报文的发送。 这种方案的缺陷在于： 如果用户有着很多需要主动推送数据报文的业务 (分别由不同的业务服务器提供） ， 则需要在用户终端连入因特网后向不同 的业务服务器分别发送登录消息 （其中还涉及鉴权认证等过程） ； 一旦用户 意外掉网后重连， IP地址发生变化， 就需要重新进行登录； 如果业务服务器 在用户连网期间发生异常， 丟失用户终端 IP地址信息， 则无法使用 PUSH功
•6匕
匕。
以上问题的根本原因就在于 IP地址的语义过载缺陷。现有因特网广泛使 用的 TCP/IP ( Transmission Control Protocol/Internet Protocol, 传输控制协议 / 互联网络协议）协议中 IP地址具有双重功能， 既作为网络层的通信终端主机 网络接口在网络拓朴中的位置标识，又作为传输层主机网络接口的身份标识。
TCP/IP协议在设计之初并未考虑主机移动的情况， 一旦通信主机位置发生变 化， IP地址即可能改变， 致使身份标识也随之改变。 当通信主机移动越来越 普遍时， 这种 IP地址的语义过载缺陷日益明显。 例如， 如前所述， 特定用户 的用户终端的 IP地址是可变的，业务服务器只有随时掌握用户终端当前的 IP 地址， 才能实现 PUSH功能。
在此背景下， 业界提出了身份标识和位置分离的思路， 将 IP地址原有的 双重功能进行分离， 位置标识与身份标识釆用不同的标识， 例如， 位置标识 仍釆用 IP地址， 身份标识釆用另外定义的主机标识。 对于同一用户终端， 其 位置标识可能随接入点位置、 接入时间等因素而改变， 但其身份标识可保持 不变， 业务层只使用通信主机的身份标识建立端到端通信， 不关心位置标识 的变化。 这样， 业务服务器只要获知特定用户的用户终端的身份标识， 即可 向其推送数据报文。 数据报文如何送到正确的用户终端所在位置， 由身份标 识和位置分离的具体解决方案来实现。
现有技术中有关身份标识和位置分离的解决方案主要有两类， 一类^^ 于主机的实现方案， 另一类是基于路由器的实现方案， 每类实现方案中又有 相关的多种技术进行支持。 在基于主机的实现方案中现有的主要协议是主机 标识协议（ Host Identity Protocol , HIP ) , 在基于路由器的实现方案中现有的 主要协议是位置身份分离协议（Locator/ID Separation Protocol, LISP )等。
HIP是一种主机移动性关联协议， HIP将 IP地址分离为端标识与位置标 识。 HIP的基本思想是在第三层网络层和第四层传输层之间引入了 3.5层的主 机标识层（Host Identity Layer, HIL ) , 即在域名空间和 IP地址空间之间引 入了主机标识（ Host Identity , HI ) 空间。 主机标识层将原来紧密耦合的传输 层和网络层分开， IP地址不再扮演标识主机的角色， 它只负责数据报文的路 由转发， 即仅用作定位符， 主机名称由主机标识符来表示。 主机标识层在逻 辑上位于网络层与传输层之间， 传输层使用传输层标识符， 由主机标识层完 成数据报文中的主机标识符和 IP地址转换。 网络层对于传输层是屏蔽的， 网 络层的任何变化（例如， 在通信过程中主机 IP地址的变化）不会影响传输层 链路， 除非服务质量发生变化。
这样， 传输层的连接建立在主机标识符之上， IP地址只能被用于网络层 路由， 而不再用于标识主机身份。 HIP 的关键思想就是断开网络层和传输层 的紧密耦合， 使应用层和传输层的连接不受 IP地址变化的影响。 当 IP地址 在一个连接中变化时， HI保持不变， 由此保证了连接的不中断。 在支持 HIP 的主机中， IP地址只是用于路由和寻址功能， 而 HI则用来标识一个连接所对 应的终端主机， 代替连接套接字中所使用的 IP地址。
HIP是一种主机协议， 其主要问题是： 部署的前提是需要参与通信的终 端主机 (包括用户终端和业务服务器）都同步支持 HIP协议， 需要对终端主 机甚至上层应用做较大改动。 另外， HIP协议无法实现匿名通信。
LISP重用了路由技术， 对现有的路由拓朴结构有了一定的改变， 结合现 有的传送网， 利用最小的改造优化了现有的路由传送技术。 主机使用 IP地址 (在 LISP系统中称为端标识 (EID) )来跟踪套接字 (socket), 建立连接、 发送 和接收数据报文。 路由器基于 IP 目的地址（在 LISP 系统中称为路由位置 (RLOCs) )传递数据报文。
在 LISP系统中引入了隧道路由， ITR (隧道入口路由器）为隧道的起始 端， ETR (隧道出口路由器） 为隧道的终结端。 在主机发出数据报文后， 由 ITR封装为 LISP数据报文，并且在 LISP数据报文最终传递到目的地前由 ETR 对 LISP数据报文进行解封装。 在 LISP数据报文中 "外层报头" 的 IP地址是 RLOCs。 在两个网络的主机之间进行端到端的包交换过程中， ITR为每个包 封装一个新 LISP头， 并执行 EID-to-RLOC查找以确定到 ETR的路由路径， ETR以 RLOC作为自身的一个地址。 ITR与 ETR之间的核心路由器只负责 RLOC的路由寻址， 不必关心 EID的路由。
LISP减少了核心路由器的路由表记录项数目， 主要解决的是网络规模过 大的问题， 目前还没有解决移动性的问题， 即， 同一个主机在发生跨子网的 移动时， 其 EID是可能发生变化的， EID不足以作为用户终端移动情况下的 身份标识。 因此， 对于 PUSH功能， LISP存在与现有因特网相类似的问题， 即业务服务器需要通过其他手段获取用户终端当前的 EID。
发明内容
本发明提供一种数据报文主动推送的实现方法及系统， 解决业务服务器 主动向用户终端推送数据报文的问题。 为了解决上述问题， 本发明提供了一种数据报文主动推送的实现方法， 包括：
第一主机节点将需推送给第二主机节点的数据报文发送给该第一主机节 点所在的第一接入服务节点， 所述数据报文中包含所述第二主机节点的身份 标识；
所述第一接入服务节点收到所述数据报文后， 如果在本地查询到所述第 二主机节点的身份标识对应的位置标识， 则将所述位置标识添加到所述数据 报文中， 将所述数据报文发送至广义转发平面； 如果在本地没有查询到所述 第二主机节点的身份标识对应的位置标识， 则将所述数据报文封装后发送至 映射转发平面， 所述映射转发平面收到所述数据报文后， 查询所述第二主机 节点的身份标识对应的位置标识，并将所述位置标识添加到所述数据报文中， 转发所述数据报文至广义转发平面； 以及
所述广义转发平面将所述数据报文转发至所述第二主机节点所在的第二 接入服务节点， 所述第二接入服务节点将所述数据报文发送给所述第二主机 节点。
上述方法还可包括： 第一接入服务节点在本地没有查询到第二主机节点 的身份标识对应的位置标识时， 向映射转发平面发起映射查询请求； 并在收 到映射转发平面返回的第二主机节点的身份标识对应的位置标识时后， 在本 地增加第二主机节点的身份标识与位置标识的映射记录。
第一主机节点向其所在的第一接入服务节点发送的数据报文中还可携带 所述第一主机节点的身份标识； 该方法还可包括： 第一接入服务节点向广义 转发平面或者映射转发平面发送数据报文前， 还对数据报文中携带的第一主 机节点的身份标识进行匿名化处理。
该方法还可包括： 第一主机节点通过如下方式获取第二主机节点的身份 标识： 在第二主机节点主动连接第一主机节点时， 记录第二主机节点的身份 标识， 或者， 在用户管理数据库中查询获述第二主机节点的身份标识。
该方法还可包括：第一接入服务节点在将位置标识添加到数据报文之前， 判断第二主机节点是否在第一接入服务节点下， 如果是， 则将数据报文转发 给第二主机节点， 如果不是， 才将位置标识添加到数据报文中， 将数据报文 发送至广义转发平面。
第一主机节点可以为用户终端或业务服务器， 第二主机节点可以为用户 终端或业务 ^良务器。
本发明还提供一种数据报文主动推送的实现系统， 包括第一主机节点、 第二主机节点、 第一接入服务节点、 第二接入服务节点、 映射转发平面及广 义转发平面， 其中：
第一主机节点设置成将需推送给第二主机节点的数据报文发送给该第一 主机节点所在的第一接入服务节点， 所述数据报文中包含所述第二主机节点 的身份标识；
所述第一接入服务节点设置成： 收到所述数据报文后， 如果在本地查询 到所述第二主机节点的身份标识对应的位置标识， 则将所述位置标识添加到 所述数据报文中， 将所述数据报文发送至广义转发平面； 如果在本地没有查 询到所述第二主机节点的身份标识对应的位置标识， 则将所述数据报文封装 后发送至映射转发平面；
所述映射转发平面设置成： 收到所述数据报文后， 查询所述第二主机节 点的身份标识对应的位置标识， 并将所述位置标识添加到所述数据报文中， 转发所述数据报文至广义转发平面；
所述广义转发平面设置成将所述数据报文转发至所述第二主机节点所在 的第二接入服务节点； 所述第二接入服务节点设置成将所述数据报文发送给所述第二主机节 点。
第一接入服务节点还可设置成： 在本地没有查询到第二主机节点的身份 标识对应的位置标识时， 向映射转发平面发起映射查询请求； 并在收到所射 转发平面返回的第二主机节点的身份标识对应的位置标识后， 在本地增加第 二主机节点的身份标识与位置标识的映射记录。
第一主机节点还可设置成在向其所在的第一接入服务节点发送的数据报 文中携带第一主机节点的身份标识； 第一接入服务节点还可设置成向广义转 发平面或者映射转发平面发送数据报文前， 对数据报文中携带的第一主机节 点的身份标识进行匿名化处理。
第一主机节点还可设置成通过如下方式获取第二主机节点的身份标识： 在第二主机节点主动连接第一主机节点时， 记录第二主机节点的身份标识， 或者， 在用户管理数据库中查询获得第二主机节点的身份标识。
第一接入服务节点还可设置成： 在将在本地查询到的第二主机节点的身 份标识对应的位置标识添加到数据报文之前， 判断第二主机节点是否在第一 接入服务节点下， 如果是， 直接将该数据报文转发给第二主机节点， 如果不 是， 才将该位置标识添加到数据报文中， 将数据报文发送至广义转发平面。
第一主机节点可以为用户终端或业务服务器， 第二主机节点可以为用户 终端为业务服务器。
与现有技术相比， 上述实施方案具有如下有益效果：
与现有因特网技术相比， 本发明支持业务服务器主动向用户终端推送数 据报文， 而不需要用户终端预先向业务服务器进行登录， 从而便于 PUSH类 业务（即需要支持 PUSH功能才能开展的业务） 的开展。
与现有的 HIP技术相比， 本发明可以兼容现有的各类业务服务器和用户 终端， 并且可以实现匿名的数据报文推送。 与现有的 LISP技术相比， 本发明直接使用用户唯一的、 不变的标识即可 进行数据报文推送， 而不需要通过其他机制去获取用户动态可变的 EID。
附图概述
图 1为本发明基于身份标识和位置分离架构的网络拓朴示意图； 图 2 为本发明实施例的基于身份标识和位置分离架构的相关接口示意 图；
图 3为业务服务器向移动的用户终端推送数据报文的实施例示意图； 图 4为业务服务器与用户终端位于同一接入服务节点下时推送数据报文 的实施例示意图。
本发明的较佳实施方式
下面将结合附图及实施例对本发明进行更详细的说明。
本发明基于身份标识和位置分离的思想， 提出一种便于 PUSH功能实现 的身份标识和位置分离架构， 其核心思想是： 将网络划分为接入层和核心层， 为网络中的每个用户 （包括业务服务器和用户终端）分配唯一的主机身份标 识（AID: Access Identifier ) , 该主机身份标识具有唯一性， 在移动过程中始 终保持不变； 网络中有两种标识类型： 主机身份标识和位置路由标识（RID: Routing Identifier ) , 其中用户身份标识只能在接入层使用， 位置路由标识只 能在核心层使用。
本发明提出的网络架构的拓朴示意图如图 1所示， 将网络划分为接入网 和骨干网， 骨干网又分为两个逻辑上独立的功能平面： 映射转发平面和广义 转发平面， 主要负责通过不同的接入网接入的主机节点 （包括用户终端和业 务服务器， 按移动能力可分为固定节点、 游牧节点和移动节点， 业务服务器 一般为固定节点） 的路由。 接入网位于骨干网的边缘， 负责所有主机节点的 接入。 接入服务节点 （ASN )位于骨干网和接入网的分界点， 分别与接入网 及骨干网接口， 为各类主机节点提供接入服务， 维护主机节点连接， 转发主 机节点数据。 接入网与骨干网在拓朴关系上没有重叠。 各类主机节点间进行 通信只需使用对端主机节点的身份标识进行。
如图 1所示， 该基于网络的身份标识和位置分离架构中， 涉及的主要网 元和功能实体如下：
主机节点， 包括移动节点、 固定节点及游牧节点等， 可以是业务服务器 或用户终端。
接入网， 负责提供并维护主机节点到 ASN之间的二层链路； 在接入网部 分，主机节点使用 AID进行寻址。接入网可以 ^^站系统，如 BSS( Base Station Subsystem,基站子系统）、 RAN( Radio Access Network,无线接入网 )、 eNodeB ( evolved Node B,演进的节点 B )等，也可以是 xDSL( Digital Subscriber Line, 数字用户线） 、 AP ( Access Point, 无线访问接入点）等。
接入服务节点 （ASN )主要负责维护主机节点与网络的连接关系、 为主 机节点分配 RID、 处理登记注册流程、 计费、 鉴权、 以及维护和查询通讯对 端的 AID-RID映射关系。
具体地， ASN负责封装、 路由并转发送达主机节点或主机节点发出的数 据报文； ASN在收到主机节点发来的数据报文时， 根据报文中的通信对端主 机节点的 AIDc查询 CACHE (緩存 )中的 AID-RID映射关系表， 查到对应的 AIDc-RIDc映射条目，将 RIDc封装在报文头部并转发到广义转发平面； 如果 没有查到对应的 AIDc-RIDc映射条目， 则将数据报文转发到映射转发平面， 并向映射转发平面发起查询 AIDc-RIDc映射关系的流程。
映射转发平面中， ILR ( Identity Location Register, 身份位置寄存器） 负 责维护及保存网络中用户的 AID-RID映射关系， 实现主机节点的登记注册功 能， 处理通信对端主机节点的位置查询流程， 并通过数据配置或路由同步的 方式形成 AID的路由表。 PTF ( Packet Transfer Function, 分组转发功能） 负 责转发以 AID标识为目的地址的数据报文。 PTF与 ILR共享网络中用户的 AID-RID映射关系， 两者可以位于同一物理实体。 映射转发平面在收到 ASN 送达的数据报文后，根据数据报文中的 AID进行选路，路由到对应的 ILR/PTF 节点， PTF节点在查到目的 AID-RID的映射关系后，在数据报文头部封装 RID 信息并转发到广义转发平面内，通过广义转发平面路由到通信对端主机节点。 广义转发平面的主要功能是根据数据报文中的 RID进行选路和转发数据 报文。 其中， 广义转发平面中包括通用交换路由器（ General Switch Router, 简称 GSR )主要用于路由并转发以 RID为目的地址的数据报文。
上述基于网络的身份标识和位置分离架构的相关接口如图 2所示， Sl、 Dl分别是主机节点与 ASN之间的控制信令、 用户数据接口。 S1是用于主机 节点接入管理的信令接口， D1是数据转发和接收的接口。
D1接口的数据报文格式为：
Figure imgf000011_0001
D3是与广义转发平面对外的接口， D3接口的数据报文格式为:
Figure imgf000011_0002
S4是 ASN与映射转发平面间的信令接口，主要用于查询和维护 AID-RID 映射关系。
D4m是 ASN与映射转发平面间的数据转发接口， D4m接口的数据报文 格式为：
Figure imgf000011_0003
其中， 源 RID对应源 AID, RIDm是与 ASN连接的映射转发平面中
ILR/PTF的路由地址， 该路由地址在每个 ASN上进行配置。
图 3以用户终端为移动节点为例， 描述在上述网络架构下业务 ^良务器主 动向用户终端推送数据报文的实现方法， 包括：
步骤 301 , 用户终端 （主机身份标识为 AID1 )开机后连接接入服务节点 ASNl , ASN1为用户终端分配位置路由标识 RID1 , 向映射转发平面中的 ILR 发起注册流程， ILR处理用户终端的注册流程，并保存注册信息中 AID1-RID1 的映射关系。 步骤 302,业务服务器（主机身份标识为 AIDs )连接接入服务节点 ASN2, ASN2为业务服务器分配位置路由标识 RIDs, 并向映射转发平面中的 ILR发 起注册流程， ILR保存注册信息中 AIDs-RIDs的映射关系。
其中， 步骤 301和步骤 302的先后顺序不限；
步骤 303 , 当业务服务器需要主动向用户终端（ AID1 )推送数据报文时， 业务服务器对该数据报文进行封装， 设置目的地址为 AID1 , 源地址为 AIDs, 然后将此数据报文发送给 ASN2。
业务服务器获得用户终端的 AID的方法可以是： 在用户终端主动连接业 务服务器以注册使用某项 PUSH类业务时， 业务服务器可以记录下用户终端 所使用的 AID以备后续使用； 或者， 业务服务器通过其他途径（如到某个集 中的用户管理数据库中查询）获取特定用户终端的 AID。
步骤 304, ASN2收到业务服务器发出的以 AID1为目的地址的数据报文 (遵循 D1接口数据报文格式）后， 根据目的 AID1查询本地緩存的映射关系 表：
如果查到 AID1-RID1的映射关系， 则在数据报文中增加 RID1信息 （作 为目的路由）和 RIDs信息（作为源路由） ， 将数据报文转换为 D3接口报文 格式， 并发送至广义转发平面进行转发；
如果在本地緩存的映射关系表中没有查到 AID1-RID1映射关系，则 ASN2 在数据报文头部增加映射转发平面路由信息 （即映射转发平面内与 ASN2连 接的 ILR/PTF的路由地址 RIDm ) ,将数据报文转换为 D4m接口报文格式后， 发送给映射转发平面进行处理； 映射转发平面根据接收到的数据报文中的目 的 AID1进行选路和转发数据报文，在数据报文中以 RID1替换 AID1的方式、 或者以封装 RID1的方式， 将数据报文发送给广义转发平面进行转发；
其中， ASN2如果在本地緩存的映射关系表中没有查到 AID1-RID1映射 关系， 可以在将数据报文封装发送给映射转发平面的同时， 通过 S4接口向映 射转发平面发起映射查询请求。映射转发平面在收到映射查询请求后，将 ILR 中所保存的 AID1-RID1 映射关系发送给 ASN2 , 供 ASN2 在本地增加 AID 1 -RID 1的映射记录。 步骤 305, 广义转发平面收到数据报文后， 以数据报文中的目的 RID1为 路由标识， 将数据报文发送至用户终端所在的 ASN1；
步骤 306, ASN1收到广义转发平面发送的数据报文后， 剥离外层的 RID 信息 （包括 RID1和 RIDs )后， 发送给用户终端。
此后， 如果用户终端发生移动， 其身份位置映射关系也将随着位置的变 化而变化。 例如， 用户终端移动后接入到 ASN3 , ASN3为其分配的位置路由 标识为 RID2 , ASN3向映射转发平面中的 ILR发起注册流程 , 使得 ILR所记 录的映射关系更新为 AID 1 -RID2。
在需要主动向用户终端（AID1 )推送数据报文时， 业务服务器对数据报 文进行封装， 仍然设置目的地址为 AID1 , 源地址为 AIDs, 然后将此数据报 文发送给 ASN2。
与前面所述步骤类似， ASN2、 映射转发平面、 广义转发平面最终将此数 据 "^文封装后 （外层目的地址为 RID2, 源地址为 RIDs )发送至 ASN3 , 由 ASN3剥离外层的 RID信息后， 发送给用户终端。
在上述过程中， ASN2 在封装业务服务器发出的数据报文并向广义转发 平面或映射转发平面发送前，可以对数据报文中的 AIDs进行匿名化处理，这 样， 用户终端最终收到的数据报文中源地址是匿名的 AID, 业务服务器真实 身份对用户是隐藏的。 此功能可应用于某些特殊业务。
ASN2是否对业务服务器发出的报文进行匿名处理， 由其他机制完成 (如 在 ASN2进行配置） ， 不在本发明的考虑范围之内。
上述实施例中， 业务服务器和终端位于不同接入服务节点下， 若业务服 务器和终端位于同一个接入服务节点下 （如图 4所示， 业务服务器和用户终 端均位于 ASN1 ) ， 则业务服务器主动向用户终端推送数据报文的实现流程 下：
步骤 401 , 用户终端 （主机身份标识为 AID1 )开机后连接接入服务节点
ASNl , ASN1为用户终端分配位置路由标识 RID1 , 向映射转发平面中的 ILR 发起注册流程， ILR处理用户终端的注册流程，并保存注册信息中 AID1-RID1 的映射关系。 步骤 402,业务服务器（主机身份标识为 AIDs )连接接入服务节点 ASN1 , ASN1为业务服务器分配位置路由标识 RIDs, 并向映射转发平面中的 ILR发 起注册流程， ILR保存注册信息中 AIDs-RIDs的映射关系。
其中， 步骤 401和步骤 402的先后顺序不限；
步骤 403 , 当业务服务器需要主动向用户终端（AID1 )推送数据报文时， 业务服务器对数据报文进行封装， 设置目的地址为 AID1 , 源地址为 AIDs, 然后将此数据报文发送给 ASN1。
步骤 404, ASN1收到业务服务器发出的以 AID1为目的地址的数据报文 (遵循 D1接口数据报文格式）后， 根据目的 AID1查询本地緩存的映射关系 表， 可以查到 AID1-RID1的映射关系， 并且可以判断出 AID1所标识的用户 终端就在本 ASN1下， 于是， ASN1直接将业务服务器发出的 PUSH数据报 文转发给用户终端 （AID1 ) , 无需进行数据报文的封装与解封装。
在上述过程中， 若 AID釆用 IPv4地址或 IPv6地址格式， 则现有的 IPv4 或 IPv6 的用户终端和业务服务器可以直接用于此系统架构和 PUSH功能流 程， 而无需对协议栈进行修改。
本发明中， 用户终端和业务服务器在网络架构中的地位是平等的， 都是 位于接入网的主机节点， 在接入、 注册、 收发数据报文等流程中并无差异。 因此， 本发明的架构和流程， 不仅适用于业务服务器主动向用户终端推送数 据报文， 也适用于用户终端向业务服务器推送数据报文， 或业务服务器之间、 用户终端之间的数据报文推送， 也适用于网络中其它主机节点之间推送数据 报文。
本发明还提供一种数据报文主动推送的实现系统， 包括第一主机节点、 第二主机节点、 第一接入服务节点、 第二接入服务节点、 映射转发平面及广 义转发平面， 其中：
第一主机节点设置成将需推送给第二主机节点的数据报文发送给其所在 的第一接入服务节点， 所述数据报文中包含所述第二主机节点的身份标识； 所述第一接入服务节点设置成： 收到所述数据报文后， 如果在本地查询 到所述第二主机节点的身份标识对应的位置标识， 则将所述位置标识添加到 所述数据报文中， 将所述数据报文发送至广义转发平面； 如果在本地没有查 询到所述第二主机节点的身份标识对应的位置标识， 则将所述数据报文封装 后发送至映射转发平面；
所述映射转发平面设置成： 收到所述数据报文后， 查询所述第二主机节 点的身份标识对应的位置标识， 并将所述位置标识添加到所述数据报文中， 转发所述数据报文至广义转发平面；
所述广义转发平面设置成将所述数据报文转发至所述第二主机节点所在 的第二接入服务节点； 所述第二接入服务节点设置成将所述数据报文发送给所述第二主机节 点。
其中， 所述第一接入服务节点还设置成： 在本地没有查询到所述第二主 机节点的身份标识对应的位置标识时， 向所述映射转发平面发起映射查询请 求； 并在收到所述映射转发平面返回的所述第二主机节点的身份标识对应的 位置标识后， 在本地增加所述第二主机节点的身份标识与位置标识的映射记 录。
其中， 所述第一主机节点还设置成： 在向其所在的第一接入服务节点发 送的数据报文中携带所述第一主机节点的身份标识； 所述第一接入服务节点 所述数据报文中携带的所述第一主机节点的身份标识进行匿名化处理。
所述第一主机节点还设置成通过如下方式获取所述第二主机节点的身份 标识： 在第二主机节点主动连接所述第一主机节点时， 记录所述第二主机节 点的身份标识， 或者， 在用户管理数据库中查询获得所述第二主机节点的身 份标识。
所述第一接入服务节点还设置成： 收到所述数据报文后， 如果在本地查 询到所述第二主机节点的身份标识对应的位置标识， 判断所述第二主机节点 是否在所述第一接入服务节点下， 如果是， 将所述数据报文转发给所述第二 主机节点， 如果不是， 才将所述位置标识添加到所述数据报文中， 将所述数 据报文发送至广义转发平面。 所述第一主机节点为用户终端或业务服务器， 所述第二主机节点为用户 终端或业务服务器。
与现有技术相比， 上述实施方案具有如下有益效果：
与现有因特网技术相比， 本发明支持业务服务器主动向用户终端推送数 据报文， 而不需要用户终端预先向业务服务器进行登录， 从而便于 PUSH类 业务（即需要支持 PUSH功能才能开展的业务） 的开展。
与现有的 HIP技术相比， 本发明可以兼容现有的各类业务服务器和用户 终端， 并且可以实现匿名的数据报文推送。
与现有的 LISP技术相比， 本发明直接使用用户唯一的、 不变的标识即可 进行数据报文推送， 而不需要通过其他机制去获取用户动态可变的 EID。
工业实用性
与现有技术相比， 本发明具有以下有益效果： 便于 PUSH类业务的开展， 可以兼容现有的各类业务服务器和用户终端，可以实现匿名的数据报文推送， 可以直接使用用户唯一的、 不变的标识进行数据报文推送， 而不需要通过其 他机制去获取用户动态可变的 EID。

Claims

权 利 要 求 书
1、 一种数据报文主动推送的实现方法， 包括：
第一主机节点将需推送给第二主机节点的数据报文发送给该第一主机节 点所在的第一接入服务节点， 所述数据报文中包含所述第二主机节点的身份 标识；
所述第一接入服务节点收到所述数据报文后， 如果在本地查询到所述第 二主机节点的身份标识对应的位置标识， 则将查询到的位置标识添加到所述 数据报文中， 将所述数据报文发送至广义转发平面； 如果在本地没有查询到 所述第二主机节点的身份标识对应的位置标识， 则将所述数据报文封装后发 送至映射转发平面， 所述映射转发平面收到所述数据报文后， 查询所述第二 主机节点的身份标识对应的位置标识， 并将所述位置标识添加到所述数据报 文中， 转发所述数据 文至广义转发平面； 以及
所述广义转发平面将所述数据报文转发至所述第二主机节点所在的第二 接入服务节点， 所述第二接入服务节点将所述数据报文发送给所述第二主机 节点。
2、 如权利要求 1所述的方法， 还包括：
所述第一接入服务节点在本地没有查询到所述第二主机节点的身份标识 对应的位置标识时， 向所述映射转发平面发起映射查询请求； 并在收到所述 映射转发平面返回的所述第二主机节点的身份标识对应的位置标识时后， 在 本地增加所述第二主机节点的身份标识与位置标识的映射记录。
3、 如权利要求 1所述的方法， 其中，
所述第一主机节点向其所在的第一接入服务节点发送的数据报文中还携 带所述第一主机节点的身份标识；
所述方法还包括： 所述第一接入服务节点向所述广义转发平面或者映射 转发平面发送所述数据报文前， 对所述数据报文中携带的所述第一主机节点 的身份标识进行匿名化处理。
4、 如权利要求 1所述的方法， 还包括：
所述第一主机节点通过如下方式获取所述第二主机节点的身份标识： 在 第二主机节点主动连接所述第一主机节点时， 记录所述第二主机节点的身份 标识， 或者， 在用户管理数据库中查询获得所述第二主机节点的身份标识。
5、如权利要求 1所述的方法， 其在第一接入服务节点将查询到的位置标 识添加到所述数据报文中的步骤之前还包括： 所述第一接入服务节点判断所 述第二主机节点是否在所述第一接入服务节点下， 如果是， 则直接将所述数 据报文转发给所述第二主机节点， 如果不是， 才将所述位置标识添加到所述 数据报文中， 将所述数据报文发送至广义转发平面。
6、 如权利要求 1至 5任一所述的方法， 其中，
所述第一主机节点为用户终端或业务服务器， 所述第二主机节点为用户 终端或业务 ^良务器。
7、 一种数据报文主动推送的实现系统， 包括第一主机节点、 第二主机节 点、 第一接入服务节点、 第二接入服务节点、 映射转发平面及广义转发平面， 其中：
所述第一主机节点设置成将需推送给第二主机节点的数据报文发送给该 第一主机节点所在的第一接入服务节点， 所述数据报文中包含所述第二主机 节点的身份标识；
所述第一接入服务节点设置成： 收到所述数据报文后， 如果在本地查询 到所述第二主机节点的身份标识对应的位置标识， 则将所述位置标识添加到 所述数据报文中， 将所述数据报文发送至广义转发平面； 如果在本地没有查 询到所述第二主机节点的身份标识对应的位置标识， 则将所述数据报文封装 后发送至映射转发平面；
所述映射转发平面设置成： 收到所述数据报文后， 查询所述第二主机节 点的身份标识对应的位置标识， 并将所述位置标识添加到所述数据报文中， 转发所述数据报文至广义转发平面；
所述广义转发平面设置成将所述数据报文转发至所述第二主机节点所在 的第二接入服务节点； 所述第二接入服务节点设置成将所述数据报文发送给所述第二主机节 点。
8、 如权利要求 7所述的系统， 其中，
所述第一接入服务节点还设置成： 在本地没有查询到所述第二主机节点 的身份标识对应的位置标识时， 向所述映射转发平面发起映射查询请求； 并 在收到所述映射转发平面返回的所述第二主机节点的身份标识对应的位置标 识后， 在本地增加所述第二主机节点的身份标识与位置标识的映射记录。
9、 如权利要求 7所述的系统， 其中，
所述第一主机节点还设置成在向其所在的第一接入服务节点发送的数据 报文中携带所述第一主机节点的身份标识；
所述第一接入服务节点还设置成在向所述广义转发平面或者映射转发平 面发送所述数据报文前， 对所述数据报文中携带的所述第一主机节点的身份 标识进行匿名化处理。
10、 如权利要求 7所述的系统， 其中，
所述第一主机节点还设置成通过如下方式获取所述第二主机节点的身份 标识： 在第二主机节点主动连接所述第一主机节点时， 记录所述第二主机节 点的身份标识， 或者， 在用户管理数据库中查询获得所述第二主机节点的身 份标识。
11、 如权利要求 7所述的系统， 其中，
所述第一接入服务节点还设置成： 在将在本地查询到的第二主机节点的 身份标识对应的位置标识添加到所述数据报文之前， 判断所述第二主机节点 是否在所述第一接入服务节点下， 如果是， 直接将所述数据报文转发给所述 第二主机节点， 如果不是， 才将所述位置标识添加到所述数据报文中， 将所 述数据报文发送至广义转发平面。
12、 如权利要求 7至 11任一所述的系统， 其中， 所述第一主机节点为用 户终端或业务服务器， 所述第二主机节点为用户终端为业务服务器。
PCT/CN2010/076902 2009-10-10 2010-09-14 一种数据报文主动推送的实现方法及系统 WO2011041972A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910205327.1 2009-10-10
CN 200910205327 CN102045655B (zh) 2009-10-10 2009-10-10 一种数据报文主动推送的实现方法及系统

Publications (1)

Publication Number Publication Date
WO2011041972A1 true WO2011041972A1 (zh) 2011-04-14

Family

ID=43856376

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/076902 WO2011041972A1 (zh) 2009-10-10 2010-09-14 一种数据报文主动推送的实现方法及系统

Country Status (2)

Country Link
CN (1) CN102045655B (zh)
WO (1) WO2011041972A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103108002B (zh) * 2011-11-10 2016-08-24 阿里巴巴集团控股有限公司 一种数据推送方法、系统及装置
CN103023805A (zh) * 2012-11-22 2013-04-03 北京航空航天大学 一种MapReduce系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000024209A1 (en) * 1998-10-19 2000-04-27 Nokia Networks Oy Mechanism for network-initiated information transfer
WO2001010091A1 (en) * 1999-07-30 2001-02-08 Telefonaktiebolaget Lm Ericsson (Publ) System, method, and apparatus for pushing data in a direct digital call environment
CN1647559A (zh) * 2002-04-08 2005-07-27 思科技术公司 用于在因特网协议网络环境中推送数据的系统和方法
CN101026634A (zh) * 2007-01-24 2007-08-29 中兴通讯股份有限公司 一种消息推送系统和方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000024209A1 (en) * 1998-10-19 2000-04-27 Nokia Networks Oy Mechanism for network-initiated information transfer
WO2001010091A1 (en) * 1999-07-30 2001-02-08 Telefonaktiebolaget Lm Ericsson (Publ) System, method, and apparatus for pushing data in a direct digital call environment
CN1647559A (zh) * 2002-04-08 2005-07-27 思科技术公司 用于在因特网协议网络环境中推送数据的系统和方法
CN101026634A (zh) * 2007-01-24 2007-08-29 中兴通讯股份有限公司 一种消息推送系统和方法

Also Published As

Publication number Publication date
CN102045655A (zh) 2011-05-04
CN102045655B (zh) 2013-09-11

Similar Documents

Publication Publication Date Title
US9622072B2 (en) Communication method, method for forwarding data message during the communication process and communication node thereof
EP2477428B1 (en) Method for anonymous communication, method for registration, method and system for transmitting and receiving information
US7616615B2 (en) Packet forwarding apparatus for connecting mobile terminal to ISP network
JP5335886B2 (ja) ローカル・ネットワーク間でデータ・パケットを通信するための方法および装置
US8711749B2 (en) Information obtaining and notification, data message forwarding and handover method and access node
US9407495B2 (en) Combining locally addressed devices and wide area network (WAN) addressed devices on a single network
US20120177052A1 (en) User-oriented communication method, route registration method and device, and communication system
WO2011124132A1 (zh) 数据通信系统及方法
KR101381701B1 (ko) 데이터 메시지 처리 방법, 시스템 및 접속 서비스 노드
WO2011035615A1 (zh) 一种数据传输方法、系统及装置
WO2011041970A1 (zh) 一种支持数据报文主动推送能力的实现方法及系统
EP2466815B1 (en) Method and system for initiating forwarding of communicaiton, information and data message and for routing configuration
WO2011041969A1 (zh) 一种支持数据报文主动推送能力的实现方法及系统
WO2011044807A1 (zh) 一种匿名通信的注册、通信方法及数据报文的收发系统
KR20140117987A (ko) 이동 통신 네트워크 및 이를 이용한 통신 방법
WO2011041972A1 (zh) 一种数据报文主动推送的实现方法及系统
WO2011124121A1 (zh) 网间数据通讯系统及方法
US20200137726A1 (en) Communications device and communication method
WO2012088828A1 (zh) 表维护方法、系统和接入网关路由器
WO2011041971A1 (zh) 一种支持数据报文主动推送能力的实现方法及系统
WO2012083685A1 (zh) 一种提高映射路由表使用效率的方法及系统
KR101529175B1 (ko) 비캡슐화 패킷 전송 방식에서의 이동성 관리방법 및 이동성 관리 시스템
WO2013053293A1 (zh) 一种标识网与传统网络互联互通的方法、asr及isr
WO2013026292A1 (zh) 基于身份位置分离网络内服务器通讯方法、系统和服务器
WO2007013628A1 (ja) データユニット転送装置及び位置情報管理装置並びにアドレス配布装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10821581

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10821581

Country of ref document: EP

Kind code of ref document: A1