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

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 present application belongs to the technical field of communication, and in particular relates to a user plane data transmission method and a network node.

Background technique

For a terminal that supports small data transmission and is in an inactive state, it usually implements small data (user plane data) transmission by initiating a radio resource control (Radio Resource Control, RRC) recovery procedure. Specifically, the terminal may multiplex the encrypted user plane data and the like into a Media Access Control Protocol Data Unit (Media Access Control Protocol Data Unit, MAC PDU) and send it to the network node. If the network node receiving the MAC PDU of the terminal does not save 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) At this time, the network node is in a waiting state, unable to determine whether to discard the user plane data or perform other actions, and the user plane data transmission delay is relatively large.

Contents of the invention

Embodiments of the present application provide a method for transmitting user plane data 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, the method comprising: a first network node receiving a first message from a terminal, where the first message includes a recovery identifier and user plane data of the terminal; the The first network node sends a second message, the second message includes the user context identifier of the terminal; the second message is used for at least one of the following: the first network node obtains the user transferred from the second network node Context: the first network node forwards the radio resource control RRC message forwarded by the second network node to the terminal; the first network node forwards data to the second network node.

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

In a third aspect, a first network node is provided, including: 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, the second message includes the user context identifier of the terminal; the second message is used for at least one of the following: the first network node obtains the user context transferred from the second network node; the first network node A network node forwards the RRC message forwarded by the second network node to the terminal; the first network node forwards the data to the second network node.

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

According to a fifth aspect, a first network node is provided. The first network node includes a processor, a memory, and a program or instruction stored in the memory and operable on the processor. The program or instruction is executed by The processor implements the method described in the first aspect when executed.

According to a sixth aspect, a second network node is provided. The second network node includes a processor, a memory, and a program or instruction stored in the memory and operable on the processor. The program or instruction is executed by The processor realizes the method as described in the second aspect when executed.

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

In an eighth aspect, a computer program product is provided, the computer program product includes a processor, a memory, and a program or instruction stored on the memory and operable on the processor, the program or instruction being executed by the When executed by the processor, the method according to the first aspect is realized, or the method according to the second aspect is realized.

A ninth aspect provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, the processor is used to run programs or instructions, and implement the method as described in the first aspect , or implement the method described in the second aspect.

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

Description of 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 flowchart of a method for transmitting user plane data according to an embodiment of the present application;

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

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

FIG. 5 is a schematic flowchart of a method for 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 ways

The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of this application.

The terms "first", "second" and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific sequence or sequence. It should be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application can be practiced in sequences other than those illustrated or described herein and that "first" and "second" distinguish objects It is usually one category, and the number of objects is not limited. For example, there may be one or more first objects. In addition, "and/or" in the description and claims means at least one of the connected objects, and the character "/" generally means that the related objects are an "or" relationship.

It is worth pointing out that the technology described in the embodiment of this application is not limited to the Long Term Evolution (Long Term Evolution, LTE)/LTE-Advanced (LTE-Advanced, LTE-A) system, and can 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 (OFDMA) , Single-carrier Frequency-Division Multiple Access (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 technologies can be used for the above-mentioned systems and radio technologies as well as other systems and radio technologies. However, the following description describes the New Radio (NR) system for example purposes, and uses NR terminology in most of the following descriptions, and these technologies can also be applied to applications other than NR system applications, such as the 6th generation (6 ^th Generation, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which the embodiment of the present application is applicable. The wireless communication system includes a terminal 11 and a network side device 12 . Wherein, the terminal 11 can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (LaptopComputer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device ( VUE), Pedestrian Terminal (PUE) and other terminal-side devices, wearable devices include: bracelets, earphones, glasses, etc. It should be noted that, the embodiment of the present application does not limit the specific type of the terminal 11 . The network side device 12 may be a base station or a core network, where a 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 Basic Service Set (BSS), Extended Service Set (ESS), Node B, Evolved Node B (eNB), Next Generation Node B (gNB), Home Node B, Home Evolved Node B, WLAN access Access point, WiFi node, Transmitting Receiving Point (Transmitting Receiving Point, TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that, in 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 user plane data transmission method and network nodes provided by the embodiments of the present application will be described in detail below through specific embodiments and application scenarios with reference to the accompanying drawings.

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

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

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

In one scenario, the terminal receives the RRC release (Release) message on the second network node to transform from the connected state (CONNECTED) to the inactive state (INACTIVE), and the second network node stores the user information of the terminal. context. Optionally, 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 includes or indicates at least one of the following:

1) The reason for triggering the recovery process;

2) The terminal expects low-latency and small data transmission;

3) The terminal estimates that there will be downlink data to be sent in the future;

4) The terminal subsequently sends uplink data.

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

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

S204: The first network node sends a second message, the second message includes the user context identifier of the terminal; the second message is used for at least one of the following: the first network node obtains the user context transferred from the second network node; the first network node Forward the 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 an example, the second message is used to instruct the first network node to forward data to the second network node. The data mentioned in this example may be uplink data and/or downlink data, and the data includes the user plane data mentioned in S202.

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

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

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

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

1) The reason for triggering the recovery process;

2) The terminal expects low-latency and small data transmission;

3) The terminal estimates that there will be downlink data to be sent in the future;

4) The terminal subsequently sends uplink data;

5) Duration information, where the duration information is used to indicate the duration for establishing a connection between the first network node and the terminal. In this way, the second network node 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 within the time period corresponding to the duration information.

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

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

In an embodiment (for ease of distinction, it will be referred to as Embodiment 1 hereinafter), after the first network node sends the second message in embodiment 200, the method further includes the following steps: the first network node receives the message from the The third message of the second network node, the third message includes first indication information; the first indication information indicates one of the following:

1) not relocating the user context of the terminal;

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

3) Perform data forwarding and/or distribution.

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

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

Optionally, after the first network node receives the third message from the second network node, the method further includes: the first network node sends a fourth message according to the first indication information, and the first network node The four messages are used to indicate 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, uplink data forwarding is performed according to each logical channel (per LCH), and uplink data forwarding tunnels are established according to LCH granularity (LCH level) /maintenance/modification/deletion, what is forwarded in the uplink data forwarding tunnel is a Radio Link Control Protocol Data Unit (Radio Link Control Protocol Data Unit, RLC PDU).

Optionally, there is a one-to-one correspondence between the uplink data forwarding and the radio link control (Radio Link Control, RLC) bearer; wherein, the uplink data forwarding is performed according to each logical channel (per RLC bearer), and the uplink data forwarding tunnel is Establishment/maintenance/modification/deletion are performed according to the granularity of the RLC bearer, and what is forwarded in the uplink data forwarding tunnel is a Packet Data Convergence Protocol Protocol Data Unit (Packet Data Convergence Protocol Protocol Data Unit, PDCP PDU).

The fourth message may include at least one of the following:

1) the identity of the terminal;

2) Information about one or more logical channels corresponding to the user plane data;

3) One or more RLC bearer information (for example, RLC bearer ID) corresponding to the user plane data; wherein, there is a one-to-one mapping relationship between the RLC bearer information and the logical channel information (for example, the mapping relationship can be As stipulated in the protocol, logical channel information 1 corresponds to RLC bearer information 1); the RLC bearer information may also be logical channel information.

4) An uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding.

In an embodiment (for ease of distinction, it will be referred to as Embodiment 2 hereinafter), after the first network node sends the second message in embodiment 200, the method further includes: the first network node receiving the message from the second message A fifth message from a network node, where the fifth message includes the user context of the terminal and second indication information, where the second indication information indicates one of the following:

1) not relocating the user context of the terminal;

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

3) Perform data forwarding and/or distribution.

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

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

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

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

The sixth message above may include at least one of the following:

1) One or more QoS flow information corresponding to the user plane data;

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

3) An uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding.

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

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

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

1) the identity of the terminal;

2) One or more logical channel information;

3) One or more QoS flow information;

4) One or more PDU session information;

5) Transport layer information associated with Xn user plane transmission, where the transport layer information is used to forward uplink data.

6) One or more RLC bearer information.

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

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

Optionally, after the first network node receives the seventh message from the second network node, the method further includes: the first network node receives a ninth message from the second network node, the The ninth message instructs the second network node to propose downlink data forwarding; 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 can also establish a downlink data forwarding tunnel towards the first network node, so that the second network node can also forward the downlink data from the UPF to the first network node, and then the first network node The node forwards to the terminal.

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

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

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

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

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

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

1) releasing resources associated with the user context of the terminal;

2) forwarding the RRC release message carried in the twelfth message to the terminal;

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

Optionally, on the basis of the foregoing 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 of the terminal the context

and / or

sending a thirteenth message, where the thirteenth message is used for at least one of the following:

responding to said twelfth message;

indicating that the first network node has released the user context of the terminal;

Indicates that the data forwarding is successful;

indicating that the RRC release message has been successfully forwarded to the terminal;

Indicates that the data transfer process was successful.

In order to describe the user plane data transmission method provided by the embodiment of the present application in detail, the following will describe in conjunction with two specific embodiments.

Embodiment one

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

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

Step 1: The terminal in the inactive state (INACTIVE UE) sends the first protocol data unit (corresponding to the first message in the previous embodiment), the first data unit includes the resume identification (resume ID) of the UE, the UE identity Verification ID, reason for triggering the resume process, user plane data, etc.

Optionally, the trigger cause of the resume process can be set as small data transmission/delay-sensitive small data transmission/emergency small data transmission/high priority small data transmission, indicating that the resume process is used for small data transmission/delay Sensitive small data transmission/small data transmission of emergency business/small data transmission of high priority business.

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

Optionally, the first data unit may also include an indication/code point/bitmap (such as a 1bit indication, such as using 10 in the code point [00,01,10,11], such as the second lowest bit in the bitmap ), the indication/codepoint/bitmap is used to indicate whether the UE predicts whether there will be downlink data to be sent in the future.

Optionally, the first data unit may also include an indication/code point/bitmap (such as a 1bit indication, such as using 01 in the code point [00,01,10,11], such as the lowest bit in the bitmap ), the indication/codepoint/bitmap is used to indicate whether the UE will send uplink data 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, and the purpose of sending the second message is to enable the first network node to send the second message to the second network node. The network node forwards the user plane data. Optionally, the second message is used for at least one of the following:

said first network node obtains a user context handed over from a second network node;

The first network node forwards the radio resource control RRC message forwarded by the second network node to the terminal;

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

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

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

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

Optionally, the second message may also include an indication/code point/bitmap (for example, a 1-bit indication, for example, using 01 in the code point [00,01,10,11], for example, the second lowest bit indication in the bitmap) , the indication/codepoint/bitmap is used to indicate whether the UE predicts whether there will be uplink data to be sent in the future.

Optionally, the second message may further include 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 the duration of a contention resolution window (contention resolution window) in the broadcast message of the first network node. Alternatively, the duration information may be the duration of T319 in the broadcast message of the first station.

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

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

Do not relocate the UE context (re-location);

Do not re-locate UE context and propose data forwarding;

The reason for performing data forwarding and/or splitting is to tell the first network node to establish an uplink data forwarding tunnel for uplink data forwarding.

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

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

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

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

The identity corresponding to the UE, (such as UE Context ID, resume ID);

One or more logical channel information (for example, logical channel ID) corresponding to the user plane data in the first protocol data unit of the UE;

An uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding.

Step 5: If the second network node decides to allow forwarding of uplink data corresponding to at least one logical channel, the second network node responds to the first network node with a seventh message, and the seventh message is used to establish uplink data towards the second network node Data forwarding tunnel. 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 include one or more of the following:

The identity corresponding to the UE, (such as UE Context ID, resume ID);

One or more logical channel information (eg, logical channel ID);

Transport layer information associated with Xn user plane transmission, where the information is used to forward uplink data to the second network node.

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

The identity corresponding to the UE, (such as UE Context ID, resume ID);

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

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

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

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

The identity corresponding to the UE, (such as UE Context ID, resume ID);

One or more logical channel information (eg, logical channel ID);

Downlink forwarding proposal field, which is used to propose downlink data forwarding.

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

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

The identity corresponding to the UE, (such as UE Context ID, resume ID);

One or more logical channel information (eg, logical channel ID);

Transport layer information associated with Xn user plane transmission, where the information is used to forward downlink data to the first network node.

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

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

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

Optionally, the twelfth message may also be used by the second network node to indicate to the first network node: to allow the release of resources associated with the UE (for example: associated with the identity identifier corresponding to the UE) (for example, radio resource , control plane resource).

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

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

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

Step 11: The first network node sends a thirteenth message, and the thirteenth message is used for at least one of the following:

responding to said twelfth message;

indicating that the first network node has released the user context of the terminal;

Indicates that the data forwarding is successful;

indicating that the RRC release message has been successfully forwarded to the terminal;

Indicates that the data transfer process was successful.

Embodiment two

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

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

Step 1: The terminal in the inactive state (INACTIVE UE) sends the first protocol data unit (corresponding to the first message in the previous embodiment), the first data unit includes the resume identification (resume ID) of the UE, the UE identity Verification ID, reason for triggering the resume process, user plane data, etc.

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

For the detailed introduction of Step 1 and Step 2 in Embodiment 2, refer to the introduction of Step 1 and Step 2 in Embodiment 1. To avoid repetition, the description is not repeated here.

Step 3: If the second network node can identify the UE context, successfully authenticates the UE identity, and decides to provide the UE context to the first network node, then the second network node responds to a fifth message, the fifth message includes at least the UE context information and second indication information, where the second indication information indicates one of the following:

not relocating the user context of the terminal;

Not relocating the user context of the terminal and performing data forwarding;

Perform data forwarding and/or splitting.

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

Optionally, there is a one-to-one correspondence between the uplink data forwarding and Qos flow or PDU session (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/deleted according to the granularity of Qos flow or PDUsession, and the uplink data forwarding tunnel The SDAP-SDU is forwarded.

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

Information about one or more PDU sessions corresponding to the user plane data in the first protocol data unit of the UE (for example, PDU session ID);

Information about one or more QoS flows corresponding to the user plane data in the first protocol data unit of the UE (for example, QoS flow ID);

An uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding.

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

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

the identity of the terminal;

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

Transport layer information associated with Xn user plane transmission, where the information is used to forward uplink data to the second network node;

In other embodiments, step 5A may also be included: if the second network node decides not to allow data forwarding corresponding to any Qosflow or PDU session, the second network node responds to the first network node with an eighth message, and the second network node Eight messages include the RRC Release message. The first network node transparently (eg, 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, where the ninth message is used to indicate that the second network node proposes to forward downlink data.

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

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

the identity of the terminal;

One or more Qos flow or PDU session information;

Downlink forwarding proposal field, which is used to propose downlink data forwarding.

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

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

the identity of the terminal;

One or more Qos flow or PDU session information;

Transport layer information associated with Xn user plane transmission, where the information is used to forward downlink data to the first network node;

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

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

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

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

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

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

Step 11: Release the saved UE context after the first network node receives the twelfth message.

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

Step 12: The first network node sends a thirteenth message, and the thirteenth message is used for at least one of the following:

responding to said twelfth message;

indicating that the first network node has released the user context of the terminal;

Indicates that the data forwarding is successful;

indicating that the RRC release message has been successfully forwarded to the terminal;

Indicates that the data transfer process was successful.

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

FIG. 5 is a schematic diagram of an implementation flow of a user plane data transmission method according to an embodiment of the present application, which 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, the second message includes the user context identifier of the terminal; the second message is used for at least one of the following: the first network node obtains the user transferred from the second network node Context: the first network node forwards the RRC message forwarded by the second network node to the terminal; the first network node forwards data to the second network node.

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

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

The reason for triggering the recovery process;

The terminal expects low-latency small data transmission;

The terminal predicts that downlink data will be sent subsequently;

The terminal subsequently sends uplink data;

Duration information, where the duration information is used to indicate a duration for establishing a connection between the first network node and the terminal, and the second network node proposes to forward downlink data and/or forward downlink data according to the duration information.

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

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

the second network node sends a third message; or

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

The third message includes first indication information, and the first indication information indicates one of the following:

not relocating the user context of the terminal;

Not relocating the user context of the terminal and performing data forwarding;

Perform data forwarding and/or splitting.

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, there is a one-to-one correspondence between the uplink data forwarding and logical channels or RLC bearers.

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

the identity of the terminal;

Information about one or more logical channels corresponding to the user plane data;

One or more RLC bearer information corresponding to the user plane data, the RLC bearer information is used for uplink data forwarding; the RLC bearer information has a one-to-one mapping relationship with the logical channel information;

An uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding.

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

the second network node sends a fifth message; or

sending, by the second network node, a fifth message according to the second message;

The fifth message includes the user context of the terminal and second indication information, where the second indication information indicates one of the following:

not relocating the user context of the terminal;

Not relocating the user context of the terminal and performing data forwarding;

Perform data forwarding and/or splitting.

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

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

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

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

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

An uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding.

Optionally, as an embodiment, the method further includes:

The second network node sends a seventh message, where the seventh message is used to establish an uplink data forwarding tunnel.

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

the identity of the terminal;

one or more logical channel information;

One or more RLC bearer information;

One or more QoS flow information;

One or more PDU session information;

Transport layer information associated with Xn user plane transmission, where the transport layer information is used to forward uplink data.

Optionally, as an embodiment, when the second network node does not allow data forwarding, the method further includes:

The second network node sends an eighth message, where the eighth message includes 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, where the ninth message instructs the second network node to propose downlink data forwarding;

The second network node receives a tenth message from the first network node, where the tenth message is used to establish a downlink data forwarding tunnel.

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

The tenth message includes at least one of the following: the identity of the terminal; one or more logical channel information; one or more RLC bearer information; one or more QoS flow information; one or more PDU session information; Transport layer information associated with Xn user plane transmission, where the transport layer information is used to forward 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 the following: request to release the user context of the terminal; request to end data forwarding and/or distribution; request to end 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 the following: release the user context information of the terminal; end data forwarding and/or offloading; end small data transmission; allow to release the user context association with the terminal H.

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

Optionally, as an embodiment, after the second network node sends the twelfth message, the method further includes: receiving a thirteenth message from the first network node, where the thirteenth message is used for at least one of the following:

responding to said twelfth message;

indicating that the first network node has released the user context of the terminal;

Indicates that the data forwarding is successful;

indicating that the RRC release message has been successfully forwarded to the terminal;

Indicates that the data transfer process was successful.

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

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

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

said first network node obtains 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 the second network node.

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

Optionally, as an example,

The first message also includes or indicates at least one of the following:

The reason for triggering the recovery process;

The terminal expects low-latency small data transmission;

The terminal predicts that downlink data will be sent subsequently;

The terminal subsequently sends uplink data;

and / or

The second message also includes or indicates at least one of the following:

The reason for triggering the recovery process;

The terminal expects low-latency small data transmission;

The terminal predicts that downlink data will be sent subsequently;

The terminal subsequently sends uplink data;

Duration information, where the duration information is used to indicate a duration for establishing a connection between the first network node and the terminal.

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

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

not relocating the user context of the terminal;

Not relocating the user context of the terminal and performing data forwarding;

Perform data forwarding and/or splitting.

Optionally, as an embodiment, the sending module 604 may also be used to:

Sending a fourth message according to the first indication information, where the fourth message is used to indicate that the first network node proposes to forward uplink data.

Optionally, as an embodiment, there is a one-to-one correspondence between the forwarding of uplink data and logical channels or radio link control (RLC) bearers.

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

the identity of the terminal;

Information about one or more logical channels corresponding to the user plane data;

One or more RLC bearer information corresponding to the user plane data, the RLC bearer information is used for uplink data forwarding; the RLC bearer information has a one-to-one mapping relationship with the logical channel information;

An uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding.

Optionally, as an embodiment, the receiving module 602 may also be used to:

Receive a fifth message from the second network node, where the fifth message includes the user context of the terminal and second indication information, where the second indication information indicates one of the following:

not relocating the user context of the terminal;

Not relocating the user context of the terminal and performing data forwarding;

Perform data forwarding and/or splitting.

Optionally, as an embodiment, the sending module 604 may also be used to:

Sending a sixth message according to the second indication information, where the sixth message is used to indicate that the first network node proposes to forward uplink data.

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

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

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

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

An uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding.

Optionally, as an embodiment, the receiving module 602 may also be used to:

Receive a seventh message from the second network node, where the seventh message is used to establish an uplink data forwarding tunnel.

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

the identity of the terminal;

one or more logical channel information;

One or more RLC bearer information;

One or more QoS flow information;

One or more PDU session information;

Transport layer information associated with Xn user plane transmission, where the transport layer information is used to forward uplink data.

Optionally, as an embodiment, the receiving module 602 may also be used to:

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.

Optionally, as an embodiment, the receiving module 602 may also be used to:

receiving a ninth message from the second network node, the ninth message instructing the second network node to propose downlink data forwarding;

The sending module 604 may also be configured to: send a tenth message, where the tenth message is used to establish a downlink data forwarding tunnel.

Optionally, as an example,

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

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

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

Wherein, the eleventh message is used to indicate at least one of the following: request to release the user context of the terminal; request to end data forwarding and/or distribution; request to end small data transmission.

Optionally, as an embodiment, the receiving module 602 may also be used to:

receiving a twelfth message from said second network node;

Wherein, the twelfth message is used to indicate at least one of the following: release the user context information of the terminal; end data forwarding and/or offloading; end small data transmission; allow to release the user context association with the terminal H.

Optionally, as an embodiment, the first network node is also used for at least one of the following:

releasing resources associated with the user context of the terminal;

Forwarding the RRC release message carried in the twelfth message to the terminal;

Continue to forward the uplink data, the uplink data is received by the first network node from the first message.

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

releasing the user context of said terminal; and/or

Send a thirteenth message through the sending module 604, where the thirteenth message is used for at least one of the following:

responding to said twelfth message;

indicating that the first network node has released the user context of the terminal;

Indicates that the data forwarding is successful;

indicating that the RRC release message has been successfully forwarded to the terminal;

Indicates that the data transfer process was successful.

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

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

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

said first network node obtains a user context handed over from said second network node;

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

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

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

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

The reason for triggering the recovery process;

The terminal expects low-latency small data transmission;

The terminal predicts that downlink data will be sent subsequently;

The terminal subsequently sends uplink data;

Duration information, where the duration information is used to indicate a duration for establishing a connection between the first network node and the terminal, and the second network node proposes to forward downlink data and/or forward downlink data according to the duration information.

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

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

send a third message; or

sending a third message according to the second message;

The third message includes first indication information, and the first indication information indicates one of the following:

not relocating the user context of the terminal;

Not relocating the user context of the terminal and performing data forwarding;

Perform data forwarding and/or splitting.

Optionally, as an embodiment, the receiving module 702 may also be used to:

A fourth message is received, where the fourth message is used to indicate that the first network node proposes to forward uplink data.

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

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

the identity of the terminal;

Information about one or more logical channels corresponding to the user plane data;

One or more RLC bearer information corresponding to the user plane data, the RLC bearer information is used for uplink data forwarding; the RLC bearer information has a one-to-one mapping relationship with the logical channel information;

An uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding.

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

send a fifth message; or

sending a fifth message according to the second message;

The fifth message includes the user context of the terminal and second indication information, where the second indication information indicates one of the following:

not relocating the user context of the terminal;

Not relocating the user context of the terminal and performing data forwarding;

Perform data forwarding and/or splitting.

Optionally, as an embodiment, the receiving module 702 may also be used to:

A sixth message is received, where the sixth message is used to indicate that the first network node proposes to forward uplink data.

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

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

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

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

An uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding.

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

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

the identity of the terminal;

one or more logical channel information;

One or more RLC bearer information;

One or more QoS flow information;

One or more PDU session information;

Transport layer information associated with Xn user plane transmission, where the transport layer information is used to forward uplink data.

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

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, where the ninth message instructs the second network node to propose Downlink data forwarding;

The receiving module 702 may also be configured to: receive a tenth message from the first network node, where the tenth message is used to establish a downlink data forwarding tunnel.

Optionally, as an example,

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

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

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

Wherein, the eleventh message is used to indicate at least one of the following: request to release the user context of the terminal; request to end data forwarding and/or distribution; request to end small data transmission.

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

Wherein, the twelfth message is used to indicate at least one of the following: release the user context information of the terminal; end data forwarding and/or offloading; end small data transmission; allow to release the user context association with the terminal H.

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

Optionally, as an embodiment, after the sending module sends the twelfth message, the receiving module 702 may also be configured to: receive a thirteenth message from the first network node, the thirteenth message Messages are used for at least one of the following:

responding to said twelfth message;

indicating that the first network node has released the user context of the terminal;

Indicates that the data forwarding is successful;

indicating that the RRC release message has been successfully forwarded to the terminal;

Indicates that the data transfer process was successful.

The second network node 700 according to the embodiment of the present application can refer to the process of the method 500 corresponding to the embodiment of the present application, and each unit/module in the second network node 700 and the above-mentioned other operations and/or functions are for implementing the method 500, and can achieve the same or equivalent technical effect, for the sake of brevity, details are not repeated here.

Optionally, as shown in FIG. 8 , this embodiment of the present application further provides a communication device 800, including a processor 801, a memory 802, and programs or instructions stored in the memory 802 and operable on the processor 801, For example, when the communication device 800 is a network node, when the program or instruction is executed by the processor 801, each process of the above-mentioned user plane data transmission method embodiment can be achieved, and the same technical effect can be achieved. To avoid repetition, it is not repeated here repeat.

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

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

Baseband device 93 for example can comprise at least one baseband board, and this baseband board is provided with a plurality of chips, as shown in Figure 9, wherein one chip is for example processor 94, is connected with memory 95, to call the program in memory 95, execute The network device operations shown in the above method embodiments.

The baseband device 93 may further include a network interface 96 for exchanging information 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 in this embodiment of the present invention further includes: instructions or programs stored in the memory 95 and operable on the processor 94, and the processor 94 calls the instructions or programs in the memory 95 to execute the instructions shown in FIGS. 6 and 7 . The methods executed by each module are shown to achieve the same technical effect. In order to avoid repetition, the details are not repeated here.

An 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 instruction is executed by a processor, each process of the above-mentioned user plane data transmission method embodiment is implemented, and The same technical effect can be achieved, so in order to avoid repetition, details will not be repeated here.

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

The embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the above user plane data transmission method The various processes of the embodiment can achieve the same technical effect, so in order to avoid repetition, details are not repeated here.

It should be understood that the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.

It should be noted that, in this document, the term "comprising", "comprising" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus comprising that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. Functions are performed, for example, the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

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

The embodiments of the present application have been described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementations. The above-mentioned specific implementations are only illustrative and not restrictive. Those of ordinary skill in the art will Under the inspiration of this application, without departing from the purpose of this application and the scope of protection of the claims, many forms can also be made, all of which belong to the protection of this application.

Claims (45)

1. A method for transmitting user plane data, characterized in that the method comprises: The first network node receives a first message from the terminal, where the first message includes the recovery identifier and user plane data of the terminal; The first network node sends a second message, where the second message includes the user context identifier of the terminal; the second message is used for at least one of the following: said first network node obtains a user context handed over from a second network node; The first network node forwards the radio resource control RRC message forwarded by the second network node to the terminal; forwarding data by the first network node to a second network node; The first network node receives a third message from the second network node, where the third message includes first indication information; the first indication information indicates one of the following: Not relocating the user context of the terminal and performing data forwarding; Perform data forwarding and/or splitting. 2. The method of claim 1, wherein, The first message also includes or indicates at least one of the following: The reason for triggering the recovery process; The terminal expects low-latency small data transmission; The terminal predicts that downlink data will be sent subsequently; The terminal subsequently sends uplink data; and / or The second message also includes or indicates at least one of the following: The reason for triggering the recovery process; The terminal expects low-latency small data transmission; The terminal predicts that downlink data will be sent subsequently; The terminal subsequently sends uplink data; Duration information, where the duration information is used to indicate a duration for establishing a connection between the first network node and the terminal. 3. The method according to claim 2, wherein the triggering cause of the restoration process includes one of the following: small data transmission; delay-sensitive small data transmission; urgent small data transmission; high priority small data transmission. 4. The method according to claim 1, wherein after the first network node receives the third message from the second network node, the method further comprises: The first network node sends a fourth message according to the first indication information, where the fourth message is used to indicate that the first network node proposes to forward uplink data. 5. The method according to claim 4, wherein there is a one-to-one correspondence between the uplink data forwarding and logical channels or radio link control (RLC) bearers. 6. The method according to claim 4, wherein the fourth message includes at least one of the following: the identity of the terminal; Information about one or more logical channels corresponding to the user plane data; One or more RLC bearer information corresponding to the user plane data, the RLC bearer information is used for uplink data forwarding, and there is a one-to-one mapping relationship between the RLC bearer information and the logical channel information; An uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding. 7. The method according to claim 1, wherein after the first network node sends the second message, the method further comprises: The first network node receives a fifth message from the second network node, where the fifth message includes the user context of the terminal and second indication information, where the second indication information indicates one of the following: not relocating the user context of the terminal; Not relocating the user context of the terminal and performing data forwarding; Perform data forwarding and/or splitting. 8. The method according to claim 7, wherein after the first network node receives the fifth message from the second network node, the method further comprises: The first network node sends a sixth message according to the second indication information, where the sixth message is used to indicate that the first network node proposes to forward uplink data. 9. The method according to claim 8, wherein there is a one-to-one correspondence between the uplink data forwarding and the QoS flow or the protocol data unit (PDU) session. 10. The method according to claim 8, wherein the sixth message includes at least one of the following: One or more QoS flow information corresponding to the user plane data; One or more PDU session information corresponding to the user plane data; An uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding. 11. according to the described method of claim 4 or 8, it is characterized in that, described method also comprises: The first network node receives a seventh message from the second network node, where the seventh message is used to establish an uplink data forwarding tunnel. 12. The method according to claim 11, wherein the seventh message includes at least one of the following: the identity of the terminal; one or more logical channel information; One or more RLC bearer information; One or more QoS flow information; One or more PDU session information; Transport layer information associated with Xn user plane transmission, where the transport layer information is used to forward uplink data. 13. The method according to claim 4 or 8, further comprising: The first network node receives 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 according to 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, where the ninth message instructs the second network node to propose downlink data forwarding; The first network node sends a tenth message, where the tenth message is used to establish a downlink data forwarding tunnel. 15. The method of claim 14, wherein, The ninth message includes at least one of the following: the identity of the terminal; one or more logical channel information; one or more RLC bearer information; one or more QoS flow information; one or more PDU session information; A downlink forwarding proposal field, where the downlink forwarding proposal field is used to propose downlink data forwarding; and/or The tenth message includes at least one of the following: the identity of the terminal; one or more logical channel information; one or more RLC bearer information; one or more QoS flow information; one or more PDU session information; Transport layer information associated with Xn user plane transmission, where the transport layer information is used to forward downlink data. 16. The method according to claim 11, further comprising: the first network node sending an eleventh message; Wherein, the eleventh message is used to indicate at least one of the following: request to release the user context of the terminal; request to end data forwarding and/or distribution; request to end small data transmission. 17. The method according to claim 15, further comprising: the first network node sending an eleventh message; Wherein, the eleventh message is used to indicate at least one of the following: request to release the user context of the terminal; request to end data forwarding and/or distribution; request to end small data transmission. 18. The method according to claim 11, further comprising: 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 the following: releasing the user context information of the terminal; ending data forwarding and/or offloading; ending small data transmission; allowing the release of resources associated with the user context of the terminal . 19. The method according to claim 16, further comprising: 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 the following: releasing the user context information of the terminal; ending data forwarding and/or offloading; ending small data transmission; allowing the release of resources associated with the user context of the terminal . 20. The method according to claim 18, further comprising at least one of the following: releasing resources associated with the user context of the terminal; Forwarding the RRC release message carried in the twelfth message to the terminal; Continue to forward the uplink data, the uplink data is received by the first network node from the first message. 21. The method according to 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 said terminal; and/or sending a thirteenth message, where the thirteenth message is used for at least one of the following: responding to said twelfth message; indicating that the first network node has released the user context of the terminal; Indicates that the data forwarding is successful; indicating that the RRC release message has been successfully forwarded to the terminal; Indicates that the data transfer process was successful. 22. A method for transmitting user plane data, characterized in that the method comprises: The second network node receives a second message from the first network node, where the second message includes a user context identifier of the terminal; the second message is used for at least one of the following: said first network node obtains a user context handed over from said second network node; forwarding, by the first network node, the RRC message forwarded by the second network node to the terminal; forwarding data by the first network node 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, and the first indication information indicates one of the following : Not relocating the user context of the terminal and performing data forwarding; Perform data forwarding and/or splitting. 23. The method according to claim 22, wherein the second message further includes or indicates at least one of the following: The reason for triggering the recovery process; The terminal expects low-latency small data transmission; The terminal predicts that downlink data will be sent subsequently; The terminal subsequently sends uplink data; Duration information, where the duration information is used to indicate a duration for establishing a connection between the first network node and the terminal, and the second network node proposes to forward downlink data and/or forward downlink data according to the duration information. 24. The method according to claim 23, wherein the triggering cause of the recovery process includes one of the following: small data transmission; delay-sensitive small data transmission; urgent small data transmission; high priority small data transmission. 25. The method according to claim 22, wherein after the second network node sends the third message, the method further comprises: The second network node receives a fourth message, where the fourth message is used to indicate that the first network node proposes to forward uplink data. 26. The method according to claim 25, wherein there is a one-to-one correspondence between the uplink data forwarding and logical channels or RLC bearers. 27. The method according to claim 25, wherein the fourth message includes at least one of the following: the identity of the terminal; Information about one or more logical channels corresponding to the user plane data; One or more RLC bearer information corresponding to the user plane data, the RLC bearer information is used for uplink data forwarding, and there is a one-to-one mapping relationship between the RLC bearer information and the logical channel information; An uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding. 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 sending, by the second network node, a fifth message according to the second message; The fifth message includes the user context of the terminal and second indication information, where the second indication information indicates one of the following: not relocating the user context of the terminal; Not relocating the user context of the terminal and performing data forwarding; Perform data forwarding and/or splitting. 29. The method according to claim 28, wherein after the second network node sends the fifth message, the method further comprises: The second network node receives a sixth message, where the sixth message is used to indicate that the first network node proposes to forward uplink data. 30. The method according to claim 29, wherein there is a one-to-one correspondence between the forwarding of the uplink data and a QoS flow or a protocol data unit (PDU) session. 31. The method according to claim 29, wherein the sixth message includes at least one of the following: One or more QoS flow information corresponding to the user plane data; One or more PDU session information corresponding to the user plane data; An uplink forwarding proposal field, where the uplink forwarding proposal field is used to propose uplink data forwarding. 32. The method according to claim 25 or 29, further comprising: The second network node sends a seventh message, where the seventh message is used to establish an uplink data forwarding tunnel. 33. The method according to claim 32, wherein the seventh message includes at least one of the following: the identity of the terminal; one or more logical channel information; One or more RLC bearer information; One or more QoS flow information; One or more PDU session information; Transport layer information associated with Xn user plane transmission, where the transport layer information is used to forward uplink data. 34. The method according to claim 25 or 29, wherein when the second network node does not allow data forwarding, the method further comprises: The second network node sends an eighth message, where the eighth message includes an RRC release message. 35. The method according to claim 32, wherein after the second network node sends the seventh message, the method further comprises: The second network node sends a ninth message, where the ninth message instructs the second network node to propose downlink data forwarding; The second network node receives a tenth message from the first network node, where the tenth message is used to establish a downlink data forwarding tunnel. 36. The method of claim 35, wherein, The ninth message includes at least one of the following: the identity of the terminal; one or more logical channel information; one or more RLC bearer information; one or more QoS flow information; one or more PDU session information; A downlink forwarding proposal field, where the downlink forwarding proposal field is used to propose downlink data forwarding; and/or The tenth message includes at least one of the following: the identity of the terminal; one or more logical channel information; one or more RLC bearer information; one or more QoS flow information; one or more PDU session information; Transport layer information associated with Xn user plane transmission, where the transport layer information is used to forward downlink data. 37. The method according to claim 32, further comprising: the second network node receiving the eleventh message from the first network node; Wherein, the eleventh message is used to indicate at least one of the following: request to release the user context of the terminal; request to end data forwarding and/or distribution; request to end small data transmission. 38. The method according to claim 32, further comprising: the second network node sending a twelfth message; Wherein, the twelfth message is used to indicate at least one of the following: releasing the user context information of the terminal; ending data forwarding and/or offloading; ending small data transmission; allowing the release of resources associated with the user context of the terminal . 39. The method according to claim 37, further comprising: the second network node sending a twelfth message; Wherein, the twelfth message is used to indicate at least one of the following: releasing the user context information of the terminal; ending data forwarding and/or offloading; ending small data transmission; allowing the release of resources associated with the user context of the terminal . 40. The method according to claim 38, further comprising: updating the air interface security message of the terminal before the second network node sends the twelfth message. 41. The method according to 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 being for at least one of: responding to said twelfth message; indicating that the first network node has released the user context of the terminal; Indicates that the data forwarding is successful; indicating that the RRC release message has been successfully forwarded to the terminal; Indicates that the data transfer process was successful. 42. 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 the user context identifier of the terminal; the second message is used for at least one of the following: said first network node obtains 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; forwarding data by the first network node 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 the following: Not relocating the user context of the terminal and performing data forwarding; Perform data forwarding and/or splitting. 43. A second network node, comprising: A receiving module, configured to receive a second message from the first network node, where the second message includes a user context identifier of the terminal; the second message is used for at least one of the following: said first network node obtains a user context handed over from said second network node; forwarding, by the first network node, the RRC message forwarded by the second network node to the terminal; forwarding data by the first network node to the second network node; A sending module, configured to send a third message; or send a third message according to the second message; the third message includes first indication information, and the first indication information indicates one of the following: Not relocating the user context of the terminal and performing data forwarding; Perform data forwarding and/or splitting. 44. A network node, characterized by comprising a processor, a memory, and a program or instruction stored in the memory and operable on the processor, and the program or instruction is implemented when executed by the processor. The method for transmitting user plane data according to any one of claims 1 to 41. 45. A readable storage medium, wherein a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the user interface according to any one of claims 1 to 41 is realized. The method of data transfer.

Images