Techniques for mobile terminated small data transmission
By introducing the MT-SDT process, the wireless network is allowed to directly send downlink data when the UE is inactive, which solves the problems of increased signaling overhead and power consumption in the existing technology, realizes efficient small data transmission, reduces the number of state transitions, and improves data transmission efficiency.
Patent Information
- Application Number
- CN202380033823.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-14
- Filing Date
- 2023-03-31
- Publication Date
- 2024-11-26
AI Technical Summary
In existing wireless networks, during small data transmission, especially when downlink data arrives, the user equipment (UE) needs to switch from an inactive state to a connected state to receive data, which increases signaling overhead and power consumption. Furthermore, existing technologies fail to effectively utilize data transmission opportunities during inactive states.
The introduction of the Mobile Termination Small Data Transmission (MT-SDT) procedure allows the network to send downlink data directly to the UE when it is inactive, without requiring the UE to switch to a connected state. Data transmission is achieved through MT-SDT capability exchange, RRC release messages, and paging mechanisms, and DL-SPS transmission and feedback mechanisms are supported.
It reduces signaling overhead and UE power consumption, improves data transmission efficiency, and reduces latency, making it particularly suitable for small data transmission scenarios and reducing unnecessary state transitions.
Smart Images

Figure CN119032600A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to U.S. Provisional Application No. 63 / 331,250, filed on April 14, 2022. The contents of that application are incorporated herein by reference in their entirety for all purposes. Background Art
[0003] The 3rd Generation Partnership Project (3GPP) Technical Specifications (TS) define standards for wireless networks. One area of research used to develop these TSs is for managing small data transmissions. BRIEF DESCRIPTION OF THE DRAWINGS
[0004] Figure 1 A network environment according to some embodiments is illustrated.
[0005] Figure 2 Mobile Terminated (MT) - Small Data Transmission (SDT) operations according to some embodiments are illustrated.
[0006] Figure 3 A signaling diagram of paging triggered mobile originated (MO)-SDT is illustrated according to some embodiments.
[0007] Figure 4 Another signaling diagram of paging triggered MO-SDT according to some embodiments is illustrated.
[0008] Figure 5 Another MT-SDT operation according to some embodiments is illustrated.
[0009] Figure 6 An operational flow / algorithm structure according to some embodiments is illustrated.
[0010] Figure 7 An operational flow / algorithm structure according to some embodiments is illustrated.
[0011] Figure 8 An operational flow / algorithm structure according to some embodiments is illustrated.
[0012] Fig. 9 An operational flow / algorithm structure according to some embodiments is illustrated.
[0013] Fig.10 User equipment according to some embodiments is illustrated.
[0014] Fig.11 A network node according to some embodiments is illustrated. DETAILED DESCRIPTION
[0015] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of illustration and not limitation, specific details, such as specific structures, architectures, interfaces and technologies are described to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art who benefit from the present disclosure that various aspects of various embodiments may be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits and methods are omitted so that the description of various embodiments will not be obscured by unnecessary details. For the purpose of this document, phrases "A / B" and "A or B" refer to (A), (B) or (A and B).
[0016] The following is a glossary of terms that may be used in this disclosure.
[0017] The term "circuit" as used herein refers to the part of the hardware component configured to provide the described function or includes the hardware component.Hardware components may include electronic circuits, logic circuits, processors (shared, dedicated or group) or memories (shared, dedicated or group), application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs or programmable systems on chip (SoCs)) or digital signal processors (DSPs).In some embodiments, circuits may execute one or more software or firmware programs to provide at least some of the functions.The term "circuit" may also refer to a combination of one or more hardware elements and a program code for performing the function of the program code (or a combination of circuits used in an electrical or electronic system).In these embodiments, the combination of hardware elements and program code may be referred to as a circuit of a specific type.
[0018] As used herein, the term "processor circuit" refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transferring digital data. The term "processor circuit" may refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional processes).
[0019] As used herein, the term "interface circuit" refers to a circuit that enables, is a part of, or includes information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card.
[0020] As used herein, the term "user equipment" or "UE" refers to a device with radio communication capabilities that can allow a user to access network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous with the following and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment or reconfigurable mobile device. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.
[0021] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to one another and configured to share computing resources or networked resources.
[0022] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time, a processor / CPU usage rate, a processor and accelerator load, a hardware time or usage rate, a power supply, an input / output operation, a port or a network socket, a channel / link allocation, a throughput, a memory usage rate, a storage, a network, a database, and an application or a unit of workload. "Hardware resources" may refer to computing, storage, or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage, or network resources provided by a virtualized infrastructure to an application, device, or system. The term "network resources" or "communication resources" may refer to resources that can be accessed by a computer device / system via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing resources or network resources. System resources may be considered as a set of coherent functions, network data objects, or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.
[0023] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" or any other similar term representing a path or medium through which data is transmitted. In addition, as used herein, the term "link" refers to a connection between two devices for transmitting and receiving information.
[0024] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.
[0025] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.
[0026] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networking hardware, network equipment, network node, or virtualized network function.
[0027] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents. An information element may include one or more additional information elements.
[0028] Figure 1 A network environment 100 according to some embodiments is illustrated. The network environment 100 may include a UE 104 coupled to a radio access network (RAN) 108 including a base station (BS) 112. The UE 104 and the BS 112 may communicate over an air interface compatible with 3GPP TSs such as those defining the fifth generation system (5GS) (or higher) standards. The BS 112 may be a next generation Node B (gNB) that provides one or more new radio (NR) cells presenting NR user plane and control plane protocol terminations to the UE 104.
[0029] The RAN 108 may be coupled to a core network (CN) 116. The CN 116 may have various network functions that provide services such as storing subscription information, authenticating UEs / network components, registering and tracking UEs, managing Quality of Service (QoS) aspects, controlling data sessions, and forwarding uplink / downlink traffic.
[0030] UE 102 may include a radio resource control (RRC) state machine that performs operations associated with various RRC procedures, including, for example, paging, RRC connection establishment, RRC connection reconfiguration, and RRC connection release. The RRC state machine may be implemented by protocol processing circuitry, see, for example, Fig.10 Baseband circuit 1004A.
[0031] The RRC state machine may transition the UE 104 to one of a variety of RRC states (or "modes"), including, for example, a connected state (RRC connected), an inactive state (RRC inactive), and an idle state (RRC idle). When the UE first camps on an NR cell, the UE may start in RRC idle, which may be after the UE 104 is turned on or after reselection of an inter-system cell from a long term evolution (LTE) cell. For active communication, the RRC state machine may transition the UE from RRC idle to RRC connected by performing an RRC establishment procedure to establish a logical connection, such as an RRC connection, with the base station 108. In the RRC connection, the UE may be configured with at least one signaling radio bearer (SRB) for signaling (e.g., control messages) with the base station; and one or more data radio bearers (DRBs) for data transmission. When the UE is not actively communicating with the network, the RRC state machine may use an RRC release procedure to transition the UE from RRC connected to RRC inactive. The RRC inactive state may allow the UE 104 to reduce power consumption compared to an RRC connected, but will still allow the UE 104 to quickly transition back to an RRC connected to transfer application data or signaling messages.
[0032] In Release 16 and earlier networks (e.g., networks implementing 3GPP TS versions prior to Release 17), for uplink data arrival for an inactive UE, the UE will trigger an RRC recovery procedure and enter a connected state for data transmission. For downlink data arrival for an inactive UE in these networks, the network will send a RAN paging message to request the UE to transition back to a connected state for data transmission.
[0033] Release 17 networks may utilize a Mobile Originated (MO)-Small Data Transmission (SDT) procedure that allows an inactive UE to perform UL data transmission in an inactive state upon receipt of uplink data arrivals for SDT resource blocks (RBs). If the amount of data to be transmitted is less than a predetermined threshold, the data may be considered SDT. This may reduce signaling overhead and UE power consumption by avoiding transitioning to a connected state, and reduce latency by allowing small and potentially infrequent packets including, for example, positioning data to be quickly transmitted. When downlink data arrives at the Release 17 network for a UE in an inactive state, the network may trigger a RAN paging to request the UE to transition back to a connected state. If the UE is in the middle of an SDT procedure and non-SDT data radio bearer (DRB) downlink data arrives at the network, the network may directly send an RRC recovery message during the SDT procedure and request the UE to transition back to a connected state.
[0034] However, for downlink data arrival, even for small and infrequent data transmission, the UE must transition back to the connected state for data reception. Providing a mobile terminated (MT)-SDT procedure based on downlink triggered SDT RBs can provide similar benefits to the MO-SDT procedure. The MT-SDT procedure allows the network to send DL data to a UE in an inactive state without requiring the UE to transition to the connected state.
[0035] Embodiments describe various aspects of MT-SDT operation. Embodiments include MT-SDT operation according to a first MT-SDT procedure and MT-SDT operation according to a second MT-SDT procedure. The first MT-SDT procedure may include MO-SDT transmission, while the second MT-SDT may not include the transmission.
[0036] Figure 2 MT-SDT operations 200 of a first MT-SDT process according to some embodiments are illustrated.
[0037] MT-SDT operations 200 may include the RAN 108 and the UE 104 performing an MT-SDT capabilities exchange, at 204. The MT-SDT capabilities exchange may indicate that both the UE 104 and the RAN 108 support the MT-SDT feature.
[0038] The MT-SDT capability exchange may include the UE 104 sending the UE MT-SDT capabilities to the RAN 108. The UE MT-SDT capabilities, which may be part of an access stratum (AS) capabilities information element (IE), may indicate an MT-SDT paging reception capability that informs the RAN 108 whether the UE 104 is capable of receiving a paging message to indicate the arrival of downlink data to be sent as an MT-SDT transmission to the UE 104. The UE MT-SDT capabilities may also indicate whether the UE 104 supports a first MT-SDT procedure or a second MT-SDT procedure.
[0039] In some embodiments, the UE MT-SDT capabilities may additionally / alternatively include SDT-DL-Semi-persistent scheduling (SPS) capabilities. The SDT-DL-SPS capability may indicate whether the UE 104 supports DL-SPS in MT-SDT. In some embodiments, the SDT-DL-SPS capability may indicate support for one activated SPS process in MT-SDT. In other embodiments, the UE MT-SDT capabilities may include a multi-SPS capability to indicate whether the UE 104 supports multiple activated SPS processes in MT-SDT. In some embodiments, the (multi) SPS capability may be mandatory for MT-SDT, but optional for MO-SDT.
[0040] In some implementations, the capabilities may be designed according to UE, frequency band, frequency range (FR) (eg, FR1 or FR2), or duplex scheme (eg, time division duplex (TDD) or frequency division duplex (FDD)).
[0041] If both the UE 104 and the RAN 108 support the MT-SDT feature, the MT-SDT operations 200 may proceed and the RAN 108 may enable MT-SDT by sending an RRC message (e.g., an RRC release message with a suspension configuration) at 208. The RRC release message may include the MT-SDT configuration and potentially the MO-SDT configuration. Upon receiving the RRC release message, the UE 104 may transition to an RRC inactive state.
[0042] At 212, the DL data may arrive at the RAN 108. The RAN 108 may send a paging message to the UE 108 to indicate that the DL data is to be sent as SDT RBs via MT-SDT transmission.
[0043] The paging message may be used as a MO-SDT triggering condition. For example, upon receiving the paging message at 212, the UE 104 may initiate a MO-SDT session 216.
[0044] The MO-SDT session may begin with the UE 104 sending an initial MO-SDT message to the RAN 108. In some embodiments, the initial MO-SDT message may be a random access (RA)-SDT. The RA-SDT message may be a random access channel (RACH) transmission sent to the RAN 108. The RAN 108 may then utilize dynamic scheduling for the remainder of the MO-SDT session 216 to schedule subsequent transmissions, including, for example, MT-SDT transmissions including DL data.
[0045] In some embodiments, the MO-SDT message may be a configured grant (CG)-SDT message. The RAN 108 may configure the CG resources in an RRC message (e.g., a dedicated RRC configuration message). The UE 104 may then use the CG resources to send the CG-SDT message within the MO-SDT session. Upon receiving the CG-SDT message, the RAN 108 may utilize dynamic scheduling for the remainder of the MO-SDT session 216 to schedule subsequent transmissions, including, for example, MT-SDT transmissions including DL data.
[0046] In various embodiments, the subsequent transmission may include UL SDT transmission and DL SDT transmission and confirmation / feedback about them. RAN 108 may schedule UE-specific UL / DL data transmission via a UE-specific cell radio network temporary identity (C-RNTI), and the data transmission may be sent via the initial BWP of the current serving cell. In some embodiments, RAN 108 may configure DL-SPS resources for DL transmission during the MO-SDT session. This may include both initial DL transmission and subsequent DL transmission. DL-SPS resources may be configured by an RRC message (e.g., a dedicated RRC configuration message).
[0047] Unless otherwise described herein, the operations of the UE 104 and the RAN 108 within the MO-SDT session may be similar to the operations described in the Change Request (CR) for Release 17 TS as defined in: R2-2204234–Introduction of SDT, 3GPP TSG-RAN WG2 Meeting #117 Electronic Elbonia, February 21-March 3, 2022; R2-2204216–Introduction of Small Data Transmission for MAC spec, 3GPP TSG-RAN2 Meeting #117e Electronic, February 21-March 3, 2022; and R2-2203768–Introduction of SDT, 3GPP TSG-RAN WG2 Meeting #117-e Electronic, February 21-March 3, 2022.
[0048] In some embodiments, the UE 104 may utilize an initial SDT transmission within the MO-SDT session 216 to provide an indication to the RAN 108 whether the UE 104 has UL SDT data to send. For example, if the UE 104 has UL SDT data to send, the UE 104 may perform a MO-SDT procedure. This may include sending a special RACH message that includes a larger transmission block size (TBS) than a traditional (e.g., non-MO-SDT) RACH message. The SDT-specific RACH may be distinguished from the traditional RACH based on configuration. Although the configuration parameters may be the same, the values of the RACH TDM / FDM resources may be different. The RAN 108 may distinguish the SDT-specific RACH from the traditional RACH based on these differences. Upon receiving the special RACH message, the RAN 108 may dynamically schedule UL resources for the UE 104 to send the MO-SDT transmission.
[0049] On the other hand, if the UE 104 has no UL SDT data to send and the initial SDT transmission is triggered entirely by MT paging, the UE 104 may perform either of the following two options. In the first option, the UE 104 may use traditional RACH resources for the initial SDT transmission. In this instance, the initial transmission may include an RRC recovery request that includes an inactive radio network temporary identity (I-RNTI). The RRC recovery request may not be used to restore the RRC connection, but rather it may be used for SDT initiation and carries information (e.g., message authentication code integrity (MAC-I), UE ID) that allows the RAN 108 to identify the SDT UE 104. Upon receiving the initial SDT transmission with traditional RACH resources and I-RNTI, the RAN 108 may understand that the access is based only on MT-SDT transmission.
[0050] In a second option, UE 104 may set the recovery cause in the RRC recovery request in a manner indicating that the initial SDT transmission is completely triggered by MT paging.
[0051] Figure 3 and Figure 4 Signaling diagrams 300 and 400, respectively, illustrate a paging-triggered MO-SDT session according to some embodiments. The paging-triggered MO-SDT session may be similar to the MO-SDT session 216 described above with respect to the MT-SDT operation 200. The signaling diagrams 300 and 400 illustrate signals between the UE 104, the serving BS 304 of the RAN 108, and the anchor BS 308 of the RAN 108 according to two options.
[0052] The signaling diagram 300 representing the first option may include, at 312, the UE 104 receiving a MT-SDT paging message from the anchor BS 308. The paging message may be similar to the paging message at 212 described above with respect to the MT-SDT operations 200.
[0053] At 316, UE 104 may send a conventional RACH message to serving BS 304. Upon receiving the conventional RACH message, serving BS 304 may forward a context acquisition request to anchor BS 308 at 320 to obtain the UE context stored at anchor BS 308. The context acquisition request may prompt anchor BS 308 to determine whether to trigger a context relocation and data forwarding process as part of the MT-SDT process. In this embodiment, anchor BS 308 may be aware of the MT-SDT process, but serving BS 304 may not be aware.
[0054] If the anchor BS 308 is able to identify the UE 104 using the UE context ID, successfully authenticate the UE 104 based on the integrity protection within the context acquisition request, and decides to provide the UE context to the serving BS 304, it may send a context acquisition response to the serving BS 304 at 324. The anchor BS may forward the DL SDT data to the serving BS 304 over the Xn interface, and the serving BS 304 may then use the UE context to send the DL SDT data to the UE 104 in a DL transmission at 328. The DL transmission may be the same as above with respect to Figure 2 A portion of a subsequent transmission of the MO-SDT session 216 is described.
[0055] In some examples, the anchor BS 308 and the serving BS may perform partial UE context relocation. In this example, the anchor BS 308 may send a partial UE context transfer message to the serving BS 304. If the serving BS can perform DL SDT transmission without anchor relocation, it will send a confirmation message to the anchor BS 308. The anchor BS 308 may forward the DL SDT data to the serving BS 304 via the Xn interface. The serving BS 304 may then schedule the data to be sent to the UE 104 over the Uu interface.
[0056] In some implementations, the anchor BS 308 may provide an explicit indication in a message (eg, context acquisition response) to the serving BS 304 that the procedure is associated with the MT-SDT procedure. At 332 and 336, the anchor BS 308 and the serving BS 304 may perform a path switch and data transmission, respectively.
[0057] The serving BS 304 may send an RRC release message to the UE 104 at 340 and may also send a context release to the anchor BS 308. The RRC release message may provide an indication to the UE 104 that the MO-SDT session is ended. In other embodiments, other RRC messages (e.g., an RRC resume message or an RRC last message) may be used to mark the end of the MO-SDT session. In other embodiments, the SDT session may be closed by other processes, for example, by expiration of a timer started at the start of the session or upon receipt of an MT-SDT paging message at 312.
[0058] In general, the full / partial context acquisition procedures and path switching procedures may be similar to conventional procedures, such as those described in, for example, 3GPP TS 38.423 v17.0.0 (2022-04-06).
[0059] The signaling diagram 400, which may represent the second option, may include signals similar to similarly named signals present in the signaling diagram 300. However, in the second option, both the serving BS 304 and the anchor BS 308 are aware of the UE access for MT-SDT. The serving BS 304 may determine whether to provide MT-SDT. This may be based on the current network situation, for example, whether the resources provided on the air interface (e.g., Uu interface) are sufficient to accommodate MT-SDT transmissions, or whether the number of transmissions within the current MO-SDT session has exceeded a predetermined threshold. The serving BS 304 may then generate an MT-SDT indication, which may be sent at 420 along with the context acquisition request to notify the anchor BS 308 whether to continue the MT-SDT process. For example, if the serving BS 304 determines not to continue the MT-SDT process, the MT-SDT indication may be set to "false", and the MT-SDT process triggered by the anchor BS 308 sending the MT-SDT paging message at 412 may be terminated. If the SDT SDT procedure continues, the MT-SDT indication may be set to "true" and the MT-SDT procedure may continue.
[0060] The anchor BS 408 may then determine whether to trigger a context relocation and data forwarding procedure as part of the MT-SDT procedure consistent with the MT-SDT indication.
[0061] Figure 5 MT-SDT operations 500 of a second MT-SDT process are illustrated according to some embodiments.
[0062] The MT-SDT operations 500 may include the RAN 108 and the UE 104 performing an MT-SDT capabilities exchange, at 504. The MT-SDT capabilities exchange may be similar to that described above with respect to the MT-SDT operations 200.
[0063] If both the UE 104 and the RAN 108 support the MT-SDT feature, the MT-SDT operations 500 may proceed and the RAN 108 may enable MT-SDT by sending an RRC release message at 508. Enabling MT-SDT using the RRC message may be similar to that described above with respect to the MT-SDT operations 200.
[0064] At 512, the DL data may arrive at the RAN 108. The RAN 108 may send a paging message to the UE 108 to indicate that the DL data is to be sent via MT-SDT transmission. The sending of the paging message may be similar to that described above with respect to MT-SDT operations 200.
[0065] In MT-SDT operation 500, UE 104 may start DL data reception directly without first sending a MO-SDT transmission. Specifically, UE 104 may wait for a period of time, such as gap / offset 516, before monitoring the UE-dedicated physical downlink control channel (PDCCH) for DL transmission at 524 after receiving the paging message. The length of the gap / offset 516 may be predefined or preconfigured by 3GPP TS. RAN 108 may send scheduling information in the PDCCH to schedule DL resources for subsequent MT-SDT transmissions within the MT-SDT session 520. UE 104 may continue to monitor the DL PDCCH throughout the MT-SDT session 520. The length of the MT-SDT session 520 and therefore the period of time during which the DL PDCCH may be monitored may be controlled by an SDT timer.
[0066] The SDT timer may be a static timer that is started when the UE 104 begins SDT PDCCH monitoring. When the static SDT timer expires, the UE 104 may terminate the MT-SDT process. In other embodiments, the SDT timer may be a dynamic timer that is extended for a period of time based on, for example, receiving a downlink transmission.
[0067] In some implementations, the RAN 108 may additionally / alternatively send a specific signal to terminate the MT-SDT process.
[0068] The UE 104 may use the C-RNTI to perform UE-specific PDCCH monitoring. The C-RNTI may be pre-configured in the RRC release message sent at 508. In some implementations, the C-RNTI may correspond to the I-RNTI.
[0069] In various embodiments, the UE-specific configuration of the SDT UE-specific transmission discussed above for UL / DL data transmission in subsequent transmissions of the MO-SDT session 216 may be reused in the MT-SDT session 520 .
[0070] In some implementations, the RAN 108 may use pre-configured DL SPS resources for DL transmissions during the MT-SDT session 520 .
[0071] Compared to MT-SDT operation 300, MT-SDT operation 500 can better support one short DL transmission; however, RAN 108 may not know whether UE 104 successfully received the page before performing any DL scheduling. Therefore, in some embodiments, UE 104 can send a feedback message at 514.
[0072] Feedback on the paging message may be performed according to one of the following two options. In the first option, the feedback may be delivered via a UE-specific physical uplink control channel (PUCCH) or a sounding reference signal (SRS). This option may be desirable if UE 104 has a valid uplink timing advance (TA). If UE 104 does not have a valid uplink TA, it may trigger a RACH before sending the feedback. The PUCCH / SRS resources used for feedback may be configured in the RRC release sent at 508. The configuration of PUCCH / SRS may associate feedback transmission with different DL beams. UE 104 may select a suitable DL beam and then use the associated PUCCH / SRS resources for feedback transmission.
[0073] In a second option, the feedback may be delivered via PUSCH resources. The UE 104 may deliver a medium access control (MAC) control element (CE) as feedback to the RAN 108 via a specific PUSCH resource. The special PUSCH resource may be pre-configured and associated with a specific paging occasion or may be a CG-SDT resource. The RAN 108 may configure different resources associated with different DL beams. The UE 104 may identify one of the DL beams and use the associated uplink resources for PUSCH.
[0074] In the event that the UE 104 has uplink SDT data, it may deliver the data after providing the feedback message at 514. If the UE 104 has uplink SDT data before sending the feedback message, the UE 104 may trigger the MO-SDT directly, thereby avoiding the need to deliver a paging message. If the RAN 108 receives a MO-SDT transmission in response to the paging message at 512, the operation may be similar to that with respect to the MO-SDT. Figure 2 The operation described.
[0075] Figure 6 An operational flow / algorithm structure 600 according to some embodiments is illustrated. The operational flow / algorithm structure 600 may be performed by a UE (such as, for example, UE 104 or 800) or a component thereof (eg, processing circuit 804).
[0076] The operational flow / algorithm structure 600 may include receiving an MT-SDT paging message at 604. The paging message may be similar to the one described above with respect to Figure 2 as described.
[0077] The operational flow / algorithm structure 600 may also include determining whether the MT-SDT criteria are met at 608. The MT-SDT criteria may be based on a signal metric, such as a reference signal received power (RSRP) of the MT-SDT paging message. If the RSRP is greater than a predetermined RSRP threshold, the MT-SDT criteria may be considered met, and the operational flow / algorithm structure 600 may proceed to initiating an MT-SDT process at 612. The MT-SDT process may be similar to the MT-SDT process described elsewhere herein. If the RSRP is not greater than a predetermined RSRP threshold, the MT-SDT criteria may be considered not met, and the operational flow / algorithm structure 600 may proceed to initiating a conventional recovery process at 616. The conventional recovery process may include the UE sending an RRC recovery message to the network to request that the UE transition to an RRC connected state.
[0078] Figure 7 An operational flow / algorithm structure 700 is illustrated according to some embodiments. The operational flow / algorithm structure 700 may be performed by a base station such as, for example, BS 112, anchor BS 308, or network device 900 or a component thereof (eg, processing circuit 904).
[0079] The operational flow / algorithm structure 700 may include, at 704, receiving downlink data to be sent to the UE.
[0080] The operation flow / algorithm structure 700 may also include determining whether the MT-SDT criteria are met at 708. The MT-SDT criteria may be based on the characteristics of the downlink data to be sent to the UE. For example, the downlink data may include SDT RBs for the UE, and the MT-SDT criteria may be based on the type or number of SDT-RBs. For example, if the downlink traffic will be better served by transitioning the UE to the RRC connected state given the type / number of SDT-RBs, the base station may determine that the MT-SDT criteria are not met. In the event that the MT-SDT criteria are not met, the operation flow / algorithm structure 700 may proceed to initiating a traditional recovery process at 716. The traditional recovery process may include the UE sending an RRC recovery message to the network to request the UE to transition to the RRC connected state.
[0081] For example, if, given the type / number of SDT-RBs, downlink traffic will be better served by sending data to a UE in an RRC inactive state, the base station may determine that the MT-SDT criteria are met. If the MT-SDT criteria are met, the operational flow / algorithm structure 700 may proceed to initiating an MT-SDT process at 712. The MT-SDT process may be similar to the MT-SDT process described elsewhere herein.
[0082] The MT-SDT standard used at 608 or 708 may be pre-defined in 3GPP TS or may be implemented based on the network or UE.
[0083] As briefly described above, some implementations may rely on DL-SPS transmissions to deliver SDT RBs. In Release 17, CG-SDT is supported only within one cell. It is not available for instances of cell changes. In addition, CG-SDT requires maintaining a valid TA in order to control the validity of CG-SDT resources. An implementation utilizing DL-SPS SDT operation during an MT-SDT session (e.g., MT-SDT session 520) may be implemented as follows.
[0084] In the downlink, DL-SPSSDT resources can be used for periodic DL data transmission in MT-SDT sessions. Figure 5 , the RAN 108 may provide configuration information in the RRC release message (or another RRC message) sent at 508 to configure the DL SPS for SDT purposes. The DL SPS configuration for SDT purposes may support multiple SPS configurations. For example, different SPS configurations may be customized for different beams or periodicities. Thereafter, the RAN 108 may activate one or more of the configured SPS configurations. In some embodiments, the RAN 108 may activate the selected SPS configuration by including activation information in the paging message sent at 512.
[0085] After UE 104 receives the MT-SDT paging message at 512, UE 104 may begin directly monitoring the SPS opportunities of the activated SPS configuration for data reception.
[0086] In case paging feedback is used, the RAN 108 may start downlink SDT data transmission using the configured SPS resources after receiving the paging feedback at 514 .
[0087] If paging feedback is not used, the RAN 108 may use the first SPS opportunity to deliver downlink SDT data after the gap / offset 516. In some embodiments, the UE 104 may send feedback based on receiving the SPS transmission. This may notify the RAN 108 that the UE 104 has entered the MT-SDT session 520. The RAN 108 may then proceed with additional downlink SDT transmissions.
[0088] In some implementations, uplink synchronization (eg, with a valid TA) may allow UE 104 to deliver uplink feedback for downlink SPS transmissions. In some examples, if the uplink TA is not valid, downlink SPS resources may be released.
[0089] In some embodiments, the verification of the TA may be based on a TA timer or RSRP change. For example, the TA may be considered valid within a predetermined time period after receiving a valid TA or until the RSRP changes by more than a predetermined threshold.
[0090] In some embodiments, DL-SPS SDT operations may additionally / alternatively be used for MO-SDT session 216. RAN 108 may configure DL-SPS in a manner similar to that discussed above with respect to MT-SDT session 520. SDT transmissions using DL-SPS resources may be in a subsequent transmission phase or as a first DL transmission in response to an initial uplink transmission.
[0091] Figure 8 An operational flow / algorithm structure 800 according to some embodiments is illustrated. The operational flow / algorithm structure 800 may be performed by a UE (such as, for example, UE 104 or 1000) or a component thereof (eg, processing circuit 1004).
[0092] The operational flow / algorithm structure 800 may include, at 804, sending MT-SDT capabilities. The MT-SDT capabilities may be sent to a base station of the RAN. The MT-SDT capabilities may be included in the AS Capabilities IE and may indicate whether the UE is capable of performing MT-SDT. In some embodiments, if the UE is capable of performing MT-SDT, the MT-SDT capabilities may provide further details of the process or features of the supported MT-SDT operations. The MT-SDT capabilities may be based on UE, frequency band, frequency range, or duplex scheme.
[0093] The operation flow / algorithm structure 800 may also include, at 808, receiving an RRC message with an MT-SDT configuration. The MT-SDT configuration may configure the UE for MT-SDT operation according to the MT-SDT capability of the UE. The configuration information may also include information about resources to be used for SDT transmissions. These SDT transmissions may include MT-SDT transmissions, feedback transmissions, and MO-SDT transmissions. The RRC message may be an RRC release message sent to indicate that the UE transitions from an RRC connected state to an RRC inactive state.
[0094] The operational flow / algorithm structure 800 may also include receiving a paging message at 812. The paging message may be received from the network to notify the UE that downlink SDT data is available at the network. In some embodiments, the UE may send a feedback message to confirm successful receipt of the paging message.
[0095] The operation flow / algorithm structure 800 may also include, at 816, performing MT-SDT operations. The MT-SDT operations may be respectively relative to Figure 2 and Figure 5One or more of the operations shown and discussed in connection with the first MT-SDT process or the second MT-SDT process may include transmitting / receiving SDT data (and possibly feedback) in a MO-SDT session (e.g., MO-SDT session 216) or a MT-SDT session (e.g., MT-SDT session 520).
[0096] Fig. 9 An operational flow / algorithm structure 900 according to some embodiments is illustrated. The operational flow / algorithm structure 900 may be performed by a base station (such as, for example, base station 112 or 1100) or a component thereof (eg, processing circuit 1104).
[0097] The operational flow / algorithm structure 900 may include receiving an indication of MT-SDT capabilities of the UE at 904. The MT-SDT capabilities may be similar to those described elsewhere herein.
[0098] The operation flow / algorithm structure 900 may also include, at 908, sending an RRC message with an MT-SDT configuration. The MT-SDT configuration may configure the UE for MT-SDT operation according to the MT-SDT capability of the UE. The configuration information may also include information about resources to be used for SDT transmissions. These SDT transmissions may include MT-SDT transmissions, feedback transmissions, and MO-SDT transmissions. The RRC message may be an RRC release message sent to indicate that the UE transitions from an RRC connected state to an RRC inactive state.
[0099] The operational flow / algorithm structure 900 may also include receiving data at 912. Data may be received from the core network to send to the UE. The base station may analyze the data to determine whether it is more efficient to send the data to the UE as an MT-SDT transmission when the UE is in an inactive state or to transition the UE to a connected state and send the data as a regular downlink transmission.
[0100] In this embodiment, the base station may determine that the data is to be sent as an MT-SDT transmission, and the operational flow / algorithm structure 900 may also include, at 916, sending a paging message. The paging message may indicate to the UE that the network has data to be sent in an MT-SDT transmission. After the paging message is sent, the base station may perform a communication with the respective Figure 2 and Figure 5 MT-SDT operations associated with a first MT-SDT process or a second MT-SDT process are shown and discussed. These operations may include transmitting / receiving SDT data (and possibly feedback) in a MO-SDT session (e.g., MO-SDT session 216) or a MT-SDT session (e.g., MT-SDT session 520).
[0101] Fig.10 UE 1000 according to some embodiments is illustrated. UE 1000 may be similar to Figure 1 UE 104 and is substantially interchangeable therewith.
[0102] UE 1000 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an XR device, glasses, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, or an actuator), a video surveillance / monitoring device (e.g., a camera or a camcorder), a wearable device (e.g., a smart watch), or an IoT device.
[0103] UE 1000 may include a processor 1004, an RF interface circuit 1008, a memory / storage device 1012, a user interface 1016, a sensor 1020, a driving circuit 1022, a power management integrated circuit (PMIC) 1024, an antenna structure 1026, and a battery 1028. The components of UE 1000 may be implemented as an integrated circuit (IC), a portion of an integrated circuit, a discrete electronic device or other module, logical component, hardware, software, firmware, or a combination thereof. Fig.10 The block diagram of UE 1000 is intended to show a high-level view of certain of the components of UE 1000. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.
[0104] Components of UE 1000 may be coupled to various other components via one or more interconnects 1032, which may represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, or optical connection that allows various circuit components (on a common or different chip or chipset) to interact with each other.
[0105] The processor 1004 may include processor circuits such as a baseband processor circuit (BB) 1004A, a central processor unit circuit (CPU) 1004B, and a graphics processor unit circuit (GPU) 1004C. The processor 1004 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program codes, software modules, or functional processes from the memory / storage device 1012) to cause the UE 1000 to perform operations as described herein.
[0106] In some embodiments, the baseband processor circuit 1004A can access the communication protocol stack 1036 in the memory / storage device 1012 to communicate through a 3GPP compatible network. Generally speaking, the baseband processor circuit 1004A can access the communication protocol stack 1036 to perform the following operations: perform user plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, SDAP sublayer and upper layers; and perform control plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, RRC layer and NAS layer. In some embodiments, the PHY layer operations can be additionally / alternatively performed by components of the RF interface circuit 1008.
[0107] The baseband processor circuit 1004A may generate or process baseband signals or waveforms that carry information in a 3GPP-compatible network. In some embodiments, the waveforms used for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.
[0108] The memory / storage 1012 may include one or more computer-readable media including instructions (e.g., the communication protocol stack 1036) that may be executed by one or more processors in the processor 1004 to cause the UE 1000 to perform various operations described herein. The memory / storage 1012 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1000. In some embodiments, some of the memory / storage 1012 may be located on the processor 1004 itself (e.g., L1 cache and L2 cache), while other memory / storage 1012 is located external to the processor 1004 but accessible via a memory interface. The memory / storage 1012 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.
[0109] The RF interface circuit 1008 may include a transceiver circuit and a radio frequency front end module (RFEM), which allows the UE 1000 to communicate with other devices through a radio access network. The RF interface circuit 1008 may include various elements arranged in a transmit path or a receive path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, and control circuits.
[0110] In the receive path, the RFEM may receive the radiated signal from the air interface via the antenna structure 1026 and continue to filter and amplify the signal (using a low noise amplifier). The signal may be provided to the transceiver's receiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of the processor 1004.
[0111] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before the signal is radiated across the air interface via the antenna 1026.
[0112] In various embodiments, the RF interface circuit 1008 may be configured to transmit / receive signals in a manner compatible with NR access technology.
[0113] Antenna 1026 may include antenna elements to convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. Antenna 1026 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple input / multiple output communications. Antenna 1026 may include a microstrip antenna; a printed antenna fabricated on the surface of one or more printed circuit boards; a patch antenna or a phased array antenna. Antenna 1026 may have one or more panels designed for a specific frequency band including a frequency band in FR1 or FR2.
[0114] The user interface circuit 1016 includes various input / output (I / O) devices designed to enable a user to interact with the UE 1000. The user interface 1016 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual components for accepting input, including in particular one or more physical or virtual buttons (e.g., reset button), physical keyboard, keypad, mouse, touch pad, touch screen, microphone, scanner, headset, etc. The output device circuit includes any physical or virtual components for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuit may include any number or combination of audio or visual displays, including in particular one or more simple visual outputs / indicators (e.g., binary state indicators (such as light emitting diodes (LEDs)) and multi-character visual outputs), or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, and projectors), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 1000.
[0115] Sensors 1020 may include devices, modules, or subsystems that are designed to detect events or changes in their environment and send information about the detected events (sensor data) to some other device, module, or subsystem. Examples of such sensors include: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, a three-axis gyroscope, or a magnetometer; a liquid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; and a microphone or other similar audio capture device.
[0116] The driver circuit 1022 may include software and hardware elements for controlling a particular device embedded in, attached to, or otherwise communicatively coupled to the UE 1000. The driver circuit 1022 may include various drivers to allow other components to interact with or control various I / O devices that may be present in or connected to the UE 1000. For example, the driver circuit 1012 may include circuits that facilitate coupling a UICC (e.g., UICC 148) to the UE 1000. For additional examples, the driver circuit 1022 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining sensor readings of the sensor circuit 1020 and controlling and allowing access to the sensor circuit 1020, a driver for obtaining an actuator position of an electromechanical component or controlling and allowing access to an electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.
[0117] The PMIC 1024 may manage power provided to various components of the UE 1000. Specifically, with respect to the processor 1004, the PMIC 1024 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.
[0118] In some embodiments, the PMIC 1024 may control or otherwise be a part of various power saving mechanisms of the UE 1000, including DRX, as discussed herein.
[0119] The battery 1028 can power the UE 1000, but in some examples, the UE 1000 can be installed in a fixed location and can have a power source coupled to the power grid. The battery 1028 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, the battery 1028 can be a typical lead-acid car battery.
[0120] Fig.11 Illustrated is a network node 1100 according to some embodiments. The network node 1100 may be similar to the base station 112, the serving BS 304, or the anchor BS 308 and may be substantially interchangeable therewith.
[0121] The network node 1100 may include a processor 1104 , RF interface circuitry 1108 (if implemented as an access node), core network (CN) interface circuitry 1112 , memory / storage circuitry 1116 , and antenna structures 1126 .
[0122] Components of network node 1100 may be coupled to various other components via one or more interconnects 1128 .
[0123] The processor 1104, RF interface circuit 1108, memory / storage circuit 1116 (including communication protocol stack 1110), antenna structure 1126 and interconnect 1128 may be similar to those of reference Fig.10 Like named elements are shown and described.
[0124] The CN interface circuit 1112 may provide connectivity to a core network, e.g., a 5th generation core network (5GC) using a 5GC-compatible network interface protocol, such as a carrier Ethernet protocol, or some other suitable protocol. Network connectivity may be provided to / from the network node 1100 via optical fiber or wireless backhaul. The CN interface circuit 1112 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1112 may include multiple controllers for providing connectivity to other networks using the same or different protocols.
[0125] In some embodiments, the network node 1100 may be coupled to a transmit receive point (TRP) using antenna structures 1126, CN interface circuitry, or other interface circuitry.
[0126] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.
[0127] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below. For another example, the circuit associated with the UE, base station, or network element described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below.
[0128] Example
[0129] In the following sections, additional exemplary embodiments are provided.
[0130] Embodiment 1 includes a method of operating a user equipment (UE), the method comprising: sending an indication of a mobile terminated (MT)-small data transmission (SDT) capability to a network; receiving a radio resource control (RRC) message including an MT-SDT configuration from the network; receiving a paging message from the network to indicate the presence of downlink data for the UE; and performing MT-SDT operation based on the paging message and the MT-SDT configuration.
[0131] Embodiment 2 includes the method according to embodiment 1 or some other embodiment herein, the method further comprising: generating an access stratum (AS) capability information element (IE) to include the MT-SDT capability; and sending the AS capability IE to the network.
[0132] Embodiment 3 includes a method according to embodiment 1 or some other embodiments herein, wherein the MT-SDT capability indicates that the UE is capable of performing a first MT-SDT process including mobile originated (MO)-SDT transmission or is capable of performing a second MT-SDT process not including MO-SDT transmission.
[0133] Embodiment 4 includes a method according to embodiment 1 or some other embodiment herein, wherein the MT-SDT capability indicates whether the UE supports one or more downlink (DL)-semi-persistent scheduling (SPS) configurations during the MT-SDT process.
[0134] Embodiment 5 includes the method according to embodiment 1 or some other embodiment herein, wherein the MT-SDT capability is based on UE, frequency band, frequency range, or duplex scheme.
[0135] Embodiment 6 includes a method according to embodiment 1 or some other embodiment herein, wherein performing the MT-SDT operation includes: sending a mobile originated (MO)-SDT transmission based on the paging message; and receiving an MT-SDT transmission after sending the MO-SDT transmission.
[0136] Embodiment 7 includes a method according to embodiment 6 or some other embodiment herein, wherein the MO-SDT transmission is a random access transmission.
[0137] Embodiment 8 includes a method according to embodiment 6 or some other embodiment herein, wherein the RRC message includes an indication of a configuration grant resource, and the MO-SDT transmission is a configuration grant transmission using the configuration grant resource.
[0138] Embodiment 9 includes a method according to embodiment 6 or some other embodiment herein, wherein the RRC message further includes a MO-SDT configuration.
[0139] Embodiment 10 includes a method of operating a user equipment (UE), the method comprising: receiving a radio resource control (RRC) message including a mobile termination (MT)-small data transmission (SDT) configuration from a network; receiving a paging message from the network to indicate the presence of downlink data for the UE; and monitoring a physical downlink control channel (PDCCH) during an MT-SDT session, wherein the MT-SDT session starts in a time period after receiving the paging message.
[0140] Embodiment 11 includes the method according to embodiment 10 or some other embodiment herein, the method further comprising: sending a feedback message to indicate successful receipt of the paging message.
[0141] Embodiment 12 includes a method according to embodiment 11 or some other embodiment of the present invention, wherein the method further includes: receiving information for configuring a physical uplink control channel (PUCCH) or a sounding reference signal (SRS) resource in the RRC message; and sending the feedback message as a PUCCH or SRS transmission using the PUCCH or SRS resources.
[0142] Embodiment 13 includes the method according to embodiment 12 or some other embodiment of the present invention, wherein the method further includes: selecting a downlink beam; and selecting the PUCCH or SRS resource based on an association between the downlink beam and the PUCCH or SRS resource.
[0143] Embodiment 14 includes a method according to embodiment 11 or some other embodiment of the present invention, wherein the method further includes: generating a medium access control (MAC) control element (CE); and sending the MAC CE as the paging message using a physical uplink shared channel (PUSCH) resource.
[0144] Embodiment 15 includes a method according to embodiment 10 or some other embodiments of the present invention, wherein the method further includes: determining a cell radio network temporary identity (C-RNTI) based on the RRC message or an inactive radio network temporary identity (I-RNTI); and monitoring the PDCCH based on the C-RNTI.
[0145] Embodiment 16 includes the method according to embodiment 10 or some other embodiments of a certain document, wherein the method further includes: starting an SDT timer when the UE starts to monitor the PDCCH; and terminating the monitoring of the PDCCH based on the expiration of the SDT timer.
[0146] Embodiment 17 includes a method according to embodiment 10 or some other embodiment herein, wherein the method further includes: receiving configuration information for providing a semi-persistent scheduling (SPS) configuration in the RRC message; determining an SPS timing based on the SPS configuration; and monitoring the PDCCH in the SPS timing.
[0147] Embodiment 18 includes a method according to embodiment 17 or some other embodiment of the present invention, wherein the configuration information is used to configure multiple SPS configurations, and the method further includes: receiving activation information for activating the SPS configuration from the multiple SPS configurations in the paging message.
[0148] Embodiment 19 includes a method of operating a base station, the method comprising: receiving an indication of mobile terminated (MT)-small data transmission (SDT) capability from a user equipment (UE); sending a radio resource control (RRC) message including an MT-SDT configuration to the UE; receiving data to be sent to the UE; and sending a paging message to the UE to indicate the presence of the data to be sent to the UE in an MT-SDT transmission.
[0149] Embodiment 20 includes the method according to embodiment 19 or some other embodiment herein, the method further comprising: receiving a mobile originated (MO)-SDT transmission from the UE; and sending the MT-SDT transmission to the UE based on the MO-SDT transmission.
[0150] Embodiment 21 includes a method according to embodiment 20 or some other embodiment herein, wherein the MO-SDT transmission is a random access transmission or a configured grant transmission.
[0151] Embodiment 22 includes a method according to embodiment 19 or some other embodiment herein, wherein the base station is an anchor base station, and the method further includes: receiving a context acquisition request from a serving base station; and sending the data to the serving base station based on the context acquisition request.
[0152] Embodiment 23 includes a method according to embodiment 22 or some other embodiment herein, wherein the context acquisition request includes an MT-SDT indication, and sending the data to the serving base station is also based on the MT-SDT indication.
[0153] Embodiment 24 may include an apparatus comprising means for performing one or more elements of a method as described or related to any one of Embodiments 1 to 23, or any other method or process described herein.
[0154] Embodiment 25 may include one or more computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described or related to any one of Embodiments 1 to 23 or any other method or process described herein.
[0155] Embodiment 26 may include a device comprising logic components, modules, or circuits for performing one or more elements of a method as described or related to any of Embodiments 1 to 23, or any other method or process described herein.
[0156] Embodiment 27 may include methods, techniques or processes as described or related to any one of Embodiments 1 to 23, or portions or components thereof.
[0157] Embodiment 28 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or a portion thereof, as described or related to any one of Embodiments 1 to 23.
[0158] Embodiment 29 may include a signal as described or related to any one of embodiments 1 to 23, or a portion or component thereof.
[0159] Embodiment 30 may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or associated with any one of Embodiments 1 to 23, or otherwise described in the present disclosure.
[0160] Embodiment 31 may include a signal encoded with data as described or associated with any one of Embodiments 1 to 23, or a portion or component thereof, or otherwise described in this disclosure.
[0161] Embodiment 32 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU or message as described or associated with any one of Embodiments 1 to 23, or a portion or component thereof, or otherwise described in the present disclosure.
[0162] Embodiment 33 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or portion thereof, as described or related to any one of Embodiments 1 to 23.
[0163] Embodiment 34 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process, or a portion thereof, as described or related to any one of Embodiments 1 to 23.
[0164] Embodiment 35 may include signals in a wireless network as shown and described herein.
[0165] Embodiment 36 may include a method of communicating in a wireless network as shown and described herein.
[0166] Embodiment 37 may include a system for providing wireless communications as shown and described herein.
[0167] Embodiment 38 may include an apparatus for providing wireless communications as shown and described herein.
[0168] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various embodiments.
[0169] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to include all such variations and modifications.
Claims
1. One or more computer-readable media having instructions that, when executed by one or more processors, cause a user equipment (UE): Sending an indication of Mobile Terminated (MT)-Small Data Transfer (SDT) capability to the network; receiving a radio resource control (RRC) message including an MT-SDT configuration from the network; receiving a paging message from the network to indicate the presence of downlink data for the UE; as well as An MT-SDT operation is performed based on the paging message and the MT-SDT configuration.
2. The one or more computer-readable media of claim 1, wherein the instructions, when executed, further cause the UE to: generating an access stratum (AS) capability information element (IE) to include the MT-SDT capability; and The AS Capability IE is sent to the network.
3. One or more computer-readable media according to claim 1, wherein the MT-SDT capability indicates that the UE can perform a first MT-SDT process including a mobile originated (MO)-SDT transmission or can perform a second MT-SDT process that does not include a MO-SDT transmission.
4. The one or more computer-readable media of claim 1, wherein the MT-SDT capability indicates whether the UE supports one or more downlink (DL)-semi-persistent scheduling (SPS) configurations during an MT-SDT procedure.
5. The one or more computer-readable media of claim 1, wherein the MT-SDT capability is per UE, frequency band, frequency range, or duplex scheme.
6. The one or more computer-readable media of claim 1 , wherein to perform the MT-SDT operation, the UE: Sending a mobile originated (MO)-SDT based on the paging message; and An MT-SDT transmission is received after sending the MO-SDT transmission.
7. The one or more computer-readable media of claim 6, wherein the MO-SDT transmission is a random access transmission.
8. The one or more computer-readable media of claim 6, wherein the RRC message includes an indication of a configuration grant resource, and the MO-SDT transmission is a configuration grant transmission using the configuration grant resource.
9. The one or more computer-readable media of claim 6, wherein the RRC message further includes a MO-SDT configuration.
10. A user equipment (UE), the user equipment (UE) comprising: Radio frequency (RF) circuits; and a processing circuit coupled to the RF circuit, the processing circuit being configured to: receiving, via the RF circuitry, a radio resource control (RRC) message including a mobile terminated (MT)-small data transmission (SDT) configuration from a network; receiving, via the RF circuitry, a paging message from the network to indicate the presence of downlink data for the UE; as well as A physical downlink control channel (PDCCH) is monitored during a MT-SDT session, wherein the MT-SDT session begins at a time period after receiving the paging message.
11. The UE according to claim 10, wherein the processing circuit is further configured to: A feedback message is sent via the RF circuit to indicate successful receipt of the paging message.
12. The UE according to claim 11, wherein the processing circuit is further configured to: receiving information for configuring a physical uplink control channel (PUCCH) or a sounding reference signal (SRS) resource in the RRC message; and The feedback message is sent as a PUCCH or SRS transmission using the PUCCH or SRS resource.
13. The UE according to claim 12, wherein the processing circuit is further configured to: Selecting a downlink beam; and The PUCCH or SRS resource is selected based on an association between the downlink beam and the PUCCH or SRS resource.
14. The UE according to claim 11, wherein the processing circuit is further configured to: generating a medium access control (MAC) control element (CE); and The MAC CE is sent as the paging message using a physical uplink shared channel (PUSCH) resource.
15. The UE according to claim 10, wherein the processing circuit is further configured to: determining a cell radio network temporary identity (C-RNTI) based on the RRC message or an inactive radio network temporary identity (I-RNTI); and The PDCCH is monitored based on the C-RNTI.
16. The UE according to claim 10, wherein the processing circuit is further configured to: When the UE starts to monitor the PDCCH, starting an SDT timer; and The monitoring of the PDCCH is terminated based on expiration of the SDT timer.
17. The UE according to claim 10, wherein the processing circuit is further configured to: receiving, in the RRC message, configuration information for providing a semi-persistent scheduling (SPS) configuration; determining an SPS opportunity based on the SPS configuration; and The PDCCH is monitored in the SPS opportunity.
18. The UE according to claim 17, wherein the configuration information is used to configure a plurality of SPS configurations, and the processing circuit is further configured to: Activation information for activating the SPS configuration from among the plurality of SPS configurations is received in the paging message.
19. A method of operating a base station, the method comprising: receiving an indication of a mobile terminated (MT)-small data transmission (SDT) capability from a user equipment (UE); sending a radio resource control (RRC) message including an MT-SDT configuration to the UE; receiving data to be sent to the UE; as well as A paging message is sent to the UE to indicate the presence of the data to be sent to the UE in an MT-SDT transmission.
20. The method according to claim 19, further comprising: receiving a mobile originated (MO)-SDT transmission from the UE; as well as The MT-SDT transmission is sent to the UE based on the MO-SDT transmission.
