WO2024103072A1 - Transmission de petites données à terminaison mobile - Google Patents

Transmission de petites données à terminaison mobile Download PDF

Info

Publication number
WO2024103072A1
WO2024103072A1 PCT/US2023/079552 US2023079552W WO2024103072A1 WO 2024103072 A1 WO2024103072 A1 WO 2024103072A1 US 2023079552 W US2023079552 W US 2023079552W WO 2024103072 A1 WO2024103072 A1 WO 2024103072A1
Authority
WO
WIPO (PCT)
Prior art keywords
downlink transmission
ran
small data
timer
base station
Prior art date
Application number
PCT/US2023/079552
Other languages
English (en)
Inventor
Shiangrung YE
Original Assignee
Google Llc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Google Llc filed Critical Google Llc
Publication of WO2024103072A1 publication Critical patent/WO2024103072A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1848—Time-out mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • This disclosure relates to wireless communications and, more particularly, to small data transmissions (SDT) in the downlink direction, i.e., transmissions of small data from a base station to a user equipment (UE).
  • SDT small data transmissions
  • UE user equipment
  • the Packet Data Convergence Protocol (PDCP) sublayer of the radio protocol stack provides services such as transfer of user-plane data, ciphering, integrity protection, etc.
  • the PDCP layer defined for the Evolved Universal Terrestrial Radio Access (EUTRA) radio interface (see 3GPP specification TS 36.323) and New Radio (NR) (see 3GPP specification TS 38.323) provides sequencing of protocol data units (PDUs) in the uplink direction (from a user device, also known as a user equipment (UE), to a base station) as well as in the downlink direction (from the base station to the UE).
  • EUTRA Evolved Universal Terrestrial Radio Access
  • NR New Radio
  • the PDCP sublayer provides services for signaling radio bearers (SRBs) to the Radio Resource Control (RRC) sublayer.
  • the PDCP sublayer also provides services for data radio bearers (DRBs) to a Service Data Adaptation Protocol (SDAP) sublayer or a protocol layer such as an Internet Protocol (IP) layer, an Ethernet protocol layer, and an Internet Control Message Protocol (ICMP) layer.
  • SDAP Service Data Adaptation Protocol
  • IP Internet Protocol
  • ICMP Internet Control Message Protocol
  • the UE and a base station can use SRBs to exchange RRC messages as well as non-access stratum (NAS) messages, and can use DRBs to transport data on a user plane.
  • NAS non-access stratum
  • the RRC sublayer specifies the RRC IDLE state, in which a UE does not have an active radio connection with a base station; the RRC CONNECTED state, in which the UE has an active radio connection with the base station; and the RRC INACTIVE state to allow a UE to more quickly transition back to the RRC CONNECTED state due to Radio Access Network (RAN)-level base station coordination and RAN-paging procedures.
  • RAN Radio Access Network
  • the UE when the UE has data to send (e.g., due to an outgoing phone call, browser launch, file upload) or receives a paging message from the base station, the UE transitions to the RRC CONNECTED state by requesting that the base station establish a new radio connection (e.g., by sending an RRC Setup Request message) or resume the suspended radio connection (e.g., by sending an RRC Resume Request message).
  • the UE in the RRC INACTIVE state has data below a certain predefined or configured small threshold to transmit to a base station. This data is referred to as “small data.”
  • a base station can have only small data to transmit to the UE.
  • a UE or a base station can generate small data periodically or non-periodically.
  • applications or services that generate small data include messaging services, email clients that provide heartbeat or keep-alive notifications, positioning services, industrial sensors such as those that periodically report temperature, pressure, humidity, etc., and smart meters.
  • 3GPP has introduced a Small Data Transmission (SDT) procedure to allow a UE to transmit or receive a small amount of data without transitioning to the RRC INACTIVE state, thereby preserving radio resources and reducing the amount of time required to communicate the small data.
  • SDT Small Data Transmission
  • MO- SDT mobile-originated SDT
  • MO-SDT mobile-terminated SDT
  • a UE receives a first downlink transmission including information which the UE can use to receive downlink small data.
  • the information can include a configuration such as a time-frequency resource, an indication of periodicity, or a modulation and encoding scheme; or the information can include an indication of a resource via which the UE can receive a subsequent paging message; or the information can include an identifier such as RNTI, C-RNTI, or group ID for example.
  • the UE attempts to receive, in accordance with the information in the first downlink transmission, a second downlink transmission related to the small data.
  • the second downlink transmission can be a message including small data or a message including a DCI for receiving the small data.
  • the UE When the UE receives the small data, the UE transmits an acknowledgement to the base station in an uplink transmission. In some cases, the UE further monitors a re-transmission of the small data or a transmission of new downlink data.
  • the UE can use one or more timers to delimit the periods of time during which can receive the second downlink transmission and/or the subsequent downlink transmission.
  • the UE When the UE detects a triggering event for discontinuing reception of the second downlink transmission, such as selection or selection of a new cell or transition to the connected state, for example, the UE can release the received configuration and, in some cases, notify the base station accordingly.
  • a triggering event for discontinuing reception of the second downlink transmission such as selection or selection of a new cell or transition to the connected state
  • An example embodiment of these techniques is a method implemented in a user equipment (UE).
  • the method comprises receiving, from a radio access network (RAN), a first downlink transmission including information related to subsequently receiving a small data from the RAN; attempting to receive, from the RAN and using the information, and when operating in an active state of a protocol for controlling radio resources, a second downlink transmission related to the small data; and in response to determining that the UE cannot correctly receive the second downlink transmission, performing an action related to a radio connection between the UE and the RAN.
  • RAN radio access network
  • Another example embodiment of these techniques is a UE comprising a transceiver and processing hardware configured to implement the method above.
  • Fig. l is a block diagram of an example system in which a radio access network (RAN) and a user device can implement the techniques of this disclosure for flexible
  • RAN radio access network
  • Fig. 2 is a block diagram of an example protocol stack according to which the UE of Fig. 1 communicates with base stations;
  • FIG. 3 is a messaging diagram of an example scenario in which a UE and a base station perform an MT-SDT procedure;
  • Fig. 4 is a flow diagram of an example method for performing MT-SDT, which can be implemented in the UE of Fig. 1;
  • Fig. 5 is a flow diagram of an example method for discontinuing MT-SDT, which can be implemented in the UE of Fig. 1.
  • Fig. 1 depicts an example wireless communication system 100 in which a communication devices can use flexible buffer size reporting techniques.
  • the wireless communication system 100 includes a UE 102, a base station (BS) 104, a base station 106 and a core network (CN) 110.
  • the UE 102 initially connects to the base station 104.
  • the base station 104 can perform an SN addition to configure the UE 102 to operate in dual connectivity (DC) with the base station 104 and the base station 106.
  • the base stations 104 and 106 operate as an MN and an SN for the UE 102, respectively.
  • a core network (CN) 110 can be for example a fifth-generation core (5GC).
  • the base station 104 can be an eNB supporting an SI interface for communicating with the CN 110 implemented as an EPC, an ng-eNB supporting an NG interface for communicating with the CN 110 implemented as a 5GC, or a gNB that supports an NR radio interface as well as an NG interface for communicating with the CN 110 implemented as a 5GC.
  • the base stations 104 and 106 can support an X2 or Xn interface.
  • the CN 110 includes a User Plane Function (UPF) 162 and an Access and Mobility Management (AMF) 164, and/or Session Management Function (SMF) 166.
  • UPF User Plane Function
  • AMF Access and Mobility Management
  • SMF Session Management Function
  • the UPF 162 is generally configured to transfer userplane packets related to audio calls, video calls, Internet traffic, etc.
  • the AMF 164 is configured to manage authentication, registration, paging, and other related functions
  • the SMF 166 is configured to manage PDU sessions.
  • the base station 104 supports cell 124A, and the base station 106 supports a cell 126.
  • the cells 124A and 126 can partially overlap, so that the UE 102 can communicate with the base station 104 and/or the base station 106 in multiple connectivity scenarios, handover scenarios, etc.
  • the base station 104 can support additional cell(s) such as cells 124B and 124C, and the base station 106 can support additional cell(s) (not shown in Fig. 1 A).
  • the cells 124A, 124B and 124C can partially overlap, so that the UE 102 can communicate in carrier aggregation (CA) with the base station 104.
  • CA carrier aggregation
  • the wireless communication network 100 can include any suitable number of base stations supporting NR cells or cells that implement other RATs such as EUTRA.
  • EUTRA NR cells or cells that implement other RATs
  • the examples below refer specifically to specific CN types (EPC, 5GC) and RAT types (5GNR and EUTRA)
  • the techniques of this disclosure also can apply to other suitable radio access and/or core network technologies such as sixth generation (6G) radio access and/or 6G core network or 5G NR-6G DC.
  • each of the base stations 104 and 106 is equipped with processing hardware 130 that can include one or more general -purpose processors (e.g., CPUs) and a non-transitory computer-readable memory storing instructions that the one or more general-purpose processors execute. Additionally or alternatively, the processing hardware 130 can include special-purpose processing units.
  • the processing hardware 130 can include a PHY controller 132 configured to transmit data and control signal on physical downlink (DL) channels and DL reference signals with one or more user devices (e.g. UE 102) via one or more cells (e.g., the cell(s) 124A, 124B and/or 124C) and/or one or more TRPs.
  • DL physical downlink
  • UE 102 user devices
  • cells e.g., the cell(s) 124A, 124B and/or 124C
  • the PHY controller 132 is also configured to receive data and control signal on physical uplink (UL) channels and/or UL reference signals with the one or more user devices via one or more cells (e.g., the cell(s) 124A, 124B and/or 124C) and/or one or more TRPs.
  • the processing hardware 130 in an example implementation includes a MAC controller 134 configured to perform MAC functions with one or more user devices.
  • the MAC functions includes a random access (RA) procedure, managing UL timing advance for the one or more user devices, and/or communicating UL/DL MAC PDUs with the one or more user devices.
  • the processing hardware 130 can further include an RRC controller 136 to implement procedures and messaging at the RRC sublayer of the protocol communication stack.
  • the RRC controller 132 may be configured to support RRC messaging associated with handover procedures, and/or to support the necessary operations when the base station 104 operates as an MN relative to an SN or as an SN relative to an MN.
  • Each of the base stations 104 and 106 is further equipped with RF circuitry 138 that can include any suitable number of antennas and electronic components for supporting the radio interface at the physical layer.
  • the UE 102 is equipped with processing hardware 150 that can include one or more general-purpose processors such as CPUs and non-transitory computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and/or special-purpose processing units.
  • the PHY controller 152 is also configured to receive data and control signal on physical DL channels and/or DL reference signals with the base station 104 or 106 via one or more cells (e.g., the cell(s) 124A, 124B, 124C and/or 126) and/or one or more TRPs.
  • the PHY controller 152 is also configured to transmit data and control signal on physical UL channels and/or UL reference signals with the base station 104 or 106 via one or more cells (e.g., the cell(s) 124A, 124B, 124C and/or 126) and/or one or more TRPs.
  • the processing hardware 150 in an example implementation includes a MAC controller 154 configured to perform MAC functions with base station 104 or 106.
  • the MAC functions includes a random access procedure, managing UL timing advance for the one or more user devices, and communicating UL/DL MAC PDUs with the base station 104 or 106.
  • the processing hardware 150 can further include an RRC controller 156 to implement procedures and messaging at the RRC sublayer of the protocol communication stack.
  • the UE 102 is equipped with RF circuitry 158 that can include any suitable number of antennas and electronic components for supporting the radio interface at the physical layer.
  • FIG. 2 illustrates in a simplified manner a radio protocol stack according to which the UE 102 can communicate with an eNB/ng-eNB or a gNB.
  • Each of the base stations 104 or 106 can be the eNB/ng-eNB or the gNB.
  • the physical layer (PHY) 202A of EUTRA provides transport channels to the EUTRA Medium Access Control (MAC) sublayer 204A, which in turn provides logical channels to the EUTRA Radio Link Control (REC) sublayer 206A, and the EUTRA REC sublayer in turn provides REC channels to the EUTRA PDCP sublayer 208 and, in some cases, NR PDCP sublayer 210.
  • the PHY 202B of NR provides transport channels to the NR MAC sublayer 204B, which in turn provides logical channels to the NR REC sublayer 206B, and the NR REC sublayer 206B in turn provides REC channels to the NR PDCP sublayer 210.
  • the UE 102 in some implementations supports both the EUTRA and the NR stack, to support handover between EUTRA and NR base stations and/or DC over EUTRA and NR interfaces. Further, as illustrated in Fig. 2A, the UE 102 can support layering of NR PDCP 210 over EUTRA REC 206 A.
  • the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 receive packets (e.g., from the Internet Protocol (IP) layer, layered directly or indirectly over the PDCP layer 208 or 210) that can be referred to as service data units (SDUs), and output packets (e.g., to the RLC layer 206A or 206B) that can be referred to as protocol data units (PDUs). Except where the difference between SDUs and PDUs is relevant, this disclosure for simplicity refers to both SDUs and PDUs as “packets.”
  • IP Internet Protocol
  • PDUs protocol data units
  • the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 provide SRBs to exchange Radio Resource Control (RRC) messages, for example.
  • RRC Radio Resource Control
  • the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 provide DRBs to support data exchange.
  • the network can provide the UE 102 with an MN-terminated bearer that uses EUTRA PDCP 208 or MN-terminated bearer that uses NR PDCP 210.
  • the network in various scenarios also can provide the UE 102 with an SN-terminated bearer, which use only NR PDCP 210.
  • the MN-terminated bearer can be an MCG bearer or a split bearer.
  • the SN-terminated bearer can be a SCG bearer or a split bearer.
  • the MN-terminated bearer can be an SRB (e.g., SRB1 or SRB2) or a DRB.
  • the SN-terminated bearer can an SRB (e.g., SRB) or a DRB.
  • FIG. 3 is a messaging diagram of an example scenario 300 in which the UE 102 and the base station 104 perform an MT-SDT procedure.
  • the UE 102 can initially operate in the RRC CONNECTED, RRC INACTIVE, RRC IDLE state.
  • the base station 104 transmits 310 to the UE 102 a first downlink transmission, which can include a configuration the UE 102 can use during the MT-SDT procedure.
  • the first downlink transmission can be a transmission of system information, such as a System Information Block (SIB) which the base station 104 broadcasts in a cell.
  • SIB System Information Block
  • the first downlink transmission can an RRC message addressed to the UE 102, such a paging message or an RRCRe lease, RRCReject, or RRCReconfiguration message.
  • the first downlink transmission can include a certain (first) configuration the UE 102 can use to receive a second downlink transmission in the RRC CONNECTED, RRC INACTIVE, or RRC IDLE state.
  • the first configuration can include a time-frequency resource, an indication of periodicity of the reoccurrence of the time-frequency resource, and a modulation & coding scheme (MCS) for the second downlink transmission.
  • MCS modulation & coding scheme
  • the first downlink transmission indicates a frame, subframe, or time slot in which the UE 102 can receive a paging message or a Physical Downlink Control Channel (PDCCH) order in the RRC INACTIVE or RRC IDLE state.
  • the base station 104 thus can notify the UE 102 of downlink data.
  • PDCCH Physical Downlink Control Channel
  • the first downlink transmission includes a dedicated Radio Network Temporary Identifier (RNTI) such as C-RNTI or CS-RNTI, which the UE 102 then can use to receive downlink transmissions.
  • RNTI Radio Network Temporary Identifier
  • the first downlink transmission includes a group RNTI that the RAN assigned to a group of UEs that includes the UE 102.
  • the first downlink transmission includes a group ID that the RAN assigned to a group of UEs that includes the UE 102. The RAN can utilize the group ID in multicast or group-east transmissions.
  • the first downlink transmission includes timing advance information.
  • the UE 102 can use the timing advance information to set up and start the first timer discussed below.
  • the UE 102 can starts 312 a certain (first) timer in response to receiving 110 the first downlink transmission.
  • the UE 102 considers the uplink communications with the base station 104 synchronized while the first timer is running; the UE 102 considers the uplink synchronization lost after the first timer expires (unless a new synchronization event has occurred). While the UE 102 considers the uplink synchronized, the UE 102 can transmit small data in the uplink direction. If the UE 102 receives a timing advance command (TAC) from the base station 104 while the first timer is running, the UE 102 restarts the synchronization timer.
  • TAC timing advance command
  • the first timer in some implementations is the time alignment timer (TAT), which the UE 102 also uses in the RRC CONNECTED state.
  • the first timer in another implementation is the configured grant SDT (CG-SDT) TAT generally associated with CG-SDT procedures.
  • CG-SDT-TAT is a time alignment timer that controls the use of a configured grant for SDT.
  • the base station 104 optionally pages 320 the UE 102. Scenarios in which the UE 102 relies on the paging message for MT-SDT are considered below.
  • the base station 104 transmits 330 to the UE 102 a second downlink transmission, which can be a unicast, a group cast, or a multicast transmission.
  • a second downlink transmission which can be a unicast, a group cast, or a multicast transmission.
  • the UE 102 uses the dedicated RNTI the UE 102 received 330 in the first downlink transmission.
  • the UE 102 uses the group RNTI the UE 102 received 310 in the first downlink transmission.
  • the second downlink transmission can include one or multiple signals, on one or more channels.
  • the second downlink transmission can include a data transmission and/or a Downlink Control Information (DCI).
  • DCI Downlink Control Information
  • the UE 102 after the UE 102 receives 310 the first downlink transmission including the first configuration, the UE begins to monitor PDCCH according to the first configuration, to detect and receive 330 the second downlink transmission.
  • the UE 102 receives 310 the first downlink transmission with the first configuration while operating in the RRC CONNECTED state, and begins to monitor PDCCH for the second downlink transmission, according to the first configuration, upon transitioning to the RRC INACTIVE or RRC IDLE state.
  • the UE 102 receives a DCI in the RRC INACTIVE or RRC IDLE state, and the DCI activates the use of the first configuration.
  • the base station 104 sends a message to UE 102 to activate the use of the first configuration.
  • the UE 102 monitors PDCCH to receive 330 the second downlink transmission.
  • the base station 104 can transmit the DCI during one of the paging occasions.
  • the DCI also can indicate the second downlink transmission for the UE 102 to receive during the paging occasion or the subframe/slot related to the paging occasion.
  • the UE 102 receives system information including the first configuration and, after receiving the first configuration, the UE 102 begins to receive the second downlink transmission according to the first configuration.
  • the system information also can include an indication that the UE 102 should activate the first configuration.
  • the UE 102 receives 320 the paging message.
  • the paging message can include the identity of the UE 102 or the identity of the group to which the UE 102 belongs (group ID).
  • the UE starts to receive the second downlink transmission according to the first configuration.
  • Several example implementations are considered next in connection with the paging message.
  • the paging message can include or indicates a DCI for the second downlink transmission.
  • the UE 102 can store the DCI and then use the DCI to receive 330 the second downlink transmission.
  • the DCI included in the paging message can override the time- frequency resourced included in the first downlink transmission, or the DCI the UE 102 previously stored.
  • the paging message includes an indication of the presence of the second downlink transmission.
  • the UE 102 detects the DCI on the PDCCH, for example, during the paging occasion where the UE 102 receives the paging message. If the UE 102 detects the DCI, the UE can detect the second downlink transmission (a transmission on a Physical Data Shared Channel (PDSCH), for example) during the paging occasion. In another such implementation, the UE 102 detects a DCI at a pre-defined subframe/ slot relative to the paging occasion. If UE 102 detects the DCI, UE can detect the second downlink transmission (e.g. PDSCH) located at a pre-defined subframe/slot relative to the paging occasion. As a more specific example, the first transmission includes the subframe/slot offset relative to the paging occasion.
  • PDSCH Physical Data Shared Channel
  • the UE 102 receives 330 the second transmission during one or more of the paging occasions.
  • the base station 104 can transmit the second downlink transmission during the paging occasions even without transmitting 320 a paging message to the UE 102.
  • the UE 102 can still receive the second downlink transmission during the one or more paging occasions.
  • the UE 102 starts or restarts a second timer when the UE 102 starts to receive 330 the second downlink transmission (or the corresponding DCI). If the second timer expires or the UE 102 stops the second timer, the UE 102 stops receiving 330 the second downlink transmission and/or releases the first configuration. The UE 102 can use the second timer to control the use of the first configuration.
  • the UE 102 stops receiving the second downlink transmission and/or releases the first configuration after CG-SDT-TAT expires. As indicated above, the UE 102 uses the CG-SDT-TAT timer to control the use of a configured grant for SDT.
  • the UE 102 stops receiving the second downlink transmission and/or releases the first configuration after UE entering the
  • the UE 102 stops receiving the second downlink transmission and/or releases the first configuration after the UE 102 selects or re-selects another cell.
  • the UE 102 stops receiving the second transmission because the UE 102 has already changed the serving cell to a camping cell.
  • the UE 102 can also release the first configuration as well.
  • the UE 102 stops receiving the second downlink transmission and/or releases the first configuration.
  • the TAT generally relates to controlling uplink transmission for non-SDT cases.
  • the UE 102 stops receiving the second downlink transmission and/or releases the first configuration after receiving a DCI that deactivates the first configuration.
  • the UE 102 stops receiving the second downlink transmission and/or releases the first configuration when the first timer expires, of if the UE 102 stops the first timer. At this point, the UE 102 cannot transmit a feedback message (see event 340 discussed below) responsive to the second transmission. Thus, the UE 102 need not monitor the PDCCH to receive the second downlink transmission. The UE 102 also can release the second configuration.
  • the UE 102 in some cases initiates a buffer status report (BSR) after receiving 330 the second downlink transmission. After initiating the BSR, and if the UE 102 has an uplink grant, the UE 102 uses the uplink grant to transmit an uplink transmission which may include the BSR. If the UE 102 has no uplink grant at the time, the UE 102 can transmit a random access preamble to the base station 104.
  • BSR buffer status report
  • the base station 104 can acknowledge the uplink SDT by including feedback (e.g., positive acknowledgement, negative acknowledgement, a MAC PDU, a MAC CE) to the uplink SDT in the second downlink transmission to the UE 102.
  • feedback can be a MAC CE associated with a certain logical channel ID.
  • the UE 102 transmits 340, to the base station 104, a first uplink transmission, which can include feedback for the second downlink transmission 330.
  • the feedback can be for example a HARQ ACK, HARQ NACK, MAC CE, or MAC PDU.
  • the UE 102 can provide 340 the feedback to the base station 104 to indicate whether the UE 102 successfully received the downlink transmission. If the UE 102 does not successfully receive 330 the downlink transmission (e.g., due to failure to decode the downlink data), the base station 104 can retransmit 350 the second downlink transmission.
  • the UE 102 receives 310, as part of the first downlink transmission, a second configuration (e.g. PUCCH resource or uplink grant), and uses this second configuration to transmit 340 the first uplink transmission.
  • a second configuration e.g. PUCCH resource or uplink grant
  • the UE 102 can use the configured grant configured for SDT to transmit 340 the feedback.
  • the feedback can be a predefined MAC CE or MAC PDU.
  • the second configuration can specify resources associated with respective downlink transmit beams.
  • the UE 102 selects a downlink beam and then uses the corresponding resource to transmit 340 the feedback.
  • the base station 104 configures resources for transmitting 340 the feedback in both a high-frequency band and a low-frequency band.
  • the UE 102 can choose to transmit 340 the feedback within the high-frequency band or the low- frequency band.
  • the second configuration includes a PUCCH resource for transmitting 340 a HARQ ACK/NACK.
  • the UE 102 can reuse the configuration the UE used to transmit feedback in the RRC CONNECTED state.
  • the UE 102 in this case uses the same configuration to transmit feedback in RRC CONNECTED and RRC INACTIVE.
  • the UE releases the resources for transmitting feedback in
  • the UE 102 retains the configuration for transmitting 340 feedback in MT-SDT.
  • the base station 104 indicates which resources the UE 102 can use to transmit 340 the feedback.
  • the base station 104 indicates 320 a resource (e.g. PUCCH resource or uplink grant) in the paging message.
  • the paging message can include an index to the pool of resources included in the first downlink transmission (event 310), or the paging message can specify the resource (e.g. time/frequency, etc.) the UE 102 can use for the transmitting 340 the feedback.
  • the DCI the UE 102 uses to decode the paging message indicates a resource for UE to transmit the feedback.
  • the base station 104 transmits 320 the paging message on a certain resource block, and the ID of the resource block can be associated with a resource included in the first downlink transmission (event 310).
  • the UE 102 can determine which resource the UE 102 should use to transmit 340 the feedback.
  • the DCI which the UE 102 used to decode the second downlink transmission indicates a resource for the UE 102 to transmit the feedback.
  • the UE 102 uses the configured grant of CG-SDT to transmit 340 the feedback (e.g. MAC CE or MAC PDU) to the base station 104.
  • the base station 104 configures the UE with CG-SDT.
  • the base station 104 includes the configured grant for SDT in the first transmission (event 310).
  • the UE 102 can use the configured grant to transmit small data in the uplink direction.
  • the UE 102 can determine that it is not allowed to transmit 340 the feedback. In this case, the UE 102 can initiate a random access procedure, which can be RA-SDT defined specifically for SDT, or la legacy (general) random access procedure.
  • the base station 104 in some cases re-transmits 350 small data or transmits new small data to the UE 102.
  • the UE 102 can detect whether the base station 104 attempts another transmission or retransmission. For example, the UE 102 can monitor PDCCH to detect a DCI addressed to the UE 102.
  • the UE 102 stops attempting to detect or receive 350 further downlink transmissions (or the corresponding DCI). In one such case, the UE 102 selects or reselects another cell. Alternatively, when the UE 102 is detecting or attempting to detect a new transmission or a retransmission (event 350), the UE 102 can determine that it should not select or resect another cell, because otherwise the UE 102 will be unable to receive 350 the downlink transmission or retransmission. [0072] In one implementation, after selecting or reselecting another cell, the UE 102 notifies 360 the base station 104 that the UE 102 selected or reselected another cell.
  • the UE 102 can transmit 360 for example an RRCResumeRequest, RRCRequest, or an RRCReestablishment message.
  • the UE 102 can initiate a random access procedure (e.g. RA- SDT) on the (re)selected cell to transmit 360 the RRC message.
  • the base station 104 then can again retransmit the data to the UE on the (re)selected cell, as part of the event 350 or a new event.
  • the base station 104 can provide the UE 102 with a dedicated random access preamble or a larger power ramping step, to prioritize the preamble transmission over other UEs, in order for the UE 102 to initiate random access procedure on the selected/reselected cell.
  • the UE 102 can perform additional or alternative actions after selecting or reselecting a new cell. In one implementation, the UE 102 resumes or reestablishes an RRC connection on the new cell. In another implementation, the UE 102 allows the CG-SDT-TAT timer to expire. In yet another implementation, the UE 102 allows the TAT timer to expire.
  • the UE 102 transmits RRCResumeRequest to the base station 104, and receives an RRC Release. RRC Resume. or RRCSetup message in response. If the UE 102 successfully receives one of these messages, the UE 102 need not monitor the PDCCH to receive 350 the subsequent downlink transmission.
  • the UE 102 starts or restarts a third timer to control how long the UE 102 should attempt to detect potential downlink retransmission or other new downlink transmissions.
  • the 102 in this implementation monitors PDCCH until the third timer expires, to receive 350 downlink (re)transmission.
  • the UE 102 can start or restart the third timer in the following scenarios.
  • the UE 102 can start or restart the third timer after receiving a PDCCH.
  • the UE 102 can start or restart the third timer after a downlink transmission (e.g. PDSCH).
  • the UE 102 can start or restart the third timer after transmitting 340 the first uplink transmission.
  • the UE 102 can stop the timer if, for example, the CG-SDT-TAT timer expires, if the UE 102 enters the RRC CONNECTED state, after the UE select or reselects another cell, after the TAT timer expires, or after receiving a DCI that deactivates the first configuration. [0078] In one implementation, the UE 102 does not select or reselect another cell while the third timer is running.
  • the UE 102 when the first timer expires or is stopped, the UE 102 alsp stops the third timer. In other words, if the UE 102 loses synchronization with the base station 104 in the uplink direction, the UE 102 no longer needs to monitor new transmissions or retransmissions.
  • the UE 102 can implement one or more of the following fallback techniques.
  • the UE 102 can maintain a (re)transmission counter and/or a timer to delimit the period of time during which the UE 102 attempts to detect the event 350.
  • the UE 102 enters the RRC IDLE state.
  • the UE 102 selects or reselects to other cell.
  • the UE 102 initiates a random access procedure, e.g., RA-SDT.
  • the UE 102 sends an RRCResumeRequest, RRCRequest, or RRCReestablish message to request that the base station 103 resume or (re)establish the RRC connection.
  • the UE 102 stops using the second configuration and/or releases the second configuration.
  • the UE 102 releases the first configuration prior to receiving 330 the second downlink transmission. If the UE 102 releases the first configuration, the UE 102 may not be able to receive 330 the second downlink transmission. In that case, the UE does not need to transmit 340 any feedback to the base station 104.
  • the UE 102 enters the RRC CONNECTED state.
  • the second configuration may not be applicable to the UE 102 in the RRC CONNECTED state.
  • the UE 102 selects or reselects another cell. If the UE 102 camps on the other cell, the second configuration is not applicable in that cell.
  • the UE 102 resumes or establishes an RRC connection on another cell, where the configuration similarly is not applicable.
  • the first timer expires, or the UE 102 stops the first timer. The UE 102 in this case no longer has synchronization with the base station 104 in the uplink direction.
  • a method 400 can be implemented in the UE 102, for example, or another suitable UE.
  • the UE receives a first downlink transmission (see event 310).
  • the first downlink transmission can include information the UE 102 can use for MT-SDT, such as an explicit configuration for receiving a second downlink transmission or an indication of how the UE can receive a paging message (see event 320) related to MT- SDT.
  • the UE receives a subsequent downlink transmission such as the second downlink transmission (see event 330).
  • the UE transmits an uplink transmission (see event 340), which can include positive or negative feedback related to the downlink transmission.
  • the UE can receive a retransmission of the small data or a new transmission of further small data (see event 350).
  • a method 500 of Fig. 5 also can be implemented in the UE 102 or another suitable UE.
  • Block 502 is similar to block 402 of Fig. 4.
  • the UE attempts to receive a subsequent downlink transmission, but, at block 506, the UE receives a trigger event for discontinuing reception. This event can be for example the selection or reselection of another cell, timer expiration, reception of a new DCI, transition to another RRC state, etc.
  • the UE stops receiving the subsequent downlink transmission. In some cases, the UE releases the relevant configuration. In some cases, the UE notifies the base station that the UE has selected a new cell.
  • the “configuration activation command” can be replaced by “serving cell change command”, “Layer 1/Layer 2 switching command”, “lower layer switching command” or “ lower layer serving cell change command”.
  • the “fast serving cell configuration procedure” can be replaced by “fast serving cell change procedure”.
  • a user device in which the techniques of this disclosure can be implemented can be any suitable device capable of wireless communications such as a smartphone, a tablet computer, a laptop computer, a mobile gaming console, a point-of-sale (POS) terminal, a health monitoring device, a drone, a camera, a media-streaming dongle or another personal media device, a wearable device such as a smartwatch, a wireless hotspot, a femtocell, or a broadband router.
  • the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS).
  • ADAS advanced driver assistance system
  • the user device can operate as an internet-of-things (loT) device or a mobile-internet device (MID).
  • the user device can include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.
  • Modules may can be software modules (e.g., code, or machine- readable instructions stored on non-transitory machine-readable medium) or hardware modules.
  • a hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner.
  • a hardware module can comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), a digital signal processor (DSP), etc.) to perform certain operations.
  • FPGA field programmable gate array
  • ASIC application-specific integrated circuit
  • DSP digital signal processor
  • a hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations.
  • programmable logic or circuitry e.g., as encompassed within a general-purpose processor or other programmable processor
  • the decision to implement a hardware module in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
  • the techniques can be provided as part of the operating system, a library used by multiple applications, a particular software application, etc.
  • the software can be executed by one or more general-purpose processors or one or more special-purpose processors.

Landscapes

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

Abstract

Pour gérer une transmission de petites données à terminaison mobile (MT-SDT), un équipement utilisateur reçoit, en provenance d'un réseau d'accès radio (RAN), une première transmission en liaison descendante comprenant des informations relatives à la réception ultérieure de petites données provenant du RAN ; tente de recevoir, en provenance du RAN et à l'aide des informations, et lors du fonctionnement dans un état actif d'un protocole pour commander des ressources radio, une seconde transmission en liaison descendante associée aux petites données ; et en réponse à la détermination que l'UE ne peut pas recevoir correctement la seconde transmission en liaison descendante, effectue une action associée à une connexion radio entre l'UE et le RAN.
PCT/US2023/079552 2022-11-11 2023-11-13 Transmission de petites données à terminaison mobile WO2024103072A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263383481P 2022-11-11 2022-11-11
US63/383,481 2022-11-11

Publications (1)

Publication Number Publication Date
WO2024103072A1 true WO2024103072A1 (fr) 2024-05-16

Family

ID=89222205

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/079552 WO2024103072A1 (fr) 2022-11-11 2023-11-13 Transmission de petites données à terminaison mobile

Country Status (1)

Country Link
WO (1) WO2024103072A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022147817A1 (fr) * 2021-01-11 2022-07-14 Zte Corporation Procédé, dispositif et système de transmission de petites données dans des réseaux sans fil
WO2022151292A1 (fr) * 2021-01-14 2022-07-21 Nokia Shanghai Bell Co., Ltd. Transmission dans un mode de transmission de petites données
WO2022151036A1 (fr) * 2021-01-13 2022-07-21 Nec Corporation Procédés, dispositifs et support de communication
WO2022192124A1 (fr) * 2021-03-08 2022-09-15 Idac Holdings, Inc. Procédés, architectures, appareils et systèmes de transmission de petites données de liaison descendante (sdt dl) et de réception dans un état de réseau d'accès radio inactif (ran)

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022147817A1 (fr) * 2021-01-11 2022-07-14 Zte Corporation Procédé, dispositif et système de transmission de petites données dans des réseaux sans fil
WO2022151036A1 (fr) * 2021-01-13 2022-07-21 Nec Corporation Procédés, dispositifs et support de communication
WO2022151292A1 (fr) * 2021-01-14 2022-07-21 Nokia Shanghai Bell Co., Ltd. Transmission dans un mode de transmission de petites données
WO2022192124A1 (fr) * 2021-03-08 2022-09-15 Idac Holdings, Inc. Procédés, architectures, appareils et systèmes de transmission de petites données de liaison descendante (sdt dl) et de réception dans un état de réseau d'accès radio inactif (ran)

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 17)", vol. RAN WG2, no. V17.2.0, 29 September 2022 (2022-09-29), pages 1 - 210, XP052211355, Retrieved from the Internet <URL:https://ftp.3gpp.org/Specs/archive/38_series/38.300/38300-h20.zip 38300-h20.docx> [retrieved on 20220929] *
ANDRIJANA BREKALO ET AL: "LS to CT1 on Small data transmission", vol. 3GPP CT 1, no. Online; 20220512 - 20220520, 21 April 2022 (2022-04-21), XP052168736, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/tsg_ct/WG1_mm-cc-sm_ex-CN1/TSGC1_136e/Docs/C1-223315.zip R2-2204234.zip R2-2204234 Stage-2 introduction of SDT.docx> [retrieved on 20220421] *
HANUL LEE ET AL: "Discussion on MT-SDT", vol. 3GPP RAN 2, no. Toulouse, FR; 20221114 - 20221118, 4 November 2022 (2022-11-04), XP052216650, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG2_RL2/TSGR2_120/Docs/R2-2212581.zip R2-2212581_Discussion on MT-SDT.docx> [retrieved on 20221104] *

Similar Documents

Publication Publication Date Title
US11889577B2 (en) Methods for handling periodic radio access network notification area (RNA) update configuration upon reject
US11792635B2 (en) Methods for handling radio access network notification area (RNA) update configuration upon reject
US9357459B2 (en) Method and apparatus for cross link establishment
TWI657707B (zh) 處理無線通訊系統中狀態不匹配的裝置及方法
KR20130136539A (ko) 무선 액세스 기술 간 서비스 재시도 동안 세션 콘텍스트를 보존하기 위한 방법들 및 장치들
US20220124568A1 (en) Managing mcg fast recovery
US20240008115A1 (en) Managing ue connectivity with master node and secondary node
US20230199578A1 (en) Managing configurations
WO2022085663A1 (fr) Procédé et circuit intégré
WO2022080306A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2022080419A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2024103072A1 (fr) Transmission de petites données à terminaison mobile
CN114175843A (zh) 通信系统、通信终端以及网络
JP2021057792A (ja) 端末装置、基地局装置、方法、および、集積回路
WO2023106315A1 (fr) Dispositif terminal, dispositif de station de base et procédé
US20230269758A1 (en) Managing multicast and broadcast services
WO2024070447A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2022080341A1 (fr) Équipement terminal, dispositif de station de base et procédé
WO2024070379A1 (fr) Équipement terminal, procédé et circuit intégré
WO2023008043A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023013292A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2023069665A1 (fr) Activation d&#39;occasion de radiomessagerie d&#39;un état de veille pour l&#39;état inactif
JP2022046876A (ja) 端末装置、基地局装置、方法、および、集積回路
WO2023070119A1 (fr) Gestion d&#39;alignement temporel de liaison montante
CN116471650A (zh) 终端装置、基站装置以及方法