WO2007147344A1

WO2007147344A1 - An user plane data transmission restoring method and evolved network entity

Info

Publication number: WO2007147344A1
Application number: PCT/CN2007/001885
Authority: WO
Inventors: Weihua Hu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-06-15
Filing date: 2007-06-15
Publication date: 2007-12-27
Also published as: CN101090358B; CN101090358A

Abstract

A method for restoring user plane data transmission, includes: when the evolved access network receives up-link data packets sent by the user of idle state, it assigns down-link data tunnel to the user, and sends the information of assigned down-link data tunnel together with the user up-link data packets received to the evolved core network through the up-link data tunnel; said evolved core network acquires the information of the down-link data tunnel assigned to the user, and sends the down-link data which is to be sent to the user to the evolved access network through the assigned down-link data tunnel, the data is then sent to the user terminal by the evolved access network. By the present invention, the speed of establishing down-link data tunnel can be increased, the delay for restoring the down-link data transmission can be reduced, and the speed of restoring the user plane data transmission can be improved.

Description

Method for restoring user plane number transmission and evolution network entity

The present invention relates to the field of mobile communication technologies, and in particular, to an evolved mobile communication network system architecture in a third generation mobile communication system, and a method for quickly recovering user plane number transmission under the network system architecture, and an evolved access network entity and an evolved network core Network entity. Background technique

In order to ensure the competitiveness of the 3GPP system, the work of an access technology evolution is being carried out within the 3GPP organization. In particular, in order to enhance the ability of 3GPP systems to handle rapidly growing IP data services, the use of packet technology within 3GPP systems needs to be further enhanced. The most important parts of this type of technology evolution include: reduced latency and latency, higher user data rates, increased system capacity and coverage, and lower overall carrier costs.

As shown in FIG. 1, it is a wireless evolved network architecture proposed in the prior art. The core network of the wireless evolution network mainly includes a Mobility Management Entity (MME), a User Plane Entity (UPE), and an Inter Access System Anchor (Inter AS Anchor,). In the following, it is referred to as mobile anchor point three logical functions, wherein the MME is a mobility management entity, which is responsible for the mobility management of the control plane, including user context and mobile state management, assigning user temporary identity, security functions, etc. In the current Universal Mobile Telecommunication System (UMTS), the control plane part of the Serving GPRS Support Node (SGSN); the UPE is a user plane entity, responsible for initiating paging for downlink data in idle state, management The IP bearer parameters and intra-network routing information are saved, which corresponds to the data plane part of the current SGSN of the current UMTS system; Inter AS Anchor acts as a user plane anchor between different access systems.

In the 3GPP system before the evolution of the network, the attachment process and the activation process of the Packet Data Protocol (PDP) context are two separate processes. After booting up, the terminal first performs a GPRS attach procedure, which mainly includes security procedures and location updates. Attachment completed After that, the terminal does not obtain an IP connection at the same time. Only when the terminal initiates a PDP context activation process, the terminal is provided with an IP address and corresponding configuration parameters. As a result, the delay of the user initiating the service becomes longer, and the process is obviously inconsistent with the requirements of the evolved network.

In order to reduce the reaction time of the mobile terminal from the idle state to the data transmission and reception state, the specification proposes that the System Architecture Evolution (SAE)/long-term evolution (LTE) system combines the network registration with the default IP bearer. When the mobile terminal is attached to the network for the first time, the network allocates an IP and a part of the corresponding bearer resources to the terminal, and whether the air interface resources are allocated remains to be determined. Thereby, the mobile terminal is always online, so that when the terminal needs to perform data service, the network can provide services faster and more quickly. In short, users in an evolved network need to establish a default IP bearer when they attach to the network. Figure 2 depicts a network attach process that includes the following steps:

1. The mobile user's terminal discovers the SAE/LTE access system, and then selects the access system and network.

2. The terminal initiates an attach request to the MME/UPE, and the request includes information previously registered by the user (for example, a temporary identity). If the terminal does not report the user's previous registration information, the request contains the user's permanent identity. The attach request may include information of the default IP access bearer (e.g., user selected IP address or access point name APN).

3a. If the user's previous registration information is reported by the terminal, the MME UPE will use the previous registration information of the user to derive the address of the old MME/UPE that the user last registered, and send the registration information of the user to the old MME UPE to request the user. Information.

3b. The old MME/UPE sends the context of the user to the new MME/UPE, including the permanent identity of the user, security context parameters, and the like.

4. The new MME/UPE performs security authentication on the mobile user or device according to the system configuration. This step is optional.

5. The MME/UPE initiates a registration update to the Home Subscriber Server (HSS), and registers as the MME UPE currently serving the mobile subscriber.

6. The HSS instructs the old MME UPE to delete the context of the mobile user. 7. The HSS confirms the registration of the new MME/UPE. The subscription information of the default IP access bearer, the related QoS policy, and the charging control information are also transmitted to the MME UPE.

8. An Inter AS Anchor is selected. The selection mechanism is not determined. The IP address configuration is determined by the user's preferences or subscription data, or the policy of the HPLMN or VPLMN.

9. Inter AS Anchor performs IP layer configuration based on the determined user IP address. User planes are established and default policy and charging rules are applied. The establishment of the user plane may be initiated by the terminal or initiated by the MME/UPE.

10. The MME/UPE provides the QoS configuration of the default IP bearer to the evolved radio access network (Evolved RAN).

11. The MME UPE sends an attach message of the accepting terminal and allocates a temporary identifier to the terminal, and the default IP bearer related information such as the user IP address is also sent to the terminal. In a roaming scenario, the roaming limit is checked and if it is violated the attachment will be rejected.

12. The terminal confirms that the attachment is successful.

The default IP bearer established by the user attach procedure in the evolved network, except that it may carry IP-based protocol signaling, such as the SIP protocol registered by the IP Multimedia Subsystem (IMS), and may also carry other default QoS. Control the potential business of policies and billing strategies. The QoS difference required by the upper-layer application service data flow is relatively large. When the QoS provided by the default IP bearer cannot meet the QoS requirements of the upper-layer service data flow, the network side or the terminal initiates the establishment of a new dedicated bearer, so as to be the corresponding service data flow. Provide hosting services.

In order to improve the user experience, speeding up the transition of the user terminal from the idle state to the data transfer state is an important requirement of the evolved network. Currently, the method approved by most equipment vendors is that if the user's service data stream requires a dedicated bearer, However, when it is not established, the default IP bearer transmission is first used, and the establishment of the dedicated bearer is performed at the same time, and the corresponding dedicated bearer is established, and then the service data stream is switched to the dedicated bearer for transmission, so as to speed up the number of users. Pass it back or start as soon as possible. It can be seen that the speed of restoring or rebuilding the default IP bearer is critical to speeding up user startup or restoring data transfers.

The default IP bearer is composed of multiple channels or bearers, including between the user terminal and the evolved access network. The air interface carries, the data channel between the evolved access network and the core network user plane entity UPE, the data channel between the core network user plane entity UPE and the mobility anchor Inter AS Anchor. According to the requirements of the specification, in order to reduce the occupation of air interface resources, when the mobile user enters the idle state, the corresponding context of the mobile user in the evolved access network entity will be released, that is, when the user is in an idle state, the default IP bearer The occupied air interface bearer resources and the access network side resources of the data channel between the evolved access network and the core network user plane entity UPE are released. As described above, when the user transitions from the idle state to the data transmission and reception state, the user's default IP bearer needs to be restored as soon as possible. This requires restoring the air interface bearer of the default IP bearer and the evolved access network and the core network user plane entity as soon as possible. Data transmission channel between UPEs.

The disadvantages of the prior art 1 are as follows:

The user terminal needs to restore the default IP bearer availability from the idle state, and the user terminal needs to first interact with the evolved access network to complete the establishment of the air interface resource bearer. Then, the evolved access network needs to be reconstructed. The data transmission channel between the core network user plane entities UPE. The following describes the two possible processes for rebuilding the default IP bearer in the prior art. Referring to FIG. 3, one of the processes for reestablishing an IP bearer from a idle state to a data receiving and receiving state of a user terminal in the prior art includes the following steps:

1. Before the user terminal transmits data, initiate a radio access request, and negotiate with the evolved access network to establish a wireless bearer.

2. After the radio bearer is established, the user terminal sends an uplink data packet. When the user equipment sends a data packet to the evolved access network, the protocol encapsulation of the outer layer of the data packet carries the uplink data channel identification information of the default IP bearer between the evolved access network and the core network user entity UPE, with the GPRS tunnel. protocol

The GPRS Tunneling Protocol (GTP) tunnel is used as an example. The IP address of the uplink tunnel on the UPE side and the tunnel end identifier information assigned by the UPE to the uplink tunnel are sent from the received core network when the user terminal attaches to the network. The attachment is obtained and saved in the message. The evolved access network uses the above information to encapsulate the received user data packet, and transmits the user uplink data to the core network user plane entity UPE through the corresponding uplink data channel between the evolved access network and the core network user plane entity UPE. The UPE forwards the data to the mobility anchor based on the routing information in the user context. Click Inter AS Anchor.

3. The user terminal initiates a service request, and requires the network to restore the default IP bearer for the user, and the message carries the user identity.

4. The evolved access network forwards the service request of the user to the control plane entity MME of the core network according to the user identity information.

5. The control plane entity MME notifies the evolved access network to create a context for the user, and the message carries the default IP bearer related information, such as QoS information, the identifier information of the uplink data channel between the evolved access network and the core network user plane entity UPE. The GTP tunnel is used as an example, including the IP address of the UPE side of the core network user plane entity used by the uplink tunnel, and the tunnel end identifier assigned by the core network user plane entity UPE for the uplink tunnel, and the security parameters required by the access network. Permanent identity (IMSI), etc. When the user is in an idle state, the information is still stored in the context of the user on the MME.

The evolved access network creates a context for the user according to the information received from the MME, and allocates resources required for the default IP bearer, that is, downlink data channel resources between the evolved access network and the core network user plane entity UPE, The GTP tunnel is used as an example, including the IP address of the downlink tunnel access network and the tunnel end identifier, and returns a notification to the MME.

7. The MME saves the received information, and sets the downlink data channel identification information allocated by the access network to take the GTP tunnel as an example, including the IP address and the tunnel end identifier of the downlink tunnel access network side, and notifies the user plane entity UPE. The downlink direction of the data transmission channel between the evolved access network and the core network user plane entity UPE is penetrated.

8. After the downlink data arrives at the UPE, it can be sent to the evolved access network through the downlink data channel between the UPE and the evolved access network, and then forwarded to the user terminal by the access network.

FIG. 4 is a second process of the IP bearer for reestablishing a user terminal from an idle state to a data receiving and receiving state in the prior art, and specifically includes the following steps:

1. Before the user terminal wants to transmit data, it initiates a wireless access request and negotiates with the access network for wireless bearer establishment.

2. After the radio bearer is established, the user terminal sends an uplink data packet. When the user terminal sends a data packet to the evolved access network, the protocol encapsulation of the outer layer of the data packet carries the default IP bearer in the evolved access network. ,

The number of the uplink channel and the channel information of the core network user entity UPE. The GTP tunnel is used as an example. The IP address of the uplink tunnel on the UPE side and the tunnel end identifier information assigned by the UPE to the uplink tunnel are user terminals. When the network is attached, it is obtained and saved from the received attachment message sent by the received core network. The evolved access network uses the above information to encapsulate the received user data packet, and transmits the user uplink data to the core network user plane entity UPE through the corresponding uplink data channel between the evolved access network and the core network user plane entity UPE. The UPE forwards the data to the mobility anchor Inter AS Anchor based on the routing information in the user context.

3. Because the data channel between the core network user plane entity UPE and the mobility anchor InterASAnchor remains, the mobile anchor Inter AS Anchor can forward the user's downlink data to the core network user plane entity UPE, and the UPE receives the downlink data. The packet is located in the context of the user, and it is found that the downlink data channel between the UPE and the evolved access network has not been restored, so the data can only be cached in the UPE first.

4. The UPE notifies the MME to re-establish the default IP bearer, and the message carries the identity of the user.

7. The MME saves the received information, and sets the downlink data channel identification information allocated by the access network to take the GTP tunnel as an example, including the IP address and the tunnel end identifier of the downlink tunnel access network side, and notifies the user plane entity UPE. The downlink direction of the data transmission channel between the evolved access network and the core network user plane entity UPE is penetrated. 8. The UPE sends the buffered data and the subsequent downlink data to the evolved access network through the downlink data channel between the UPE and the evolved access network, and then forwards the data to the user terminal.

In summary, after the user is in the idle state, the context of the user in the UPE of the core network user plane is not released. Therefore, the data channel resources allocated by the UPE for the default IP bearer of the user do not change during the next user access. Reuse. For this reason, the user terminal is required to save the uplink data channel identification information between the UPEs of the core entity after entering the idle state. The GTP tunnel is used as an example, including the IP address and the tunnel end identifier of the core network side of the uplink tunnel, so that the user needs to When the data transmission is performed, the information may be notified to the evolved access network, so that the evolved access network can forward the uplink data of the user normally, and no additional signaling procedure is needed for reconstructing the default IP bearer of the user in the evolved access network and The upstream data channel between the core network user plane entity UPE. The above two methods have applied this idea to achieve the purpose of speeding up the user's uplink data transmission. The difference between the two methods is only the timing of reconstructing the downlink data channel. The process shown in Figure 3 is to initiate the reconstruction of the downlink data channel through the user terminal. The process shown in Figure 4 is the downlink data triggering reconstruction of the downlink data channel.

As for the reconstruction of the downlink data channel between the evolved access network and the core network user plane entity UPE, the key needs the core network user plane UPE to know that the evolved access network is the channel identifier information allocated by the user's default IP bearer downlink data, to GTP. For example, the tunnel includes the IP address of the downlink tunnel access network and the tunnel end identifier, so that the core network user plane entity UPE can correctly encapsulate and forward the downlink data to the correct downlink data channel. However, when the user enters the idle state, the evolved access network releases the user's context, and the corresponding resources are released, and may be occupied by other users, so even if the information is still stored in the user of the core network user plane UPE In the context, it is also not reusable. When the user terminal accesses again, it must be reallocated by the evolved access network and notified to the user plane entity UPE of the core network. For this reason, as described in the above two methods, additional signaling is required to control the downlink data channel between the evolved access network and the core network user plane entity UPE. The recovery of the transmission increased the delay. Summary of the invention The embodiment of the invention provides a method for restoring the number of user planes and an evolved network entity, which is used to solve the problem that the recovery delay of the downlink data transmission of the user existing in the prior art is long.

A method for restoring the number of user planes, including:

When receiving the uplink data packet sent by the idle state user, the evolved access network allocates a downlink data channel to the user, and sends the allocated downlink data channel information together with the received user uplink data packet to the evolved network core network through the uplink data channel. ;

The evolved network core network obtains the downlink data channel information that is allocated to the user, and the downlink data that needs to be forwarded to the user is sent to the evolved access network through the allocated downlink data channel, and is sent by the evolved access network to the user terminal.

An evolved access network entity, including:

a downlink data channel allocation unit, configured to allocate a downlink data channel to the user and send the uplink data packet when the idle state user sends the uplink data packet;

The encapsulating unit is configured to receive the downlink data channel information sent by the downlink data channel allocation unit, and send the downlink data channel information together with the uplink data packet sent by the user to the evolved network core network through the uplink data channel.

An evolved network core network entity, including:

a downlink data channel information acquiring unit, configured to acquire, from the uplink data packet, downlink data channel information that is allocated to the user by the evolved access network, and send the information;

And a sending unit, configured to receive downlink data channel information sent by the downlink data channel information acquiring unit, and send downlink data that needs to be forwarded to the user to the progress access network by using the downlink data channel.

According to the embodiment of the present invention, when the evolved access network receives the uplink data packet sent by the idle state user, the downlink data channel is allocated to the user, and the allocated downlink data channel information and the received user uplink data packet are used together through the uplink data channel. The egress network core network obtains the downlink data channel information allocated to the user, and the downlink data that needs to be forwarded to the user is sent to the evolved access network through the allocated downlink data channel, and is sent by the evolved access network. Give the user terminal. In this way, there is no need to establish a downlink data channel through additional signaling, which shortens the downlink data recovery. The delay speeds up the recovery of the user's face number. DRAWINGS

1 is a schematic diagram of a prior art wireless evolution network architecture;

2 is a flow chart of a network attachment of a terminal in the prior art;

3 is a signaling flow chart of a prior art user terminal from an idle state to a data transceiving state; FIG. 4 is a second flow chart of signaling of a prior art user terminal from an idle state to a data transceiving state; Embodiments of the present invention are a signaling flow chart of a user terminal from an idle state to a data transceiving state;

FIG. 6 is a schematic structural diagram of an evolved access network entity according to an embodiment of the present disclosure;

FIG. 7 is a schematic structural diagram of an evolved network core network entity according to an embodiment of the present invention. detailed description

The method for restoring the number of user planes provided by the embodiment of the present invention includes:

The evolved network core network obtains the downlink data channel information allocated to the user, and the downlink data that needs to be forwarded to the user is sent to the evolved access network through the allocated downlink data channel, and is sent by the evolved access network to the user terminal.

In a specific implementation, the downlink data channel information may be encapsulated into a data channel protocol header of the outer layer of the user data packet. (If the protocol used by the data channel includes an extended cell domain, the extended cell domain may be used to encapsulate the downlink data. Channel information; if the protocol used in the data channel does not include an extended cell domain, the protocol extension is used to add a new cell field to carry the downlink data channel information, and the encapsulated downlink data channel information and the user's The uplink data packets are sent together to the user plane entity in the evolved network core network.

The above method of the embodiment of the present invention will be described in detail below with reference to the accompanying drawings. Referring to FIG. 5, it is assumed that the three functional entities MME, UPE, and Inter AS ''Anchor in the evolved network core network are mutually independent network nodes, and the foregoing signaling method is used as follows:

1. Before the user terminal transmits the data, initiate a wireless access request, and negotiate with the evolved access network to establish a wireless bearer.

2. After the radio bearer is established, the user terminal sends an uplink data packet. When the user equipment sends a data packet to the evolved access network, the protocol encapsulation of the outer layer of the data packet carries the uplink data channel identification information of the default IP bearer between the evolved access network and the core network user entity UPE, and the GTP tunnel is used. For example, the IP address of the uplink tunnel on the UPE side and the tunnel end identifier information allocated by the UPE for the uplink tunnel are obtained and saved from the received attachment message sent by the core network when the user terminal attaches to the network. of.

3. The evolved access network saves the identifier information of the received uplink data channel, and according to the above information, encapsulates the received user data packet and forwards it to the corresponding uplink data channel. At this point, the upstream direction of the user's default IP bearer has been penetrated. At the same time, the evolved access network allocates channel resources of the downlink data channel between the evolved access network and the core network user plane entity UPE for the default IP bearer of the user, and encapsulates the allocated downlink data channel information into a protocol header used by the data channel. The encapsulated data is transferred to the UPE through the upstream data channel.

The following upper/downlink data channel is a GTP tunnel as an example to specify how to carry the downlink data channel information allocated to the user through the user uplink data packet.

When the uplink/downlink data channel is a GTP tunnel, the extended data field included in the GTP header can be used to encapsulate the downlink data channel information.

As shown in Table 1 below, the GTP header format is GTP V1:

Table 1 : Bi ts (bits)

Octets (word 2

Section)

1 Version PN (N-PDU appears marked)

Message Type

Length ( ' Octet) (length field from low to high first byte)

Length (2 ^nd Octet) (length field from low to high second byte)

Tunnel Endpoint Ident if ier ( ^ι Octet) (the first byte of the tunnel end identification field from low to high)

Tunnel Endpoint Ident if ier (2 ^nd Octet) (the second byte of the tunnel end identification field from low to high)

Tunnel Endpoint Ident if ier (3 ^rd Octet) (the third byte of the tunnel end identification field from low to high)

Tunnel Endpoint Ident if ier (4 ^,h Octet) (the fourth byte of the tunnel end identification field from low to high)

Sequence Number (l ^sl Octet) " ^A) S flag (the serial number field is from the low to the first byte)

10 Sequence Number (2 ^ηί Octet) ^{0 4)} (The serial number field is from the low to the second byte)

11 N-PDU Number ² ' ⁴⁾ (Packet Data Single Sequence Number)

12 Next Extens ion Header Type3) 4) (Next extension header type)

The tail of the GTP header can contain an extended header field. The fields of the extended header are as shown in Table 2, where the length is 4 bytes, that is, the extended header length must be an integer multiple of 4 bytes:

Table 2:

A GTP header can contain multiple extension fields. The extension fields allowed in the current GTP header are shown in the table.

Next Extension Header Field Value Type of Extension Header

(the value of the next extended header field)

0000 0000 No more extens ion headers

Head, the last extension header)

0000 0001 MBMS support indica t ion (MBMS to indication)

1100 0000 PDCP PDU number (PDCP packet data unit number)

1100 0001 Suspend Request

1100 0010 Suspend Response (suspend response) In order to support the method provided by the present invention, a new GTP extension header type "Downlink Tunnel ID" needs to be added, and its type value is defined as shown in Table 4 below:

Table 4:

Table 5 is a specific example of the new GTP extension header format of the present invention.

Obviously, when the data channel between the evolved access network and the core network user plane entity UPE adopts the GTP protocol, as long as the extended header is filled in the GTP packet sent by the evolved access network to the core network user plane entity UPE, Downlink data channel information (including evolved access) allocated by the evolved access network The network side IP address and the tunnel end identification information are notified to the core network user plane entity UPE.

After the UPE receives the data packet, the UPU decapsulates the data channel protocol of the outer layer of the user data packet, and parses the downlink data channel information allocated by the evolved access network for the default IP bearer of the user from the data channel protocol header, and saves the information to the downlink data channel. In the context of the user, the parsed data payload is then re-encapsulated according to the data channel format between the core network user plane entity UPE and the mobility anchor Inter AS Anchor, and the data is forwarded to the mobility anchor according to the routing information of the user context. Point Inter AS Anchor

5. At this point, the downstream direction of the user's default IP bearer has also been penetrated. After that, the downlink data is sent from the mobility anchor Inter AS Anchor to the core network user plane entity UPE UPE, and the downlink data is forwarded to the evolved access network according to the downlink data channel information between the evolved access network and the UPE saved in the user context. The evolved access network forwards the data to the user terminal.

6. The core network user plane entity UPE receives the uplink data of the user forwarded by the evolved access network and performs the forwarding process, and notifies the control plane entity of the core network to recover the data transmission of the MME user plane, and initiates a bearer establishment indication to the control plane entity MME. .

The control plane entity MME learns from the notification of the user plane entity UPE that the user plane number is restored, and initiates a process of reestablishing the user context to the evolved access network, requesting the evolved access network to create a context for the user, and the message carries the default IP bearer. Relevant information, such as QoS information, security parameters required by the access network, permanent identity of the user (IMSI), etc. When the user is in an idle state, the information is still stored in the context of the user on the MME.

8. The evolved access network creates a context for the user according to the information received from the control plane entity MME, and feeds back the result to the control plane entity MME.

Steps 6 to 8 in the above embodiment can be performed in synchronization with steps 4 to 5, without a sequential relationship. In the foregoing embodiment, the control plane entity MME and the user plane entity UPE in the core network are independent network nodes, but the present invention is also applicable to the case where the MME and the UPE are located in the same network node. When the user plane entity UPE and the control plane entity MME are mutually independent network nodes, the external interface is connected; when the user plane entity UPE and the control plane entity MME are located in the same network node, the two interact through the internal interface.

In addition, the network location of the mobile anchor Inter AS Anchor does not affect the applicability of the present invention, If the mobile anchor Inter AS Anchor and the user plane entity UPE coexist in the same network node are not excluded. When the user plane entity UPE and the mobility anchor Inter AS Anchor are mutually independent network nodes, they are connected through an external interface; when the user plane entity UPE and the mobility anchor Inter AS Anchor are located in the same network node, the two are internally Interface interaction.

The method for restoring the number of user planes is provided according to the foregoing embodiment of the present invention. An embodiment of an evolved access network entity structure, as shown in FIG. 6, includes:

The downlink data channel allocating unit 101 is configured to allocate a downlink data channel and send the uplink data channel to the user when receiving the uplink data packet sent by the idle state user;

The encapsulating unit 102 is configured to receive the downlink data channel information sent by the downlink data channel allocating unit 101, and send the downlink data channel information together with the uplink data packet sent by the user to the evolved network core network through the uplink data channel.

A method for restoring the number of user planes is provided according to the foregoing embodiment of the present invention. An embodiment of an evolved network core network entity, as shown in FIG. 7, includes:

The downlink data channel information obtaining unit 201 is configured to obtain, from the uplink data packet, downlink data channel information that is allocated to the user by the evolved access network, and send the information;

The sending unit 202 is configured to receive the downlink data channel information sent by the downlink data channel information acquiring unit 201, and send the downlink data that needs to be forwarded to the user to the evolved access network through the downlink data channel.

In summary, according to the embodiment of the present invention, when the evolved access network receives the uplink data packet sent by the idle state user, the downlink data channel is allocated to the user, and the allocated downlink data channel information and the received user uplink data packet are obtained. The uplink data channel is sent to the evolved access network through the uplink data channel, and the downlink data channel that needs to be forwarded to the user is sent to the evolved access network through the allocated downlink data channel. The evolved access network is sent to the user terminal. In this way, the downlink data channel is not newly established by using additional signaling, which shortens the delay of downlink data transmission recovery, and speeds up the recovery of the user plane number transmission. The spirit and scope of the invention. Thus, if such modifications and variations of the present invention are claimed in the present invention The invention is also intended to cover such modifications and variations within the scope of the invention.

Claims

Rights request

A method for restoring the number of user planes, characterized in that it comprises:

The method according to claim 1, wherein the transmitting the downlink data channel information and the received user uplink data packet to the evolved network core network through the uplink data channel, the method specifically includes:

The downlink data channel information is encapsulated into a data channel protocol header of the outer layer of the user data packet, and sent to the user plane entity in the evolved network core network together with the uplink data packet of the user.

The method of claim 2, wherein the evolved network core network obtains downlink data channel information that is allocated to the user, and specifically includes:

The user plane entity releases the data channel protocol encapsulation of the outer layer of the user data packet, parses the downlink data channel information from the data channel protocol header, and saves the parsed downlink data channel information into the context of the user;

The downlink data that needs to be forwarded to the user is sent to the access access network through the allocated downlink data channel, and specifically includes:

The user plane entity forwards the downlink data of the user to the evolved access network according to the downlink data channel information saved in the user context.

The method according to claim 3, further comprising the following steps: after receiving the uplink data packet forwarded by the evolved access network, the user plane entity sends a notification to the control plane entity of the evolved network core network. The message informs the user of the face number recovery;

After receiving the notification message, the control plane entity initiates a re-establishment of the user to the evolved access network. The following process;

The evolved access network creates a context for the user and returns a response message to the control plane entity.

The method according to claim 4, wherein the user plane entity forwards the downlink data of the user to the evolved access network, and the user plane entity according to the downlink data channel information saved in the user context. After receiving the uplink data packet forwarded by the evolved access network, the notification message is sent to the control plane entity of the evolved network core network and executed simultaneously.

The method according to claim 4, wherein the user plane entity and the control plane entity are mutually independent network nodes, and are connected through an external interface; or

The user plane entity and the control plane entity are located on the same network node, and the two interact through the internal interface.

The method according to any one of claims 1-6, wherein the uplink/downlink data channel is a GTP tunnel; and the downlink data channel information is encapsulated in a newly added GTP extension header field.

The method of claim 7, wherein the downlink data channel information encapsulated in the newly added GTP extension header field comprises: an IP address and a tunnel of an evolved access network side used by the downlink tunnel End identification.

The method of claim 8, wherein the new GTP extension header has a length of 12 bytes, and the specific format is:

The extended header length identifier occupies the first byte;

The IP address information on the evolved access network side occupies 4 bytes.

The tunnel end identifier occupies 4 bytes.

Invalid padding character occupies 2 bytes;

The field value corresponding to the extended header type occupies the last 1 byte.

10. An evolved access network entity, comprising:

The encapsulating unit is configured to receive the downlink data channel information sent by the downlink data channel allocation unit, and send the downlink data channel information together with the uplink data packet sent by the user through the uplink data channel The channel is sent to the evolved network core network.

11. An evolved network core network entity, characterized by comprising: