Methods, apparatus, and computer program products for wireless communication

Abstract

A method, device, and computer program product for wireless communication are provided, the method including: transmitting, by a first wireless communication node, a control message to a second wireless communication node to control the second wireless communication node to instruct the wireless communication terminal to enter a radio resource control (RRC) inactive mode; and transmitting at least one small data transmission (SDT) configuration to the wireless communication terminal.

Description

Technical Field

[0001] This document generally relates to wireless communication.

Background Art

[0002] In the new radio (NR) of 5G communication, a UE (user equipment) can enter the RRC_INACTIVE (inactive) state / mode (also referred to as the INACTIVE state / mode in the following paragraphs) to reduce power consumption. Normally, in the RRC_INACTIVE state, the UE cannot send data. Therefore, the UE has to resume the connection for downlink (e.g., mobile terminal (MT)) and uplink (e.g., mobile origin (MO)) data (i.e., return to the RRC_CONNECTED (connected) state). However, in the case of small-scale and rare data transmissions, it is inefficient and power-consuming to establish and release the connection every time transmission is required.

[0003] Therefore, a method for small data transmission in the RRC_INACTIVE state, as well as related configurations for the network node and the UE, are required.

Summary of the Invention

Problems to be Solved by the Invention

[0004] The present disclosure relates to a method, a device, and a computer program product for wireless communication that can enable a UE to perform small data transmission (SDT).

Means for Solving the Problems

[0005] One aspect of the present disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes the steps of: having a first wireless communication node transmit a control message to a second wireless communication node to control the second wireless communication node to instruct a wireless communication terminal to enter a wireless resource control RRC inactive mode; and transmitting at least one small data transmission SDT configuration to the wireless communication terminal.

[0006] Another aspect of the present disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes the steps of: a second wireless communication node receiving a control message from a first wireless communication node; the second wireless communication node transmitting an RRC message included in the control message from the first wireless communication node to a wireless communication terminal; and the second wireless communication node refraining from releasing information related to the wireless communication terminal in accordance with the control message.

[0007] Another aspect of the present disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes the steps of: a wireless communication terminal receiving an interruption instruction from a second wireless communication node or a third wireless communication and entering a radio resource control RRC inactive mode in accordance with the interruption instruction; and a wireless communication terminal receiving at least one small data transmission SDT configuration from the second wireless communication node or the third wireless communication.

[0008] Another aspect of the present disclosure relates to a wireless communication node. In one embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to send control messages to a second wireless communication node in order to instruct a wireless communication terminal to enter a radio resource control (RRC) inactive mode and to control the second wireless communication node to transmit at least one small data transmission (SDT) configuration to the wireless communication terminal.

[0009] Another aspect of the present disclosure relates to a wireless communication node. In one embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to receive a control message from a first wireless communication node, transmit an RRC message contained in the control message from the first wireless communication node to a wireless communication terminal, and refrain from releasing information related to the wireless communication terminal in accordance with the control message.

[0010] Another aspect of the present disclosure relates to a wireless communication terminal. In one embodiment, the wireless communication terminal includes a communication unit and a processor. The processor is configured to receive an interruption instruction from a second wireless communication node or a third wireless communication, enter a radio resource control RRC inactive mode in accordance with the interruption instruction, and receive at least one small data transmission SDT configuration from the second wireless communication node or the third wireless communication.

[0011] Various embodiments can preferably implement the following features: Preferably, the control message comprises an RRC message which includes an SDT configuration and an interruption instruction which causes the wireless communication terminal to enter RRC inactive mode, and the second wireless communication node is configured to transparently forward this RRC message to the wireless communication terminal.

[0012] Preferably, the control message includes an information element to prevent the second wireless communication node from releasing information related to the wireless communication terminal.

[0013] Preferably, information related to the wireless communication terminal is used for SDT between the wireless communication terminal and the second wireless communication node.

[0014] Preferably, the information related to the wireless communication terminal includes at least one of the following: at least one radio link control RLC entity for SDT between the wireless communication terminal and the second wireless communication node, at least one RLC bearer configuration for SDT between the wireless communication terminal and the second wireless communication node, or at least one downlink cell group CG transport network layer TNL for SDT between the wireless communication terminal and the second wireless communication node.

[0015] Preferably, the control message comprises an RRC message, which comprises at least one SDT timer or at least one SDT duration indicating the available time for at least one SDT configuration.

[0016] Preferably, the first wireless communication node is configured to send a request message to the second wireless communication node requesting SDT resources.

[0017] Preferably, the first wireless communication node is configured to receive a response message from the second wireless communication node indicating the result of the request for an SDT resource.

[0018] Preferably, the response message includes at least one SDT timer or at least one SDT duration indicating the available time for at least one SDT configuration.

[0019] Preferably, the first wireless communication node is configured to obtain information about the SDT resources of the second wireless communication node by sending an SDT resource inquiry request to the second wireless communication node.

[0020] Preferably, the first wireless communication node is configured to receive requests from the wireless communication terminal for SDT resources for the wireless communication terminal.

[0021] Preferably, the first wireless communication node is configured to receive, from the second wireless communication node, a configuration completion message indicating that the SDT resources are configured and the wireless communication terminal enters the RRC inactive mode.

[0022] Preferably, the SDT configuration includes at least one of at least one SDT resource, at least one SDT index, at least one SDT duration or SDT timer, or at least one SDT indicator.

[0023] Preferably, the SDT configuration is used for SDT between the wireless communication terminal and the second wireless communication node.

[0024] Preferably, the RRC message is an RRC release message or an RRC reconfiguration message.

[0025] Preferably, the second wireless communication node is configured to receive, from the first wireless communication node, a request message requesting SDT resources.

[0026] Preferably, the second wireless communication node is configured to send, to the first wireless communication node, a response message indicating the result of the request for SDT resources.

[0027] Preferably, the second wireless communication node is configured to send, to the first wireless communication node, a configuration completion message indicating that at least one SDT resource is configured and the wireless communication terminal enters the RRC inactive mode.

[0028] Preferably, the second wireless communication node or the third wireless communication is configured to hold information related to the wireless communication terminal during the transmission of the interruption indication.

[0029] Preferably, the SDT configuration and the interruption indication are received in an RRC message from the second wireless communication node.

[0030] Preferably, the wireless communication terminal is further configured to receive at least one SDT timer or at least one SDT duration indicating the available time of at least one SDT configuration.

[0031] Preferably, the wireless communication terminal is further configured to run an SDT timer and, in response to the expiration of the SDT timer, discard the corresponding SDT configuration.

[0032] Preferably, the wireless communication terminal is further configured to transmit a request to a first wireless communication node or a third wireless communication node requesting at least one SDT resource or configuration of the wireless communication terminal.

[0033] Preferably, the wireless communication terminal is further configured to determine the hypersystem frame number H-SFN for initiating an SDT opportunity according to the following formula.

[0034] H-SFN = (H-SFN_Ref + offset) mod 1024 FLOOR(offset / 1024) occurs after the H-SFN cycle. Here, H-SFN_Ref is the H-SFN reference, mod is the modulus function, and FLOOR is the floor function.

[0035] Preferably, the wireless communication terminal is further configured to determine the system frame number SFN, subframe, slot, or OFDM for initiating an SDT opportunity according to the SDT configuration.

[0036] This disclosure relates to a computer program product including stored computer-readable program medium code, wherein, when executed by a processor, the code causes the processor to perform one of the wireless communication methods described above.

[0037] The exemplary embodiments disclosed herein are intended to provide features that will be readily apparent by referring to the following description in conjunction with the accompanying drawings. Various embodiments disclose exemplary systems, methods, devices, and computer program products. However, it should be understood that these embodiments are presented as examples and not as limitations, and it will be apparent to those skilled in the art who have read this disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of this disclosure.

[0038] Therefore, this disclosure is not limited to the exemplary embodiments and uses described and illustrated herein. Furthermore, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of this disclosure. Accordingly, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or operations in a sample order, and that this disclosure is not limited to the specific order or hierarchy presented unless otherwise specified.

[0039] The above and other aspects and their embodiments will be described in more detail in the drawings, description and claims. [Brief explanation of the drawing]

[0040] [Figure 1] A flowchart of a wireless communication method according to one embodiment of this disclosure is shown. [Figure 2] A flowchart of another wireless communication method according to one embodiment of the present disclosure is shown. [Figure 3] A flowchart of another wireless communication method according to one embodiment of the present disclosure is shown. [Figure 4] A flowchart of another wireless communication method according to one embodiment of the present disclosure is shown. [Figure 5] A flowchart of another wireless communication method according to one embodiment of the present disclosure is shown. [Figure 6]A flowchart of another wireless communication method according to one embodiment of the present disclosure is shown. [Figure 7] An example of a schematic diagram of a wireless communication terminal according to one embodiment of the present disclosure is shown. [Figure 8] An example of a schematic diagram of another wireless communication node according to another embodiment of this disclosure is shown. [Modes for carrying out the invention]

[0041] Some terms used in this disclosure are defined below. SDT: Small Data Transmission or Specific Data Transmission SDT Resources: An SDT resource can be one of the following: a pre-configured UL resource (PUR), a configured grant resource (CG), or any other pre-configured resource.

[0042] SDT Configuration: An SDT configuration may include at least one of the following: at least one SDT resource, at least one SDT index, at least one SDT duration or SDT timer, or at least one SDT indicator.

[0043] According to one embodiment of the present disclosure, after receiving an RRC message from a user device (UE) requesting a Small Data Transmission (SDT) configuration, the gNB-CU (gNodeB Central Unit) can initiate an F1AP (F1 Application Protocol) procedure for SDT configuration (e.g., a UE context change procedure). If the SDT configuration request is successful, the gNB-DU (gNodeB Distributed Unit) can send the result of the SDT request to the gNB-CU and retain the UE context and DL (Downlink) CG (Cell Group) TNL (Transport Network Layer) address. Furthermore, the gNB-DU can execute an SDT timer for UL data transmission according to the SDT resources.

[0044] In 5G New Radio (NR) communication, the User Equipment (UE) can enter the RRC_INACTIVE state to reduce power consumption. Normally, in the RRC_INACTIVE state, the UE cannot transmit data. Therefore, the UE must re-establish connections for downlink (e.g., mobile terminal (MT)) and uplink (e.g., source (MO)) data (i.e., return to the RRC_CONNECTED state). However, for small, infrequent data transmissions, establishing and releasing a connection each time transmission is required is inefficient and power-consuming. Additionally, signaling overhead is incurred.

[0045] Signaling overhead in the UE's inactive state for Small Data Transmission (SDT) is a problem in 5G communications. Generally, devices that need to send or receive small data packets in the inactive state can benefit from adopting small data transmission in the inactive state.

[0046] There are several techniques that can be employed for SDT in an inactive state, such as 2-step RACH (Random Access Channel), 4-step RACH, and configuration grant type-1 (CG type-1). Some embodiments of this disclosure can be implemented based on these techniques.

[0047] If the RRC_INACTIVE state is present: 1) UL small data transmission for RACH-based schemes (i.e., 2-step and 4-step RACH) is: General procedure for enabling UP (User Plane) data transmission for small data packets from an INACTIVE state (e.g., using MsgA or Msg3), The INACTIVE state of MsgA and Msg3 allows for a more flexible payload size than the currently possible Rel-16CCCH message size to support UP data transmission in UL (actual payload size may depend on network configuration), and Context fetch and data transfer in an inactive state for RACH-based solutions (with and without anchor relocation).

[0048] Please note that the security aspects of the above operations can be checked by the 3GPP® Security Working Group (SA3).

[0049] 2) Transmitting UL data over a pre-configured PUSCH (Physical Uplink Shared Channel) resource (i.e., reusing configuration grant type 1) (for example, if TA (Timing Advance) is enabled) General procedure for sending small data via a configured grant type 1 resource from an INACTIVE state, and Configuration of a grant type 1 resource for small data transmission in an INACTIVE state UL. 3) Specify the RRM (Radio Resource Management) core requirements for small data transmission in RRC_INACTIVE, if necessary.

[0050] The configuration of a CG type 1 resource that is valid in the INACTIVE state may be provided to the UE before the UE enters the INACTIVE state, and the CG resource configuration is only valid in the cell in which the UE enters the INACTIVE state.

[0051] In addition, configurations stored within the UE context may be used for RLC (Radio Link Control) bearer configurations for different SDT mechanisms (e.g., RACH or CG). CG can transmit UL small data using pre-configured PUSCH resources (i.e., pre-configured UL SDT resources).

[0052] Under a CU / DU partitioned architecture, several behaviors for SDT may be employed, including the following:

[0053] 1) The UE and CU-CP (Control Plane) remember the UE context when the UE transitions to (e.g., enters) the RRC_INACTIVE state.

[0054] 2) When the UE transitions to the RRC_INACTIVE state, the DU releases the stored UE context, and a corresponding tunnel is established between the DU and the CU-UP (user plane).

[0055] 3) CU-UP keeps the UE context in a suspended state when the UE is in the RRC_INACTIVE state.

[0056] This disclosure provides a method for maintaining the UE context in the gNB-DU when the UE enters an INACTIVE state.

[0057] One embodiment of this disclosure will be described with reference to Figure 1. In operation 0, the UE is in RRC connection mode. Both the UE and the cell servicing the UE support SDT functionality.

[0058] In operation 1, the UE may notify the gNB-CU that it wishes to be configured with SDT by sending an RRC message (e.g., an SDT ConfigurationRequest message). In one embodiment, the RRC message may include SDT request information regarding the requested resource (e.g., occurrence count, periodicity, time offset, TBS (transport block size), RRC Ack, etc.). In one embodiment, operation 1 is optional.

[0059] In one embodiment, the UE may consist of one SDT or a set of SDTs that include multiple SDT resources.

[0060] In one embodiment, the UE may consist of a DRB (Data Radio Bearer) based SDT. That is, the UE may consist of an SDT for each DRB that supports an SDT. In other words, if there are multiple DRBs that support an SDT, a corresponding number of SDTs can be configured, and each PDU (Protocol Data Unit) is used for each DRB.

[0061] In operation 1.2, the UE may request the gNB-CU to further modify or release the configured SDT by using another RRC message (e.g., SDT ConfigurationRequest).

[0062] In one embodiment, the gNB-CU (or gNB) can respond to an RRC message (e.g., an SDT resource request message) with an RRC message (i.e., an acknowledgment of the SDT resource request).

[0063] In operation 2, the gNB-CU decides to transition the UE to RRC_INACTIVE mode.

[0064] In operation 3, the gNB-CU sends an F1AP message (i.e., the first message) to the gNB-DU to initiate the F1AP procedure and request SDT configuration.

[0065] This F1AP procedure is used to request SDT resources. This F1AP procedure can be implemented by adding new IEs (information elements) (e.g., IE "SDT configuration request" and IE "SDT configuration response"), or by using a newly defined F1AP procedure (e.g., an SDT configuration procedure that includes SDT configuration request and SDT configuration response messages), or by modifying an existing UE context change procedure.

[0066] Accordingly, the first message of operation 3 may be a UE context modification request message containing IE "SDT configuration request", or it may be an SDT configuration request message.

[0067] In this disclosure, the SDT configuration procedure can be considered a modification of the UE context change procedure, and it should be noted that the terms SDT configuration procedure and UE context change procedure may be used instead.

[0068] In operation 4, the gNB-DU sends a second message to the gNB-CU to communicate the SDT configuration result.

[0069] The second message may be either a UE context change response message containing IE "SDT configuration result / request" or an SDT configuration response message, based on the format of the first message.

[0070] The gNB-DU is supposed to send failure information to the gNB-CU if it fails to successfully configure the SDT. For example, the failure information may be a UE context modification failure message containing a cause value (e.g., SDT configuration failure) or an SDT configuration failure message containing a cause value (e.g., SDT configuration failure), based on the format of the first message.

[0071] Optionally, an SDT configured by a gNB-DU may be a single SDT or a set of SDTs containing multiple SDT resources.

[0072] Optionally, each SDT resource can be configured with a specific SDT timer / duration, or a set of SDT resources can be configured with a common SDT timer / duration. The SDT timer / duration is set by the gNB-DU and forwarded to the UE in the RRC message and used to indicate the availability of the SDT. Each SDT timer is used to indicate whether one SDT is available. After one SDT or set of SDTs has been successfully configured, the gNB-DU can start the corresponding SDT timer. The corresponding SDT is available and can be used by the UE until the SDT timer expires. After the SDT timer expires, the corresponding SDT is no longer available and can be discarded.

[0073] In operation 5, the gNB-CU initiates the F1AP procedure and sends a third message (for example, a UE context modification request message or a UE context release command message) to the gNB-DU.

[0074] This F1AP procedure is used to instruct the gNB-DU to command the UE to switch from RRC connected mode to RRC inactive mode, and to forward an RRC release message to the UE to communicate any SDT configurations, if any.

[0075] The RRC release message is generated by the gNB-CU and may include a suspension instruction and SDT resources, and optionally may include at least one SDT timer if an SDT timer is configured.

[0076] This F1AP procedure can be implemented by modifying the UE context change procedure or by using the UE context release procedure.

[0077] If the UE context release procedure is modified, the third message may be a UE context release command message containing an IE instructing the gNB-DU not to release any stored UE-related information. Furthermore, the third message may include an RRC release message containing the SDT configuration.

[0078] In some methods, UE-related information stored in the gNB-DU (i.e., the UE context stored in the gNB-DU) can be released when the UE context release command message is released. UE-related information can be retained in the gNB-DU by instructing the gNB-DU not to release it.

[0079] When using the UE context modification procedure, the third message is a UE context modification request message. The third message may include an RRC release message containing the SDT configuration. In this case, since the gNB-DU does not release the UE-related information in accordance with the UE context modification request message, an IE instructing the gNB-DU not to release the UE-related information is not required. In some embodiments, the gNB-DU may be configured to hold only the UE-related information related to the SDT.

[0080] The entire UE context is stored in the gNB-CU, while the gNB-DU stores a portion of the UE context. This portion of the UE context is called the UE-related information stored in the gNB-DU (i.e., the UE context stored in the gNB-DU).

[0081] Upon receiving the third message, the gNB-DU may continue to store all or part of the UE-related information in order to support the resulting UL or DL ​​SDT.

[0082] In some embodiments, the gNB-DU may hold at least one of the following:

[0083] 1) At least one RLC entity for SDT, 2) At least one RLC bearer configuration for SDT, or 3) At least one DL CG TNL address for SDT In operation 6, the gNB-DU sends an RRC release message to the UE.

[0084] In operation 7, gNB-DU sends either a UE context modification response message or a UE context release complete message to the UE based on the format of the third message.

[0085] Note that the order of operations 6 and 7 may be reversed, or operations 6 and 7 may be executed in parallel.

[0086] In operation 8, the UE enters the RRC_INACTIVE state and stores the SDT configuration.

[0087] Note that in alternative embodiments, RRC reconfiguration messages can be used to replace the RRC release messages described above and below.

[0088] Other embodiments of this disclosure will be described with reference to Figure 2. Operations 0 to 2 in this embodiment are the same as operations 0 to 2 in the embodiment corresponding to Figure 1, and therefore the same explanation will not be repeated here.

[0089] In operation 3, the gNB-CU initiates the F1AP procedure and sends a fourth message (for example, a UE context modification request message or a UE context release command message) to the gNB-DU.

[0090] When gNB-CU attempts to configure SDT resources for a UE, it can obtain information about available SDT resources within gNB-DU beforehand (i.e., the SDT resources can be used in gNB-DU). Then, gNB-CU can configure the appropriate SDT resources for the UE.

[0091] There are several ways for gNB-CU to obtain information about available SDT resources within gNB-DU in advance.

[0092] In one embodiment, prior to operation 3, the gNB-CU may use a UE-related F1AP procedure (e.g., a UE context change procedure) along with an SDT resource query to request information about the SDT resource, and obtain the requested information in a response message.

[0093] In another embodiment, prior to operation 3, the gNB-CU may use a non-UE related F1AP procedure (e.g., gNB-DU configuration update message, gNB-DU status instruction, resource status report start procedure) along with the SDT resource query to request information about the SDT resource, and obtain the requested information in the response message.

[0094] This F1AP procedure is used to instruct the gNB-DU to instruct the UE to switch from RRC connected mode to RRC inactive mode, to forward an RRC release message to the UE, and to forward any SDT resources configured by the gNB-CU to the UE.

[0095] The RRC release message is generated by the gNB-CU and may include a suspension instruction and SDT resources, and may optionally include at least one SDT timer if configured.

[0096] This F1AP procedure can be implemented by modifying the UE context change procedure or by using the UE context release procedure.

[0097] If the UE context release procedure is changed, the fourth message may be a UE context release command message containing an IE instructing the gNB-DU not to release any stored UE-related information. Furthermore, the third message may include an RRC release message containing the SDT configuration.

[0098] In some methods, UE-related information stored in the gNB-DU (i.e., the UE context stored in the gNB-DU) can be released when the UE context release command message is released. UE-related information can be retained in the gNB-DU by instructing the gNB-DU not to release it.

[0099] When using the UE context modification procedure, the fourth message is a UE context modification request message. The fourth message may include an RRC release message containing the SDT resource configuration. In this case, the fourth message instructs the gNB-DU not to release any UE-related information that is not needed, because the gNB-DU does not release UE-related information in accordance with the UE context modification request message. In some embodiments, the gNB-DU may be configured to hold only UE-related information related to the SDT.

[0100] The entire UE context is stored in the gNB-CU, and the gNB-DU stores a portion of the UE context, which is called the UE-related information stored in the gNB-DU (i.e., the UE context stored in the gNB-DU).

[0101] Upon receiving the fourth message, the gNB-DU may continue to store all or part of the UE-related information in order to support the resulting UL / DL SDT.

[0102] Unlike the embodiment corresponding to Figure 1, in this embodiment, the fourth message sent to the gNB-DU (either a UE context modification request message or a UE context release command message) may include additional IEs (e.g., SDT resource configurations) which are the same IEs as those in the RRC release message. Upon receiving the fourth message, the gNB-DU may retain the corresponding SDT resources indicated by the fourth message for the SDT using the UE (e.g., after the UE enters RRC INACTIVE mode).

[0103] In some embodiments, the gNB-DU may hold at least one of the following:

[0104] 1) At least one RLC entity for SDT, 2) At least one RLC bearer configuration for SDT, or 3) At least one DL CG TNL address for SDT Operations 4 to 6 in this embodiment are the same as operations 6 to 8 in the embodiment corresponding to Figure 1, and therefore the same explanation will not be repeated here.

[0105] Comparing the embodiment corresponding to Figure 1 (Embodiment A) with the embodiment corresponding to Figure 2 (Embodiment B), 1) Embodiment B has shorter latency. In Embodiment B, the gNB-CU can configure the SDT resources without requesting them from the gNB-DU, thus allowing some messages to be omitted.

[0106] 2) In Embodiment B, the gNB-CU may need to acknowledge the SDT resource information in advance. Otherwise, the gNB-CU may not be able to create the appropriate configuration.

[0107] 3) Since SDT resources are stored in the gNB-DU, and the gNB-DU can have the most accurate and up-to-date SDT resource information (e.g., availability, wireless status, etc.), the embodiment is simpler and the gNB-DU can be configured better than the gNB-CU.

[0108] Other embodiments of this disclosure will be described with reference to Figure 3. In operation 1, the gNB-CU receives an RRC message (i.e., an SDT Configuration Request message) from the UE. This RRC message contains a request for SDT configuration. Details of the SDT configuration can be found by referring to the embodiments described above and will not be repeated here. In one embodiment, operation 1 is optional.

[0109] In operation 1-2, the gNB-CU receives one or more RRC messages from the UE. These RRC messages may request an SDT change or SDT release. In one embodiment, operation 1-2 is optional.

[0110] In operation 2, the gNB-CU decides to transition the UE to the RRC INACTIVE state.

[0111] In operation 3, the gNB-CU determines whether an SDT configuration is required. If it is required, operation 4 is performed. If it is not required, operation 4c is performed, and the gNB-CU sends a UE context release command to the gNB-DU, which includes the RRC release message described above.

[0112] In operation 4, the gNB-CU sends the first message described above (for example, a UE context modification request message) to the gNB-DU to request SDT configuration.

[0113] In operation 5, 5a, or 5b, the gNB-CU receives a second message containing information about the successfully configured SDT resource (e.g., a UE context modification response message) or a failure message containing the cause of the failure (e.g., a UE context modification failure message). Note that in the case of embodiment B described above, operations 5, 5a, and 5b may be omitted.

[0114] In operation 6a or 6b, the gNB-CU sends a third message to the gNB-DU in the format of a UE context modification request message. The third message includes an RRC release message, which includes a suspend indicator and, if any, an SDT configuration. Alternatively, the gNB-CU sends a third message to the gNB-DU in the format of a UE context release command message. In this case, the third message includes an instruction to the gNB-DU to retain UE-related information and, if any, an SDT configuration.

[0115] In operation 7a, 7b, or 5c, the gNB-CU receives a response message from the gNB-DU (for example, a UE context modification response message or a UE context release complete message).

[0116] Other embodiments of this disclosure will be described with reference to Figure 4. In operation 1, the gNB-DU receives a third message from the gNB-CU containing SDT configuration request information (for example, a UE context modification request message).

[0117] In operation 2, the gNB-DU determines whether the SDT configuration request can be satisfied (e.g., whether the SDT resources can be successfully configured). If it can be satisfied, operation 3a is performed, and the gNB-DU sends a response message (e.g., a UE context modification response message) containing the configured SDT resources to the gNB-CU. If it cannot be satisfied, operation 3b is performed, and the gNB-DU sends a failure message (e.g., a UE context modification failure message) containing the cause of the failure to the gNB-CU.

[0118] If the SDT resource can be configured successfully, the UE context change response message sent by the gNB-DU may include the corresponding SDT timer.

[0119] If an SDT timer is configured, the gNB-DU executes the SDT timer. The gNB-DU can store the information of the corresponding SDT and execute the corresponding SDT until the SDT timer expires. After the SDT timer expires, the gNB-DU can discard the information of the corresponding SDT.

[0120] Other embodiments of this disclosure will be described with reference to Figure 5. In operation 1, the gNB-DU receives a third or fourth message (e.g., a UE context modification request message) from the gNB-CU. The third or fourth message includes an RRC message.

[0121] In operation 2, the gNB-DU sends the RRC message included in the UE context modification request message to the UE and the UE context modification response message to the gNB-CU.

[0122] From the perspective of the gNB-DU, it does not decode the RRC message, but simply forwards the RRC message transparently to the UE.

[0123] Other embodiments of this disclosure will be described with reference to Figure 6. In operation 1, the gNB-DU receives a UE context release command message and an RRC message from the gNB-CU.

[0124] In operation 2, if the UE context release command message contains an instruction to retain UE-related information, operation 3a is performed. Otherwise, operation 3b is performed.

[0125] In operation 3a, the gNB-DU holds UE-related information, sends an RRC message to the UE, and sends a UE context release completion message to the gNB-CU.

[0126] In operation 3b, the gNB-DU sends an RRC message to the UE and a UE context release completion message to the gNB-CU.

[0127] From the perspective of the gNB-DU, it does not decode the RRC message, but simply forwards the RRC message transparently to the UE.

[0128] In one embodiment of this disclosure, the UE can perform the following actions. In operation 0, the UE is in RRC connection mode, and the corresponding cell and UE support SDT functionality.

[0129] In operation 1, optionally, the UE sends an RRC message (e.g., an SDT ConfigurationRequest message) to the gNB or gNB-CU to request SDT configuration.

[0130] In operation 1-2, optionally, the UE sends one or more other RRC messages to the gNB-CU to request an SDT change or SDT release.

[0131] In operation 1a, the UE may optionally receive an RRC message (confirm SDT ConfigurationRequest message) from the gNB or gNB-CU.

[0132] In operation 2, the UE receives an RRC release message that includes the SDT configuration. Details of the SDT configuration can be found by referring to the paragraph above.

[0133] In operation 3, the UE is in the RRC INACTIVE state, and the UE can transmit data based on the SDT configuration.

[0134] In one embodiment, if the SDT configuration includes an SDT timer or SDT duration, the UE may transmit data based on the SDT configuration before the timer or duration expires. After the SDT timer / duration expires, the UE does not transmit data based on the SDT configuration.

[0135] In one embodiment, the UE stores information about the UE context and the SDT resource. If the SDT resource includes an SDT timer or duration, the UE stores and uses the SDT duration, or executes the SDT timer.

[0136] The SDT timer / duration is transmitted by the gNB-CU or gNB and is used to indicate the availability of the SDT. Each SDT may have two or more timers / durations.

[0137] In one embodiment, the UE is configured to determine the hypersystem frame number (H-SFN) for initiating an SDT opportunity according to the following formula:

[0138] H-SFN = (H-SFN_Ref + offset) mod 1024 FLOOR(offset / 1024) occurs after the H-SFN cycle. H-SFN_Ref is the H-SFN reference, mod is the modulus function, and FLOOR is the floor function.

[0139] In one embodiment, the UE is further configured to determine a system frame number SFN, subframe, slot, or OFDM for initiating an SDT opportunity according to the SDT configuration.

[0140] Figure 7 relates to a schematic diagram of a wireless communication terminal 40 (e.g., a terminal node or terminal device) according to one embodiment of the present disclosure. The wireless communication terminal 40 may be, but is not limited herein, a user device (UE), a mobile phone, a laptop, a tablet computer, an e-reader, or a portable computer system. The wireless communication terminal 40 may include a processor 400, such as a microprocessor or an application-specific integrated circuit (ASIC), a storage unit 410, and a communication unit 420. The storage unit 410 may be any data storage device that stores program code 412 accessed and executed by the processor 400. Embodiments of the storage code 412 include, but are not limited to, a subscriber identification module (SIM), read-only memory (ROM), flash memory, random access memory (RAM), a hard disk, and an optical data storage device. The communication unit 420 may be a transceiver and is used to send and receive signals (e.g., messages or packets) according to the processing results of the processor 400. In one embodiment, the communication unit 420 sends and receives signals via at least one antenna 422.

[0141] In one embodiment, the storage unit 410 and the program code 412 may be omitted, and the processor 400 may include a storage unit having the stored program code.

[0142] The processor 400 may, for example, perform any of the steps in the illustrated embodiment at the wireless communication terminal 40 by executing program code 412.

[0143] The communication unit 420 may be a transceiver. The communication unit 420 may also be a combination of a transmitting unit and a receiving unit configured to transmit and receive signals to and from a wireless communication node, respectively, either alternatively or additionally.

[0144] In some embodiments, the wireless communication terminal 40 may be used to perform the operations of the UE described above. In some embodiments, the processor 400 and the communication unit 420 cooperate to perform the operations described above. For example, the processor 400 performs operations to transmit or receive signals, messages, and / or information via the communication unit 420.

[0145] Figure 8 shows a schematic diagram of a wireless communication node 50 (e.g., a network device) according to one embodiment of the present disclosure. The wireless communication node 50 may be, but is not limited herein, a satellite, a base station (BS) (e.g., a gNB-CU or gNB-DU), a network entity, a mobility management entity (MME), a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a radio access network (RAN), a next-generation RAN (NG-RAN), a data network, a core network, or a wireless network controller (RNC). Furthermore, the wireless communication node 50 may include (perform) at least one network function, such as an access and mobility management function (AMF), a session management function (SMF), a user place function (UPF), a policy control function (PCF), or an application function (AF). The wireless communication node 50 may include a processor 500 such as a microprocessor or ASIC, a storage unit 510, and a communication unit 520. The storage unit 510 may be any data storage device that stores program code 512 accessed and executed by the processor 500. Examples of the storage unit 512 include, but are not limited to, SIM, ROM, flash memory, RAM, hard disk, and optical data storage device. The communication unit 520 may be a transceiver and is used to send and receive signals (e.g., messages or packets) according to the processing results of the processor 500. In one example, the communication unit 520 sends and receives signals via at least one antenna 522.

[0146] In one embodiment, the storage unit 510 and the program code 512 may be omitted. The processor 500 may include a storage unit having the stored program code.

[0147] The processor 500 may perform any of the steps described in the illustrated embodiment at the wireless communication node 50, for example, by executing program code 512.

[0148] The communication unit 520 may be a transceiver. The communication unit 520 may also be combined with a transmitting unit and a receiving unit configured to transmit and receive signals, messages, or information to and from a wireless terminal (e.g., user equipment), either alternatively or additionally.

[0149] In some embodiments, the wireless communication node 50 may be used to perform the operations of the gNB-CU or gNB-DU described above. In some embodiments, the processor 500 and the communication unit 520 cooperate to perform the operations described above. For example, the processor 500 performs an operation to transmit or receive a signal via the communication unit 520.

[0150] A wireless communication method according to one embodiment of the present disclosure is also provided. In one embodiment, the wireless communication method may be performed using a first wireless communication node (e.g., gNB-CU). In one embodiment, the first wireless communication node may be implemented using the wireless communication node 50 described above, but is not limited thereto.

[0151] In one embodiment, the wireless communication method includes the steps of: sending a control message from a first wireless communication node to a second wireless communication node in order to instruct the wireless communication terminal to enter a wireless resource control (RRC) inactive mode; and sending at least one small data transmission (SDT) configuration to the wireless communication terminal.

[0152] Further details on this point can be found in the paragraph above and will not be repeated here.

[0153] According to one embodiment of the present disclosure, another wireless communication method is also provided. In one embodiment, the wireless communication method may be performed using a second wireless communication node (e.g., gNB-DU). In one embodiment, the second wireless communication node may be implemented using the wireless communication node 50 described above, but is not limited thereto.

[0154] In one embodiment, the wireless communication method includes the steps of: a second wireless communication node receiving a control message from a first wireless communication node; the second wireless communication node transmitting an RRC message included in the control message from the first wireless communication node to a wireless communication terminal; and the second wireless communication node refraining from releasing information related to the wireless communication terminal in accordance with the control message.

[0155] Further details on this point can be found in the paragraph above and will not be repeated here.

[0156] According to one embodiment of the present disclosure, another wireless communication method is also provided. In one embodiment, the wireless communication method may be performed using a wireless communication terminal (e.g., UE). In one embodiment, the wireless communication terminal may be implemented using the wireless communication terminal 40 described above, but is not limited thereto.

[0157] In one embodiment, the wireless communication method includes the steps of: a wireless communication terminal receiving an interruption instruction from a second wireless communication node or a third wireless communication and entering a radio resource control RRC inactive mode in accordance with the interruption instruction; and a wireless communication terminal receiving at least one small data transmission SDT configuration from the second wireless communication node or the third wireless communication.

[0158] In one embodiment, the third wireless communication is a gNB that is not separated into CU and DU. Further details on this point can be found in the paragraph above and will not be repeated here.

[0159] While various embodiments of this disclosure have been described above, it should be understood that they are presented only as examples and not as limitations. Similarly, various figures may illustrate exemplary architectures or configurations provided to enable those skilled in the art to understand the exemplary features and functions of this disclosure. However, such those skilled in the art will understand that this disclosure is not limited to the illustrated exemplary architectures or configurations and can be implemented using various alternative architectures and configurations. Furthermore, as will be understood by those skilled in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited by any of the exemplary embodiments described above.

[0160] Furthermore, it should be understood that any reference to elements in this specification using designations such as "first," "second," etc., does not generally limit the quantity or order of those elements. Rather, these names can be used in this specification as a convenient means of distinguishing two or more elements or examples of elements. Thus, references to first and second elements do not mean that only two elements can be used, or that the first element must in some way precede the second element.

[0161] Furthermore, those skilled in the art will understand that information and signals can be represented using any of the various different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols that can be referred to throughout the above description can be represented by voltage, electric current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0162] Those skilled in the art will further understand that any of the various exemplary logic blocks, units, processors, means, circuits, methods, and functions described in relation to the embodiments disclosed herein can be implemented by electronic hardware (e.g., digital implementations, analog implementations, or a combination of both), firmware, various forms of programs or design code incorporating instructions (which may be referred to herein as “software” or “software units” for convenience), or any combination thereof.

[0163] To clearly demonstrate this compatibility with hardware, firmware, and software, various exemplary components, blocks, units, circuits, and steps are generally described above in relation to their functions. Whether such functions are implemented as hardware, firmware, software, or a combination thereof depends on the specific application and the design constraints imposed on the overall system. A person skilled in the art can implement the described functions in various ways for each specific application, but such implementation decisions should not be construed as departing from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc., can be configured to perform one or more of the functions described herein. The terms “configured for” or “configured to” as used herein in relation to a specified operation or function refer to processors, devices, components, circuits, structures, machines, units, etc., that are physically constructed, programmed and / or positioned to perform the specified operation or function.

[0164] Furthermore, those skilled in the art will understand that various exemplary logic blocks, units, devices, components, and circuits described herein can be implemented in, or performed by, an integrated circuit (IC) which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, or any combination thereof. Logic blocks, units, and circuits may further include antennas and / or transceivers for communicating with various components within a network or device. While a general-purpose processor may be a microprocessor, in alternative examples, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working with a DSP core, or any other suitable configuration for performing the functions described herein. When implemented in software, the functions may be stored as one or more instructions or codes on a computer-readable medium. Thus, steps of the methods or algorithms disclosed herein may be performed as software stored on a computer-readable medium.

[0165] Computer-readable media include both computer storage media and communication media, which include any media that can enable the transfer of computer programs or code from one location to another. Storage media can be any available media that can be accessed by a computer. Such computer-readable media, but not limited to, include RAM, ROM, EEPROM, CD-ROM, or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other media that can be used to store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0166] As used herein, the term “unit” refers to software, firmware, hardware, and any combination thereof for performing the relevant functions described herein. Furthermore, for illustrative purposes, various units are described as individual units, but as will be apparent to those skilled in the art, two or more units can be combined to form a single unit that performs the relevant functions according to embodiments of this disclosure.

[0167] Furthermore, embodiments of this disclosure may include memory or other storage devices, as well as communication components. For clarity, it will be understood that the above description has illustrated embodiments of this disclosure with reference to different functional units and processors. However, it will be clear that any appropriate distribution of functionality between different functional units, processing logic elements, or domains can be used without prejudice to this disclosure. For example, a function shown to be performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Thus, references to specific functional units are not intended to indicate a strict logical or physical structure or organization, but merely to refer to appropriate means for providing the described functionality.

[0168] Various modifications to the embodiments described herein will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but should be given the broadest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. A wireless communication method, A wireless communication method comprising the steps of: a first wireless communication node transmitting a control message to a second wireless communication node to instruct a wireless communication terminal to enter a wireless resource control (RRC) inactive mode; and controlling the second wireless communication node to transmit at least one small data transmission (SDT) configuration to the wireless communication terminal.

2. The control message comprises an RRC message comprising the SDT configuration and an interruption instruction to cause the wireless communication terminal to enter the RRC inactive mode, and the second wireless communication node is configured to transparently transfer this RRC message to the wireless communication terminal. The wireless communication method according to claim 1, wherein the RRC message is an RRC release message.

3. The wireless communication method according to claim 1 or 2, wherein the control message includes an information element for preventing the second wireless communication node from releasing information related to the wireless communication terminal.

4. The wireless communication method according to any one of claims 1 to 3, wherein the information related to the wireless communication terminal is used for SDT between the wireless communication terminal and the second wireless communication node.

5. The information related to the aforementioned wireless communication terminal is: At least one radio link control RLC entity for SDT between the wireless communication terminal and the second wireless communication node, or At least one RLC bearer configuration for SDT between the wireless communication terminal and the second wireless communication node, A wireless communication method according to any one of claims 1 to 4, comprising:

6. The first wireless communication node is configured to send a request message to the second wireless communication node requesting SDT resources. The wireless communication method according to any one of claims 1 to 5, wherein the first wireless communication node is configured to receive a response message from the second wireless communication node indicating the result of the request for the SDT resource.

7. The first wireless communication node is configured to receive a configuration complete message from the second wireless communication node indicating that the SDT resource has been configured and the wireless communication terminal has entered the RRC inactive mode. The wireless communication method according to any one of claims 1 to 6, wherein the SDT configuration comprises at least one SDT resource.

8. A wireless communication method, The wireless communication terminal includes the step of receiving a wireless resource control RRC message from a second wireless communication node, The RRC message comprises at least one small data transmission SDT configuration and an interruption instruction to cause the wireless communication terminal to enter RRC inactive mode. A wireless communication method wherein the second wireless communication node is configured to refrain from releasing information related to the wireless communication terminal in accordance with a control message received from the first wireless communication node.

9. The wireless communication method according to claim 8, wherein the control message includes an information element for preventing the second wireless communication node from releasing information related to the wireless communication terminal.

10. The wireless communication method according to claim 8 or 9, wherein the control message comprises the RRC message, and the second wireless communication node is configured to transparently transfer the RRC message to the wireless communication terminal.

11. The wireless communication method according to any one of claims 8 to 10, wherein the information related to the wireless communication terminal is used for SDT between the wireless communication terminal and the second wireless communication node.

12. The information related to the aforementioned wireless communication terminal is: At least one radio link control RLC entity for SDT between the wireless communication terminal and the second wireless communication node, or At least one of at least one RLC bearer configurations for SDT between the wireless communication terminal and the second wireless communication node A wireless communication method according to any one of claims 8 to 11, comprising:

13. The wireless communication method according to any one of claims 8 to 12, wherein the SDT configuration comprises at least one SDT resource.

14. The wireless communication method according to any one of claims 8 to 13, wherein the RRC message is an RRC release message.

15. A wireless communication node, Communication unit and A wireless communication node comprising: a processor configured to perform the wireless communication method described in any one of claims 1 to 7.

16. A wireless communication terminal, Communication unit and The system comprises a processor configured to receive radio resource control (RRC) messages from a second wireless communication node, The RRC message comprises at least one small data transmission SDT configuration and an interruption instruction to cause the wireless communication terminal to enter RRC inactive mode. The second wireless communication node is configured to refrain from releasing information related to the wireless communication terminal in accordance with a control message received from the first wireless communication node, and is a wireless communication terminal.

17. The wireless communication terminal according to claim 16, wherein the processor is further configured to perform the wireless communication method according to any one of claims 8 to 14.

Images