CN114095138B

CN114095138B - User plane data transmission method and network node

Info

Publication number: CN114095138B
Application number: CN202010860022.0A
Authority: CN
Inventors: 莫毅韬; 张艳霞
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-08-24
Filing date: 2020-08-24
Publication date: 2023-05-30
Anticipated expiration: 2040-08-24
Also published as: WO2022042440A1; CN114095138A

Abstract

The embodiment of the application discloses a transmission method of user plane data and a network node, which can solve the problem of large transmission delay of the user plane data. The method comprises the following steps: the method comprises the steps that a first network node receives a first message from a terminal, wherein the first message comprises a recovery identifier of the terminal and user plane data; the first network node sends a second message, wherein the second message comprises a user context identifier of the terminal; the second message is for at least one of: the first network node acquires a user context forwarded from a second network node; the first network node forwards a Radio Resource Control (RRC) message forwarded by the second network node to the terminal; the first network node forwards data to a second network node.

Description

User plane data transmission method and network node

Technical Field

The application belongs to the technical field of communication, and particularly relates to a user plane data transmission method and a network node.

Background

For terminals that support small data transmissions and are in an inactive state, small data (user plane data) transmission is typically achieved by initiating a radio resource control (Radio Resource Control, RRC) recovery procedure. In particular, the terminal may multiplex encrypted user plane data etc. in one media access control protocol data unit (Media Access Control Protocol Data Unit, MAC PDU) to the network node. If the network node that receives the terminal MAC PDU does not store the user context (UE context) of the terminal, the network node cannot decrypt the user plane data and cannot forward the user plane data to the user plane function (User Plane Function, UPF) entity, at this time, the network node is in a waiting state, and cannot determine whether to discard the user plane data or perform other actions, and the transmission delay of the user plane data is larger.

Disclosure of Invention

The embodiment of the application provides a transmission method of user plane data and a network node, which can solve the problem of large transmission delay of the user plane data.

In a first aspect, a method for transmitting user plane data is provided, where the method includes: the method comprises the steps that a first network node receives a first message from a terminal, wherein the first message comprises a recovery identifier of the terminal and user plane data; the first network node sends a second message, wherein the second message comprises a user context identifier of the terminal; the second message is for at least one of: the first network node acquires a user context forwarded from a second network node; the first network node forwards a Radio Resource Control (RRC) message forwarded by the second network node to the terminal; the first network node forwards data to a second network node.

In a second aspect, a method for transmitting user plane data is provided, where the method includes: the second network node receives a second message from the first network node, the second message including a user context identification of the terminal; the second message is for at least one of: the first network node obtains a 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.

In a third aspect, there is provided a first network node comprising: the receiving module is used for receiving a first message from a terminal, wherein the first message comprises a recovery identifier of the terminal and user plane data; a sending module, configured to send a second message, where the second message includes a user context identifier of the terminal; the second message is for at least one of: the first network node acquires a user context forwarded from a 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 a second network node.

In a fourth aspect, there is provided a second network node comprising: a receiving module, configured to receive a second message from a first network node, where the second message includes a user context identifier of a terminal; the second message is for at least one of: the first network node obtains a 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.

In a fifth aspect, there is provided a 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 when executed by the processor implementing the method according to the first aspect.

In a sixth aspect, there is provided a 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 when executed by the processor implementing the method according to the second aspect.

In a seventh aspect, there is provided a readable storage medium having stored thereon a program or instructions which when executed by a processor, implement the method according to the first aspect or implement the method according to the second aspect.

In an eighth aspect, there is provided a 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 when executed by the processor implementing the method according to the first aspect or implementing the method according to the second aspect.

In a ninth aspect, there is provided a chip comprising a processor and a communication interface, the communication interface and the processor being coupled, the processor being for running a program or instructions to implement the method according to the first aspect or to implement the method according to the second aspect.

In this embodiment of the present application, the first network node sends a second message after receiving a first message from a terminal, where the first message includes a recovery identifier of the terminal and user plane data, and the second message includes a user context identifier of the terminal, and the second message is used for at least one of: the first network node acquires a 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. Based on the second message, the first network node can forward the user plane data or forward the RRC message to the terminal, so that the sending delay of the user plane data is reduced, and the waiting time of the terminal is reduced.

Drawings

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

fig. 2 is a schematic flow chart of a method of transmitting user plane data according to one embodiment of the present application;

Fig. 3 is a schematic flow chart of a method of transmitting user plane data according to a specific embodiment of the present application;

fig. 4 is a schematic flow chart of a method of transmitting user plane data according to another specific embodiment of the present application;

fig. 5 is a schematic flow chart of a method of transmitting user plane data according to another embodiment of the present application;

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

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

fig. 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 following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate, such that embodiments of the present application may be implemented in sequences other than those illustrated or described herein, and that the "first" and "second" distinguished objects generally are of the type and do not limit the number of objects, e.g., the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.

It is noted that the techniques described in embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single-carrier frequency division multiple access (Single-carrier Frequency-Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the present application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. However, the following description describes a New air interface (NR) system for purposes of example, and NR terminology is used in much of the description below, these techniques are also applicable to applications other than NR system applications, such as generation 6 (6) ^th Generation, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network device 12. The terminal 11 may also be called a terminal Device or a User Equipment (UE), and the terminal 11 may be a terminal-side Device such as a mobile phone, a tablet Computer (Tablet Personal Computer), a Laptop (Laptop Computer) or a notebook (Personal Digital Assistant, PDA), a palm Computer, a netbook, an ultra-mobile personal Computer (ultra-mobile personal Computer, UMPC), a mobile internet Device (Mobile Internet Device, MID), a Wearable Device (or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and the Wearable Device includes: a bracelet, earphone, glasses, etc. Note that, the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may be a base station or a core network, wherein the base station may be called a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a node B, an evolved node B (eNB), a next generation node B (gNB), a home node B, a home evolved node B, a WLAN access point, a WiFi node, a transmission and reception point (Transmitting Receiving Point, TRP), or some other suitable terminology in the field, and the base station is not limited to a specific technical vocabulary, and it should be noted that, in the embodiment of the present application, only the base station in the NR system is taken 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 are described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.

As shown in fig. 2, one embodiment of the present application provides a method 200 for transmitting user plane data, which may be performed by a first network node, in other words, by software or hardware installed at the first network node, the method comprising the following steps.

S202: the first network node receives a first message from the terminal, the first message comprising a recovery identity of the terminal and user plane data.

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

In one scenario, the terminal receives an RRC Release (Release) message at a second network node to transition from a CONNECTED state (CONNECTED) to an INACTIVE state (INACTIVE), and the second network node maintains the user context of the terminal. Alternatively, the second network node may be an 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 comprises or indicates at least one of:

1) The triggering reason of the recovery process;

2) The terminal expects to transmit low-delay small data;

3) The terminal estimates that downlink data is sent subsequently;

4) The terminal then has uplink data to send.

Alternatively, the above-mentioned recovery procedure trigger cause may include one of the following: transmitting small data; time delay sensitive small data transmission; emergency small data transmission; high priority small data transmissions.

By this restoration procedure triggering reason, the first network node or the second network node can learn why the terminal triggers the small data transmission procedure by triggering the type of traffic data. For example, if the recovery procedure trigger cause carried by the terminal in the first message is delay-sensitive small data transmission, the first network node or the second network node may learn that the user plane data carried in the first message of the terminal is from delay-sensitive service.

S204: the first network node sends a second message, wherein the second message comprises a user context identifier of the terminal; the second message is for at least one of: the first network node acquires a user context forwarded from the second network node; the first network node forwards a radio resource control (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 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, which 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 to the second network node, which forwards to the user plane function (User Plane Function, UPF); in this example, the first network node may also receive downstream data from the second network node and forward the data to the terminal.

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

In yet another example, the second message is for the first network node to forward an RRC message forwarded by the second network node to the terminal. Alternatively, the RRC message may be an RRC release message, where the RRC message is an RRC release message, typically indicating that the second network node is not allowed to perform user plane data forwarding.

Optionally, the second message further comprises or indicates at least one of:

1) The triggering reason of the recovery process;

2) The terminal expects to transmit low-delay small data;

3) The terminal estimates that downlink data is sent subsequently;

4) The terminal subsequently has uplink data to send;

5) And the duration information is used for indicating the duration of establishing connection between the first network node and the terminal. In this way, the second network node may decide to propose downlink data forwarding and/or forward downlink data according to the duration information, so as to ensure that the downlink data is sent to the first network node in a time period corresponding to the duration information.

According to the transmission method of the user plane data, after receiving the first message from the terminal, the first network node sends the second message, wherein the first message comprises the recovery identifier of the terminal and the user plane data, the second message comprises the user context identifier of the terminal, and the second message is used for at least one of the following: the first network node acquires a 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. Based on the second message, the first network node can forward the user plane data or forward the RRC message to the terminal, so that the sending delay of the user plane data is reduced, and the waiting time of the terminal is reduced.

In one embodiment (hereinafter referred to as embodiment one for ease of distinction), after the first network node in embodiment 200 sends the second message, the method further comprises the steps of: the first network node receives a third message from the second network node, wherein the third message comprises first indication information; the first indication information indicates one of:

1) The user context of the terminal is not relocated;

2) The user context of the terminal is not repositioned and data forwarding is carried out;

3) Data forwarding and/or offloading is performed.

In an embodiment one, the second network node does not forward the user context of the terminal to the first network node.

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

Optionally, after the first network node receives the third message from the second network node, the method further comprises: and the first network node sends a fourth message according to the first indication information, wherein the fourth message is used for indicating that the first network node proposes to forward uplink data.

Optionally, there is a one-to-one correspondence between uplink data forwarding and logical channels; wherein, the uplink data forwarding is performed according to each logical channel (per LCH), the uplink data forwarding tunnel is established/maintained/modified/torn down according to granularity (LCH level) of LCH, and the uplink data forwarding tunnel forwards radio link layer control protocol data units (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) bearers; the uplink data forwarding is performed according to each logical channel (per RLC bearer), the uplink data forwarding tunnel is established/maintained/modified/torn down according to granularity of RLC bearers, and the uplink data forwarding tunnel forwards packet data convergence protocol data units (Packet Data Convergence Protocol Protocol Data Unit, PDCP PDUs).

The fourth message may include at least one of:

1) The identity of the terminal;

2) One or more logic channel information corresponding to the user plane data;

3) One or more RLC bearer information (e.g., RLC bearer ID) corresponding to the user plane data; wherein, the RLC bearer information and the logical channel information have a one-to-one mapping relationship (for example, the mapping relationship may be agreed by a protocol, and logical channel information 1 corresponds to RLC bearer information 1); the RLC bearer information may also be logical channel information.

4) And the uplink forwarding proposal domain is used for proposing uplink data forwarding.

In one embodiment (hereinafter referred to as embodiment two for ease of distinction), after the first network node in embodiment 200 sends the second message, the method further includes: the first network node receives a fifth message from the second network node, the fifth message comprising a user context of the terminal and second indication information, the second indication information indicating one of:

1) The user context of the terminal is not relocated;

3) Data forwarding and/or offloading is performed.

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

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

In a second embodiment, after the first network node receives the fifth message from the second network node, the method further comprises: and the first network node sends a sixth message according to the second indication information, wherein the sixth message is used for indicating that the first network node proposes to forward uplink data.

Optionally, the uplink data forwarding has a one-to-one correspondence with a quality of service (Quality of Service, qoS) flow or protocol data unit (Protocol Data Unit, PDU) session.

The sixth message may include at least one of:

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) And the uplink forwarding proposal domain is used for proposing uplink data forwarding.

In the first embodiment, after the first network node sends the fourth message; or in the second embodiment, after the first network node sends the sixth message, the method may further include the following steps: the first network node receives a seventh message from the second network node, wherein the seventh message is used for establishing an uplink data forwarding tunnel.

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

Optionally, the seventh message may include at least one of:

1) The identity of the terminal;

2) One or more logical channel information;

3) One or more QoS flow information;

4) One or more PDU session information;

5) And transmitting associated transport layer information with the Xn user plane, wherein the transport layer information is used for forwarding uplink data.

6) One or more RLC carries information.

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

In other embodiments, if the second network node does not allow forwarding of the uplink data, in the first embodiment, the first network node sends the fourth message; or in the second embodiment, after the first network node sends the sixth message, the method may further include the following steps: the first network node receiving an eighth message from the second network node, the eighth message may include an RRC release message; the first 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 comprises: the first network node receives 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.

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 further forward the downlink data from the UPF to the first network node, and then forward the downlink data from the UPF to the terminal by the first network node.

Optionally, the ninth message includes at least one of: 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; and the downlink forwarding proposal domain is used for proposing downlink data forwarding.

Optionally, the tenth message includes at least one of: 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; and transmitting associated transport layer information with the Xn user plane, wherein the transport layer information is used for forwarding 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 sends an eleventh message; wherein the eleventh message is configured to indicate at least one of: requesting release of a user context of the terminal; request to end data forwarding and/or offloading; the request ends for small data transmissions.

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 receiving a twelfth message from the second network node; wherein the twelfth message is used for indicating at least one of the following: releasing the user context information of the terminal; ending data forwarding and/or splitting; ending the small data transmission; allowing release of resources associated with the user context of the terminal.

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

In case the first network node receives a twelfth message from the second network node, the method further comprises at least one of:

1) Releasing resources associated with a user context of the terminal;

2) Forwarding an RRC release message carried by the twelfth message to the terminal;

3) And continuing to forward uplink data, wherein the uplink data is received from the first message by the first network node.

Optionally, on the basis of the second embodiment, after the first network node receives the twelfth message from the second network node, the method further includes: the first network node releasing the user context of the terminal

And/or

Transmitting 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 that the data forwarding is successful;

indicating a success of forwarding the RRC release message to the terminal;

indicating that the data transmission process was successful.

In order to describe the transmission method of the user plane data provided in the embodiments of the present application in detail, the following description will be made with reference to two specific embodiments.

Example 1

In this embodiment one, the second network node (or referred to as old node or anchor node) does not send UE context to the first network node (or referred to as new node), and the first network node forwards RLC PDU to the second network node through the user plane data forwarding tunnel.

As shown in fig. 3, this embodiment includes the steps of:

step 1: the INACTIVE UE sends a first protocol data unit (corresponding to the first message in the foregoing embodiment) containing a resume ID (resume ID) of the UE, a UE identity authentication ID, a resume procedure trigger reason, user plane data, and so on.

Alternatively, the cause of triggering the resume procedure may be set to be small data transmission/delay sensitive small data transmission/emergency small data transmission/high priority small data transmission, which means small data transmission for small data transmission/delay sensitive small data transmission/small data transmission for emergency service/small data transmission for high priority service during the resume procedure.

Optionally, the first data unit may further include an indication/code point/bitmap (e.g., a 1bit indication, e.g., using 00 of code points [00,01,10,11], e.g., the most significant bit of the bitmap), which indicates whether the UE desires low latency small data transmission.

Optionally, the first data unit may further include an indication/code point/bitmap (e.g. a 1bit indication, e.g. using 10 of the code points [00,01,10,11], e.g. the next lower bit indication in the bitmap), where the indication/code point/bitmap is used to indicate whether the UE estimates that downlink data is transmitted subsequently.

Optionally, the first data unit may further include an indication/code point/bitmap (e.g. a 1bit indication, e.g. using 01 in code points [00,01,10,11], e.g. the lowest bit in bitmap), which indicates whether the UE has uplink data to send subsequently.

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, where the second message is sent to enable the first network node to forward the user plane data to the second network node. Optionally, the second message is for at least one of:

the first network node acquires a user context forwarded from a second network node;

the first network node forwards a Radio Resource Control (RRC) message forwarded by the second network node to the terminal;

the first network node forwards data to a second network node.

Optionally, the second message may further include a resume procedure trigger reason.

Optionally, the second message may further include an indication/code point/bitmap (e.g., a 1bit indication, e.g., using 00 of code points [00,01,10,11], e.g., the most significant bit of the bitmap), which indicates whether the UE desires low latency small data transmission.

Optionally, the second message may further include an indication/code point/bitmap (e.g. a 1bit indication, e.g. using 10 of the code points [00,01,10,11], e.g. the next lower bit indication in the bitmap), where the indication/code point/bitmap is used to indicate whether the UE predicts that downlink data is sent subsequently.

Optionally, the second message may further include an indication/code point/bitmap (e.g. a 1bit indication, e.g. using 01 in code points [00,01,10,11], e.g. the next lower bit indication in bitmap), where the indication/code point/bitmap is used to indicate whether the UE predicts that uplink data is sent subsequently.

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

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 including at least a cause value.

Optionally, the cause value in the third message may indicate any of the following reasons:

relocation (re-location) of the UE context is not performed;

re-positioning is not carried out on the UE context and data forwarding is proposed;

data forwarding and/or offloading is performed because the first network node is told that: and establishing an uplink data forwarding tunnel to forward the uplink data.

Optionally, the third message may further include an indication, where the indication is used to indicate that uplink data forwarding is proposed, and the indication is used to tell the first network node: and establishing an uplink data forwarding tunnel to forward the uplink data.

Step 4: according to the indication of the third message, the first network node sends a fourth message to the second network node, wherein the fourth message is used for indicating that the first network node proposes uplink data forwarding.

Optionally, the uplink data forwarding has a one-to-one correspondence with a logical channel (e.g., per logical channel)

Optionally, the fourth message may contain one or more of the following:

the identity corresponding to the UE, (e.g., UE Context ID, resume ID);

one or more logical channel information (e.g., logical channel ID) corresponding to user plane data in the UE first protocol data unit;

And the uplink forwarding proposal domain is used for proposing uplink data forwarding.

Step 5: if the second network node decides to allow the uplink data forwarding corresponding to the at least one logical channel, the second network node responds to the seventh message to the first network node, wherein the seventh message is used for establishing an uplink data forwarding tunnel towards the second network node. In this way, the first network node can forward the 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:

the identity corresponding to the UE, (e.g., UE Context ID, resume ID);

one or more logical channel information (e.g., logical channel IDs);

and transmitting associated transport layer information with the Xn user plane, wherein the information is used for forwarding uplink data to the second network node.

In other embodiments, the embodiment may further include step 5A: if the second network node decides not to allow data forwarding corresponding to any one of the logical channels, the second network node responds to the first network node with an eighth message, which may contain one or more of the following:

The identity corresponding to the UE, (e.g., UE Context ID, resume ID);

RRC Release message. The first network node transparently (e.g., does not parse the RRC Release message) sends the RRC Release message to the UE.

Step 6: the second network node sends a ninth message to the first network node, the ninth message being used to indicate that the second network node proposes to forward downstream data.

Optionally, the downstream data forwarding has a one-to-one correspondence with a logical channel (e.g., per logical channel).

Optionally, the ninth message may contain one or more of the following:

the identity corresponding to the UE, (e.g., UE Context ID, resume ID);

one or more logical channel information (e.g., logical channel IDs);

a downstream forwarding proposal field for proposing downstream data forwarding.

Step 7: if the first network node decides to allow the downlink data forwarding corresponding to the at least one logical channel, the first network node responds to a tenth message to the second network node, wherein the tenth message is used for establishing a downlink data forwarding tunnel towards the first network node.

Optionally, the tenth message may contain one or more of the following:

The identity corresponding to the UE, (e.g., UE Context ID, resume ID);

one or more logical channel information (e.g., logical channel IDs);

and transmitting associated transport layer information with the Xn user plane, wherein the information is used for forwarding downlink data to the first network node.

Step 8: the first network node sending an eleventh message to the second network node, the eleventh message being for the first network node to indicate to the second network node: requesting release of a user context of the terminal; request to end data forwarding and/or offloading; the request ends for small data transmissions.

Step 9: the second network node sends twelve messages to the first network node, the second network node indicating to the first network node: releasing the user context information of the terminal; ending data forwarding and/or splitting; ending the small data transmission; allowing release of resources associated with the user context of the terminal.

Optionally, the twelfth message is for responding to an eleventh message;

optionally, the twelfth message may be further used for the second network node to indicate to the first network node: allowing release of resources (e.g., radio resources, control plane resources) associated with the UE (e.g., associated with an identity corresponding to the UE).

Optionally, the twelfth message includes an RRC Release message. At this point, the first network node transparently (e.g., 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 forwarding 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 containing the RRC Release message, the second network node updates the UE air interface security message (e.g., acquires the new NCC from the AMF and updates the saved UE context).

Step 11: the first network node sends a thirteenth message for at least one of:

responding to the twelfth message;

indicating that the data forwarding is successful;

indicating a success of forwarding the RRC release message to the terminal;

indicating that the data transmission process was successful.

Example two

In the second embodiment, the second network node (or referred to as Old node or anchor node) sends the UE context to the first network node (or referred to as new node), the first network node forwards the SDAP-SDU to the second network node through the user plane data forwarding tunnel, 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 fig. 4, this embodiment includes the steps of:

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.

The detailed description of step 1 and step 2 in the second embodiment can be referred to the description of step 1 and step 2 in the first embodiment, and the description thereof will not be repeated here to avoid repetition.

Step 3: if the second network node is able to identify the UE context and successfully verify the UE identity and decide to provide the UE context to the first network node, the second network node responds to a fifth message comprising at least UE context information and second indication information, said second indication information indicating one of the following:

the user context of the terminal is not relocated;

the user context of the terminal is not repositioned and data forwarding is carried out;

Data forwarding and/or offloading is performed.

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

Optionally, the uplink data forwarding has a one-to-one correspondence with Qos flow or PDU session (e.g., per Qos flow or per PDU session). Specifically, the uplink data forwarding is performed according to each logical channel (per Qos flow or per PDU session), the uplink data forwarding tunnel is established/maintained/modified/removed according to granularity of Qos flow or PDU session, and the SDAP-SDU is forwarded in the uplink data forwarding tunnel.

Optionally, the sixth message may contain one or more of the following:

information of one or more PDU sessions (e.g., PDU session ID) corresponding to user plane data in the UE first protocol data unit;

information (e.g., qoS flow ID) of one or more QoS flows corresponding to user plane data in the UE first protocol data unit;

Step 5: if the second network node decides to allow the uplink data forwarding corresponding to at least one Qos flow or PDU session, the second network node responds to the first network node with a seventh message, where the seventh message is used to establish an uplink data forwarding tunnel towards the second network node.

Optionally, the seventh message may contain one or more of the following:

the identity of the terminal;

one or more Qos flow or PDU session (session) information;

transmitting associated transport layer information with the Xn user plane, the information being for forwarding uplink data to the second network node;

in other embodiments, step 5A may be further included: if the second network node decides that the data forwarding corresponding to any one of Qos flow or PDU session is not allowed, the second network node responds to the first network node with an eighth message, wherein the eighth message comprises an RRC Release message. The first network node transparently (e.g., does not parse the RRC Release message) sends the RRC Release message to the UE.

Optionally, the downlink data forwarding has a one-to-one correspondence (per QoS flow or per PDU session) with PDU session or QoS flow.

Optionally, the ninth message may contain one or more of the following:

the identity of the terminal;

one or more Qos flow or PDU session information;

Step 7: if the first network node decides to allow the downlink data forwarding corresponding to at least one Qos flow or PDU session, the first network node responds to a tenth message to the second network node, where the tenth message is used to establish a downlink data forwarding tunnel towards the first network node.

Optionally, the tenth message may contain one or more of the following:

the identity of the terminal;

one or more Qos flow or PDU session information;

transmitting associated transport layer information with the Xn user plane, the information being for forwarding downstream data to the first network node;

Step 9: the second network node sending a twelfth message to the first network node, the second network node indicating to the first network node: releasing the user context information of the terminal; ending data forwarding and/or splitting; ending the small data transmission; allowing release of resources associated with the user context of the terminal.

Optionally, the twelfth message is for responding to an eleventh message;

optionally, the twelfth message may be further used for the second network node to indicate to the first network node: allowing release of resources (e.g., radio resources, control plane resources) associated with the UE Context ID.

Step 11: and after the first network node receives the twelfth message, releasing the stored UE context.

Step 12: the first network node sends a thirteenth message for at least one of:

responding to the twelfth message;

indicating that the data forwarding is successful;

indicating a success of forwarding the RRC release message to the terminal;

indicating that the data transmission process was successful.

The transmission method of the user plane data according to the embodiment of the present application is described in detail above with reference to fig. 2 to 4. A method for transmitting user plane data according to another embodiment of the present application will be described in detail with reference to fig. 5. It will be appreciated that the interaction of the second network node with 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 the relevant description is omitted appropriately to avoid repetition.

Fig. 5 is a schematic flow chart of an implementation 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:

s502: the second network node receives a second message from the first network node, the second message including a user context identification of the terminal; the second message is for at least one of: the first network node acquires a 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 this embodiment of the present application, the first network node sends a second message after receiving a first message from a terminal, where the first message includes a recovery identifier of the terminal and user plane data, and the second message includes a user context identifier of the terminal, and the second message is used for at least one of: the first network node acquires a 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 a second network node. Based on the second message, the first network node can forward the user plane data or forward the RRC message to the terminal, so that the sending delay of the user plane data is reduced, and the waiting time of the terminal is reduced.

Optionally, as an embodiment, the second message further includes or indicates at least one of:

the triggering reason of the recovery process;

the terminal expects to transmit low-delay small data;

the terminal estimates that downlink data is sent subsequently;

the terminal is provided with uplink data transmission subsequently;

and the time length information is used for indicating the time length for establishing 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 time length information.

Optionally, as an embodiment, the recovery procedure triggering reason includes one of the following: transmitting small data; time delay sensitive small data transmission; emergency small data transmission; high priority small data transmissions.

Optionally, as an embodiment, after the second network node receives the second message, the method further comprises:

the second network node sends a third message; or (b)

The second network node sends a third message according to the second message;

the third message includes first indication information indicating one of:

the user context of the terminal is not relocated;

data forwarding and/or offloading is performed.

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 that the first network node proposes uplink data forwarding.

Optionally, as an embodiment, the uplink data forwarding has a one-to-one correspondence with a logical channel or RLC bearer.

Optionally, as an embodiment, the fourth message includes at least one of:

the identity of the terminal;

one or more logic channel information corresponding to the user plane data;

one or more pieces of RLC bearing information corresponding to the user plane data, wherein the RLC bearing information is used for forwarding uplink data; the RLC bearing information and the logic channel information have a one-to-one mapping relation;

the second network node sends a fifth message; or (b)

The second network node sends a fifth message according to the second message;

the fifth message includes a user context of the terminal and second indication information indicating one of:

the user context of the terminal is not relocated;

data forwarding and/or offloading is 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 that the first network node proposes uplink data forwarding.

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

Optionally, as an embodiment, the sixth message includes at least one of:

one or more QoS flow information corresponding to the user plane data;

one or more PDU session information corresponding to the user plane data;

Optionally, as an embodiment, the method further includes:

and the second network node sends a seventh message, wherein the seventh message is used for establishing an uplink data forwarding tunnel.

Optionally, as an embodiment, the seventh message includes at least one of:

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;

and transmitting associated transport layer information with the Xn user plane, wherein the transport layer information is used for forwarding uplink data.

Optionally, as an embodiment, in case the second network node is not allowed to forward data, the method further comprises:

the second network node sends an eighth message comprising an RRC release message.

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, and the ninth message indicates that the second network node proposes downlink data forwarding;

the second network node receives a tenth message from the first network node, wherein the tenth message is used for establishing a downlink data forwarding tunnel.

Optionally, as an embodiment, the ninth message includes at least one of: 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 domain, where the downlink forwarding proposal domain is used for proposing downlink data forwarding; and/or

The tenth message includes at least one of: 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; and transmitting associated transport layer information with the Xn user plane, wherein the transport layer information is used for forwarding downlink 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 configured to indicate at least one of: requesting release of a user context of the terminal; request to end data forwarding and/or offloading; the request ends for small data transmissions.

Optionally, as an embodiment, the method further includes: the second network node sends a twelfth message;

wherein the twelfth message is used for indicating at least one of the following: releasing the user context information of the terminal; ending data forwarding and/or splitting; ending the small data transmission; allowing 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: and updating the air interface safety 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, the thirteenth message for at least one of:

Responding to the twelfth message;

indicating that the data forwarding is successful;

indicating a success of forwarding the RRC release message to the terminal;

indicating that the data transmission 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, a first network node 600 includes:

a receiving module 602, 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 604, configured to send a second message, where the second message includes a user context identifier of the terminal; the second message is for at least one of:

the first network node forwards the RRC message forwarded by the second network node to the terminal;

the first network node forwards data to a second network node.

Alternatively, the first and second modules may, as one embodiment,

the first message further includes or indicates at least one of:

the triggering reason of the recovery process;

the terminal expects to transmit low-delay small data;

the terminal estimates that downlink data is sent subsequently;

the terminal is provided with uplink data transmission subsequently;

and/or

The second message further includes or indicates at least one of:

the triggering reason of the recovery process;

the terminal expects to transmit low-delay small data;

the terminal estimates that downlink data is sent subsequently;

the terminal is provided with uplink data transmission subsequently;

and the duration information is used for indicating the duration of establishing connection between the first network node and the terminal.

Optionally, as an embodiment, the receiving module 602 may be further configured to:

receiving a third message from the second network node, the third message comprising first indication information; the first indication information indicates one of:

The user context of the terminal is not relocated;

data forwarding and/or offloading is performed.

Optionally, as an embodiment, the sending module 604 may be further configured to:

and sending a fourth message according to the first indication information, wherein the fourth message is used for indicating that the first network node proposes to forward uplink data.

Optionally, as an embodiment, the uplink data forwarding has a one-to-one correspondence with a logical channel or radio link control RLC bearer.

Optionally, as an embodiment, the fourth message includes at least one of:

the identity of the terminal;

one or more logic channel information corresponding to the user plane data;

Receiving a fifth message from the second network node, the fifth message comprising a user context of the terminal and second indication information, the second indication information indicating one of:

the user context of the terminal is not relocated;

data forwarding and/or offloading is performed.

and sending a sixth message according to the second indication information, wherein the sixth message is used for indicating that the first network node proposes uplink data forwarding.

Optionally, as an embodiment, the sixth message includes at least one of:

one or more QoS flow information corresponding to the user plane data;

one or more PDU session information corresponding to the user plane data;

And receiving a seventh message from the second network node, wherein the seventh message is used for establishing an uplink data forwarding tunnel.

Optionally, as an embodiment, the seventh message includes at least one of:

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;

receiving an eighth message from the second network node, the eighth message comprising an RRC release message;

the first network node sends the RRC release message to the terminal.

receiving a ninth message from the second network node, the ninth message indicating that the second network node proposes downlink data forwarding;

the sending module 604 may be further configured to: and transmitting a tenth message, wherein the tenth message is used for establishing a downlink data forwarding tunnel.

Alternatively, the first and second modules may, as one embodiment,

the ninth message includes at least one of: 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 domain, where the downlink forwarding proposal domain is used for proposing downlink data forwarding; and/or

Optionally, as an embodiment, the sending module 604 may be further configured to: transmitting an eleventh message;

receiving a twelfth message from the second network node;

Optionally, as an embodiment, the first network node is further configured to at least one of:

releasing resources associated with a user context of the terminal;

forwarding an RRC release message carried by the twelfth message to the terminal;

and continuing to forward uplink data, wherein the uplink data is received from the first message by the first network node.

Optionally, as an embodiment, the first network node 600 is further configured to:

releasing the user context of the terminal; and/or

Transmitting, by the transmitting module 604, a thirteenth message for at least one of:

responding to the twelfth message;

indicating that the data forwarding is successful;

indicating a success of forwarding the RRC release message to the terminal;

indicating that the data transmission process was successful.

The first network node 600 according to the embodiments of the present application may refer to the flow of the method 200 corresponding to the embodiments of the present application, and each unit/module in the first network node 600 and the other operations and/or functions described above are respectively for implementing the corresponding flow in the method 200, and may achieve the same or equivalent technical effects, which are not described herein for brevity.

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, a second network node 700 includes:

a receiving module 702, configured to receive a second message from the first network node, where the second message includes a user context identification of the terminal; the second message is for at least one of:

the first network node obtains a user context forwarded from the second network node;

the first network node forwards data to the second network node.

the triggering reason of the recovery process;

the terminal expects to transmit low-delay small data;

the terminal estimates that downlink data is sent subsequently;

the terminal is provided with uplink data transmission subsequently;

Optionally, as an embodiment, the second network node 700 further includes a sending module, which may be configured to:

sending a third message; or (b)

Sending a third message according to the second message;

the third message includes first indication information indicating one of:

the user context of the terminal is not relocated;

Data forwarding and/or offloading is performed.

Optionally, as an embodiment, the receiving module 702 may be further configured to:

and receiving a fourth message, wherein the fourth message is used for indicating that the first network node proposes uplink data forwarding.

Optionally, as an embodiment, the fourth message includes at least one of:

the identity of the terminal;

one or more logic channel information corresponding to the user plane data;

sending a fifth message; or (b)

According to the second message, a fifth message is sent;

The user context of the terminal is not relocated;

data forwarding and/or offloading is performed.

a sixth message is received, the sixth message being used to indicate that the first network node proposes uplink data forwarding.

Optionally, as an embodiment, the sixth message includes at least one of:

one or more QoS flow information corresponding to the user plane data;

one or more PDU session information corresponding to the user plane data;

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

Optionally, as an embodiment, the seventh message includes at least one of:

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;

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

Optionally, as an embodiment, the second network node 700 further includes a sending module, which may be configured to: the second network node sends a ninth message, and the ninth message indicates that the second network node proposes downlink data forwarding;

the receiving module 702 may be further configured to: and receiving a tenth message from the first network node, wherein the tenth message is used for establishing a downlink data forwarding tunnel.

Alternatively, the first and second modules may, as one embodiment,

Optionally, as an embodiment, the receiving module 702 may be further configured to: receiving an eleventh message from the first network node;

Optionally, as an embodiment, the second network node 700 further includes a sending module, which may be configured to: transmitting a twelfth message;

Optionally, as an embodiment, the second network node 700 further includes an update module, which may be configured to: and updating the air interface safety 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: receiving a thirteenth message from the first network node, the thirteenth message for at least one of:

responding to the twelfth message;

indicating that the data forwarding is successful;

indicating a success of forwarding the RRC release message to the terminal;

indicating that the data transmission process was successful.

The second network node 700 according to the embodiment of the present application may refer to the flow corresponding to the method 500 of the embodiment of the present application, and each unit/module in the second network node 700 and the other operations and/or functions described above are respectively for implementing the corresponding flow in the method 500, and may achieve the same or equivalent technical effects, which are not described herein for brevity.

Optionally, as shown in fig. 8, the embodiment of the present application further provides a communication device 800, including a processor 801, a memory 802, and a program or an instruction stored in the memory 802 and capable of running on the processor 801, for example, when the communication device 800 is a network node, the program or the instruction is executed by the processor 801 to implement each process of the foregoing embodiment of the method for transmitting user plane data, and the same technical effects can be achieved, so that repetition is avoided and no description is repeated here.

Specifically, the embodiment of the application also provides network side equipment. As shown in fig. 9, the network device 900 includes: an antenna 91, a radio frequency device 92, a baseband device 93. The antenna 91 is connected to a radio frequency device 92. In the uplink direction, the radio frequency device 92 receives information via the antenna 91, and transmits the received information to the baseband device 93 for processing. In the downlink direction, the baseband device 93 processes information to be transmitted, and transmits the processed information to the radio frequency device 92, and the radio frequency device 92 processes the received information and transmits the processed information through the antenna 91.

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

The baseband device 93 may, for example, comprise at least one baseband board on which a plurality of chips are disposed, as shown in fig. 9, where one chip, for example, a processor 94, is connected to the memory 95 to invoke a program in the memory 95 to perform the network device operations shown in the above method embodiment.

The baseband device 93 may also include a network interface 96 for interacting with the radio frequency device 92, such as a common public radio interface (common public radio interface, CPRI for short).

Specifically, the network side device of the embodiment of the present invention further includes: instructions or programs stored in the memory 95 and executable on the processor 94, the processor 94 invokes the instructions or programs in the memory 95 to perform the methods performed by the modules shown in fig. 6 and 7, and achieve the same technical effects, and are not repeated here.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the processes of the foregoing user plane data transmission method embodiment are implemented, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.

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

The embodiment of the application further provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction, implement each process of the above-mentioned user plane data transmission method embodiment, and achieve the same technical effect, so that repetition is avoided, and no further description is given here.

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

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises 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 an opposite order depending on the functions involved, e.g., 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 certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), including several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.

Claims

1. A method for transmitting user plane data, the method comprising:

the method comprises the steps that a first network node receives a first message from a terminal, wherein the first message comprises a recovery identifier of the terminal and user plane data;

the first network node sends a second message, wherein the second message comprises a user context identifier of the terminal; the second message is for at least one of:

the first network node forwards data to a second network node;

the first network node receives a third message from the second network node, wherein the third message comprises first indication information; the first indication information indicates one of:

data forwarding and/or offloading is performed.

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

the first message further includes or indicates at least one of:

the triggering reason of the recovery process;

the terminal expects to transmit low-delay small data;

The terminal estimates that downlink data is sent subsequently;

the terminal is provided with uplink data transmission subsequently;

and/or

The second message further includes or indicates at least one of:

the triggering reason of the recovery process;

the terminal expects to transmit low-delay small data;

the terminal estimates that downlink data is sent subsequently;

the terminal is provided with uplink data transmission subsequently;

3. The method of claim 2, wherein the recovery procedure trigger cause comprises one of: transmitting small data; time delay sensitive small data transmission; emergency small data transmission; high priority small data transmissions.

4. The method of claim 1, wherein after the first network node receives the third message from the second network node, the method further comprises:

and the first network node sends a fourth message according to the first indication information, wherein the fourth message is used for indicating that the first network node proposes to forward uplink data.

5. The method of claim 4, wherein the uplink data forwarding has a one-to-one correspondence with a logical channel or radio link control, RLC, bearer.

6. The method of claim 4, wherein the fourth message comprises at least one of:

the identity of the terminal;

one or more logic channel information corresponding to the user plane data;

one or more pieces of RLC bearing information corresponding to the user plane data, wherein the RLC bearing information is used for forwarding uplink data, and a one-to-one mapping relation exists between the RLC bearing information and the logic channel information;

7. The method of 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, the fifth message comprising a user context of the terminal and second indication information, the second indication information indicating one of:

the user context of the terminal is not relocated;

data forwarding and/or offloading is performed.

8. The method of claim 7, wherein after the first network node receives the fifth message from the second network node, the method further comprises:

And the first network node sends a sixth message according to the second indication information, wherein the sixth message is used for indicating that the first network node proposes to forward uplink data.

9. The method of claim 8, wherein the uplink data forwarding has a one-to-one correspondence with a quality of service QoS flow or protocol data unit PDU session.

10. The method of claim 8, wherein the sixth message comprises at least one of:

one or more QoS flow information corresponding to the user plane data;

one or more PDU session information corresponding to the user plane data;

11. The method according to claim 4 or 8, characterized in that the method further comprises:

the first network node receives a seventh message from the second network node, wherein the seventh message is used for establishing an uplink data forwarding tunnel.

12. The method of claim 11, wherein the seventh message comprises at least one of:

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;

13. The method according to claim 4 or 8, characterized in that the method further comprises:

the first network node receiving an eighth message from the second network node, the eighth message comprising an RRC release message;

the first network node sends the RRC release message to the terminal.

14. The method of claim 11, wherein after the first network node receives the seventh message from the second network node, the method further comprises:

the first network node receives a ninth message from the second network node, the ninth message indicating that the second network node proposes to forward downlink data;

and the first network node sends a tenth message, wherein the tenth message is used for establishing a downlink data forwarding tunnel.

15. The method of claim 14, wherein the step of providing the first information comprises,

16. The method of claim 11, wherein the method further comprises: the first network node sends an eleventh message;

wherein the eleventh message is used to indicate at least one of: requesting release of a user context of the terminal; request to end data forwarding and/or offloading; the request ends for small data transmissions.

17. The method of claim 15, wherein the method further comprises: the first network node sends an eleventh message;

18. The method of claim 11, wherein the method further comprises: the first network node receiving a twelfth message from the second network node;

Wherein the twelfth message is used to indicate at least one of: releasing the user context information of the terminal; ending data forwarding and/or splitting; ending the small data transmission; allowing release of resources associated with the user context of the terminal.

19. The method of claim 16, wherein the method further comprises: the first network node receiving a twelfth message from the second network node;

20. The method of claim 18, further comprising at least one of:

releasing resources associated with a user context of the terminal;

21. The method of claim 18, wherein after the first network node receives the twelfth message from the second network node, the method further comprises:

Releasing the user context of the terminal; and/or

Transmitting a thirteenth message for at least one of:

responding to the twelfth message;

indicating that the data forwarding is successful;

indicating a success of forwarding the RRC release message to the terminal;

indicating that the data transmission process was successful.

22. A method for transmitting user plane data, the method comprising:

the second network node receives a second message from the first network node, the second message including a user context identification of the terminal; the second message is for at least one of:

the first network node forwards data to the second network node;

the second network node sends a third message; or the second network node sends a third message according to the second message; the third message includes first indication information indicating one of:

data forwarding and/or offloading is performed.

23. The method of claim 22, wherein the second message further comprises or indicates at least one of:

the triggering reason of the recovery process;

the terminal expects to transmit low-delay small data;

the terminal estimates that downlink data is sent subsequently;

the terminal is provided with uplink data transmission subsequently;

24. The method of claim 23, wherein the recovery procedure trigger cause comprises one of: transmitting small data; time delay sensitive small data transmission; emergency small data transmission; high priority small data transmissions.

25. The method of claim 22, wherein after the second network node sends the third message, the method further comprises:

26. The method of claim 25, wherein the uplink data forwarding has a one-to-one correspondence with a logical channel or RLC bearer.

27. The method of claim 25, wherein the fourth message comprises at least one of:

the identity of the terminal;

one or more logic channel information corresponding to the user plane data;

28. The method according to claim 22 or 23, wherein after the second network node receives the second message, the method further comprises:

the second network node sends a fifth message; or (b)

The second network node sends a fifth message according to the second message;

the user context of the terminal is not relocated;

data forwarding and/or offloading is performed.

29. The method of claim 28, wherein after the second network node sends the fifth message, the method further comprises:

30. The method of claim 29, wherein the uplink data forwarding has a one-to-one correspondence with a quality of service QoS flow or protocol data unit PDU session.

31. The method of claim 29, wherein the sixth message comprises at least one of:

one or more QoS flow information corresponding to the user plane data;

one or more PDU session information corresponding to the user plane data;

32. The method according to claim 25 or 29, characterized in that the method further comprises:

33. The method of claim 32, wherein the seventh message comprises at least one of:

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;

34. The method according to claim 25 or 29, wherein in case the second network node is not allowed to forward data, the method further comprises:

35. The method of claim 32, wherein after the second network node sends the seventh message, the method further comprises:

36. The method of claim 35, wherein the step of determining the position of the probe is performed,

37. The method of claim 32, wherein the method further comprises: the second network node receiving an eleventh message from the first network node;

38. The method of claim 32, wherein the method further comprises: the second network node sends a twelfth message;

39. The method of claim 37, wherein the method further comprises: the second network node sends a twelfth message;

40. The method of claim 38, wherein prior to the second network node sending the twelfth message, the method further comprises: and updating the air interface safety message of the terminal.

41. The method of claim 38, wherein after the second network node sends the twelfth message, the method further comprises:

receiving a thirteenth message from the first network node, the thirteenth message for at least one of:

responding to the twelfth message;

indicating that the data forwarding is successful;

indicating a success of forwarding the RRC release message to the terminal;

indicating that the data transmission process was successful.

42. A first network node, comprising:

the receiving module is used for receiving a first message from a terminal, wherein the first message comprises a recovery identifier of the terminal and user plane data;

a sending module, configured to send a second message, where the second message includes a user context identifier of the terminal; the second message is for at least one of:

the first network node forwards data to a second network node;

the receiving module is 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 one of:

data forwarding and/or offloading is performed.

43. A second network node, comprising:

a receiving module, configured to receive a second message from a first network node, where the second message includes a user context identifier of a terminal; the second message is for at least one of:

the first network node forwards data to the second network node;

the sending module is used for sending the third message; or sending a third message according to the second message; the third message includes first indication information indicating one of:

data forwarding and/or offloading is performed.

44. A network node comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which when executed by the processor implements a method of transmitting user plane data as claimed in any one of claims 1 to 41.

45. A readable storage medium having stored thereon a program or instructions which when executed by a processor implement a method of transmitting user plane data according to any one of claims 1 to 41.