WO2023116336A1 - 指示方法、数据传输方法、通信节点及存储介质 - Google Patents

指示方法、数据传输方法、通信节点及存储介质 Download PDF

Info

Publication number
WO2023116336A1
WO2023116336A1 PCT/CN2022/134052 CN2022134052W WO2023116336A1 WO 2023116336 A1 WO2023116336 A1 WO 2023116336A1 CN 2022134052 W CN2022134052 W CN 2022134052W WO 2023116336 A1 WO2023116336 A1 WO 2023116336A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
terminal
context
communication node
resource
Prior art date
Application number
PCT/CN2022/134052
Other languages
English (en)
French (fr)
Inventor
刘壮
马子江
高音
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to KR1020247012051A priority Critical patent/KR20240053075A/ko
Publication of WO2023116336A1 publication Critical patent/WO2023116336A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • 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.
  • a base station (such as gNB) can be separated into a centralized unit (Centralized Unit, CU) and a distributed unit (Distributed Unit, DU).
  • a base station can contain one CU and multiple DUs. Between CU and DU Connect via interface.
  • a dedicated scheduling (Configured Grant, CG) resource is allocated for the terminal (User Equipment, UE) in the Radio Resource Control (Radio Resource Control, RRC) inactive state (RRC_INACTIVE) for small data (Small Data Transmission, SDT) ) transmission, but if the UE uses Random Access Channel (RACH) resources for SDT transmission, the DU cannot use the UE context saved when generating CG configuration resources for small data transmission, which wastes resources on the base station side.
  • CG Configured Grant
  • the present application provides an indication method, a data transmission method, a communication node and a storage medium.
  • An embodiment of the present application provides an indication method, which is applied to a first communication node, including: determining a context of a terminal; sending an indication message to a second communication node, where the indication message includes interface connection information associated with the context, and the 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 to use the saved interface to perform SDT.
  • the embodiment of the present application also provides a data transmission method applied to a second communication node, including: receiving an indication message, the indication message includes interface connection information associated with the context of the terminal, and the interface connection information includes the first communication
  • the terminal interface identifier corresponding to the node and the first terminal interface identifier of the second communication node determine the context of the terminal and the associated saved interface according to the interface connection information; determine the context of the terminal and the saved interface according to the context of the terminal and the saved interface interface for SDT.
  • the embodiment of the present application also provides a communication node, including: a memory, a processor, and a computer program stored in the memory and operable on the processor.
  • a communication node including: a memory, a processor, and a computer program stored in the memory and operable on the processor.
  • the processor executes the program, it realizes the above-mentioned indicating method or data transfer method.
  • the embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the above-mentioned instruction method or data transmission method is realized.
  • Fig. 1 is a flow chart of an indication method provided by an embodiment
  • FIG. 2 is a flowchart of a data transmission method provided by an embodiment
  • FIG. 3 is a schematic diagram of an implementation of a small data transmission method provided by an embodiment
  • FIG. 4 is a schematic diagram of another small data transmission method provided by an embodiment
  • FIG. 5 is a schematic diagram of another small data transmission method provided by an embodiment
  • FIG. 6 is a schematic diagram of another small data transmission method provided by an embodiment
  • Fig. 7 is a schematic structural diagram of an indicating device provided by an embodiment
  • FIG. 8 is a schematic structural diagram of a data transmission device provided by an embodiment
  • Fig. 9 is a schematic diagram of a hardware structure of a communication node provided by an embodiment.
  • the 4G network supports when the UE accesses the random access channel (Random Access Channel, RACH), the UE
  • RACH Random Access Channel
  • the corresponding small data may be carried in the RACH access request message or the radio resource control (Radio Resource Control, RRC) connection establishment request message and transmitted to the RAN.
  • RRC Radio Resource Control
  • the RRC state of 4G Long Term Evolution can include two types: RRC_IDLE (that is, RRC idle state) and RRC_CONNECTED (that is, RRC connected state), and 5G introduces RRC_INACTIVE (that is, RRC inactive state).
  • RRC INACTIVE the UE is in a power-saving sleep state, but the UE still retains the RAN context, and the RAN side also retains the UE context (ie UE Context), so that the UE can quickly switch from the RRC INACTIVE state when there is data transmission Transition to RRC CONNECTED state and perform data transmission. This can reduce signaling overhead, enable fast access, reduce latency, and save power.
  • 5G also supports the UE to maintain the RRC_INACTIVE state without entering the RRC_CONNECTED state, and perform data transmission with the RAN.
  • 5G small data transmission (that is, SDT) includes RACH-based SDT and CG resource-based SDT.
  • SDT small data transmission
  • CG resources in the RRC_INACTIVE state are configured for the UE, the UE can use the CG resources for small data transmission in RRC_INACTIVE, but the signal quality of the CG resources of the UE may not be very good. In this case, even if the UE is configured In the case of CG resources, it is also possible to use the RACH access process to transmit small data in the RRC_INACTIVE state.
  • a 5G base station (such as gNB), it can be separated into CU and DU.
  • a gNB can contain one CU and multiple DUs, and CUs and DUs are connected through interfaces.
  • the gNB allocates CG resources for RRC_INACTIVE UEs for small data transmission, but at this time, if the UE uses RACH resources for small data transmission, the DU cannot use the UE context saved when generating CG configuration resources for small data transmission, resulting in Resources on the base station side are wasted.
  • FIG. 1 is a flow chart of an indication method provided by an embodiment. As shown in FIG. 1, the method can be applied to a first communication node, and the first communication node may be a CU. The method provided in this embodiment includes steps 110 and Step 120.
  • step 110 the context of the terminal is determined.
  • an indication message is sent to the second communication node, the indication message includes interface connection information associated with the context, and the interface connection information includes the terminal interface identifier corresponding to the first communication node and the second The 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 saved interface to perform SDT.
  • the first communication node determines the context of the terminal, and then sends an indication message to the second communication node.
  • the second communication node may be a DU
  • the indication message may include context-associated interface connection information
  • 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, the interface connection
  • the information may be used to instruct the second communication node to use the saved interface for SDT.
  • the saved interface may include an interface saved according to the context of the terminal, and may specifically include a UE F1 interface on the CU side and a UE F1 interface on the DU side.
  • the first communication node determines the context of the terminal, and sends an indication message to the second communication node, enabling the second communication node to perform SDT according to the interface connection information and the terminal context associated with the context contained in the indication message, In order to effectively utilize resources on the base station side.
  • the method further includes: receiving an initial uplink RRC message of the second communication node, the initial uplink RRC message includes an RRC recovery request message, and the RRC recovery request message includes an inactive radio network temporary identifier (Inactive Radio Network Tempory Identity, I-RNTI); identify the terminal according to the I-RNTI; perform SDT authentication on the terminal.
  • I-RNTI Inactive Radio Network Tempory Identity
  • the indication message includes at least one of the following: SDT authentication pass message; terminal context establishment request message; terminal context modification message.
  • the method further includes: receiving an uplink common control channel RRC message of the second communication node, where the uplink common control channel RRC message carries signaling data; if the uplink common control channel RRC message carries a common control channel (Common Control Channel , CCCH) message indication, or if the uplink common control channel RRC message does not carry context-associated interface connection information, then determine the terminal to which the signaling data belongs according to the I-RNTI in the signaling data carried by the uplink common control channel RRC message .
  • CCCH Common Control Channel
  • the method further includes: receiving a text update message from the second communication node, where the text update message includes a configuration authorization (Configured Grant, CG) resource release indication or an updated CG resource; if the text update message includes a CG resource release indication, it is determined according to the CG resource release indication that the context of the terminal at the second communication node side is released or maintained.
  • a configuration authorization Configured Grant, CG
  • the method further includes: according to the CG resource release indication or the updated CG resource, setting the CG resource related information in the RRC release message; sending the RRC release message, the RRC release message is used to notify the terminal to release the CG resource or Update CG resources.
  • the method further includes: receiving an initial uplink RRC message of the second communication node, the initial uplink RRC message carries SDT type information, and the SDT type includes RACH SDT or CG SDT; if CG resources have been configured, and the SDT type For RACH SDT, release or update CG resources.
  • the method further includes: sending a terminal context update request, where the terminal context update request includes a CG resource release indication or a CG resource update indication; wherein the CG resource release indication is used to instruct the second communication node to release the CG resource and The UE context is reserved; the CG resource update indication is used to instruct the DU to reallocate and update the CG resource.
  • FIG. 2 is a flowchart of a data transmission method provided by 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, the method provided by this embodiment includes step 210 , step 220 and step 230.
  • an indication message is received, the indication message includes interface connection information associated with the context of the terminal, and the interface connection information includes the terminal interface identifier corresponding to the first communication node and the terminal interface corresponding to the second communication node logo.
  • step 220 the context of the terminal and the associated saved interface are determined according to the interface connection information.
  • step 230 SDT is performed according to the context of the terminal and the saved interface.
  • the second communication node receives the indication message sent by the first communication node, where the indication message may include interface connection information associated with the context of the terminal, and the interface connection information may include the terminal corresponding to the first communication node The interface identifier and the terminal interface identifier corresponding to the second communication node. Then, the second communication node may determine the context of the terminal and the associated saved interface according to the interface connection information associated with the context of the terminal in the indication message; the saved interface may include an interface saved according to the context of the terminal, specifically Including 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 according to the context of the terminal and the saved interface.
  • the second communication node can determine the context of the terminal and the associated saved interface according to the interface connection information in the indication information by receiving the indication information of the first communication node, and then according to the context of the terminal and the saved interface SDT is performed on the interface to effectively utilize resources on the base station side.
  • the method further includes: sending 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.
  • the indication message includes at least one of the following: SDT authentication pass message; terminal context establishment request message; terminal context modification message.
  • performing SDT according to the context of the terminal and the saved interface includes: in the case of receiving the SDT service data of the terminal, according to the saved terminal interface corresponding to the first communication node and the terminal corresponding to the second communication node
  • the interface transmits SDT service data to the first communication node through a data radio bearer (Data Radio Bearer, DRB) data transmission channel corresponding to the terminal.
  • DRB Data Radio Bearer
  • the method further includes: when the signaling data of the terminal is received, sending an uplink common control channel RRC message, where the uplink common control channel RRC message carries signaling data.
  • the uplink common control channel RRC message also carries a CCCH message indication, or interface connection information associated with the context.
  • the method further includes: sending a text update message, where the text update message includes a CG resource release indication or an updated CG resource.
  • the method further includes: sending an initial uplink RRC message, where the initial uplink RRC message carries SDT type information, and the SDT type includes RACH SDT or CG SDT.
  • the method further includes: receiving a terminal context update request, wherein the terminal context update request includes a CG resource release indication; releasing the CG resource and retaining the UE context according to the CG release indication.
  • the method further includes: receiving a terminal context update request, the terminal context update request including a CG resource update indication; reallocating and updating the CG resource according to the CG update indication; sending a terminal context update request feedback message.
  • the first communication node is a CU
  • the second communication node is a DU.
  • Fig. 3 is a schematic diagram of an implementation of a small data transmission method provided by an embodiment. As shown in Figure 3, the specific process of the method may include:
  • Step 1 When the service of the terminal (ie, UE) ends, the base station (eg, gNB) releases the UE to the RRC inactive state (ie, RRC_INACTIVE), instead of completely releasing the connection of the UE.
  • the gNB configures CG resources for the UE for small data transmission (ie SDT), and the DU side of the gNB saves the UE context (such as radio link control layer protocol (Radio Link Control, RLC) configuration, etc.), and the CU side of the gNB also Save UE context (such as Packet Data Convergence Protocol (PDCP) configuration, etc.), CU and DU save DRB data transmission channel (ie F1-U DRB tunnel).
  • PDCP Packet Data Convergence Protocol
  • Step 2 The UE is in the RRC inactive state and is ready to perform SDT, but the CG resources are not satisfied at this time, for example, the received signal quality corresponding to the CG resources does not meet the threshold requirements, or the RRC recovery request message sent through the CG resources fails to be transmitted to the gNB , the UE may prepare to send an RRC recovery request message to the gNB through the RACH channel.
  • Step 3 The UE sends an RRC recovery request message (that is, RRC RESUME REQUEST) to the gNB through the RACH channel.
  • RRC recovery request message that is, RRC RESUME REQUEST
  • the DU of the gNB recognizes that the UE needs to transmit small data, and the DU will receive the RRC recovery request
  • the message is encapsulated into the initial uplink RRC message (that is, Initial UL RRC Message), and the initial uplink RRC message is sent to the CU, wherein the initial uplink RRC message carries SDT indication information, which is used to indicate to the CU that the initial uplink RRC message is for small data transmission.
  • Step 4 The CU receives the RRC recovery request message contained in the initial uplink RRC message of the DU, identifies the UE through the I-RNTI contained in the RRC recovery request message, and performs authentication for small data transmission on the UE (that is, SDT authentication) , and find the UE context (i.e. UE Context) on the corresponding CU side and the connection information of the F1 interface associated with the UE context.
  • the UE context i.e. UE Context
  • the connection information may include the terminal F1 interface identification (Identification, ID) corresponding to the CU and the corresponding Terminal F1 interface ID (that is, to determine the UE F1 interface ID on the CU side and the UE F1 interface ID on the DU side associated with the UE context), where the UE F1 interface ID on the CU side can be expressed as CU UE F1AP ID, and the UE F1 interface ID on the DU side
  • the F1 interface ID can be expressed as DU UE F1AP ID
  • F1AP can refer to the F1 interface.
  • Step 5 The CU sends an indication message to the DU, such as an SDT authentication pass message (that is, an SDT Authentication Message), which includes the UE F1 interface ID on the CU side and the UE F1 interface ID on the DU side associated with the UE context.
  • the DU determines the context of the UE on the DU side through (CU UE F1AP ID, DU UE F1AP ID), and determines the connection of the F1 interface associated with the UE context.
  • the indication message sent by the CU to the DU here is not limited to the SDT authentication passing message, and the CU can also carry (CU UE F1AP ID , DU UE F1AP ID) is used to notify the DU to determine the context of the UE, that is, the indication message sent by the CU to the DU includes at least one of the following: SDT authentication pass message; terminal context establishment request message; terminal context modification message.
  • Step 6 During the subsequent small data transmission process, the UE sends DRB data (that is, the SDT service data of the terminal) to the DU through the RACH scheduling resource or the CG scheduling resource.
  • the DU After the DU receives the DRB data, it For the connection of the F1 interface (that is, the stored terminal interface corresponding to the CU and the terminal interface corresponding to the DU), the DRB data transmission channel corresponding to the UE on the F1 interface transmits the DRB data to the CU.
  • the CU After receiving the DRB data, the CU sends the DRB data to the 5G core network (ie 5GC)
  • Fig. 4 is an implementation schematic diagram of another small data transmission method provided by an embodiment. As shown in Figure 4, the specific process of the method may include:
  • Step 1 When the service of the terminal (ie, UE) ends, the base station (eg, gNB) releases the UE to the RRC inactive state (ie, RRC_INACTIVE), instead of completely releasing the connection of the UE.
  • the gNB configures CG resources for the UE for small data transmission (ie SDT), and the DU side of the gNB saves the UE context (such as RLC configuration, etc.), and the CU side of the gNB also saves the UE context (PDCP configuration, etc.), CU and DU Save the data transmission channel of DRB (ie F1-U DRB tunnel).
  • Step 2 The UE is in the RRC inactive state and is ready to perform SDT, but the CG resources are not satisfied at this time, for example, the received signal quality corresponding to the CG resources does not meet the threshold requirements, or the RRC recovery request message sent through the CG resources fails to be transmitted to the gNB , the UE may prepare to send an RRC recovery request message to the gNB through the RACH channel.
  • Step 3 The UE sends an RRC recovery request message (that is, RRC RESUME REQUEST) to the gNB through the RACH channel.
  • RRC recovery request message that is, RRC RESUME REQUEST
  • the DU of the gNB recognizes that the UE needs to transmit small data, and the DU will receive the RRC recovery request
  • the message is encapsulated into the initial uplink RRC message (that is, Initial UL RRC Message), and the initial uplink RRC message is sent to the CU, wherein the initial uplink RRC message carries SDT indication information, which is used to indicate to the CU that the initial uplink RRC message is for small data transmission.
  • Step 4 The CU receives the RRC recovery request message contained in the initial uplink RRC message of the DU, identifies the UE through the I-RNTI contained in the RRC recovery request message, and performs authentication for small data transmission on the UE (that is, SDT authentication) , and find the UE context (ie, UE context) on the corresponding CU side and the connection information of the F1 interface associated with the UE context.
  • the connection information may include the terminal F1 interface identification (Identification, ID) corresponding to the CU and the corresponding Terminal F1 interface ID (that is, to determine the UE F1 interface ID on the CU side and the UE F1 interface ID on the DU side associated with the UE context), where the UE F1 interface ID on the CU side can be expressed as CU UE F1AP ID, and the UE F1 interface ID on the DU side
  • the F1 interface ID can be expressed as DU UE F1AP ID
  • F1AP can refer to the F1 interface.
  • Step 5 The CU sends an indication message to the DU, such as an SDT authentication pass message (that is, an SDT Authentication Message), which includes the UE F1 interface ID on the CU side and the UE F1 interface ID on the DU side associated with the UE context.
  • the DU determines the context of the UE on the DU side through (CU UE F1AP ID, DU UE F1AP ID), and determines the connection of the F1 interface associated with the UE context.
  • the indication message sent by the CU to the DU here is not limited to the SDT authentication passing message, and the CU can also carry (CU UE F1AP ID , DU UE F1AP ID) is used to notify the DU to determine the context of the UE, that is, the indication message sent by the CU to the DU includes at least one of the following: SDT authentication pass message; terminal context establishment request message; terminal context modification message.
  • Step 6 UE sends subsequent signaling data, such as Signaling Radio Bearers (SRB) protocol data unit (Protocol Data Unit, PDU) through RACH scheduling or CG scheduling corresponding dedicated control channel (Dedicated Control Channel, DCCH) resource ) or Non Access Stratum (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 is sent to the CU through the uplink RRC message transfer (i.e. UL RRC Message Transfer) message carrying signaling data (i.e. SRB PDU or NAS PDU), where the UL RRC Message Transfer message carries the UE F1AP ID and The UE F1AP ID on the DU side is used to indicate to the CU which UE the signaling data belongs to.
  • SRB Signaling Radio Bearers
  • PDU Protocol Data Unit
  • Step 7 The UE sends subsequent signaling data (ie, SRB PDU or NAS PDU) to the DU through the corresponding CCCH common control channel resource scheduled by RACH, and the signaling data carries the UE's I-RNTI. Since it is a CCCH common channel, the DU cannot identify which UE the signaling data is aimed at at this time, and the DU sends the signaling data (ie SRB PDU or NAS PDU) through the uplink CCCH RRC message transfer (ie UL CCCH RRC Message Transfer) message
  • the message may optionally carry a CCCH message indication, which is used to indicate to the CU that the signaling data carried in the message is CCCH channel signaling.
  • the CU After the CU receives the UL CCCH RRC Message Transfer message, if the message carries the CCCH message indication, or the message does not carry the UE F1AP ID on the CU side and the UE F1AP ID on the DU side associated with the UE context (that is, CU&DU UE F1AP ID ), the CU identifies which UE the signaling data belongs to according to the I-RNTI of the UE in the signaling data carried in the message.
  • Fig. 5 is a schematic diagram of another small data transmission method provided by an embodiment. As shown in Figure 5, the specific process of the method may include:
  • Step 1 The CG resource is configured between the base station and the UE, and the UE performs small data transmission through the CG resource and the base station in the RRC inactive state.
  • Step 2 The DU decides to release or reconfigure (that is, update) the CG resource due to some reasons, for example, the effective timer of the CG resource configured on the DU side expires, or the load on the DU side is too large.
  • Step 3 DU sends UE text update (ie UE Context Modification Required) to CU, wherein UE text update message contains CG resource release instruction or updated CG resource (but not limited to this UE text update message).
  • UE text update ie UE Context Modification Required
  • UE text update message contains CG resource release instruction or updated CG resource (but not limited to this UE text update message).
  • Step 4 The CU receives the UE Context Modification Required message. If it contains a CG resource release indication, the CU can decide whether to release or keep the UE text (ie UE context) on the DU side (but not limited to this UE text update message) .
  • the CU can decide whether to release or keep the UE text (ie UE context) on the DU side (but not limited to this UE text update message) .
  • Step 5 If the CU decides to release the context on the DU side, the CU sends a UE Context Release (i.e. UE Context Release Request) message to the DU. After the DU receives the UE Context Release message, it releases the corresponding context on the DU side (such as RLC entity and configuration, physical layer and MAC layer entity and configuration, and the F1 interface channel between the CU).
  • UE Context Release i.e. UE Context Release Request
  • Step 6 The CU sends an RRC release message to the UE through the DU, instructing the UE to release to the inactive state.
  • the CU sets the CG resource related information in the RRC release message, such as setting the CG resource release instruction or the updated CG resource
  • the CU sends an RRC release message to the UE to notify the UE to release the CG resources or update the CG resources.
  • Step 7 The UE receives the RRC release message. If the message includes a CG resource release indication, the UE releases the corresponding CG resource configuration; if the message includes the updated CG resource, the UE saves and updates the corresponding CG resource configuration.
  • Fig. 6 is a schematic diagram of another small data transmission method provided by an embodiment. As shown in Figure 6, the specific process of the method may include:
  • Step 1 When the service of the UE ends, the base station (such as gNB) releases the UE to the RRC inactive state (ie RRC_INACTIVE), instead of completely releasing the connection of the UE.
  • the gNB configures CG resources for the UE for small data transmission (ie SDT), and the DU side of the gNB saves the UE context (such as RLC configuration, etc.), and the CU side of the gNB also saves the UE context (such as PDCP configuration, etc.), CU And DU saves the data transmission channel of DRB (ie F1-U DRB tunnel).
  • Step 2 The UE is in the RRC inactive state and is ready to perform SDT, but the CG resources are not satisfied at this time, for example, the received signal quality corresponding to the CG resources does not meet the threshold requirements, or the RRC recovery request message sent through the CG resources fails to be transmitted to the gNB , the UE prepares to send an RRC recovery request message to the gNB through the RACH channel.
  • Step 3 The UE sends an RRC recovery request message (ie, RRC RESUME REQUEST) to the gNB through the RACH channel.
  • RRC recovery request message ie, RRC RESUME REQUEST
  • the DU of the gNB recognizes that the UE needs to perform SDT, and recognizes that the type of SDT is RACH SDT.
  • the DU encapsulates the received RRC recovery request message into an initial uplink RRC message (that is, Initial UL RRC Message), and sends the initial uplink RRC message to the CU, wherein the initial uplink RRC message carries SDT indication information, which is used to indicate that the CU should The RRC recovery message is used for small data transmission; the initial uplink RRC message carries SDT type information, which is used to indicate to the CU whether the SDT is RACH SDT or CG SDT.
  • an initial uplink RRC message that is, Initial UL RRC Message
  • 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 in it. If the base station has configured CG resources and the SDT type is RACH SDT, the CU can decide to release or request an update CG resources of the base station.
  • 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 (that is, 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 (ie It can be called UE context update request message or UE text update message) to DU, where the message contains CG resource release instruction to instruct DU to release CG resource but retain UE context, or contains CG resource update instruction to instruct DU to re-allocate and Update CG resources.
  • a UE Context Release Request message that is, a UE Context Release Request message or a UE Text Release message
  • UE Context Modification Request message ie It can be called UE context update request message or UE text update message
  • Step 6 If the DU receives the UE Context Release Request message (that is, the UE context release request), the DU releases the context on the corresponding DU side (such as RLC entity and configuration, physical layer and MAC layer entity and configuration, and between CU and CU F1 interface channel);
  • the DU releases the context on the corresponding DU side (such as RLC entity and configuration, physical layer and MAC layer entity and configuration, and between CU and CU F1 interface channel);
  • the DU receives the UE Context Modification Request message sent by the CU (that is, the UE context update request), which contains the CG resource release indication, the DU will not release the context on the DU side (that is, retain the UE context on the DU side, such as the RLC entity and configuration, physical layer and MAC layer entities and configuration, and the F1 interface channel between the CU), but the DU releases the CG resources on the DU side. And after the DU releases the original CG resources on the DU side, the DU can optionally reallocate new CG resources, and send the new CG resources to the CU in the UE context update request feedback message;
  • the DU receives the UE Context Modification Request message sent by the CU (i.e., the UE context update request), which contains the CG resource update indication, the DU reallocates and updates the CG resource, and sends the updated CG resource to the UE Context Update Request feedback message (that is, it can also be called UE text update feedback message) and sent to the CU.
  • the UE Context Update Request feedback message that is, it can also be called UE text update feedback message
  • Step 7 The CU sends an RRC release message to the UE through the DU, instructing the UE to release to the inactive state.
  • the RRC release message includes the CG resource release indication or the updated CG resource of the DU.
  • Step 8 The UE receives the 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 the updated CG resource, the UE saves and updates the corresponding CG resource. configuration.
  • Fig. 7 is a schematic structural diagram of an indicating device provided by an embodiment. As shown in Figure 7, the indicating device includes:
  • a context determining module 310 configured to determine the context of the terminal
  • the indication message sending module 320 is configured to send an indication message to the second communication node, the indication message includes interface connection information associated with the context, and the interface connection information includes the terminal interface identifier corresponding to the first communication node and The 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 saved interface to perform SDT.
  • the first communication node determines the context of the terminal, and sends an indication message to the second communication node, which can enable the second communication node to perform an operation according to the interface connection information and the terminal context associated with the context contained in the indication message. SDT to effectively utilize resources on the base station side.
  • the device also includes:
  • the first RRC message receiving module is configured to receive an initial uplink RRC message of the second communication node, 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 according to the I-RNTI
  • the authentication module is configured to perform SDT authentication on the terminal.
  • the indication message includes at least one of the following: SDT authentication pass message; terminal context establishment request message; terminal context modification message.
  • the device also includes:
  • the second RRC message receiving module is configured to receive an uplink common control channel RRC message of the second communication node, and the uplink common control channel RRC message carries signaling data;
  • the terminal determination module is configured to: if the uplink common control channel RRC message carries a CCCH message indication, or if the uplink common control channel RRC message does not carry context-associated interface connection information, then according to the signaling data carried by the uplink common control channel RRC message
  • the I-RNTI in determines the terminal to which the signaling data belongs.
  • the device also includes:
  • An update message receiving module configured to receive a text update message from the second communication node, where the text update message includes a CG resource release instruction or an updated CG resource;
  • the context control module is configured to determine, according to the CG resource release indication, that the context of the terminal at the second communication node side is released or maintained if the text update message includes a CG resource release indication.
  • the device also includes:
  • the information setting module is configured to set the CG resource related information in the RRC release message according to the CG resource release instruction or the updated CG resource;
  • the release message sending module is configured to send an RRC release message, and the RRC release message is used to notify the terminal to release CG resources or update CG resources.
  • the device also includes:
  • the third RRC message receiving module is configured to receive the initial uplink RRC message of the second communication node, the initial uplink RRC message carries SDT category information, and the SDT category includes RACH SDT or CG SDT;
  • the CG resource control module is configured to release or update the CG resource if the CG resource has been configured and the SDT type is RACH SDT.
  • the device also includes:
  • the update request sending module is configured to send a terminal context update request, and the terminal context update request includes a CG resource release indication or a CG resource update indication; wherein the CG resource release indication is used to instruct the second communication node to release the CG resource and retain the UE context; The CG update indication is used to instruct the DU to reallocate and update CG resources.
  • the pointing device proposed in this embodiment and the pointing method proposed in the above-mentioned embodiment belong to the same inventive concept, and the technical details not described in detail in this embodiment can be referred to any of the above-mentioned embodiments, and this embodiment has the same benefits as the execution of the pointing method Effect.
  • Fig. 8 is a schematic structural diagram of a data transmission device provided by an embodiment. As shown in Figure 8, the data transmission device includes:
  • the indication message receiving module 410 is configured to receive an indication message, the indication message includes interface connection information associated with the context of the terminal, and the interface connection information includes the terminal interface identifier corresponding to the first communication node and the terminal interface identifier corresponding to the second communication node.
  • the terminal interface identifier for .
  • the context and interface determining module 420 is configured to determine the context of the terminal and the associated saved interface according to the interface connection information.
  • the SDT execution module 430 is configured to perform SDT according to the context of the terminal and the saved interface.
  • the second communication node can determine the context of the terminal and the associated saved interface according to the interface connection information in the indication information by receiving the indication information from the first communication node, and on this basis, according to the terminal's
  • the context and the saved interface are used for SDT to effectively utilize resources on the base station side.
  • the device also includes:
  • the first RRC message sending module is configured to send an initial uplink RRC message, the initial uplink RRC message includes an RRC recovery request message, and the RRC recovery request message includes an I-RNTI.
  • the indication message includes at least one of the following: SDT authentication pass message; terminal context establishment request message; terminal context modification message.
  • the SDT execution module specifically includes:
  • the transmission unit is configured to, in the case of receiving the SDT service data of the terminal, according to the stored terminal interface corresponding to the first communication node and the terminal interface corresponding to the second communication node, through the DRB data transmission channel corresponding to the terminal, to the first The communication node transmits SDT service data.
  • the device also includes:
  • the second RRC message sending module is configured to send an uplink common control channel RRC message when receiving signaling data from the terminal, and the uplink common control channel RRC message carries signaling data.
  • the uplink common control channel RRC message also carries a CCCH message indication, or interface connection information associated with the context.
  • the device also includes:
  • the update message sending module is configured to send a text update message, and the text update message includes a CG resource release instruction or an updated CG resource.
  • the device also includes:
  • the third RRC message sending module is configured to send an initial uplink RRC message, the initial uplink RRC message carries SDT category information, and the SDT category includes RACH SDT or CG SDT.
  • the device also includes:
  • the first update request receiving module is configured to receive a terminal context update request, and the terminal context update request includes a CG resource release indication;
  • the release module is configured to release the CG resource and reserve the UE context according to the CG resource release instruction.
  • the device also includes:
  • the second update request receiving module is configured to receive a terminal context update request, and the terminal context update request includes a CG resource update indication;
  • the CG resource update module is configured to reallocate and update the CG resource according to the CG resource update instruction
  • the feedback message sending module is configured to send a terminal context update request feedback message.
  • the data transmission device proposed in this embodiment and the data transmission method proposed in the above-mentioned embodiments belong to the same inventive concept, and the technical details not described in detail in this embodiment can be referred to any of the above-mentioned embodiments, and this embodiment has and executes a data transmission method Same beneficial effect.
  • FIG. 9 is a schematic diagram of a hardware structure of a communication node provided by an embodiment, as shown in FIG. 9 .
  • the communication node provided in this application includes a memory 520, a processor 510, and a computer program stored in the memory and operable on the processor. When the processor 510 executes the program, the above-mentioned instruction method or data transmission method is realized.
  • the communication node may also include a memory 520; there may be one or more processors 510 in the communication node, and one processor 510 is taken as an example in FIG. 9; the memory 520 is used to store one or more programs; the one or more A program is executed by the one or more processors 510, so that the one or more processors 510 implement the indication method or the data transmission method as described in the embodiment of the present application.
  • the communication node further includes: a communication device 530 , an input device 540 and an output device 550 .
  • the processor 510, the memory 520, the communication device 530, the input device 540, and the output device 550 in the communication node may be connected through a bus or in other ways. In FIG. 9, connection through a bus is taken as an example.
  • the input device 540 can be used to receive input numbers or character information, and generate key signal input related to user settings and function control of the communication node.
  • the output device 550 may include a display device such as a display screen.
  • Communications device 530 may include a receiver and a transmitter.
  • the communication device 530 is configured to perform information sending and receiving communication according to the control of the processor 510 .
  • the memory 520 can be set to store software programs, computer-executable programs and modules, such as the program instructions/modules corresponding to the indication method described in the embodiment of the present application (for example, the context determination module in the indication device 310 and the instruction message sending module 320); or the program instructions/modules corresponding to the data transmission method described in the embodiment of the present application (for example, the instruction message receiving module 410 and the context, interface determination module 420 and SDT execution module in the data transmission device 430).
  • the program instructions/modules corresponding to the indication method described in the embodiment of the present application for example, the context determination module in the indication device 310 and the instruction message sending module 320
  • the program instructions/modules corresponding to the data transmission method described in the embodiment of the present application for example, the instruction message receiving module 410 and the context, interface determination module 420 and SDT execution module in the data transmission device 430.
  • the memory 520 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the communication node, and the like.
  • the memory 520 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage devices.
  • memory 520 may further include memory located remotely from processor 510, and these remote memories may be connected to communication nodes through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the embodiment of the present application further provides a storage medium, the storage medium stores a computer program, and when the computer program is executed by a processor, the instruction method or the data transmission method described in any one of the embodiments of the present application is implemented.
  • the indication method includes: determining the context of the terminal; sending an indication message to the second communication node, where the indication message includes interface connection information associated with the context, and the interface connection information includes the terminal corresponding to the first communication node.
  • the interface connection information is used to instruct the second communication node to use the saved interface to perform SDT.
  • the data transmission method includes: receiving an indication message, where the indication message includes interface connection information associated with the context of the terminal, and the interface connection information includes the terminal interface identifier corresponding to the first communication node and the terminal interface identifier corresponding to the second communication node Terminal interface identification; determining the context of the terminal and the associated saved interface according to the interface connection information; performing SDT according to the context of the terminal and the saved interface.
  • the computer storage medium in the embodiments of the present application may use 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.
  • a computer-readable storage medium may be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination thereof.
  • Computer-readable storage media include: electrical connections with one or more conductors, portable computer disks, hard disks, Random Access Memory (RAM), read-only memory (Read Only Memory, ROM), Erasable Programmable Read Only Memory (EPROM), flash memory, optical fiber, portable disc storage (Compact Disc Read-Only Memory, CD-ROM), optical storage devices, A magnetic storage device, or any suitable combination of the above.
  • a computer readable storage medium may be any tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device.
  • a computer readable signal medium may include a data signal carrying computer readable program code in baseband or as part of a carrier wave. Such propagated data signals may take many forms, including but not limited to: electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • a computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. .
  • Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wires, optical cables, radio frequency (Radio Frequency, RF), etc., or any suitable combination of the above.
  • any appropriate medium including but not limited to: wireless, wires, optical cables, radio frequency (Radio Frequency, RF), etc., or any suitable combination of the above.
  • Computer program codes for performing 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 conventional A procedural programming language, such as the "C" language or similar programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or it may be connected to an external computer such as use an Internet service provider to connect via the Internet).
  • LAN Local Area Network
  • WAN Wide Area Network
  • user terminal covers any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser or a vehicle-mounted mobile station.
  • the various embodiments of the present application can be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.
  • Embodiments of the present application may be realized by a data processor of a mobile device executing computer program instructions, for example in a processor entity, or by hardware, or by a combination of software and hardware.
  • Computer program instructions may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages source or object code.
  • ISA Instruction Set Architecture
  • Any logic flow block diagrams in the figures of this application may represent program steps, or may represent interconnected logic circuits, modules and functions, or may represent a combination of program steps and logic circuits, modules and functions.
  • Computer programs can be stored on memory.
  • the memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as but not limited to Read-Only Memory (ROM), Random Access Memory (RAM), Optical Memory devices and systems (Digital Video Disc (DVD) or Compact Disk (CD), etc.
  • Computer-readable media may include non-transitory storage media.
  • Data processors may be any Types, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic devices (Field-Programmable Gate Array , FPGA) and processors based on multi-core processor architectures.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • processors based on multi-core processor architectures.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Databases & Information Systems (AREA)

Abstract

本申请提供一种指示方法、数据传输方法、通信节点及存储介质。该方法确定终端的上下文；向第二通信节点发送指示消息，所述指示消息包含所述上下文相关联的接口连接信息，所述接口连接信息包括所述第一通信节点对应的终端接口标识和所述第二通信节点对应的终端接口标识，所述接口连接信息用于指示所述第二通信节点使用保存的接口进行小数据传输SDT。

Description

指示方法、数据传输方法、通信节点及存储介质 技术领域
本申请涉及无线通信网络技术领域，例如涉及一种指示方法、数据传输方法、通信节点及存储介质。
背景技术
在无线通信系统中，基站(如gNB)可分离为集中式单元(Centralized Unit，CU)和分布式单元(Distributed Unit，DU)，一个基站可以包含一个CU和多个DU，CU和DU之间通过接口连接。此外，为处于无线资源控制(Radio Resource Control，RRC)非激活态(RRC_INACTIVE)的终端(User Equipment，UE)分配了专有调度(Configured Grant，CG)资源用于小数据(Small Data Transmission，SDT)传输，但如果UE使用随机接入信道(Random Access Channel，RACH)资源进行SDT传输，DU无法利用生成CG配置资源的时候保存的UE上下文进行小数据传输，这样浪费了基站侧的资源。
发明内容
本申请提供一种指示方法、数据传输方法、通信节点及存储介质。
本申请实施例提供一种指示方法，应用于第一通信节点，包括：确定终端的上下文；向第二通信节点发送指示消息，所述指示消息包含所述上下文相关联的接口连接信息，所述接口连接信息包括所述第一通信节点对应的终端接口标识和所述第二通信节点对应的终端接口标识，所述接口连接信息用于指示所述第二通信节点使用保存的接口进行SDT。
本申请实施例还提供了一种数据传输方法，应用于第二通信节点，包括：接收指示消息，所述指示消息包含终端的上下文相关联的接口连接信息，所述接口连接信息包括第一通信节点对应的终端接口标识和所述第二通信节点第一的终端接口标识；根据所述接口连接信息确定所述终端的上下文和相关联的保存的接口；根据所述终端的上下文和所述保存的接口进行SDT。
本申请实施例还提供了一种通信节点，包括：存储器、处理器以及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现上述的指示方法或数据传输方法。
本申请实施例还提供了一种计算机可读存储介质，计算机可读存储介质上 存储有计算机程序，该程序被处理器执行时实现上述的指示方法或数据传输方法。
附图说明
图1为一实施例提供的一种指示方法的流程图；
图2为一实施例提供的一种数据传输方法的流程图；
图3为一实施例提供的一种小数据传输方法的实现示意图；
图4为一实施例提供的另一种小数据传输方法的实现示意图；
图5为一实施例提供的又一种小数据传输方法的实现示意图；
图6为一实施例提供的又一种小数据传输方法的实现示意图；
图7为一实施例提供的一种指示装置的结构示意图；
图8为一实施例提供的一种数据传输装置的结构示意图；
图9为一实施例提供的一种通信节点的硬件结构示意图。
具体实施方式
下面结合附图和实施例对本申请进行说明。可以理解的是，此处所描述的具体实施例仅仅用于解释本申请，而非对本申请的限定。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。另外还需要说明的是，为了便于描述，附图中仅示出了与本申请相关的部分而非全部结构。
随着智能终端和物联网终端的发展，一些即时通信业务应用的用户量越来越大，这类业务通常一直在线，并且用户在使用的时候，主要进行小数据量的传输，如文字类的消息。由于小数据量业务需要UE频繁地和无线网络(Radio Network，RAN)进行信令链接重建，因此可能会引起RAN的信令负荷加重等问题。
在第四代移动通信(Fourth Generation，4G)的时候，为了优化对不频繁的小数据包传输的支持，4G网络支持UE在随机接入信道(Random Access Channel，RACH)接入的时候，UE可以在RACH接入请求消息中或者无线资源控制(Radio Resource Control，RRC)连接建立请求消息中携带相应的小数据传输给RAN。在这种情况下，UE可以不需要和网络频繁地进行信令链接重建，即可以传输偶发的小数据量数据。
4G长期演进(Long Term Evolution，LTE)的RRC状态可包括两种： RRC_IDLE(即RRC空闲态)和RRC_CONNECTED(即RRC连接态)，5G引入了RRC_INACTIVE(即RRC非激活态)。在RRC INACTIVE状态下，UE处于省电的睡眠状态，但UE仍然保留RAN上下文，RAN侧也保留了UE上下文(即UE Context)，这样UE在有数据传输的时候，可以快速的从RRC INACTIVE状态转移到RRC CONNECTED状态并进行数据传输。这样做可以减少信令开销，可以快速接入，降低时延，还能更省电。
但是对于小数据传输，5G也支持UE保持在RRC_INACTIVE状态的时候而不用进入RRC_CONNECTED状态，和RAN进行数据传输。5G的小数据传输(即SDT)包括基于RACH的SDT，和基于CG资源的SDT。在给UE配置了RRC_INACTIVE状态的CG资源的情况下，UE在RRC_INACTIVE可以使用CG资源进行小数据传输，但是可能该UE的CG资源的信号质量不太好，这种情况下，UE即使在配置了CG资源的情况下，在RRC_INACTIVE状态也可能使用RACH接入过程进行小数据的传输。
对于5G基站(如gNB)，可分离为CU和DU，一个gNB可以包含一个CU和多个DU，CU和DU之间通过接口连接。在gNB为RRC_INACTIVE的UE分配了CG资源用于小数据的传输，但此时如果UE使用RACH资源进行小数据的传输，DU无法利用生成CG配置资源的时候保存的UE上下文进行小数据传输，导致浪费基站侧的资源。
图1为一实施例提供的一种指示方法的流程图，如图1所示，该方法可应用于第一通信节点，第一通信节点可以是CU，本实施例提供的方法包括步骤110和步骤120。
在步骤110中，确定终端的上下文。
在步骤120中，向第二通信节点发送指示消息，所述指示消息包含所述上下文相关联的接口连接信息，所述接口连接信息包括所述第一通信节点对应的终端接口标识和所述第二通信节点对应的终端接口标识，所述接口连接信息用于指示所述第二通信节点使用保存的接口进行SDT。
本实施例中，第一通信节点确定终端的上下文，然后向第二通信节点发送指示消息。其中，第二通信节点可以是DU，指示消息中可包含上下文相关联的接口连接信息，接口连接信息可包括第一通信节点对应的终端接口标识和第二通信节点对应的终端接口标识，接口连接信息可用于指示第二通信节点使用保存的接口进行SDT。保存的接口可以包括根据终端的上下文所保存的接口，具体可包括CU侧的UE F1接口和DU侧的UE F1接口。
本实施例中，第一通信节点确定终端的上下文，并发送指示消息至第二通信节点，能够使得第二通信节点根据指示消息中所包含的上下文相关联的接口连接信息和终端上下文进行SDT，以有效利用基站侧的资源。
在一实施例中，该方法还包括：接收第二通信节点的初始上行RRC消息，初始上行RRC消息包含RRC恢复请求消息，RRC恢复请求消息包含非激活态的无线网络临时标识(Inactive Radio Network Tempory Identity，I-RNTI)；根据I-RNTI识别终端；对终端进行SDT鉴权。
在一实施例中，指示消息包括以下至少之一：SDT鉴权通过消息；终端上下文建立请求消息；终端上下文修改消息。
在一实施例中，该方法还包括：接收第二通信节点的上行公共控制信道RRC消息，上行公共控制信道RRC消息携带信令数据；若上行公共控制信道RRC消息携带公共控制信道(Common Control Channel，CCCH)消息指示，或者，上行公共控制信道RRC消息中不携带上下文相关联的接口连接信息，则根据上行公共控制信道RRC消息携带的信令数据中的I-RNTI确定信令数据所属的终端。
在一实施例中，该方法还包括：接收第二通信节点的文本更新消息，文本更新消息包含配置授权(Configured Grant，CG)资源释放指示或者更新后的CG资源；若文本更新消息包含CG资源释放指示，则根据CG资源释放指示确定第二通信节点侧终端的上下文被释放或者被保持。
在一实施例中，该方法还包括：根据CG资源释放指示或者更新后的CG资源，设置RRC释放消息中的CG资源相关信息；发送RRC释放消息，RRC释放消息用于通知终端释放CG资源或者更新CG资源。
在一实施例中，该方法还包括：接收第二通信节点的初始上行RRC消息，初始上行RRC消息携带SDT类别信息，SDT类别包括RACH SDT或CG SDT；若已经配置了CG资源，且SDT类别为RACH SDT，则释放或更新CG资源。
在一实施例中，该方法还包括：发送终端上下文更新请求，终端上下文更新请求中包含CG资源释放指示或者CG资源更新指示；其中，CG资源释放指示用于指示第二通信节点释放CG资源并保留UE上下文；CG资源更新指示用于指示DU重新分配并更新CG资源。
本申请实施例还提供一种数据传输方法。图2为一实施例提供的一种数据传输方法的流程图，如图2所示，该方法可应用于第二通信节点，第二通信节点可以是DU，本实施例提供的方法包括步骤210、步骤220和步骤230。
在步骤210中，接收指示消息，所述指示消息包含终端的上下文相关联的接口连接信息，所述接口连接信息包括第一通信节点对应的终端接口标识和所述第二通信节点对应的终端接口标识。
在步骤220中，根据所述接口连接信息确定所述终端的上下文和相关联的保存的接口。
在步骤230中，根据所述终端的上下文和所述保存的接口进行SDT。
本实施例中，首先，第二通信节点接收第一通信节点所发送的指示消息，其中，指示消息可以包含终端的上下文相关联的接口连接信息，接口连接信息可以包括第一通信节点对应的终端接口标识和第二通信节点对应的终端接口标识。然后，第二通信节点可以根据指示消息中与终端的上下文相关联的接口连接信息确定终端的上下文和相关联的保存的接口；其中保存的接口可以包括根据终端的上下文所保存的接口，具体可包括CU侧的UE F1接口和DU侧的UE F1接口。最后，第二通信节点可以根据终端的上下文和保存的接口进行SDT。
本实施例中，第二通信节点通过接收第一通信节点的指示信息，根据指示信息中的接口连接信息能够确定终端的上下文和相关联的保存的接口，在此基础上根据终端的上下文和保存的接口进行SDT，以有效利用基站侧的资源。
在一实施例中，该方法还包括：发送初始上行RRC消息，初始上行RRC消息包含RRC恢复请求消息，RRC恢复请求消息包含I-RNTI。
在一实施例中，指示消息包括以下至少之一：SDT鉴权通过消息；终端上下文建立请求消息；终端上下文修改消息。
在一实施例中，根据终端的上下文和保存的接口进行SDT，包括：在接收到终端的SDT业务数据的情况下，根据保存的第一通信节点对应的终端接口和第二通信节点对应的终端接口，通过终端对应的数据无线承载(Data Radio Bearer，DRB)数据传输通道，向第一通信节点传输SDT业务数据。
在一实施例中，该方法还包括：在接收到终端的信令数据的情况下，发送上行公共控制信道RRC消息，上行公共控制信道RRC消息携带信令数据。
在一实施例中，上行公共控制信道RRC消息还携带CCCH消息指示，或者，上下文相关联的接口连接信息。
在一实施例中，该方法还包括：发送文本更新消息，文本更新消息包含CG资源释放指示或者更新后的CG资源。
在一实施例中，该方法还包括：发送初始上行RRC消息，初始上行RRC消息携带SDT类别信息，SDT类别包括RACH SDT或CG SDT。
在一实施例中，该方法还包括：接收终端上下文更新请求，终端上下文更新请求中包含CG资源释放指示；根据CG释放指示释放CG资源并保留UE上下文。
在一实施例中，该方法还包括：接收终端上下文更新请求，终端上下文更新请求中包含CG资源更新指示；根据CG更新指示重新分配并更新CG资源；发送终端上下文更新请求反馈消息。
以下通过不同实施例对小数据的传输方法进行示例性说明。在以下实施例中，第一通信节点为CU，第二通信节点为DU。
实施例一
图3为一实施例提供的一种小数据传输方法的实现示意图。如图3所示，该方法的具体过程可以包括：
步骤1：在终端(即UE)业务结束的时候，基站(如gNB)将UE释放到RRC非激活态(即RRC_INACTIVE)，而不是完全释放UE的连接。gNB为UE配置了CG资源用于小数据传输(即SDT)，并且gNB的DU侧保存了UE上下文(如无线链路控制层协议(Radio Link Control，RLC)配置等)，gNB的CU侧也保存UE上下文(如分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)配置等)，CU和DU保存了DRB的数据传输通道(即F1-U DRB tunnel)。
步骤2：UE处于RRC非激活态，准备进行SDT，但此时CG资源不满足，比如CG资源对应的接收信号质量不满足门限要求，或者通过CG资源发送RRC恢复请求消息未能成功传输给gNB，则UE可准备通过RACH信道发送RRC恢复请求消息给gNB。
步骤3：UE通过RACH信道发送RRC恢复请求消息(即RRC RESUME REQUEST)给gNB，gNB的DU接收到RRC恢复请求消息后，识别出UE是需要进行小数据传输，DU将接收到的RRC恢复请求消息封装到初始上行RRC消息(即Initial UL RRC Message)中，并将初始上行RRC消息发送给CU，其中初始上行RRC消息中携带SDT指示信息，用于指示CU该初始上行RRC消息是用于小数据传输。
步骤4：CU接收到DU在初始上行RRC消息中包含的RRC恢复请求消息，通过RRC恢复请求消息中包含的I-RNTI识别出UE，对UE进行小数据传输的鉴权(即SDT鉴权)，并找到对应的CU侧的UE上下文(即UE Context)以及和该UE上下文相关联的F1接口的连接信息，该连接信息可包括CU对应的 终端F1接口标识(Identification，ID)和DU对应的终端F1接口ID(即确定该UE上下文相关联的CU侧的UE F1接口ID和DU侧的UE F1接口ID)，其中CU侧的UE F1接口ID可表示为CU UE F1AP ID，DU侧的UE F1接口ID可表示为DU UE F1AP ID，F1AP可指F1接口。
步骤5：CU向DU发送指示消息如SDT鉴权通过消息(即SDT Authentication Message)，其中包含该UE上下文相关联的CU侧的UE F1接口ID和DU侧的UE F1接口ID。DU接收到该消息后，通过(CU UE F1AP ID，DU UE F1AP ID)确定该UE在DU侧的上下文，以及确定该UE上下文相关联的F1接口的连接。需要说明的是，此处CU向DU发送的指示消息不限于SDT鉴权通过消息，CU也可以在UE上下文建立请求消息/修改消息(即UE CONTEXT SETUP/MODIFICATION REQUEST)中携带(CU UE F1AP ID，DU UE F1AP ID)用于通知DU确定UE的上下文，即CU向DU发送的指示消息包括以下至少之一：SDT鉴权通过消息；终端上下文建立请求消息；终端上下文修改消息。
步骤6：UE在后续的小数据传输过程中，通过RACH调度资源，或者CG调度资源发送DRB数据(即终端的SDT业务数据)给DU，DU接收到DRB数据后，根据该UE上下文相关联的F1接口的连接(即保存的CU对应的终端接口和DU对应的终端接口)，在F1接口上的该UE对应的DRB数据传输通道将DRB数据传输给CU。CU接收到DRB数据后，将DRB数据发送给5G核心网(即5GC)
实施例二
图4为一实施例提供的另一种小数据传输方法的实现示意图。如图4所示，该方法的具体过程可以包括：
步骤1：在终端(即UE)业务结束的时候，基站(如gNB)将UE释放到RRC非激活态(即RRC_INACTIVE)，而不是完全释放UE的连接。gNB为UE配置了CG资源用于小数据传输(即SDT)，并且gNB的DU侧保存了UE上下文(如RLC配置等)，gNB的CU侧也保存UE上下文(PDCP配置等)，CU和DU保存了DRB的数据传输通道(即F1-U DRB tunnel)。
步骤2：UE处于RRC非激活态，准备进行SDT，但此时CG资源不满足，比如CG资源对应的接收信号质量不满足门限要求，或者通过CG资源发送RRC恢复请求消息未能成功传输给gNB，则UE可准备通过RACH信道发送RRC恢复请求消息给gNB。
步骤3：UE通过RACH信道发送RRC恢复请求消息(即RRC RESUME REQUEST)给gNB，gNB的DU接收到RRC恢复请求消息后，识别出UE是 需要进行小数据传输，DU将接收到的RRC恢复请求消息封装到初始上行RRC消息(即Initial UL RRC Message)中，并将初始上行RRC消息发送给CU，其中初始上行RRC消息中携带SDT指示信息，用于指示CU该初始上行RRC消息是用于小数据传输。
步骤4：CU接收到DU在初始上行RRC消息中包含的RRC恢复请求消息，通过RRC恢复请求消息中包含的I-RNTI识别出UE，对UE进行小数据传输的鉴权(即SDT鉴权)，并找到对应的CU侧的UE上下文(即UE context)以及和该UE上下文相关联的F1接口的连接信息，该连接信息可包括CU对应的终端F1接口标识(Identification，ID)和DU对应的终端F1接口ID(即确定该UE上下文相关联的CU侧的UE F1接口ID和DU侧的UE F1接口ID)，其中CU侧的UE F1接口ID可表示为CU UE F1AP ID，DU侧的UE F1接口ID可表示为DU UE F1AP ID，F1AP可指F1接口。
步骤5：CU向DU发送指示消息如SDT鉴权通过消息(即SDT Authentication Message)，其中包含该UE上下文相关联的CU侧的UE F1接口ID和DU侧的UE F1接口ID。DU接收到该消息后，通过(CU UE F1AP ID，DU UE F1AP ID)确定该UE在DU侧的上下文，以及确定该UE上下文相关联的F1接口的连接。需要说明的是，此处CU向DU发送的指示消息不限于SDT鉴权通过消息，CU也可以在UE上下文建立请求消息/修改消息(即UE CONTEXT SETUP/MODIFICATION REQUEST)中携带(CU UE F1AP ID，DU UE F1AP ID)用于通知DU确定UE的上下文，即CU向DU发送的指示消息包括以下至少之一：SDT鉴权通过消息；终端上下文建立请求消息；终端上下文修改消息。
步骤6：UE通过RACH调度或者CG调度的对应专用控制信道(Dedicated Control Channel，DCCH)资源发送后续信令数据，如信令无线承载(Signalling Radio Bearers，SRB)协议数据单元(Protocol Data Unit，PDU)或者非接入层(Non Access Stratum，NAS)PDU给DU，DU可以根据针对不同UE调度的资源，识别出信令数据是针对哪个UE的。DU通过上行RRC信息传输(即UL RRC Message Transfer)消息携带信令数据(即SRB PDU或NAS PDU)发送给CU，其中UL RRC Message Transfer消息携带该UE上下文相关联的CU侧的UE F1AP ID和DU侧的UE F1AP ID，用于指示CU该信令数据属于哪个UE。
步骤7：UE通过RACH调度的对应CCCH公共控制信道资源发送后续信令数据(即SRB PDU或者NAS PDU)给DU，且在信令数据中携带UE的I-RNTI。由于是CCCH公共信道，DU此时无法识别出信令数据是针对哪个UE的，DU通过上行CCCH RRC信息传输(即UL CCCH RRC Message Transfer)消息携带信令数据(即SRB PDU或NAS PDU)发送给CU，其中消息中可选的携带CCCH 消息指示，用于指示CU该消息中携带的信令数据是CCCH信道信令。CU接收到UL CCCH RRC Message Transfer消息后，如果该消息中携带CCCH消息指示，或者消息中不携带该UE上下文相关联的CU侧的UE F1AP ID和DU侧的UE F1AP ID(即CU&DU UE F1AP ID)，则CU根据该消息中携带的信令数据中的UE的I-RNTI识别出该信令数据属于哪个UE。
实施例三
图5为一实施例提供的又一种小数据传输方法的实现示意图。如图5所示，该方法的具体过程可以包括：
步骤1：基站和UE之间配置的CG资源，UE在RRC非激活态通过CG资源和基站进行小数据传输。
步骤2：DU因某些原因决定释放或者重新配置(即更新)CG资源，比如DU侧配置的CG资源的有效定时器超时，或者DU侧的负荷过大。
步骤3：DU发送UE文本更新(即UE Context Modification Required)给CU，其中UE文本更新消息包含CG资源释放指示或者更新后的CG资源(但不限于此UE文本更新消息)。
步骤4：CU接收到UE Context Modification Required消息，如果其中包含了CG资源释放指示，则CU可以决定是否释放或者依旧保持DU侧的UE文本(即UE上下文)(但不限于此UE文本更新消息)。
步骤5：如果CU决定释放DU侧的上下文，则CU发送UE文本释放(即UE Context Release Request)消息给DU，DU接收到该UE文本释放消息后，则释放对应的DU侧的上下文(如RLC实体和配置，物理层和MAC层实体和配置，以及和CU之间的F1接口通道)。
步骤6：CU通过DU向UE发送RRC释放消息，指示UE释放到非激活态。其中根据CU从DU侧接收的UE Context Modification Required等消息包含的CG资源释放指示或者DU更新后的CG资源，CU设置RRC释放消息中的CG资源相关信息，如设置CG资源释放指示或者更新后的CG资源，CU发送RRC释放消息给UE从而通知UE释放CG资源或者更新CG资源。
步骤7：UE接收RRC释放消息，如果该消息中包含CG资源释放指示，则UE释放相应CG资源配置；如果该消息中包含更新后的CG资源，UE保存并更新相应的CG资源配置。
实施例四
图6为一实施例提供的又一种小数据传输方法的实现示意图。如图6所示， 该方法的具体过程可以包括：
步骤1：在UE业务结束的时候，基站(如gNB)将UE释放到RRC非激活态(即RRC_INACTIVE)，而不是完全释放UE的连接。gNB并为UE配置了CG资源用于小数据传输(即SDT)，并且gNB的DU侧保存了UE上下文(如RLC配置等)，gNB的CU侧也保存UE上下文(如PDCP配置等)，CU和DU保存了DRB的数据传输通道(即F1-U DRB tunnel)。
步骤2：UE处于RRC非激活态，准备进行SDT，但此时CG资源不满足，比如CG资源对应的接收信号质量不满足门限要求，或者通过CG资源发送RRC恢复请求消息未能成功传输给gNB，则UE准备通过RACH信道发送RRC恢复请求消息给gNB。
步骤3：UE通过RACH信道发送RRC恢复请求消息(即RRC RESUME REQUEST)给gNB，gNB的DU接收到RRC恢复请求消息后，识别出来UE是需要进行SDT，并识别出SDT的类型是RACH SDT。DU将接收到的RRC恢复请求消息封装到初始上行RRC消息(即Initial UL RRC Message)中，并将初始上行RRC消息发送给CU,其中初始上行RRC消息中携带SDT指示信息，用于指示CU该RRC恢复消息是用于小数据传输；其中初始上行RRC消息中携带SDT类别信息，用于指示CU该SDT是RACH SDT还是CG SDT。
步骤4：CU接收初始上行RRC消息，根据其中携带SDT类别信息，识别该SDT是RACH SDT还是CG SDT，如果基站侧已经配置了CG资源，而SDT类别为RACH SDT，CU可以决定释放或请求更新基站的CG资源。
步骤5：如果CU决定同时释放DU侧的上下文，则CU发送UE Context Release Request消息(即可称为UE上下文释放请求消息或UE文本释放消息)给DU；否则CU发送UE Context Modification Request消息(即可称为UE上下文更新请求消息或UE文本更新消息)给DU，其中消息中包含CG资源释放指示用于指示DU释放CG资源但保留UE上下文，或者包含CG资源更新指示用于指示DU重新分配并更新CG资源。
步骤6：如果DU接收到UE Context Release Request消息(即UE上下文释放请求)，则DU释放对应的DU侧的上下文(如RLC实体和配置，物理层和MAC层实体和配置，以及和CU之间的F1接口通道)；
如果DU接收到CU发送的UE Context Modification Request消息(即UE上下文更新请求)，其中消息中包含CG资源释放指示，则DU不释放DU侧的上下文(即保留DU侧的UE上下文，如RLC实体和配置，物理层和MAC层实体和配置，以及和CU之间的F1接口通道)，但DU释放DU侧的CG资源。 并且DU在释放了DU侧的原有CG资源后，DU可选的可以重新分配新的CG资源，并将新的CG资源在UE上下文更新请求反馈消息中发送给CU；
如果DU接收到CU发送的UE Context Modification Request消息(即UE上下文更新请求)，其中消息中包含CG资源更新指示，DU重新分配并更新CG资源，并将更新的CG资源在UE上下文更新请求反馈消息(即也可称为UE文本更新反馈消息)中发送给CU。
步骤7：CU通过DU向UE发送RRC释放消息，指示UE释放到非激活态。其中该RRC释放消息包含CG资源释放指示或者DU更新后的CG资源。
步骤8：UE接收RRC释放消息，如果该RRC释放消息中包含CG资源释放指示，则UE释放相应CG资源配置；如果该RRC释放消息中包含更新后的CG资源，UE保存并更新相应的CG资源配置。
本申请实施例还提供一种指示装置。图7为一实施例提供的一种指示装置的结构示意图。如图7所示，所述指示装置包括：
上下文确定模块310，设置为确定终端的上下文；
指示消息发送模块320，设置为向第二通信节点发送指示消息，所述指示消息包含所述上下文相关联的接口连接信息，所述接口连接信息包括所述第一通信节点对应的终端接口标识和所述第二通信节点对应的终端接口标识，所述接口连接信息用于指示所述第二通信节点使用保存的接口进行SDT。
本实施例的指示装置，第一通信节点确定终端的上下文，并发送指示消息至第二通信节点，能够使得第二通信节点根据指示消息中所包含的上下文相关联的接口连接信息和终端上下文进行SDT，以有效利用基站侧的资源。
在一实施例中，该装置还包括：
第一RRC消息接收模块，设置为接收第二通信节点的初始上行RRC消息，初始上行RRC消息包含RRC恢复请求消息，RRC恢复请求消息包含I-RNTI；
终端识别模块，设置为根据I-RNTI识别所述终端；
鉴权模块，设置为对终端进行SDT鉴权。
在一实施例中，指示消息包括以下至少之一：SDT鉴权通过消息；终端上下文建立请求消息；终端上下文修改消息。
在一实施例中，该装置还包括：
第二RRC消息接收模块，设置为接收第二通信节点的上行公共控制信道 RRC消息，上行公共控制信道RRC消息携带信令数据；
终端确定模块，设置为若上行公共控制信道RRC消息携带CCCH消息指示，或者，上行公共控制信道RRC消息中不携带上下文相关联的接口连接信息，则根据上行公共控制信道RRC消息携带的信令数据中的I-RNTI确定信令数据所属的终端。
在一实施例中，该装置还包括：
更新消息接收模块，设置为接收第二通信节点的文本更新消息，文本更新消息包含CG资源释放指示或者更新后的CG资源；
上下文控制模块，设置为若文本更新消息包含CG资源释放指示，则根据CG资源释放指示确定第二通信节点侧终端的上下文被释放或者被保持。
在一实施例中，该装置还包括：
信息设置模块，设置为根据CG资源释放指示或者更新后的CG资源，设置RRC释放消息中的CG资源相关信息；
释放消息发送模块，设置为发送RRC释放消息，RRC释放消息用于通知终端释放CG资源或者更新CG资源。
在一实施例中，该装置还包括：
第三RRC消息接收模块，设置为接收第二通信节点的初始上行RRC消息，初始上行RRC消息携带SDT类别信息，SDT类别包括RACH SDT或CG SDT；
CG资源控制模块，设置为若已经配置了CG资源，且SDT类别为RACH SDT，则释放或更新CG资源。
在一实施例中，该装置还包括：
更新请求发送模块，设置为发送终端上下文更新请求，终端上下文更新请求中包含CG资源释放指示或者CG资源更新指示；其中，CG资源释放指示用于指示第二通信节点释放CG资源并保留UE上下文；CG更新指示用于指示DU重新分配并更新CG资源。
本实施例提出的指示装置与上述实施例提出的指示方法属于同一发明构思，未在本实施例中详尽描述的技术细节可参见上述任意实施例，并且本实施例具备与执行指示方法相同的有益效果。
本申请实施例还提供一种数据传输装置。图8为一实施例提供的一种数据传输装置的结构示意图。如图8所示，所述数据传输装置包括：
指示消息接收模块410，设置为接收指示消息，所述指示消息包含终端的上下文相关联的接口连接信息，所述接口连接信息包括第一通信节点对应的终端接口标识和所述第二通信节点对应的终端接口标识。
上下文和接口确定模块420，设置为根据所述接口连接信息确定所述终端的上下文和相关联的保存的接口。
SDT执行模块430，设置为根据所述终端的上下文和所述保存的接口进行SDT。
本实施例的数据传输装置，第二通信节点通过接收第一通信节点的指示信息，根据指示信息中的接口连接信息能够确定终端的上下文和相关联的保存的接口，在此基础上根据终端的上下文和保存的接口进行SDT，以有效利用基站侧的资源。
在一实施例中，该装置还包括：
第一RRC消息发送模块，设置为发送初始上行RRC消息，初始上行RRC消息包含RRC恢复请求消息，RRC恢复请求消息包含I-RNTI。
在一实施例中，指示消息包括以下至少之一：SDT鉴权通过消息；终端上下文建立请求消息；终端上下文修改消息。
在一实施例中，SDT执行模块，具体包括：
传输单元，设置为在接收到终端的SDT业务数据的情况下，根据保存的第一通信节点对应的终端接口和第二通信节点对应的终端接口，通过终端对应的DRB数据传输通道，向第一通信节点传输SDT业务数据。
在一实施例中，该装置还包括：
第二RRC消息发送模块，设置为在接收到终端的信令数据的情况下，发送上行公共控制信道RRC消息，上行公共控制信道RRC消息携带信令数据。
在一实施例中，上行公共控制信道RRC消息还携带CCCH消息指示，或者，上下文相关联的接口连接信息。
在一实施例中，该装置还包括：
更新消息发送模块，设置为发送文本更新消息，文本更新消息包含CG资源释放指示或者更新后的CG资源。
在一实施例中，该装置还包括：
第三RRC消息发送模块，设置为发送初始上行RRC消息，初始上行RRC消息携带SDT类别信息，SDT类别包括RACH SDT或CG SDT。
在一实施例中，该装置还包括：
第一更新请求接收模块，设置为接收终端上下文更新请求，终端上下文更新请求中包含CG资源释放指示；
释放模块，设置为根据CG资源释放指示释放CG资源并保留UE上下文。
在一实施例中，该装置还包括：
第二更新请求接收模块，设置为接收终端上下文更新请求，终端上下文更新请求中包含CG资源更新指示；
CG资源更新模块，设置为根据CG资源更新指示重新分配并更新CG资源；
反馈消息发送模块，设置为发送终端上下文更新请求反馈消息。
本实施例提出的数据传输装置与上述实施例提出的数据传输方法属于同一发明构思，未在本实施例中详尽描述的技术细节可参见上述任意实施例，并且本实施例具备与执行数据传输方法相同的有益效果。
本申请实施例还提供了一种通信节点，该通信节点可以是第一通信节点或第二通信节点，图9为一实施例提供的一种通信节点的硬件结构示意图，如图9所示，本申请提供的通信节点，包括存储器520、处理器510以及存储在存储器上并可在处理器上运行的计算机程序，处理器510执行所述程序时实现上述的指示方法或数据传输方法。
通信节点还可以包括存储器520；该通信节点中的处理器510可以是一个或多个，图9中以一个处理器510为例；存储器520用于存储一个或多个程序；所述一个或多个程序被所述一个或多个处理器510执行，使得所述一个或多个处理器510实现如本申请实施例中所述的指示方法或数据传输方法。
通信节点还包括：通信装置530、输入装置540和输出装置550。
通信节点中的处理器510、存储器520、通信装置530、输入装置540和输出装置550可以通过总线或其他方式连接，图9中以通过总线连接为例。
输入装置540可用于接收输入的数字或字符信息，以及产生与通信节点的用户设置以及功能控制有关的按键信号输入。输出装置550可包括显示屏等显示设备。
通信装置530可以包括接收器和发送器。通信装置530设置为根据处理器510的控制进行信息收发通信。
存储器520作为一种计算机可读存储介质，可设置为存储软件程序、计算 机可执行程序以及模块，如本申请实施例所述指示方法对应的程序指令/模块(例如，指示装置中的上下文确定模块310和指示消息发送模块320)；或者如本申请实施例所述数据传输方法对应的程序指令/模块(例如，数据传输装置中的指示消息接收模块410和上下文、接口确定模块420和SDT执行模块430)。存储器520可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据通信节点的使用所创建的数据等。此外，存储器520可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器520可进一步包括相对于处理器510远程设置的存储器，这些远程存储器可以通过网络连接至通信节点。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
本申请实施例还提供一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现本申请实施例中任一所述的指示方法或数据传输方法。该指示方法，包括：确定终端的上下文；向第二通信节点发送指示消息，所述指示消息包含所述上下文相关联的接口连接信息，所述接口连接信息包括所述第一通信节点对应的终端接口标识和所述第二通信节点对应的终端接口标识，所述接口连接信息用于指示所述第二通信节点使用保存的接口进行SDT。该数据传输方法，包括：接收指示消息，所述指示消息包含终端的上下文相关联的接口连接信息，所述接口连接信息包括第一通信节点对应的终端接口标识和所述第二通信节点对应的终端接口标识；根据所述接口连接信息确定所述终端的上下文和相关联的保存的接口；根据所述终端的上下文和所述保存的接口进行SDT。
本申请实施例的计算机存储介质，可以采用一个或多个计算机可读的介质的任意组合。计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质。计算机可读存储介质例如可以是，但不限于：电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子(非穷举的列表)包括：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机存取存储器(Random Access Memory，RAM)、只读存储器(Read Only Memory，ROM)、可擦式可编程只读存储器(Erasable Programmable Read Only Memory，EPROM)、闪存、光纤、便携式光盘存储器(Compact Disc Read-Only Memory，CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。
计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于：电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。
计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于：无线、电线、光缆、无线电频率(Radio Frequency，RF)等等，或者上述的任意合适的组合。
可以以一种或多种程序设计语言或其组合来编写用于执行本申请操作的计算机程序代码，所述程序设计语言包括面向对象的程序设计语言，诸如Java、Smalltalk、C++，还包括常规的过程式程序设计语言，诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算机上执行、部分地在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算机的情形中，远程计算机可以通过任意种类的网络，包括局域网(Local Area Network，LAN)或广域网(Wide Area Network，WAN)，连接到用户计算机，或者，可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。
以上所述，仅为本申请的示例性实施例而已，并非用于限定本申请的保护范围。
本领域内的技术人员应明白，术语用户终端涵盖任何适合类型的无线用户设备，例如移动电话、便携数据处理装置、便携网络浏览器或车载移动台。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和 功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(Read-Only Memory，ROM)、随机访问存储器(Random Access Memory，RAM)、光存储器装置和系统(数码多功能光碟(Digital Video Disc，DVD)或光盘(Compact Disk，CD)等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field-Programmable Gate Array，FPGA)以及基于多核处理器架构的处理器。

Claims (20)

  1. 一种指示方法，应用于第一通信节点，包括：
    确定终端的上下文；
    向第二通信节点发送指示消息，所述指示消息包含所述上下文相关联的接口连接信息，所述接口连接信息包括所述第一通信节点对应的终端接口标识和所述第二通信节点对应的终端接口标识，所述接口连接信息用于指示所述第二通信节点使用保存的接口进行小数据传输SDT。
  2. 根据权利要求1所述的方法，还包括：
    接收所述第二通信节点的初始上行无线资源控制RRC消息，所述初始上行RRC消息包含RRC恢复请求消息，所述RRC恢复请求消息包含非激活态的无线网络临时标识I-RNTI；
    根据所述I-RNTI识别所述终端；
    对所述终端进行SDT鉴权。
  3. 根据权利要求1所述的方法，其中，所述指示消息包括以下至少之一：
    SDT鉴权通过消息；终端上下文建立请求消息；终端上下文修改消息。
  4. 根据权利要求1所述的方法，还包括：
    接收所述第二通信节点的上行公共控制信道RRC消息，所述上行公共控制信道RRC消息携带信令数据；
    在所述上行公共控制信道RRC消息携带公共控制信道CCCH消息指示，或者，所述上行公共控制信道RRC消息中不携带所述上下文相关联的接口连接信息的情况下，根据所述上行公共控制信道RRC消息携带的信令数据中的I-RNTI确定所述信令数据所属的终端。
  5. 根据权利要求1所述的方法，还包括：
    接收所述第二通信节点的文本更新消息，所述文本更新消息包含配置授权CG资源释放指示或者更新后的CG资源；
    在所述文本更新消息包含所述CG资源释放指示的情况下，根据所述CG资源释放指示确定第二通信节点侧终端的上下文被释放或者被保持。
  6. 根据权利要求5所述的方法，还包括：
    根据所述CG资源释放指示或者所述更新后的CG资源，设置RRC释放消息中的CG资源相关信息；
    发送所述RRC释放消息，所述RRC释放消息用于通知所述终端释放CG资 源或者更新CG资源。
  7. 根据权利要求1所述的方法，还包括：
    接收所述第二通信节点的初始上行RRC消息，所述初始上行RRC消息携带SDT类别的信息，所述SDT类别包括随机接入信道RACH SDT或CG SDT；
    在已经配置了CG资源，且所述SDT类别为RACH SDT的情况下，释放或更新所述CG资源。
  8. 根据权利要求1所述的方法，还包括：
    发送终端上下文更新请求，所述终端上下文更新请求中包含CG资源释放指示或者CG资源更新指示；
    其中，所述CG资源释放指示用于指示所述第二通信节点释放CG资源并保留所述终端的上下文；
    所述CG资源更新指示用于指示所述第二通信节点重新分配并更新CG资源。
  9. 一种数据传输方法，应用于第二通信节点，包括：
    接收指示消息，所述指示消息包含终端的上下文相关联的接口连接信息，所述接口连接信息包括第一通信节点对应的终端接口标识和所述第二通信节点对应的终端接口标识；
    根据所述接口连接信息确定所述终端的上下文和相关联的保存的接口；
    根据所述终端的上下文和所述保存的接口进行小数据传输SDT。
  10. 根据权利要求9所述的方法，还包括：
    发送初始上行无线资源控制RRC消息，所述初始上行RRC消息包含RRC恢复请求消息，所述RRC恢复请求消息包含非激活态的无线网络临时标识I-RNTI。
  11. 根据权利要求9所述的方法，其中，所述指示消息包括以下至少之一：
    SDT鉴权通过消息；终端上下文建立请求消息；终端上下文修改消息。
  12. 根据权利要求9所述的方法，其中，根据所述终端的上下文和所述保存的接口进行SDT，包括：
    在接收到所述终端的SDT业务数据的情况下，根据保存的所述第一通信节点对应的终端接口和所述第二通信节点对应的终端接口，通过所述终端对应的数据无线承载DRB数据传输通道，向所述第一通信节点传输所述SDT业务数据。
  13. 根据权利要求9所述的方法，还包括：
    在接收到所述终端的信令数据的情况下，发送上行公共控制信道RRC消息，所述上行公共控制信道RRC消息携带所述信令数据。
  14. 根据权利要求13所述的方法，其中，
    所述上行公共控制信道RRC消息还携带公共控制信道CCCH消息指示，或者，所述上下文相关联的接口连接信息。
  15. 根据权利要求9所述的方法，还包括：
    发送文本更新消息，所述文本更新消息包含配置授权CG资源释放指示或者更新后的CG资源。
  16. 根据权利要求9所述的方法，还包括：
    发送初始上行RRC消息，所述初始上行RRC消息携带SDT类别的信息，所述SDT类别包括随机接入信道RACH SDT或CG SDT。
  17. 根据权利要求9所述的方法，还包括：
    接收终端上下文更新请求，所述终端上下文更新请求中包含CG资源释放指示；
    根据所述CG资源释放指示释放CG资源并保留所述终端的上下文。
  18. 根据权利要求9所述的方法，还包括：
    接收终端上下文更新请求，所述终端上下文更新请求中包含CG资源更新指示；
    根据所述CG资源更新指示重新分配并更新CG资源；
    发送终端上下文更新请求反馈消息。
  19. 一种通信节点，包括存储器、处理器以及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述程序时实现如权利要求1-8中任一所述的指示方法或如权利要求9-18中任一所述的数据传输方法。
  20. 一种计算机可读存储介质，其上存储有计算机程序，其中，所述计算机程序被处理器执行时实现如权利要求1-8中任一所述的指示方法或如权利要求9-18中任一所述的数据传输方法。
PCT/CN2022/134052 2021-12-24 2022-11-24 指示方法、数据传输方法、通信节点及存储介质 WO2023116336A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020247012051A KR20240053075A (ko) 2021-12-24 2022-11-24 지시 방법, 데이터 전송 방법, 통신 노드 및 저장 매체

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111599622.7A CN115942508A (zh) 2021-12-24 2021-12-24 指示方法、数据传输方法、通信节点及存储介质
CN202111599622.7 2021-12-24

Publications (1)

Publication Number Publication Date
WO2023116336A1 true WO2023116336A1 (zh) 2023-06-29

Family

ID=86549435

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/134052 WO2023116336A1 (zh) 2021-12-24 2022-11-24 指示方法、数据传输方法、通信节点及存储介质

Country Status (3)

Country Link
KR (1) KR20240053075A (zh)
CN (1) CN115942508A (zh)
WO (1) WO2023116336A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110139386A (zh) * 2018-02-08 2019-08-16 电信科学技术研究院有限公司 一种上行小数据的传输方法、网络侧du和网络侧cu
CN111294982A (zh) * 2018-12-10 2020-06-16 华为技术有限公司 通信方法和通信装置
CN111345074A (zh) * 2017-11-17 2020-06-26 瑞典爱立信有限公司 与ue非活动有关的方法、装置和系统
WO2021026706A1 (zh) * 2019-08-09 2021-02-18 华为技术有限公司 一种f1接口管理方法及装置
WO2021134728A1 (zh) * 2019-12-31 2021-07-08 华为技术有限公司 一种上下文管理方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111345074A (zh) * 2017-11-17 2020-06-26 瑞典爱立信有限公司 与ue非活动有关的方法、装置和系统
CN110139386A (zh) * 2018-02-08 2019-08-16 电信科学技术研究院有限公司 一种上行小数据的传输方法、网络侧du和网络侧cu
CN111294982A (zh) * 2018-12-10 2020-06-16 华为技术有限公司 通信方法和通信装置
WO2021026706A1 (zh) * 2019-08-09 2021-02-18 华为技术有限公司 一种f1接口管理方法及装置
WO2021134728A1 (zh) * 2019-12-31 2021-07-08 华为技术有限公司 一种上下文管理方法及装置

Also Published As

Publication number Publication date
KR20240053075A (ko) 2024-04-23
CN115942508A (zh) 2023-04-07

Similar Documents

Publication Publication Date Title
US11115893B2 (en) Information transmission method, base station, and user equipment
US20200383035A1 (en) Communications method and apparatus
US11510175B2 (en) Method and device for sending uplink data by an inactive terminal
CN111901847A (zh) sidelink中继通信方法、装置、设备及介质
EP3911019B1 (en) Communication method and apparatus
US20220201539A1 (en) Method for obtaining data radio bearer identifier and base station
US10560929B2 (en) Resource request method and system, device, and network side node
CN110649997B (zh) 数据处理方法及装置
JP7157813B2 (ja) Ｒｒｃ状態遷移方法、端末、ｃｕ、ｄｕ、およびコンピュータ可読記憶媒体
EP3709686B1 (en) Data transmission control method and related product
WO2019076060A1 (zh) 数据转发方法、装置和系统
WO2017133295A1 (zh) 数据传输方法、装置和系统
US20220248290A1 (en) Communication Method and Communications Apparatus
WO2021134728A1 (zh) 一种上下文管理方法及装置
WO2023116336A1 (zh) 指示方法、数据传输方法、通信节点及存储介质
CN113973366A (zh) 一种信息处理方法、终端、设备和可读存储介质
WO2022206618A1 (zh) 一种通信方法及装置
CN110324857B (zh) 一种业务质量数据流的处理方法和装置
WO2023093605A1 (zh) 信息传输方法、终端及网络设备
JP2020522950A (ja) 通信方法、装置、およびシステム
WO2023134332A1 (zh) 一种通信方法及系统
KR20240076847A (ko) 통신 방법, 장치 및 시스템
CN115915386A (zh) 一种注册方法、终端设备、核心网设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22909651

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022909651

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20247012051

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2022909651

Country of ref document: EP

Effective date: 20240329