A context management method and device

Abstract

A context management method and apparatus, wherein the method includes: when the distributed unit DU of a network side device receives a first message from the centralized unit CU of the network side device, the context of the terminal side device in an inactive state can be retained. The first message includes a second message, and the second message is used to indicate that the terminal side device enters an inactive state and releases the connection with the network side device. Through the method provided in the present application, when the DU of the network side device retains (or maintains) the context of the terminal side device in an inactive state, uplink data from the terminal side device in an inactive state can be received based on information such as the context, which can reduce the overhead and power consumption of the terminal side device in sending signaling.

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a context management method and device. Background Art

[0002] In current communication systems, such as the long term evolution (LTE) system or the new radio (NR) system, after the terminal side device accesses the network side device, the network side device can establish a corresponding context for the terminal side device. When the terminal side device switches from the radio resource control (RRC) connection state to the RRC idle state, the network side device releases the context of the terminal side device. In addition, in the new radio (NR) system, an inactive state (also referred to as the third state) is introduced for the RRC state of the terminal side device. In this inactive state, the terminal side device can maintain the core network connection, but does not perform operations such as cell switching, uplink timing update, and radio link monitoring. When the terminal side device is converted from the RRC connection state to the inactive state, the terminal side device saves part of the context. When the terminal side device is converted from the inactive state to the RRC connection state, the network side device notifies the terminal side device to restore the saved context.

[0003] In NR and LTE systems, the network side device can be composed of a centralized unit (CU) and a distributed unit (DU), wherein some functions of the network side device are deployed in a CU, and the remaining functions are deployed in the DU. Multiple DUs can share a CU, which can save costs and facilitate network expansion. For the network side device of the CU-DU architecture, the CU of the network side device is responsible for managing the RRC state of the terminal side device. Therefore, when the RRC state of the terminal side device changes, the CU of the network side device needs to notify the DU of the network side device to perform linked context processing. Specifically, during the process of the terminal side device switching from the RRC connected state to the inactive state, the CU of the network side device notifies the DU of the network side device to release the context of the terminal side device, which includes all dedicated F1 transmission resources and air interface configuration information.

[0004] However, if the DU of the network side device releases the context of the terminal side device, when the inactive terminal side device sends uplink data to the DU of the network side device, the DU of the network side device cannot immediately send the data to the CU of the network side device. The DU of the network side device must wait until the context establishment process is completed before sending uplink data to the CU of the network side device, which results in a longer uplink data transmission delay and also increases the power consumption of the terminal side device. Summary of the invention

[0005] The purpose of the implementation mode of the present application is to provide a context management method and apparatus to solve the problem of how to reduce the uplink data transmission delay of a terminal side device in an inactive state.

[0006] In a first aspect, the present application provides a context management method, comprising: a distributed unit DU of a network side device receives a first message from a centralized unit CU of the network side device; the first message includes a second message, and the second message is used to instruct the terminal side device to enter an inactive state and release the connection with the network side device; the DU of the network side device retains the context of the terminal side device in an inactive state.

[0007] Through the above method, when the DU of the network side device retains the context of the terminal side device in an inactive state, it can receive uplink data from the inactive terminal side device based on the context and other information, which can reduce the overhead and power consumption of sending signaling by the terminal side device.

[0008] In a possible implementation, the first message includes first information, and the first information is used to instruct the DU of the network side device to retain the air interface context in the context of the terminal side device; the DU of the network side device retains the air interface context of the terminal side device according to the first information.

[0009] In a possible implementation, the first information is also used to instruct the DU of the network side device to retain the F1 context in the context of the terminal side device; the F1 context includes the data transmission channel of the terminal side device, and the data transmission channel is the F1 interface dedicated transmission tunnel corresponding to the data wireless bearer DRB data of the terminal side device.

[0010] Furthermore, when the DU of the network side device reserves the data transmission channel of the terminal side device in an inactive state, the uplink data of the inactive terminal side device can be immediately transmitted to the CU of the network side device, thereby reducing the data transmission delay. At the same time, the delay of the terminal side device in monitoring the PDCCH that responds to the uplink data can also be reduced, thereby reducing the power consumption of the terminal side device.

[0011] In a possible implementation, the first message is an interface message between the CU of the network side device and the DU of the network side device, but is not a user equipment UE context release command message in the interface message.

[0012] In a possible implementation, the context includes one or more of the following:

[0013] Configuration authorization for the terminal side device configuration;

[0014] Configuration information of the PDCCH configured for the terminal side device;

[0015] A temporary identifier used to scramble the PDCCH;

[0016] An inactive wireless network temporary identifier I-RNTI configured for the terminal side device;

[0017] Configuration information of the RLC layer of the wireless bearer configured for the terminal side device.

[0018] In a second aspect, the present application further provides a communication device, which has the function of implementing any of the methods provided in the first aspect. The communication device can be implemented by hardware, or by executing corresponding software implementation by hardware. The hardware or software includes one or more units or units corresponding to the above functions.

[0019] In one possible implementation, the communication device includes: a processor configured to support the communication device to perform the corresponding functions of the DU of the network side device in the method shown above. The communication device may also include a memory, which may be coupled to the processor and stores the necessary program instructions and data of the communication device. Optionally, the communication device also includes a communication interface, which is used to support communication between the communication device and a device such as a CU of the network side device.

[0020] In a possible implementation, the communication device includes corresponding functional units, which are respectively used to implement the steps in the above method. The functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

[0021] In a possible implementation, the structure of the communication device includes a processing unit and a communication unit, and these units can perform corresponding functions in the above method example. For details, please refer to the description of the method provided in the first aspect, which will not be repeated here.

[0022] In a third aspect, the present application provides a context management method, comprising:

[0023] When the centralized unit CU of the network side device determines that the terminal side device enters an inactive state, a first message is generated; the first message includes a second message, and the second message is used to indicate that the terminal side device enters an inactive state and releases the connection with the network side device;

[0024] The CU of the network side device sends the first message to the distributed unit DU of the network side device, where the first message is used to instruct the DU of the network side device to retain the context of the terminal side device in an inactive state.

[0025] In a possible implementation, the first message includes first information, and the first information is used to instruct the DU of the network side device to retain the air interface context of the terminal side device.

[0026] In a possible implementation, the first information is also used to instruct the DU of the network side device to retain the F1 context of the terminal side device; the F1 context includes a data transmission channel of the terminal side device, and the data transmission channel is an F1 interface dedicated transmission tunnel corresponding to the data wireless bearer DRB data of the terminal side device.

[0027] In a possible implementation manner, the first message is an F1 application layer F1AP message, but is not a context release command message in the F1AP message.

[0028] In a possible implementation, the context includes one or more of the following:

[0029] Configuration authorization for the terminal side device configuration;

[0030] Configuration information of the PDCCH configured for the terminal side device;

[0031] A temporary identifier used to scramble the PDCCH;

[0032] An inactive wireless network temporary identifier I-RNTI configured for the terminal side device;

[0033] Configuration information of the RLC layer of the radio bearer configured for the terminal side device;

[0034] Configuration information of the MAC layer configured for the terminal side device.

[0035] In a fourth aspect, the present application further provides a communication device, which has the function of implementing any of the methods provided in the third aspect. The communication device can be implemented by hardware, or by executing corresponding software implementation by hardware. The hardware or software includes one or more units or units corresponding to the above functions.

[0036] In one possible implementation, the communication device includes: a processor configured to support the communication device to perform the corresponding functions of the CU of the network side device in the method shown above. The communication device may also include a memory, which may be coupled to the processor and stores the necessary program instructions and data of the communication device. Optionally, the communication device also includes a communication interface, which is used to support communication between the communication device and a device such as a DU of the network side device.

[0037] In a possible implementation, the communication device includes corresponding functional units, which are respectively used to implement the steps in the above method. The functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

[0038] In a possible implementation, the structure of the communication device includes a processing unit and a communication unit, and these units can perform corresponding functions in the above method example. For details, please refer to the description of the method provided in the third aspect, which will not be repeated here.

[0039] In a fifth aspect, the present application provides a context management method, including: a distributed unit DU of a network side device receives capability information from a centralized unit CU of the network side device; the capability information is used to indicate the capability of a terminal side device; when the DU of the network side device determines that the terminal side device is in an inactive state based on the capability information and has the ability to transmit uplink information in a configuration authorization, the context of the terminal side device in an inactive state is retained.

[0040] Through the above method, when the DU of the network side device retains the context of the terminal side device in an inactive state, it can receive uplink data from the inactive terminal side device based on the context and other information, which can reduce the overhead and power consumption of sending signaling by the terminal side device.

[0041] In a possible implementation, the DU of the network side device retains the air interface context in the context of the terminal side device.

[0042] In one possible implementation, the DU of the network side device retains the F1 context in the context of the terminal side device; the F1 context includes a data transmission channel of the terminal side device, and the data transmission channel is an F1 interface dedicated transmission tunnel corresponding to the data wireless bearer DRB data sent to the terminal side device.

[0043] Furthermore, when the DU of the network side device reserves the data transmission channel of the terminal side device in an inactive state, the uplink data of the inactive terminal side device can be immediately transmitted to the CU of the network side device, thereby reducing the data transmission delay. At the same time, the delay of the terminal side device in monitoring the PDCCH that responds to the uplink data can also be reduced, thereby reducing the power consumption of the terminal side device.

[0044] In a possible implementation, the context includes one or more of the following:

[0045] Configuration authorization for the terminal side device configuration;

[0046] Configuration information of the PDCCH configured for the terminal side device;

[0047] A temporary identifier used to scramble the PDCCH;

[0048] An inactive wireless network temporary identifier I-RNTI configured for the terminal side device;

[0049] Configuration information of the RLC layer of the wireless bearer configured for the terminal side device.

[0050] In a sixth aspect, the present application further provides a communication device, which has the function of implementing any of the methods provided in the fifth aspect. The communication device can be implemented by hardware, or by executing corresponding software implementation by hardware. The hardware or software includes one or more units or units corresponding to the above functions.

[0051] In one possible implementation, the communication device includes: a processor configured to support the communication device to perform the corresponding functions of the DU of the network side device in the method shown above. The communication device may also include a memory, which may be coupled to the processor and stores the necessary program instructions and data of the communication device. Optionally, the communication device also includes a communication interface, which is used to support communication between the communication device and a device such as a CU of the network side device.

[0052] In a possible implementation, the communication device includes corresponding functional units, which are respectively used to implement the steps in the above method. The functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

[0053] In a possible implementation, the structure of the communication device includes a processing unit and a communication unit, and these units can perform corresponding functions in the above method example. For details, please refer to the description of the method provided in the fifth aspect, which will not be repeated here.

[0054] In a seventh aspect, the present application provides a communication device, comprising a processor, and when the processor executes a computer program or instruction in a memory, the method described in the first aspect, the third aspect, or the fifth aspect is executed.

[0055] In an eighth aspect, the present application provides a communication device, comprising a processor and a memory, the memory being used to store computer programs or instructions; the processor being used to execute the computer programs or instructions stored in the memory so that the communication device performs the corresponding method as shown in the first aspect, the third aspect, or the fifth aspect.

[0056] In the ninth aspect, the present application provides a communication device, comprising a processor, a memory and a transceiver, wherein the transceiver is used to receive a signal or send a signal; the memory is used to store a computer program or instruction; and the processor is used to call the computer program or instruction from the memory to execute the method described in the first aspect, the third aspect or the fifth aspect.

[0057] In a tenth aspect, the present application provides a communication device, comprising a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor; the processor runs the code instructions to execute the corresponding method as shown in the first aspect, the third aspect, or the fifth aspect.

[0058] In the eleventh aspect, the present application provides a computer-readable storage medium, which is used to store computer programs or instructions. When a computer reads and executes the computer program or instructions, the method described in the first aspect, the third aspect, or the fifth aspect is implemented.

[0059] In a twelfth aspect, the present application provides a computer program product comprising instructions, and when a computer reads and executes the computer program product, the method described in the first aspect, the third aspect, or the fifth aspect is implemented.

[0060] In the thirteenth aspect, the present application provides a chip, including a processor, which is coupled to a memory and is used to execute a computer program or instructions stored in the memory. When the processor executes the computer program or instructions, the method described in the first aspect, the third aspect, or the fifth aspect is implemented.

[0061] In a fourteenth aspect, the present application provides a system, comprising the communication device provided in the second aspect and the communication device provided in the fourth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] Figure 1 A schematic diagram of the structure of a network side device applicable to an embodiment of the present application;

[0063] Figure 2 A schematic diagram of a protocol stack structure provided in an embodiment of the present application;

[0064] Figure 3 Another schematic diagram of a protocol stack structure provided in an embodiment of the present application;

[0065] Figure 4 It is a structural diagram of another network side device applicable to the embodiment of the present application;

[0066] Figure 5 A schematic diagram of a context configuration process provided in an embodiment of the present application;

[0067] Figure 6 A flowchart of a context management method provided in an embodiment of the present application;

[0068] Figure 7 A schematic diagram of a data transmission process provided in an embodiment of the present application;

[0069] Figure 8 A flowchart of a context management method provided in an embodiment of the present application;

[0070] Fig. 9 A schematic diagram of a data transmission process provided in an embodiment of the present application;

[0071] Fig.10 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0072] Fig.11 A schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0073] The embodiments of the present application will be further described in detail below in conjunction with the accompanying drawings.

[0074] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: the 5th Generation mobile communication technology (5G) system (such as New Radio (NR)), Long Term Evolution (LTE) system, LTE frequency division duplex (Frequency Division Duplex, FDD) system, LTE time division duplex (Time Division Duplex, TDD), etc., without limitation here.

[0075] In the embodiment of the present application, the terminal side device can be a device with wireless transceiver function or a chip that can be set in any device, and can also be called user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent or user device. The terminal side device in the embodiment of the present application can be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc.

[0076] The network side device can be an evolved base station (evolutional node B, eNB) in the LTE system, or a next generation base station (next Generation node B, gNB) in the NR system, etc.

[0077] like Figure 1 As shown, in an embodiment of the present application, the network side device can be composed of a centralized unit (CU) and a distributed unit (DU). Part of the functions of the network side device are deployed in a CU, and the remaining functions are deployed in the DU, and multiple DUs can share one CU. For the network side device of the CU-DU architecture, the CU of the network side device is responsible for managing the RRC state of the terminal side device.

[0078] In the embodiment of the present application, when the network side device is a device supporting the NR system, the CU of the network side device and the DU of the network side device can be divided according to the protocol stack as follows: Figure 2 shown. Figure 2In the wireless communication system, the radio resource control (RRC) layer, the service data adaptation protocol (SDAP) layer and the packet data convergence protocol (PDCP) layer are deployed in the CU of the network side device; the radio link control (RLC) layer, the media access control (MAC) layer and the physical (PHY) layer are deployed in the DU of the network side device.

[0079] When the network side device is a device supporting the LTE system, the CU of the network side device and the DU of the network side device can be divided according to the protocol stack as follows: Figure 3 shown. Figure 3 In the present invention, the RRC layer and the PDCP layer are deployed in the CU of the network side device; the RLC layer, the MAC layer and the physical layer are deployed in the DU of the network side device.

[0080] The division of the protocol layers described above is only an example, and division can also be performed at other protocol layers, which will not be described one by one here.

[0081] Further, such as Figure 4 As shown, relative to Figure 1 In the architecture shown, the CU of the network side device may also be in a form of separation of the control plane (CP) and the user plane (UP), that is, the CU can be divided into two logical network elements: CU-CP and CU-UP. At present, in the LTE system, the interface between CU-DU is named W1 interface, and the interface between CU-DU in the NR system is named F1 interface. The functions of these two interfaces are similar. Figure 4 The network side device is taken as an example of gNB in ​​the NR system. The F1 interface includes the control plane (CP) and the user plane (UP). The transport layer protocol of the control plane is the stream control transport protocol (SCTP), and the transmitted message is the F1 application layer protocol (F1 application protocol, F1AP) message. The transport layer protocol of the user plane is the General Packet Radio Service (GPRS) Tunnelling Protocol User Plane (GPRS Tunnelling Protocol User Plane, GTP-U).

[0082] The interface between CU-CP and CU-UP is named E1, which is used to transmit signaling between CU-CP and CU-UP. The F1-C interface between CU-CP and DU is used to transmit F1 signaling between CU-CP and DU and RRC signaling of terminal-side devices. The F1-U interface between CU-CP and DU is used to transmit data of data radio bearer (DRB). After the DU air interface receives the uplink data carried on the DRB, it is processed by the physical layer, MAC layer, and RLC layer of the DU, and the DRB data is sent to the CU through the F1-U interface. After the DU air interface receives the RRC message sent by the terminal-side device, it is processed by the physical layer, MAC layer, and RLC layer of the DU, and the RRC message is sent to the CU through the F1-CP interface.

[0083] In the above network architecture, the signaling generated by the CU can be sent to the terminal side device through the DU, and the DU can pass the signaling to the terminal without parsing it; correspondingly, the signaling generated by the terminal side device can be sent to the CU through the DU, and the DU can pass the signaling to the CU without parsing it.

[0084] As mentioned above, when the network side device is a CU-DU architecture, the CU has an RRC layer, which is responsible for managing the RRC state of the terminal side device. When the RRC state of the terminal side device changes to an inactive state, an embodiment of the present application provides a method for processing the context of the terminal side device, which will be described in detail below.

[0085] It should be noted that the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0086] In the embodiment of the present application, it mainly involves how the DU of the network side device determines whether to retain the context of the terminal side device. Before the DU of the network side device determines whether to retain the context of the terminal side device, it may also include a process for establishing the context of the terminal side device. For details, please refer to Figure 5 shown.

[0087] Step 501: The terminal side device sends capability information to the CU of the network side device.

[0088] The capability information is used to indicate the capability of the terminal side device. Further, optionally, the capability information is used to indicate that the terminal side device has the capability of inactive state data transmission, which means that when the terminal side device is in an inactive state, it has the capability of transmitting uplink information in a configuration authorization or a scheduling authorization. Among them, the uplink information includes but is not limited to uplink signaling and uplink data. The uplink signaling can be uplink RRC signaling, etc., and the uplink data can be uplink service data, such as video data, audio data, etc.

[0089] It should be noted that scheduling authorization refers to the resource request sent by the terminal side device, and the network side device allocates resources to the terminal side device according to the resource request. For example, the resource request can be a preamble in the random access process, or an uplink scheduling request, etc. Configuration authorization refers to the resources pre-configured by the network side device, without the need for the terminal side device to send a resource request, and has the characteristics of one-time allocation and multiple uses.

[0090] It should be noted that there are multiple capabilities of the terminal side device, and the capability information can also indicate other capabilities of the terminal side device, which is not limited in the embodiments of the present application.

[0091] Step 502: The CU of the network side device sends a UE context establishment request message to the DU of the network side device.

[0092] The UE context establishment request message can be used to request to establish a context for a terminal side device.

[0093] Optionally, the UE context establishment request message may include the capability information.

[0094] Step 503: The DU of the network side device establishes a context for the terminal side device and sends a UE context establishment response message to the CU of the network side device.

[0095] It should be noted that, in the embodiment of the present application, the context may include an air interface context and an F1 context.

[0096] Among them, the air interface context may refer to the RLC layer configuration, MAC layer configuration, physical layer configuration information, I-RNTI, C-RNTI, etc. of the terminal side device. It may also include "configuration authorization for data transmission in inactive state", PDCCH configuration information for sending physical layer feedback information, and RNTI for scrambling PDCCH. F1 context may refer to F1AP ID, transport layer address information for F1 data transmission, etc. The transmission of DRB data of the terminal side device between the CU of the network side device and the DU of the network side device may also be called F1 data transmission.

[0097] In the embodiment of the present application, the context established by the DU of the network side device for the terminal side device may include one or more of the following:

[0098] 1. A configured grant configured for the terminal side device; the configured grant can be used to indicate the uplink resources allocated to the terminal side device, wherein the configured grant may include but is not limited to one or more of a physical uplink shared channel (PUSCH) frequency domain resources, period, starting position, and data demodulation reference information.

[0099] Optionally, the configuration authorization may be configured for a terminal side device in an inactive state, and the terminal side device in the inactive state may use the configuration authorization to send one or more of uplink RRC signaling and uplink data.

[0100] Optionally, the time-frequency resources configured by the configuration authorization can be time-frequency resources dedicated to the terminal side device, that is, time-frequency resources not shared with other terminal side devices. In this case, the DU of the network side device can establish a mapping relationship between the configuration authorization and the context of the terminal side device and the data transmission channel of the terminal side device.

[0101] Optionally, the time-frequency resources configured by the configuration authorization may be time-frequency resources shared by the terminal side device and other terminal side devices. In this case, when the CU of the network side device determines that the terminal side device enters an inactive state, an inactive radio network temporary identity (I-RNTI) may be sent to the DU of the network side device. The DU of the network side device may establish a mapping relationship between the configuration authorization and the I-RNTI of the terminal side device. I-RNTI may be a unique identifier of an inactive terminal side device within a RAN-based notification area (RNA).

[0102] 2. Configuration information of the physical downlink control channel (PDCCH) configured for the terminal side device; the configuration information of PDCCH can be used to send feedback information of uplink data or schedule PUSCH transmission, schedule physical downlink shared control channel (PDSCH) transmission, etc.

[0103] The configuration information of the PDCCH includes but is not limited to the resource location information, period, start position, etc. of the PDCCH.

[0104] In an embodiment of the present application, the PDCCH may schedule the transmission of physical layer signaling, such as at least one of Acknowledgement (ACK) or Negative Acknowledgement (NACK) signaling, uplink authorization for initial transmission, and uplink authorization for retransmission. The PDCCH may also schedule the transmission of the PDSCH, and the information carried in the PDSCH includes but is not limited to one or more of downlink RRC signaling, downlink data, and timing advance commands. The terminal side device can perform uplink transmission and downlink transmission according to the scheduling of the PDCCH.

[0105] 3. A temporary identifier for scrambling the PDCCH; the temporary identifier is a 32-bit radio network temporary identity (RNTI) for scrambling the PDCCH. For example, the temporary identifier may be a cell radio network temporary identity (C-RNTI) of a terminal side device.

[0106] 4. Configuration information of the RLC layer of the wireless bearer configured for the terminal side device.

[0107] 5. Configuration information of the MAC layer configured for the terminal side device.

[0108] 6. I-RNTI configured for the terminal side device.

[0109] It should be noted that the above are only examples, and the context of the terminal-side device may also include other information, which is not limited in the embodiments of the present application and will not be illustrated one by one here.

[0110] Exemplarily, the UE context establishment response message sent by the CU of the network side device may include the context of the terminal side device.

[0111] Figure 5 In the process shown, only the main steps are described. There may be other steps in the process of establishing a context for the terminal-side device, which will not be repeated here.

[0112] pass Figure 5 The process shown in the figure establishes the context of the terminal side device. When the terminal side device enters the inactive state, how the network side device handles the context of the terminal side device can be referred to Figure 6 See Figure 6 , is a flowchart of a context management method provided in an embodiment of the present application, the method flow comprising:

[0113] Step 601: When the CU of the network side device determines that the terminal side device enters an inactive state, a first message is generated.

[0114] The first message includes a second message, and the second message is used to instruct the terminal side device to enter an inactive state and release the connection with the network side device. For example, the second message can be an RRC connection release message defined in the third generation partnership project (3GPP) standard.

[0115] It should be noted that the embodiments of the present application do not limit how the CU of the network side device determines that the terminal side device enters an inactive state. For details, please refer to the description in the prior art, which will not be repeated here. When the CU of the network side device determines that the terminal side device enters an inactive state, it can generate a second message, such as an RRC connection release message, and carry the second message in the first message to the DU of the network side device.

[0116] In an embodiment of the present application, the first message may be an F1AP message, for example, the first message may be a UE context release command message; the first message may also be an F1AP message other than the UE context release command message, for example, the first message may be a downlink RRC message transmission message defined in the 3GPP standard.

[0117] In an embodiment of the present application, the first message can be used to instruct the DU of the network side device to retain (or maintain) the context of the terminal side device in an inactive state.

[0118] Among them, retaining a configuration may mean retaining the variables in the configuration, but the variables in the configuration may be reset; keeping a configuration may mean keeping the values ​​of the variables in the configuration unchanged. For example, retaining the serial number of the configuration may reset the serial number to 0; keeping the serial number of the configuration may not reset the serial number to 0, but may keep the serial number unchanged.

[0119] Optionally, when the CU of the network side device determines, based on the capability information of the terminal side device, that the terminal side device has the capability of inactive state data transmission, the CU of the network side device instructs the DU of the network side device through a first message to retain (or maintain) the context of the terminal side device in an inactive state. When the CU of the network side device determines, based on the capability information of the terminal side device, that the terminal side device does not have the capability of inactive state data transmission, the DU of the network side device may not be instructed through the first message to retain (or maintain) the context of the terminal side device in an inactive state.

[0120] In an embodiment of the present application, there may be multiple implementation methods for the first message. In a first possible implementation method, the first message may include first information, and the first information is used to indicate that the DU of the network side device retains (or maintains) the context of the terminal side device.

[0121] There are many ways to implement the first information. For example, the first information can be the I-RNTI of the terminal side device. When the DU of the network side device determines that the first message includes the I-RNTI, it can determine to retain (or maintain) the context of the terminal side device.

[0122] For another example, the first information may also be inactive status information of the terminal side device, and the inactive status information is used to indicate that the terminal side device is in an inactive state. When the DU of the network side device determines that the first message includes inactive status information, and determines that the terminal side device is in an inactive state based on the inactive status information, it can be determined to retain (or maintain) the context of the terminal side device.

[0123] For another example, the first information may also be a dedicated retention indication, such as a bit. When the value of the bit is 1, it indicates that the context of the terminal side device is reserved (or maintained). When the DU of the network side device determines that the value of the bit corresponding to the dedicated retention indication is 1, the context of the terminal side device is reserved (or maintained).

[0124] Optionally, when the CU of the network side device determines, based on the capability information of the terminal side device, that the terminal side device has the capability of inactive state data transmission, the CU carries the first information in the first message.

[0125] In this implementation, the first message may be a UE context release command message.

[0126] In this implementation, by carrying the first information in the first message, the DU of the network side device can no longer delete the context of the terminal side device according to the first information.

[0127] Optionally, the first information may be used to instruct the DU of the network side device to retain (or maintain) part of the content in the context of the terminal side device, for example, to instruct to retain (or maintain) one or more of the following:

[0128] 1. Configuration authorization for the terminal side device configuration.

[0129] Optionally, the CU of the network side device may also instruct the DU of the network side device to retain the configuration authorization of data transmission corresponding to which radio bearer identifiers or logical channel identifiers.

[0130] Optionally, when the time-frequency resources configured for the authorization are time-frequency resources shared by the terminal side device and other terminal side devices, the first message may also include I-RNTI, so that the DU of the network side device can establish a mapping relationship between the I-RNTI of the terminal side device and the data transmission channel and context of the terminal side device.

[0131] 2. Configuration information of the PDCCH configured for the terminal side device.

[0132] 3. A temporary identifier used to scramble the PDCCH.

[0133] 4. Configuration information of the RLC layer of the wireless bearer configured for the terminal side device.

[0134] 5. Configuration information of the MAC layer configured for the terminal side device.

[0135] 6. Transport layer information of the F1 data transmission channel of the terminal side device, which may include, for example, a transport layer address and a GTP-tunnel endpoint identifier (TEID).

[0136] Optionally, the first information can also be used to instruct the DU of the network side device to retain (or maintain) the F1 context of the terminal side device, wherein the F1 context includes but is not limited to the data transmission channel of the terminal side device, and the data transmission channel is the F1 interface dedicated transmission tunnel corresponding to the DRB data of the terminal side device, that is, the GTP tunnel. The DRB data of the terminal side device is transmitted from the DU of the network side device to the CU of the network side device through the data transmission channel. The data transmission channel can also be referred to as the F1 data transmission channel, etc. For the convenience of description, it is referred to as the data transmission channel below.

[0137] Further optionally, the CU of the network side device may also instruct the DU of the network side device to reserve (or maintain) the data transmission channels of the F1 interfaces corresponding to which DRBs.

[0138] In an embodiment of the present application, the second message may include part or all of the content in the context of the terminal side device, for example, it may include one or more of the following: configuration authorization configured for the terminal side device; configuration information of the PDCCH configured for the terminal side device; a temporary identifier for scrambling the PDCCH; an I-RNTI configured for the terminal side device; configuration information of the RLC layer of the wireless bearer configured for the terminal side device; and configuration information of the MAC layer configured for the terminal side device.

[0139] It should be noted that when the DU of the network side device does not retain (or does not maintain) the configuration authorization, and / or the second message does not include the configuration authorization configured for the terminal side device, the terminal side device can send uplink data through common time-frequency resources. For example, the terminal side device can select a 2-step random access channel (RACH) resource configuration from the broadcast message sent by the network side device, or select a 4-step RACH resource configuration, and request the network to schedule an uplink authorization, so as to perform uplink data transmission according to the selected 2-step RACH resource configuration or 4-step RACH resource configuration. For details, please refer to the following description, which will not be repeated here.

[0140] When the DU of the network side device does not retain (or does not maintain) the configuration information of the PDCCH, and / or the second message does not include the configuration information of the PDCCH configured for the terminal side device, the DU of the network side device may send the PDCCH using the configuration information of the public PDCCH, for example, using the configuration information of the PDCCH for scheduling broadcast messages or random access responses, etc.

[0141] When the DU of the network side device does not retain (or does not maintain) a temporary identifier for scrambling the PDCCH, and / or the second message does not include a temporary identifier for scrambling the PDCCH, a common RNTI can be used to scramble the PDCCH, or an RNTI for scrambling the PDCCH can be deduced based on RACH resources or configuration authorization.

[0142] When the DU of the network side device does not retain (or does not maintain) the configuration information of the RLC layer, and / or the second message does not include the configuration information of the RLC layer, the DU of the network side device may adopt the common configuration information of the RLC layer.

[0143] When the DU of the network side device does not retain (or does not maintain) the configuration information of the MAC layer, and / or the second message does not include the configuration information of the MAC layer, the DU of the network side device may adopt the common configuration information of the MAC layer.

[0144] When the DU of the network side device does not reserve (or does not maintain) the data transmission channel of the terminal side device, the DU of the network side device can request the CU of the network side device to restore and establish the data transmission channel of the F1 interface of the terminal side device after receiving the uplink data of the terminal side device, and then send the uplink data of the terminal side device to the CU of the network side device through the restored data transmission channel.

[0145] In a second possible implementation, the first message may be implicitly indicated. For example, the first message is an F1AP message other than the UE context release command message, for example, the first message may be a downlink RRC message transmission message.

[0146] Optionally, when the CU of the network side device determines, based on the capability information of the terminal side device, that the terminal side device has the capability of inactive state data transmission, it implicitly instructs the DU of the network side device through a first message to retain the air interface context of the terminal side device.

[0147] It should be noted that in the existing protocol, when the DU of the network side device receives the UE context release command message, all configuration information of the terminal side device can be deleted, including context information and the like. In a second possible implementation, the CU of the network side device carries a second message through a downlink RRC message transmission message or other F1AP message other than the UE context release command message. At this time, when the DU of the network side device receives a downlink RRC message transmission message or other message, it will not delete the context information and the like of the terminal side device, thereby retaining (or maintaining) the air interface context in the context of the terminal side device that is in an inactive state.

[0148] Optionally, in this implementation, the DU of the network side device may retain (or maintain) part or all of the content in the air interface context of the terminal side device in an inactive state, for example, retain (or maintain) one or more of the following:

[0149] 1. Configuration information of the PDCCH configured for the terminal side device.

[0150] 2. A temporary identifier used to scramble the PDCCH.

[0151] 3. I-RNTI configured for the terminal side device.

[0152] 4. Configuration information of the RLC layer of the wireless bearer configured for the terminal side device.

[0153] 5. Configuration information of the MAC layer configured for the terminal side device.

[0154] For details of the above content, please refer to the description in the first possible implementation method above, which will not be repeated here.

[0155] It should be noted that when the DU of the network side device does not retain (or does not maintain) any of the above items, you can refer to the description in the first possible implementation method above, which will not be repeated here.

[0156] Optionally, in this implementation, the DU of the network side device may also reserve (or maintain) the data transmission channel of the terminal side device.

[0157] Further optionally, the DU of the network side device can also reserve (or maintain) the data transmission channels of the F1 interface corresponding to some or all DRBs of the terminal side device. The specific data transmission channels of the F1 interface corresponding to which DRBs are reserved (or maintained) can be determined based on actual conditions and are no longer limited.

[0158] Step 602: The CU of the network side device sends the first message to the DU of the network side device.

[0159] Step 603: The DU of the network side device receives a first message from the CU of the network side device.

[0160] Step 604: The DU of the network side device reserves (or maintains) the context of the terminal side device that is in an inactive state.

[0161] As mentioned above, in the first possible implementation, when the first message includes the first information, the DU of the network side device retains (or maintains) the air interface context of the terminal side device in an inactive state according to the first information. The DU of the network side device can also retain (or maintain) the F1 context of the terminal side device in an inactive state. For details, please refer to the description in step 601, which will not be repeated here.

[0162] In a second possible implementation, when the first message does not include the first information, the DU of the network side device determines that the first message is not a UE context release command message, and retains (or maintains) the air interface context of the terminal side device in an inactive state. The DU of the network side device may also retain (or maintain) the F1 context of the terminal side device in an inactive state.

[0163] As to how the DU of the network side device specifically retains (or maintains) the context of the terminal side device in an inactive state, please refer to the description in the previous steps and will not be repeated here.

[0164] Optionally, when the time-frequency resources configured by the configuration authorization in the context of the terminal side device are time-frequency resources dedicated to the terminal side device, the DU of the network side device can establish a mapping relationship between the configuration authorization and the context of the terminal side device and the data transmission channel of the terminal side device.

[0165] Optionally, when the time-frequency resources configured by the configuration authorization in the context of the terminal side device are time-frequency resources shared by the terminal side device and other terminal side devices, the first message may include the I-RNTI configured for the terminal side device, and the DU of the network side device can establish a mapping relationship between the I-RNTI of the terminal side device and the data transmission channel and context of the terminal side device.

[0166] Figure 6In the process shown, only the main steps are described. There may be other steps, such as step 605, and the other steps will not be repeated here.

[0167] Step 605: The DU of the network side device sends a third message to the CU of the network side device.

[0168] The third message may be a response message to the first message. For example, when the first message is a UE context release command message defined in the 3GPP standard, the third message may be a UE context release completion message defined in the 3GPP standard. Other situations will not be described in detail.

[0169] pass Figure 6 In the process, when the DU of the network side device retains (or maintains) the context of the terminal side device in an inactive state, it can receive uplink data from the terminal side device in an inactive state based on information such as the context, which can reduce the overhead and power consumption of sending signaling by the terminal side device.

[0170] Furthermore, when the DU of the network side device reserves (or maintains) the data transmission channel of the terminal side device in an inactive state, the uplink data of the inactive terminal side device can be immediately transmitted to the CU of the network side device, thereby reducing the data transmission delay. At the same time, the delay of the terminal side device in monitoring the PDCCH that responds to the uplink data can also be reduced, thereby reducing the power consumption of the terminal side device.

[0171] After the DU of the network side device retains (or maintains) at least one of the air interface context of the terminal side device and the data transmission channel of the terminal side device, the uplink data of the terminal side device can be transmitted according to Figure 7 Process as shown. Figure 7 In the process shown, the CU of the network side device sends the configuration authorization of the DU configuration of the network side device to the terminal side device as an example for explanation.

[0172] Step 701: The terminal side device in an inactive state sends an RRC connection recovery request message and uplink data carried on the DRB to the DU of the network side device.

[0173] The specific content of the uplink data carried on the DRB is not limited in the embodiments of the present application.

[0174] It should be noted that the terminal side device can send at least one of the RRC connection recovery request message and the uplink data carried on the DRB through the configuration authorization. Alternatively, the terminal side device can send the RRC connection recovery request message and the uplink data carried on the DRB separately. For example, the configuration authorization of the same frequency domain resources sends the RRC connection recovery request message and the uplink data carried on the DRB at different times; or, the two configuration authorizations obtained in the 2-step random access process send the RRC connection recovery request message and the uplink data carried on the DRB respectively. Alternatively, the scheduling authorization obtained in the 4-step random access process sends the RRC connection recovery request message, and the uplink data carried on the DRB is sent through the obtained configuration authorization.

[0175] Step 702: When the DU of the network side device receives the RRC connection recovery request message and the uplink data carried on the DRB from the terminal side device, the MAC layer entity in the DU of the network side device can obtain the RRC connection recovery request message and the uplink data carried on the DRB. The DU of the network side device can transmit an initial uplink RRC message to the CU of the network side device, which carries the "RRC connection recovery request" message.

[0176] Step 703: The DU of the network side device transmits the uplink data carried on the DRB to the CU of the network side device through the data transmission channel corresponding to the uplink data carried on the DRB.

[0177] Combined with the previous description, when the time-frequency resources configured by the configuration authorization are time-frequency resources dedicated to the terminal side device, the DU of the network side device can determine the data transmission channel mapped with the configuration authorization, thereby transmitting the uplink data carried on the DRB to the CU of the network side device through the data transmission channel mapped with the configuration authorization.

[0178] When the time-frequency resources configured by the configuration authorization are time-frequency resources shared by the terminal side device and other terminal side devices, the I-RNTI of the terminal side device may be included in the RRC connection recovery request message, and the DU of the network side device can determine the data transmission channel mapped to the I-RNTI, thereby transmitting the uplink data carried on the DRB to the CU of the network side device through the data transmission channel mapped to the I-RNTI.

[0179] Optionally, if the CU of the network side device needs to send downlink data to the terminal side device, step 704 may also be included.

[0180] Step 704: The CU of the network side device sends the downlink data carried on the DRB to the DU of the network side device.

[0181] Step 705: The CU of the network side device sends a downlink RRC message transmission message to the DU of the network side device.

[0182] Step 706: The DU of the network side device sends an RRC connection release message to the terminal side device.

[0183] The RRC connection release message and the downlink data carried on the DRB can be sent to the DU of the network side device through the same transmission block, and the DU of the network side device then sends the RRC connection release message and the downlink data carried on the DRB to the terminal side device at the same time.

[0184] The RRC connection release message and the downlink data carried on the DRB can also be sent to the DU of the network side device at different times, and the DU of the network side device can then be sent to the terminal side device respectively.

[0185] Figure 7 This is just an example. In the actual process, there may be other steps, which will not be described here.

[0186] In another implementation, if the CU of the network side device has not sent the configuration authorization of the DU configuration of the network side device to the terminal side device, then the terminal side device can determine the RACH resource configuration through a broadcast message when sending uplink data. Specifically, in implementation method one, the terminal side device can select a 2-step random access channel (RACH) resource configuration from the broadcast message sent by the network side device. Among them, the 2-step RACH resource configuration includes RACH time-frequency resources, a preamble identifier, and a random access configuration authorization; the terminal side device can send uplink data to the DU of the network side device in the random access configuration authorization, and the terminal side device sends the preamble corresponding to the preamble identifier on the RACH resource; wherein the preamble and the random access configuration authorization are a one-to-one or many-to-one relationship. That is, after the terminal side device sends the preamble, it can send uplink data on the random access configuration authorization corresponding to the preamble.

[0187] In the second implementation method, the terminal side device can select a 4-step RACH resource configuration from the broadcast message sent by the network side device. The terminal side device can send a preamble to the DU of the network side device according to the 4-step RACH resource configuration, and receive the random access response of the DU of the network side device, where the random access response includes PUSCH resources and timing advance information, etc. The PUSCH resources are the resources for the terminal side device to send message 3. The terminal side device can send uplink data through the resources of message 3. It should be noted that message 3 here refers to message 3 in the random access process.

[0188] The process after the terminal side device sends the uplink data can refer to the description in step 702 to step 706, which will not be repeated here.

[0189] Front Figure 6 In the process shown, the DU of the network side device is instructed by the first message to retain (or maintain) the context of the terminal side device in an inactive state. In the embodiment of the present application, a method is also provided to instruct the DU of the network side device to retain (or maintain) the context of the terminal side device in an inactive state without instructing the DU of the network side device to retain (or maintain) the context of the terminal side device in an inactive state through the first message. For details, please refer to Figure 8 shown.

[0190] Step 801: The DU of a network side device receives capability information from the CU of the network side device.

[0191] Among them, the capability information is used to indicate the capability of the terminal side device.

[0192] Step 802: When the DU of the network side device determines that the terminal side device is in an inactive state based on the capability information and has the ability to transmit uplink information in the configuration authorization or scheduling authorization, it retains (or maintains) the context of the terminal side device in the inactive state.

[0193] For details about the context of the terminal device, please refer to Figure 5 as well as Figure 6 The description of the process will not be repeated here.

[0194] Optionally, the DU of the network side device may retain (or maintain) a portion of the context of the terminal side device. For example, the DU of the network side device may retain (or maintain) the air interface context in the context of the terminal side device, or part of the content in the air interface context; for another example, the DU of the network side device may also retain (or maintain) the F1 context in the context of the terminal side device, or part of the content in the F1 context. For details, please refer to Figure 6 The description of the process will not be repeated here.

[0195] The DU of the network side device can also perform other tasks. For details, please refer to Figure 5 , Figure 6 as well as Figure 7 The part of the process involving the DU of the network side device will not be repeated here.

[0196] In the foregoing various possible implementations, the DU of the network side device reserves (or maintains) the air interface context and F1 context of the terminal side device in an inactive state, thereby reducing the data transmission delay of the inactive terminal side device. In another embodiment of the present application, the DU of the network side device may also not reserve (or maintain) the air interface context and F1 context of the terminal side device in an inactive state, and the CU of the network side device maintains the air interface configuration such as the RLC layer, and the DU of the network side device sends data to the CU of the network side device through a public channel, and the CU of the network side device performs RLC processing of the data, which will be described in detail below. Among them, the public channel may refer to an F1 data transmission channel shared by multiple terminal side devices under the UD of a network side device.

[0197] Step 1: The DU of the network side device receives the CU message 1 from the network side device through the F1 interface.

[0198] Among them, message 1 can be a "UE context release command message" or a "downlink RRC message transmission message" or a "UE context modification request message" or the like.

[0199] Optionally, message 1 may carry configuration request information for requesting at least one of the RLC layer configuration and MAC layer configuration corresponding to the data radio bearer of the terminal side device, and the RLC layer configuration includes multiple radio bearer identifiers.

[0200] Among them, the RLC layer configuration may refer to the configuration information of the RLC layer; the MAC layer configuration may refer to the configuration information of the MAC layer.

[0201] Furthermore, the configuration request information may also indicate which radio bearer identifier(s) in the RLC layer configuration is requested.

[0202] Message 1 may also carry an "RRC connection release message", and step 2 is also included in this case.

[0203] Optional, step two: the DU of the network side device sends an RRC connection release message to the terminal side device.

[0204] Step 3: The DU of the network side device sends message 2 to the CU of the network side device.

[0205] For example, when message 1 is a "UE context release command message", message 2 may be a "UE context release completion message".

[0206] Message 2 may include at least one of the RLC layer configuration and MAC layer configuration corresponding to the data radio bearer of the terminal side device.

[0207] Optionally, when message 1 is a "UE context release command message", message 2 includes at least the RLC layer configuration corresponding to the data radio bearer of the terminal side device.

[0208] Step 4: When receiving message 2, the CU of the network side device can set the variables in the RLC entity to the initial values.

[0209] Through the above process, the CU of the network side device can obtain the RLC layer configuration on the DU of the network side device. When the DU of the network side device receives the uplink data of the terminal side device, the uplink data of the terminal side device can be sent to the CU of the network side device through the following process.

[0210] Step 901: The terminal side device in an inactive state sends an RRC connection recovery request message and uplink data carried on the DRB to the DU of the network side device.

[0211] Step 902: When the DU of the network side device receives the RRC connection recovery request message and the uplink data carried on the DRB from the terminal side device, the DU of the network side device transmits the uplink data carried on the DRB to the CU of the network side device through an F1 message.

[0212] The F1 message may be an initial uplink RRC message transmission message, etc.

[0213] It should be noted that the DU of the network side device can also transmit the uplink data carried on the DRB to the CU of the network side device through a public channel.

[0214] The following is an example of how to use the F1 message. The DU of the network side device may send data in two formats:

[0215] If the CU of the network side device obtains the RLC layer configuration, the uplink data carried on the DRB in the F1 message may include a logical channel identifier and a MAC service data unit (SDU), and may be sent in the RLC protocol data unit (PDU) format.

[0216] If the CU of the network side device obtains the RLC layer configuration and the MAC layer configuration, the uplink data carried on the DRB in the F1 message may be sent in the MAC PDU format.

[0217] It should be noted that the DU of the network side device can carry the content of the RRC recovery request message in the "initial uplink RRC message transmission message".

[0218] Optionally, the RRC recovery request message and the uplink data carried on the DRB may not be sent to the CU of the network side device in the same F1 message.

[0219] Step 903: After completing data processing, the CU of the network side device sends a downlink RRC message transmission message to the DU of the network side device.

[0220] Corresponding to step 902, the DU of the network side device may send two types of data, and the CU of the network side device processes them as follows:

[0221] If the CU of the network side device receives an RLC PDU, it determines the RLC configuration according to the logical channel identifier and processes the RLC PDU.

[0222] If the CU of the network side device supports MAC PDU, the CU of the network side device first performs MAC processing to obtain RLC PDU, and then processes the RLC PDU.

[0223] The specific processing process of the CU of the network side device will not be repeated here.

[0224] Optionally, the downlink RRC message transmission message may include an air interface message. The air interface message may be other RRC messages such as an RRC connection release message, an RRC connection recovery message or an RRC connection rejection message.

[0225] Optionally, if the CU of the network side device has downlink data to send, the downlink data may be carried in the downlink RRC message transmission message.

[0226] When the CU of the network side device receives the content in the RRC recovery request message, it can set the variables in the RLC entity to the initial values.

[0227] Step 904: The DU of the network side device sends an RRC connection release message to the terminal side device.

[0228] Fig. 9 This is just an example. In the actual process, there may be other steps, which will not be described here.

[0229] The various embodiments described herein may be independent solutions or may be combined according to internal logic, and all of these solutions fall within the protection scope of this application.

[0230] In the embodiments provided by the present application above, the methods provided by the embodiments of the present application are introduced from the perspective of interaction between various devices. In order to implement the various functions in the methods provided by the embodiments of the present application above, the CU of the network side device or the DU of the network side device may include a hardware structure and / or a software module to implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether one of the above functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.

[0231] The division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment of the present application may be integrated into a processor, or may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0232] Same as above idea, Fig.10 As shown, the embodiment of the present application also provides a device 1000 for implementing the functions of the CU of the network side device or the DU of the network side device in the above method. For example, the device can be a software module or a chip system. In the embodiment of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices. The device 1000 may include: a processing unit 1001 and a communication unit 1002.

[0233] In the embodiment of the present application, the communication unit may also be referred to as a transceiver unit, and may include a sending unit and / or a receiving unit, which are respectively used to execute the steps of sending and receiving the CU of the network side device or the DU of the network side device in the above method embodiment.

[0234] The following, combined Figure 10 to Figure 11 The communication device provided in the embodiment of the present application is described in detail. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment, so the contents not described in detail can be referred to the method embodiment above, and for the sake of brevity, they will not be described one by one here.

[0235] For example, when the apparatus 1000 implements Figure 6 In the process shown, the functions of the DU of the network side device are:

[0236] The communication unit 1002 is used to receive a first message from the CU of the network side device; the first message includes a second message, and the second message is used to instruct the terminal side device to enter an inactive state and release the connection with the network side device;

[0237] The processing unit 1001 is used to retain the context of the terminal side device in an inactive state.

[0238] In a possible implementation manner, the first message includes first information, where the first information is used to instruct the apparatus to retain the air interface context in the context of the terminal side device;

[0239] The processing unit 1001 is specifically used for:

[0240] The air interface context of the terminal side device is retained according to the first information.

[0241] In a possible implementation manner, the first information is further used to instruct the apparatus to retain the F1 context in the context of the terminal side device;

[0242] The F1 context includes a data transmission channel of the terminal side device, and the data transmission channel is an F1 interface dedicated transmission tunnel corresponding to the data radio bearer DRB data of the terminal side device.

[0243] In a possible implementation manner, the first message is an interface message between the apparatus and the CU of the network side device, but is not a user equipment UE context release command message in the interface message.

[0244] In a possible implementation, the context includes one or more of the following:

[0245] Configuration authorization for the terminal side device configuration;

[0246] Configuration information of the physical downlink control channel PDCCH configured for the terminal side device;

[0247] A temporary identifier used to scramble the PDCCH;

[0248] An inactive wireless network temporary identifier I-RNTI configured for the terminal side device;

[0249] Configuration information of the RLC layer of the wireless bearer configured for the terminal side device.

[0250] For example, when the apparatus 1000 implements Figure 6 In the process shown, the functions of the CU of the network side device are:

[0251] The processing unit 1001 is used to generate a first message when determining that the terminal side device enters an inactive state; the first message includes a second message, and the second message is used to indicate that the terminal side device enters an inactive state and releases the connection with the network side device;

[0252] The communication unit 1002 is used to send the first message to the distributed unit DU of the network side device, where the first message is used to instruct the DU of the network side device to retain the context of the terminal side device in an inactive state.

[0253] In a possible implementation, the first message includes first information, and the first information is used to instruct the DU of the network side device to retain the air interface context in the context of the terminal side device.

[0254] In a possible implementation manner, the first information is further used to instruct the DU of the network side device to retain the F1 context in the context of the terminal side device;

[0255] The F1 context includes a data transmission channel of the terminal side device, and the data transmission channel is an F1 interface dedicated transmission tunnel corresponding to the data radio bearer DRB data of the terminal side device.

[0256] In a possible implementation manner, the first message is an interface message between the device and the DU of the network side equipment, but is not a context release command message in the interface message.

[0257] In a possible implementation, the context includes one or more of the following:

[0258] Configuration authorization for the terminal side device configuration;

[0259] Configuration information of the physical downlink control channel PDCCH configured for the terminal side device;

[0260] A temporary identifier used to scramble the PDCCH;

[0261] An inactive wireless network temporary identifier I-RNTI configured for the terminal side device;

[0262] Configuration information of the RLC layer of the wireless bearer configured for the terminal side device.

[0263] For example, when the apparatus 1000 implements Figure 8 In the process shown, the functions of the DU of the network side device are:

[0264] The communication unit 1002 is used to receive capability information of the CU from the network side device; the capability information is used to indicate the capability of the terminal side device;

[0265] The processing unit 1001 is used to retain the context of the terminal side device in the inactive state when it is determined according to the capability information that the terminal side device has the ability to transmit uplink information in the configuration authorization.

[0266] In a possible implementation manner, the processing unit is specifically used to: retain the air interface context in the context of the terminal side device.

[0267] In a possible implementation, the processing unit is specifically configured to: retain the F1 context in the context of the terminal side device;

[0268] The F1 context includes a data transmission channel of the terminal side device, and the data transmission channel is an F1 interface dedicated transmission tunnel corresponding to the data radio bearer DRB data of the terminal side device.

[0269] In a possible implementation, the context includes one or more of the following:

[0270] Configuration authorization for the terminal side device configuration;

[0271] Configuration information of the PDCCH configured for the terminal side device;

[0272] A temporary identifier used to scramble the PDCCH;

[0273] An inactive wireless network temporary identifier I-RNTI configured for the terminal side device;

[0274] Configuration information of the RLC layer of the wireless bearer configured for the terminal side device.

[0275] like Fig.11 The device 1100 provided in an embodiment of the present application is shown. Fig.11 The device shown can be Fig.10 A hardware circuit implementation of the device shown. For ease of explanation, Fig.11 Only the main components of the communication device are shown.

[0276] Fig.11 The device 1100 shown includes at least one processor 1101, and the device 1100 may also include at least one memory 1103 for storing program instructions and / or data. The memory 1103 is coupled to the processor 1101. The coupling in the embodiment of the present application is an indirect coupling or communication connection between devices, units or modules, which may be electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. The processor 1101 may operate in conjunction with the memory 1103. The processor 1101 may execute program instructions stored in the memory 1103. At least one of the at least one memory may be included in the processor.

[0277] In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software. The steps of the method disclosed in conjunction with the embodiment of the present application can be embodied as being executed by a hardware processor, or being executed by a combination of hardware and software modules in a processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it is not described in detail here.

[0278] It should be noted that the processor in the embodiment of the present application can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processing circuit (digitalsignal processor, DSP), an application specific integrated circuit (application specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be embodied as a hardware decoding processor to perform, or a combination of hardware and software modules in the decoding processor to perform. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0279] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0280] The device 1100 may also include a communication interface 1102 for communicating with other devices via a transmission medium, so that the device in the device 1100 can communicate with other devices. In the embodiment of the present application, the communication interface may be a transceiver, a circuit, a bus, a module, or other types of communication interfaces. In the embodiment of the present application, when the communication interface is a transceiver, the transceiver may include an independent receiver, an independent transmitter; or a transceiver with integrated transceiver functions, or an interface circuit.

[0281] The device 1100 may further include a communication line 1104. The communication interface 1102, the processor 1101, and the memory 1103 may be interconnected via the communication line 1104; the communication line 1104 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The communication line 1104 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.11 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0282] For example, when the apparatus 1100 implements Figure 6 In the process shown, the functions of the DU of the network side device are:

[0283] The communication interface 1102 is used to receive a first message from the CU of the network side device; the first message includes a second message, and the second message is used to instruct the terminal side device to enter an inactive state and release the connection with the network side device;

[0284] Processor 1101 is used to retain the context of the terminal side device in an inactive state.

[0285] In a possible implementation manner, the first message includes first information, where the first information is used to instruct the apparatus to retain the air interface context in the context of the terminal side device;

[0286] The processor 1101 is specifically configured to:

[0287] The air interface context of the terminal side device is retained according to the first information.

[0288] In a possible implementation manner, the first information is further used to instruct the apparatus to retain the F1 context in the context of the terminal side device;

[0289] The F1 context includes a data transmission channel of the terminal side device, and the data transmission channel is an F1 interface dedicated transmission tunnel corresponding to the data radio bearer DRB data of the terminal side device.

[0290] In a possible implementation manner, the first message is an interface message between the apparatus and the CU of the network side device, but is not a user equipment UE context release command message in the interface message.

[0291] In a possible implementation, the context includes one or more of the following:

[0292] Configuration authorization for the terminal side device configuration;

[0293] Configuration information of the physical downlink control channel PDCCH configured for the terminal side device;

[0294] A temporary identifier used to scramble the PDCCH;

[0295] An inactive wireless network temporary identifier I-RNTI configured for the terminal side device;

[0296] Configuration information of the RLC layer of the wireless bearer configured for the terminal side device.

[0297] For example, when the apparatus 1100 implements Figure 6 In the process shown, the functions of the CU of the network side device are:

[0298] The processor 1101 is used to generate a first message when determining that the terminal side device enters an inactive state; the first message includes a second message, and the second message is used to indicate that the terminal side device enters an inactive state and releases a connection with the network side device;

[0299] The communication interface 1102 is used to send the first message to the distributed unit DU of the network side device, where the first message is used to instruct the DU of the network side device to retain the context of the terminal side device in an inactive state.

[0300] In a possible implementation, the first message includes first information, and the first information is used to instruct the DU of the network side device to retain the air interface context in the context of the terminal side device.

[0301] In a possible implementation manner, the first information is further used to instruct the DU of the network side device to retain the F1 context in the context of the terminal side device;

[0302] The F1 context includes a data transmission channel of the terminal side device, and the data transmission channel is an F1 interface dedicated transmission tunnel corresponding to the data radio bearer DRB data of the terminal side device.

[0303] In a possible implementation manner, the first message is an interface message between the device and the DU of the network side equipment, but is not a context release command message in the interface message.

[0304] In a possible implementation, the context includes one or more of the following:

[0305] Configuration authorization for the terminal side device configuration;

[0306] Configuration information of the physical downlink control channel PDCCH configured for the terminal side device;

[0307] A temporary identifier used to scramble the PDCCH;

[0308] An inactive wireless network temporary identifier I-RNTI configured for the terminal side device;

[0309] Configuration information of the RLC layer of the wireless bearer configured for the terminal side device.

[0310] For example, when the apparatus 1100 implements Figure 8 In the process shown, the functions of the DU of the network side device are:

[0311] The communication interface 1102 is used to receive capability information of the CU from the network side device; the capability information is used to indicate the capability of the terminal side device;

[0312] Processor 1101 is used to retain the context of the terminal side device in the inactive state when it is determined according to the capability information that the terminal side device has the ability to transmit uplink information in the configuration authorization.

[0313] In a possible implementation, the processor 1101 is specifically configured to: retain the air interface context in the context of the terminal side device.

[0314] In a possible implementation, the processor 1101 is specifically configured to: retain the F1 context in the context of the terminal side device;

[0315] The F1 context includes a data transmission channel of the terminal side device, and the data transmission channel is an F1 interface dedicated transmission tunnel corresponding to the data radio bearer DRB data of the terminal side device.

[0316] In a possible implementation, the context includes one or more of the following:

[0317] Configuration authorization for the terminal side device configuration;

[0318] Configuration information of the PDCCH configured for the terminal side device;

[0319] A temporary identifier used to scramble the PDCCH;

[0320] An inactive wireless network temporary identifier I-RNTI configured for the terminal side device;

[0321] Configuration information of the RLC layer of the wireless bearer configured for the terminal side device.

[0322] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) that contain computer-usable program code.

[0323] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0324] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0325] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these 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 also intended to include these modifications and variations.

Claims

1. A context management method, characterized in that: include: The distributed unit DU of the network side device receives a first message from the centralized unit CU of the network side device; The first message includes a second message, the second message is used to instruct the terminal side device to enter an inactive state and release the connection with the network side device; the first message includes first information, the first information is used to instruct the DU of the network side device to retain the air interface context and the F1 context in the context of the terminal side device; The DU of the network side device retains the air interface context and the F1 context in the context of the terminal side device which is in an inactive state according to the first information.

2. The method according to claim 1, characterized in that The F1 context includes a data transmission channel of the terminal side device, and the data transmission channel is an F1 interface dedicated transmission tunnel corresponding to the data radio bearer DRB data of the terminal side device.

3. The method according to claim 1, characterized in that The first message is an interface message between the CU of the network side device and the DU of the network side device, but is not a user equipment UE context release command message in the interface message.

4. The method according to any one of claims 1 to 3, characterized in that: The context includes one or more of the following: Configuration authorization for the terminal side device configuration; Configuration information of the physical downlink control channel PDCCH configured for the terminal side device; A temporary identifier used to scramble the PDCCH; An inactive wireless network temporary identifier I-RNTI configured for the terminal side device; Configuration information of the RLC layer of the wireless bearer configured for the terminal side device.

5. A context management method, characterized in that: include: When the centralized unit CU of the network side device determines that the terminal side device enters an inactive state, a first message is generated; The first message includes a second message, where the second message is used to instruct the terminal side device to enter an inactive state and release a connection with the network side device; The CU of the network side device sends the first message to the distributed unit DU of the network side device, where the first message includes first information, and the first information is used to instruct the DU of the network side device to retain the air interface context and the F1 context in the context of the terminal side device.

6. The method according to claim 5, characterized in that The F1 context includes a data transmission channel of the terminal side device, and the data transmission channel is an F1 interface dedicated transmission tunnel corresponding to the data radio bearer DRB data of the terminal side device.

7. The method according to claim 5, characterized in that The first message is an interface message between the CU of the network side device and the DU of the network side device, but is not a context release command message in the interface message.

8. The method according to any one of claims 5 to 7, characterized in that: The context includes one or more of the following: Configuration authorization for the terminal side device configuration; Configuration information of the physical downlink control channel PDCCH configured for the terminal side device; A temporary identifier used to scramble the PDCCH; An inactive wireless network temporary identifier I-RNTI configured for the terminal side device; Configuration information of the RLC layer of the wireless bearer configured for the terminal side device.

9. A communication device, characterized in that: include: A communication unit, configured to receive a first message from a centralized unit CU of a network side device; The first message includes a second message, the second message is used to instruct the terminal side device to enter an inactive state and release the connection with the network side device; the first message includes first information, the first information is used to instruct the DU of the network side device to retain the air interface context and the F1 context in the context of the terminal side device; A processing unit is used to retain the air interface context and the F1 context in the context of the terminal side device in an inactive state according to the first information.

10. The device according to claim 9, characterized in that The F1 context includes a data transmission channel of the terminal side device, and the data transmission channel is an F1 interface dedicated transmission tunnel corresponding to the data radio bearer DRB data of the terminal side device.

11. The device according to claim 9, characterized in that The first message is an interface message between the device and the CU of the network side device, but is not a user equipment UE context release command message in the interface message.

12. The device according to any one of claims 9 to 11, characterized in that: The context includes one or more of the following: Configuration authorization for the terminal side device configuration; Configuration information of the physical downlink control channel PDCCH configured for the terminal side device; A temporary identifier used to scramble the PDCCH; An inactive wireless network temporary identifier I-RNTI configured for the terminal side device; Configuration information of the RLC layer of the wireless bearer configured for the terminal side device.

13. A communication device, characterized in that: include: A processing unit, configured to generate a first message when determining that a terminal side device enters an inactive state; The first message includes a second message, where the second message is used to instruct the terminal side device to enter an inactive state and release a connection with the network side device; A communication unit is used to send the first message to the distributed unit DU of the network side device, wherein the first message includes first information, and the first information is used to instruct the DU of the network side device to retain the air interface context and the F1 context in the context of the terminal side device.

14. The device according to claim 13, characterized in that The F1 context includes a data transmission channel of the terminal side device, and the data transmission channel is an F1 interface dedicated transmission tunnel corresponding to the data radio bearer DRB data of the terminal side device.

15. The device according to claim 13, characterized in that The first message is an interface message between the device and the DU of the network side equipment, but is not a context release command message in the interface message.

16. The device according to any one of claims 13 to 15, characterized in that The context includes one or more of the following: Configuration authorization for the terminal side device configuration; Configuration information of the physical downlink control channel PDCCH configured for the terminal side device; A temporary identifier used to scramble the PDCCH; An inactive wireless network temporary identifier I-RNTI configured for the terminal side device; Configuration information of the RLC layer of the wireless bearer configured for the terminal side device.

17. A communication device, characterized in that: include: A memory and a processor, wherein the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory, and the execution of the instructions stored in the memory enables the processor to execute the method according to any one of claims 1 to 8.

18. A computer-readable storage medium, characterized in that: The method comprises computer-readable instructions, and when a communication device reads and executes the computer-readable instructions, the communication device executes the method according to any one of claims 1 to 8.

19. A computer program product, characterized in that The method comprises computer-readable instructions, and when a communication device reads and executes the computer-readable instructions, the communication device executes the method according to any one of claims 1 to 8.

Images