Instruction method, data transmission method, communication node, and storage medium
By determining and aligning the UE context with appropriate communication nodes through interface connection information, the method optimizes resource utilization in wireless communication systems, addressing inefficiencies in CG resource allocation for SDT.
Patent Information
- Application Number
- JP2024526750
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-12-24
- Filing Date
- 2022-11-24
- Publication Date
- 2024-11-06
- Estimated Expiration
- 2042-11-24
AI Technical Summary
In wireless communication systems, the allocation of configured grants (CG) for small data transmission (SDT) in the RRC_INACTIVE state leads to resource wastage when UEs use RACH resources instead of CG resources due to potential poor signal quality, resulting in inefficient use of base station resources.
A method and device that determine the context of a terminal and transmit an instruction message to a second communication node, including interface connection information to facilitate Small Data Transmission (SDT) using stored interfaces, optimizing resource utilization by aligning the UE context with appropriate communication nodes.
Enhances resource efficiency by enabling effective SDT based on terminal context and stored interfaces, reducing signaling overhead and improving resource utilization in wireless communication networks.
Smart Images

Figure 2024541064000001_ABST
Abstract
Description
[Technical field]
[0001] The present application relates to the technical field of wireless communication networks, for example to an indication 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., 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, and the CU and the DU are connected via an interface. In addition, a terminal (User Equipment, UE) in a Radio Resource Control (RRC) inactive state (RRC_INACTIVE) is assigned a specifically scheduled (Configured Grant, CG) resource for small data transmission (Small Data Transmission, SDT) transmission. However, when 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, which wastes 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 embodiment of the present application is An instruction method applied to a first communication node, comprising: 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 of an SDT by a stored interface. Provide a method of instruction.
[0005] The embodiment of the present application is A data transmission method applied to a second communication node, comprising: receiving an indication message, the indication 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; determining the terminal context and a related stored interface based on the interface connection information; and performing SDT based on the terminal context and the stored interface; A data transmission method is also provided.
[0006] The embodiment of the present application is A communication node including a memory, a processor, and a computer program stored in the memory and executable by the processor, the program being executed by the processor to realize the instruction method or the data transmission method. A communication node is further provided.
[0007] The embodiment of the present application 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 description of the drawings]
[0008] [Figure 1] 1 is a flowchart of an instruction method according to an embodiment. [Diagram 2] 4 is a flowchart of a data transmission method according to an embodiment. [Diagram 3] FIG. 2 is a schematic diagram illustrating an implementation of a small data transmission method according to an embodiment. [Figure 4] 1 is a schematic diagram illustrating another small data transmission method according to an embodiment. FIG. [Diagram 5] 1 is a schematic diagram illustrating a further small data transmission method according to an embodiment; [Figure 6] 1 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 indication 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 of the hardware structure of a communication node according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[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 do not limit the present application. For the sake of convenience, the drawings show only parts related to the present application, not all 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 transmits 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 RAN because the UE needs to frequently reestablish the signaling link with the radio network (RAN).
[0011] In the case of Fourth Generation (4G), in order to optimize support for infrequent small data packet transmission, the 4G network supports that the UE can transmit corresponding small data to the RAN 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 data amounts of data without frequently reestablishing a signaling link with the network.
[0012] The RRC state of 4G Long Term Evolution (LTE) may include two types: RRC_IDLE (i.e., RRC idle state) and RRC_CONNECTED (i.e., RRC connected state), and RRC_INACTIVE (i.e., RRC inactive state) is introduced in 5G. 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 side also reserves the UE context (i.e., UE Context), so that the UE can quickly transition from the RRC INACTIVE state to the RRC CONNECTED state to transmit data when there is data transmission. This can reduce signaling overhead, provide quick access, reduce delay, and save more power.
[0013] However, in the case of 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. Small data transmission (i.e., SDT) in 5G includes SDT based on RACH and SDT based on CG resources. If the 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, but 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 the 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 a CG resource for transmitting small data to a UE in RRC_INACTIVE, but the UE transmits small data using a RACH resource, the DU cannot transmit small data using the UE context stored when generating the CG configuration resource, which wastes 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, and 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, the instruction message includes interface connection information related to the context, the interface connection information includes 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 of an SDT via the stored interface.
[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, and the indication message may include interface connection information related to the 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, and the interface connection information can be used to make the second communication node indicate the SDT by the stored interface. The stored interface may include an interface stored based on the context of the terminal, specifically, the UE F1 interface on the CU side and the 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 of 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 a 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 including a Configured Grant (CG) resource release instruction or updated CG resources from a second communication node, 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 a second communication node carrying SDT type information including a RACH SDT or a CG SDT; and releasing or updating the CG resource if a CG resource is configured and the SDT type is a RACH SDT.
[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] The embodiment of the present application further provides a data transmission method. Figure 2 is a flowchart of a data transmission method according to an embodiment, as shown in Figure 2, the method can be applied to a second communication node, the second communication node can be a DU, and the method according to this embodiment includes steps 210, 220 and 230.
[0028] In step 210, an indication message is received, the indication 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, a context of the terminal and associated stored interfaces are determined based on the interface connection information.
[0030] In step 230, SDT is performed based on the terminal's context and the stored interfaces.
[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 the context of the terminal, and 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 the associated stored interface based on the interface connection information related to the context of the terminal in the indication message, where the stored interface may include an interface stored based on the context of the terminal, specifically, may include a UE F1 interface on the CU side and a UE F1 interface on the DU side. Finally, the second communication node can perform SDT based on the context of the terminal and the stored interface.
[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 of 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, the initial uplink RRC message including an RRC recovery request message, and the RRC recovery request message including the 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 of 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 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 sending 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 provides an illustrative description of a 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. EXAMPLES
[0043] 3 is a schematic diagram of an implementation of a small data transmission method according to an embodiment. As shown in FIG. 3, a specific process of the method may include the following steps:
[0044] Step 1: When the traffic of the terminal (i.e., UE) is terminated, 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., Radio Link Control, RLC configuration, etc.), the CU side of the gNB also stores the UE's context (e.g., Packet Data Convergence Protocol, PDCP configuration, etc.), and the CU and DU store the data transmission channel of the DRB (i.e., F1-U DRB tunnel).
[0045] Step 2: When the UE is in an RRC inactive state and is ready to perform SDT, but the CG resource does not meet, for example, the received signal quality corresponding to the CG resource does not meet a threshold requirement, or the RRC recovery request message sent by the CG resource cannot be successfully transmitted to the gNB, the UE may prepare to send an RRC recovery request message to the gNB via a RACH channel.
[0046] Step 3: The UE sends an RRC recovery request message (i.e., RRC RESUME REQUEST) to the gNB via a RACH channel, and after receiving the RRC recovery request message, the DU of the gNB identifies that the UE needs to perform small data transmission, and 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 RRC recovery request message of the DU 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 UE context on the CU side (i.e., UE Context) and connection information of the F1 interface related to the UE context, where the connection information may include a terminal F1 interface identifier (ID) corresponding to the CU and a terminal F1 interface ID corresponding to the DU (i.e., determine the UE F1 interface ID on the CU side and the UE F1 interface ID on the DU side related to the UE context), where the UE F1 interface ID on the CU side can be expressed as CU UE F1AP ID, the UE F1 interface ID on the DU side can be expressed as DU UE F1AP ID, and F1AP can mean F1 interface.
[0048] Step 5: The CU sends an indication message to the DU, such as an SDT authentication success message (i.e., SDT Authentication Message), in which the UE F1 interface ID on the CU side and the UE F1 interface ID on the DU side related to the context of the UE are included. After receiving the message, the DU determines the context of the UE on the DU side by (CU UE F1AP ID, DU UE F1AP ID), and determines the connection of the F1 interface related to the context of the UE. Note that the indication message sent from the CU to the DU is not limited to the SDT authentication success message, and the CU can also carry (CU UE F1AP ID, DU UE F1AP ID) in the UE context establishment request message / modification message (i.e., UE CONTEXT SETUP / MODIFICATION REQUEST) to notify the DU to determine the context of the UE, that is, the indication message sent from the CU to the DU includes at least one of the SDT authentication success message, the terminal context establishment request message, and the terminal context modification message.
[0049] Step 6: In the subsequent small data transmission process, the UE sends DRB data (ie, SDT traffic data of the terminal) to the DU through the resource scheduled by the RACH or the resource scheduled by the CG, and after the DU receives the DRB data, the DU transmits the DRB data to the CU through the DRB data transmission channel corresponding to the UE in the F1 interface according to the connection of the F1 interface related to the context of the UE (ie, the terminal interface corresponding to the stored CU and the terminal interface corresponding to the DU). After the CU receives the DRB data, the CU transmits the DRB data to the 5G core network (ie, 5GC). EXAMPLES
[0050] 4 is a schematic diagram of another small data transmission method according to an embodiment. As shown in FIG. 4, a specific process of the method may include the following steps:
[0051] Step 1: When the traffic of the terminal (i.e., UE) is terminated, 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) in 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 (PDCP configuration, etc.), and the CU and DU store the data transmission channel of the DRB (i.e., F1-U DRB tunnel).
[0052] Step 2: When the UE is in an RRC inactive state and is ready to perform SDT, but the CG resource does not meet, for example, the received signal quality corresponding to the CG resource does not meet a threshold requirement, or the RRC recovery request message sent by the CG resource cannot be successfully transmitted to the gNB, the UE may prepare to send an RRC recovery request message to the gNB via a RACH channel.
[0053] Step 3: The UE sends an RRC recovery request message (i.e., RRC RESUME REQUEST) to the gNB via a RACH channel, and after receiving the RRC recovery request message, the DU of the gNB identifies that the UE needs to perform small data transmission, and 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 RRC recovery request message of the DU 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 UE context on the CU side (i.e., UE context) and connection information of the F1 interface related to the UE context, where the connection information may include a terminal F1 interface identifier (ID) corresponding to the CU and a terminal F1 interface ID corresponding to the DU (i.e., determine the UE F1 interface ID on the CU side and the UE F1 interface ID on the DU side related to the UE context), where the UE F1 interface ID on the CU side can be expressed as CU UE F1AP ID, the UE F1 interface ID on the DU side can be expressed as DU UE F1AP ID, and F1AP can mean F1 interface.
[0055] Step 5: The CU sends an indication message to the DU, such as an SDT authentication success message (i.e., SDT Authentication Message), in which the UE F1 interface ID on the CU side and the UE F1 interface ID on the DU side related to the context of the UE are included. After receiving the message, the DU determines the context of the UE on the DU side by (CU UE F1AP ID, DU UE F1AP ID), and determines the connection of the F1 interface related to the context of the UE. Note that the indication message sent from the CU to the DU is not limited to the SDT authentication success message, and the CU can also carry (CU UE F1AP ID, DU UE F1AP ID) in the UE context establishment request message / modification message (i.e., UE CONTEXT SETUP / MODIFICATION REQUEST) to notify the DU to determine the context of the UE, that is, the indication message sent from the CU to the DU includes at least one of the SDT authentication success message, the terminal context establishment request message, and the terminal context modification message.
[0056] Step 6: The UE sends subsequent signaling data by corresponding Dedicated Control Channel (DCCH) resources scheduled by RACH or scheduled by CG, for example, sends Signaling Radio Bearers (SRB) Protocol Data Unit (PDU) or Non Access Stratum (NAS) PDU to the DU, and the DU can identify which UE the signaling data is for according to the resources scheduled for different UEs. The DU carries and sends the signaling data (i.e., SRB PDU or NAS PDU) to the CU by 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 related to the context of the UE to indicate to the CU which UE the signaling data belongs to.
[0057] Step 7: The UE sends 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 I-RNTI of the UE in the signaling data. Because of the CCCH common channel, the DU cannot identify which UE the signaling data is for at this time, and the DU carries and sends the signaling data (i.e., SRB PDU or NAS PDU) 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 indicate to the CU that the signaling data carried in the message is CCCH channel signaling. After receiving a 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 context of the UE (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. EXAMPLES
[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, a 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) CG resources for some reason, such as the validity timer of the CG resources 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 (ie, UE Context Modification Required) to the CU, where the UE text update message includes a CG resource release indication or an updated CG resource (but is not limited to this UE text update message).
[0062] Step 4: When the CU receives the UE Context Modification Required message, which contains 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 (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).
[0064] Step 6: The CU sends an RRC release message to the UE through 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 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 notifies the UE to send or update the CG resource by sending an RRC release message to the UE.
[0065] Step 7: The UE receives an RRC release message, and if the message contains a CG resource release instruction, the UE releases the corresponding CG resource configuration, and if the message contains an updated CG resource, the UE stores and updates the corresponding CG resource configuration. EXAMPLES
[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, a 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) in 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's 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, for example, the received signal quality corresponding to the CG resource does not meet a 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 a RACH channel.
[0069] Step 3: The UE sends an RRC recovery request message (i.e., RRC RESUME REQUEST) to the gNB via a RACH channel, and the DU of the gNB identifies that the UE needs to perform SDT after receiving the RRC recovery request message, and identifies that the type of the 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, where the initial uplink RRC message carries SDT indication information for instructing the CU that the RRC recovery message is for small data transmission, and where 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 according to 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 context on the DU side at the same time, the CU sends a UE Context Release Request message (i.e., may 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 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 the F1 interface channel 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 indication, the DU does not release the context on the DU side (i.e., reserves the UE context on the DU side, such as RLC entities and configurations, physical layer and MAC layer entities and configurations, and F1 interface channel between the CU), but releases the CG resources on the DU side. And after the DU releases the existing CG resources on the DU side, 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 an updated CG resource of the DU.
[0076] Step 8: The UE receives an RRC release message, and if the RRC release message includes a CG resource release instruction, the UE releases the corresponding CG resource configuration, and if the RRC release message includes an updated CG resource, the UE stores and updates the corresponding CG resource configuration.
[0077] The embodiment of the present application further provides a pointing device. FIG. 7 is a structural schematic diagram of a pointing device according to an embodiment. As shown in FIG. 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, 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 of 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, where 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 a 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 a CCCH message indication is carried in the uplink common control channel (RRC) message or when the uplink common control channel (RRC) message does not carry interface connection information related to a context.
[0082] In one embodiment, the apparatus comprises: an update message receiving module configured to receive a text update message including a CG resource release instruction or an updated CG resource of a second communication node; and a context control module configured to determine, when the text update message includes a CG resource release instruction, to release or hold 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 a CG resource release indication or an 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; and a CG resource control module configured to release or update the CG resource if the CG resource is configured and the SDT type is RACH SDT.
[0085] In one embodiment, the apparatus comprises: The terminal context update request sending module 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 embodiments, and the technical details not described in detail in this embodiment may refer 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 an 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 of 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 includes: The terminal 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 includes a second RRC message sending module configured to send 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 comprises 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; The device further comprises a release module configured to release the CG resource and reserve a 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 described in detail in this embodiment may refer 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. FIG. 9 is a schematic diagram of the hardware structure of a communication node according to an embodiment. As shown in FIG. 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 in another manner, 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 associated with user settings and function control of the communication node. The output device 550 can 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 indication method according to the embodiment of the present application (e.g., the context determination module 310 and the indication message sending module 320 in the indication device), or program instructions / modules corresponding to the data transmission method according to the embodiment of the present application (e.g., the indication 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, an application program 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 a high-speed random access memory, and may further include a 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 memories provided remotely to 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 indication methods or data transmission methods of the embodiments of the present application. The indication method includes: determining a context of a terminal; sending an indication message to a second communication node, the indication 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 being used to cause the second communication node to indicate SDT by a stored interface. The data transmission method includes: receiving 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 the first communication node and a terminal interface identifier corresponding to the second communication node; determining the context of the terminal and the associated stored interface based on the interface connection information; and performing SDT based on the context of the terminal and the stored interface.
[0107] The computer storage medium of the embodiments of the present application may employ 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 (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 by or in connection with an instruction execution system, apparatus or device.
[0108] A computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with computer-readable program code carried therein. Such a propagated data signal may take a variety of 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 may transmit, propagate, or transport 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), or the like, or any suitable combination of the above.
[0110] Computer program code for carrying out the operations of the present application may be written in one or more programming languages or combinations thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and even conventional procedural programming languages such as "C" or similar. The program code may be executed entirely on the user's computer, partially on the user's computer, as a single independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of 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 embodiments of the present application, and are not intended to limit the protection scope of the present application.
[0112] It should be appreciated by those skilled in the art 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 and 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 of this application may represent program steps, interconnected logic circuits, modules, and functions, or combinations of program steps and logic circuits, modules, and functions. The computer program may be stored in a memory. The memory may have any type suitable for the local technology environment and may be implemented with any suitable data storage technology, such as, but not limited to, a Read-Only Memory (ROM), a Random Access Memory (RAM), an optical storage device and system (Digital Video Disc (DVD) or Compact Disc (CD)). The computer readable medium may include a non-transitory storage medium. 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 first communication node, comprising: Determining the context of the terminal; 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 small data transmission (SDT) via a stored interface; Instruction method.
2. receiving an initial uplink radio resource control (RRC) message of the 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 identifier (I-RNTI); Identifying the terminal based on the I-RNTI; and performing SDT authentication on the terminal. The method of claim 1.
3. 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; The method of claim 1.
4. receiving an uplink common control channel RRC message of the second communication node carrying signaling data; 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 the 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. The method of claim 1.
5. Receiving a text update message including a config-advance grant CG resource release instruction or an updated CG resource from the second communication node; If the text update message includes the CG resource release instruction, determining whether to release or hold the context of the second communication node side terminal based on the CG resource release instruction. The method of claim 1.
6. 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 a CG resource. The method according to claim 5.
7. Receiving an initial uplink RRC message of the second communication node carrying SDT type information including a random access channel (RACH) SDT or a CG SDT; If a CG resource is configured and the SDT type is a RACH SDT, releasing or updating the CG resource. The method of claim 1.
8. The method further includes sending a terminal context update request including a CG resource release instruction or a CG resource update instruction; The CG resource release instruction is used to instruct a second communication node to release a CG resource and reserve a context of the terminal; The CG resource update instruction is used to instruct the second communication node to reallocate and update CG resources. The method of claim 1.
9. A data transmission method applied to a second communication node, comprising: receiving an indication message, the indication message including interface connection information associated with 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; determining a context of the terminal and associated stored interfaces based on the interface connection information; and performing a small data transmission (SDT) based on the context of the terminal and the stored interface. Data transmission method.
10. sending an initial uplink radio resource control (RRC) message, the initial uplink RRC message including an RRC recovery request message, the RRC recovery request message including an inactive radio network temporary identifier (I-RNTI) included in the RRC recovery request message; 10. The method of claim 9.
11. 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; 10. The method of claim 9.
12. Performing SDT based on the context of the terminal and the stored interface, When receiving SDT traffic data of the terminal, transmitting the SDT traffic data to the first communication node through 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 terminal interface corresponding to the second communication node.
10. The method of claim 9.
13. When the signaling data of the terminal is received, the signaling data is transmitted via an uplink common control channel (RRC) message carrying the uplink common control channel (RRC) message.
10. The method of claim 9.
14. 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 13.
15. The method further includes sending a text update message including a config-advance grant CG resource release instruction or an updated CG resource; 10. The method of claim 9.
16. The method further includes transmitting an initial uplink RRC message carrying SDT type information including a random access channel RACH SDT or a CG SDT; 10. The method of claim 9.
17. Receiving a terminal context update request including a CG resource release instruction; and releasing the CG resource based on the CG resource release instruction to reserve the context of the terminal.
10. The method of claim 9.
18. Receiving a terminal context update request including a CG resource update instruction; reallocating and updating CG resources based on the CG resource update instruction; sending a terminal context update request feedback message; 10. The method of claim 9.
19. 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 8 or the data transmission method according to any one of claims 9 to 18 is realized. Communication node.
20. A computer-readable storage medium having a computer program stored thereon, The computer program, when executed by a processor, implements the instruction method according to any one of claims 1 to 8 or the data transmission method according to any one of claims 9 to 18. A computer-readable storage medium.
Citation Information
Patent Citations
Method, apparatus and system for UE inactivity state
JP2021503749A
