Instruction method, data transmission method, communication node and storage medium

Abstract

The present application provides an instruction method, a data transmission method, a communication node and a storage medium, which include determining a context of a terminal and sending an instruction message to a second communication node, the instruction message including interface connection information related to the context, the interface connection information including a terminal interface identifier corresponding to the first communication node and a terminal interface identifier corresponding to the second communication node, and the interface connection information is used to instruct the second communication node to perform small data transmission SDT via a stored interface.

Description

[Technical Field]

[0001] The present application relates to the technical field of wireless communication networks, for example, to a pointing method, a data transmission method, a communication node, and a storage medium. [Background technology]

[0002] In a wireless communication system, a base station (e.g., a gNB) can be divided into a centralized unit (CU) and a distributed unit (DU), and one base station may include one CU and multiple DUs, with the CU and DUs connected via an interface. Furthermore, a specifically scheduled (Configured Grant (CG)) resource for small data transmission (SDT) is allocated to a user equipment (UE) in a Radio Resource Control (RRC) inactive state (RRC_INACTIVE). However, if the UE performs SDT transmission using a random access channel (RACH) resource, the DU cannot perform small data transmission using the UE context stored when generating the CG configuration resource, resulting in wasted resources on the base station side. Summary of the Invention [Problem to be solved by the invention]

[0003] The present application provides an instruction method, a data transmission method, a communication node, and a storage medium. [Means for solving the problem]

[0004] The present embodiment is Base station centralized unit CU A method of indication applied to receiving an initial uplink radio resource control (RRC) message associated with the terminal from a distributed unit (DU) of the base station, the initial uplink radio resource control (RRC) message including SDT indication information for indicating a small data SDT and an RRC recovery request message transmitted from the terminal via a random access channel (RACH); determining the context of the terminal; DUand sending an instruction message to the interface connection information associated with the context, the instruction message including interface connection information associated with the context, the interface connection information being CU and the terminal interface identifier corresponding to DU The interface connection information includes a terminal interface identifier corresponding to the small data transmission SDT through the stored interface. DU Used to instruct The stored interface is a data radio bearer DRB data transmission channel associated with the terminal. and Provide a method of instruction.

[0005] The present embodiment is Distributed unit DU at base station A data transmission method applied to receiving a radio resource control (RRC) recovery request message from the terminal via a random access channel (RACH); sending an initial uplink RRC message associated with the terminal to a centralized unit (CU) of the base station, where the initial uplink RRC message includes SDT indication information for indicating a small data SDT and the received RRC recovery request message; and receiving an indication message, the indication message including interface connection information related to a context of the terminal, the interface connection information including: CU and the terminal interface identifier corresponding to DU and determining a terminal context and associated stored interfaces based on the interface connection information; and Based on , remembered interface Terminal to CU via Small Data Transmission (SDT) Traffic Data of The interface that transmits and stores the data is the data radio bearer DRB data transmission channel associated with the terminal. and A data transmission method is also provided.

[0006] The present embodiment is a communication node including a memory, a processor, and a computer program stored in the memory and executable by the processor, the program implementing the instruction method or the data transmission method when executed by the processor; A communication node is also provided.

[0007] The present embodiment is a computer-readable storage medium having a computer program stored thereon, the program implementing the instruction method or data transmission method when executed by a processor; A computer-readable storage medium is also provided. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a flowchart of an instruction method according to an embodiment. [Figure 2] 1 is a flowchart of a data transmission method according to an embodiment. [Figure 3] FIG. 1 is a schematic diagram illustrating an implementation of a small data transmission method according to an embodiment. [Figure 4] FIG. 10 is a schematic diagram illustrating another small data transmission method according to an embodiment. [Figure 5] FIG. 10 is a schematic diagram illustrating a further small data transmission method according to an embodiment. [Figure 6] FIG. 10 is a schematic diagram illustrating a further small data transmission method according to an embodiment. [Figure 7] 1 is a structural schematic diagram of an indicator device according to an embodiment; [Figure 8] 1 is a structural schematic diagram of a data transmission device according to an embodiment; [Figure 9] FIG. 2 is a schematic diagram illustrating the hardware structure of a communication node according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] The present application will be described below with reference to the drawings and examples. It will be understood that the specific examples described here are merely for the purpose of interpreting the present application and are not intended to limit the present application. For the sake of convenience, the drawings show only parts relevant to the present application, rather than all of the structures.

[0010] With the development of smart terminals and IoT terminals, the number of users of some instant communication traffic applications is increasing, and such traffic is usually always online and mainly involves the transmission of small data such as text messages when used by users. Small data traffic may cause problems such as an increase in the signaling load of the radio network (RAN) because the UE needs to frequently reestablish a signaling link with the RAN.

[0011] In the case of fourth generation mobile communications (4G), to optimize support for infrequent small data packet transmissions, 4G networks support the UE's ability to transmit corresponding small data to the RAN by carrying it in a RACH access request message or a Radio Resource Control (RRC) connection establishment request message when accessing a Random Access Channel (RACH). In this case, the UE can transmit occasional small amounts of data without frequently reestablishing a signaling link with the network.

[0012] The RRC states in 4G Long Term Evolution (LTE) may include two types: RRC_IDLE (i.e., RRC idle state) and RRC_CONNECTED (i.e., RRC connected state). 5G introduces RRC_INACTIVE (i.e., RRC inactive state). In the RRC INACTIVE state, the UE is in a power-saving sleep state, but the UE still reserves the RAN context, and the RAN also reserves the UE context (i.e., UE Context). Therefore, when there is data transmission, the UE can quickly transition from the RRC INACTIVE state to the RRC CONNECTED state to perform data transmission. This reduces signaling overhead, enables fast access, reduces latency, and further saves power.

[0013] However, for small data transmission, 5G also supports data transmission with the RAN while the UE remains in the RRC_INACTIVE state without entering the RRC_CONNECTED state. 5G small data transmission (i.e., SDT) includes RACH-based SDT and CG resource-based SDT. If a UE is configured with CG resources in the RRC_INACTIVE state, the UE can perform small data transmission using the CG resources in RRC_INACTIVE. However, the signal quality of the CG resources of the UE may be poor. In this case, the UE may transmit small data using the RACH access process in the RRC_INACTIVE state even when CG resources are configured.

[0014] A 5G base station (e.g., gNB) can be separated into a CU and a DU, and one gNB may include one CU and multiple DUs, and the CU and DU are connected via an interface. If a gNB allocates CG resources for small data transmission to a UE in RRC_INACTIVE, but the UE transmits small data using RACH resources, the DU cannot transmit the small data using the UE context stored when generating the CG configuration resource, resulting in wasting resources on the base station side.

[0015] FIG. 1 is a flowchart of an instruction method according to one embodiment. As shown in FIG. 1, the method can be applied to a first communication node, which may be a CU. The method according to this embodiment includes steps 110 and 120.

[0016] In step 110, the context of the terminal is determined.

[0017] In step 120, an instruction message is sent to a second communication node, and the instruction message includes interface connection information related to the context, the interface connection information including a terminal interface identifier corresponding to the first communication node and a terminal interface identifier corresponding to the second communication node, and the interface connection information is used to instruct the second communication node to use the stored interface for SDT.

[0018] In this embodiment, the first communication node determines the context of the terminal and then sends an indication message to the second communication node. Here, the second communication node may be a DU. The indication message may include interface connection information related to the context, which may include a terminal interface identifier corresponding to the first communication node and a terminal interface identifier corresponding to the second communication node. The interface connection information may be used to instruct the second communication node to perform SDT via the stored interface. The stored interface may include an interface stored based on the terminal context, specifically, a UE F1 interface on the CU side and a UE F1 interface on the DU side.

[0019] In this embodiment, in order to effectively use resources on the base station side, the first communication node determines the context of the terminal and sends an instruction message to the second communication node, so that the second communication node can perform SDT based on the interface connection information and terminal context related to the context contained in the instruction message.

[0020] In one embodiment, the method further includes receiving an initial uplink RRC message from a second communication node, the initial uplink RRC message including an RRC recovery request message, the RRC recovery request message including an inactive radio network temporary identity (I-RNTI), identifying a terminal based on the I-RNTI, and performing SDT authentication on the terminal.

[0021] In one embodiment, the indication message includes at least one of an SDT authentication success message, a terminal context establishment request message, and a terminal context modification message.

[0022] In one embodiment, the method further includes receiving an uplink common control channel (RRC) message of the second communication node carrying signaling data; and, if the uplink common control channel (RRC) message carries a Common Control Channel (CCCH) message indication or if the uplink common control channel (RRC) message does not carry interface connection information related to a context, determining a terminal to which the signaling data belongs based on an I-RNTI in the signaling data carried in the uplink common control channel (RRC) message.

[0023] In one embodiment, the method further includes receiving a text update message from a second communication node, the text update message including a Configured Grant (CG) resource release instruction or updated CG resources; and, if the text update message includes a CG resource release instruction, determining to release or retain a context of the second communication node side terminal based on the CG resource release instruction.

[0024] In one embodiment, the method further includes: setting CG resource related information in an RRC release message based on the CG resource release instruction or the updated CG resource; and sending an RRC release message to notify the terminal to release the CG resource or update the CG resource.

[0025] In one embodiment, the method further includes receiving an initial uplink RRC message of the second communication node, the initial uplink RRC message carrying SDT type information including a RACH SDT or a CG SDT; and, if a CG resource is configured and the SDT type is a RACH SDT, releasing or updating the CG resource.

[0026] In one embodiment, the method further includes sending a terminal context update request including a CG resource release instruction or a CG resource update instruction, where the CG resource release instruction is used to instruct the second communication node to release the CG resource and suspend the UE context, and the CG resource update instruction is used to instruct the DU to reallocate and update the CG resource.

[0027] An embodiment of the present application further provides a data transmission method. Figure 2 is a flowchart of the data transmission method according to an embodiment. As shown in Figure 2, the method can be applied to a second communication node, which may be a DU. The method according to this embodiment includes steps 210, 220, and 230.

[0028] In step 210, an instruction message is received, the instruction message including interface connection information related to a terminal context, the interface connection information including a terminal interface identifier corresponding to a first communication node and a terminal interface identifier corresponding to the second communication node.

[0029] In step 220, the context of the terminal and the associated stored interfaces are determined based on the interface connection information.

[0030] In step 230, SDT is performed based on the terminal context and the stored interface.

[0031] In this embodiment, first, the second communication node receives an indication message sent by the first communication node, where the indication message may include interface connection information related to a terminal context, where the interface connection information may include a terminal interface identifier corresponding to the first communication node and a terminal interface identifier corresponding to the second communication node. Then, the second communication node can determine the terminal context and associated stored interfaces based on the interface connection information related to the terminal context in the indication message, where the stored interfaces may include interfaces stored based on the terminal context, specifically, the UE F1 interface on the CU side and the UE F1 interface on the DU side. Finally, the second communication node can perform SDT based on the terminal context and the stored interfaces.

[0032] In this embodiment, in order to effectively use resources on the base station side, the second communication node can determine the terminal context and the associated stored interface based on the interface connection information in the instruction information by receiving the instruction information from the first communication node, and then perform SDT based on the terminal context and the stored interface.

[0033] In one embodiment, the method further includes: sending an initial uplink RRC message, wherein the initial uplink RRC message includes an RRC recovery request message, and wherein the RRC recovery request message includes an I-RNTI.

[0034] In one embodiment, the indication message includes at least one of an SDT authentication success message, a terminal context establishment request message, and a terminal context modification message.

[0035] In one embodiment, performing SDT based on the terminal context and the stored interface includes, when receiving SDT traffic data for the terminal, transmitting the SDT traffic data to the first communication node via a Data Radio Bearer (DRB) data transmission channel corresponding to the terminal based on the stored terminal interface corresponding to the first communication node and the stored terminal interface corresponding to the second communication node.

[0036] In one embodiment, the method further includes, if the terminal receives signaling data, transmitting an uplink common control channel RRC message carrying the signaling data.

[0037] In one embodiment, the uplink common control channel (RRC) message further carries interface connection information related to the CCCH message indication or context.

[0038] In one embodiment, the method further includes sending a text update message including a CG resource release instruction or the updated CG resource.

[0039] In one embodiment, the method further includes transmitting an initial uplink RRC message carrying SDT type information including a RACH SDT or a CG SDT.

[0040] In one embodiment, the method further includes receiving a terminal context update request including a CG resource release instruction; and releasing the CG resource and suspending the context of the UE based on the CG release instruction.

[0041] In one embodiment, the method further includes receiving a terminal context update request including a CG resource update instruction, reallocating and updating the CG resource based on the CG update instruction, and sending a terminal context update request feedback message.

[0042] The following describes an exemplary method for transmitting small data through different embodiments. In the following embodiments, the first communication node is a CU, and the second communication node is a DU. [Example]

[0043] 3 is a schematic diagram of an implementation of a small data transmission method according to an embodiment. As shown in FIG. 3, the specific process of the method may include the following steps:

[0044] Step 1: When the terminal (i.e., UE) traffic ends, the base station (e.g., gNB) releases the UE to an RRC inactive state (i.e., RRC_INACTIVE) instead of completely releasing the UE connection. The gNB configures CG resources for small data transmission (i.e., SDT) for the UE, and the DU side of the gNB stores the UE context (e.g., Radio Link Control (RLC) configuration, etc.), and the CU side of the gNB also stores the UE context (e.g., Packet Data Convergence Protocol (PDCP) configuration, etc.), and the CU and DU store the DRB data transmission channel (i.e., F1-U DRB tunnel).

[0045] Step 2: If the UE is in an RRC inactive state and is ready to perform SDT, but the CG resource does not meet the threshold requirement, for example, the received signal quality corresponding to the CG resource does not meet the threshold requirement, or the RRC recovery request message sent by the CG resource cannot be successfully transmitted to the gNB, the UE can prepare to send an RRC recovery request message to the gNB via the RACH channel.

[0046] Step 3: The UE sends an RRC recovery request message (i.e., RRC RESUME REQUEST) to the gNB via the RACH channel. After receiving the RRC recovery request message, the DU of the gNB identifies that the UE needs to perform small data transmission. The DU packages the received RRC recovery request message into an initial uplink RRC message (i.e., Initial UL RRC Message) and sends the initial uplink RRC message to the CU, where the initial uplink RRC message carries SDT indication information to instruct the CU that the initial uplink RRC message is for small data transmission.

[0047] Step 4: The CU receives the DU's RRC recovery request message included in the initial uplink RRC message, identifies the UE by the I-RNTI included in the RRC recovery request message, performs small data transmission authentication (i.e., SDT authentication) on the UE, and finds the corresponding CU-side UE context (i.e., UE Context) and connection information of the F1 interface associated with the UE context, where the connection information may include the terminal F1 interface identifier (ID) corresponding to the CU and the terminal F1 interface ID corresponding to the DU (i.e., determines the CU-side UE F1 interface ID and the DU-side UE F1 interface ID associated with the UE context), where the CU-side UE F1 interface ID can be represented as CU UE F1AP ID, and the DU-side UE F1 interface ID can be represented as DU UE F1AP ID, and F1AP can refer to the F1 interface.

[0048] Step 5: The CU sends an indication message, such as an SDT authentication success message (i.e., SDT Authentication Message), to the DU, which includes the UE F1 interface ID on the CU side and the UE F1 interface ID on the DU side related to the UE context. After receiving the message, the DU determines the UE context on the DU side using (CU UE F1AP ID, DU UE F1AP ID) and establishes the connection of the F1 interface related to the UE context. Note that the indication message sent from the CU to the DU is not limited to an SDT authentication success message. The CU can also carry (CU UE F1AP ID, DU UE F1AP ID) in a UE context establishment request message / modification message (i.e., UE CONTEXT SETUP / MODIFICATION REQUEST) to notify the DU to determine the UE context. That is, the indication message sent from the CU to the DU includes at least one of an SDT authentication success message, a terminal context establishment request message, and a terminal context modification message.

[0049] Step 6: In the subsequent small data transmission process, the UE transmits DRB data (i.e., SDT traffic data of the terminal) to the DU through resources scheduled by the RACH or resources scheduled by the CG. After receiving the DRB data, the DU transmits the DRB data to the CU through a DRB data transmission channel corresponding to the UE on the F1 interface based on the connection of the F1 interface associated with the UE's context (i.e., the terminal interface corresponding to the stored CU and the terminal interface corresponding to the DU). After receiving the DRB data, the CU transmits the DRB data to the 5G core network (i.e., 5GC). [Example]

[0050] 4 is a schematic diagram of another small data transmission method according to an embodiment. As shown in FIG. 4, the specific process of the method may include the following steps:

[0051] Step 1: When the terminal (i.e., UE) traffic ends, the base station (e.g., gNB) releases the UE to an RRC inactive state (i.e., RRC_INACTIVE) instead of completely releasing the UE connection. The gNB configures CG resources for small data transmission (i.e., SDT) for the UE, and the DU side of the gNB stores the UE context (e.g., RLC configuration, etc.), the CU side of the gNB also stores the UE context (e.g., PDCP configuration, etc.), and the CU and DU store the DRB data transmission channel (i.e., F1-U DRB tunnel).

[0052] Step 2: If the UE is in an RRC inactive state and is ready to perform SDT, but the CG resource does not meet the threshold requirement, for example, the received signal quality corresponding to the CG resource does not meet the threshold requirement, or the RRC recovery request message sent by the CG resource cannot be successfully transmitted to the gNB, the UE can prepare to send an RRC recovery request message to the gNB via the RACH channel.

[0053] Step 3: The UE sends an RRC recovery request message (i.e., RRC RESUME REQUEST) to the gNB via the RACH channel. After receiving the RRC recovery request message, the DU of the gNB identifies that the UE needs to perform small data transmission. The DU packages the received RRC recovery request message into an initial uplink RRC message (i.e., Initial UL RRC Message) and sends the initial uplink RRC message to the CU, where the initial uplink RRC message carries SDT indication information to instruct the CU that the initial uplink RRC message is for small data transmission.

[0054] Step 4: The CU receives the DU's RRC recovery request message included in the initial uplink RRC message, identifies the UE by the I-RNTI included in the RRC recovery request message, performs small data transmission authentication (i.e., SDT authentication) on the UE, and finds the corresponding CU-side UE context (i.e., UE context) and connection information of the F1 interface associated with the UE context, where the connection information may include the terminal F1 interface identifier (ID) corresponding to the CU and the terminal F1 interface ID corresponding to the DU (i.e., determine the CU-side UE F1 interface ID and the DU-side UE F1 interface ID associated with the UE context), where the CU-side UE F1 interface ID can be expressed as CU UE F1AP ID, and the DU-side UE F1 interface ID can be expressed as DU UE F1AP ID, and F1AP can refer to the F1 interface.

[0055] Step 5: The CU sends an indication message, such as an SDT authentication success message (i.e., SDT Authentication Message), to the DU, which includes the UE F1 interface ID on the CU side and the UE F1 interface ID on the DU side related to the UE context. After receiving the message, the DU determines the UE context on the DU side using (CU UE F1AP ID, DU UE F1AP ID) and establishes the connection of the F1 interface related to the UE context. Note that the indication message sent from the CU to the DU is not limited to an SDT authentication success message. The CU can also carry (CU UE F1AP ID, DU UE F1AP ID) in a UE context establishment request message / modification message (i.e., UE CONTEXT SETUP / MODIFICATION REQUEST) to notify the DU to determine the UE context. That is, the indication message sent from the CU to the DU includes at least one of an SDT authentication success message, a terminal context establishment request message, and a terminal context modification message.

[0056] Step 6: The UE transmits subsequent signaling data through corresponding dedicated control channel (DCCH) resources scheduled by the RACH or CG, for example, a signaling radio bearer (SRB) protocol data unit (PDU) or a non-access stratum (NAS) PDU to the DU, and the DU can identify which UE the signaling data is for based on the resources scheduled for different UEs. The DU carries the signaling data (i.e., SRB PDU or NAS PDU) and sends it to the CU via an uplink RRC information transfer (i.e., UL RRC Message Transfer) message, where the UL RRC Message Transfer message carries the CU-side UE F1AP ID and the DU-side UE F1AP ID associated with the UE context to indicate to the CU which UE the signaling data belongs to.

[0057] Step 7: The UE transmits the subsequent signaling data (i.e., SRB PDU or NAS PDU) to the DU through the corresponding CCCH common control channel resource scheduled by the RACH, and carries the UE's I-RNTI in the signaling data. Because it is a CCCH common channel, the DU cannot identify which UE the signaling data is for at this time. The DU then carries the signaling data (i.e., SRB PDU or NAS PDU) and sends it to the CU through an uplink CCCH RRC information transfer (i.e., UL CCCH RRC Message Transfer) message, where the message optionally carries a CCCH message indication to instruct the CU that the signaling data carried in the message is CCCH channel signaling. After receiving the UL CCCH RRC Message Transfer message, if the message carries a CCCH message indication or does not carry the UE F1AP ID on the CU side and the UE F1AP ID on the DU side related to the UE's context (i.e., CU&DU UE F1AP ID), the CU identifies which UE the signaling data belongs to based on the UE's I-RNTI in the signaling data carried in the message. [Example]

[0058] 5 is a schematic diagram of an implementation of a further small data transmission method according to an embodiment. As shown in FIG. 5, the specific process of the method may include the following steps:

[0059] Step 1: A CG resource is configured between the base station and the UE, and the UE performs small data transmission via the CG resource and the base station in an RRC inactive state.

[0060] Step 2: The DU decides to release or reallocate (i.e., update) the CG resource for some reason, such as the valid timer of the CG resource allocated on the DU side times out or the load on the DU side is too large.

[0061] Step 3: The DU sends a UE text update (i.e., UE Context Modification Required) to the CU, where the UE text update message includes a CG resource release instruction or an updated CG resource (but is not limited to this UE text update message).

[0062] Step 4: If the CU receives a UE Context Modification Required message containing a CG resource release instruction, the CU can decide whether to release or keep the UE text (i.e., UE context) on the DU side (including but not limited to the UE text update message).

[0063] Step 5: If the CU decides to release the DU-side context, the CU sends a UE text release (i.e., UE Context Release Request) message to the DU, and after receiving the UE text release message, the DU releases the corresponding DU-side context (e.g., RLC entities and configurations, physical layer and MAC layer entities and configurations, and F1 interface channels between the CU and the CU).

[0064] Step 6: The CU sends an RRC release message to the UE via the DU to instruct the UE to release to the inactive state. Here, based on the CG resource release instruction or the updated CG resource of the DU included in the message such as UE Context Modification Required received by the CU from the DU, the CU sets the CG resource-related information in the RRC release message, for example, sets the CG resource release instruction or the updated CG resource, and the CU sends an RRC release message to the UE to notify the UE to release or update the CG resource.

[0065] Step 7: The UE receives an RRC release message. If the message contains a CG resource release instruction, the UE releases the corresponding CG resource configuration. If the message contains updated CG resources, the UE stores and updates the corresponding CG resource configuration. [Example]

[0066] 6 is a schematic diagram of an implementation of a further small data transmission method according to an embodiment. As shown in FIG. 6, the specific process of the method may include the following steps:

[0067] Step 1: When the UE's traffic ends, the base station (e.g., gNB) releases the UE to an RRC inactive state (i.e., RRC_INACTIVE) instead of completely releasing the UE's connection. The gNB configures CG resources for small data transmission (i.e., SDT) for the UE, and the DU side of the gNB stores the UE's context (e.g., RLC configuration, etc.), the CU side of the gNB also stores the UE's context (e.g., PDCP configuration, etc.), and the CU and DU store the DRB data transmission channel (i.e., F1-U DRB tunnel).

[0068] Step 2: If the UE is in an RRC inactive state and is ready to perform SDT, but the CG resource does not meet the threshold requirement, for example, the received signal quality corresponding to the CG resource does not meet the threshold requirement, or the RRC recovery request message sent by the CG resource cannot be successfully transmitted to the gNB, the UE prepares to send an RRC recovery request message to the gNB via the RACH channel.

[0069] Step 3: The UE sends an RRC recovery request message (i.e., RRC RESUME REQUEST) to the gNB via the RACH channel. After receiving the RRC recovery request message, the DU of the gNB determines that the UE needs to perform SDT and determines that the type of SDT is RACH SDT. The DU packages the received RRC recovery request message into an initial uplink RRC message (i.e., Initial UL RRC Message) and sends the initial uplink RRC message to the CU. The initial uplink RRC message carries SDT indication information for instructing the CU that the RRC recovery message is for small data transmission, and the initial uplink RRC message carries SDT type information for instructing the CU whether the SDT is RACH SDT or CG SDT.

[0070] Step 4: The CU receives the initial uplink RRC message, and identifies whether the SDT is a RACH SDT or a CG SDT based on the SDT type information carried therein. If the CG resource is configured on the base station side and the SDT type is a RACH SDT, the CU can decide to release the CG resource of the base station or request an update of the CG resource of the base station.

[0071] Step 5: If the CU decides to release the DU-side context simultaneously, the CU sends a UE Context Release Request message (i.e., may also be called a UE context release request message or a UE text release message) to the DU; otherwise, the CU sends a UE Context Modification Request message (i.e., may also be called a UE context update request message or a UE text update message) to the DU, where the message includes a CG resource release instruction to instruct the DU to release the CG resources but suspend the UE context, or a CG resource update instruction to instruct the DU to reallocate and update the CG resources.

[0072] Step 6: If the DU receives a UE Context Release Request message (i.e., a UE context release request), the DU releases the corresponding DU-side context (e.g., RLC entities and configurations, physical layer and MAC layer entities and configurations, and F1 interface channels between the CU).

[0073] When the DU receives a UE Context Modification Request message (i.e., a UE context update request) sent from the CU and the message contains a CG resource release instruction, the DU does not release the DU-side context (i.e., reserves the DU-side UE context, such as RLC entities and configurations, physical layer and MAC layer entities and configurations, and the F1 interface channel between the CU), but releases the DU-side CG resources. After releasing the existing DU-side CG resources, the DU can optionally reallocate new CG resources and send the new CG resources to the CU in a UE context update request feedback message.

[0074] When the DU receives a UE Context Modification Request message (i.e., a UE context update request) sent from the CU and the message contains a CG resource update instruction, the DU reallocates and updates the CG resources and sends the updated CG resources to the CU in a UE context update request feedback message (i.e., also called a UE text update feedback message).

[0075] Step 7: The CU sends an RRC release message to the UE via the DU, instructing the UE to release to an inactive state, where the RRC release message includes a CG resource release indication or the updated CG resource of the DU.

[0076] Step 8: The UE receives an RRC release message. If the RRC release message contains a CG resource release indication, the UE releases the corresponding CG resource configuration. If the RRC release message contains updated CG resources, the UE stores and updates the corresponding CG resource configuration.

[0077] An embodiment of the present application further provides a pointing device. Figure 7 is a structural schematic diagram of a pointing device according to an embodiment. As shown in Figure 7, the pointing device includes: a context determination module 310 configured to determine a context of the terminal; an instruction message sending module 320 configured to send an instruction message to a second communication node, wherein the instruction message includes interface connection information related to the context, the interface connection information including a terminal interface identifier corresponding to the first communication node and a terminal interface identifier corresponding to the second communication node, and the interface connection information is used to instruct the second communication node on an SDT via a stored interface.

[0078] In the instruction device of this embodiment, in order to effectively use resources on the base station side, the first communication node determines the context of the terminal and sends an instruction message to the second communication node, so that the second communication node can perform SDT based on the interface connection information and terminal context related to the context contained in the instruction message.

[0079] In one embodiment, the apparatus comprises: a first RRC message receiving module configured to receive an initial uplink RRC message of a second communication node, wherein the initial uplink RRC message includes an RRC recovery request message, and the RRC recovery request message includes an I-RNTI; a terminal identification module configured to identify the terminal based on an I-RNTI; and an authentication module configured to perform SDT authentication on the terminal.

[0080] In one embodiment, the indication message includes at least one of an SDT authentication success message, a terminal context establishment request message, and a terminal context modification message.

[0081] In one embodiment, the apparatus comprises: a second RRC message receiving module configured to receive an uplink common control channel RRC message of the second communication node carrying signaling data; and a terminal determination module configured to determine a terminal to which the signaling data belongs based on an I-RNTI in the signaling data carried in the uplink common control channel (RRC) message, when the uplink common control channel (RRC) message carries a CCCH message indication or when the uplink common control channel (RRC) message does not carry interface connection information related to the context.

[0082] In one embodiment, the apparatus comprises: an update message receiving module of the second communication node configured to receive a text update message including a CG resource release instruction or an updated CG resource; The device further includes a context control module configured to, when the text update message includes a CG resource release instruction, determine the release or retention of the context of the second communication node side terminal based on the CG resource release instruction.

[0083] In one embodiment, the apparatus comprises: an information setting module configured to set CG resource related information in an RRC release message according to the CG resource release instruction or the updated CG resource; and a release message sending module configured to send an RRC release message to notify the terminal to release or update the CG resource.

[0084] In one embodiment, the apparatus comprises: a third RRC message receiving module configured to receive an initial uplink RRC message of a second communication node carrying SDT type information including a RACH SDT or a CG SDT; The radio access point further includes a CG resource control module configured to release or update the CG resource if the CG resource is allocated and the SDT type is RACH SDT.

[0085] In one embodiment, the apparatus comprises: The terminal further includes an update request sending module configured to send a terminal context update request including a CG resource release instruction or a CG resource update instruction, where the CG resource release instruction is used to instruct the second communication node to release the CG resource and suspend the UE context, and the CG update instruction is used to instruct the DU to reallocate and update the CG resource.

[0086] The indicating device presented in this embodiment belongs to the same inventive idea as the indicating method presented in the above embodiment, and the technical details not explained in detail in this embodiment can be referred to any of the above embodiments, and this embodiment has the same beneficial effects as the implementation of the indicating method.

[0087] An embodiment of the present application further provides a data transmission device. Figure 8 is a structural schematic diagram of a data transmission device according to an embodiment. As shown in Figure 8, the data transmission device includes: an indication message receiving module 410 configured to receive an indication message, the indication message including interface connection information related to a context of a terminal, the interface connection information including a terminal interface identifier corresponding to a first communication node and a terminal interface identifier corresponding to the second communication node; a context and interface determination module 420 configured to determine a context of the terminal and associated stored interfaces based on the interface connection information; and an SDT execution module 430 configured to perform SDT based on the terminal context and the stored interface.

[0088] In the data transmission device of this embodiment, in order to effectively use resources on the base station side, the second communication node can determine the terminal context and the associated stored interface based on the interface connection information in the instruction information by receiving the instruction information from the first communication node, and then perform SDT based on the terminal context and the stored interface.

[0089] In one embodiment, the apparatus comprises: The radio communication device further includes a first RRC message sending module configured to send an initial uplink RRC message, where the initial uplink RRC message includes an RRC recovery request message, and the RRC recovery request message includes an I-RNTI.

[0090] In one embodiment, the indication message includes at least one of an SDT authentication success message, a terminal context establishment request message, and a terminal context modification message.

[0091] In one embodiment, the SDT execution module specifically: The device further includes a transmission unit configured to, when receiving SDT traffic data of the terminal, transmit the SDT traffic data to the first communication node via a DRB data transmission channel corresponding to the terminal based on the stored terminal interface corresponding to the first communication node and the terminal interface corresponding to the second communication node.

[0092] In one embodiment, the apparatus comprises: The terminal further comprises a second RRC message transmitting module configured to transmit an uplink common control channel RRC message carrying the signaling data when receiving the signaling data of the terminal.

[0093] In one embodiment, the uplink common control channel (RRC) message further carries interface connection information related to the CCCH message indication or context.

[0094] In one embodiment, the apparatus comprises: The device further includes an update message sending module configured to send a text update message including a CG resource release instruction or an updated CG resource.

[0095] In one embodiment, the apparatus comprises: The mobile station further includes a third RRC message sending module configured to send an initial uplink RRC message carrying SDT type information including a RACH SDT or a CG SDT.

[0096] In one embodiment, the apparatus comprises: a first update request receiving module configured to receive a terminal context update request including a CG resource release instruction; and a release module configured to release the CG resource and reserve the context of the UE based on the CG resource release instruction.

[0097] In one embodiment, the apparatus comprises: a second update request receiving module configured to receive a terminal context update request including a CG resource update instruction; a CG resource update module configured to reallocate and update the CG resource based on the CG resource update instruction; and a feedback message sending module configured to send a terminal context update request feedback message.

[0098] The data transmission device presented in this embodiment belongs to the same inventive idea as the data transmission method presented in the above embodiments, and the technical details not explained in detail in this embodiment can be referred to any of the above embodiments, and this embodiment has the same beneficial effects as the implementation of the data transmission method.

[0099] An embodiment of the present application further provides a communication node, which may be a first communication node or a second communication node. Figure 9 is a schematic diagram of the hardware structure of a communication node according to an embodiment. As shown in Figure 9, the communication node according to the present application includes a memory 520, a processor 510, and a computer program stored in the memory and executable by the processor. When the processor 510 executes the program, the above-mentioned instruction method or data transmission method is realized.

[0100] The communication node may further include a memory 520, and the processor 510 in the communication node may be one or more. In FIG. 9, one processor 510 is taken as an example, and the memory 520 is used to store one or more programs. When the one or more programs are executed by the one or more processors 510, the one or more processors 510 realize the instruction method or data transmission method described in the embodiments of the present application.

[0101] The communication node further includes a communication device 530 , an input device 540 and an output device 550 .

[0102] The processor 510, memory 520, communication device 530, input device 540 and output device 550 in the communication node can be connected via a bus or other methods, and in FIG. 9, they are connected via a bus as an example.

[0103] The input device 540 can be used to receive input numeric or textual information and generate key signal inputs related to user settings and function control of the communication node. The output device 550 may include a display device such as a display.

[0104] The communication device 530 may include a receiver and a transmitter and is configured to transmit and receive information under the control of the processor 510.

[0105] The memory 520 can be used as a computer-readable storage medium to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the instruction method according to an embodiment of the present application (e.g., the context determination module 310 and the instruction message sending module 320 in the instruction device) or program instructions / modules corresponding to the data transmission method according to an embodiment of the present application (e.g., the instruction message receiving module 410, the context and interface determination module 420, and the SDT execution module 430 in the data transmission device). The memory 520 may include a program storage area and a data storage area, where the program storage area can store an operating system and / or application programs required for at least one function, and the data storage area can store data generated based on the use of the communication node, etc. The memory 520 may also include high-speed random access memory and may further include non-volatile memory, such as at least one magnetic disk storage device, flash memory, or other non-volatile solid-state storage device. In some embodiments, the memory 520 can include memory located remotely from the processor 510, and these remote memories can be connected to the device via a network. Examples of such networks may include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0106] An embodiment of the present application further provides a storage medium having a computer program stored thereon, which, when executed by a processor, realizes any of the instruction methods or data transmission methods of the embodiments of the present application. The instruction method includes: determining a context of a terminal; and sending an instruction message to a second communication node, the instruction message including interface connection information related to the context, the interface connection information including a terminal interface identifier corresponding to the first communication node and a terminal interface identifier corresponding to the second communication node, the interface connection information being used to instruct the second communication node to perform SDT via stored interfaces. The data transmission method includes receiving an instruction message, the instruction message including interface connection information related to the context of the terminal, the interface connection information including a terminal interface identifier corresponding to the first communication node and a terminal interface identifier corresponding to the second communication node; determining the terminal context and the associated stored interfaces based on the interface connection information; and performing SDT based on the terminal context and the stored interfaces.

[0107] The computer storage medium of the present application may be any combination of one or more computer-readable media. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium may be, for example, but not limited to, an electric, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. Further specific examples (a non-exhaustive list) of computer-readable storage media may include, but are not limited to, an electrical connection having one or more leads, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. The computer-readable storage medium may be any tangible medium that contains or stores a program that can be used in or in connection with an instruction execution system, apparatus, or device.

[0108] A computer-readable signal medium may include a propagated data signal, either in baseband or as part of a carrier wave, having computer-readable program code carried therein. Such a propagated data signal may take various forms, including, but not limited to, an electromagnetic signal, an optical signal, or any suitable combination of the above. A computer-readable signal medium may be any computer-readable medium other than a computer-readable storage medium, which is capable of transmitting, propagating, or transporting a program for use in or in connection with an instruction execution system, apparatus, or device.

[0109] The program code contained in the computer readable medium may be transmitted over any suitable medium, including, but not limited to, electrical wire, optical cable, radio frequency (RF), etc., or any suitable combination of the above.

[0110] Computer program code for carrying out the operations of the present application can be written in one or more programming languages, or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may run entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. When referring to a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., connected via the Internet using an Internet traffic provider).

[0111] The above are only illustrative examples of the present application, and are not intended to limit the protection scope of the present application.

[0112] Those skilled in the art will appreciate that the term user terminal includes any suitable type of wireless user equipment, including, for example, a mobile phone, a portable data processing device, a portable network browser, or a mobile station mounted on a vehicle.

[0113] In general, various embodiments of the present application may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware while other aspects may be implemented in firmware or software executable by a controller, microprocessor, or other computing device, and the present application is not limited thereto.

[0114] Embodiments of the present application may be implemented by execution of computer program instructions by a data processor of a mobile device, for example in a processor entity, by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or target code written in any combination of one or more programming languages.

[0115] Any logic flow block diagrams in the figures herein may represent program steps, interconnected logic circuits, modules, and functions, or combinations of program steps and logic circuits, modules, and functions. Computer programs may be stored in memory. The memory may be of any type suitable for the local technology environment and may be implemented with any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Versatile Disc (DVD) or Compact Disc (CD)), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable for the local technology environment, such as, but not limited to, a general purpose computer, a special purpose computer, a microprocessor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), and a processor based on a multi-core processor architecture.

Claims

1. An indication method applied to a centralized unit CU of a base station, comprising: receiving an initial uplink radio resource control (RRC) message associated with a terminal from a distributed unit (DU) of the base station, the initial uplink radio resource control (RRC) message including SDT indication information for indicating small data (SDT) and an RRC recovery request message transmitted from the terminal via a random access channel (RACH); determining a context of the terminal; Sending an instruction message to the DU, the instruction message including interface connection information related to the context, the interface connection information including a terminal interface identifier corresponding to the CU and a terminal interface identifier corresponding to the DU, the interface connection information being used to instruct the DU to perform small data transmission (SDT) via a stored interface, and the stored interface being a data radio bearer (DRB) data transmission channel associated with the terminal. Instruction method.

2. The instruction message is At least one of an SDT authentication success message, a terminal context establishment request message, and a terminal context modification message is included; The method of claim 1.

3. receiving a context update message including a config-advance grant CG resource release instruction or updated CG resources of the DU; If the context update message includes the CG resource release instruction, determining whether to release or retain the context of the DU side terminal based on the CG resource release instruction. The method of claim 1.

4. Setting CG resource related information in an RRC release message based on the CG resource release instruction or the updated CG resource; and sending the RRC release message to notify the terminal to release or update CG resources. The method of claim 3.

5. Further comprising: sending a terminal context update request including a CG resource release instruction or a CG resource update instruction; The CG resource release indication is used to instruct the DU to release CG resources and reserve the context of the terminal; The CG resource update instruction is used to instruct the DU to reallocate and update CG resources; The method of claim 1.

6. receiving SDT transmission data from the DU via the stored interface, the SDT transmission data being transmitted from a terminal to the DU via a RACH; The method of claim 1.

7. A data transmission method applied to a distributed unit (DU) of a base station, comprising: receiving a radio resource control (RRC) recovery request message from a terminal via a random access channel (RACH); Send an initial uplink RRC message associated with the terminal to a centralized unit (CU) of the base station, where the initial uplink RRC message includes SDT indication information for indicating small data SDT and the received RRC recovery request message; receiving an indication message from the CU, the indication message including interface connection information related to a context of the terminal, the interface connection information including a terminal interface identifier corresponding to the CU and a terminal interface identifier corresponding to the DU; determining a context of the terminal and associated stored interfaces based on the interface connection information; and transmitting small data transmission (SDT) traffic data of the terminal to the CU via the stored interface based on the context of the terminal, the stored interface being a data radio bearer (DRB) data transmission channel associated with the terminal. Data transmission method.

8. The instruction message is At least one of an SDT authentication success message, a terminal context establishment request message, and a terminal context modification message is included; The method of claim 7.

9. transmitting SDT traffic data of the terminal to the CU via the stored interface based on the context of the terminal; When SDT traffic data of the terminal is received via the RACH, transmitting the SDT traffic data to the CU via the stored interface. The method of claim 7.

10. When the signaling data of the terminal is received, the method further includes transmitting an uplink common control channel RRC message carrying the signaling data. The method of claim 7.

11. The uplink common control channel RRC message further carries a common control channel CCCH message indication or interface connection information related to the context. The method of claim 10.

12. Further comprising sending a context update message including a config-advance grant CG resource release instruction or an updated CG resource; The method of claim 7.

13. receiving a terminal context update request including a CG resource release instruction; and releasing a CG resource based on the CG resource release instruction to reserve the context of the terminal. The method of claim 7.

14. A communications node including a memory, a processor, and a computer program stored in the memory and executable by the processor, When the processor executes the program, the instruction method according to any one of claims 1 to 6 or the data transmission method according to any one of claims 7 to 13 is realized. Base station.

15. A computer-readable storage medium having a computer program stored thereon, When the computer program is executed by a processor, it implements the instruction method according to any one of claims 1 to 6 or the data transmission method according to any one of claims 7 to 13. A computer-readable storage medium.

Images