WO2012097527A1 - 一种连接重建方法、设备和系统 - Google Patents

一种连接重建方法、设备和系统 Download PDF

Info

Publication number
WO2012097527A1
WO2012097527A1 PCT/CN2011/070502 CN2011070502W WO2012097527A1 WO 2012097527 A1 WO2012097527 A1 WO 2012097527A1 CN 2011070502 W CN2011070502 W CN 2011070502W WO 2012097527 A1 WO2012097527 A1 WO 2012097527A1
Authority
WO
WIPO (PCT)
Prior art keywords
gateway
connection
message
identifier
user
Prior art date
Application number
PCT/CN2011/070502
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 华为技术有限公司
Priority to CN201180000657.2A priority Critical patent/CN102860116B/zh
Priority to PCT/CN2011/070502 priority patent/WO2012097527A1/zh
Publication of WO2012097527A1 publication Critical patent/WO2012097527A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/19Connection re-establishment

Definitions

  • the present invention relates to the field of mobile communication network technologies, and in particular, to a connection reconstruction method, device, and system. Background technique
  • the logical architecture of the next generation mobile communication network is as shown in FIG. 1.
  • the user terminal 11 is accessed through the local wireless access network 12, and the mobility management network element 13 is responsible for location management, connection management, security authentication, and gateway selection of the mobile user terminal 11.
  • the service gateway 14 is a local access gateway of the user terminal 11, and is responsible for access technology related connection management and data forwarding.
  • the data gateway 15 is a gateway for the user terminal to access the external data network.
  • the data gateway needs to connect to the downlink channel of the data packet by the corresponding PDN (Packet Data Network) connection context or bearer context, such as which tunnel to send the packet to, which service gateway, if The data gateway is reset. After the reset, the data gateway cannot know the packet forwarding channel because the PDN connection context or bearer context is lost. After receiving the downlink data packet of the user terminal, the data gateway can only discard the data packet.
  • PDN Packet Data Network
  • the serving gateway After the service gateway learns that the data gateway is reset, the serving gateway notifies the affected mobility management network element to delete the PDN connection context related to the serving gateway and the reset data gateway. After receiving the message of the serving gateway, the mobility management network element notifies the user terminal to re-establish the PDN connection or reattach. In the process of establishing or attaching a PDN connection initiated by the user terminal, the mobility management network element re-establishes the PDN connection on the core network side, where the core network side includes a service gateway and a data gateway. Re-establish PDN After the connection, the service corresponding to the PDN connection of the user terminal can be performed in the network.
  • the mobile management network element learns that the data gateway reset notifies the user terminal that the establishment of the affected PDN connection or re-attachment mechanism depends on the time when the service gateway learns the data gateway reset, and the service gateway learns that the data gateway is reset and scans the internal affected PDN connection. Time, which may take up to half an hour or more.
  • the service gateway reset is similar. Before the user context is re-established, the downlink packets received on the serving gateway are directly discarded. The reconstruction of the user context depends on the time when the mobility management network element detects the service gateway reset.
  • connection re-establishment method in the prior art may cause the user terminal to be unable to perform data transmission for a long time, which affects the normal operation of the service.
  • connection re-establishment method device and system to solve the problem that the connection re-establishment method in the prior art affects the normal operation of the service.
  • the specific plan is as follows:
  • a connection reconstruction method comprising:
  • connection message including a user identifier sent by the home user register HSS
  • the connection message is sent by the data gateway to the HSS after being reset by the data gateway or the service gateway connected to the data gateway;
  • a connection re-establishment method is applied to a data gateway or a service gateway connected to a data gateway, and is characterized in that: Receiving downlink data packets;
  • a connection re-establishment method comprising: receiving a connection message sent by a data gateway and including a user identifier, where the connection message is sent by the data gateway according to the user identifier after being reset by itself or a service gateway connected thereto ;
  • connection message Transmitting the connection message to a mobility management network element corresponding to the user identity, the mobility management network element reestablishing the connection according to the message.
  • a mobility management network element comprising: a first connection message receiving module, configured to receive a connection message that is sent by a home user register HSS and includes a user identifier, where the connection message is used by the data gateway in the data gateway or The service gateway connected to the data gateway is reset and sent to the HSS;
  • a connection re-establishment module is configured to re-establish a connection according to the connection message.
  • a data gateway comprising: a data packet receiving module, configured to receive a downlink data packet; a user identity obtaining module, configured to acquire a user identifier corresponding to the downlink data packet; and a first connection message sending module, The connection message containing the user identifier is sent to the home user register HSS corresponding to the user identifier, so that the HSS is sent to the mobility management network element corresponding to the user identifier for reestablishing the connection.
  • a home user register HSS comprising: a second connection message receiving module, configured to receive a connection that is sent by a data gateway and includes a user identifier And the disconnected connection is sent by the data gateway according to the user identifier after being reset by itself or a service gateway connected thereto;
  • a second connection message sending module configured to send the connection message to the mobility management network element corresponding to the user identifier, where the mobility management network element reestablishes the connection according to the connection message.
  • a connection re-establishment system comprising: a data gateway as described above and a home user register as claimed in claim 22 or 23.
  • connection reconstruction time is greatly shortened, the normal transmission of data is ensured, and the user experience is improved.
  • FIG. 1 is a schematic diagram of a logical architecture of a next generation mobile communication network
  • FIG. 2 is a flowchart of a method for establishing a connection according to an embodiment of the present invention
  • FIG. 3 is a flowchart of obtaining a user identifier according to an embodiment of the present invention
  • FIG. 4 is a flowchart of still acquiring a user identifier according to an embodiment of the present invention
  • FIG. 5 is a flowchart of still another connection reconstruction method according to an embodiment of the present invention
  • FIG. 6 is a flowchart of still another connection reconstruction method according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of still another connection reconstruction method according to an embodiment of the present invention.
  • FIG. 8 is a flowchart of a method for reestablishing a connection by sending an indication message for re-establishing a PDN connection or re-attaching to a user terminal corresponding to a user identifier according to an embodiment of the present disclosure
  • FIG. 9 is a flowchart of a method for reestablishing a PDN connection by restoring a PDN connection of a data gateway corresponding to the data gateway identifier according to an embodiment of the present invention
  • FIG. 10 is a flowchart of an IP address allocation method according to an embodiment of the present invention.
  • FIG. 11 is a flowchart of a method for reestablishing a connection by restoring a PDN connection corresponding to the default bearer identifier according to an embodiment of the present disclosure
  • FIG. 12 is a schematic structural diagram of a data gateway according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic structural diagram of a user identity obtaining module according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic diagram of an enlarged structure of an HSS according to an embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of a mobility management network element according to an embodiment of the present disclosure.
  • FIG. 16 is a schematic structural diagram of a connection reconstruction system according to an embodiment of the present invention. detailed description
  • the invention provides a method for connection reconstruction after a gateway reset, which is suitable for mobile communication
  • the data gateway in the network because the gateway reset includes: the data gateway reset and the reset of the service gateway connected to the data gateway. Therefore, when the reset gateway is the data gateway, the packet data network PDN connection is taken as an example, and the specific connection reconstruction is performed.
  • the process is shown in Figure 2, including:
  • Step S21 Receive a downlink data packet, and obtain a user identifier corresponding to the downlink data packet.
  • the data gateway performs an operation of acquiring the user identifier, and the specific operation of obtaining the user identifier includes: receiving the downlink data packet, and obtaining the Set the user ID contained in the IP address of the user terminal of the downlink data packet assigned by the mode.
  • the downlink data packet sent to the user terminal is received, and the downlink data packet may be a service data packet or a signaling message data packet of the user terminal.
  • the data gateway identifies the PDN connection context or bearer context of the user terminal according to the header information of the service data packet, such as the destination IP address, or the IP address of the user terminal and the APN (Access Point Name) in the signaling message. . Since the PDN connection context is lost due to the data gateway reset, the data gateway cannot locate the PDN connection context or the bearer context, the data gateway obtains the user identifier according to the destination IP address of the downlink service data packet, or according to the information contained in the signaling message.
  • the IP address of the user terminal acquires a user identifier, which may be an IMSI (International Mobile Subscriber Identity) or an MSISDN (Mobile Station International ISDN number).
  • IMSI International Mobile Subscriber Identity
  • MSISDN Mobile Station International ISDN number
  • Step S22 Send a connection message including a user identifier to the Home Subscriber Server (HSS) corresponding to the user identifier, so that the HSS is sent to the mobility management network element corresponding to the user identifier for reestablishing the connection.
  • HSS Home Subscriber Server
  • the data gateway obtains the HSS of the user terminal by using the user identifier, and sends a connection message to the HSS.
  • the connection message includes the user identifier and the data gateway identifier, and may also include the APN.
  • the data gateway The identifier may be an Internet Protocol (IP) address of the data gateway, or may be a Fully Qualified Domain Name (FQDN) of the data gateway.
  • IP Internet Protocol
  • FQDN Fully Qualified Domain Name
  • the home user register After receiving the connection message, the home user register learns the mobile management network element serving the user terminal according to the user identifier, and sends the connection message to the mobility management network element.
  • the home user register After receiving the connection message, the home user register can also reply a response message to the data gateway to notify the data gateway. When the data gateway does not receive the response message, the connection message is sent again to the home user register, thereby avoiding the phenomenon that the home user register receives the connection message due to interference in the data transmission process, etc., and ensuring the reliability of the connection reconstruction process. Sex and effectiveness.
  • the mobility management network element can also notify the home user register by replying to the response message.
  • This embodiment does not limit the number of data packets received by the data gateway. If the data gateway receives multiple PDN-connected data packets for a period of time or at the same time, the message sent to the HSS may include multiple user identifiers, multiple The data gateway identifier and the plurality of APNs are used to indicate different PDN connections represented by the plurality of data packets, thereby instructing the mobility management network element to re-establish all connections.
  • the data gateway after resetting, obtains the user identifier through the received downlink data packet and determines the HSS, and sends a connection message to the HSS, and the HSS transmits the connection message to the mobility management network element in time to enable mobility management.
  • the network element can obtain the information of the gateway reset in time, perform connection reconstruction in time, shorten the waiting time for connection reconstruction, reduce the number of data packets discarded due to connection loss, and shorten the waiting time for the user terminal to re-implement data communication. , improved user experience.
  • the process of obtaining the user identifier may be implemented according to the process shown in FIG. 3, including: Step S31: Receive a downlink data packet.
  • Step S32 Acquire a user identifier included in a user terminal IP address of the downlink data packet allocated according to the preset manner.
  • the process of obtaining the user identifier is related to the process of assigning an IP address according to a preset manner.
  • the preset manner is as follows: the user identifier is included in the interface identifier, and is allocated to the user terminal.
  • the specific steps include:
  • Step S321 The user terminal initiates an attach, a Packet Data Protocol (PDP) context activation process, or a PDN connection establishment process.
  • PDP Packet Data Protocol
  • Step S322 The mobility management network element sends a setup session request message to the serving gateway, where the request message is forwarded to the data gateway by the serving gateway.
  • Step S323 The data gateway determines the type of the IP address allocated to the user terminal according to the type of the IP address requested in the received session establishment request message and some policies of the user.
  • IPv4 address IPv4 and IPv6, or IPv6.
  • Step S324 The data gateway sends a session establishment response message, where the message includes a PDN address cell. If the IP address type assigned to the user terminal includes an IPv6 address, the cell includes a prefix and an interface identifier assigned to the user terminal. The data gateway can assign an IPv6 prefix by itself or obtain an IPv6 prefix from other devices. For the interface identifier, the data gateway includes the user identifier in the interface identifier and is assigned to the user terminal.
  • Step S325 The serving gateway forwards the message sent by the data gateway to the mobility management network element.
  • Step S327 The user terminal initiates an IPv6 address acquisition process, and sends a route request message to the data gateway.
  • Step S328 The data gateway sends a route advertisement message, where the message includes a prefix allocated to the user terminal.
  • the interface identifier can also be included in further messages.
  • the IP address allocation process is as described above, and the step S324 and the step S328 may both carry the interface identifier including the user identifier.
  • the step S324 carries the interface identifier that includes the user identifier, and the step S328 does not carry the interface identifier.
  • the step S324 includes the interface identifier that is arbitrarily assigned by the data gateway, and the step 8 carries the interface identifier that includes the user identifier.
  • step S323 is: the serving gateway sends a proxy binding update message to the data gateway;
  • step S324 is: the data gateway sends a proxy binding acknowledgement message, where the message includes a PDN address cell;
  • Step S327 is: the user terminal initiates an IPv6 address acquisition process, and sends a route request message to the service gateway;
  • step S324 the interface identifier including the user identifier must be carried, and the interface identifier obtained by the serving gateway in step S324 may be included in step S328.
  • the data gateway In order to prevent PDN connection context conflicts established before and after reset, the data gateway must ensure that the IPv6 address allocated before reset is not reassigned to any user within a certain period of time after reset. That is, the data gateway is not allocated and allocated to any user before the data gateway is reset within a preset time after the reset. The IP address of the terminal is duplicated to the user terminal.
  • the data gateway may perform the encryption operation on the user identifier, and include the encrypted user identifier in the interface identifier.
  • the specific encryption process includes: encrypting the user identifiers of all user terminals by using the same key, and the data gateway may or may not store the keys; or, according to the type of the user terminal, or different time The factors are encrypted by using different keys, the keys are stored, and an index for indicating a key for encrypting the user identifier included in the interface identifier is included in the interface identifier.
  • the user identifier when obtaining the user identifier, the user identifier may be directly obtained from the interface identifier, or the user identifier that is encrypted in the interface identifier may be decrypted by using the key, and the user identifier is obtained, or according to the
  • the key index included in the interface identifier obtains a key for encrypting the user identifier included in the user interface identifier, decrypts the encrypted user identifier, and obtains the user identifier.
  • the specific situation will vary depending on the distribution process.
  • the present invention also discloses another process of obtaining a user identifier, as shown in FIG. 4, including: Step S41: Acquire an IP address of a user terminal in a downlink data packet;
  • Step S42 Send an identifier request message to the policy and charging rule function.
  • PCRF Policy and Charging rule function
  • the identifier request message includes the user terminal IP address
  • the data gateway sends a message to the PCRF.
  • the PCRF is responsible for policy control, charging, and QoS rule delivery.
  • the message includes the destination IP address of the IP header of the downlink service data packet, which is the IP address of the user terminal, or contains signaling message data.
  • the data gateway sends the message to the opposite end transmitting the signaling message data packet.
  • the PCRF sends the request message.
  • Step S43 Receive response information that is returned by the PCRF and includes the user identifier.
  • the PCRF replies to the response message. If there is information related to the user terminal on the PCRF, the user identifier is included in the response message. If the information of the user terminal is not available on the PCRF, the rejection message is replied.
  • Step S44 Acquire a user identifier in the response information.
  • the data gateway After the data gateway receives the message, if the message includes the user identifier, the data gateway obtains the home user register of the user terminal through the user identifier, and sends a connection message to the home user register, where the connection message includes the user identifier and the data gateway identifier, and Can contain APN.
  • the data gateway may also use the process as described in Figure 3 to obtain the user identity.
  • the connection re-establishment process is as shown in FIG. 5, including: Step S51: Receive a downlink data packet, and send the downlink data packet to the serving gateway; the serving gateway receives the downlink data packet, where the downlink
  • the packet type may be a service data packet or a signaling message data packet of the user terminal.
  • the serving gateway cannot find the stored user context/bearer context according to the Tunnel Endpoint Identifier (TEID) of the GTP header in the data packet, and the service gateway discards the data packet if the type of the received data packet is a service data packet.
  • TEID Tunnel Endpoint Identifier
  • the service gateway sends an error indication message as a reset indication message.
  • the serving gateway sends a response message including the reason value of the rejection as a reset indication message, and sends a reset indication message to the downlink data packet corresponding to the received downlink data packet.
  • a data gateway that is, a data gateway connected to the service gateway.
  • Step S52 The data gateway receives a reset indication message sent by the serving gateway, where the reset indication is cancelled.
  • the information is sent by the serving gateway according to the type of the received downlink data packet;
  • Step S53 The data gateway determines, according to the reset indication message, that the service gateway is reset.
  • the data gateway learns that the service gateway resets and restarts. For the case of receiving the error indication message, the data gateway may determine that the service gateway has been reset according to the information in the error indication message or path detection. For the case of receiving a response signaling message, the data gateway determines that the serving gateway resets and restarts based on the reset counter contained in the message.
  • Step S54 The data gateway acquires the user identifier corresponding to the downlink data packet received by the serving gateway. Because the service gateway is reset and the data gateway works normally, the data gateway can directly use the downlink data packet received by the serving gateway that is stored by itself. The corresponding PDN connection acquires the user identifier corresponding to the downlink data packet.
  • Step S55 Send a connection message including a user identifier to the HSS corresponding to the user identifier, and the connection message is sent to the mobility management network element corresponding to the user identifier by using the HSS, and the mobility management network element reestablishes the connection according to the connection message.
  • the connection message also includes a default bearer identifier.
  • the default bearer identifier is an identifier of a default bearer of a PDN connection corresponding to the received downlink packet that is lost on the service gateway that is reset.
  • the HSS sends a message containing the user ID and the default bearer ID to the mobility management network element.
  • FIG. 6 Another method for connection reconstruction disclosed in the present invention is shown in FIG. 6. The method is applicable to HSS in a mobile communication network, and includes:
  • Step S61 Receive a message that includes a user identifier sent by the data gateway, where the message is reset by the data gateway at its own or a service gateway connected thereto, and receives the downlink data packet, and obtains the user identifier of the downlink data packet, according to the user identifier. send;
  • the connection message includes the data gateway identifier of the data gateway, and may also include the APN when the gateway is the data gateway, and the default bearer identifier is also included when the gateway is the serving gateway.
  • Step S62 Send the connection message to the mobility management network element, and the mobility management network element reestablishes the connection according to the message.
  • the foregoing two steps further include: confirming, according to the user identifier, the mobility management network element corresponding to the user identifier.
  • the connection message is sent to the corresponding mobility management network element.
  • the method may further include: sending a reply response message to the data gateway, so that the data gateway can learn that the HSS has successfully received the connection message. Thereby improving the accuracy and reliability of the connection establishment process.
  • the HSS transmits the connection message sent by the data gateway to the mobility management network element, so that the mobile management network element can obtain the information of the gateway reset in time, and the connection reconstruction is performed in time, thereby shortening the connection reconstruction.
  • the waiting time reduces the number of data packets discarded due to connection interruption, shortens the waiting time for the user terminal to re-implement data communication, and improves the user experience.
  • FIG. 7 Another method for connection reconstruction disclosed in the present invention is shown in FIG. 7. The method is applicable to a mobility management network element in a mobile communication network, and includes:
  • Step S71 Receive a connection message that is sent by the HSS according to the user identifier, and includes the connection identifier of the user identifier.
  • the message is reset by the data gateway at the data gateway or the service gateway connected to the data gateway, and after receiving the downlink data packet, acquiring the downlink.
  • the connection message further includes: a data gateway identifier of the data gateway, and further, may include an APN; when the serving gateway connected to the data gateway is reset, the connection message is further The identifier of the default bearer of the PDN connection corresponding to the downlink data packet is included.
  • Step S72 Reestablish the connection according to the connection message.
  • connection message After receiving the connection message, re-establish the connection.
  • the process of reestablishing the connection according to the connection message includes:
  • FIG. 8 The process of re-establishing a PDN connection or re-attaching the indication message to the user terminal corresponding to the user identifier to re-establish the connection is as shown in FIG. 8 , which specifically includes:
  • Step S81 After receiving the message of the home user register, the mobility management network element determines the state of the user terminal represented by the user identifier. If it is in an idle state, step S82 is performed, if it is in a connected state, step S83 is directly performed;
  • Step S82 paging the user terminal in the idle state, triggering the user terminal to initiate a service request process to resume the radio bearer, and then performing step S83;
  • Step S83 The mobility management network element sends a delete session request message to the service gateway, where the delete session request message includes the user identifier and the data gateway identifier included in the message received in step S71, if The connection message includes an APN, and the deletion session request message may further include an APN, a default 7-digit identifier of the identified PDN connection context.
  • Step S84 The mobility management network element initiates a deletion process to the radio access network and the user terminal, and deletes the PDN connection corresponding to the user identifier and the data gateway identifier in step S83, or connects to the PDN corresponding to the APN.
  • the mobility management network element sets the cause value to the reactivation connection request in the message sent to the user terminal;
  • Step S85 The user terminal initiates a PDN connection establishment process, and re-establishes the PDN connection deleted in step S84.
  • Step S86 The mobility management network element reselects the data gateway, and the data gateway may be a data gateway after resetting the restart, or may be another data gateway, sending a setup session request to the serving gateway of the service user terminal, and the service gateway forwards the message. Give the data gateway. The data gateway and the service gateway reply to the response message, and the process re-establishes the PDN connection on the service gateway and the data gateway;
  • Step S87 Establish a radio bearer, and notify the serving gateway of downlink tunnel information.
  • the data gateway that established the PDN connection forwards the data packet to the user terminal on the downlink path.
  • Step S83 The mobility management network element sends a delete session request message to the service gateway, where the message includes an indication of deleting all contexts of the user terminal represented by the user identifier.
  • Step S84 The mobility management network element sends a separation request message to the user terminal, where the cause value is set in the message. To reattach; the user terminal replies with a corresponding response message. The mobility management network element releases the wireless signaling connection. Step S85: The user terminal initiates an attach procedure.
  • Step S86 The mobility management network element selects a service gateway and a data gateway, and re-establishes a PDN connection on the service gateway and the data gateway.
  • Step S87 initial context establishment, attach accepting, and air interface bearer establishment, and notify the serving gateway to download tunnel information.
  • a PDN connection of the user terminal is re-established in the network. If the user terminal has multiple PDN connections to be reconstructed, a subsequent PDN connection establishment process such as step S85-S87 is initiated to re-establish these PDN connections.
  • the present invention does not limit the number of data packets received by the data gateway. If the data gateway receives multiple PDN-connected data packets for a period of time or at the same time, the message sent to the HSS may include multiple user identifiers, multiple The data gateway identifier and the plurality of APNs are used to indicate different PDN connections represented by the plurality of data packets, thereby instructing the mobility management network element to re-establish all PDN connections.
  • the present invention also discloses recovering a PDN connection of a data gateway corresponding to the data gateway identifier.
  • the method for reestablishing the PDN connection is as shown in Figure 9, which includes:
  • Step S91 Send a recovery message to the service gateway connected to the data gateway, where at least the pre-stored IP address allocated to the user terminal is included;
  • the recovery information further includes: an APN, a general wireless packet service tunneling protocol GTP control plane allocated by the serving gateway to the data gateway, and a user plane tunnel information, etc., required for the data gateway to restore the PDN connection Information.
  • Step S92 The recovery message is forwarded to the data gateway by the serving gateway.
  • Step S93 The data gateway restores the PDN connection of the user terminal corresponding to the user identifier according to the recovery message.
  • the data gateway After receiving the recovery message forwarded by the serving gateway, the data gateway stores the information carried in the recovery message, and restores the PDN connection context of the user terminal.
  • the information carried in the recovery message is the information required for the PDN connection context on the data gateway. Further, it also includes:
  • Step S94 The data gateway returns a response message to the serving gateway.
  • Step S95 The serving gateway forwards the received response message to the mobility management network element.
  • Step S96 Paging the user terminal in the idle state, triggering the user terminal to initiate a service request process to resume the radio bearer.
  • the mobility management network element may be in the step
  • the air interface connection of the user terminal is released before S91, and the state of the user terminal is changed to the idle state.
  • the user ID, the data gateway identifier, and the PDN connection context lost on the data gateway of the APN identifier are recovered in the network by the mobile management network element.
  • the reset The data gateway forwards the data packet to the user terminal on the downlink path.
  • the embodiment does not limit the number of data packets received by the data gateway. If the data gateway receives multiple PDN-connected data packets for a period of time or at the same time, the message sent to the HSS may include multiple user identifiers. A plurality of data gateway identifiers and a plurality of APNs are used to indicate different PDN connections represented by the plurality of data packets, thereby instructing the mobility management network element to restore all PDN connections.
  • the user terminal obtains the dynamic host configuration protocol version 4 (DHCPv4). If the IPv4 address is not available on the mobility management network element, the IPv4 address assigned to the user terminal needs to be pre-stored on the mobility management network element.
  • DHCPv4 dynamic host configuration protocol version 4
  • Step S101 The user terminal initiates an attach, the PDP context is activated, or the PDN connection is established, and a PDN connection is established in the network.
  • Step S102 The user terminal requests the DHCPv4 mode to obtain an IPv4 address, and the user terminal and the data gateway obtain an IPv4 address through a DHCPv4 process.
  • Step S103 The data gateway sends a notification message to the serving gateway, where the notification message is used to notify the IPv4 address allocated to the user terminal, and the service gateway forwards the notification message to the mobility management network element, and the mobility management network element and the monthly service gateway reply correspondingly.
  • Step S104 Store the IP address assigned to the user terminal.
  • the message in the DHCPv4 process of step S102 is forwarded by the service gateway and sent to the data gateway or the user terminal.
  • the service gateway sends a notification message to the mobility management network element. This message is used to notify the IPv4 address assigned to the user terminal.
  • the mobility management network element replies with a response message.
  • step S83 is not performed, and the mobile management network element directly performs the steps of S84 and subsequent steps after the step S81, and the user terminal in the idle state directly executes after the step S82.
  • step S84 the PDN connection that needs to be deleted is determined by using the user identifier and the default identifier.
  • step S86 for a case where only part of the PDN connection needs to be re-established, the mobility management network element selects a new service gateway, which may be a reset service gateway or other service gateway.
  • the mobile management network element can also select a new data gateway.
  • the mobility management network element re-establishes a PDN connection on the service gateway and the data gateway;
  • Step S11 determining the state of the user terminal, if it is in the connected state, step S112 is performed, if it is idle, step S113 is performed;
  • Step S112 releasing an air interface connection, and turning the user terminal into an idle state
  • Step S113 Select a service gateway, and send a setup session request message to the serving gateway.
  • Step S115 The data gateway replies with a response message to the serving gateway.
  • Step S116 The serving gateway sends a session establishment request message to the mobility management network element.
  • Step S117 The mobile management network element pages the user terminal in the idle state, and triggers the user terminal to initiate a service request process to resume the radio bearer.
  • the present invention discloses a data gateway, which has the structure shown in FIG. 12, and includes: a data packet receiving module 121, a user identifier obtaining module 122, and a first connection message sending module 123, where:
  • the data packet receiving module 121 is configured to receive a downlink data packet, where the user identifier obtaining module 122 is configured to obtain And the first connection message sending module 123 is configured to send the connection that includes the user identifier to the home user register HSS corresponding to the user identifier, and further includes: a data packet sending module 124, configured to send the downlink data packet to the serving gateway, a reset indication information receiving module 125, configured to receive a reset indication message sent by the serving gateway, and a determining module 126, configured to use the reset indication information Determine the service gateway reset.
  • the user identifier obtaining module 122 includes: a first obtaining unit 1221, configured to acquire a user identifier in a user terminal IP address in the downlink data packet.
  • the method further includes: a decryption unit 1222, configured to obtain the user identifier according to the encrypted user identifier in the key identifier, or obtain the encrypted user interface identifier according to the key index included in the interface identifier. The key of the user identifier, decrypting the encrypted user identifier, and obtaining the user identifier.
  • a decryption unit 1222 configured to obtain the user identifier according to the encrypted user identifier in the key identifier, or obtain the encrypted user interface identifier according to the key index included in the interface identifier. The key of the user identifier, decrypting the encrypted user identifier, and obtaining the user identifier.
  • the user identity obtaining module 122 includes another unit combination, as shown in FIG.
  • the IP address obtaining unit 1223 is configured to obtain the user terminal IP address in the downlink data packet, and the identifier request message sending unit 1224 is configured to send an identifier request message to the policy and charging rule function PCRF, where the identifier request message is used.
  • the user terminal IP address is included;
  • the response message receiving unit 1225 is configured to receive the response information that is returned by the PCRF and includes the user identifier; and
  • the second obtaining unit 1226 is configured to obtain the user identifier in the response information.
  • the corresponding unit combination can be selected according to the actual situation to implement the function of the user identification acquisition module.
  • the working process of each module is as shown in the specific implementation method corresponding to any process in Figure 2-5. This will not be repeated here.
  • the invention also discloses an HSS, the structure of which is shown in FIG. 14 and includes:
  • the second connection message receiving module 141 is configured to receive a connection message that is sent by the data gateway and includes a user identifier, where the message is reset by the data gateway at itself or a service gateway connected thereto, and is sent according to the user identifier;
  • the second message sending module 142 is configured to send the message to the mobile management network element corresponding to the user identifier, where the mobility management network element reestablishes the connection according to the message.
  • the method further includes: an acknowledgment module 143, configured to confirm, according to the user identifier, the mobility management network element corresponding to the user identifier.
  • the present invention discloses a mobility management network element, and its structure is as shown in FIG. 15, including: a first message receiving module 151 and a connection re-establishment module 152, wherein: the first message receiving module 151 is configured to receive a home user register.
  • the connection message is sent by the HSS, and the connection message is sent by the data gateway to the HSS after being reset by the data gateway or the service gateway connected to the data gateway; the connection re-establishment module 152 is configured to re-establish the connection according to the message. .
  • connection reconstruction module 152 includes:
  • the indication message sending unit 1521 is configured to send, to the user terminal corresponding to the user identifier, an indication message for re-establishing a PDN connection or re-attaching;
  • the recovery unit 1522 is configured to restore a PDN connection of the data gateway corresponding to the data gateway identifier when the data gateway is reset, and restore the default bearer when the serving gateway is reset Identifies the corresponding PDN connection.
  • the working process of each module is as described in the specific implementation manner corresponding to the flowchart shown in FIG. 7-11, and details are not described herein again.
  • the invention also discloses a connection reconstruction system, which has the structure shown in FIG. 16, and includes: a data gateway 161, configured to reset the service gateway connected to the data gateway or the data gateway, and receive the downlink data packet, and obtain a user identifier corresponding to the downlink data packet, and sending a message including the user identifier to a home user register HSS corresponding to the user identifier; the HSS 162, configured to receive a message that includes a user identifier sent by the data gateway, where the message is sent The mobile management network element 163 is configured to receive a message that is sent by the home user register HSS according to the user identifier, and includes the user identifier, and reconstructs the connection according to the message.
  • a data gateway 161 configured to reset the service gateway connected to the data gateway or the data gateway, and receive the downlink data packet, and obtain a user identifier corresponding to the downlink data packet, and sending a message including the user identifier to a home user register HSS corresponding to the user identifier
  • the structure of the data gateway in the system disclosed in this embodiment is as shown in FIG. 12 or 13.
  • the structure of the HSS is as shown in FIG. 14
  • the mobility management network element is as shown in FIG. 15 , but the embodiment does not limit the structure of each part. It can be divided into functional modules of arbitrary structure according to its function.
  • the software module can be placed in random access memory (RAM), memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or technical field. Any other form of storage medium known.
  • RAM random access memory
  • ROM read only memory
  • electrically programmable ROM electrically erasable programmable ROM
  • registers hard disk, removable disk, CD-ROM, or technical field. Any other form of storage medium known.

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)

Description

一种连接重建方法、 设备和系统
技术领域
本发明涉及移动通信网络技术领域, 尤其涉及一种连接重建方法、设备和 系统。 背景技术
下一代移动通信网络的逻辑架构如图 1所示, 用户终端 11通过本地的无 线接入网络 12接入, 移动管理网元 13负责移动用户终端 11的位置管理、 连 接管理、 安全认证、 网关选择等功能, 服务网关 14是用户终端 11的本地接入 网关, 负责接入技术相关的连接管理和数据转发, 数据网关 15是用户终端访 问外部数据网络的网关。
现有技术中, 数据网关需要通过对应的 PDN ( Packet Data Network, 分组 数据网络)连接上下文或者承载上下文才能获知数据包发行的下行通道,如将 数据包通过哪条隧道发送给哪个服务网关,如果数据网关复位, 复位后数据网 关因为丟失了 PDN连接上下文或者承载上下文而无法获知数据包转发通道, 数据网关收到用户终端的下行数据包后, 只能丟弃该数据包。
服务网关通过信令消息获知数据网关复位后,通知受影响的移动管理网元 删除服务网关和复位的数据网关相关的 PDN连接上下文。 移动管理网元收到 服务网关的消息后, 通知用户终端重新建立该 PDN连接或者重新附着。 在用 户终端发起的 PDN连接建立或者附着流程中, 移动管理网元会在核心网侧, 重新建立该 PDN连接, 该核心网侧包括服务网关和数据网关。 重新建立 PDN 连接后, 用户终端的该 PDN连接对应的业务才能在网络内进行。
由此可以看出, 上述现有技术中, 用户终端的 PDN连接重建之前, 复位的 数据网关上收到的该 PDN连接对应的下行数据包都会直接丟弃。而移动管理网 元获知数据网关复位通知用户终端重建建立受影响的 PDN连接或者重新附着 的机制依赖于服务网关获知数据网关复位的时间,以及服务网关获知数据网关 复位后扫描内部受影响的 PDN连接的时间, 该时间可能耗掉半小时或者更久。
服务网关复位的情况也类似, 用户上下文重建之前,服务网关上收到的下 行数据包都会被直接丟弃,而用户上下文的重建依赖于移动管理网元探测到服 务网关复位的时间。
所以,现有技术中的连接重建方法会导致用户终端长时间无法进行数据传 输, 影响了业务的正常进行。 发明内容
有鉴于此, 本发明提供一种连接重建方法、设备和系统, 以解决现有技术 中的连接重建方法影响业务的正常进行的问题。 其具体方案如下:
一种连接重建方法, 其特征在于, 包括:
接收家乡用户寄存器 HSS发送的包含用户标识的连接消息, 所述连接消 息由数据网关在本数据网关或与本数据网关相连的服务网关复位后发送给所 述 HSS;
依据所述连接消息重建连接。
一种连接重建方法, 应用于数据网关或与数据网关相连的服务网关复位 后, 其特征在于, 包括: 接收下行数据包;
获取与所述下行数据包对应的用户标识; 向与所述用户标识对应的家乡用户寄存器 HSS发送包含有所述用户标识 重建连接。
一种连接重建方法, 其特征在于, 包括: 接收数据网关发送的包含用户标识的连接消息,所述连接消息由所述数据 网关在其自身或与其相连的服务网关复位后依据所述用户标识发送;
将所述连接消息发送给与所述用户标识对应的移动管理网元,所述移动管 理网元依据所述消息重建连接。
一种移动管理网元, 其特征在于, 包括: 第一连接消息接收模块, 用于接收家乡用户寄存器 HSS发送的包含用户 标识的连接消息,所述连接消息由数据网关在本数据网关或与本数据网关相连 的服务网关复位后发送给所述 HSS;
连接重建模块, 用于依据所述连接消息重建连接。
一种数据网关, 其特征在于, 包括: 数据包接收模块, 用于接收下行数据包; 用户标识获取模块, 用于获取与所述下行数据包对应的用户标识; 第一连接消息发送模块, 用于向与所述用户标识对应的家乡用户寄存器 HSS发送包含有所述用户标识的连接消息, 以使所述 HSS发送给与所述用户 标识对应的移动管理网元用于重建连接。
一种家乡用户寄存器 HSS, 其特征在于, 包括: 第二连接消息接收模块,用于接收数据网关发送的包含用户标识的连接消 息,所述消连接息由所述数据网关在其自身或与其相连的服务网关复位后依据 所述用户标识发送;
第二连接消息发送模块,用于将所述连接消息发送给与所述用户标识对应 的移动管理网元, 所述移动管理网元依据所述连接消息重建连接。
一种连接重建系统, 其特征在于, 包括: 如上所述的数据网关和如权利要 求 22或 23所述的家乡用户寄存器。
从上述的技术方案可以看出, 本发明实施例公开的连接重建方法中, 采用 当数据网关复位或者与数据网关相连的服务网关复位时,将包含有用户标识的 连接消息发送给家乡用户寄存器, 并由其发送给移动管理网元,使得移动管理 网元可以依据连接消息进行连接重建,而无需采用现有技术中的方式等待一定 的时间后才能使移动管理网元获知网关复位, 进行连接重建,从而极大的缩短 了连接重建的时间, 保证了数据的正常传输, 提升了用户体验。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案,下面将对实施 例或现有技术描述中所需要使用的附图作筒单地介绍,显而易见地, 下面描述 中的附图仅仅是本发明的一些实施例, 对于本领域普通技术人员来讲,在不付 出创造性劳动的前提下, 还可以根据这些附图获得其他的附图。
图 1为下一代移动通信网络的逻辑架构示意图;
图 2为本发明实施例公开的连接重建方法的流程图; 图 3为本发明实施例公开的获取用户标识的流程图;
图 4为本发明实施例公开的又一获取用户标识的流程图; 图 5为本发明实施例公开的又一连接重建方法的流程图;
图 6为本发明实施例公开的又一连接重建方法的流程图;
图 7为本发明实施例公开的又一连接重建方法的流程图;
图 8 为本发明实施例公开的通过向与用户标识对应的用户终端发送重新 建立 PDN连接或者重新附着的指示消息重建连接的方法流程图;
图 9 为本发明实施例公开的通过恢复与所述数据网关标识对应的数据网 关的 PDN连接的重建 PDN连接的方法流程图;
图 10 为本发明实施例公开的 IP地址分配方法的流程图;
图 11为本发明实施例公开的通过恢复与所述缺省承载标识对应的 PDN连 接重建连接的方法流程图;
图 12为本发明实施例公开的一种数据网关的结构示意图;
图 13为本发明实施例公开的用户标识获取模块的结构示意图;
图 14为本发明实施例公开的一种 HSS放大结构示意图;
图 15为本发明实施例公开的一种移动管理网元的结构示意图;
图 16为本发明实施例公开的一种连接重建系统的结构示意图。 具体实施方式
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清 楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而不是 全部的实施例。基于本发明中的实施例, 本领域普通技术人员在没有做出创造 性劳动前提下所获得的所有其他实施例, 都属于本发明保护的范围。
本发明提供了一种网关复位后进行连接重建的方法,该方法适用于移动通 信网络中的数据网关, 由于网关复位包括: 数据网关复位和与数据网关相连的 服务网关的复位, 所以, 当复位网关为数据网关时, 以分组数据网络 PDN连 接为例, 其具体的连接重建流程如图 2所示, 包括:
步骤 S21、 接收下行数据包, 获取与下行数据包对应的用户标识; 当数据网关复位时,数据网关进行获取用户标识的操作, 具体的获取用户 标识的操作包括: 接收下行数据包, 获取按照预设方式分配的下行数据包的用 户终端 IP地址中包含的用户标识。
数据网关复位后收到发送给用户终端的下行数据包, 该下行数据包可以为 用户终端的业务数据包或者信令消息数据包。数据网关根据业务数据包的头部 信息, 如目的 IP 地址, 或者信令消息中包含的用户终端的 IP 地址和 APN ( Access Point Name接入点名字 )标识定位用户终端的 PDN连接上下文或者 承载上下文。 由于该 PDN连接上下文因为数据网关复位已经丟失, 数据网关 无法定位到该 PDN连接上下文或者承载上下文, 则数据网关根据下行业务数 据包的目的 IP地址获取用户标识, 或者根据该信令消息中包含的用户终端的 IP地址获取用户标识, 该用户标识可以为 IMSI ( international mobile subscriber identity 国际移动用户标识), 也可以 MSISDN ( Mobile Station International ISDN number, 移动用户国际号码)等。
步骤 S22、向与用户标识对应的家乡用户寄存器( Home Subscriber Server , HSS )发送包含用户标识的连接消息, 以使所述 HSS发送给与所述用户标识 对应的移动管理网元用于重建连接。
数据网关通过用户标识获知用户终端的 HSS, 发送连接消息给该 HSS, 该连接消息中包含用户标识和数据网关标识, 还可以包含 APN。 该数据网关 标识可以为数据网关的网际协议(Internet Protocol, IP )地址, 也可以为数据 网关的域名 ( Fully Qualified Domain Name, FQDN )等。
家乡用户寄存器接收到连接消息后,依据用户标识获知服务该用户终端的 移动管理网元, 将连接消息发送给移动管理网元。
家乡用户寄存器在接收到连接消息后,还可向数据网关回复响应消息, 以 通知数据网关。 当数据网关没有接收到响应消息时, 向该家乡用户寄存器再次 发送连接消息,从而避免由于数据传输过程中的干扰等问题影响家乡用户寄存 器接收连接消息的现象发生, 保证了该连接重建过程的可靠性和有效性。
同理,移动管理网元接收到连接消息后, 同样可以采用回复响应消息的方 式通知家乡用户寄存器。
本实施例并不限定数据网关接收的数据包的个数,如果数据网关上一段时 间内或同时收到了多个 PDN连接的数据包,发送给 HSS的消息中可以包含多 个用户标识, 多个数据网关标识以及多个 APN, 用以表示多个数据包代表的 不同的 PDN连接, 从而指示移动管理网元重新建立起全部的连接。
本实施例公开的连接重建方法中,数据网关在复位后,通过接收的下行数 据包获得用户标识并确定 HSS ,向 HSS发送连接消息, HSS将连接消息及时 传送给移动管理网元, 使得移动管理网元可以及时获得网关复位的信息, 及 时进行连接重建, 缩短了连接重建所需等待的时间, 降低了因连接丟失而丟 弃的数据包的数量, 缩短了用户终端重新实现数据通信的等待时间, 提升了 用户体验。 进一步的, 获取用户标识的过程可按照如图 3所示流程实现, 包括: 步骤 S31、 接收下行数据包;
步骤 S32、 获取按照预设方式分配的下行数据包的用户终端 IP地址中包 含的用户标识。
其中, 获取用户标识的过程与按照预设方式分配 IP地址的过程相关, 所 述预设方式为: 将用户标识包含在接口标识中, 分配给所述用户终端。
具体步骤包括:
步骤 S321、用户终端发起附着,分组数据协议( Packet Data Protocol, PDP ) 上下文激活流程或者 PDN连接建立流程;
步骤 S322、 移动管理网元发送建立会话请求消息给服务网关, 该请求消 息经服务网关转发给数据网关;
步骤 S323、数据网关根据收到的建立会话请求消息中请求的 IP地址类型, 以及自身的一些策略, 决定分配给用户终端的 IP地址类型;
如 IPv4地址, IPv4和 IPv6, 或者 IPv6。
步骤 S324、数据网关发送建立会话响应消息,消息中包含 PDN地址信元; 如果分配给用户终端的 IP地址类型包含 IPv6地址, 该信元中包含分配给 用户终端的前缀和接口标识。 数据网关可以自身分配 IPv6前缀, 或者从其它 设备上获取 IPv6前缀。 对于接口标识, 数据网关将用户标识包含在接口标识 中分配给用户终端。
步骤 S325、 服务网关将数据网关发来的消息转发给移动管理网元; 步骤 S326、 移动管理网元发送附着接受, PDP上下文激活接受或者 PDN 连接建立接受消息给用户终端;
该消息中包含数据网关分配的接口标识。 步骤 S327、 用户终端发起 IPv6地址获取流程, 发送路由请求消息给数据 网关;
步骤 S328、 数据网关发送路由公告消息, 消息中包含分配给用户终端的 前缀;
进一步的消息中还可以包含接口标识。
当服务网关和数据网关之间的接口为 GPRS隧道协议(GPRS Tunnelling Protocol, GTP )时, 其 IP地址的分配过程如上所述, 并且, 步骤 S324和步骤 S328可以都携带包含用户标识的接口标识,或者步骤 S324中携带包含用户标 识的接口标识, 而步骤 S328不携带接口标识; 或者, 步骤 S324包含数据网关 任意分配的接口标识, 而步骤 8携带包含用户标识的接口标识。
当服务网关和数据网关之间的接口为代理移动 IPv6 ( Proxy Mobile IPv6, ΡΜΙΡνό ) 时,
上述步骤 S323为: 服务网关发送代理绑定更新消息给数据网关; 步骤 S324为:数据网关发送代理绑定确认消息, 消息中包含 PDN地址信 元;
步骤 S327为: 用户终端发起 IPv6地址获取流程, 发送路由请求消息给服 务网关;
并且,步骤 S324中必定携带包含用户标识的接口标识,步骤 S328中可以 包含服务网关在步骤 S324中获得的接口标识。
为了防止复位前后建立的 PDN连接上下文沖突, 数据网关必须确保复位 前分配的 IPv6地址在复位后的一定时间内不会重新分配给任意用户。 即, 数 据网关在复位后的预设时间内不分配与所述数据网关复位前分配给任一用户 终端的 IP地址重复的 IP地址给所述用户终端。
更进一步的,出于安全性考虑,数据网关可以将该用户标识进行加密操作, 并将加密后的用户标识包含在接口标识中。具体的加密过程包括: 对所有的用 户终端的用户标识采用相同的密钥进行加密,数据网关可以存储所述密钥, 也 可以不存储; 或者, 依据所述用户终端的类型, 或者不同的时间等因素采用不 同的密钥进行加密,存储所述密钥, 并在所述接口标识中包含用于指示加密所 述接口标识包含的用户标识的密钥的索引。
对应于上述 IP地址的分配过程, 在获取用户标识时, 可以直接从接口标 识中获取, 也可利用密钥, 解密所述接口标识中加密的用户标识, 获取所述用 户标识,或者依据所述接口标识中包含的密钥索引获得加密该用户接口标识包 含的用户标识的密钥, 解密所述加密的用户标识, 获取所述用户标识。 具体的 情况依据分配过程的不同而不同。
同时, 本发明还公开了另一获取用户标识的过程, 如图 4所示, 包括: 步骤 S41、 获取下行数据包中的用户终端 IP地址;
步骤 S42、 发送标识请求消息给策略和计费规则功能 PCRF ( Policy and
Charging Rules Function, PCRF ), 所述标识请求消息中包含所述用户终端 IP 地址;
数据网关发送消息给 PCRF, PCRF负责策略控制, 计费和 QoS规则下发 等, 该消息中包含下行业务数据包 IP头的目的 IP地址, 即为用户终端的 IP 地址, 或包含信令消息数据包中包含的用户终端的 IP地址。 对于收到信令消 息数据包的情况,数据网关向发送该信令消息数据包的对端发送该消息。对于 收到业务数据包的情况, 数据网关如果无法确定具体的 PCRF, 则向本网的 PCRF都发送该请求消息。
步骤 S43、 接收 PCRF返回的包含有该用户标识的响应信息;
PCRF回复响应消息, 如果 PCRF上有用户终端相关的信息, 则在响应消 息中包含用户标识, 如果 PCRF上没有该用户终端的信息, 则回复拒绝消息。
步骤 S44、 获取响应信息中的用户标识。
数据网关收到消息后,如果消息中包含了用户标识,数据网关通过用户标 识获知用户终端的家乡用户寄存器,发送连接消息给该家乡用户寄存器, 该连 接消息中包含用户标识和数据网关标识, 还可以包含 APN。
如果消息中没有包含用户标识,则数据网关还可以采用如图 3中所述的流 程获取用户标识。 进一步的, 当复位网关为服务网关时,该连接重建过程如图 5所示, 包括: 步骤 S51、 接收下行数据包, 发送所述下行数据包给服务网关; 服务网关接收下行数据包,该下行数据包类型可以为用户终端的业务数据 包或者信令消息数据包。 服务网关根据数据包中 GTP 头部的隧道端点标识 ( Tunnel Endpoint Identifier, TEID )无法找到存储的用户上下文 /承载上下文, 服务网关则丟弃该数据包,如果接收的数据包的类型为业务数据包, 则服务网 关发送错误指示消息作为复位指示消息,对于信令消息数据包,服务网关发送 包含拒绝的原因值的响应消息作为复位指示消息,将复位指示消息发送给与接 收的下行数据包对应的数据网关, 即, 与该服务网关相连的数据网关。
步骤 S52、 数据网关接收服务网关发送的复位指示消息, 所述复位指示消 息为所述服务网关依据接收的下行数据包的类型发送的;
步骤 S53、 数据网关依据复位指示消息确定该服务网关复位;
数据网关收到复位指示消息后获知服务网关复位重启。对于收到错误指示 消息的情况, 数据网关可以根据错误指示消息中的信息, 或者进行路径探测, 确定服务网关已经复位。对于收到响应信令消息的情况,数据网关根据消息中 包含的复位计数器确定服务网关复位重启。
步骤 S54、 数据网关获取与服务网关接收的下行数据包对应的用户标识; 由于此时复位的是服务网关,数据网关正常工作, 所以数据网关可以直接 利用其自身存储的服务网关接收的下行数据包对应的 PDN连接获取该下行数 据包对应的用户标识。
步骤 S55、 向与用户标识对应的 HSS发送包含用户标识的连接消息, 连 接消息经由所述 HSS发送给与用户标识对应的移动管理网元, 移动管理网元 依据连接消息重建连接。
所述连接消息中还包含缺省承载标识。所述缺省承载标识为复位的服务网 关上丟失的该接收到的下行数据包对应的 PDN连接的缺省承载的标识。 HSS 将包含有用户标识和缺省承载标识的消息发送给移动管理网元。 本发明公开的又一连接重建的方法如图 6所示,该方法适用于移动通信网 络中的 HSS, 包括:
步骤 S61、 接收数据网关发送的包含用户标识的消息, 该消息由所述数据 网关在其自身或与其相连的服务网关复位,接收下行数据包, 获取的该下行数 据包的用户标识, 依据用户标识发送; 连接消息除包含用户标识外, 当复位网关为数据网关时,还包含数据网关 的数据网关标识, 还可以包含 APN, 当复位网关为服务网关时, 还包含缺省 承载标识。
步骤 S62、 将连接消息发送给移动管理网元, 移动管理网元依据消息重建 连接。
进一步的, 在上述两个步骤间, 还包括: 根据用户标识确认所述用户标识 对应的移动管理网元。
确定移动管理网元后, 将连接消息发送给对应的移动管理网元。
进一步的还可以包括: 向所述数据网关发送回复响应消息的过程, 以使数 据网关可以获知 HSS 已经成功接收到了连接消息。 从而提高连接建立过程的 准确性和可靠性。
HSS作为联通数据网关与移动管理网元的设备,将数据网关发送的连接消 息传送给移动管理网元,使得移动管理网元可以及时获得网关复位的信息, 及 时进行连接重建, 缩短了连接重建所需等待的时间, 降低了因连接中断丟弃的 数据包的数量, 缩短了用户终端重新实现数据通信的等待时间,提升了用户体 验。 本发明公开的又一连接重建的方法如图 7所示,该方法适用于移动通信网 络中的移动管理网元, 包括:
步骤 S71、 接收 HSS依据用户标识发送的, 包含该用户标识的连接消息; 所述消息由数据网关在本数据网关或与本数据网关相连的服务网关复位, 接收到下行数据包后, 获取该下行数据包对应的用户标识,依据所述用户标识 发送给所述 HSS。
当所述数据网关复位时, 所述连接消息还包含: 所述数据网关的数据网关 标识, 进一步的, 还可以包含 APN; 当与所述数据网关相连的服务网关复位 时, 所述连接消息还包含: 与所述下行数据包对应的 PDN连接的缺省承载的 标识。
步骤 S72、 依据连接消息重建连接。
接收到连接消息后, 重建连接。
当数据网关复位时, 依据所述连接消息重建连接的过程包括:
根据数据网关标识获知需要重新激活所述数据网关标识对应的数据网关 的 PDN连接,向与所述用户标识对应的用户终端发送重新激活 PDN连接的指 示消息;
根据数据网关标识获知需要用户重新附着,向与所述用户标识对应的用户 终端发送重新附着的指示消息;
向与所述用户标识对应的用户终端发送重新建立 PDN连接或者重新附着 的指示消息重建连接的过程如图 8所示, 具体包括:
步骤 S81、 移动管理网元收到家乡用户寄存器的消息后, 判断用户标识所 代表的用户终端的状态。 如果为空闲态, 则执行步骤 S82, 如果为连接状态, 则直接执行步骤 S83;
步骤 S82、 寻呼空闲态的用户终端, 触发用户终端发起服务请求流程恢复 无线承载, 然后执行步骤 S83;
步骤 S83、 移动管理网元发送删除会话请求消息给服务网关, 该删除会话 请求消息中包含步骤 S71收到的消息中包含的用户标识和数据网关标识,如果 连接消息中包含了 APN , 该删除会话请求消息还可以包含 APN , 标识的 PDN 连接上下文的缺省 7 载标识。
步骤 S84、 移动管理网元向无线接入网和用户终端发起^载删除流程, 删 除步骤 S83中用户标识和数据网关标识对应的 PDN连接,还或者与 APN对应 的 PDN连接。 移动管理网元在发给用户终端的消息中将原因值设为重新激活 连接请求;
步骤 S85、 用户终端发起 PDN连接建立流程, 重新建立步骤 S84中删除 的 PDN连接;
步骤 S86、 移动管理网元重新选择数据网关, 该数据网关可能为复位重启 后的数据网关,也可能为另外的数据网关, 向服务用户终端的服务网关发送建 立会话请求,服务网关将该消息转发给该数据网关。数据网关和服务网关回复 响应消息, 该过程在服务网关和数据网关上重新建立了 PDN连接;
步骤 S87、 建立无线承载, 以及通知服务网关下行隧道信息。
此流程后,因为复位的数据网关影响的 PDN连接已经在网络内重新建立, 新的数据包到达后, 建立了该 PDN连接的数据网关将数据包在下行通路上转 发给用户终端。
上述流程是用户终端有多个 PDN连接,而只有部分 PDN连接受到复位的 数据网关的影响需要重建的情况, 如果用户终端的所有的 PDN连接都需要重 建, 步骤 S83-S87相应的修改为:
步骤 S83、 移动管理网元发送删除会话请求消息给服务网关, 消息中包含 删除用户标识代表的用户终端的所有上下文的指示。
步骤 S84、 移动管理网元发送分离请求消息给用户终端, 消息中原因值设 为重新附着;用户终端回复相应的响应消息。移动管理网元释放无线信令连接。 步骤 S85、 用户终端发起附着流程;
步骤 S86、 移动管理网元选择服务网关和数据网关, 并在服务网关和数据 网关上重新建立 PDN连接;
步骤 S87、 初始上下文建立、 附着接受和空口承载建立, 通知服务网关下 行隧道信息。
上述附着流程中, 网络内重新建立了用户终端的一个 PDN连接, 如果用 户终端有多个 PDN连接需要重建,后续会发起与步骤 S85-S87—样的 PDN连 接建立流程来重新建立这些 PDN连接。
本实施例并不限定数据网关接收的数据包的个数,如果数据网关上一段时 间内或同时收到了多个 PDN连接的数据包,发送给 HSS的消息中可以包含多 个用户标识, 多个数据网关标识以及多个 APN, 用以表示多个数据包代表的 不同的 PDN连接, 从而指示移动管理网元重新建立起全部的 PDN连接。 除上述向与所述用户标识对应的用户终端发送重新建立 PDN连接或者重 新附着的指示消息重建连接的过程外,本发明还公开了通过恢复与所述数据网 关标识对应的数据网关的 PDN连接的重建 PDN连接的方法, 具体流程如图 9 所示, 包括:
步骤 S91、 向与数据网关相连的服务网关发送恢复消息, 其中至少包含有 预先存储的分配给用户终端的 IP地址;
所述恢复信息还包含: APN、服务网关分配给数据网关的通用无线分组业 务隧道协议 GTP控制面和用户面隧道信息等数据网关恢复该 PDN连接需要的 信息。
步骤 S92、 恢复消息经服务网关转发给数据网关; 步骤 S93、数据网关依据所述恢复消息恢复与用户标识对应的用户终端的 PDN连接。
所述数据网关接收到服务网关转发的恢复消息后,存储恢复消息中携带的 信息, 恢复用户终端的该 PDN连接上下文。 所述恢复消息中携带的信息即为 数据网关上 PDN连接上下文所需的信息。 进一步的, 还包括:
步骤 S94、 数据网关回复响应消息给服务网关;
步骤 S95、 服务网关将收到的响应消息转发给移动管理网元。
步骤 S96、 寻呼空闲态的用户终端, 触发用户终端发起服务请求流程恢复 无线承载。 具体实现时, 对于连接态的用户终端, 移动管理网元可以在步骤
S91前释放用户终端的空口连接, 将用户终端的状态转变为空闲态。
此流程后, 移动管理网元收到的 HSS发来的消息中用户标识, 数据网关 标识和 APN标识的数据网关上丟失的 PDN连接上下文已经在网络内恢复,新 的数据包到达后, 该复位的数据网关将数据包在下行通路上转发给用户终端。
同样, 本实施例并不限定数据网关接收的数据包的个数,如果数据网关上 一段时间内或同时收到了多个 PDN连接的数据包,发送给 HSS的消息中可以 包含多个用户标识, 多个数据网关标识以及多个 APN, 用以表示多个数据包 代表的不同的 PDN连接, 从而指示移动管理网元恢复全部的 PDN连接。
上述方法中, 如果按照 IPv4地址分配过程, 用户终端通过动态主机配置 版本 4 ( Dynamic Host Configuration Protocol Version 4, DHCPv4 ) 方式获得 IPv4地址,那么移动管理网元上无法获知网络分配给用户终端的 IPv4地址, 则 需要将分配给用户终端的 IPv4地址预先存储在移动管理网元上。 其具体的过 程如图 10所示, 包括:
步骤 S101、 用户终端发起附着, PDP上下文激活或者 PDN连接建立流程, 网络内建立起 PDN连接;
步骤 S 102、 用户终端请求 DHCPv4的方式获取 IPv4地址, 用户终端和数据 网关之间通过 DHCPv4流程获取 IPv4地址;
步骤 S103、 数据网关发送通知消息给服务网关, 该通知消息用于通知分 配给用户终端的 IPv4地址, 服务网关将该通知消息转发给移动管理网元, 移 动管理网元和月良务网关回复相应的响应消息;
步骤 S104、 存储所述分配给所述用户终端的 IP地址。
当服务网关和数据网关间的接口协议为 PMIPv6时, 步骤 S102的 DHCPv4 流程中的消息经过服务网关转发, 发送给数据网关或者用户终端; 步骤 S103 中,服务网关发送通知消息给移动管理网元, 该消息用于通知分配给用户终端 的 IPv4地址。 移动管理网元回复响应消息。 当服务网关复位时, 依据所述连接消息重建连接的过程包括:
向与所述用户标识对应的用户终端发送重新激活 PDN连接或者重新附着 的指示消息;
根据数据网关标识获知需要重新激活所述缺省承载的标识对应的 PDN连 接, 向与所述用户标识对应的用户终端发送重新激活 PDN连接的指示消息; 根据缺省 载的标识获知需要用户重新附着,向与所述用户标识对应的用 户终端发送重新附着的指示消息;
其采用向与所述用户标识对应的用户终端发送重新建立 PDN连接或者重 新附着的指示消息的过程与图 8所示过程相似, 但是存在以下区别:
1. 无需执行步骤 S83 ,移动管理网元对于连接态的用户终端在步骤 S81后 直接执行 S84及其之后的步骤, 对于空闲态的用户终端在步骤 S82后直接执行
S84及其之后的步骤;
2. 步骤 S84中通过用户标识和缺省^载标识确定需要删除的 PDN连接;
3. 步骤 S86中, 对于只有部分 PDN连接需要重建的情况, 移动管理网元 选择新的服务网关, 该服务网关可以为复位的服务网关,也可以为其它的服务 网关。 其中, 移动管理网元也可以选择新的数据网关。 移动管理网元在服务网 关和数据网关上重新建立 PDN连接;
其余过程请参考图 8所示其他步骤, 在此不再赘述。 其采用恢复与所述缺省承载标识对应的 PDN连接重建连接的过程如图 11 所示, 包括
步骤 Slll、 判断用户终端的状态, 若为连接态, 则执行步骤 S112, 若为空 闲态, 则执行步骤 S113;
步骤 S112、 释放空口连接, 将用户终端转为空闲态;
步骤 S113、 选择服务网关, 并发送建立会话请求消息给服务网关; 步骤 S114、 服务网关发送更新会话请求消息给数据网关;
步骤 S115、 数据网关回复响应消息给服务网关;
步骤 S116、 服务网关发送建立会话请求消息给移动管理网元;
步骤 S117、移动管理网元寻呼空闲态的用户终端,触发用户终端发起服务 请求流程恢复无线承载。
此流程后, 复位的服务网关影响的 PDN连接已经在网络内恢复。 同时, 本发明公开了一种数据网关, 其结构如图 12所示, 包括: 数据包接 收模块 121、 用户标识获取模块 122和第一连接消息发送模块 123, 其中:
数据包接收模块 121 , 用于接收下行数据包, 用户标识获取模块 122用于获 取与所述下行数据包对应的用户标识; ; 第一连接消息发送模块 123用于向与 所述用户标识对应的家乡用户寄存器 HSS发送包含有所述用户标识的连接消 进一步的, 还包括: 数据包发送模块 124, 用于发送所述下行数据包给服 务网关; 复位指示信息接收模块 125, 用于接收所述服务网关发送的复位指示 消息; 确定模块 126, 用于依据所述复位指示信息确定所述 务网关复位。
进一步的, 用户标识获取模块 122包括: 第一获取单元 1221 , 用于获取 所述下行数据包中的用户终端 IP地址中的用户标识。
进一步的, 还包括: 解密单元 1222, 用于依据密钥解密接口标识中加密 的用户标识, 获取所述用户标识, 或者, 依据所述接口标识中包含的密钥索引 获得加密该用户接口标识包含的用户标识的密钥, 解密所述加密的用户标识, 获取所述用户标识。
用户标识获取模块 122除包括上述单元组合外,还包括另一单元组合,如 图 13所示, 具体包括:
IP地址获取单元 1223 , 用于获取所述下行数据包中的用户终端 IP地址;; 标识请求消息发送单元 1224, 用于发送标识请求消息给策略和计费规则功能 PCRF, 所述标识请求消息中包含所述用户终端 IP地址; 响应消息接收单元 1225, 用于接收所述 PCRF返回的包含所述用户标识的响应信息; 第二获取单 元 1226, 用于获取所述响应信息中的用户标识。
具体应用过程中,可根据实际情况选择相应的单元组合实现用户标识获取 模块的功能。
其各个模块的工作过程如图 2-5中任意流程对应的具体实施方式所示,在 此不再赘述。 本发明同时公开了一种 HSS, 其结构如图 14所示, 包括:
第二连接消息接收模块 141 , 用于接收数据网关发送的包含用户标识的连 接消息, 所述消息由所述数据网关在其自身或与其相连的服务网关复位,依据 所述用户标识发送;
第二消息发送模块 142, 用于将所述消息发送给与所述用户标识对应的移 动管理网元, 所述移动管理网元依据所述消息重建连接。
进一步的, 还包括: 确认模块 143, 用于根据用户标识确认所述用户标识 对应的移动管理网元。
其各个模块的工作过程如图 6对应的具体实施方式所述, 在此不再赘述。 进一步的, 本发明公开了一种移动管理网元, 其结构如图 15所示, 包括: 第一消息接收模块 151和连接重建模块 152, 其中: 第一消息接收模块 151用 于接收家乡用户寄存器 HSS发送的包含用户标识的连接消息, 所述连接消息 由数据网关在本数据网关或与本数据网关相连的服务网关复位后发送给所述 HSS; 连接重建模块 152用于依据所述消息重建连接。
进一步的, 所述连接重建模块 152包括:
指示消息发送单元 1521 , 用于向与所述用户标识对应的用户终端发送重 新建立 PDN连接或者重新附着的指示消息;
恢复单元 1522, 用于当所述数据网关复位时, 恢复与所述数据网关标识 对应的数据网关的 PDN连接, 当所述服务网关复位时, 恢复与所述缺省承载 标识对应的 PDN连接。 其中, 各个模块的工作过程如图 7-11所示流程图对应的具体实施方式所 述, 在此不再赘述。
本发明还公开了一种连接重建系统, 其结构如图 16所示, 包括: 数据网 关 161 , 用于在本数据网关或与本数据网关相连的服务网关复位, 接收下行数 据包后, 获取与所述下行数据包对应的用户标识, 向与所述用户标识对应的家 乡用户寄存器 HSS发送包含所述用户标识的消息; HSS162, 用于接收数据网 关发送的包含用户标识的消息,将所述消息发送给与所述用户标识对应的移动 管理网元;移动管理网元 163 ,用于接收家乡用户寄存器 HSS依据用户标识发 送的, 包含所述用户标识的消息, 依据所述消息重建连接。
本实施例公开的系统中的数据网关的结构如图 12或 13所示, HSS的结构 如图 14所示,移动管理网元如图 15所示,但是本实施例并不限定各个部分的 结构, 其可以根据其功能, 划分为任意结构的功能模块。
本说明书中各个实施例采用递进的方式描述,每个实施例重点说明的都是 与其他实施例的不同之处,各个实施例之间相同相似部分互相参见即可。对于 实施例公开的装置而言, 由于其与实施例公开的方法相对应, 所以描述的比较 筒单, 相关之处参见方法部分说明即可。
专业人员还可以进一步意识到,结合本文中所公开的实施例描述的各示例 的单元及算法步骤, 能够以电子硬件、 计算机软件或者二者的结合来实现, 为 了清楚地说明硬件和软件的可互换性,在上述说明中已经按照功能一般性地描 述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行,取决于 技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来 使用不同方法来实现所描述的功能, 但是这种实现不应认为超出本发明的范 围。 结合本文中所公开的实施例描述的方法或算法的步骤可以直接用硬件、处 理器执行的软件模块, 或者二者的结合来实施。软件模块可以置于随机存储器 ( RAM )、内存、只读存储器( ROM )、电可编程 ROM、电可擦除可编程 ROM、 寄存器、 硬盘、 可移动磁盘、 CD-ROM, 或技术领域内所公知的任意其它形式 的存储介质中。 对所公开的实施例的上述说明,使本领域专业技术人员能够实现或使用本 发明。 对这些实施例的多种修改对本领域的专业技术人员来说将是显而易见 的, 本文中所定义的一般原理可以在不脱离本发明的精神或范围的情况下, 在 其它实施例中实现。 因此, 本发明将不会被限制于本文所示的这些实施例, 而 是要符合与本文所公开的原理和新颖特点相一致的最宽的范围。

Claims

权 利 要 求
1、 一种连接重建方法, 其特征在于, 包括:
接收家乡用户寄存器 HSS发送的包含用户标识的连接消息, 所述连接消 息由数据网关在本数据网关或与本数据网关相连的服务网关复位后发送给所 述 HSS;
依据所述连接消息重建连接。
2、 根据权利要求 1所述的方法, 其特征在于, 当所述数据网关复位时, 所述连接消息还包含: 所述数据网关的数据网关标识;
则所述依据所述连接消息重建连接的过程包括:
根据数据网关标识获知需要重新激活所述数据网关标识对应的数据网关 的 PDN连接,向与所述用户标识对应的用户终端发送重新激活 PDN连接的指 示消息;
根据数据网关标识获知需要用户重新附着,向与所述用户标识对应的用户 终端发送重新附着的指示消息;
或恢复与所述数据网关标识对应的数据网关的 PDN连接。
3、 根据权利要求 2所述的方法, 其特征在于,
所述恢复与所述数据网关标识对应的数据网关的 PDN连接的过程包括: 向与所述数据网关相连的服务网关发送恢复消息,所述恢复消息经所述服 务网关转发给所述数据网关,所述数据网关依据所述恢复消息恢复所述用户标 识对应的用户终端的 PDN连接。
4、 根据权利要求 3所述的方法, 其特征在于, 所述恢复消息包含: 分配 给所述用户终端的网际协议 IP地址、 接入点名字 APN、 服务网关分配给数据 网关的通用无线分组业务隧道协议 GTP控制面和用户面隧道信息, 则恢复与所述数据网关标识对应的数据网关的 PDN连接具体为: 所述数 据网关接收到服务网关转发的恢复消息后,存储恢复消息中携带的信息, 恢复 用户终端的该 PDN连接上下文。
5、 根据权利要求 4所述的方法, 其特征在于, 当所述分配给用户终端的
IP地址为第四代网际协议 IPv4地址时, 所述 IPv4地址为预先存储的 IP地址, 所述预先存储的过程包括:
接收所述服务网关发送的包含所述分配给所述用户终端的 IP地址的通知 消息, 所述通知消息为所述用户终端和所述数据网关之间通过 DHCPv4 流程 获取 IPv4地址后, 所述数据网关发送给所述服务网关;
存储所述分配给所述用户终端的 IPv4地址。
6、 根据权利要求 2所述的方法, 其特征在于, 当与所述数据网关相连的 服务网关复位时, 所述连接消息还包含: 与所述复位的服务网关相连的数据网 关上的分组数据网络 PDN连接的缺省承载的标识,
所述依据所述连接消息重建连接的过程包括:
根据数据网关标识获知需要重新激活所述缺省承载的标识对应的 PDN连 接, 向与所述用户标识对应的用户终端发送重新激活 PDN连接的指示消息; 根据缺省承载的标识获知需要用户重新附着,向与所述用户标识对应的用 户终端发送重新附着的指示消息;
或恢复所述缺省 7 载标识对应的 PDN连接。
7、 一种连接重建方法, 应用于数据网关或与数据网关相连的服务网关复 位后, 其特征在于, 包括: 接收下行数据包;
获取与所述下行数据包对应的用户标识;
向与所述用户标识对应的家乡用户寄存器 HSS 发送包含有所述用户标识 重建连接。
8、 根据权利要求 7所述的方法, 其特征在于, 当所述服务网关复位时, 获取与所述下行数据包对应的用户标识之前还包括:
发送所述下行数据包给服务网关;
接收所述服务网关发送的复位指示消息;
依据所述复位指示消息确定所述服务网关复位。
9、 根据权利要求 8所述的方法, 其特征在于, 接收所述服务网关发送的 复位指示消息之前还包括, 服务网关获知所述下行数据包类型为业务数据包 时, 发送所述复位指示消息, 其中, 所述复位指示消息为错误指示消息; 则依据所述复位指示消息确定所述服务网关复位具体为:
依据所述错误指示消息中的信息,或者进行路径探测确定所述服务网关复 位。
10、 根据权利要求 9所述的方法, 其特征在于, 接收所述服务网关发送的 复位指示消息之前还包括,服务网关获知所述下行数据包类型为信令消息数据 包时,发送所述复位指示消息, 其中所述复位指示消息为包含拒绝原因值的拒 绝响应消息;
则依据所述复位指示消息确定所述服务网关复位具体为:
依据所述拒绝响应消息中包含的复位计数器确定所述服务网关复位。
11、 根据权利要求 7所述的方法, 其特征在于, 当所述数据网关复位时, 所述获取用户标识的过程包括:
获取所述下行数据包中的用户终端 IP地址中的用户标识。
12、 根据权利要求 11所述的方法, 其特征在于, 所述下行数据包中的用 户终端 IP地址为数据网关按照预设方式分配的, 其中所述预设方式为:
将用户标识包含在用户终端的 IP地址的接口标识中, 分配给所述用户终 端;
或将所述用户标识进行加密, 将加密后的用户标识包含在用户终端的 IP 地址的接口标识中, 分配给所述用户终端。
13、 根据权利要求 7所述的方法, 其特征在于, 当所述数据网关复位时, 所述获取用户标识的过程包括:
获取所述下行数据包中的用户终端 IP地址;
发送标识请求消息给策略和计费规则功能 PCRF, 所述标识请求消息中包 含所述用户终端 IP地址;
接收所述 PCRF返回的包含所述用户标识的响应信息;
获取所述响应信息中的用户标识。
14、 一种连接重建方法, 其特征在于, 包括:
接收数据网关发送的包含用户标识的连接消息,所述连接消息由所述数据 网关在其自身或与其相连的服务网关复位后依据所述用户标识发送;
将所述连接消息发送给与所述用户标识对应的移动管理网元,所述移动管 理网元依据所述消息重建连接。
15、 根据权利要求 14所述的方法, 其特征在于, 还包括: 根据用户标识确认所述用户标识对应的移动管理网元。
16、 一种移动管理网元, 其特征在于, 包括:
第一连接消息接收模块, 用于接收家乡用户寄存器 HSS发送的包含用户 标识的连接消息,所述连接消息由数据网关在本数据网关或与本数据网关相连 的服务网关复位后发送给所述 HSS;
连接重建模块, 用于依据所述连接消息重建连接。
17、 根据权利要求 16所述的移动管理网元, 其特征在于, 所述连接重建 模块包括:
指示消息发送单元,用于向与所述用户标识对应的用户终端发送重新建立 PDN连接或者重新附着的指示消息;
恢复单元, 用于当所述数据网关复位时, 恢复与所述数据网关标识对应的 数据网关的 PDN连接, 当所述服务网关复位时, 恢复与所述缺省承载标识对 应的 PDN连接。
18、 一种数据网关, 其特征在于, 包括:
数据包接收模块, 用于接收下行数据包;
用户标识获取模块, 用于获取与所述下行数据包对应的用户标识; 第一连接消息发送模块, 用于向与所述用户标识对应的家乡用户寄存器 HSS发送包含有所述用户标识的连接消息, 以使所述 HSS发送给与所述用户 标识对应的移动管理网元用于重建连接。
19、 根据权利要求 18所述的数据网关, 其特征在于, 还包括:
数据包发送单元, 用于发送所述下行数据包给服务网关;
复位指示消息接收模块, 用于接收所述服务网关发送的复位指示消息; 确定模块, 用于依据所述复位指示消息确定所述服务网关复位。
20、 根据权利要求 18所述的数据网关, 其特征在于, 所述用户标识获取 模块包括:
第一获取单元, 用于获取所述下行数据包中的用户终端 IP地址中的用户 标识。
21、 根据权利要求 18所述的数据网关, 其特征在于, 所述用户标识获取 模块包括:
IP地址获取单元, 用于获取所述下行数据包中的用户终端 IP地址; 标识请求消息发送单元, 用于发送标识请求消息给策略和计费规则功能 PCRF , 所述标识请求消息中包含所述用户终端 IP地址;
响应消息接收单元,用于接收所述 PCRF返回的包含所述用户标识的响应 信息;
第二获取单元, 用于获取所述响应信息中的用户标识。
22、 一种家乡用户寄存器 HSS, 其特征在于, 包括:
第二连接消息接收模块,用于接收数据网关发送的包含用户标识的连接消 息,所述消连接息由所述数据网关在其自身或与其相连的服务网关复位后依据 所述用户标识发送;
第二连接消息发送模块, 用于将所述连接消息发送给与所述用户标识对应 的移动管理网元, 所述移动管理网元依据所述连接消息重建连接。
23、 根据权利要求 22所述的 HSS, 其特征在于, 还包括:
确认模块, 用于根据用户标识确认所述用户标识对应的移动管理网元。
24、 一种连接重建系统, 其特征在于, 包括: 如权利要求 16或 17所述的 移动管理网元、如权利要求 18-21中任意一项所述的数据网关和如权利要求 22 或 23所述的家乡用户寄存器。
PCT/CN2011/070502 2011-01-21 2011-01-21 一种连接重建方法、设备和系统 WO2012097527A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201180000657.2A CN102860116B (zh) 2011-01-21 2011-01-21 一种连接重建方法、设备和系统
PCT/CN2011/070502 WO2012097527A1 (zh) 2011-01-21 2011-01-21 一种连接重建方法、设备和系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/070502 WO2012097527A1 (zh) 2011-01-21 2011-01-21 一种连接重建方法、设备和系统

Publications (1)

Publication Number Publication Date
WO2012097527A1 true WO2012097527A1 (zh) 2012-07-26

Family

ID=46515105

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/070502 WO2012097527A1 (zh) 2011-01-21 2011-01-21 一种连接重建方法、设备和系统

Country Status (2)

Country Link
CN (1) CN102860116B (zh)
WO (1) WO2012097527A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103338525A (zh) * 2013-06-26 2013-10-02 华为技术有限公司 一种网络连接重建方法、相关设备及系统
CN109802980A (zh) * 2017-11-17 2019-05-24 华为技术有限公司 消息交互方法、相关装置及系统

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4333549A3 (en) 2015-12-31 2024-06-05 Huawei Technologies Co., Ltd. Mobility management method, terminal, and base station

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1928126A2 (en) * 2006-12-01 2008-06-04 Fujitsu Ltd. Mobile equipment, base station apparatus ans communication control method
CN101610201A (zh) * 2008-06-20 2009-12-23 大唐移动通信设备有限公司 实现pdn连接释放的方法、装置和系统
CN101720115A (zh) * 2009-03-02 2010-06-02 中兴通讯股份有限公司 一种重建分组数据网络连接的方法及系统
CN101730071A (zh) * 2009-05-19 2010-06-09 中兴通讯股份有限公司 多分组数据网络连接的实现方法及系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101541097B (zh) * 2008-03-19 2013-04-17 华为技术有限公司 恢复承载的方法、装置及系统
CN101547168B (zh) * 2008-03-26 2012-04-25 华为技术有限公司 设备复位通知方法及系统、服务及分组数据网关和移动管理网元

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1928126A2 (en) * 2006-12-01 2008-06-04 Fujitsu Ltd. Mobile equipment, base station apparatus ans communication control method
CN101610201A (zh) * 2008-06-20 2009-12-23 大唐移动通信设备有限公司 实现pdn连接释放的方法、装置和系统
CN101720115A (zh) * 2009-03-02 2010-06-02 中兴通讯股份有限公司 一种重建分组数据网络连接的方法及系统
CN101730071A (zh) * 2009-05-19 2010-06-09 中兴通讯股份有限公司 多分组数据网络连接的实现方法及系统

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103338525A (zh) * 2013-06-26 2013-10-02 华为技术有限公司 一种网络连接重建方法、相关设备及系统
WO2014206247A1 (zh) * 2013-06-26 2014-12-31 华为技术有限公司 一种网络连接重建方法、相关设备及系统
EP3001763A4 (en) * 2013-06-26 2016-07-13 Huawei Tech Co Ltd METHOD FOR RESTORING A NETWORK CONNECTION, ASSOCIATED DEVICE AND SYSTEM
CN103338525B (zh) * 2013-06-26 2017-12-29 华为技术有限公司 一种网络连接重建方法、相关设备及系统
US9893899B2 (en) 2013-06-26 2018-02-13 Huawei Technologies Co., Ltd. Network connection re-establishment method, related device and system
CN109802980A (zh) * 2017-11-17 2019-05-24 华为技术有限公司 消息交互方法、相关装置及系统

Also Published As

Publication number Publication date
CN102860116B (zh) 2016-03-30
CN102860116A (zh) 2013-01-02

Similar Documents

Publication Publication Date Title
US20210274575A1 (en) Application Triggering for a Wireless Device
KR101044685B1 (ko) 리소스를 구축하고 삭제하기 위한 방법 및 네트워크 장비
WO2011144134A1 (zh) 一种信息推送方法、装置和系统
WO2007051407A1 (fr) Systeme de communication mobile ameliore et procede d’enregistrement de terminal correspondant
WO2009115054A1 (zh) 一种获取信息的方法、用户设备及网络设备
US9332426B2 (en) Communication system, communication method, and communication program
WO2014067098A1 (zh) 一种基于移动管理实体池MME Pool的通信方法、设备及系统
US9893899B2 (en) Network connection re-establishment method, related device and system
WO2010133107A1 (zh) 家用基站网关转发消息至家用基站的方法及系统
WO2009105956A1 (zh) 无线通信网络中建立多隧道的控制方法和系统
US9516681B2 (en) Method, device and system for accessing core network by means of non-3GPP access
WO2011011945A1 (zh) 消息发送方法及通用无线分组业务服务支持节点
WO2011032455A1 (zh) 切换管理及切换时用户数据管理的方法、系统和agr
WO2013178160A1 (zh) 无线数据终端及其支持IPv4/IPv6双栈的方法
US9467962B2 (en) Trusted non-3GPP access network element, and method for accessing mobile network and de-attachment
US8634394B1 (en) Mechanism to verify packet data network support for internet protocol mobility
WO2012097527A1 (zh) 一种连接重建方法、设备和系统
JPWO2010052919A1 (ja) ハンドオーバ方法、その方法で用いられる移動端末及びホームエージェント
WO2012013103A1 (zh) 一种网关标识上报的方法及系统
US11108734B2 (en) Error indication processing and system, and device
WO2012089030A1 (zh) 一种多种接入方式接入网络的方法、接入设备和认证设备
WO2012103755A1 (zh) 一种获取终端的身份标识的方法及系统
JP4791402B2 (ja) 移動通信システム及び移動通信プログラム
WO2012159350A1 (zh) 移动节点、其转交地址获取方法、系统及dhcp服务器
KR20100121800A (ko) 이기종망간의 연동을 위한 pmip 기반의 핸드오버 처리 방법

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180000657.2

Country of ref document: CN

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

Ref document number: 11856327

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: 11856327

Country of ref document: EP

Kind code of ref document: A1