CN114095138A

CN114095138A - User plane data transmission method and network node

Info

Publication number: CN114095138A
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: 2022-02-25
Anticipated expiration: 2040-08-24
Also published as: WO2022042440A1; CN114095138B

Abstract

The embodiment of the application discloses a user plane data transmission method and a network node, which can solve the problem of long transmission delay of user plane data. The method comprises the following steps: a first network node receives a first message from a terminal, wherein the first message comprises a recovery identifier and user plane data of the terminal; 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 obtaining a user context handed over from a second network node; the first network node forwards a Radio Resource Control (RRC) message forwarded by a 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 present application belongs to the field of communication technology, and in particular, relates to a method for transmitting user plane data and a network node.

Background

For a terminal supporting small data transmission and in an inactive state, small data (user plane data) transmission is generally achieved by initiating a Radio Resource Control (RRC) recovery procedure. Specifically, the terminal may multiplex the encrypted user plane Data and the like in a Media Access Control Protocol Data Unit (MAC PDU) and send the MAC PDU to the network node. If the network node that receives the MAC PDU of the terminal does not store the User context (UE context) of the terminal, the network node cannot decrypt the User Plane data or forward the User Plane data to a User Plane Function (UPF) entity, and 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, so that the transmission delay of the User Plane data is large.

Disclosure of Invention

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

In a first aspect, a method for transmitting user plane data is provided, where the method includes: a first network node receives a first message from a terminal, wherein the first message comprises a recovery identifier and user plane data of the terminal; 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 obtaining a user context handed over from a second network node; the first network node forwards a Radio Resource Control (RRC) message forwarded by a 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, the method including: the second network node receives a second message from the first network node, wherein the second message comprises the user context identification of the terminal; the second message is for at least one of: the first network node obtaining a 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 data to the second network node.

In a third aspect, a first network node is provided, comprising: a receiving module, configured to receive a first message from a terminal, where the first message includes a recovery identifier and user plane data of the terminal; 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 obtaining a user context handed over 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, a second network node is provided, 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 obtaining a 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 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 instructions stored on the memory and executable on the processor, which when executed by the processor implements the method according to the first aspect.

In a sixth aspect, a second network node is provided, comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, which when executed by the processor, implements the method according to the second aspect.

In a seventh aspect, there is provided a readable storage medium on which is stored a program or instructions which, when executed by a processor, implements the method of the first aspect or implements the method of the second aspect.

In an eighth aspect, a computer program product is provided, which comprises a processor, a memory, and a program or instructions stored on the memory and executable on the processor, which when executed by the processor, implements the method according to the first aspect, or implements 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 being coupled to the processor, the processor being configured to execute a program or instructions to implement the method according to the first aspect, or to implement the method according to the second aspect.

In an 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 and user plane data of the terminal, 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 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. Based on the second message, the first network node can implement forwarding of the user plane data or forwarding of the RRC message to the terminal, so as to reduce the transmission delay of the user plane data and reduce the waiting time of the terminal.

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 diagram of a method of transmission of user plane data according to an embodiment of the present application;

fig. 3 is a schematic flow chart diagram of a method for transmission of user plane data in accordance with a specific embodiment of the present application;

fig. 4 is a schematic flow chart diagram of a method of transmitting user plane data in accordance with another particular embodiment of the present application;

fig. 5 is a schematic flow chart diagram of a method of transmission of 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 block diagram of a communication device according to one 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 drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used are interchangeable under appropriate circumstances such that embodiments of the application can be practiced in sequences other than those illustrated or described herein, and the terms "first" and "second" used herein generally do not denote any order, nor do they denote any order, for example, the first object may be one or more. In addition, "and/or" in the specification and the claims means at least one of connected objects, and a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

It is noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, but may also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), 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 techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for purposes of example, and NR terminology is used in much of the description below, and these techniques are also applicableApplications other than NR system applications, e.g. 6 th generation (6)^thGeneration, 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-side device 12. Wherein, the terminal 11 may also be called as a terminal Device or a User Equipment (UE), the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a notebook Computer, a Personal Digital Assistant (PDA), a palmtop Computer, a netbook, a super-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and other terminal side devices, the Wearable Device includes: bracelets, earphones, glasses and the like. 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 (BSS), an 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 (hbo), a WLAN access Point, a WiFi node, a Transmission Receiving Point (TRP), or some other suitable terminology in the field, as long as the same technical effect is achieved, 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 following describes in detail a transmission method and a network node of user plane data provided in the embodiments of the present application through specific embodiments and application scenarios thereof 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, which may be performed by a first network node, in other words, the method may be performed by software or hardware installed in the first network node, and the method includes the following steps.

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

In this embodiment, the terminal may be in an INACTIVE state (INACTIVE) mode and initiate the small data transmission procedure, the first network node may be a network node where the terminal initiates the small data transmission procedure, and the first network node does not save 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 transitions from the CONNECTED state (CONNECTED) to the INACTIVE state (INACTIVE) upon receipt of an RRC Release message at the second network node, which 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 (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) a recovery procedure trigger cause;

2) the terminal expects to perform low-delay small-data transmission;

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

4) and the terminal subsequently transmits uplink data.

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

By this recovery procedure trigger cause, the first network node or the second network node may know why the terminal triggered the traffic data and trigger the small data transmission procedure. For example, if the trigger reason for the recovery process carried in the first message by the terminal is the transmission of the delay-sensitive small data, the first network node or the second network node may know that the user plane data carried in the first message by the terminal is from the 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 handed over from the second network node; the first network node transmits a 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 includes the user plane data mentioned in S202.

In this example, the first network node may receive uplink data of the terminal and forward the uplink data to the second network node, and the uplink data is forwarded to a User Plane Function (UPF) by the second network node; in this example, the first network node may also receive downlink data from the second network node and forward the downlink data to the terminal.

In another example, the second message is used to instruct the first network node to forward data to the second network node and to obtain, by the first network node, a user context for handover from the second network node.

In yet another example, the second message is for the first network node to forward an RRC message handed over by the second network node to the terminal. Alternatively, the RRC message may be an RRC release message, and in the case of the RRC release message, the RRC message generally indicates that the second network node is not allowed to forward user plane data.

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

1) a recovery procedure trigger cause;

2) the terminal expects to perform low-delay small-data transmission;

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

4) the terminal has uplink data transmission subsequently;

5) and time length information, wherein the time length information is used for indicating the time length for establishing the connection between the first network node and the terminal. In this way, the second network node may decide to propose to forward the downlink data and/or forward the downlink data according to the duration information, thereby ensuring that the downlink data is sent to the first network node within a time period corresponding to the duration information.

In the method for transmitting user plane data provided in the embodiment of the present application, a 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, 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 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. Based on the second message, the first network node can implement forwarding of the user plane data or forwarding of the RRC message to the terminal, so as to reduce the transmission delay of the user plane data and reduce the waiting time of the terminal.

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

1) not relocating a user context of the terminal;

2) not relocating the user context of the terminal and forwarding data;

3) and carrying out data forwarding and/or shunting.

In a first embodiment, 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 a third message; the first network node may also obtain the first indication information according to the indication domain carried in the third message; the first network node may also derive the first indication information in dependence 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 includes: 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 the uplink data forwarding and the logical channel; the uplink Data forwarding is performed according to each logical channel (per LCH), the uplink Data forwarding tunnel is established/maintained/modified/removed according to the granularity (LCH level) of the LCH, and the uplink Data forwarding tunnel forwards a Radio Link Control Protocol Data Unit (RLC PDU).

Optionally, there is a one-to-one correspondence between uplink data forwarding and Radio Link Control (RLC) bearer; the uplink Data forwarding is performed according to each logical channel (per RLC bearer), the uplink Data forwarding tunnel is established/maintained/modified/removed according to the granularity of the RLC bearer, and the uplink Data forwarding tunnel forwards a Packet Data Convergence Protocol Data Unit (PDCP PDU).

The fourth message may include at least one of:

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 (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) An upstream forwarding proposal field for proposing upstream data forwarding.

In one embodiment (hereinafter referred to as embodiment two for ease of distinction), after the first network node sends the second message in embodiment 200, the method further comprises: the first network node 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:

1) not relocating a user context of the terminal;

2) not relocating the user context of the terminal and forwarding data;

3) and carrying out data forwarding and/or shunting.

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 a 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 also derive the second indication information according to a message type of the fifth message.

In embodiment two, 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 and a Quality of Service (QoS) stream or a Protocol Data Unit (PDU) session have a one-to-one correspondence relationship.

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) an upstream forwarding proposal field for proposing an upstream data transfer.

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: and 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, and through the uplink data forwarding tunnel, the first network node may forward the user plane data carried in the first message to the second network node, and then forward the user plane data to the UPF by the second network node, thereby reducing 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 the related transmission layer information with the Xn user plane, wherein the transmission layer information is used for forwarding the uplink data.

6) One or more RLC bearers carry 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 another embodiment, 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, which may comprise an RRC release message; and the first network node sends the RRC release message to the terminal.

Optionally, after the first network node receives a seventh message from the second network node, the method further comprises: the first network node receiving a ninth message from the second network node, the ninth message indicating that the second network node proposes to perform downlink data forwarding; and the first network node sends a tenth message, wherein the tenth message is used for establishing 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 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; a downstream forwarding proposal field for proposing downstream 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 the related transmission layer information with the Xn user plane, wherein the transmission layer information is used for forwarding the downlink data.

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

Optionally, after the first network node receives a seventh message from the second network node, or after the first network node sends an 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 to indicate at least one of: releasing the user context information of the terminal; ending data forwarding and/or offloading; finishing small data transmission; allowing release of resources associated with a 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 the RRC release message carried by the twelfth message to the terminal;

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

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 releases the user context of the terminal

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

indicating successful forwarding of 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, two specific embodiments will be described below.

Example one

In this first embodiment, the second network node (or old node or anchor node) does not send UE context to the first network node (or new node), and the first network node forwards the 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 terminal (INACTIVE UE) sends a first protocol data unit (corresponding to the first message in the foregoing embodiment), where the first data unit includes a recovery identifier (resume ID) of the UE, a UE identity authentication identifier, a resume procedure trigger reason, user plane data, and the like.

Optionally, the trigger reason of 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 indicates that the resume procedure is used for small data transmission/delay-sensitive small data transmission/small data transmission of emergency service/small data transmission of high-priority service.

Optionally, the first data unit may further include an indication/code point/bitmap (e.g. 1-bit indication, for example, using 00 of the code points [00,01,10,11], for example, the bit indication of the highest bit in the bitmap), which is used to indicate whether the UE desires to perform low-latency small data transmission.

Optionally, the first data unit may further include an indication/code point/bitmap (e.g., a 1-bit indication, for example, 10 of the code points [00,01,10,11], for example, a bit indication of the second lowest bit of the bitmap), where the indication/code point/bitmap is used to indicate whether the UE predicts that downlink data is transmitted subsequently.

Optionally, the first data unit may further include an indication/code point/bitmap (e.g., a 1-bit indication, for example, using 01 in the code point [00,01,10,11], for example, the bit indication of the lowest bit in the bitmap), where the indication/code point/bitmap is used to indicate whether the UE has uplink data transmission 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 obtaining a user context handed over from a second network node;

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

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

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

Optionally, the second message may further include an indication/code point/bitmap (e.g. 1-bit indication, for example, using 00 of the code points [00,01,10,11], for example, the bit indication of the highest bit in the bitmap), where the indication/code point/bitmap is used to indicate whether the UE desires to perform low-latency small data transmission.

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

Optionally, the second message may further include an indication/code point/bitmap (e.g., a 1-bit indication, for example, using 01 in the code point [00,01,10,11], for example, a bit indication of the second lowest bit in the bitmap), where the indication/code point/bitmap is used to indicate whether the UE predicts that uplink data is transmitted 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 the duration of T319 in the first station broadcast message.

And 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 comprising at least a cause (cause) value.

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

not relocating (re-location) the UE context;

not re-locating the UE context and proposing to forward data;

the reason for forwarding and/or forking data is to tell the first network node: and establishing an uplink data forwarding tunnel for uplink data forwarding.

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

And 4, step 4: and 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 to carry out uplink data forwarding.

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

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

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;

an upstream forwarding proposal field for proposing upstream data forwarding.

And 5: and if the second network node determines that the uplink data forwarding corresponding to the at least one logical channel is allowed, the second network node responds to the first network node with a seventh message, wherein the seventh message is used for establishing an uplink data forwarding tunnel towards the second network node. Therefore, 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:

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

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

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

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

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

RRC Release message. The first network node transparently (e.g., without parsing the RRC Release message) sends the RRC Release message to the UE.

Step 6: and the second network node sends a ninth message to the first network node, wherein the ninth message is used for indicating that the second network node proposes to carry out downlink data forwarding.

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

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

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

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

a downstream forwarding proposal field for proposing downstream data forwarding.

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

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

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

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

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

And 8: the first network node sends an eleventh message to the second network node, the eleventh message indicating to the second network node: requesting to release a user context of the terminal; requesting to end data forwarding and/or offloading; requesting to end the small data transmission.

And step 9: the second network node sends a twelve message to the first network node, said for the second network node to indicate to the first network node: releasing the user context information of the terminal; ending data forwarding and/or offloading; finishing small data transmission; allowing release of resources associated with a 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: the release of resources (e.g., radio resources, control plane resources) associated with the UE (e.g., associated with the UE's corresponding identity) is allowed.

Optionally, the twelfth message comprises an RRC Release message. At this point, the first network node transparently (e.g., without parsing 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 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 a 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 successful forwarding of 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 Old node or anchor node) sends the UE context to the first network node (or 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: and 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 descriptions of step 1 and step 2 in this second embodiment can be referred to the descriptions of step 1 and step 2 in this first embodiment, and in order to avoid repetition, the descriptions will not be repeated here.

And step 3: if the second network node is able to recognize the UE context and successfully verify the UE identity and decides 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, the second indication information indicating one of:

not relocating a user context of the terminal;

not relocating the user context of the terminal and forwarding data;

and carrying out data forwarding and/or shunting.

And 4, step 4: the first network node sends a sixth message to the second network node, wherein the sixth message is used for indicating that the first network node proposes to forward the uplink data.

Optionally, the uplink data forwarding and the Qos flow or PDU session have a one-to-one correspondence (for example, 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, or removed according to the granularity of the Qos flow or PDU session, and the uplink data forwarding tunnel forwards the SDAP-SDU.

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

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

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

an upstream forwarding proposal field for proposing an upstream data transfer.

And 5: and if the second network node determines that uplink data forwarding corresponding to at least one QoS flow or PDU session is allowed, the second network node responds to the first network node with a seventh message, wherein the seventh message is used for establishing 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 transmission layer information associated with the Xn user plane, wherein the information is used for forwarding uplink data to a second network node;

in other embodiments, the method may further include step 5A: and if the second network node decides that the data forwarding corresponding to any one of the Qos flow or the 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., without parsing the RRC Release message) sends the RRC Release message to the UE.

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

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;

And 7: and if the first network node determines that the downlink data forwarding corresponding to at least one Qos flow or PDU session is allowed, the first network node responds to the second network node by a tenth message, 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 of the terminal;

one or more Qos flow or PDU session information;

transmitting transmission layer information associated with the Xn user plane, wherein the information is used for forwarding downlink data to a first network node;

And step 9: the second network node sending a twelfth message to the first network node, the instructions for the second network node to indicate to the first network node: releasing the user context information of the terminal; ending data forwarding and/or offloading; finishing small data transmission; allowing release of resources associated with a 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 releasing the saved UE context after the first network node receives the twelfth message.

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 successful forwarding of the RRC release message to the terminal;

indicating that the data transmission process was successful.

The method for transmitting 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 is to be understood that the interaction of the second network node with the first network node described from the second network node is the same as that described on the first network node side in the method shown in fig. 2, and the related description is appropriately omitted to avoid redundancy.

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, and the method can 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, wherein the second message comprises the user context identification of the terminal; the second message is for at least one of: the first network node acquires a 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.

In an 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 and user plane data of the terminal, 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 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 data to a second network node. Based on the second message, the first network node can implement forwarding of the user plane data or forwarding of the RRC message to the terminal, so as to reduce the transmission delay of the user plane data and reduce the waiting time of the terminal.

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

a recovery procedure trigger cause;

the terminal expects to perform low-delay small-data transmission;

the terminal estimates that downlink data is sent subsequently;

the terminal has uplink data transmission subsequently;

and the second network node proposes to forward downlink data and/or forward the downlink data according to the duration information.

Optionally, as an embodiment, the recovery procedure trigger cause includes one of: small data transmission; time delay sensitive small data transmission; transmitting the emergency small data; 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 sending 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:

not relocating a user context of the terminal;

not relocating the user context of the terminal and forwarding data;

and carrying out data forwarding and/or shunting.

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 to forward uplink data.

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

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

the identity of the terminal;

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

one or more pieces of RLC (radio link control) 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;

an upstream forwarding proposal field for proposing upstream data forwarding.

the second network node sends a fifth message; or

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:

not relocating a user context of the terminal;

not relocating the user context of the terminal and forwarding data;

and carrying out data forwarding and/or shunting.

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 to perform uplink data forwarding.

Optionally, as an embodiment, the uplink data forwarding has a one-to-one correspondence relationship with a QoS flow or a 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;

an upstream forwarding proposal field for proposing an upstream data transfer.

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 the related transmission layer information with the Xn user plane, wherein the transmission layer information is used for forwarding the uplink data.

Optionally, as an embodiment, in a case that the second network node does not allow data forwarding, the method further includes:

the second network node sends an eighth message, the 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 sending 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, the tenth message being used to establish a downstream 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 field 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 the related transmission layer information with the Xn user plane, wherein the transmission layer information is used for forwarding the 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 used to indicate at least one of: requesting to release a user context of the terminal; requesting to end data forwarding and/or offloading; requesting to end the small data transmission.

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

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 offloading; finishing small data transmission; allowing release of resources associated with a 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 successful forwarding of 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, and as shown in fig. 6, the 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 and user plane data of the terminal;

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 processor may, as an embodiment,

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

a recovery procedure trigger cause;

the terminal expects to perform low-delay small-data transmission;

the terminal estimates that downlink data is sent subsequently;

the terminal has uplink data transmission subsequently;

and/or

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

a recovery procedure trigger cause;

the terminal expects to perform low-delay small-data transmission;

the terminal estimates that downlink data is sent subsequently;

the terminal has uplink data transmission subsequently;

and time length information, wherein the time length information is used for indicating the time length for establishing the connection between the first network node and the terminal.

Optionally, as an embodiment, the receiving module 602 may further be 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:

not relocating a user context of the terminal;

not relocating the user context of the terminal and forwarding data;

and carrying out data forwarding and/or shunting.

Optionally, as an embodiment, the sending module 604 may further be 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 relationship with a logical channel or a 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 logical channel information corresponding to the user plane data;

an upstream forwarding proposal field for proposing upstream data forwarding.

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:

not relocating a user context of the terminal;

not relocating the user context of the terminal and forwarding data;

and carrying out data forwarding and/or shunting.

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 to forward uplink data.

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;

an upstream forwarding proposal field for proposing an upstream data transfer.

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;

and 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 to perform downlink data forwarding;

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

Alternatively, the processor may, 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 field for proposing downlink data forwarding; and/or

Optionally, as an embodiment, the sending module 604 may further be 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:

releasing resources associated with a user context of the terminal;

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

and continuing to forward uplink data, wherein 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:

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 successful forwarding of the RRC release message to the terminal;

indicating that the data transmission process was successful.

The first network node 600 according to the embodiment of the present application may refer to the flow corresponding to the method 200 of the embodiment of the present application, and each unit/module and the other operations and/or functions in the first network node 600 are respectively for implementing the corresponding flow in the method 200, and can achieve the same or equivalent technical effects, and for brevity, no repeated description is provided herein.

Fig. 7 is a schematic structural diagram of a second network node according to an embodiment of the present application, and as shown in fig. 7, the second network node 700 includes:

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

the first network node obtaining a user context handed over from the second network node;

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

a recovery procedure trigger cause;

the terminal expects to perform low-delay small-data transmission;

the terminal estimates that downlink data is sent subsequently;

the terminal has 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

Sending a third message according to the second message;

the third message includes first indication information indicating one of:

not relocating a user context of the terminal;

not relocating the user context of the terminal and forwarding data;

and carrying out data forwarding and/or shunting.

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

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

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

the identity of the terminal;

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

an upstream forwarding proposal field for proposing upstream data forwarding.

sending a fifth message; or

Sending a fifth message according to the second message;

not relocating a user context of the terminal;

not relocating the user context of the terminal and forwarding data;

and carrying out data forwarding and/or shunting.

receiving a sixth message, 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;

an upstream forwarding proposal field for proposing an upstream data transfer.

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, which is configured to send an eighth message under the condition that 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 sending a ninth message, the ninth message indicating that the second network node proposes to forward downlink data;

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

Alternatively, the processor may, as an 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: sending a twelfth message;

Optionally, as an embodiment, the second network node 700 further includes an updating 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 further be 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 successful forwarding of 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 and the other operations and/or functions in the second network node 700 are respectively for implementing the corresponding flow in the method 500 and can achieve the same or equivalent technical effects, and for brevity, no further description is provided herein.

Optionally, as shown in fig. 8, an embodiment of the present application further provides a communication device 800, which includes a processor 801, a memory 802, and a program or an instruction stored in the memory 802 and executable 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 above-mentioned embodiment of the method for transmitting user plane data, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

Specifically, the embodiment of the application further provides a network side device. As shown in fig. 9, the network device 900 includes: antenna 91, radio frequency device 92, baseband device 93. The antenna 91 is connected to a radio frequency device 92. In the uplink direction, the rf device 92 receives information via the antenna 91 and sends 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 information to the rf device 92, and the rf device 92 processes the received information and transmits the processed information through the antenna 91.

The above-mentioned frequency band processing means may be located in the baseband means 93, and the method performed by the network side device in the above embodiment may be implemented in the baseband means 93, where the baseband means 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 disposed, as shown in fig. 9, wherein one of the chips, for example, the processor 94, is connected to the memory 95 to call up the program in the memory 95 to perform the network device operation shown in the above method embodiment.

The baseband device 93 may further include a network interface 96 for exchanging information with the radio frequency device 92, for example, a Common Public Radio Interface (CPRI).

Specifically, the network side device of the embodiment of the present invention further includes: the instructions or programs stored in the memory 95 and capable of being executed on the processor 94, and the processor 94 calls the instructions or programs in the memory 95 to execute the methods executed by the modules shown in fig. 6 and 7, and achieve the same technical effects, which are not described herein in detail to avoid repetition.

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 program or the instruction implements each process of the above-mentioned embodiment of the method for transmitting user plane data, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The processor may be the 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 (RAM), a magnetic disk or an optical disk, and so on.

The 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 configured to run a program or an instruction to implement each process of the embodiment of the method for transmitting user plane data, and can achieve the same technical effect, and in order to avoid repetition, the details are not repeated here.

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

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 an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

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

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

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.

2. The method of claim 1,

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

a recovery procedure trigger cause;

the terminal expects to perform low-delay small-data transmission;

the terminal estimates that downlink data is sent subsequently;

the terminal has uplink data transmission subsequently;

and/or

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

a recovery procedure trigger cause;

the terminal expects to perform low-delay small-data transmission;

the terminal estimates that downlink data is sent subsequently;

the terminal has uplink data transmission subsequently;

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

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

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

not relocating a user context of the terminal;

not relocating the user context of the terminal and forwarding data;

and carrying out data forwarding and/or shunting.

5. The method of claim 4, wherein after the first network node receives a 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.

6. The method of claim 5, wherein the uplink data forwarding has a one-to-one correspondence with logical channels or Radio Link Control (RLC) bearers.

7. The method of claim 5, wherein the fourth message comprises at least one of:

the identity of the terminal;

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

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

an upstream forwarding proposal field for proposing upstream data forwarding.

8. The method of claim 1, wherein after the first network node sends the second message, the method further comprises:

the first network node 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:

not relocating a user context of the terminal;

not relocating the user context of the terminal and forwarding data;

and carrying out data forwarding and/or shunting.

9. The method of claim 8, wherein after the first network node receives a 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.

10. The method of claim 9, wherein the upstream data forwarding has a one-to-one correspondence with a quality of service (QoS) flow or a Protocol Data Unit (PDU) session.

11. The method of claim 9, 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;

an upstream forwarding proposal field for proposing an upstream data transfer.

12. The method according to claim 5 or 9, characterized in that the method further comprises:

and 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.

13. The method of claim 12, 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;

14. The method according to claim 5 or 9, 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;

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

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

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

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

16. The method of claim 15,

17. The method according to claim 12 or 16, characterized in that the method further comprises: the first network node transmitting an eleventh message;

18. The method according to claim 12 or 17, characterized in that the method further comprises: the first network node receiving a twelfth message from the second network node;

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

releasing resources associated with a user context of the terminal;

20. The method according to claim 18 or 19, wherein after the first network node receives a twelfth message from the second network node, the method further comprises:

releasing the user context of the terminal; and/or

Sending a thirteenth message for at least one of:

responding to the twelfth message;

indicating that the data forwarding is successful;

indicating successful forwarding of the RRC release message to the terminal;

indicating that the data transmission process was successful.

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

the second network node receives a second message from the first network node, wherein the second message comprises the 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.

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

a recovery procedure trigger cause;

the terminal expects to perform low-delay small-data transmission;

the terminal estimates that downlink data is sent subsequently;

the terminal has uplink data transmission subsequently;

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

24. 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 sending 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:

not relocating a user context of the terminal;

not relocating the user context of the terminal and forwarding data;

and carrying out data forwarding and/or shunting.

25. The method of claim 24, 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 logical channels or RLC bearers.

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

the identity of the terminal;

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

an upstream forwarding proposal field for proposing upstream data forwarding.

28. 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

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

not relocating a user context of the terminal;

not relocating the user context of the terminal and forwarding data;

and carrying out data forwarding and/or shunting.

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 upstream data forwarding has a one-to-one correspondence with quality of service (QoS) flows or Protocol Data Unit (PDU) sessions.

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;

an upstream forwarding proposal field for proposing an upstream data transfer.

32. The method of claim 25 or 29, further comprising:

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 data forwarding is not allowed by the second network node, the method further comprises:

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

36. The method of claim 35,

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

38. The method of claim 32 or 37, further comprising: the second network node sending a twelfth message;

39. The method of claim 38, wherein before the second network node sends the twelfth message, the method further comprises: and updating the air interface safety message of the terminal.

40. 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 successful forwarding of the RRC release message to the terminal;

indicating that the data transmission process was successful.

41. 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 and user plane data of the terminal;

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.

42. 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.

43. A network node comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing a method of transmission of user plane data as claimed in any one of claims 1 to 39.

44. A readable storage medium, on which a program or instructions are stored, which, when executed by the processor, implement the method of transmission of user plane data according to any one of claims 1 to 39.