WO2022042440A1 - User plane data transmission method and network node - Google Patents

Abstract

The embodiments of the present application disclose a user plane data transmission method and a network node, which can solve the problem of large delay of user plane data transmission. Said method comprises: a first network node receiving a first message from a terminal, the first message comprising a recovery identifier of the terminal and user plane data; and the first network node sending a second message, the second message comprising a UE context identifier of the terminal, and the second message being used for at least one of the following: the first network node acquiring UE context forwarded by a second network node; the first network node forwarding, to the terminal, a radio resource control (RRC) message forwarded by the second network node; and the first network node forwarding data to the second network node.

Description

User plane data transmission method and network node

cross reference

This application claims the priority of the Chinese patent application with the application number 202010860022.0 and the invention title "User Plane Data Transmission Method and Network Node" filed in China on August 24, 2020, the entire contents of which are incorporated by reference in in this application.

technical field

The present application belongs to the field of communication technologies, and in particular relates to a user plane data transmission method and a network node.

Background technique

For a terminal that supports small data transmission and is in an inactive state, small data (user plane data) transmission is usually implemented by initiating a Radio Resource Control (Radio Resource Control, RRC) recovery process. Specifically, the terminal can multiplex the encrypted user plane data etc. in a Media Access Control Protocol Data Unit (MAC PDU) and send it to the network node. If the network node that receives the terminal MAC PDU does not save the user context (UE context) of the terminal, the network node cannot decrypt the user plane data, nor can it forward the user plane data to the user plane function (UPF) At this time, the network node is in a waiting state, and it is impossible to determine whether to discard the user plane data or perform other actions, and the user plane data transmission delay is relatively large.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a user plane data transmission method and a network node, which can solve the problem of long delay in user plane data transmission.

In a first aspect, a method for transmitting user plane data is provided, the method comprising: a first network node receiving a first message from a terminal, the first message including a recovery identifier of the terminal and user plane data; the The first network node sends a second message, where the second message includes the user context identifier of the terminal; the second message is used for at least one of the following: the first network node obtains the user transferred from the second network node context; the first network node forwards the radio resource control RRC message forwarded by the second network node to the terminal; the first network node forwards the data to the second network node.

In a second aspect, a method for transmitting user plane data is provided, the method comprising: a second network node receiving a second message from a first network node, the second message including a user context identifier of a terminal; the first The two messages are used for at least one of the following: the first network node obtains the user context forwarded from the second network node; the first network node forwards the RRC message forwarded by the second network node to the terminal; The first network node forwards the data to the second network node.

In a third aspect, a first network node is provided, including: a receiving module for receiving a first message from a terminal, where the first message includes a recovery identifier of the terminal and user plane data; a sending module for sending a second message, where the second message includes the user context identifier of the terminal; the second message is used for at least one of the following: the first network node obtains the user context transferred from the second network node; the first network node obtains the user context transferred from the second network node; A network node forwards the RRC message forwarded by the second network node to the terminal; the first network node forwards the data to the second network node.

In a fourth aspect, a second network node is provided, comprising: a receiving module configured to receive a second message from the first network node, where the second message includes a user context identifier of a terminal; the second message is used for At least one of the following: the first network node obtains the user context forwarded from the second network node; the first network node forwards the RRC message forwarded by the second network node to the terminal; the first network node forwards the RRC message forwarded by the second network node to the terminal; The network node forwards the data to the second network node.

A fifth aspect provides a first network node, the first network node comprising a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being The processor implements the method according to the first aspect when executed.

In a sixth aspect, a second network node is provided, the second network node comprising a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being The processor implements the method of the second aspect when executed.

In a seventh aspect, a readable storage medium is provided, on which a program or an instruction is stored, and when the program or instruction is executed by a processor, the method described in the first aspect or the second the method described in the aspect.

In an eighth aspect, a computer program product is provided, the computer program product comprising a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the When executed by the processor, the method described in the first aspect or the method described in the second aspect is realized.

In a ninth aspect, a chip is provided, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement the method according to the first aspect , or implement the method described in the second aspect.

In this embodiment of the present application, the first network node sends a second message after receiving the first message from the terminal, where the first message includes the recovery identifier of the terminal and user plane data, and the second message includes the user context identifier of the terminal, The second message is used for at least one of the following: the first network node obtains the user context forwarded from the second network node; the first network node forwards the RRC message forwarded by the second network node to the terminal; the first network node forwards data to the second network node. Based on the above-mentioned second message, the first network node can forward user plane data or forward RRC messages to the terminal, so as to reduce the transmission delay of the user plane data and reduce the waiting time of the terminal at the same time.

Description of drawings

1 is a block diagram of a wireless communication system according to an embodiment of the present application;

2 is a schematic flowchart of a method for transmitting user plane data according to an embodiment of the present application;

3 is a schematic flowchart of a method for transmitting user plane data according to a specific embodiment of the present application;

4 is a schematic flowchart of a method for transmitting user plane data according to another specific embodiment of the present application;

5 is a schematic flowchart of a method for transmitting user plane data according to another embodiment of the present application;

6 is a schematic structural diagram of a first network node according to an embodiment of the present application;

7 is a schematic structural diagram of a second network node according to an embodiment of the present application;

8 is a schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a network side device according to an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the protection scope of the present application.

The terms "first", "second" and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and "first", "second" distinguishes Usually it is a class, and the number of objects is not limited. For example, the first object may be one or multiple. In addition, "and/or" in the description and claims indicates at least one of the connected objects, and the character "/" generally indicates that the associated objects are in an "or" relationship.

It is worth noting that the technologies described in the embodiments of this application are not limited to Long Term Evolution (LTE)/LTE-Advanced (LTE-Advanced, LTE-A) systems, and can also be used in other wireless communication systems, such as code Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (Orthogonal Frequency Division Multiple Access, OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies. However, the following description describes a New Radio (NR) system for example purposes, and uses NR terminology in most of the following description, these techniques can also be applied to applications other than NR system applications, such as the 6th generation (6th ^generation ). Generation, 6G) communication system.

FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied. The wireless communication system includes a terminal 11 and a network-side device 12 . Wherein, the terminal 11 may also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital computer Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device (VUE), pedestrian terminal (PUE) and other terminal-side devices, wearable devices include: bracelets, headphones, glasses, etc. It should be noted that, the embodiment of the present application does not limit the specific type of the terminal 11 . The network side device 12 may be a base station or a core network, wherein the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Next Generation Node B (gNB), Home Node B, Home Evolved Node B, WLAN Access point, WiFi node, Transmitting Receiving Point (TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. In the application embodiments, only the base station in the NR system is used as an example, but the specific type of the base station is not limited.

The method for transmitting user plane data and the network node provided by the embodiments of the present application will be described in detail below through specific embodiments and application scenarios with reference to the accompanying drawings.

As shown in FIG. 2 , an embodiment of the present application provides a method 200 for transmitting user plane data. The method can be executed by a first network node. In other words, the method can be implemented by software or hardware installed in the first network node. Executed, the method includes the following steps.

S202: The first network node receives a first message from the terminal, where the first message includes a recovery identifier of the terminal and user plane data.

In this embodiment, the terminal may be in an INACTIVE mode and initiate a small data transmission process, the first network node may be the network node where the terminal initiates the small data transmission process, and the first network node does not save the user context ( UE context). The second network node mentioned later stores the user context of the terminal.

In one scenario, the terminal receives an RRC release (Release) message on the second network node and is converted from a connected state (CONNECTED) to an inactive state (INACTIVE), and the second network node stores the user of the terminal. context. Optionally, the second network node may be the anchor node of the terminal.

In this embodiment, the user plane data included in the first message may be data radio bearer (Data Radio Bearer, DRB) data. Optionally, the user plane data may also be uplink data.

Optionally, the first message further includes or indicates at least one of the following: 1) the reason for triggering the recovery process; 2) the terminal expects to perform low-latency small data transmission; 3) the terminal estimates that there will be subsequent downlink data transmission; 4) the terminal will follow up There is upstream data to send.

Optionally, the above-mentioned triggering reason for the recovery process may include one of the following: small data transmission; delay-sensitive small data transmission; urgent small data transmission; high-priority small data transmission.

Through the triggering cause of the recovery process, the first network node or the second network node can know what type of service data the terminal triggers to trigger the small data transmission process. For example, if the reason for triggering the recovery process carried by the terminal in the first message is the transmission of delay-sensitive small data, the first network node or the second network node can know that the user plane data carried in the first message of the terminal is from the time delay sensitive business.

S204: The first network node sends a second message, where the second message includes the user context identifier of the terminal; the second message is used for at least one of the following: the first network node obtains the user context transferred from the second network node; the first network node The radio resource control (Radio Resource Control, RRC) message forwarded by the second network node is forwarded to the terminal; the first network node forwards the data to the second network node.

In one example, the second message is used to instruct the first network node to forward data to the second network node. The data mentioned in this example may be uplink data and/or downlink data, and the data includes the user plane data mentioned in S202.

In this example, the first network node may receive the uplink data of the terminal and forward it to the second network node, and the second network node may forward it to a user plane function (UPF); in this example, the first network node may also The downlink data from the second network node is received and forwarded to the terminal.

In another example, the second message is used for instructing the first network node to forward data to the second network node, and for the first network node to obtain the user context forwarded from the second network node.

In yet another example, the second message is used for the first network node to forward the RRC message forwarded by the second network node to the terminal. Optionally, the RRC message may be an RRC release message, and when the RRC message is an RRC release message, it usually indicates that the second network node does not allow user plane data forwarding.

Optionally, the second message further includes or indicates at least one of the following: 1) the reason for triggering the recovery process; 2) the terminal expects to perform low-latency small data transmission; 3) the terminal estimates that there will be subsequent downlink data transmission; 4) the terminal will follow up There is uplink data to send; 5) duration information, where the duration information is used to indicate the duration for establishing a connection between the first network node and the terminal. In this way, the second network node can decide to propose forwarding downlink data and/or forward downlink data according to the duration information, thereby ensuring that the downlink data is sent to the first network node within the time period corresponding to the duration information.

Optionally, the above-mentioned triggering reason for the recovery process may include one of the following: small data transmission; delay-sensitive small data transmission; urgent small data transmission; high-priority small data transmission.

In the method for transmitting user plane data provided by this embodiment of the present application, after receiving a first message from a terminal, a first network node sends a second message, where the first message includes a recovery identifier of the terminal and user plane data, and the second message includes the User context identifier of the terminal, the second message is used for at least one of the following: the first network node obtains the user context transferred from the second network node; the first network node forwards the RRC message transferred by the second network node to the terminal ; The first network node forwards the data to the second network node. Based on the above-mentioned second message, the first network node can forward user plane data or forward RRC messages to the terminal, so as to reduce the transmission delay of the user plane data and reduce the waiting time of the terminal at the same time.

In an embodiment (hereinafter referred to as Embodiment 1 for the convenience of distinction), after the first network node sends the second message in Embodiment 200, the method further includes the following step: the first network node receives a message from the first network node. the third message of the second network node, the third message includes first indication information; the first indication information indicates one of the following: 1) do not relocate the user context of the terminal; 2) do not The user context of the terminal is relocated and data forwarding is performed; 3) data forwarding and/or offloading are performed.

In Embodiment 1, the second network node does not forward the user context of the terminal to the first network node.

Optionally, the above-mentioned first indication information may be obtained through the cause value carried in the third message; the first network node may also obtain the first indication information according to the indication field carried in the third message; the first network node may further The first indication information may be obtained according to the message type of the third message.

Optionally, after the first network node receives the third message from the second network node, the method further includes: the first network node sends a fourth message according to the first indication information, the first The four messages are used to indicate that the first network node proposes to perform uplink data forwarding.

Optionally, there is a one-to-one correspondence between uplink data forwarding and logical channels; wherein, uplink data forwarding is performed according to each logical channel (per LCH), and uplink data forwarding tunnels are established according to the granularity (LCH level) of the LCH. /maintenance/modification/removal, the uplink data forwarding tunnel forwards the radio link layer control protocol data unit (Radio Link Control Protocol Data Unit, RLC PDU).

Optionally, there is a one-to-one correspondence between uplink data forwarding and radio link control (Radio Link Control, RLC) bearing; wherein, uplink data forwarding is carried out according to each logical channel (per RLC bearing), and the uplink data forwarding tunnel is The establishment/maintenance/modification/removal is carried out according to the granularity of the RLC bearer, and the packet data convergence protocol protocol data unit (Packet Data Convergence Protocol Protocol Data Unit, PDCPPDU) is forwarded in the uplink data forwarding tunnel.

The fourth message may include at least one of the following: 1) the identity of the terminal. 2) One or more logical channel information corresponding to the user plane data. 3) One or more RLC bearer information (for example, RLC bearer ID) corresponding to the user plane data; wherein, there is a one-to-one mapping relationship between the RLC bearer information and the logical channel information (for example, the mapping relationship may be According to the agreement, logical channel information 1 corresponds to RLC bearer information 1); the RLC bearer information may also be logical channel information. 4) An uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding.

In an embodiment (hereinafter referred to as Embodiment 2 for ease of distinction), after the first network node sends the second message in Embodiment 200, the method further includes: the first network node receives a message from the first network node. The fifth message of the second network node, the fifth message includes the user context of the terminal and second indication information, and the second indication information indicates one of the following: 1) Do not relocate the user context of the terminal; 2) Do not relocate the user context of the terminal and perform data forwarding; 3) Perform data forwarding and/or offloading.

In the second embodiment, the second network node forwards the user context of the terminal to the first network node.

Optionally, the above-mentioned second indication information may be obtained through the cause value carried in the fifth message; the first network node may also obtain the second indication information according to the indication field carried in the fifth message; the first network node may further The second indication information may be obtained according to the message type of the fifth message.

In Embodiment 2, after the first network node receives the fifth message from the second network node, the method further includes: the first network node sends a sixth message according to the second indication information , and the sixth message is used to indicate that the first network node proposes to perform uplink data forwarding.

Optionally, there is a one-to-one correspondence between the upstream data forwarding and a quality of service (Quality of Service, QoS) flow or a protocol data unit (Protocol Data Unit, PDU) session.

The sixth message may include at least one of the following: 1) one or more QoS flow information corresponding to the user plane data; 2) one or more PDU session information corresponding to the user plane data; 3) uplink Forwarding proposal field, where the upstream forwarding proposal field is used to propose upstream data forwarding.

In the above embodiment 1, after the first network node sends the fourth message; or in the above embodiment 2, after the first network node sends the sixth message, the following steps may be further included: the first The network node receives a seventh message from the second network node, where the seventh message is used to establish an uplink data forwarding tunnel.

For example, the seventh message is used by the first network node to establish an uplink data forwarding tunnel towards the second network node, and through the uplink data forwarding tunnel, the first network node can forward the user plane data carried in the first message to the second network node , and then forwarded to the UPF by the second network node to reduce the transmission delay of user plane data.

Optionally, the seventh message may include at least one of the following: 1) the identity of the terminal; 2) one or more logical channel information; 3) one or more QoS flow information; 4) one or more PDUs Session information; 5) Transport layer information associated with Xn user plane transmission, the transport layer information is used to forward uplink data; 6) One or more RLC bearer information.

Specifically, on the basis of the above-mentioned first embodiment, the above-mentioned seventh message may include at least one of 1), 2), 5) and 6); on the basis of the above-mentioned second embodiment, the above-mentioned seventh message may include 1 ), at least one of 3), 4) and 5).

In other embodiments, if the second network node does not allow forwarding of uplink data, in the first embodiment, after the first network node sends the fourth message; or in the second embodiment, all After the first network node sends the sixth message, it may further include the following steps: the first network node receives an eighth message from the second network node, and the eighth message may include an RRC release message; the first network node receives an eighth message from the second network node. A network node sends the RRC release message to the terminal.

Optionally, after the first network node receives the seventh message from the second network node, the method further includes: the first network node receives the ninth message from the second network node, the The ninth message indicates that the second network node proposes to forward downlink data; the first network node sends a tenth message, where the tenth message is used to establish a downlink data forwarding tunnel.

In this embodiment, the second network node may further establish a downlink data forwarding tunnel towards the first network node, so that the second network node may also forward the downlink data from the UPF to the first network node, and then the first network node can forward the downlink data from the UPF to the first network node. The node forwards to the terminal.

Optionally, the ninth message includes at least one of the following: the identity of the terminal; one or more logical channel information; one or more RLC bearer information; one or more QoS flow information; one or more PDU session information; downlink forwarding proposal field, the downlink forwarding proposal field is used to propose downlink data forwarding.

Optionally, the tenth message includes at least one of the following: the identity of the terminal; one or more logical channel information; one or more RLC bearer information; one or more QoS flow information; one or more PDU session information; transport layer information associated with Xn user plane transmission, the transport layer information is used to forward downlink data.

Optionally, after the first network node receives the seventh message from the second network node, or after the first network node sends the tenth message, the method further includes: the first network node Send an eleventh message; wherein, the eleventh message is used to indicate at least one of the following: request to release the user context of the terminal; request to end data forwarding and/or offloading; request to end small data transmission.

Optionally, after the first network node receives the seventh message from the second network node, or after the first network node sends the eleventh message, the method further includes: the first network node The node receives the twelfth message from the second network node; wherein, the twelfth message is used to indicate at least one of the following: release the user context information of the terminal; end data forwarding and/or offloading; end small Data transfer; allows the release of resources associated with the user context of the terminal.

In this embodiment, the twelfth message may be a response message of the eleventh message.

In the case where the first network node receives the twelfth message from the second network node, the method further includes at least one of the following: 1) releasing resources associated with the user context of the terminal; 2) forwarding the RRC release message carried in the twelfth message to the terminal; 3) continuing to forward the uplink data, the uplink data being received by the first network node from the first message.

Optionally, on the basis of the foregoing Embodiment 2, after the first network node receives the twelfth message from the second network node, the method further includes: the first network node releases the user of the terminal context; and/or; sending a thirteenth message for at least one of: responding to the twelfth message; indicating that the first network node has released the user context of the terminal; indicating Data forwarding is successful; indicating that the RRC release message is successfully forwarded to the terminal; indicating that the data transmission process is successful.

In order to describe in detail the method for transmitting user plane data provided by the embodiments of the present application, the following will be described with reference to two specific embodiments.

Example 1

In the first embodiment, the second network node (or called the old node or the anchor node) does not send the UE context to the first network node (or called the new node), and the first network node forwards the tunnel through the user plane data The RLC PDU is forwarded to the second network node.

As shown in Figure 3, this embodiment includes the following steps:

Step 1: The terminal in the inactive state (INACTIVE UE) sends a first protocol data unit (corresponding to the first message in the foregoing embodiment), and the first data unit includes the resume ID of the UE, the identity of the UE Verify the identity, the trigger reason for the resume process, and the user plane data.

Optionally, the triggering cause of the resume process may be set as small data transmission/delay-sensitive small data transmission/urgent small data transmission/high-priority small data transmission, indicating that the resume process is used for small data transmission/delay. Sensitive small data transfer/small data transfer for urgent business/small data transfer for high priority business.

Optionally, the first data unit may also include an indication/code point/bitmap (for example, a 1-bit indication, for example, using 00 in the code point [00, 01, 10, 11], for example, the highest bit indication in the bitmap) , the indication/code point/bitmap is used to indicate whether the UE expects low-latency small data transmission.

Optionally, the first data unit may further include an indication/code point/bitmap (for example, a 1-bit indication, for example, using 10 in the code point [00, 01, 10, 11], for example, the next-lowest bit indication in the bitmap ), the indication/code point/bitmap is used to indicate whether the UE estimates whether there is subsequent downlink data transmission.

Optionally, the first data unit may further include an indication/codepoint/bitmap (for example, a 1-bit indication, for example, using 01 in the codepoint [00, 01, 10, 11], for example, the lowest bit indication in the bitmap ), the indication/code point/bitmap is used to indicate whether the UE has subsequent uplink data transmission.

Step 2: After receiving the first protocol data unit sent by the INACTIVE UE, the first network node sends a second message to the second network node, and the second message is sent to enable the first network node to send the second message to the second network node. The network node forwards the user plane data. Optionally, the second message is used for at least one of the following: the first network node obtains the user context forwarded from the second network node; the first network node forwards the radio resource control RRC message forwarded by the second network node to the terminal; the first network node forwards the data to the second network node.

Optionally, the second message may further include a reason for triggering the resume process.

Optionally, the second message may also include an indication/code point/bitmap (for example, a 1-bit indication, for example, using 00 in the code point [00, 01, 10, 11], for example, the highest bit indication in the bitmap), The indication/code point/bitmap is used to indicate whether the UE expects low-latency small data transmission.

Optionally, the second message may further include an indication/code point/bitmap (for example, a 1-bit indication, for example, using 10 in the code point [00, 01, 10, 11], for example, the next-lowest bit indication in the bitmap) , and the indication/code point/bitmap is used to indicate whether the UE estimates whether there will be downlink data transmission in the future.

Optionally, the second message may further include an indication/code point/bitmap (for example, a 1-bit indication, for example, using 01 in the code point [00, 01, 10, 11], for example, the next-lowest bit indication in the bitmap) , the indication/code point/bitmap is used to indicate whether the UE estimates whether there is subsequent uplink data transmission.

Optionally, the second message may further include duration information, where the duration information is used to indicate the duration for establishing a connection between the first network node and the terminal. For example, the duration information may be the duration of the contention resolution window in the broadcast message of the first network node. Alternatively, the duration information may be the duration of T319 in the broadcast message of the first station.

Step 3: If the second network node decides not to provide the UE context to the first network node, the second network node responds to the first network node with a third message, the third message including at least a cause value.

Optionally, the cause value in the third message may indicate any of the following reasons: do not perform re-location (re-location) on the UE context; do not perform re-location on the UE context and propose to perform data forwarding; perform data forwarding and/or The reason is to tell the first network node to establish an uplink data forwarding tunnel for forwarding the uplink data.

Optionally, the third message may further include an indication, which is used to indicate that uplink data forwarding is proposed, and the indication is to tell the first network node to establish an uplink data forwarding tunnel for uplink data forwarding.

Step 4: According to the instruction of the third message, the first network node sends a fourth message to the second network node, where the fourth message is used to indicate that the first network node proposes to perform uplink data forwarding.

Optionally, there is a one-to-one correspondence between the uplink data forwarding and a logical channel (for example, a per logical channel).

Optionally, the fourth message may contain one or more of the following contents: the identity identifier corresponding to the UE, (for example, UE Context ID, resume ID); the user plane data in the first protocol data unit of the UE corresponds to One or more logical channel information (for example, logical channel ID) of ; and an uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding.

Step 5: If the second network node decides to allow the forwarding of uplink data corresponding to at least one logical channel, the second network node responds to the first network node with a seventh message, the seventh message is used to establish an uplink towards the second network node Data forwarding tunnel. In this way, the first network node can forward user plane data to the second network node through the uplink data forwarding tunnel.

Optionally, the seventh message may contain one or more of the following contents: an identity identifier corresponding to the UE (for example, UE Context ID, resume ID); one or more logical channel information (for example, logical channel ID) ; Transport layer information associated with Xn user plane transmission, the information is used to forward uplink data to the second network node.

In other embodiments, this embodiment may further include step 5A: if the second network node decides not to allow data forwarding corresponding to any logical channel, the second network node responds to the first network node with an eighth message, the eighth The message may contain one or more of the following contents: the identity identifier corresponding to the UE, (for example, UE Context ID, resume ID); and an RRC Release message. The first network node transmits the RRC Release message to the UE transparently (eg, without parsing the RRC Release message).

Step 6: The second network node sends a ninth message to the first network node, where the ninth message is used to indicate that the second network node proposes to forward downlink data.

Optionally, there is a one-to-one correspondence between the downlink data forwarding and a logical channel (for example, a per logical channel).

Optionally, the ninth message may include one or more of the following contents: an identity identifier corresponding to the UE (for example, UE Context ID, resume ID); one or more logical channel information (for example, logical channel ID) ; Downlink forwarding proposal field, this field is used to propose downlink data forwarding.

Step 7: If the first network node decides to allow the forwarding of downlink data corresponding to at least one logical channel, the first network node responds to the second network node with a tenth message, the tenth message is used to establish a downlink towards the first network node Data forwarding tunnel.

Optionally, the tenth message may include one or more of the following contents: an identity identifier corresponding to the UE (for example, UE Context ID, resume ID); one or more logical channel information (for example, logical channel ID) ; Transport layer information associated with Xn user plane transmission, the information is used to forward downlink data to the first network node.

Step 8: The first network node sends an eleventh message to the second network node, where the eleventh message is used by the first network node to indicate to the second network node: request to release the user context of the terminal; request to end data forwarding and/or offload; request to end small data transfer.

Step 9: The second network node sends a twelve message to the first network node, which is used for the second network node to indicate to the first network node: release the user context information of the terminal; end data forwarding and/or offloading; end Small data transfer; allows to release resources associated with the user context of the terminal.

Optionally, the twelfth message is for responding to the eleventh message.

Optionally, the twelfth message can also be used by the second network node to indicate to the first network node that it is allowed to release the resources (eg, radio resources) associated with the UE (eg, associated with the identity corresponding to the UE). , control plane resources).

Optionally, the twelfth message includes an RRC Release message. At this time, the first network node transparently (eg, does not parse the RRC Release message) sends the RRC Release message to the UE.

Optionally, after the first network node receives the twelfth message, the first network node may continue to forward the uplink data, where the uplink data is received by the first network node from the first protocol data unit.

Step 10: Before sending the twelfth message including the RRC Release message, the second network node updates the UE air interface security message (for example, obtains a new NCC from the AMF, and updates the saved UE context).

Step 11: the first network node sends a thirteenth message, where the thirteenth message is used for at least one of the following: responding to the twelfth message; indicating that the first network node has released the user context of the terminal; Indicates that the data is forwarded successfully; Indicates that the RRC release message is successfully forwarded to the terminal; Indicates that the data transmission process is successful.

Embodiment 2

In the second embodiment, the second network node (or called the Old node, or the anchor node) sends the UE context to the first network node (or called the new node), and the first network node forwards the tunnel through the user plane data The SDAP-SDU is forwarded to the second network node, and finally the first network node releases the UE context, and the second network node updates the security information of the UE context.

As shown in Figure 4, this embodiment includes the following steps:

Step 1: The terminal in the inactive state (INACTIVE UE) sends a first protocol data unit (corresponding to the first message in the foregoing embodiment), and the first data unit includes the resume ID of the UE, the identity of the UE Verify the identity, the trigger reason for the resume process, and the user plane data.

Step 2: After receiving the first protocol data unit sent by the INACTIVE UE, the first network node sends a second message to the second network node.

For the detailed introduction of step 1 and step 2 in the second embodiment, reference may be made to the introduction of step 1 and step 2 in the first embodiment. In order to avoid repetition, the description is not repeated here.

Step 3: If the second network node can identify the UE context, successfully verifies the UE identity, and decides to provide the UE context to the first network node, the second network node responds to the fifth message, and the fifth message includes at least the UE context. information and second indication information, the second indication information indicates one of the following: do not relocate the user context of the terminal; do not relocate the user context of the terminal and perform data forwarding; perform data forwarding and/or shunt.

Step 4: The first network node sends a sixth message to the second network node, where the sixth message is used to indicate that the first network node proposes to perform uplink data forwarding.

Optionally, there is a one-to-one correspondence between the upstream data forwarding and Qos flow or PDU session (for example, perQos flow or per PDU session). Specifically, upstream data forwarding is performed according to each logical channel (perQos flow or per PDU session), upstream data forwarding tunnels are established/maintained/modified/removed according to the granularity of QoS flow or PDU session, and upstream data forwarding The SDAP-SDU is forwarded in the tunnel.

Optionally, the sixth message may include one or more of the following contents: information of one or more PDU sessions (for example, PDU session IDs) corresponding to the user plane data in the first protocol data unit of the UE; The information of one or more QoS flows (for example, QoS flow IDs) corresponding to the user plane data in the first protocol data unit of the UE; the uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data transfer.

Step 5: If the second network node decides to allow at least one QoS flow or upstream data forwarding corresponding to the PDU session, the second network node responds to the first network node with a seventh message, and the seventh message is used to establish a direction toward the second network. The upstream data forwarding tunnel of the node.

Optionally, the seventh message may contain one or more of the following: the identity of the terminal; one or more QoS flows or PDU session information; transport layer information associated with Xn user plane transmission, The information is used to forward uplink data to the second network node.

In other embodiments, step 5A may also be included: if the second network node decides not to allow data forwarding corresponding to any QoS flow or PDU session, the second network node responds to the first network node with an eighth message, the said The eighth message contains the RRC Release message. The first network node transmits the RRC Release message to the UE transparently (eg, without parsing the RRC Release message).

Step 6: The second network node sends a ninth message to the first network node, where the ninth message is used to indicate that the second network node proposes to forward downlink data.

Optionally, there is a one-to-one correspondence between the downlink data forwarding and the PDU session or QoS flow (perQos flow or per PDU session).

Optionally, the ninth message may contain one or more of the following contents: the identity of the terminal; one or more QoS flows or PDU session information; a downlink forwarding proposal field, which is used to propose downlink data forwarding .

Step 7: If the first network node decides to allow forwarding of downlink data corresponding to at least one QoS flow or PDU session, the first network node responds to the second network node with a tenth message, the tenth message is used to establish a direction toward the first network. Downlink data forwarding tunnel of the node.

Optionally, the tenth message may contain one or more of the following: the identity of the terminal; one or more QoS flows or PDU session information; transport layer information associated with Xn user plane transmission, the information for forwarding downlink data to the first network node.

Step 8: The first network node sends an eleventh message to the second network node, where the eleventh message is used by the first network node to indicate to the second network node: request to release the user context of the terminal; request to end data forwarding and/or offload; request to end small data transfer.

Step 9: the second network node sends a twelfth message to the first network node, the second network node indicating to the first network node: release the user context information of the terminal; end data forwarding and/or offloading; End the small data transfer; allow the resources associated with the user context of the terminal to be released.

Optionally, the twelfth message is for responding to the eleventh message.

Optionally, the twelfth message may also be used by the second network node to indicate to the first network node that the resources (eg, radio resources, control plane resources) associated with the UE Context ID are allowed to be released.

Optionally, the twelfth message includes an RRC Release message. At this time, the first network node transparently (eg, does not parse the RRC Release message) sends the RRC Release message to the UE.

Step 10: Before sending the twelfth message including the RRC Release message, the second network node updates the UE air interface security message (for example, obtains a new NCC from the AMF, and updates the saved UE context).

Step 11: After the first network node receives the twelfth message, it releases the saved UE context.

Optionally, after the first network node receives the twelfth message, the first network node may continue to forward the uplink data, where the uplink data is received by the first network node from the first protocol data unit.

Step 12: the first network node sends a thirteenth message, where the thirteenth message is used for at least one of the following: responding to the twelfth message; indicating that the first network node has released the user context of the terminal; Indicates that the data is forwarded successfully; Indicates that the RRC release message is successfully forwarded to the terminal; Indicates that the data transmission process is successful.

The method for transmitting user plane data according to an embodiment of the present application has been described in detail above with reference to FIGS. 2 to 4 . A method for transmitting user plane data according to another embodiment of the present application will be described in detail below with reference to FIG. 5 . It can be understood that the interaction between the second network node and the first network node described from the second network node is the same as the description on the first network node side in the method shown in FIG. 2 , and relevant descriptions are appropriately omitted to avoid repetition.

FIG. 5 is a schematic diagram of an implementation flowchart of a method for transmitting user plane data according to an embodiment of the present application, which may be applied to a second network node. As shown in FIG. 5 , the method 500 includes the following steps.

S502: The second network node receives a second message from the first network node, where the second message includes the user context identifier of the terminal; the second message is used for at least one of the following: the first network node obtains the user transferred from the second network node context; the first network node forwards the RRC message forwarded by the second network node to the terminal; the first network node forwards the data to the second network node.

In this embodiment of the present application, the first network node sends a second message after receiving the first message from the terminal, where the first message includes the recovery identifier of the terminal and user plane data, and the second message includes the user context identifier of the terminal, The second message is used for at least one of the following: the first network node obtains the user context forwarded from the second network node; the first network node forwards the RRC message forwarded by the second network node to the terminal; the first network node The node forwards the data to the second network node. Based on the above-mentioned second message, the first network node can forward user plane data or forward RRC messages to the terminal, so as to reduce the transmission delay of the user plane data and reduce the waiting time of the terminal at the same time.

Optionally, as an embodiment, the second message further includes or indicates at least one of the following: a cause for triggering the recovery process; the terminal expects to perform low-latency small data transmission; the terminal estimates that there will be downlink data transmission in the future ; The terminal has subsequent uplink data transmission; duration information, the duration information is used to indicate the duration of the connection between the first network node and the terminal, and the second network node proposes to carry out the process according to the duration information Downlink data forwarding and/or forwarding of downlink data.

Optionally, as an embodiment, the reason for triggering the recovery process includes one of the following: small data transmission; delay-sensitive small data transmission; urgent small data transmission; and high-priority small data transmission.

Optionally, as an embodiment, after the second network node receives the second message, the method further includes: the second network node sends a third message; or the second network node sends a third message according to the second message, send a third message; the third message includes first indication information, and the first indication information indicates one of the following: do not relocate the user context of the terminal; do not relocate the user context of the terminal And carry out data forwarding; carry out data forwarding and/or offloading.

Optionally, as an embodiment, after the second network node sends the third message, the method further includes: the second network node receives a fourth message, where the fourth message is used to indicate the first message The network node proposes upstream data forwarding.

Optionally, as an embodiment, there is a one-to-one correspondence between the uplink data forwarding and the logical channel or the RLC bearer.

Optionally, as an embodiment, the fourth message includes at least one of the following: the identity of the terminal; one or more logical channel information corresponding to the user plane data; One or more RLC bearer information, the RLC bearer information is used for uplink data forwarding; the RLC bearer information and the logical channel information have a one-to-one mapping relationship; the uplink forwarding proposal field, the uplink forwarding proposal field is used for Uplink data forwarding is proposed.

Optionally, as an embodiment, after the second network node receives the second message, the method further includes: the second network node sends a fifth message; or the second network node according to the second message, send a fifth message; the fifth message includes the user context of the terminal and second indication information, and the second indication information indicates one of the following: do not relocate the user context of the terminal; do not relocate the user context of the terminal; The user context of the terminal is relocated and data forwarding is performed; data forwarding and/or offloading are performed.

Optionally, as an embodiment, after the second network node sends the fifth message, the method further includes: the second network node receives a sixth message, where the sixth message is used to indicate the first message The network node proposes upstream data forwarding.

Optionally, as an embodiment, there is a one-to-one correspondence between the uplink data forwarding and the quality of service QoS flow or the protocol data unit PDU session.

Optionally, as an embodiment, the sixth message includes at least one of the following: one or more QoS flow information corresponding to the user plane data; one or more PDU sessions corresponding to the user plane data information; an uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data transfer.

Optionally, as an embodiment, the method further includes: the second network node sends a seventh message, where the seventh message is used to establish an uplink data forwarding tunnel.

Optionally, as an embodiment, the seventh message includes at least one of the following: an identity of the terminal; one or more logical channel information; one or more RLC bearer information; one or more QoS flow information ; One or more PDU session information; Transport layer information associated with Xn user plane transmission, the transport layer information is used to forward uplink data.

Optionally, as an embodiment, when the second network node does not allow data forwarding, the method further includes: the second network node sends an eighth message, where the eighth message includes RRC release information.

Optionally, as an embodiment, after the second network node sends the seventh message, the method further includes: the second network node sends a ninth message, where the ninth message indicates to the second network node Downlink data forwarding is proposed; the second network node receives a tenth message from the first network node, where the tenth message is used to establish a downlink data forwarding tunnel.

Optionally, as an embodiment, the ninth message includes at least one of the following: the identity of the terminal; one or more logical channel information; one or more RLC bearer information; one or more QoS flow information ; one or more PDU session information; a downlink forwarding proposal field, the downlink forwarding proposal field is used to propose downlink data forwarding, and/or, the tenth message includes at least one of the following: the identity of the terminal; One or more logical channel information; one or more RLC bearer information; one or more QoS flow information; one or more PDU session information; Forward downstream data.

Optionally, as an embodiment, the method further includes: the second network node receiving an eleventh message from the first network node; wherein the eleventh message is used to indicate at least one of the following : request to release the user context of the terminal; request to end data forwarding and/or offloading; request to end small data transmission.

Optionally, as an embodiment, the method further includes: the second network node sends a twelfth message; wherein the twelfth message is used to indicate at least one of the following: release the user context of the terminal information; end data forwarding and/or offloading; end small data transmission; allow the release of resources associated with the user context of the terminal.

Optionally, as an embodiment, before the second network node sends the twelfth message, the method further includes: updating the air interface security message of the terminal.

Optionally, as an embodiment, after the second network node sends the twelfth message, the method further includes: receiving a thirteenth message from the first network node, where the thirteenth message is used for At least one of the following: respond to the twelfth message; indicate that the first network node has released the user context of the terminal; indicate that data forwarding is successful; indicate that the RRC release message is successfully forwarded to the terminal; indicate The data transfer process was successful.

FIG. 6 is a schematic structural diagram of a first network node according to an embodiment of the present application. As shown in FIG. 6 , the first network node 600 includes the following modules.

The receiving module 602 may be configured to receive a first message from a terminal, where the first message includes a recovery identifier of the terminal and user plane data.

The sending module 604 may be configured to send a second message, where the second message includes the user context identifier of the terminal; the second message is used for at least one of the following: the first network node obtains information from the second network node forwarded user context; the first network node forwards the RRC message forwarded by the second network node to the terminal; the first network node forwards the data to the second network node.

In this embodiment of the present application, the first network node sends a second message after receiving the first message from the terminal, where the first message includes the recovery identifier of the terminal and user plane data, and the second message includes the user context identifier of the terminal, The second message is used for at least one of the following: the first network node obtains the user context forwarded from the second network node; the first network node forwards the RRC message forwarded by the second network node to the terminal; the first network node The node forwards the data to the second network node. Based on the above-mentioned second message, the first network node can forward user plane data or forward RRC messages to the terminal, so as to reduce the transmission delay of the user plane data and reduce the waiting time of the terminal at the same time.

Optionally, as an embodiment, the first message further includes or indicates at least one of the following: a cause for triggering the recovery process; the terminal expects to perform low-latency small data transmission; the terminal estimates that there will be downlink data transmission in the future ; the terminal has subsequent uplink data transmission; and/or; the second message also includes or indicates at least one of the following: a recovery process triggering cause; the terminal expects to perform low-latency small data transmission; the terminal estimates Downlink data is sent subsequently; uplink data is sent by the terminal subsequently; duration information, where the duration information is used to indicate the duration for establishing a connection between the first network node and the terminal.

Optionally, as an embodiment, the reason for triggering the recovery process includes one of the following: small data transmission; delay-sensitive small data transmission; urgent small data transmission; and high-priority small data transmission.

Optionally, as an embodiment, the receiving module 602 may be further configured to: receive a third message from the second network node, where the third message includes first indication information; the first indication information indicates the following One: do not relocate the user context of the terminal; do not relocate the user context of the terminal and perform data forwarding; perform data forwarding and/or offloading.

Optionally, as an embodiment, the sending module 604 may be further configured to: send a fourth message according to the first indication information, where the fourth message is used to indicate that the first network node proposes to perform uplink data forwarding .

Optionally, as an embodiment, there is a one-to-one correspondence between the uplink data forwarding and a logical channel or a radio link control RLC bearer.

Optionally, as an embodiment, the fourth message includes at least one of the following: the identity of the terminal; one or more logical channel information corresponding to the user plane data; One or more RLC bearer information, the RLC bearer information is used for uplink data forwarding; the RLC bearer information and the logical channel information have a one-to-one mapping relationship; the uplink forwarding proposal field, the uplink forwarding proposal field is used for Uplink data forwarding is proposed.

Optionally, as an embodiment, the receiving module 602 may be further configured to: receive a fifth message from the second network node, where the fifth message includes the user context of the terminal and the second indication information, so The second indication information indicates one of the following: do not relocate the user context of the terminal; do not relocate the user context of the terminal and perform data forwarding; perform data forwarding and/or offloading.

Optionally, as an embodiment, the sending module 604 may be further configured to: send a sixth message according to the second indication information, where the sixth message is used to indicate that the first network node proposes to perform uplink data forwarding .

Optionally, as an embodiment, there is a one-to-one correspondence between the uplink data forwarding and the quality of service QoS flow or the protocol data unit PDU session.

Optionally, as an embodiment, the sixth message includes at least one of the following: one or more QoS flow information corresponding to the user plane data; one or more PDU sessions corresponding to the user plane data information; an uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data transfer.

Optionally, as an embodiment, the receiving module 602 may be further configured to: receive a seventh message from the second network node, where the seventh message is used to establish an uplink data forwarding tunnel.

Optionally, as an embodiment, the seventh message includes at least one of the following: an identity of the terminal; one or more logical channel information; one or more RLC bearer information; one or more QoS flow information ; One or more PDU session information; Transport layer information associated with Xn user plane transmission, the transport layer information is used to forward uplink data.

Optionally, as an embodiment, the receiving module 602 may be further configured to: receive an eighth message from the second network node, where the eighth message includes an RRC release message; the first network node sends the The RRC release message is sent to the terminal.

Optionally, as an embodiment, the receiving module 602 may be further configured to: receive a ninth message from the second network node, where the ninth message indicates that the second network node proposes to forward downlink data; send Module 604 may be further configured to: send a tenth message, where the tenth message is used to establish a downlink data forwarding tunnel.

Optionally, as an embodiment, the ninth message includes at least one of the following: the identity of the terminal; one or more logical channel information; one or more RLC bearer information; one or more QoS flow information ; one or more PDU session information; a downlink forwarding proposal field, the downlink forwarding proposal field is used to propose downlink data forwarding, and/or, the tenth message includes at least one of the following: the identity of the terminal; One or more logical channel information; one or more RLC bearer information; one or more QoS flow information; one or more PDU session information; Forward downstream data.

Optionally, as an embodiment, the sending module 604 may be further configured to: send an eleventh message; wherein, the eleventh message is used to indicate at least one of the following: request to release the user context of the terminal; request End data forwarding and/or offloading; request end small data transfer.

Optionally, as an embodiment, the receiving module 602 may be further configured to: receive a twelfth message from the second network node; wherein the twelfth message is used to indicate at least one of the following: release all user context information of the terminal; end data forwarding and/or offloading; end small data transmission; allow the release of resources associated with the user context of the terminal.

Optionally, as an embodiment, the first network node is further configured to at least one of the following: release resources associated with the user context of the terminal; forward the RRC release message carried in the twelfth message to the terminal; continue forwarding the uplink data, the uplink data is received by the first network node from the first message.

Optionally, as an embodiment, the first network node 600 is further configured to: release the user context of the terminal; and/or send a thirteenth message through the sending module 604, where the thirteenth message is used for the following At least one of: responding to the twelfth message; indicating that the user context of the terminal has been released by the first network node; indicating that data forwarding is successful; indicating that the RRC release message has been successfully forwarded to the terminal; indicating that data The transfer process was successful.

The first network node 600 according to the embodiment of the present application may refer to the process of the method 200 corresponding to the embodiment of the present application, and each unit/module and the above-mentioned other operations and/or functions in the first network node 600 are respectively for the purpose of implementing the method The corresponding process in 200 can achieve the same or equivalent technical effect, and for brevity, it will not be repeated here.

FIG. 7 is a schematic structural diagram of a second network node according to an embodiment of the present application. As shown in FIG. 7 , the second network node 700 includes the following modules.

The receiving module 702 can be configured to receive a second message from the first network node, where the second message includes the user context identifier of the terminal; the second message is used for at least one of the following: the first network node obtains the the user context forwarded by the second network node; the first network node forwards the RRC message forwarded by the second network node to the terminal; the first network node forwards the data to the second network node.

In this embodiment of the present application, the first network node sends a second message after receiving the first message from the terminal, where the first message includes the recovery identifier of the terminal and user plane data, and the second message includes the user context identifier of the terminal, The second message is used for at least one of the following: the first network node obtains the user context forwarded from the second network node; the first network node forwards the RRC message forwarded by the second network node to the terminal; the first network node forwards data to the second network node. Based on the above-mentioned second message, the first network node can forward user plane data or forward RRC messages to the terminal, so as to reduce the transmission delay of the user plane data and reduce the waiting time of the terminal at the same time.

Optionally, as an embodiment, the second message further includes or indicates at least one of the following: a cause for triggering the recovery process; the terminal expects to perform low-latency small data transmission; the terminal estimates that there will be downlink data transmission in the future; The terminal has subsequent uplink data to send; duration information, the duration information is used to indicate the duration for establishing a connection between the first network node and the terminal, and the second network node proposes downlink data according to the duration information. Forward and/or forward downstream data.

Optionally, as an embodiment, the reason for triggering the recovery process includes one of the following: small data transmission; delay-sensitive small data transmission; urgent small data transmission; and high-priority small data transmission.

Optionally, as an embodiment, the second network node 700 further includes a sending module, which can be configured to: send a third message; or send a third message according to the second message; the third message includes the first Indication information, the first indication information indicates one of the following: do not relocate the user context of the terminal; do not relocate the user context of the terminal and perform data forwarding; perform data forwarding and/or offloading.

Optionally, as an embodiment, the receiving module 702 may be further configured to: receive a fourth message, where the fourth message is used to indicate that the first network node proposes to perform uplink data forwarding.

Optionally, as an embodiment, there is a one-to-one correspondence between the uplink data forwarding and the logical channel or the RLC bearer.

Optionally, as an embodiment, the fourth message includes at least one of the following: the identity of the terminal; one or more logical channel information corresponding to the user plane data; One or more RLC bearer information, the RLC bearer information is used for uplink data forwarding; the RLC bearer information and the logical channel information have a one-to-one mapping relationship; the uplink forwarding proposal field, the uplink forwarding proposal field is used for Uplink data forwarding is proposed.

Optionally, as an embodiment, the second network node 700 further includes a sending module, which can be configured to: send a fifth message; or send a fifth message according to the second message; the fifth message includes the The user context of the terminal and the second indication information, the second indication information indicates one of the following: do not relocate the user context of the terminal; do not relocate the user context of the terminal and perform data forwarding; Forwarding and/or offloading.

Optionally, as an embodiment, the receiving module 702 may be further configured to: receive a sixth message, where the sixth message is used to indicate that the first network node proposes to perform uplink data forwarding.

Optionally, as an embodiment, there is a one-to-one correspondence between the uplink data forwarding and the quality of service QoS flow or the protocol data unit PDU session.

Optionally, as an embodiment, the sixth message includes at least one of the following: one or more QoS flow information corresponding to the user plane data; one or more PDU sessions corresponding to the user plane data information; an uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data transfer.

Optionally, as an embodiment, the second network node 700 further includes a sending module, which may be configured to: send a seventh message, where the seventh message is used to establish an uplink data forwarding tunnel.

Optionally, as an embodiment, the seventh message includes at least one of the following: an identity of the terminal; one or more logical channel information; one or more RLC bearer information; one or more QoS flow information ; One or more PDU session information; Transport layer information associated with Xn user plane transmission, the transport layer information is used to forward uplink data.

Optionally, as an embodiment, the second network node 700 further includes a sending module, which can be configured to send an eighth message when the second network node does not allow data forwarding, the eighth message Including the RRC release message.

Optionally, as an embodiment, the second network node 700 further includes a sending module, which can be configured to: the second network node sends a ninth message, where the ninth message indicates that the second network node proposes to do Downlink data forwarding; the receiving module 702 may be further configured to: receive a tenth message from the first network node, where the tenth message is used to establish a downlink data forwarding tunnel.

Optionally, as an embodiment, the ninth message includes at least one of the following: the identity of the terminal; one or more logical channel information; one or more RLC bearer information; one or more QoS flow information ; one or more PDU session information; a downlink forwarding proposal field, the downlink forwarding proposal field is used to propose downlink data forwarding, and/or, the tenth message includes at least one of the following: the identity of the terminal; One or more logical channel information; one or more RLC bearer information; one or more QoS flow information; one or more PDU session information; Forward downstream data.

Optionally, as an embodiment, the receiving module 702 may be further configured to: receive an eleventh message from the first network node; wherein the eleventh message is used to indicate at least one of the following: Request to release the user context of the terminal; request to end data forwarding and/or offloading; request to end small data transmission.

Optionally, as an embodiment, the second network node 700 further includes a sending module, which can be configured to: send a twelfth message; wherein the twelfth message is used to indicate at least one of the following: release the User context information of the terminal; end data forwarding and/or offloading; end small data transmission; allow the release of resources associated with the user context of the terminal.

Optionally, as an embodiment, the second network node 700 further includes an update module, which can be configured to: update the air interface security message of the terminal.

Optionally, as an embodiment, after the sending module sends the twelfth message, the receiving module 702 may be further configured to: receive a thirteenth message from the first network node, the thirteenth message The message is used for at least one of the following: responding to the twelfth message; indicating that the first network node has released the user context of the terminal; indicating that data forwarding is successful; indicating that the RRC release message is successfully forwarded to the Terminal; indicates that the data transfer process was successful.

For the second network node 700 according to the embodiment of the present application, reference may be made to the process of the method 500 corresponding to the embodiment of the present application, and each unit/module and the above-mentioned other operations and/or functions in the second network node 700 are for the purpose of implementing the method, respectively. The corresponding process in 500 can achieve the same or equivalent technical effect, which is not repeated here for brevity.

Optionally, as shown in FIG. 8 , an embodiment of the present application further provides a communication device 800, including a processor 801, a memory 802, a program or instruction stored in the memory 802 and executable on the processor 801, For example, when the communication device 800 is a network node, when the program or instruction is executed by the processor 801, each process of the above-mentioned user plane data transmission method embodiment can be achieved, and the same technical effect can be achieved. Repeat.

Specifically, an embodiment of the present application further provides a network side device. As shown in FIG. 9 , the network device 900 includes: an antenna 91 , a radio frequency device 92 , and a baseband device 93 . The antenna 91 is connected to the radio frequency device 92 . In the uplink direction, the radio frequency device 92 receives information through the antenna 91, and sends the received information to the baseband device 93 for processing. In the downlink direction, the baseband device 93 processes the information to be sent and sends it to the radio frequency device 92 , and the radio frequency device 92 processes the received information and sends it out through the antenna 91 .

The above-mentioned frequency band processing apparatus may be located in the baseband apparatus 93 , and the method performed by the network side device in the above embodiments may be implemented in the baseband apparatus 93 . The baseband apparatus 93 includes a processor 94 and a memory 95 .

The baseband device 93 may include, for example, at least one baseband board on which a plurality of chips are arranged. As shown in FIG. 9 , one of the chips is, for example, the processor 94 , which is connected to the memory 95 to call the program in the memory 95 and execute it. The network devices shown in the above method embodiments operate.

The baseband device 93 may further include a network interface 96 for exchanging information with the radio frequency device 92, and the interface is, for example, a common public radio interface (CPRI for short).

Specifically, the network-side device in the embodiment of the present invention further includes: an instruction or program stored in the memory 95 and executable on the processor 94, and the processor 94 invokes the instruction or program in the memory 95 to execute the instructions or programs shown in FIG. 6 and FIG. 7 . In order to avoid repetition, it is not repeated here.

The embodiments of the present application further provide a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, each process of the foregoing user plane data transmission method embodiment is implemented, and The same technical effect can be achieved, and in order to avoid repetition, details are not repeated here.

The processor may be the processor in the terminal described in the foregoing embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.

An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or an instruction to implement the above method for transmitting user plane data Each process of the embodiment can achieve the same technical effect, and to avoid repetition, it will not be repeated here.

It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.

An embodiment of the present application further provides a computer program product, where the computer program product is stored in a non-volatile memory, and the computer program product is executed by at least one processor to implement the above embodiments of the user plane data transmission method Each process can achieve the same technical effect. In order to avoid repetition, it will not be repeated here.

The embodiment of the present application further provides a communication device, which is configured to execute each process of the above-mentioned user plane data transmission method embodiment, and can achieve the same technical effect. To avoid repetition, details are not repeated here.

It should be noted that, herein, the terms "comprising", "comprising" or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements, It also includes other elements not expressly listed or inherent to such a process, method, article or apparatus. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in a process, method, article or apparatus that includes the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in the reverse order depending on the functions involved. To perform functions, for example, the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to some examples may be combined in other examples.

From the description of the above embodiments, those skilled in the art can clearly understand that the method of the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence or in a part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, CD-ROM), including several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of this application.

The embodiments of the present application have been described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific embodiments, which are merely illustrative rather than restrictive. Under the inspiration of this application, without departing from the scope of protection of the purpose of this application and the claims, many forms can be made, which all fall within the protection of this application.

Claims (47)

A method for transmitting user plane data, the method comprising: the first network node receives a first message from the terminal, where the first message includes a recovery identifier of the terminal and user plane data; The first network node sends a second message, where the second message includes the user context identifier of the terminal; the second message is used for at least one of the following: the first network node obtains the user context handed over from the second network node; forwarding, by the first network node, the radio resource control RRC message forwarded by the second network node to the terminal; The first network node forwards the data to the second network node. The method of claim 1, wherein, The first message also includes or indicates at least one of the following: The reason for triggering the recovery process; The terminal expects low-latency small data transmission; The terminal estimates that downlink data will be sent later; The terminal sends uplink data subsequently; and / or The second message further includes or indicates at least one of the following: The reason for triggering the recovery process; The terminal expects low-latency small data transmission; The terminal estimates that downlink data will be sent later; The terminal sends uplink data subsequently; Duration information, where the duration information is used to indicate the duration for establishing a connection between the first network node and the terminal. The method according to claim 2, wherein the triggering cause of the recovery process comprises one of the following: small data transmission; delay sensitive small data transmission; urgent small data transmission; high priority small data transmission. The method according to claim 1, wherein after the first network node sends the second message, the method further comprises: The first network node receives a third message from the second network node, where the third message includes first indication information; the first indication information indicates one of the following: not relocating the user context of the terminal; not relocating the user context of the terminal and forwarding data; Perform data forwarding and/or offloading. The method of claim 4, wherein after the first network node receives the third message from the second network node, the method further comprises: The first network node sends a fourth message according to the first indication information, where the fourth message is used to indicate that the first network node proposes to perform uplink data forwarding. The method according to claim 5, wherein there is a one-to-one correspondence between the uplink data forwarding and a logical channel or a radio link control RLC bearer. The method of claim 5, wherein the fourth message includes at least one of the following: the identity of the terminal; One or more logical channel information corresponding to the user plane data; One or more RLC bearer information corresponding to the user plane data, the RLC bearer information is used for uplink data forwarding, and there is a one-to-one mapping relationship between the RLC bearer information and the logical channel information; The upstream forwarding proposal field is used to propose upstream data forwarding. The method according to claim 1, wherein after the first network node sends the second message, the method further comprises: The first network node receives a fifth message from the second network node, where the fifth message includes the user context of the terminal and second indication information, where the second indication information indicates one of the following: not relocating the user context of the terminal; not relocating the user context of the terminal and forwarding data; Perform data forwarding and/or offloading. The method of claim 8, wherein after the first network node receives the fifth message from the second network node, the method further comprises: The first network node sends a sixth message according to the second indication information, where the sixth message is used to indicate that the first network node proposes to perform uplink data forwarding. The method according to claim 9, wherein there is a one-to-one correspondence between the uplink data forwarding and a quality of service (QoS) flow or a protocol data unit (PDU) session. The method of claim 9, wherein the sixth message includes at least one of the following: One or more QoS flow information corresponding to the user plane data; One or more PDU session information corresponding to the user plane data; An uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding. The method according to claim 5 or 9, wherein the method further comprises: The first network node receives a seventh message from the second network node, where the seventh message is used to establish an uplink data forwarding tunnel. The method of claim 12, wherein the seventh message includes at least one of the following: the identity of the terminal; one or more logical channel information; one or more RLC bearer information; One or more QoS flow information; One or more PDU session information; Transport layer information associated with Xn user plane transmission, where the transport layer information is used to forward uplink data. The method according to claim 5 or 9, wherein the method further comprises: the first network node receives an eighth message from the second network node, where the eighth message includes an RRC release message; The first network node sends the RRC release message to the terminal. The method of claim 12, wherein after the first network node receives the seventh message from the second network node, the method further comprises: receiving, by the first network node, a ninth message from the second network node, the ninth message indicating that the second network node proposes to forward downlink data; The first network node sends a tenth message, where the tenth message is used to establish a downlink data forwarding tunnel. The method of claim 15, wherein, The ninth message includes at least one of the following: the identity of the terminal; one or more logical channel information; one or more RLC bearer information; one or more QoS flow information; one or more PDU session information; A downlink forwarding proposal field, where the downlink forwarding proposal field is used to propose downlink data forwarding; and/or The tenth message includes at least one of the following: the identity of the terminal; one or more logical channel information; one or more RLC bearer information; one or more QoS flow information; one or more PDU session information; Transport layer information associated with Xn user plane transmission, where the transport layer information is used to forward downlink data. The method of claim 12 or 16, wherein the method further comprises: the first network node sending an eleventh message; The eleventh message is used to indicate at least one of the following: request to release the user context of the terminal; request to end data forwarding and/or offloading; request to end small data transmission. The method of claim 12 or 17, wherein the method further comprises: the first network node receiving a twelfth message from the second network node; The twelfth message is used to indicate at least one of the following: release the user context information of the terminal; end data forwarding and/or offloading; end small data transmission; allow the release of resources associated with the user context of the terminal . The method of claim 18, wherein the method further comprises at least one of the following: releasing resources associated with the user context of the terminal; forwarding the RRC release message carried in the twelfth message to the terminal; Continue to perform uplink data forwarding, where the uplink data is received by the first network node from the first message. The method of claim 18 or 19, wherein after the first network node receives the twelfth message from the second network node, the method further comprises: release the user context of the terminal; and/or A thirteenth message is sent for at least one of the following: responding to the twelfth message; indicating that the first network node has released the user context of the terminal; Indicates that data forwarding is successful; indicating that the RRC release message is successfully forwarded to the terminal; Indicates that the data transfer process was successful. A method for transmitting user plane data, wherein the method comprises: The second network node receives a second message from the first network node, where the second message includes the user context identifier of the terminal; the second message is used for at least one of the following: obtaining, by the first network node, the user context handed over from the second network node; forwarding, by the first network node, the RRC message forwarded by the second network node to the terminal; The first network node forwards the data to the second network node. The method of claim 21, wherein the second message further comprises or indicates at least one of the following: The reason for triggering the recovery process; The terminal expects low-latency small data transmission; The terminal estimates that downlink data will be sent later; The terminal sends uplink data subsequently; Duration information, where the duration information is used to indicate the duration for establishing a connection between the first network node and the terminal, and the second network node proposes to forward downlink data and/or forward downlink data according to the duration information. The method according to claim 22, wherein the triggering reason for the recovery process comprises one of the following: small data transmission; delay sensitive small data transmission; urgent small data transmission; high priority small data transmission. The method according to claim 21 or 22, wherein after the second network node receives the second message, the method further comprises: the second network node sends a third message; or sending, by the second network node, a third message according to the second message; The third message includes first indication information, and the first indication information indicates one of the following: not relocating the user context of the terminal; not relocating the user context of the terminal and forwarding data; Perform data forwarding and/or offloading. The method of claim 24, wherein after the second network node sends the third message, the method further comprises: The second network node receives a fourth message, where the fourth message is used to indicate that the first network node proposes to perform uplink data forwarding. The method according to claim 25, wherein there is a one-to-one correspondence between the uplink data forwarding and a logical channel or an RLC bearer. The method of claim 25, wherein the fourth message includes at least one of the following: the identity of the terminal; One or more logical channel information corresponding to the user plane data; One or more RLC bearer information corresponding to the user plane data, the RLC bearer information is used for uplink data forwarding, and there is a one-to-one mapping relationship between the RLC bearer information and the logical channel information; The upstream forwarding proposal field is used to propose upstream data forwarding. The method according to claim 21 or 22, wherein after the second network node receives the second message, the method further comprises: the second network node sends a fifth message; or sending, by the second network node, a fifth message according to the second message; The fifth message includes the user context of the terminal and second indication information, where the second indication information indicates one of the following: not relocating the user context of the terminal; not relocating the user context of the terminal and forwarding data; Perform data forwarding and/or offloading. The method of claim 28, wherein after the second network node sends the fifth message, the method further comprises: The second network node receives a sixth message, where the sixth message is used to indicate that the first network node proposes to perform uplink data forwarding. The method according to claim 29, wherein there is a one-to-one correspondence between the upstream data forwarding and a quality of service (QoS) flow or a protocol data unit (PDU) session. The method of claim 29, wherein the sixth message includes at least one of the following: One or more QoS flow information corresponding to the user plane data; One or more PDU session information corresponding to the user plane data; An uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding. The method of claim 25 or 29, wherein the method further comprises: The second network node sends a seventh message, where the seventh message is used to establish an uplink data forwarding tunnel. The method of claim 32, wherein the seventh message includes at least one of the following: the identity of the terminal; one or more logical channel information; one or more RLC bearer information; One or more QoS flow information; One or more PDU session information; Transport layer information associated with Xn user plane transmission, where the transport layer information is used to forward uplink data. The method according to claim 25 or 29, wherein, in the case that the second network node does not allow data forwarding, the method further comprises: The second network node sends an eighth message, where the eighth message includes an RRC release message. The method of claim 32, wherein after the second network node sends the seventh message, the method further comprises: sending, by the second network node, a ninth message, the ninth message indicating that the second network node proposes to forward downlink data; The second network node receives a tenth message from the first network node, where the tenth message is used to establish a downlink data forwarding tunnel. The method of claim 35, wherein, The ninth message includes at least one of the following: the identity of the terminal; one or more logical channel information; one or more RLC bearer information; one or more QoS flow information; one or more PDU session information; A downlink forwarding proposal field, where the downlink forwarding proposal field is used to propose downlink data forwarding; and/or The tenth message includes at least one of the following: the identity of the terminal; one or more logical channel information; one or more RLC bearer information; one or more QoS flow information; one or more PDU session information; Transport layer information associated with Xn user plane transmission, where the transport layer information is used to forward downlink data. The method of claim 32, wherein the method further comprises: the second network node receiving an eleventh message from the first network node; The eleventh message is used to indicate at least one of the following: request to release the user context of the terminal; request to end data forwarding and/or offloading; request to end small data transmission. The method of claim 32 or 37, wherein the method further comprises: the second network node sending a twelfth message; The twelfth message is used to indicate at least one of the following: release the user context information of the terminal; end data forwarding and/or offloading; end small data transmission; allow the release of resources associated with the user context of the terminal . The method according to claim 38, wherein before the second network node sends the twelfth message, the method further comprises: updating the air interface security message of the terminal. The method of claim 38, wherein after the second network node sends the twelfth message, the method further comprises: A thirteenth message from the first network node is received, the thirteenth message being for at least one of: responding to the twelfth message; indicating that the first network node has released the user context of the terminal; Indicates that data forwarding is successful; indicating that the RRC release message is successfully forwarded to the terminal; Indicates that the data transfer process was successful. A first network node, comprising: a receiving module, configured to receive a first message from a terminal, where the first message includes a recovery identifier of the terminal and user plane data; a sending module, configured to send a second message, where the second message includes the user context identifier of the terminal; the second message is used for at least one of the following: the first network node obtains the user context handed over from the second network node; the first network node forwards the RRC message forwarded by the second network node to the terminal; The first network node forwards the data to the second network node. A second network node, comprising: a receiving module, configured to receive a second message from the first network node, where the second message includes a user context identifier of the terminal; the second message is used for at least one of the following: obtaining, by the first network node, the user context handed over from the second network node; forwarding, by the first network node, the RRC message forwarded by the second network node to the terminal; The first network node forwards the data to the second network node. A network node, comprising a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the processor to achieve as claimed in claims 1 to 40 Any one of the transmission methods for user plane data. A readable storage medium on which programs or instructions are stored, and when the programs or instructions are executed by the processor, the method for transmitting user plane data according to any one of claims 1 to 40 is implemented . A chip, the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is used for running a program or an instruction to implement the user interface according to any one of claims 1 to 40 data transfer method. A computer program product, the computer program product being stored in a non-volatile memory, the computer program product being executed by at least one processor to realize the transmission of user plane data according to any one of claims 1 to 40 method. A communication device configured to perform the transmission method of user plane data as claimed in any one of claims 1 to 40.

Images