CN114126091A

CN114126091A - Uplink data processing method, device, network equipment, terminal equipment and medium

Info

Publication number: CN114126091A
Application number: CN202010873107.2A
Authority: CN
Inventors: 孙建成
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2020-08-26
Filing date: 2020-08-26
Publication date: 2022-03-01
Also published as: WO2022042652A1

Abstract

The application provides an uplink data processing method, an uplink data processing device, a network device, a terminal device and a medium, wherein the method comprises the following steps: receiving a first message sent by terminal equipment; performing data processing on the uplink data to obtain first processed data; and sending the first processing data to the first centralized unit CU, and not executing the operation of releasing the UE context corresponding to the terminal equipment. In this application, when receiving uplink data sent by the terminal device, the first DU processes the uplink data and sends the processed uplink data to the first CU. In addition, the first DU does not execute the operation of releasing the UE context corresponding to the terminal device, and when the next uplink data processing is performed, the first DU may process the next uplink data according to the UE context without re-establishing the corresponding UE context with the first CU, so that the transmission flow of the uplink data may be simplified, and the data transmission efficiency may be improved.

Description

Uplink data processing method, device, network equipment, terminal equipment and medium

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, a network device, a terminal device, and a medium for processing uplink data.

Background

In a New Radio (NR) communication system of the fifth Generation mobile communication technology (5-Generation, 5G), in addition to states (IDLE state IDLE and Connected state Connected) of an access stratum in a Long Term Evolution (LTE) system, a third state, called Inactive state, is introduced.

When the terminal device completes the last transmission of uplink data and enters the RRC inactive state, the distribution unit DU in the network device that performs the last service on the terminal device releases the UE context corresponding to the terminal device.

However, when the terminal device in the RRC inactive state performs the next uplink data transmission, the distribution unit DU in the network device needs to reestablish the UE context corresponding to the terminal device. Therefore, the existing data transmission process is complicated and the efficiency is low.

Disclosure of Invention

The application provides an uplink data processing method, an uplink data processing device, a network device, a terminal device and a medium, which are used for solving the technical problems in the prior art.

In a first aspect, the present application provides an uplink data processing method, which is applied to a first distribution unit DU, and the method includes:

receiving a first message sent by terminal equipment (UE) in a Radio Resource Control (RRC) inactive state, wherein the first message comprises uplink data and is used for requesting RRC recovery;

performing data processing on the uplink data to obtain first processed data;

and sending the first processing data to a first centralized unit CU, and not executing the operation of releasing the UE context corresponding to the terminal equipment.

In some embodiments, the not performing the operation of releasing the UE context corresponding to the terminal device includes:

and receiving a second message sent by the first CU, and not executing the operation of releasing the UE context corresponding to the terminal equipment according to the second message.

In some embodiments, the first message further comprises an RRC recovery request for requesting RRC recovery;

after receiving the first message sent by the terminal equipment UE in the radio resource control RRC inactive state, the method further includes:

sending the RRC recovery request to the first CU.

In some embodiments, in a previous uplink data processing process, if the first DU does not perform an operation of releasing the UE context corresponding to the terminal device, the performing data processing on the uplink data to obtain first processed data includes:

and performing data processing on the uplink data according to the reserved UE context to obtain the first processed data.

In some embodiments, if the first DU does not retain the UE context corresponding to the terminal device, the performing data processing on the uplink data to obtain first processed data includes:

receiving a UE context establishment request initiated by the first CU based on the UE context corresponding to the terminal equipment, and establishing the UE context;

and performing data processing on the uplink data according to the established UE context to obtain the first processed data.

In a second aspect, the present application provides an uplink data processing method applied to a first centralized unit CU, where the method includes:

receiving first processing data sent by a first Distribution Unit (DU), wherein the first processing data is obtained by performing data processing on uplink data contained in a first message after the first DU receives the first message sent by terminal equipment (UE) in a Radio Resource Control (RRC) inactive state;

and sending a second message to the first DU, wherein the second message is used for indicating the first DU not to execute the operation of releasing the UE context corresponding to the terminal equipment.

In some embodiments, further comprising:

and receiving an RRC recovery request which is sent by the first DU and contained in the first message.

In some embodiments, further comprising:

and when a first control message is sent to the terminal equipment to indicate that the terminal equipment enters an RRC (radio resource control) inactive state, sending a second control message to the first DU, wherein the second control message is used for indicating that the first DU does not execute the operation of releasing the UE context corresponding to the terminal equipment.

In some embodiments, if the first CU retains the UE context corresponding to the terminal device, the method further includes:

and initiating a UE context establishment request to the first DU based on the UE context corresponding to the terminal device, wherein the UE context establishment request is used for indicating the first DU to establish the UE context, and performing data processing on the uplink data according to the established UE context to obtain the first processed data.

In some embodiments, further comprising:

and sending a third message to a second DU, where the third message is used to instruct the second DU to release the UE context corresponding to the terminal device, the second DU is a DU to which an operation of releasing the UE context corresponding to the terminal device has not been executed in a previous uplink data processing process, and the second DU is different from the first DU.

In some embodiments, if the first CU does not retain the UE context corresponding to the terminal device, the method further includes:

sending a UE context acquisition request to a second CU according to the RRC recovery request, wherein the second CU is an anchor CU of the terminal equipment;

receiving a UE context corresponding to the terminal equipment and sent by the second CU based on the UE context acquisition request;

and initiating a UE context establishment request to the first DU based on the UE context, wherein the UE context establishment request is used for indicating the first DU to establish the UE context, and performing data processing on the uplink data according to the established UE context to obtain the first processed data.

In some embodiments, further comprising:

and sending a fourth message to the second CU, wherein the fourth message is used for indicating the second CU to release the UE context corresponding to the terminal equipment.

In a third aspect, the present application provides an uplink data processing method, which is applied to a terminal device, and the method includes:

when the mobile terminal is in a Radio Resource Control (RRC) inactive state, if uplink data needs to be sent, generating a first message, wherein the first message comprises the uplink data;

and sending the first message to a first Distribution Unit (DU), wherein the first message is used for instructing the first DU to perform data processing on the uplink data to obtain first processing data, and sending the first processing data to a first Central Unit (CU) without executing an operation of releasing a UE context corresponding to the terminal equipment.

In a fourth aspect, the present application provides a first distribution unit, DU, of a network device, comprising a memory, a transceiver, a processor:

a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:

performing data processing on the uplink data to obtain first processed data;

after the receiving the first message sent by the terminal equipment UE in the radio resource control RRC inactive state, the operations further include:

sending the RRC recovery request to the first CU.

In a fifth aspect, the present application provides a first centralized unit CU of a network device, comprising a memory, a transceiver, a processor:

In some embodiments, the operations further comprise:

In a sixth aspect, the present application provides a network device, which includes the first distribution unit DU described above, and the first concentration unit CU described above.

In a seventh aspect, the present application provides a terminal device, including a memory, a transceiver, a processor:

when the mobile terminal is in a Radio Resource Control (RRC) inactive state, if uplink data needs to be sent, generating a first message, wherein the first message comprises the uplink data; and sending the first message to a first Distribution Unit (DU), wherein the first message is used for instructing the first DU to perform data processing on the uplink data to obtain first processing data, and sending the first processing data to a first Central Unit (CU) without executing an operation of releasing a UE context corresponding to the terminal equipment.

In an eighth aspect, the present application provides an uplink data processing apparatus, applied to a first distribution unit DU, the apparatus including:

a receiving unit, configured to receive a first message sent by a terminal device UE in an RRC inactive state, where the first message includes uplink data, and the first message is used to request RRC recovery;

the processing unit is used for carrying out data processing on the uplink data to obtain first processed data;

a sending unit configured to send the first processing data to a first central unit CU;

the processing unit is further configured to not perform an operation of releasing a UE context corresponding to the terminal device.

In a ninth aspect, the present application provides an upstream data processing apparatus, applied to a first centralized unit CU, the apparatus including:

a receiving unit, configured to receive first processing data sent by a first distribution unit DU, where the first processing data is obtained by performing data processing on uplink data included in a first message after the first DU receives the first message sent by a terminal device UE in a radio resource control RRC inactive state;

a sending unit, configured to send a second message to the first DU, where the second message is used to instruct the first DU not to execute an operation of releasing a UE context corresponding to the terminal device.

In a tenth aspect, the present application provides an uplink data processing apparatus, which is applied to a terminal device, where the apparatus includes:

a processing unit, configured to generate a first message if uplink data needs to be sent when the RRC is in an inactive state, where the first message includes the uplink data;

and a sending unit, configured to send the first message to a first distribution unit DU, where the first message is used to instruct the first DU to perform data processing on the uplink data to obtain first processed data, and send the first processed data to a first central unit CU, where an operation of releasing a UE context corresponding to the terminal device is not performed.

In an eleventh aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and the computer-executable instructions are executed by a processor to implement the uplink data processing method described above.

The application provides an uplink data processing method, an uplink data processing device, a network device, a terminal device and a medium, wherein the method comprises the following steps: receiving a first message sent by terminal equipment (UE) in a Radio Resource Control (RRC) inactive state, wherein the first message comprises uplink data and is used for requesting RRC recovery; performing data processing on the uplink data to obtain first processed data; and sending the first processing data to the first centralized unit CU, and not executing the operation of releasing the UE context corresponding to the terminal equipment. In this application, when receiving uplink data sent by a terminal device in an RRC inactive state, a first DU processes the uplink data and sends the uplink data to a first CU. In addition, the first DU does not execute the operation of releasing the UE context corresponding to the terminal device, and when performing the next uplink data processing, the first DU may process the next uplink data according to the unreleased UE context without re-establishing the corresponding UE context with the first CU, thereby simplifying the transmission flow of the uplink data and improving the data transmission efficiency.

It should be understood that what is described in the summary above is not intended to limit key or critical features of embodiments of the invention, nor is it intended to limit the scope of the invention. Other features of the present invention will become apparent from the following description.

Drawings

In order to more clearly illustrate the technical solutions in the present application or the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.

FIG. 1 is a schematic diagram of a CU-DU separation architecture;

fig. 2 is a schematic diagram of data transmission performed by a terminal device in an RRC inactive state in the prior art;

fig. 3 is a schematic diagram of an uplink data processing method according to an embodiment of the present application;

fig. 4 is another schematic diagram of an uplink data processing method according to an embodiment of the present application;

fig. 5 is another schematic diagram of an uplink data processing method according to an embodiment of the present application;

fig. 6 is a further schematic diagram of an uplink data processing method according to an embodiment of the present application;

fig. 7 is a schematic diagram of a first distribution unit provided in an embodiment of the present application;

fig. 8 is a schematic diagram of a terminal device provided in an embodiment of the present application;

fig. 9 is a schematic diagram of an uplink data processing apparatus according to an embodiment of the present application;

fig. 10 is another schematic diagram of an uplink data processing apparatus according to an embodiment of the present application;

fig. 11 is another schematic diagram of an uplink data processing apparatus according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the embodiments of the present application, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It should be understood that the term "and/or" as used herein is merely one type of association that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

The words "if", as used herein, may be interpreted as "at … …" or "at … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrases "if determined" or "if detected (a stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when detected (a stated condition or event)" or "in response to a detection (a stated condition or event)", depending on the context.

It is also noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a good or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such good or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of additional like elements in the article or system in which the element is included.

The technical scheme provided by the embodiment of the application can be suitable for various systems, particularly 5G systems. For example, the applicable System may be a Global System Of Mobile Communication (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (General Packet Radio Service, GPRS) System, a Long Term Evolution (Long Term Evolution, LTE) System, a LTE Frequency Division Duplex (Frequency Division Duplex, FDD) System, a LTE Time Division Duplex (TDD) System, a Long Term Evolution (Long Term Evolution, LTE-a) System, a Universal Mobile Telecommunications System (UMTS), a Universal Mobile telecommunications Access (UMTS), a Global System For Mobile Access (Microwave Access, Microwave Access (Microwave NR) System, a wireless network Access (wlan) System, a wireless network Access (NR) System, etc. These various systems include terminal devices and network devices. The System may further include a core network portion, such as an Evolved Packet System (EPS), a 5G System (5GS), and the like.

The terminal device referred to in the embodiments of the present application may refer to a device providing voice and/or data connectivity to a user, a handheld device having a wireless connection function, or another processing device connected to a wireless modem. In different systems, the names of the terminal devices may be different, for example, in a 5G system, the terminal device may be called a User Equipment (UE). A wireless terminal device, which may be a mobile terminal device such as a mobile telephone (or "cellular" telephone) and a computer having a mobile terminal device, for example, a portable, pocket, hand-held, computer-included, or vehicle-mounted mobile device, may communicate with one or more Core Networks (CNs) via a Radio Access Network (RAN). Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). The wireless Terminal Device may also be referred to as a system, a Subscriber Unit (Subscriber Unit), a Subscriber Station (Subscriber Station), a Mobile Station (Mobile), a Remote Station (Remote Station), an Access Point (Access Point), a Remote Terminal Device (Remote Terminal), an Access Terminal Device (Access Terminal), a User Terminal Device (User Terminal), a User Agent (User Agent), and a User Device (User Device), which are not limited in the embodiment of the present application.

The network device according to the embodiment of the present application may be a base station, and the base station may include a plurality of cells for providing services to a terminal. A base station may also be referred to as an access point, or a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminal devices, or by other names, depending on the particular application. The network device may be configured to exchange received air frames with Internet Protocol (IP) packets as a router between the wireless terminal device and the rest of the access network, which may include an Internet Protocol (IP) communication network. The network device may also coordinate attribute management for the air interface. For example, the network device according to the embodiment of the present application may be a Base Transceiver Station (BTS) in a Global System For Mobile Communications (GSM) or Code Division Multiple Access (CDMA), a network device (Node B) in a Wideband Code Division Multiple Access (WCDMA), a Evolved network device (Gnb) in a Long Term Evolution (Long Term Evolution, LTE) System, a 5G Base Station (Gnb) in a 5G network architecture (Next Generation System), a Home Evolved Node B (Home Evolved Node B, Henb), a Relay Node (Relay Node), a Home Base Station (Femto), a Pico Base Station (Pico), and the like, which are not limited in the embodiments of the present application. In some network architectures, network devices may include Centralized Unit (CU) nodes and Distributed Unit (DU) nodes, which may also be geographically separated.

The network device related to the embodiment of the present application may specifically adopt a CU-DU separation architecture. Fig. 1 is a schematic diagram of a CU-DU separation architecture, and as shown in fig. 1, a CU and a DU may be physically separated or deployed together. A plurality of DUs can share one CU. One DU may also connect multiple CUs. The CU and DU may be connected via an interface, such as an F1 interface. CUs and DUs may be partitioned according to protocol layers of the wireless network. For example, the functions of the RRC (Radio Resource Control), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) layers are set in the CU, and the functions of the Radio Link Control (RLC), Media Access Control (MAC), Physical (PHY), and the like are set in the DU. It is to be understood that the division of CU and DU processing functions according to such protocol layers is merely an example, and may be performed in other manners. For example, a CU or DU may be partitioned to have more protocol layer functionality. For example, a CU or DU may also be divided into partial processing functions with protocol layers. In one design, some of the functions of the RLC layer and the functions of protocol layers above the RLC layer are provided in the CUs, and the remaining functions of the RLC layer and the functions of protocol layers below the RLC layer are provided in the DUs. In another design, the functions of a CU or DU may also be divided according to traffic type or other system requirements. For example, dividing by time delay, setting the function that processing time needs to meet the time delay requirement in DU, and setting the function that does not need to meet the time delay requirement in CU. In another design, a CU may also have one or more functions of the core network. One or more CUs may be centrally located or separately located. For example, the CUs may be located on the network side to facilitate centralized management. The DU may have multiple rf functions, or may have a remote rf function.

Fig. 2 is a schematic diagram of data transmission performed by a terminal device in an RRC inactive state in the prior art, as shown in fig. 2, the terminal device first sends an RRC connection recovery request carrying a UE context identifier (e.g., I-RNTI) to a DU, the DU sends an access request carrying the UE context identifier to a CU, the CU establishes a UE context with the DU based on the access request, and thus the terminal device recovers to an RRC connected state, and finally, the terminal device, the DU, and the CU perform uplink and downlink data transmission. Wherein, the uplink data transmission process between the DU and the CU comprises the following steps: the DU performs data processing on the uplink data and sends the processed data to the CU.

In the prior art, before a CU and a DU establish a UE context, the DU does not retain the UE context corresponding to the terminal device, so that the DU cannot process uplink data. After the CU establishes the UE context with the DU, the DU may complete processing of uplink data according to the established UE context. Therefore, in the prior art, the establishment of the UE context between the CU and the DU becomes a key in the uplink data transmission process.

However, for a small data transmission scenario, for example, an internet of things data transmission scenario, the amount and specification of uplink data are small, and if the UE contexts of the CU and the DU need to be established first for transmitting the uplink data each time, the data transmission process is complicated, and the efficiency is low.

For example, for a device such as an intelligent water meter, the corresponding upstream data only includes water consumption data, device health status data, and the like, the upstream data can be transmitted by one or a small number of upstream data packets, and the device does not have the desired downstream data. In this case, the existing uplink data transmission method has the problems of complicated process and low efficiency. In addition, when the number of devices is large, if operations such as anchor point transfer or path switching are required, a large amount of signaling overhead is also caused, thereby causing waste of network resources.

The embodiment of the application provides an uplink data processing method, an uplink data processing device, network equipment, terminal equipment and a medium, which are used for solving the technical problems in the prior art.

The method and the device are based on the same application concept, and because the principles of solving the problems of the method and the device are similar, the implementation of the device and the method can be mutually referred, and repeated parts are not repeated.

Fig. 3 is a schematic diagram of an uplink data processing method provided in an embodiment of the present application, and as shown in fig. 3, the uplink data processing method specifically includes the following steps:

s1, when in the radio resource control RRC inactive state, the terminal device sends a first message to the first distribution unit DU.

The first message comprises uplink data, and the first message is used for requesting RRC recovery. The first DU is a service DU corresponding to the terminal device, and the first CU corresponding to the first DU is a service CU corresponding to the terminal device.

S2, the first DU receives a first message sent by the UE in the RRC inactive state, and performs data processing on the uplink data to obtain first processed data.

Specifically, the first DU performs L2 (layer 2) processing on the uplink data, that is, data processing in the MAC and RLC layers, thereby obtaining first processed data.

S3, the first DU sends the first processed data to the first central unit CU, and does not perform the operation of releasing the UE context corresponding to the terminal device.

Specifically, after receiving the first processing data, the first CU may perform data processing on the first processing data, including PDCP and SDAP processing, to obtain second processing data, and send the second processing data to the core network device, thereby completing uplink data transmission of the terminal device.

In this embodiment, the first DU does not perform an operation of releasing the UE context corresponding to the terminal device, and specifically includes the following two cases:

the first condition is as follows:

after finishing the uplink data processing, the first DU is set in advance in a mode of program setting and the like, and does not release the UE context by default; and when receiving a UE context release indication message sent by the first CU, releasing the UE context corresponding to the terminal equipment.

Case two:

after the uplink data processing is finished, the first DU defaults to release the UE context, and after the first CU sends an indication message for not releasing the UE context to the first DU, the first DU does not release the UE context according to the indication message.

For convenience of understanding, the embodiments of the present application take the case two as an example to explain the technical solutions of the present application, and it should be understood that the technical solutions of the present application are not limited to the case two, and the technical solutions of the embodiments of the present application can be correspondingly changed to be applied to the case one.

Referring to fig. 3, when the first DU does not perform the operation of releasing the UE context corresponding to the terminal device, specifically, in case two, the method further includes:

s4, the first CU sends a second message to the first DU, where the second message is used to instruct the first DU not to execute an operation of releasing the UE context corresponding to the terminal device.

Correspondingly, the first DU receives a second message sent by the first CU, and does not perform an operation of releasing the UE context corresponding to the terminal device according to the second message, so that the UE context corresponding to the terminal device is retained in the first DU. When the next uplink data processing is performed, the first DU may directly perform data processing on the uplink data according to the reserved UE context, so as to obtain first processed data.

In this embodiment, when receiving uplink data sent by the terminal device in the RRC inactive state, the first DU processes the uplink data and sends the processed uplink data to the first CU. In addition, the first DU does not execute the operation of releasing the UE context corresponding to the terminal device, and when performing the next uplink data processing, the first DU may process the next uplink data according to the unreleased UE context without re-establishing the corresponding UE context with the first CU, thereby simplifying the transmission flow of the uplink data and improving the data transmission efficiency.

It should be noted that the uplink data processing method provided in this embodiment of the present application may be applied to an application scenario in which the terminal device performs small data transmission with the serving network device currently corresponding to the terminal device, where the application scenario may be specifically divided into multiple cases, such as whether the serving CU currently corresponding to the terminal device stores a UE context corresponding to the terminal device, and whether the serving DU currently corresponding to the terminal device stores a UE context corresponding to the terminal device. The following explains the uplink data processing method in different cases.

In some embodiments, when a service DU corresponding to the terminal device currently stores a UE context corresponding to the terminal device, a flow of the uplink data processing method is explained. This embodiment specifically corresponds to a case where the first DU does not perform an operation of releasing the UE context corresponding to the terminal device in the previous uplink data processing process.

Fig. 4 is a schematic diagram of an uplink data processing method provided in an embodiment of the present application, and as shown in fig. 4, the uplink data processing method specifically includes the following steps:

s100a, when sending the first control message to the terminal device to instruct the terminal device to enter a radio resource control RRC inactive state, the first CU sends a second control message to the first DU, where the second control message is used to instruct the first DU not to execute an operation of releasing a UE context corresponding to the terminal device.

The first CU is a CU in the service network device currently corresponding to the terminal device, that is, the first CU is a service CU, and the first DU is a DU in the service network device currently corresponding to the terminal device, that is, the first DU is a service DU.

In addition, the UE context specifically includes configuration Of an SRB (signaling Radio Bearer) and a DRB (Data Radio Bearer) before the terminal device enters the RRC inactive state, where the DRB configuration includes Qos (Quality Of Service) information Of the DRB, a TNL (transport network layer) address Of an UL user plane, a mapping relationship between the DRB and Qos Flow, and the like.

S100b, the terminal device enters into an RRC inactive state according to the first control message.

S100c, the first DU does not perform an operation of releasing the UE context corresponding to the terminal device according to the second control message.

S101, when the terminal equipment in the RRC inactive state needs to send uplink data, sending a first message to a corresponding first Distribution Unit (DU), wherein the first message comprises the uplink data and an RRC recovery request.

The uplink Data (UL Data) may be specifically uplink Small Data (UL Small Data). The RRC recovery request (rrcoresumerequest) includes an identity corresponding to the terminal device.

The difference between this embodiment and the prior art is that the first message sent by the terminal device to the first DU includes uplink data to be sent, in addition to the RRC recovery request.

Optionally, the first message further includes auxiliary information, specifically, for example, whether there is any Subsequent uplink Data (Subsequent UL Data) that needs to be transmitted, a Data amount of the Subsequent uplink Data, whether there is promising downlink Data, and the like.

S102, after receiving a first message sent by the terminal device, the first DU sends an RRC recovery request to the first CU.

The first DU sends an RRC recovery request to the first CU through the F1 interface, where the RRC recovery request sent by the first DU to the first CU includes a Cause Value (Cause Value) as small data. Optionally, the auxiliary information in the first message may also be included.

S103, the first DU carries out data processing on the uplink data to obtain first processing data.

Specifically, in the previous uplink data processing process, the first DU does not perform an operation of releasing the UE context corresponding to the terminal device, so that the UE context corresponding to the terminal device is retained in the first DU, and thus the first DU performs L2 (layer 2) processing on the uplink data according to the retained UE context of the terminal device, that is, data processing in the MAC and RLC layers, thereby obtaining the first processed data.

S104, the first DU sends the first processing data to the first CU.

S105, the first CU receives the first processed data sent by the first DU, and performs data sending processing.

It can be understood that when subsequent uplink data exists, the terminal device sends the subsequent uplink data to the first DU, the first DU processes the subsequent uplink data according to the reserved UE context, and sends the processed uplink data to the first CU, and the first CU processes the processed uplink data and sends the processing result to the core network device.

S106, the first CU determines the RRC state of the terminal equipment according to the auxiliary information.

Specifically, if the first CU determines that no subsequent uplink data exists currently and the terminal device does not have the expected downlink data according to the auxiliary information, the first CU determines that the RRC state of the terminal device is the RRC inactive state, and at this time, the first CU sends a corresponding message to instruct the terminal device to maintain the RRC inactive state.

S107, the first CU sends a second message to the first DU, wherein the second message is used for indicating that the first DU does not execute the operation of releasing the UE context corresponding to the terminal equipment.

S108, after receiving the second message sent by the first CU, the first DU does not perform an operation of releasing the UE context corresponding to the terminal device, so that when performing next uplink data transmission, the first DU may perform data processing according to the reserved UE context without establishing the UE context with the first CU.

In this embodiment, when receiving uplink data sent by a terminal device in an RRC inactive state, a first DU processes the uplink data according to a reserved UE context and sends the processed data to a first CU, where the process does not need to establish the UE context with the first CU. Then, the first CU sends a second message indicating that the UE context corresponding to the terminal is reserved to the first DU, so that the first DU continues to reserve the UE context corresponding to the terminal after completing the processing of the uplink data, and when performing the next uplink data processing, the first DU can process the uplink data without establishing a corresponding UE context with the first CU, thereby simplifying the transmission flow of the uplink data and improving the data transmission efficiency.

In some embodiments, when the service DU corresponding to the terminal device currently does not store the UE context corresponding to the terminal device, and the service CU stores the UE context corresponding to the terminal device, a flow of the uplink data processing method is explained. This embodiment specifically corresponds to a case where the first DU does not reserve a UE context corresponding to the terminal device, and the first CU reserves a UE context corresponding to the terminal device.

Fig. 5 is a schematic diagram of an uplink data processing method provided in an embodiment of the present application, and as shown in fig. 5, the uplink data processing method specifically includes the following steps:

s200a, when sending the first control message to the terminal device to instruct the terminal device to enter the RRC inactive state, the first CU sends a second control message to the second DU, where the second control message is used to instruct the second DU not to execute an operation of releasing a UE context corresponding to the terminal device.

The first CU is a CU in the serving network device currently corresponding to the terminal device, that is, the first CU is a serving CU, the second DU is a DU in the serving network device currently corresponding to the terminal device, the serving network device further includes a first DU, the first DU is a serving DU, the second DU is a DU in which an operation of releasing a UE context corresponding to the terminal device is not performed in a previous uplink data processing process, and the second DU is different from the first DU.

S200b, the terminal device enters into RRC non-active state according to the first control message.

S200c, the second DU does not execute the operation of releasing the UE context corresponding to the terminal device according to the second control message.

S201, when a terminal device in an RRC inactive state needs to send uplink data, sending a first message to a corresponding first DU, where the first message includes the uplink data and an RRC recovery request.

The uplink data may specifically be uplink small data. The RRC recovery request comprises an identity corresponding to the terminal equipment.

Optionally, the first message further includes auxiliary information, specifically, for example, whether there is any subsequent uplink data that needs to be sent, a data size of the subsequent uplink data, whether there is promising downlink data, and the like.

S202, after receiving the first message sent by the terminal device, the first DU sends an RRC recovery request to the first CU.

S203, the first CU initiates a UE context establishment request to the first DU based on the reserved UE context.

S204, the first DU receives a UE context establishment request initiated by the first CU based on the saved UE context, and establishes the UE context.

S205, the first DU carries out data processing on the uplink data according to the established UE context to obtain first processed data.

Specifically, the first DU performs L2 (layer 2) processing on the uplink data according to the established UE context, that is, data processing in the MAC and RLC layers, thereby obtaining first processed data.

S206, the first DU sends the first processing data to the first CU.

S207, the first CU receives the first processed data sent by the first DU, and performs data transmission processing.

S208, the first CU determines the RRC state of the terminal equipment according to the auxiliary information.

S209, when the first CU determines that the RRC state of the terminal device is the RRC inactive state, the first CU sends a second message to the first DU, where the second message is used to instruct the first DU not to execute an operation of releasing the UE context corresponding to the terminal device.

S210, after receiving the second message sent by the first CU, the first DU does not perform an operation of releasing the UE context corresponding to the terminal device, so that when performing next uplink data transmission, the first DU may perform data processing according to the reserved UE context without establishing the UE context with the first CU.

S211, optionally, the first CU sends a third message to a second DU, where a UE context corresponding to the terminal device is reserved, where the third message is used to instruct the second DU to release the UE context corresponding to the terminal device, and the second DU is different from the first DU.

S212, the second DU releases the UE context of the terminal equipment according to the third message, so as to avoid waste of network resources.

In this embodiment, when receiving uplink data sent by a terminal device in an RRC inactive state, a first DU sends an RRC recovery request to a first CU in which a UE context is stored, so as to establish the UE context, so that the uplink data can be processed according to the established UE context. In addition, the first CU sends the second message to the first DU, so that, after the first DU completes processing of the uplink data, the first DU does not perform an operation of releasing the UE context corresponding to the terminal device to reserve the UE context corresponding to the terminal device, and thus, when next uplink data processing is performed, the first DU can process the uplink data without establishing a corresponding UE context with the first CU, thereby simplifying a transmission flow of the uplink data and improving data transmission efficiency.

In some embodiments, when neither the service DU nor the service CU currently corresponding to the terminal device stores the UE context corresponding to the terminal device, a flow of the uplink data processing method is explained.

Fig. 6 is a schematic diagram of an uplink data processing method provided in an embodiment of the present application, and as shown in fig. 6, the uplink data processing method specifically includes the following steps:

s301, when a terminal device in an RRC inactive state needs to send uplink data, sending a first message to a corresponding first distribution unit DU, where the first message includes the uplink data and an RRC recovery request. Optionally, the first message further includes auxiliary information.

The first DU is a DU in a service network device currently corresponding to the terminal device, that is, the first DU is a service DU, and the service network device further includes a first CU, which is a service DU. Neither the first CU nor the first DU stores the UE context corresponding to the terminal device.

S302, after receiving a first message sent by the terminal device, the first DU sends an RRC recovery request to the first CU.

S303, the first CU sends a UE context acquisition request to the second CU according to the RRC recovery request.

The second CU is an anchor CU of the terminal device, that is, the second CU stores a UE context corresponding to the terminal device.

S304, the second CU sends the UE context corresponding to the terminal device to the first CU based on the UE context obtaining request.

S305, the first CU initiates a UE context establishment request to the first DU based on the received and obtained UE context.

S306, the first DU receives a UE context establishment request initiated by the first CU based on the received and obtained UE context, and establishes the UE context.

S307, the first DU carries out data processing on the uplink data according to the established UE context to obtain first processed data.

S308, the first DU sends the first processing data to the first CU.

S309, the first CU receives the first processed data sent by the first DU, and performs data transmission processing.

S310, the first CU determines the RRC state of the terminal equipment according to the auxiliary information.

S311, when the first CU determines that the RRC state of the terminal device is the RRC inactive state, the first CU sends a second message to the first DU, wherein the second message is used for indicating that the first DU does not execute the operation of releasing the UE context corresponding to the terminal device.

S312, after receiving the second message sent by the first CU, the first DU does not perform an operation of releasing the UE context corresponding to the terminal device, so that when performing next uplink data transmission, the first DU may perform data processing according to the reserved UE context without establishing the UE context with the first CU.

S313, optionally, the first CU sends a fourth message to the second CU on which the UE context corresponding to the terminal device is reserved, where the fourth message is used to instruct the second CU to release the UE context corresponding to the terminal device.

S314, the second CU releases the UE context of the terminal equipment according to the fourth message, so that waste of network resources is avoided.

The embodiment provides an uplink data processing method, where a first DU sends an RRC recovery request to a first CU when receiving uplink data sent by a terminal device in an RRC inactive state, and the first CU acquires a UE context corresponding to the terminal device from a second CU storing the UE context based on the RRC recovery request, and then establishes the UE context, so that the first DU can process the uplink data according to the established UE context. In addition, the first CU sends a second message indicating that the UE context corresponding to the terminal is reserved to the first DU, so that the first DU does not perform an operation of releasing the UE context corresponding to the terminal device after the uplink data processing is completed, that is, the UE context corresponding to the terminal is reserved, and thus when the next uplink data processing is performed, the first DU can process the uplink data without establishing a corresponding UE context with the first CU, thereby simplifying a transmission flow of the uplink data and improving data transmission efficiency.

In some embodiments, a first distribution unit DU of a network device is provided, and fig. 7 is a schematic diagram of the first distribution unit, and as shown in fig. 7, the first distribution unit 600 includes a memory 610, a transceiver 620, and a processor 630.

The memory 610 is used for storing computer programs. A transceiver 620 for transceiving data under the control of the processor 630. A processor 630 for reading the computer program in the memory 610 and performing the following operations: receiving a first message sent by terminal equipment (UE) in a Radio Resource Control (RRC) inactive state, wherein the first message comprises uplink data and is used for requesting RRC recovery; performing data processing on the uplink data to obtain first processed data; and sending the first processing data to a first centralized unit CU, and not executing the operation of releasing the UE context corresponding to the terminal equipment.

In FIG. 7, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 630, and various circuits of memory, represented by memory 610, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 620 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium including wireless channels, wired channels, fiber optic cables, and the like. The processor 630 is responsible for managing the bus architecture and general processing, and the memory 610 may store data used by the processor 630 in performing operations.

The processor 630 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD), and may also have a multi-core architecture.

after receiving a first message sent by a terminal equipment UE in a radio resource control, RRC, inactive state, the operations further include:

an RRC recovery request is sent to the first CU.

In some embodiments, in the previous uplink data processing process, if the first DU does not perform an operation of releasing a UE context corresponding to the terminal device, performing data processing on the uplink data to obtain first processed data, including:

and performing data processing on the uplink data according to the reserved UE context to obtain first processed data.

In some embodiments, if the first DU does not retain the UE context corresponding to the terminal device, performing data processing on the uplink data to obtain first processed data, including:

receiving a UE context establishment request initiated by a first CU based on a UE context corresponding to the terminal equipment, and establishing the UE context;

and performing data processing on the uplink data according to the established UE context to obtain first processed data.

In some embodiments, a first centralized unit CU of a network device is provided, comprising a memory, a transceiver, a processor, wherein the memory is adapted to store a computer program. And a transceiver for transceiving data under the control of the processor. A processor for reading the computer program in the memory and performing the following operations: receiving first processing data sent by a first Distribution Unit (DU), wherein the first processing data is obtained by performing data processing on uplink data contained in a first message after the first DU receives the first message sent by terminal equipment (UE) in a Radio Resource Control (RRC) inactive state; and sending a second message to the first DU, wherein the second message is used for indicating the first DU not to execute the operation of releasing the UE context corresponding to the terminal equipment.

Regarding the structure of the first concentration unit CU, reference may be made to the structural definition of the first distribution unit DU in fig. 7, which is not described herein again.

In some embodiments, the operations further comprise:

and when sending a first control message to the terminal device to indicate that the terminal device enters an RRC (radio resource control) inactive state, sending a second control message to the first DU, wherein the second control message is used for indicating that the first DU does not execute the operation of releasing the UE context corresponding to the terminal device.

In some embodiments, if the first CU retains a UE context corresponding to the terminal device, the method further includes:

and initiating a UE context establishment request to the first DU based on the UE context corresponding to the terminal equipment, wherein the UE context establishment request is used for indicating the first DU to establish the UE context, and performing data processing on uplink data according to the established UE context to obtain first processing data.

In some embodiments, the operations further comprise:

and sending a third message to a second DU, where the third message is used to instruct the second DU to release the UE context corresponding to the terminal device, the second DU is a DU to which an operation of releasing the UE context corresponding to the terminal device has not been executed in the previous uplink data processing process, and the second DU is different from the first DU.

receiving a UE context corresponding to the terminal equipment sent by a second CU based on the UE context acquisition request;

and initiating a UE context establishment request to the first DU based on the UE context, wherein the UE context establishment request is used for indicating the first DU to establish the UE context, and performing data processing on uplink data according to the established UE context to obtain first processing data.

In some embodiments, the operations further comprise:

In some embodiments, a network device is provided, comprising the first distribution unit DU described above, and the first concentration unit CU described above.

The network device may specifically adopt a CU-DU separation architecture, and for the structure of the network device, reference may be made to fig. 1 and corresponding explanations, which are not described herein again.

In some embodiments, a terminal device is provided, fig. 8 is a schematic diagram of a terminal device, and as shown in fig. 8, the terminal device 700 includes a memory 710, a transceiver 720, and a processor 730. Wherein the memory is used for storing the computer program. And a transceiver for transceiving data under the control of the processor. A processor for reading the computer program in the memory and performing the following operations: when the mobile terminal is in a Radio Resource Control (RRC) inactive state, if uplink data needs to be sent, generating a first message, wherein the first message comprises the uplink data; and sending the first message to a first Distribution Unit (DU), wherein the first message is used for instructing the first DU to perform data processing on the uplink data to obtain first processing data, and sending the first processing data to a first Central Unit (CU) without executing an operation of releasing a UE context corresponding to the terminal equipment.

Optionally, referring to fig. 8, the terminal device further comprises a user interface 740.

In FIG. 8, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented in particular by processor 730, and various circuits of memory, represented by memory 710, linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 720 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over transmission media including wireless channels, wired channels, fiber optic cables, and the like. The user interface 740 may also be an interface capable of interfacing with a desired device for different user devices, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, etc.

The processor 730 is responsible for managing the bus architecture and general processing, and the memory 710 may store data used by the processor 730 in performing operations.

Optionally, the processor 730 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi-core architecture.

The processor is used for executing any method provided by the embodiment of the application according to the obtained executable instructions by calling the computer program stored in the memory. The processor and memory may also be physically separated.

It should be noted that, the apparatus provided in the embodiment of the present invention can implement all the method steps implemented by the method embodiment and achieve the same technical effect, and detailed descriptions of the same parts and beneficial effects as the method embodiment in this embodiment are omitted here.

In some embodiments, an uplink data processing apparatus is provided and applied to the first distribution unit DU.

Fig. 9 is a schematic diagram of an uplink data processing apparatus in an embodiment of the present application, and as shown in fig. 9, the uplink data processing apparatus 800 includes:

a receiving unit 810, configured to receive a first message sent by a terminal device UE in an RRC inactive state, where the first message includes uplink data, and the first message is used to request RRC recovery.

The processing unit 820 is configured to perform data processing on the uplink data to obtain first processed data.

A sending unit 830 for sending the first processed data to the first centralized unit CU.

The processing unit 820 is further configured to not perform an operation of releasing a UE context corresponding to the terminal device.

In some embodiments, the receiving unit 810 is further configured to: and receiving a second message sent by the first CU.

In some embodiments, processing unit 820 is further configured to: and according to the second message, not executing the operation of releasing the UE context corresponding to the terminal equipment.

In some embodiments, the sending unit 830 is further configured to: an RRC recovery request is sent to the first CU.

In some embodiments, processing unit 820 is further configured to: and performing data processing on the uplink data according to the reserved UE context to obtain first processed data.

In some embodiments, the receiving unit 810 is further configured to: and receiving a UE context establishment request initiated by the first CU based on the UE context corresponding to the terminal equipment, and establishing the UE context.

In some embodiments, processing unit 820 is further configured to: and performing data processing on the uplink data according to the established UE context to obtain first processed data.

In some embodiments, an upstream data processing apparatus is provided, which is applied to the first centralized unit CU.

Fig. 10 is a schematic diagram of an upstream data processing apparatus in an embodiment of the present application, and as shown in fig. 10, the upstream data processing apparatus 900 includes:

a receiving unit 910, configured to receive first processing data sent by a first distribution unit DU, where the first processing data is obtained by performing data processing on uplink data included in a first message after the first DU receives the first message sent by a terminal device UE in a radio resource control RRC inactive state.

A sending unit 920, configured to send a second message to the first DU, where the second message is used to instruct the first DU not to execute an operation of releasing the UE context corresponding to the terminal device.

In some embodiments, the receiving unit 910 is further configured to: and receiving an RRC recovery request which is sent by the first DU and contained in the first message.

In some embodiments, the sending unit 920 is further configured to: when a first control message is sent to the terminal equipment to indicate the terminal equipment to enter an RRC (radio resource control) inactive state, a second control message is sent to the first DU, and the second control message is used for indicating the first DU not to execute the operation of releasing the UE context corresponding to the terminal equipment

In some embodiments, the sending unit 920 is further configured to: and initiating a UE context establishment request to the first DU based on the UE context corresponding to the terminal equipment, wherein the UE context establishment request is used for indicating the first DU to establish the UE context, and performing data processing on uplink data according to the established UE context to obtain first processing data.

In some embodiments, the sending unit 920 is further configured to: and sending a third message to a second DU, where the third message is used to instruct the second DU to release the UE context corresponding to the terminal device, the second DU is a DU to which an operation of releasing the UE context corresponding to the terminal device has not been executed in the previous uplink data processing process, and the second DU is different from the first DU.

In some embodiments, the sending unit 920 is further configured to: and sending a UE context acquisition request to a second CU according to the RRC recovery request, wherein the second CU is an anchor CU of the terminal equipment.

In some embodiments, the receiving unit 910 is further configured to: and receiving the UE context corresponding to the terminal equipment sent by the second CU based on the UE context acquisition request.

In some embodiments, the sending unit 920 is further configured to: and initiating a UE context establishment request to the first DU based on the UE context, wherein the UE context establishment request is used for indicating the first DU to establish the UE context, and performing data processing on uplink data according to the established UE context to obtain first processing data.

In some embodiments, referring to fig. 10, the uplink data processing apparatus 900 includes: the processing unit 930 is configured to perform data processing, including PDCP and SDAP processing, on the first processed data after receiving the first processed data, so as to obtain second processed data.

In some embodiments, the sending unit 920 is further configured to: and sending a fourth message to the second CU, wherein the fourth message is used for indicating the second CU to release the UE context corresponding to the terminal equipment.

In some embodiments, an uplink data processing apparatus is provided and applied to a terminal device.

Fig. 11 is a schematic diagram of an uplink data processing apparatus in an embodiment of the present application, and as shown in fig. 11, the uplink data processing apparatus 1000 includes:

a processing unit 1010, configured to generate a first message if uplink data needs to be sent when the RRC is in an inactive state, where the first message includes the uplink data;

a sending unit 1020, configured to send a first message to the first distribution unit DU, where the first message is used to instruct the first DU to perform data processing on uplink data to obtain first processed data, and send the first processed data to the first centralized unit CU, and the operation of releasing the UE context corresponding to the terminal device is not performed.

It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functioning unit and sold or used as a stand-alone product, may be stored in a processor readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method of the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

In some embodiments, a computer-readable storage medium is provided, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, the computer-executable instructions are used to implement the steps of the uplink data processing method in the embodiments of the present application.

The processor-readable storage medium can be any available medium or data storage device that can be accessed by a processor, including but not limited to magnetic memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND FLASH), Solid State Disks (SSDs)), etc.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. An uplink data processing method applied to a first Distribution Unit (DU) includes:

performing data processing on the uplink data to obtain first processed data;

2. The method according to claim 1, wherein the not performing the operation of releasing the UE context corresponding to the terminal device includes:

3. The method according to claim 1 or 2, wherein the first message further comprises an RRC recovery request for requesting RRC recovery;

sending the RRC recovery request to the first CU.

4. The method according to claim 1 or 2, wherein in a previous uplink data processing procedure, if the first DU does not perform an operation of releasing the UE context corresponding to the terminal device, the performing data processing on the uplink data to obtain first processed data includes:

5. The method according to claim 1 or 2, wherein if the first DU does not retain the UE context corresponding to the terminal device, the performing data processing on the uplink data to obtain first processed data includes:

receiving a UE context establishment request initiated by a first CU based on the UE context corresponding to the terminal equipment, and establishing the UE context;

6. An uplink data processing method applied to a first Centralized Unit (CU) is characterized by comprising the following steps:

7. The method of claim 6, further comprising:

8. The method of claim 6 or 7, further comprising:

9. The method according to claim 6 or 7, wherein if the first CU retains the UE context corresponding to the terminal device, further comprising:

10. The method of claim 9, further comprising:

11. The method of claim 7, wherein if the first CU does not have the UE context corresponding to the terminal device reserved, further comprising:

12. The method of claim 11, further comprising:

13. An uplink data processing method is applied to a terminal device, and is characterized by comprising the following steps:

14. A first distribution unit, DU, of a network device, comprising a memory, a transceiver, a processor:

performing data processing on the uplink data to obtain first processed data;

15. The distribution unit according to claim 14, wherein the not performing the operation of releasing the UE context corresponding to the terminal device includes:

16. The distribution unit according to claim 14 or 15, wherein the first message further comprises an RRC recovery request for requesting RRC recovery;

sending the RRC recovery request to the first CU.

17. The distribution unit according to claim 14 or 15, wherein in the previous uplink data processing process, if the first DU does not perform an operation of releasing the UE context corresponding to the terminal device, the performing data processing on the uplink data to obtain first processed data includes:

18. The distribution unit according to claim 14 or 15, wherein if the first DU does not retain the UE context corresponding to the terminal device, the performing data processing on the uplink data to obtain first processed data includes:

19. A first central unit, CU, of a network device, comprising a memory, a transceiver, a processor:

20. The hub unit of claim 19, wherein the operations further comprise:

21. The hub unit of claim 19 or 20, wherein the operations further comprise:

22. The central unit according to claim 19 or 20, wherein if the first CU has a UE context corresponding to the terminal device reserved, further comprising:

23. The hub unit of claim 22, wherein the operations further comprise:

24. The centralized unit of claim 20, wherein if the first CU does not have a UE context corresponding to the terminal device reserved, further comprising:

25. The hub unit of claim 24, wherein the operations further comprise:

26. A network device comprising a first distribution unit DU according to any of claims 14-18 and a first concentration unit CU according to any of claims 19-25.

27. A terminal device, comprising a memory, a transceiver, a processor:

28. An upstream data processing apparatus, applied to a first Distribution Unit (DU), the apparatus comprising:

29. Upstream data processing device, applied to a first central unit, CU, comprising:

30. An uplink data processing apparatus, applied to a terminal device, the apparatus comprising:

31. A computer-readable storage medium, wherein computer-executable instructions are stored in the computer-readable storage medium, and when executed by a processor, the computer-executable instructions are configured to implement the uplink data processing method according to any one of claims 1 to 13.