Paging techniques for small data transmission
By introducing the MT-SDT process in the wireless network, allowing user equipment to receive and send small data in an inactive state, solving the problem of low efficiency in sending small data in the prior art, and achieving lower signaling overhead and power consumption. Improves network response speed.
Patent Information
- Application Number
- CN202380033754.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-14
- Filing Date
- 2023-04-04
- Publication Date
- 2024-11-26
AI Technical Summary
In wireless networks, it is difficult for the prior art to efficiently manage the transmission of small data, especially for inactive user equipment (UE), which requires frequent conversion of connection states to receive and transmit small data, resulting in increased signaling overhead and power consumption, and delays. Larger.
Introduce a mobile termination small data transmission (MT-SDT) process, receive downlink data through the base station and determine that it can be sent through MT-SDT, generate paging messages related to SDT, and trigger the UE to execute the MT-SDT process, so that it can be in Receive multiple operations in an inactive state, including monitoring the PDCCH and sending the scheduling DCI, allowing small data transmission without transitioning to the connection state.
Reduces signaling overhead and UE power consumption, reduces delay, realizes the ability to quickly send small data in an inactive state, and improves network efficiency.
Smart Images

Figure CN119032599A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to U.S. Provisional Application No. 63 / 331,252, filed on April 14, 2022. The contents of said application are hereby incorporated by reference in their entirety. Technical Field
[0003] The present application relates to the field of wireless networks, and in particular to a paging technology for small data transmission. Background Art
[0004] The 3rd Generation Partnership Project (3GPP) Technical Specifications (TS) define standards for wireless networks. One area of research in developing these TSs is around managing small data transmissions. BRIEF DESCRIPTION OF THE DRAWINGS
[0005] Figure 1 A network environment according to some embodiments is illustrated.
[0006] Figure 2 Mobile Terminated (MT) - Small Data Transmission (SDT) operations according to some embodiments are illustrated.
[0007] Figure 3 A paging message according to some embodiments is illustrated.
[0008] Figure 4 Another paging message according to some embodiments is illustrated.
[0009] Figure 5 Another paging message according to some embodiments is illustrated.
[0010] Figure 6 Paging occasion configuration according to some embodiments is illustrated.
[0011] Figure 7 Paging operations according to some embodiments are illustrated.
[0012] Figure 8 MT-SDT operation according to some embodiments is illustrated.
[0013] Fig. 9 An operational flow / algorithm structure according to some embodiments is illustrated.
[0014] Fig.10 An operational flow / algorithm structure according to some embodiments is illustrated.
[0015] Fig.11 An operational flow / algorithm structure according to some embodiments is illustrated.
[0016] Fig.12 User equipment according to some embodiments is illustrated.
[0017] Fig.13 A network node according to some embodiments is illustrated. DETAILED DESCRIPTION
[0018] 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 can 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).
[0019] The following is a glossary of terms that may be used in this disclosure.
[0020] 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.
[0021] 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 transmitting 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).
[0022] 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.
[0023] 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.
[0024] 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.
[0025] 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.
[0026] 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 sending and receiving information.
[0027] 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.
[0028] 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.
[0029] 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.
[0030] 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.
[0031] 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) for providing one or more new radio (NR) cells presenting NR user plane and control plane protocol terminations to the UE 104.
[0032] 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.
[0033] 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.12 Baseband processor circuit 1204A.
[0034] 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, it may start in RRC idle, which may be after the UE 104 is turned on or after an inter-system cell reselection from a long term evolution (LTE) cell. For active communications, 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 RAN 108. In an RRC connection, the UE may be configured with at least one signaling radio bearer (SRB) for signaling (e.g., control messages) with a 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 transition the UE from RRC connected to RRC inactive using an RRC release procedure. 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.
[0035] The network can send paging messages to reach UEs in RRC idle or RRC inactive states. Paging can also be used to notify UEs (in idle, inactive or connected states) of changes in system information and Earthquake and Tsunami Warning System (ETWS) / Commercial Mobile Alert System (CMAS) indications via short messages.
[0036] Both paging messages and short messages can be addressed using a paging radio network temporary identity (P-RNTI) on a physical downlink control channel (PDCCH). Paging messages can be transmitted via a paging control channel (PCCH), while short messages can be transmitted directly on the PDCCH.
[0037] The UE may monitor one paging occasion (PO) per paging discontinuous reception (DRX) cycle. The paging message may have a CN initiated paging type or a RAN initiated paging type. The CN initiated paging type may be used to transition the UE from an idle state to a connected state with a 5G shortened temporary mobile user identity (S-TMSI) UE identifier (ID) for paging reception. The CN initiated paging type may have a paging DRX cycle equal to the minimum value of [a default cycle from a system information block (SIB) or a UE-specific cycle from a non-access stratum (NAS) signaling]. The RAN initiated paging type may be used to transition the UE from an inactive state to a connected state with an inactive radio network temporary identity (I-RNTI) UE ID for paging reception. The RAN initiated paging type may have a paging DRX cycle equal to the minimum value of [a default cycle from a SIB, a UE-specific cycle from NAS signaling, or a RAN-specific cycle from an RRC signal].
[0038] A PO may be a set of PDCCH monitoring occasions and may include a plurality of time slots in which a paging DCI (eg, a DCI scheduling a paging message) may be transmitted.
[0039] UE 104 may determine the system frame number (SFN) of the paging frame (PF) based on the following formula:
[0040] (SFN+PF_offset) mod T = (T div N) * (UE_ID mod N), Equation 1 where T is the DRX cycle of UE 104, N is the number of total paging frames in T, PF_offset is the offset used for PF determination, and UE_ID is 5G-S-TMSI mod 1024.
[0041] The index (i_s) of a PO can be determined by the following formula:
[0042] i_s=floor(UE_ID / N)mode Ns, Equation 2 where Ns is the number of paging occasions of the PF. N, Ns, and PF_offset may be determined based on the PCCH configuration.
[0043] The short message field in DCI format 1_0 may be used to send a short message on the PDCCH using the P-RNTI with or without an associated paging message. The short message field may include eight bits, the first of which provides a system information modification indication and the second provides an ETWS or CMAS indication. The first bit may be set to "1" to indicate a broadcast control channel modification other than SIB6, SIB7, and SIB8. The second bit may be set to "1" to indicate an ETWS primary notification, an ETWS secondary notification, or a CMAS notification. The remaining bits are considered to be reserved bits in legacy networks.
[0044] The paging message may be sent via the PCCH, which may be a physical downlink shared channel (PDSCH). One paging message may be used to notify up to 32 UEs.
[0045] Release 17 networks may utilize Paging Early Indication (PEI) in PDCCH transmissions to reduce UE power consumption due to false paging alerts. Each PO may be associated with a configured PEI opportunity. A UE may belong to a paging subgroup configured by the CN or calculated based on the UEID. The UE may monitor the PEI opportunities associated with its PO. If the UE receives a PEI with that subgroup ID, the UE shall start monitoring the PO.
[0046] 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 transmit a RAN paging message to request the UE to transition back to a connected state for data transmission.
[0047] 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 transitions 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 process of an SDT procedure and non-SDT data radio bearer (DRB) downlink data arrives at the network, the network may directly transmit an RRC recovery message during the SDT procedure and request the UE to transition back to a connected state.
[0048] 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 transmit downlink data to a UE in an inactive state without requiring the UE to transition to a connected state.
[0049] As mentioned above, the current purpose of UE-specific paging is to instruct the UE to return to the connected state. Embodiments describe various paging techniques that may be used to trigger the UE to enter the MT-SDT procedure so that it can receive SDT transmissions while remaining in the inactive state.
[0050] Figure 2 MT-SDT operations 200 are illustrated according to some embodiments.
[0051] MT-SDT operations 200 may include, at 204, BS 112 receiving UE-specific downlink data from CN 116. The downlink data may be directed to UE 104.
[0052] At 208, BS 112 may determine that downlink data may be sendable by MT-SDT. This determination may be based on the amount of data to be transmitted to UE 104 or channel conditions over the air interface.
[0053] The MT-SDT operation 200 may also include: at 212, the BS 112 generates and sends a transmission related to the SDT paging to the UE 104. At 216, the SDT paging related transmission may trigger the UE 104 to perform the MT-SDT process. The MT-SDT process may include multiple operations that enable the UE 104 to receive DL data in the MT-SDT. For example, the MT-SDT process 216 may involve the UE 104 monitoring the PDCCH to receive a scheduling DCI that schedules downlink resources for the MT-SDT. For another example, the MT-SDT process 216 may involve the UE 104 sending a mobile-initiated (MO)-SDT to the base station 112, and then the base station may send the MT-SDT as a subsequent transmission. In some embodiments, the BS 112 may schedule the UE-specific SDT via a UE-specific cell radio network temporary identifier (C-RNTI), and the data transmission may be transmitted via the initial BWP of the current serving cell.
[0054] In some embodiments, the SDT paging-related transmission may be a paging message with an SDT indication to be used as a trigger to the UE 104 .
[0055] Figure 3 An Abstract Syntax Notation 1 (ASN1) code for a paging message 300 according to some embodiments is illustrated. Unless otherwise described, the paging message 300 may be similar to a paging message as described in 3GPP TS 38.331 v16.7.0 (2021-12).
[0056] The paging message 300 may include multiple paging records within a paging record list. The paging record list may include up to a maximum number of paging records (maxNrofPageRec). Each paging record may be used to address a single UE.
[0057] The paging record of the paging message 300 may have an access type of non-3GPP or SDT 304. The base station 112 may set the access type to non-3GPP to indicate that the paging message is initiated due to a protocol data unit (PDU) session from a non-3GPP access. The base station 112 may set the access type to SDT 304 to indicate that the paging message is for MT-SDT transmission purposes. Therefore, the UE 104 may regard the detection of the SDT access type 304 as a trigger to perform the MT-SDT process at 216.
[0058] Figure 4 An ASN1 code for a paging message 400 according to some embodiments is illustrated. Unless otherwise described, the paging message 400 may be similar to a paging message as described in 3GPP TS 38.331 v16.7.0 (2021-12).
[0059] The paging message 400 may have an SDT-RNTI 404 within the paging UE identification field. The SDT-RNTI 404, which may have an I-RNTI value, may indicate that the paging is for MT-SDT transmission purposes. Therefore, the UE 104 may regard the detection of the SDT-RNTI 404 as a trigger to perform the MT-SDT process at 216.
[0060] The network may use RRC signaling to explicitly configure the SDT-RNTI 404 along with the legacy I-RNTI (eg, full I-RNTI). For example, the configuration may be done in an RRC release with a suspend configuration message that the network uses to request the UE to transition to an inactive state and enable the MT-SDT feature.
[0061] Figure 5 An ASN1 code for a paging message 500 according to some embodiments is illustrated. Unless otherwise described, the paging message 500 may be similar to a paging message as described in 3GPP TS 38.331 v16.7.0 (2021-12).
[0062] The paging message 500 may have an SDT purpose IE 504 in the paging record field. The base station 112 may set the SDT purpose IE 504 to SDT to indicate that the paging message is for MT-SDT transmission purposes. Therefore, the UE 104 may regard the detection of the SDT purpose IE 504 set to SDT as a trigger to perform the MT-SDT process at 216.
[0063] In some embodiments, the SDT paging-related transmission 212 may be, for example, a DCI transmission of a scheduled paging message. For example, the SDT paging-related transmission 212 may be a short message sent on the PDCCH using the P-RNTI, with or without an associated paging message using the short message field in the DCI format 1_0. In some embodiments, the short message transmission may include a bit (e.g., the third bit) set to "1" to indicate that the associated paging message is for MT-SDT transmission purposes. Therefore, the UE 104 may treat the detection of the third bit set to "1" of the paging scheduling DCI as a trigger to perform the MT-SDT process at 216.
[0064] If the SDT indication is carried in the paging short message DCI, the network may use the scheduled paging message to provide the UE identity. The paging message in this example may be similar to a traditional paging message and may not require an additional SDT indication.
[0065] In some embodiments, the SDT paging related transmission 212 can be a PDCCH transmission including a PEI. The PEI can trigger the UE 104 to enter the MT-SDT process 216 by including a bit indication to indicate whether the associated paging message is used for the MT-SDT transmission purpose. Additionally / alternatively, for SDT purposes, subgroups can be predefined / preconfigured. For example, the UE 104 can be associated with a first subgroup for traditional paging purposes and a second subgroup for SDT purposes. If the UE 104 detects a PEI with an ID of the first subgroup, the UE 104 can monitor the PO to detect traditional paging messages and continue to transition to the RRC connection state after receiving the paging message. On the other hand, if the UE 104 detects a PEI with an ID of the second subgroup, the UE 104 can determine that the associated paging message is for the MT-SDT transmission purpose. In this way, the UE 104 can regard the SDT indication in the PEI (through a dedicated bit or identification of the SDT subgroup) as a trigger for performing the MT-SDT process at 216.
[0066] The PO of the DCI used to schedule the RAN paging message may be referred to as the RAN PO, and the PO of the DCI used to schedule the SDT paging message may be referred to as the SDT PO. Figure 6 Various PO configurations are illustrated according to some embodiments.
[0067] In PO configuration 600, SDT PO and RAN PO may completely overlap each other. That is, UE 104 may determine PO using conventional methods and use those PO for both RAN paging and SDT paging.
[0068] In PO configuration 604, the SDT PO may have an SDT specific paging cycle. The SDT specific paging cycle may be configured by the RAN 108 via a broadcast message such as a SIB or by a UE-specific configuration sent by RRC signaling. As shown, the initial SDT PO and the RAN PO may overlap, but the SDT PO may have a paging cycle that is shorter than the paging cycle of the RAN PO. As shown, the RAN specific paging cycle may be a multiple of the SDT specific paging cycle. This may result in a partial overlap between the RAN PO and the SDT PO. The UE 104 may use the SDT paging cycle to derive the SDT PO for which it will monitor SDT paging messages.
[0069] Although PO configuration 604 shows that the SDT paging cycle is shorter than the RAN paging cycle, in other embodiments, the SDT paging cycle may be longer than the RAN paging cycle.
[0070] In PO configuration 608, the position of the SDT PO may be derived relative to the RAN PO. For example, the SDT PO may be set to be offset after the RAN PO in the time domain. The offset may be dynamically or statically configured or predefined by the 3GPP TS.
[0071] Although PO configuration 608 shows the SDT PO offset after the RAN PO, other embodiments may have the SDT PO offset before the RAN PO.
[0072] Figure 7 Paging operations 700 are illustrated in accordance with some embodiments.
[0073] At 704, BS 112 may send a paging message to UE 104. UE 104 may be in an inactive or idle state. The paging message may be an SDT paging message, a RAN paging message, or a CN paging message.
[0074] At 708, the UE 104 can determine the paging type of the received paging message.
[0075] If the UE 104 determines at 708 that the paging message is an SDT paging message, the paging operation 700 may proceed to 712, where the UE 104 remains in an inactive state and performs an MT-SDT procedure. The MT-SDT procedure may be similar to that described above with respect to Figure 2 MT-SDT process 216 discussed.
[0076] If the UE 104 determines at 708 that the paging message is a RAN paging message, the paging operations 700 may proceed to 716 where the UE 104 performs a conventional recovery procedure to transition from an inactive state to a connected state.
[0077] If the UE 104 determines at 708 that the paging message is a CN paging message, the paging operation 700 may proceed to 720, where the UE 104 performs an RRC establishment procedure to transition from an idle state to a connected state. A non-access stratum (NAS) layer of the UE 104 may trigger the RRC establishment procedure. If the UE 104 receives a CN paging message while in an inactive state, it may perform an enter idle operation by releasing the RRC connection and the stored inactive context, and the NAS may release the NAS connection and trigger the RRC establishment procedure and initiate a connection from the idle state.
[0078] In some instances, the UE 104 may receive multiple pages within one paging message. In this case, the UE 104 may prioritize the pages based on the paging type. For example, in some embodiments, the UE 104 may assign a high priority to CN pages, a medium priority to RAN pages, and a low priority to SDT pages. Thus, RAN pages may be given priority over SDT pages, and CN pages may be given priority over both RAN pages and SDT pages.
[0079] Figure 8 MT-SDT operations 800 according to some embodiments are illustrated. MT-SDT operations 800 may be performed in association with a roaming event. For example, when in an inactive state, UE 104 moves from a cell provided by anchor BS 808 to a cell provided by serving BS 804. Serving BS 804 and anchor BS 808 may be similar to those described above with respect to Figure 1 The base station 112.
[0080] MT-SDT operations 800 may include the CN 116 providing UE-specific DL data to the anchor BS 808. The DL data may be addressed to the UE 104.
[0081] After receiving the DL data, the anchor BS 808 may determine that the data can be delivered to the UE 104 through the MT-SDT procedure and may generate and send a RAN paging message. The RAN paging message may be forwarded to all serving BSs within the SDT RAN Notification Area (RNA).
[0082] In some embodiments, the RAN / anchor BS 808 may generate an SDT RNA and configure the SDT RNA to the UE 104. The UE 104 may use the configured SDT RNA to determine whether to allow the SDT process. For example, if the UE 104 resides on a cell of the SDT RNA, the UE 104 may initiate the SDT process. Otherwise, the UE 104 may only perform a traditional RRC recovery process. In other embodiments, the network may maintain the SDT RNA on the network side without configuring it to the UE 104.
[0083] 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 UE (such as, for example, UE 104 or 1300) or a component thereof (eg, processing circuit 1304).
[0084] The operational flow / algorithm structure 900 may include, at 904, receiving a transmission from a base station. The transmission may be associated with a paging operation. For example, the transmission may be a DCI scheduling a paging transmission, a PDCCH including a PEI, or the paging message itself.
[0085] The operational flow / algorithm structure 900 may also include, at 908, detecting a trigger for an MT-SDT process based on the transmission. If the transmission is a paging message, the detection of the trigger may be based on: a paging message including an indication of an SDT access type; an SDT paging UE identity; or an SDT IE. If the transmission is a scheduling DCI, the detection of the trigger may be based on the presence of an SDT indication in a short message field. If the transmission is a PDCCH with PEI, the detection of the trigger may be based on the presence of an SDT indication in a PEI field or the detection of a subgroup ID associated with a subgroup configured with an SDT purpose.
[0086] The operation flow / algorithm structure 900 may also include: at 912, performing MT-SDT operations based on the detection trigger. The MT-SDT operation may be an operation of an MT-SDT process that enables the reception of a downlink transmission including MT-SDT data. This may include monitoring the PDCCH for a DCI that schedules a downlink transmission, or initiating a MO-SDT that enables a downlink transmission as a subsequent transmission. MO-SDT may be similar to that described in the Change Requests (CRs) for Release 17 TS defined in: R2-2204234–Introduction of SDT, 3GPP TSG-RAN WG2 Meeting #117 Electronic Elbonia, February 21 to March 3, 2022; R2-2204216–Introduction of Small Data Transmission for MAC spec, 3GPP TSG-RAN2 Meeting #117 e Electronic, February 21 to March 3, 2022; and R2-2203768–Introduction of SDT, 3GPP TSG-RAN WG2 Meeting #117-e Electronic, February 21 to March 3, 2022.
[0087] Fig.10 An operational flow / algorithm structure 1000 according to some embodiments is shown. The operational flow / algorithm structure 1000 may be performed by a base station (such as, for example, BS 112, serving BS 804, or network node 1300) or a component thereof (eg, processing circuit 1304).
[0088] The operational flow / algorithm structure 1000 may include receiving a RAN paging message at 1004. The RAN paging message received from the anchor base station may include an MT-SDT indication. The MT-SDT indication may indicate that the anchor base station has data to be sent to the UE via MT-SDT.
[0089] The operational flow / algorithm structure 1000 may also include generating a transmission associated with the paging operation at 1008. The transmission may be a DCI scheduling the paging transmission, a PDCCH including a PEI, or the paging message itself.
[0090] The transmission may be generated to include an MT-SDT trigger. Similar to what is discussed above, if the transmission is a paging message, the MT-SDT trigger may be an indication of an SDT access type, an indication of an SDT paging UE identity, or an SDT IE. If the transmission is a PDCCH transmission with a PEI field, the MT-SDT trigger may be an SDT indication in the PEI field. If the transmission is a scheduled DCI, the MT-SDT trigger may be an SDT indication in the short message field.
[0091] Fig.11 An operational flow / algorithm structure 1100 is shown according to some embodiments. The operational flow / algorithm structure 1100 may be performed by a base station (such as, for example, BS 112, anchor BS 808, or network node 1300) or a component thereof (eg, processing circuit 1304).
[0092] The operational flow / algorithm structure 1100 may include determining at 1104 that downlink data for the UE can be delivered via the SDT process. The base station may make this determination based on the amount of data received or expected to be received. In some embodiments, if the amount of data is less than a predetermined threshold, the base station may determine that it can deliver the data via the MT-SDT process.
[0093] The operational flow / algorithm structure 1100 may also include generating a RAN paging message with an MT-SDT indication at 1108. The MT-SDT indication may prompt the receiving base station to transmit paging-related transmissions over the Uu interface in a manner that triggers the UE to perform MT-SDT operations to facilitate reception of MT-SDT transmissions. The RAN paging message may be generated for transmission over an Xn interface between base stations.
[0094] The operation flow / algorithm structure 1100 may also include sending a RAN paging message to one or more base stations at 1112. In some embodiments, the base station may send the RAN paging message to all serving base stations within the SDT-RNA.
[0095] Fig.12 UE 1200 according to some embodiments is illustrated. UE 1200 may be similar to Figure 1 UE 124 and is substantially interchangeable therewith.
[0096] UE 1200 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.
[0097] UE 1200 may include a processor 1204, an RF interface circuit 1208, a memory / storage device 1212, a user interface 1216, a sensor 1220, a driving circuit 1222, a power management integrated circuit (PMIC) 1224, an antenna 1226, and a battery 1228. The components of UE 1200 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.12 The block diagram of UE 1200 is intended to show a high-level view of certain of the components of UE 1200. 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.
[0098] Components of UE 1200 may be coupled to various other components via one or more interconnects 1232, 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.
[0099] The processor 1204 may include processor circuits such as, for example, a baseband processor circuit (BB) 1204A, a central processor unit circuit (CPU) 1204B, and a graphics processor unit circuit (GPU) 1204C. The processor 1204 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 1212) to cause the UE 1200 to perform operations as described herein.
[0100] In some embodiments, the baseband processor circuit 1204A can access the communication protocol stack 1236 in the memory / storage device 1212 to communicate through a 3GPP compatible network. Generally speaking, the baseband processor circuit 1204A can access the communication protocol stack 1236 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 1208.
[0101] The baseband processor circuit 1204A 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.
[0102] The memory / storage 1212 may include one or more non-transitory computer-readable media including instructions (e.g., the communication protocol stack 1236) that may be executed by one or more processors in the processor 1204 to cause the UE 1200 to perform various operations described herein. The memory / storage 1212 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1200. In some embodiments, some of the memory / storage 1212 may be located on the processor 1204 itself (e.g., L1 cache and L2 cache), while other memory / storage 1212 is located external to the processor 1204 but can be accessed via a memory interface. The memory / storage 1212 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.
[0103] The RF interface circuit 1208 may include a transceiver circuit and a radio frequency front end module (RFEM), which allows the UE 1200 to communicate with other devices through a radio access network. The RF interface circuit 1208 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.
[0104] In the receive path, the RFEM may receive the radiated signal from the air interface via antenna 1226 and proceed 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 processor 1204.
[0105] 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 1226.
[0106] In various embodiments, the RF interface circuit 1208 may be configured to send / receive signals in a manner compatible with NR access technology.
[0107] Antenna 1226 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 1226 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple input / multiple output communications. Antenna 1226 may include: microstrip antennas; printed antennas fabricated on the surface of one or more printed circuit boards; patch antennas or phased array antennas. Antenna 1226 may have one or more panels designed for specific frequency bands including frequency bands in FR1 or FR2.
[0108] The user interface 1216 includes various input / output (I / O) devices designed to enable a user to interact with the UE 1200. The user interface 1216 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, touchpad, 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 1200.
[0109] Sensors 1220 may include devices, modules, or subsystems that are designed to detect events or changes in their environment and transmit 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.
[0110] The driver circuit 1222 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 1200. The driver circuit 1222 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 1200. For example, the driver circuit 1222 may include circuits that facilitate coupling a UICC (e.g., UICC 148) to the UE 1200. For additional examples, the driver circuit 1222 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 1220 and controlling and allowing access to the sensor 1220; 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; an audio driver for controlling and allowing access to one or more audio devices.
[0111] The PMIC 1224 may manage the power provided to various components of the UE 1200. Specifically, with respect to the processor 1204, the PMIC 1224 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.
[0112] In some embodiments, the PMIC 1224 may control or otherwise be a part of various power saving mechanisms of the UE 1200 including DRX, as discussed herein.
[0113] The battery 1228 can power the UE 1200, but in some examples, the UE 1200 can be installed in a fixed location and can have a power source coupled to the grid. The battery 1228 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 implementations, such as in vehicle-based applications, the battery 1228 can be a typical lead-acid car battery.
[0114] Fig.13 Illustrated is a network node 1300 according to some embodiments. The network node 1300 may be similar to the base station 132, the serving BS 804, or the anchor BS 808 and may be substantially interchangeable therewith.
[0115] The network node 1300 may include processing circuitry 1304 , RF interface circuitry 1308 (if implemented as an access node), core network (CN) interface circuitry 1312 , memory / storage circuitry 1316 , and antenna structures 1326 .
[0116] Components of network node 1300 may be coupled to various other components via one or more interconnects 1328 .
[0117] Processor circuit 1304, RF interface circuit 1308, memory / storage circuit 1316 (including communication protocol stack 1310), antenna structure 1326 and interconnect 1328 may be similar to those described with respect to Fig.12 Like named elements are shown and described.
[0118] The CN interface circuit 1312 may provide connectivity to a core network (e.g., a 5GC using a 5th Generation Core Network (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 1300 via optical fiber or wireless backhaul. The CN interface circuit 1312 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 1312 may include multiple controllers for providing connectivity to other networks using the same or different protocols.
[0119] In some embodiments, the network node 1300 may be coupled to a transmit receive point (TRP) using an antenna structure 1326, a CN interface circuit, or other interface circuitry.
[0120] 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.
[0121] 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.
[0122] Example
[0123] In the following sections, additional exemplary embodiments are provided.
[0124] Embodiment 1 includes a method of operating a user equipment (UE), the method comprising: receiving a transmission from a base station, the transmission being associated with a paging operation; detecting a trigger for a mobile termination (MT)-small data transmission (SDT) process based on the transmission received from the base station; and performing an MT-SDT operation based on the detection of the trigger.
[0125] Embodiment 2 includes a method according to embodiment 1 or some other embodiment herein, wherein the sending is a paging message.
[0126] Embodiment 3 includes a method according to embodiment 2 or some other embodiment herein, wherein the paging message includes an indication of an SDT access type, and the method further includes: detecting the triggering of the MT-SDT based on the indication of the SDT access type.
[0127] Embodiment 4 includes a method according to Embodiment 2 or some other embodiment herein, wherein the paging message includes an indication of an SDT paging UE identifier, and the method further includes: detecting the triggering of the MT-SDT based on the indication of the SDT paging UE identifier.
[0128] Embodiment 5 includes a method according to embodiment 4 or any other embodiment herein, wherein the SDT paging UE identity includes an Inactive Radio Network Temporary Identity (I-RNTI) value.
[0129] Embodiment 6 includes a method according to embodiment 2 or some other embodiment herein, wherein the paging message includes a paging record having an SDT information element (IE), and the method further includes detecting the triggering of the MT-SDT based on the SDT IE.
[0130] Embodiment 7 includes a method according to embodiment 1 or some other embodiment herein, wherein the transmission is a downlink control information (DCI) transmission that schedules a paging message.
[0131] Embodiment 8 includes a method according to embodiment 7 or some other embodiment herein, wherein the DCI transmission includes a short message field with an SDT indication, and the method further includes: detecting the triggering of the MT-SDT process based on the SDT indication.
[0132] Embodiment 9 includes a method according to embodiment 1 or some other embodiment herein, wherein the transmission is a physical downlink control channel (PDCCH) transmission including a paging early indication (PEI) field having an SDT indication, and the method further includes: detecting the triggering of the MT-SDT process based on the SDT indication.
[0133] Embodiment 10 includes a method according to embodiment 1 or some other embodiment herein, wherein the transmission is a physical downlink control channel (PDCCH) transmission including a paging early indication (PEI) field having a subgroup ID, the subgroup ID being associated with a subgroup configured with an SDT purpose, and the method further includes: detecting the triggering of the MT-SDT process based on the subgroup ID.
[0134] Embodiment 11 includes the method according to embodiment 1 or any other embodiment herein, the method further comprising: monitoring an SDT paging occasion; and receiving the transmission based on the monitoring.
[0135] Embodiment 12 includes a method according to embodiment 11 or some other embodiment herein, wherein the one or more SDT paging occasions completely or partially overlap with one or more RAN paging occasions.
[0136] Embodiment 13 includes the method according to embodiment 11 or any other embodiment herein, wherein the one or more SDT paging occasions are respectively offset from the one or more RAN paging occasions by a predetermined amount in the time domain.
[0137] Embodiment 14 includes a method for operating a serving base station, the method comprising: receiving a radio access network (RAN) paging message with a mobile termination (MT)-small data transmission (SDT) indication from an anchor base station; generating a transmission associated with a paging operation based on the RAN paging message with the MT-SDT indication, the transmission including an MT-SDT trigger; and sending the transmission to a user equipment (UE).
[0138] Embodiment 15 includes a method according to embodiment 14 or some other embodiment herein, wherein the transmission is a paging message.
[0139] Embodiment 16 includes a method according to embodiment 15 or some other embodiment herein, wherein the MT-SDT trigger includes: an indication of an SDT access type; an indication of an SDT paging UE identity; or an SDT information element (IE).
[0140] Embodiment 17 includes a method according to embodiment 15 or some other embodiment herein, wherein the transmission is a downlink control information (DCI) transmission that schedules a paging message.
[0141] Embodiment 18 includes a method according to embodiment 17 or some other embodiment herein, wherein the trigger includes a short message field with an SDT indication within the DCI transmission.
[0142] Embodiment 19 includes a method according to embodiment 15 or some other embodiment herein, wherein the transmission is a physical downlink control channel (PDCCH) transmission, and the trigger includes a paging early indication (PEI) field with an SDT indication within the PDCCH transmission.
[0143] Embodiment 20 includes a method of operating a first base station, the method comprising: receiving downlink data for a user equipment (UE); determining that the downlink data can be delivered via a small data transmission (SDT) process; generating a radio access network (RAN) paging message with a mobile termination (MT)-SDT indication based on the determination; and sending the RAN paging message to a second base station.
[0144] Embodiment 21 includes a method according to embodiment 20 or any other embodiment herein, wherein an SDT RAN Notification Area (RNA) includes a plurality of base stations, and the method further includes: sending the RAN paging message to the plurality of base stations.
[0145] Example 22 may include an apparatus comprising means for performing one or more elements of the method described in or related to any of Examples 1 to 21, or any other method or process described herein.
[0146] Embodiment 23 may include one or more non-transitory 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 in or related to any one of Embodiments 1 to 21 or any other method or process described herein.
[0147] Embodiment 24 may include a device comprising logic components, modules, or circuits for performing one or more elements of a method described in or related to any of Embodiments 1 to 21, or any other method or process described herein.
[0148] Embodiment 25 may include methods, techniques or processes described in or related to any one of Embodiments 1 to 21, or parts or components thereof.
[0149] Embodiment 26 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 21.
[0150] Embodiment 27 may include a signal as described or related to any one of Embodiments 1 to 21, or a portion or component thereof.
[0151] Embodiment 28 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 21, or otherwise described in the present disclosure.
[0152] Embodiment 29 may include a signal encoded with data as described or associated with any one of Embodiments 1 to 21, or a portion or component thereof, or otherwise described in this disclosure.
[0153] Embodiment 30 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 21, or a portion or component thereof, or otherwise described in the present disclosure.
[0154] Embodiment 31 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, described in or related to any one of Embodiments 1 to 21.
[0155] Embodiment 32 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 21.
[0156] Embodiment 33 may include signals in a wireless network as shown and described herein.
[0157] Embodiment 34 may include a method of communicating in a wireless network as shown and described herein.
[0158] Embodiment 35 may include a system for providing wireless communications as shown and described herein.
[0159] Embodiment 36 may include an apparatus for providing wireless communications as shown and described herein.
[0160] 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.
[0161] 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, cause a user equipment (UE): receiving a transmission from a base station, the transmission being associated with a paging operation; detecting a trigger of a mobile terminated (MT)-small data transmission (SDT) procedure based on the transmission received from the base station; as well as An MT-SDT operation is performed based on the detection of the trigger.
2. The one or more computer-readable media of claim 1, wherein the transmission is a paging message.
3. The one or more computer-readable media of claim 2, wherein the paging message includes an indication of an SDT access type, and the instructions when executed further cause the UE to: The triggering of the MT-SDT procedure is detected based on the indication of the SDT access type.
4. The one or more computer-readable media of claim 2, wherein the paging message includes an indication of an SDT paging UE identity, and the instructions when executed further cause the UE to: The triggering of the MT-SDT procedure is detected based on the indication of the SDT paging UE identity.
5. The one or more computer-readable media of claim 4, wherein the SDT paging UE identity comprises an Inactive Radio Network Temporary Identity (I-RNTI) value.
6. The one or more computer-readable media of claim 2, wherein the paging message comprises a paging record having an SDT information element (IE), and the instructions when executed further cause the UE to: The triggering of the MT-SDT procedure is detected based on the SDT IE.
7. The one or more computer-readable media of claim 1, wherein the transmission is a downlink control information (DCI) transmission that schedules a paging message.
8. The one or more computer-readable media of claim 7, wherein the DCI transmission includes a short message field with an SDT indication, and the instructions when executed further cause the UE to: The triggering of the MT-SDT procedure is detected based on the SDT indication.
9. The one or more computer-readable media of claim 1 , wherein the transmission is a physical downlink control channel (PDCCH) transmission including a paging early indication (PEI) field with an SDT indication, and the instructions, when executed, further cause the UE to: The triggering of the MT-SDT procedure is detected based on the SDT indication.
10. The one or more computer-readable media of claim 1, wherein the transmission is a physical downlink control channel (PDCCH) transmission including a paging early indication (PEI) field having a subgroup ID associated with a subgroup configured with an SDT purpose, and the instructions when executed further cause the UE to: The triggering of the MT-SDT procedure is detected based on the sub-group ID.
11. The one or more computer-readable media of claim 1 , wherein the instructions, when executed, further cause the UE to: Monitoring SDT paging occasions; and The transmission is received based on the monitoring.
12. The one or more computer-readable media of claim 11, wherein the one or more SDT paging occasions fully or partially overlap with one or more RAN paging occasions.
13. The one or more computer-readable media of claim 11, wherein the one or more SDT paging occasions are respectively offset from one or more RAN paging occasions by a predetermined amount in the time domain.
14. A method for operating a serving base station, the method include: receiving a radio access network (RAN) paging message with a mobile terminated (MT)-small data transmission (SDT) indication from an anchor base station; generating a transmission associated with a paging operation based on the RAN paging message with the MT-SDT indication, the transmission comprising an MT-SDT trigger; as well as The transmission is sent to a user equipment (UE).
15. The method of claim 14, wherein the transmission is a paging message.
16. The method according to claim 15, wherein the MT-SDT triggers include: An indication of an SDT access type; an indication of an SDT paging UE identity; or an SDT information element (IE).
17. The method of claim 15, wherein the transmission is a downlink control information (DCI) transmission that schedules a paging message.
18. The method of claim 17, wherein the MT-SDT trigger comprises a short message field with an SDT indication within the DCI transmission.
19. The method of claim 15, wherein the transmission is a physical downlink control channel (PDCCH) transmission, and the trigger comprises a paging early indication (PEI) field with an SDT indication within the PDCCH transmission.
20. A first base station, wherein the first base station include: an interface circuit for receiving downlink data for a user equipment (UE); A processing circuit coupled to the interface circuit, the processing circuit being configured to: determining that the downlink data can be delivered via a small data transmission (SDT) procedure; generating a radio access network (RAN) paging message with a mobile terminated (MT)-SDT indication based on the determination; as well as The interface circuit is enabled to send the RAN paging message to the second base station.
21. The first base station of claim 20, wherein an SDT RAN Notification Area (RNA) includes a plurality of base stations, and the processing circuitry further causes the interface circuitry to send the RAN paging message to the plurality of base stations.
