[go: up one dir, main page]

WO2024092574A1 - Identification pour transmission de petites quantités de données - Google Patents

Identification pour transmission de petites quantités de données Download PDF

Info

Publication number
WO2024092574A1
WO2024092574A1 PCT/CN2022/129346 CN2022129346W WO2024092574A1 WO 2024092574 A1 WO2024092574 A1 WO 2024092574A1 CN 2022129346 W CN2022129346 W CN 2022129346W WO 2024092574 A1 WO2024092574 A1 WO 2024092574A1
Authority
WO
WIPO (PCT)
Prior art keywords
sdt
terminal device
identifier
procedure
network device
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2022/129346
Other languages
English (en)
Inventor
Samuli Heikki TURTINEN
Jussi-Pekka Koskinen
Chunli Wu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Nokia Technologies Oy
Original Assignee
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Nokia Technologies Oy
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 Nokia Shanghai Bell Co Ltd, Nokia Solutions and Networks Oy, Nokia Technologies Oy filed Critical Nokia Shanghai Bell Co Ltd
Priority to PCT/CN2022/129346 priority Critical patent/WO2024092574A1/fr
Priority to CN202280100190.7A priority patent/CN119895984A/zh
Publication of WO2024092574A1 publication Critical patent/WO2024092574A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • 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

  • Various example embodiments relate to the field of telecommunication and in particular, to methods, devices, apparatuses, and computer readable storage media for identification for small data transmission (SDT) .
  • SDT small data transmission
  • NR New Radio
  • NR New Radio
  • NR New Radio
  • NR New Radio
  • a transmission scheme called SDT has been proposed to facilitate data transmission.
  • SDT data interaction between a base station and a UE may be achieved, while the UE is in the RRC_INACTIVE state during the transmission.
  • RRC_INACTIVE radio resource control INACTIVE
  • RRC_CONNECTED Radio resource control INACTIVE
  • SDT data interaction between a base station and a UE may be achieved, while the UE is in the RRC_INACTIVE state during the transmission.
  • example embodiments of the present disclosure provide a solution related to identification for SDT.
  • a terminal device comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to: receive, from a network device, a message comprising at least a first identifier of the terminal device for a non-small data transmission (non-SDT) procedure and a second identifier of the terminal device for an SDT procedure; and transmit, to the network device, a request message comprising the first identifier or the second identifier.
  • non-SDT non-small data transmission
  • a network device comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the network device at least to: transmit, to a terminal device, a message comprising at least a first identifier of the terminal device for a non-small data transmission (non-SDT) procedure and a second identifier of the terminal device for an SDT procedure; and receive, from the terminal device, a request message comprising the first identifier or the second identifier.
  • non-SDT non-small data transmission
  • a method implemented at a terminal device comprises receiving, from a network device, a message comprising at least a first identifier of the terminal device for a non-small data transmission (non-SDT) procedure and a second identifier of the terminal device for an SDT procedure; and transmitting, to the network device, a request message comprising the first identifier or the second identifier.
  • non-SDT non-small data transmission
  • a method implemented at a network device comprises transmitting, to a terminal device, a message comprising at least a first identifier of the terminal device for a non-small data transmission (non-SDT) procedure and a second identifier of the terminal device for an SDT procedure; and receiving, from the terminal device, a request message comprising the first identifier or the second identifier.
  • non-SDT non-small data transmission
  • an apparatus comprising means for receiving, at a terminal device from a network device, a message comprising at least a first identifier of the terminal device for a non-small data transmission (non-SDT) procedure and a second identifier of the terminal device for an SDT procedure; and means for transmitting, to the network device, a request message comprising the first identifier or the second identifier.
  • non-SDT non-small data transmission
  • an apparatus comprises means for transmitting, at a network device to a terminal device, a message comprising at least a first identifier of the terminal device for a non-small data transmission (non-SDT) procedure and a second identifier of the terminal device for an SDT procedure; and means for receiving, from the terminal device, a request message comprising the first identifier or the second identifier.
  • non-SDT non-small data transmission
  • a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method according to any one of the above third to fourth aspect.
  • a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to perform at least the method according to any one of the above third to fourth aspect.
  • a terminal device comprising receiving circuitry configured to receive, from a network device, a message comprising at least a first identifier of the terminal device for a non-small data transmission (non-SDT) procedure and a second identifier of the terminal device for an SDT procedure; and transmitting configured to transmitting, to the network device, a request message comprising the first identifier or the second identifier.
  • non-SDT non-small data transmission
  • a network device comprising transmitting circuitry configured to transmit, to a terminal device, a message comprising at least a first identifier of the terminal device for a non-small data transmission (non-SDT) procedure and a second identifier of the terminal device for an SDT procedure; and receiving circuitry configured to receive, from the terminal device, a request message comprising the first identifier or the second identifier.
  • non-SDT non-small data transmission
  • FIG. 1 illustrates an example environment in which example embodiments of the present disclosure can be implemented
  • FIG. 2 illustrates a signaling flow between the terminal device and the network device according to some example embodiments of the present disclosure
  • FIG. 3 illustrates an example communication process between the terminal device and the network device according to some example embodiments of the present disclosure
  • FIG. 4 illustrates a flowchart of a method implemented at a terminal device according to some embodiments of the present disclosure
  • FIG. 5 illustrates a flowchart of a method implemented at a network device according to some embodiments of the present disclosure
  • FIG. 6 illustrates a simplified block diagram of a device that is suitable for implementing some example embodiments of the present disclosure.
  • FIG. 7 illustrates a block diagram of an example of a computer readable medium in accordance with some example embodiments of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the listed terms.
  • circuitry may refer to one or more or all of the following:
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
  • the term “communication network” refers to a network following any suitable communication standards, such as Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • NB-IoT Narrow Band Internet of Things
  • the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the third generation (3G) , the fourth generation (4G) , 4.5G, the future fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of
  • the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom.
  • the network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a New Radio (NR) NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology.
  • BS base station
  • AP access point
  • NodeB or NB node B
  • eNodeB or eNB evolved NodeB
  • NR New Radio
  • RRU Remote Radio Unit
  • RH radio header
  • RRH remote radio head
  • terminal device refers to any end device that may be capable of wireless communication.
  • a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) .
  • UE user equipment
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and/
  • the UE may indicate the initiation of the SDT procedure by dedicated RACH resources that NW may have configured. If such RACH resources do not exist (that is, SDT also uses common RACH resources that are not reserved or configured for the SDT) , the network device may only deduce the need for SDT from a buffer state report (BSR) which is indicated by the UE in message 3 (Msg3) of the random access procedure if there is enough space after including the common control channel (CCCH) service data unit (SDU) /RRCResumeRequest) or then after the successful contention resolution of the random access procedure.
  • BSR buffer state report
  • Msg3 message 3
  • the UE evaluates whether it may trigger an SDT procedure based on a data amount threshold and, if configured, reference signal received power (RSRP) of the communication link, as specified in the following third-generation partnership project (3GPP) technical specification (TS) 38.321 v17.2.0:
  • 3GPP third-generation partnership project
  • TS technical specification
  • a UE in RRC_INACTIVE is paged with an I-RNTI.
  • I-RNTI an I-RNTI.
  • LTE long term evolution
  • EDT MT early data transmission
  • any additional information included in the paging record will increase the overhead of the paging procedure within the whole UE RAN Notification Area (RNA) within each beam of the cell.
  • RNA RAN Notification Area
  • a terminal device receives, from a network device, a message comprising at least a first identifier of the terminal device for a non-small data transmission (non-SDT) procedure and a second identifier of the terminal device for an SDT procedure. Moreover, the terminal device transmits, to the network device, a request message comprising the first identifier or the second identifier.
  • non-SDT non-small data transmission
  • This scheme optimizes the identification for SDT by comprising different identifiers in the request message to the network device. In this way, it is possible to avoid additional signalling overhead, save power consumption and improve transmission efficiency.
  • FIG. 1 illustrates an example environment 100 in which example embodiments of the present disclosure can be implemented.
  • the environment 100 which may be a part of a communication network, comprises a terminal device 110 and a network device 120 communicating with each other or with other devices via each other.
  • the communication environment 100 may comprise any suitable number of devices and cells.
  • the terminal device 110 and the network device 120 can communicate data and control information with each other.
  • a link from the network device 120 to the terminal device 110 is referred to as a downlink (DL)
  • a link from the terminal device 110 to the network device 120 is referred to as an uplink (UL) .
  • the environment 100 may comprise a further device to communicate with the terminal device 110 and network device 120.
  • the communications in the environment 100 may follow any suitable communication standards or protocols, which are already in existence or to be developed in the future, such as Universal Mobile Telecommunications System (UMTS) , long term evolution (LTE) , LTE-Advanced (LTE-A) , the fifth generation (5G) New Radio (NR) , Wireless Fidelity (Wi-Fi) and Worldwide Interoperability for Microwave Access (WiMAX) standards, and employs any suitable communication technologies, including, for example, Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Division Multiplexing (OFDM) , time division multiplexing (TDM) , frequency division multiplexing (FDM) , code division multiplexing (CDM) , Bluetooth, ZigBee, and machine type communication (MTC) , enhanced mobile broadband (eMBB) , massive machine type communication (mMTC) , ultra-reliable low latency communication (URLLC) , Carrier Aggregation (CA) , Dual Connectivity (DC) ,
  • FIG. 2 illustrates a signaling flow 200 between the terminal device and the network device according to some example embodiments of the present disclosure.
  • the signaling flow 200 will be described with reference to FIG. 1.
  • the network device 120 transmits (205) , to the terminal device 110, a message comprising at least a first identifier of the terminal device 110 for a non-SDT procedure and a second identifier of the terminal device for an SDT procedure.
  • the terminal device 110 receives (210) from the network device 120 the message.
  • the message may be a release message, such as an RRC release message to indicate the terminal device 110 to enter the RRC_INACTIVE state or RRC_IDLE state.
  • the non-SDT procedure may be a non-SDT resume procedure, also referred to as a regular resume procedure
  • the SDT procedure may be an SDT resume procedure.
  • a non-SDT resume procedure may comprise a regular RRC resume procedure where UE is moved from RRC_INACTIVE state to RRC_CONNECTED state.
  • the message may be a reconfiguration message, such as an RRC reconfiguration message.
  • the first and second identifiers may be inactive radio network temporary identifiers (I-RNTIs) .
  • I-RNTIs radio network temporary identifiers
  • the first and second identifiers may be full I-RNTIs.
  • the first and second identifiers may be short I-RNTIs.
  • the first and second identifiers may be S-Temporary Mobile Subscriber Identity (S-TMSI) .
  • S-TMSI S-Temporary Mobile Subscriber Identity
  • the terminal device 110 transmits (215) , to the network device 120, a request message comprising the first identifier or the second identifier. Accordingly, the network device receives (220) from the terminal device 110 the request message.
  • the request message may be a resume request message.
  • the resume request message may be used to initiate an MT-SDT resume procedure, an MO-SDT resume procedure or a regular resume procedure.
  • the request message may be a setup request message.
  • the network device 120 may transmit to the terminal device 110 a paging message.
  • the paging message may comprise the first or the second identifier.
  • the terminal device 110 may, as a response to the paging message, transmit to the network device 120 the request message comprising the first identifier. In this case, prior to transmitting the request message comprising the first identifier, the terminal device 110 may initiate the non-SDT resume procedure.
  • the terminal device 110 may initiate the non-SDT resume procedure.
  • at least one RACH resource that is not configured for SDT also referred to as a common RACH resource
  • the terminal device 110 may, as a response to the paging message, transmit to the network device 120 the request message comprising the second identifier.
  • the terminal device 110 may initiate the SDT resume procedure.
  • the terminal device 110 may resume the data radio bearers (DRBs) /signaling radio bearers (SRBs) configured for SDT.
  • DRBs data radio bearers
  • SRBs signalaling radio bearers
  • at least one RACH resource that is not configured for SDT may be used for the initiation of the SDT procedure, so that the MO-SDT in the cell does not need to be a prerequisite for enabling the MT-SDT.
  • the network device 120 may determine that the SDT resume procedure is initiated on at least one RACH resource that is not configured for SDT based on the second identifier in the request message.
  • the terminal device 110 may or may not have any uplink SDT data to be transmitted, it would not be necessary to use at least one RACH resource configured for SDT (if configured) in case the terminal device 110 does not have any uplink SDT data to transmit, since the network would likely allocate a bigger amount of resources for Msg3 transmission to fit at least part of the uplink SDT data into it. It would seem beneficial to allow the terminal device 110 to use normal RACH resources that are not configured for SDT to initiate the SDT procedure with MT-SDT access, so that the network device 120 may use Msg3 resources in case no uplink SDT data is available.
  • the second identifier may be an MT-SDT specific identifier (for example, an I-RNTI) .
  • the network device 120 may indicate the terminal device 110 to initiate MT-SDT using the MT-SDT specific identifier in the paging message or paging record.
  • the terminal device 110 may initiate the MT-SDT resume procedure if the MT-SDT specific identifier is received in the paging message, and initiate the regular non-SDT resume procedure if the regular identifier is received.
  • this does not expose any additional overhead to be introduced to the paging message for the MT-SDT purpose, thus the legacy paging message may be reused.
  • the initiation of the SDT/non-SDT procedure may be further based on other condition checking at the terminal device side.
  • the condition checking may comprise RSRP checking, UL data checking, and the like.
  • RSRP checking may be used to ensure successful transmission of the downlink data in case the terminal device 110 is in worse channel conditions than an RSRP threshold allows, for example, by using the non-SDT procedure in such a case.
  • the terminal device 110 may further determine whether there is any uplink data in a buffer and/or whether the RSRP of communication link is above an RSRP threshold.
  • the RSRP threshold may be configured by the network device 120 or be pre-defined.
  • the RSRP threshold may be different for MT-SDT than for MO-SDT.
  • network device 120 may configure different RSRP thresholds for MT-SDT than for MO-SDT.
  • the terminal device 110 after receiving the paging message comprising the second identifier, if the terminal device 110 determines that there is no uplink SDT data in a buffer or the RSRP of communication link is below the RSRP threshold, it may initiate the non-SDT procedure on at least one RACH resource that is not configured for SDT. As another example, if the terminal device 110 determines that there is uplink non-SDT data in a buffer, it may also initiate the non-SDT procedure on at least one RACH resource that is not configured for SDT.
  • the request message transmitted to the network device 120 may comprise the first identifier to indicate that a non-SDT procedure is required.
  • the network device 120 may determine that RSRP of communication link at the terminal device 110 is below an RSRP threshold or there is uplink non-SDT data at the terminal device 110 to be transmitted. Then, the network device 120 may configure the terminal device 110 to enter a connected state. For example, the network device 120 may transmit a resume message to the terminal device 110.
  • the terminal device may further set a cause in the request message to indicate the cause of initiating the non-SDT procedure.
  • the terminal device 110 After receiving the paging message comprising the second identifier, if the terminal device 110 determines that there is no uplink data in a buffer and the RSRP of communication link is below an RSRP threshold, it may set the cause in the request message to a first cause value (for example, mt-Access resumeCause) indicating that the non-SDT procedure is for MT access or MT data. For example, the terminal device 110 may resume SDT bearers before transmitting the request message comprising the first identifier with the first cause value. As an example, in this case, the network device 120 may transmit, to the terminal device 110, SDT data without configuring the terminal device 110 to enter a connected state. In other words, in this case, the network device 120 may attempt to transmit the DL SDT data without bringing the terminal device 110 to the RRC_CONNECTED state even though it knows the measured RSRP at the terminal device 110 is below the RSRP threshold.
  • a first cause value for example, mt-Access resumeCause
  • the terminal device 110 may set the cause in the request message to a second cause value (for example, mo-data resumeCause) indicating that the non-SDT procedure is for MO access or MO data. Accordingly, based on the request message with the second cause value, the network device 120 may determine that there is uplink non-SDT data at the terminal device 110 to be transmitted.
  • a second cause value for example, mo-data resumeCause
  • the terminal device 110 may initiate the SDT procedure on the at least one RACH resource that is not configured for SDT, and then transmit the request message comprising the second identifier to the network device 120.
  • the terminal device 120 may initiate the SDT procedure further based on the RSRP of communication link.
  • the terminal device 110 may initiate the SDT procedure, if it determines that the RSRP of communication link is above an RSRP threshold.
  • the terminal device 110 may initiate the SDT procedure, if it determines that there is no uplink SDT data in a buffer and the RSRP of communication link is below an RSRP threshold.
  • the network device 120 may determine that there is no uplink SDT data at the terminal device 110 to be transmitted and then transmit, to the terminal device 110, SDT data without configuring the terminal device 110 to a connected state.
  • the terminal device 110 may initiate the SDT procedure on at least one RACH resource configured for SDT, and then transmit the request message comprising the second identifier to the network device 120.
  • the terminal device 120 may initiate the SDT procedure further based on the RSRP of communication link.
  • the terminal device 110 may initiate the SDT procedure, if it determines that there is uplink SDT data in a buffer and the RSRP of communication link is above an RSRP threshold.
  • the terminal device 110 may initiate the SDT procedure, if it determines that there is uplink SDT data in a buffer and the RSRP of communication link is below an RSRP threshold.
  • the network device 120 may determine that there is uplink SDT data at the terminal device 110 to be transmitted and the terminal device 110 has received the paging message comprising the second identifier.
  • the terminal device 120 may initiate the SDT procedure on at least one RACH resource configured for SDT, and then transmit, to the network device 120, the request message comprising the first identifier. In this case, for example, if the network device 120 has transmitted to the terminal device 110 the paging message comprising the second identifier, it may determine that the terminal device 120 has not received the paging message.
  • the terminal device 110 may initiate the non-SDT procedure on at least one RACH resource that is not configured for SDT, and then transmit, to the network device 120, the request message comprising the first identifier.
  • the request message comprising the first identifier.
  • the second specific identifier may not be used although it is allocated.
  • there may be UL-SDT data in the buffer there may be UL-SDT data in the buffer.
  • the second identifier may not be used although it is allocated, because the network device 120 has paged the terminal device 110 to use the non-SDT procedure.
  • the network device 120 may determine that the non-SDT procedure is initiated on at least one RACH resource that is not configured for SDT. The following non-SDT procedure may be continued.
  • the above identifiers can apply to MO-SDT cases.
  • the second identifier may be used by the terminal device 110 for MO-SDT over at least one RACH resource that is not configured for SDT.
  • the network device 120 may indicate MO-SDT configuration in the cell but may not provide any SDT specific RACH resources. Then, if a condition to initiate MO-SDT is fulfilled (e.g. the RSRP threshold is met as explained in the next paragraph) , the terminal device 110 may initiate an SDT procedure on at least one RACH resource that is not configured for SDT and use the second identifier in the request message to indicate that the initiation is for MO-SDT.
  • the terminal device may initiate the SDT procedure on at least one RACH resource that is not configured for SDT, and then transmit, to the network device 120, the request message comprising the second identifier.
  • the SDT procedure is a MO-SDT procedure.
  • the network device 120 may determine that the SDT procedure is initiated on at least one RACH resource that is not configured for SDT, and then determine that the SDT procedure is a MO-SDT procedure based on the second identifier.
  • the simple and efficient mechanism can be used to provide paging for SDT and identification for initiating an SDT procedure or a regular non-SDT procedure based on the different identifiers.
  • No additional overhead is exposed to any downlink or uplink RRC messages to initiate the SDT procedure (for example, the MT-SDT specific resume procedure) compared to regular RRC procedure (for example, regular RRC resume procedure) .
  • some cause values for example, current resumeCause values
  • FIG. 3 illustrates an example communication process 300 between the terminal device and the network device according to some example embodiments of the present disclosure.
  • the process 300 will be described with reference to FIG. 1. It would be appreciated that although the process 300 has been described in the network environment 100 of FIG. 1, this process flow may be likewise applied to other communication scenarios.
  • the terminal device 110 is implemented by a UE 301
  • the network device 120 is implemented by a gNB 303.
  • the gNB 303 transmits to the UE 301 an RRCRelease message with multiple identifiers including at least a first identifier and a second identifier.
  • the identifiers are I-RNTIs.
  • the first identifier is also referred as a regular I-RNTI
  • the second identifier is also referred to as MT-SDT specific I-RNTI.
  • the UE 301 goes to an RRC_INACTIVE state and stores the above I-RNTIs.
  • downlink SDT data becomes available.
  • the gNB 303 transmits to the UE 301 a paging message with MT-SDT specific I-RNTI.
  • the UE 301 initiates a random access (RA) procedure over common RACH resources that are not configured for SDT.
  • RA random access
  • the UE 301 transmits to the gNB 303 an RRCResumeRequest message with MT-SDT specific I-RNTI.
  • SDT data in downlink is transmitted and subsequent uplink SDT data may be transmitted (if any) .
  • the gNB 303 may transmit an RRCRelease message with multiple I-RNTIs comprising regular and MT-SDT specific I-RNTIs.
  • FIG. 4 illustrates a flowchart 400 of a method implemented at a terminal device 110 according to some embodiments of the present disclosure. For the purpose of discussion, the method 400 will be described from the perspective of the terminal device 110 with reference to FIG. 1.
  • the terminal device 110 receives, from the network device 120, a message comprising at least a first identifier of the terminal device 110 for a non-small data transmission (non-SDT) procedure and a second identifier of the terminal device 110 for an SDT procedure.
  • the terminal device 110 transmits, to the network device 120, a request message comprising the first identifier or the second identifier.
  • the terminal device 110 transmits the request message by: based on receiving, from the network device 120, a paging message comprising the second identifier, transmitting, to the network device 120, the request message comprising the second identifier. In some example embodiments, the terminal device 110 further, prior to transmitting the request message comprising the second identifier, initiates the SDT procedure on at least one random access channel, RACH, resource that is not configured for SDT. In some example embodiments, the terminal device 110 initiates the SDT procedure by: based on determining that there is no uplink SDT data in a buffer, initiating the SDT procedure on the at least one RACH resource that is not configured for SDT.
  • the terminal device 110 further, prior to transmitting the request message comprising the second identifier, based on determining that there is uplink SDT data in a buffer, initiates the SDT procedure on at least one RACH resource configured for SDT.
  • the terminal device 110 initiates the SDT procedure by: further based on reference signal received power (RSRP) of communication link is above an RSRP threshold, initiating the SDT procedure.
  • the terminal device 110 initiates the SDT procedure by: further based on RSRP of communication link is below an RSRP threshold, initiating the SDT procedure.
  • RSRP reference signal received power
  • the terminal device 110 further receives, from the network device 120, a paging message comprising the second identifier; and prior to transmitting the request message, based on determining that there is no uplink SDT data in a buffer and RSRP of communication link is below an RSRP threshold or there is uplink non-SDT data in a buffer, initiates the non-SDT procedure on at least one RACH resource that is not configured for SDT.
  • the terminal device 110 transmits the request message by: transmitting, to the network device 120, the request message comprising the first identifier.
  • the terminal device 110 further, based on determining that there is no uplink data in a buffer and RSRP of communication link is below an RSRP threshold, sets a cause in the request message to a first cause value indicating that the non-SDT procedure is for mobile terminated (MT) access. In some example embodiments, the terminal device 110 further, based on determining that there is uplink non-SDT data in a buffer, sets a cause in the request message to a second cause value indicating that the non-SDT procedure is for mobile originated (MO) access or MO data.
  • terminal device 110 further receives, from the network device 120, a paging message comprising the first identifier; and initiates the non-SDT procedure on at least one RACH resource that is not configured for SDT, and the terminal device 110 transmits the request message by: transmitting, to the network device 120, the request message comprising the first identifier.
  • the terminal device 110 further, prior to transmitting the request message, based on determining that there is uplink SDT data in a buffer and RSRP of communication link is above an RSRP threshold, initiates the SDT procedure on at least one RACH resource that is not configured for SDT, the SDT procedure being a mobile originated (MO) -SDT procedure, and the terminal device 110 transmits the request message by: transmitting, to the network device 120, the request message comprising the second identifier.
  • RSRP mobile originated
  • the RSRP threshold is different for MT-SDT than for MO-SDT.
  • the first and second identifiers are full inactive radio network temporary identifiers (I-RNTIs) or short I-RNTIs for an SDT procedure.
  • I-RNTIs full inactive radio network temporary identifiers
  • short I-RNTIs for an SDT procedure.
  • the message is a release message or a reconfiguration message.
  • FIG. 5 illustrates a flowchart 500 of a method implemented at a network device 120 according to some embodiments of the present disclosure. For the purpose of discussion, the method 500 will be described from the perspective of the network device 120 with reference to FIG. 1.
  • the network device 120 transmits, to a terminal device 110, a message comprising at least a first identifier of the terminal device 110 for a non-small data transmission (non-SDT) procedure and a second identifier of the terminal device 110 for an SDT procedure.
  • the network device 120 receives, from the terminal device 110, a request message comprising the first identifier or the second identifier.
  • the network device 120 further, prior to receiving the request message, transmits, to the terminal device 110, a paging message comprising the second identifier.
  • the network device 120 further, after transmitting the paging message comprising the second identifier, determines that the SDT procedure is initiated on at least one random access channel, RACH, resource that is not configured for SDT.
  • RACH random access channel
  • the network device 120 further, after transmitting the paging message comprising the second identifier, based on determining that the non-SDT procedure is initiated on at least one RACH resource that is not configured for SDT and the received request message comprises the first identifier, determines that reference signal received power (RSRP) of communication link at the terminal device 110 is below an RSRP threshold or there is uplink non-SDT data at the terminal device 110 to be transmitted; and configures the terminal device 110 to enter a connected state.
  • RSRP reference signal received power
  • the network device 120 determines that there is uplink non-SDT data at the terminal device 110 to be transmitted by: based on determining that a cause in the request message is set to a second cause value indicating that the non-SDT procedure is for mobile originated (MO) access, determining that there is uplink non-SDT data at the terminal device 110 to be transmitted.
  • the RSRP threshold is different for MT-SDT than for MO-SDT.
  • the network device 120 further, after transmitting the paging message comprising the second identifier, determines that the non-SDT procedure is initiated on at least one RACH resource that is not configured for SDT and the received request message comprises the first identifier; determines that a cause in the request message is set to a first cause value indicating the non-SDT procedure is for mobile terminated (MT) access; and transmits, to the terminal device 110, SDT data without configuring the terminal device 110 to enter a connected state.
  • MT mobile terminated
  • the network device 120 further, after transmitting the paging message comprising the second identifier, based on determining that the SDT procedure is initiated on at least one RACH resource that is not configured for SDT and the received request message comprises the second identifier, determines that there is no uplink SDT data at the terminal device 110 to be transmitted; and transmit, to the terminal device 110, SDT data without configuring the terminal device 110 to a connected state.
  • the network device 120 further, after transmitting the paging message comprising the second identifier, based on determining that the SDT procedure is initiated on at least one RACH resource configured for SDT and the received request message comprises the second identifier, determines that there is uplink SDT data at the terminal device 110 to be transmitted and the terminal device 110 has received the paging message comprising the second identifier.
  • the network device 120 further, prior to receiving the request message, transmits, to the terminal device 110, a paging message comprising the first identifier, and after transmitting the paging message comprising the first identifier, determines that the non-SDT procedure is initiated on at least one RACH resource that is not configured for SDT.
  • the network device 120 further, prior to receiving the request message comprising the second identifier, determines that the SDT procedure is initiated on at least one RACH resource that is not configured for SDT, the SDT procedure being a mobile originated (MO) -SDT procedure.
  • the first and second identifiers are full inactive radio network temporary identifiers (I-RNTIs) or short I-RNTIs for an SDT procedure.
  • I-RNTIs full inactive radio network temporary identifiers
  • short I-RNTIs for an SDT procedure.
  • the message is a release message or a reconfiguration message.
  • an apparatus capable of performing the method 400 may comprise means for performing the respective steps of the method 400.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises means for receiving, from a network device, a message comprising at least a first identifier of the terminal device for a non-small data transmission (non-SDT) procedure and a second identifier of the terminal device for an SDT procedure; and means for transmitting, to the network device, a request message comprising the first identifier or the second identifier.
  • non-SDT non-small data transmission
  • the means for transmitting the request message comprises: means for, based on receiving, from the network device, a paging message comprising the second identifier, transmitting, to the network device, the request message comprising the second identifier.
  • the apparatus further comprises means for, prior to transmitting the request message comprising the second identifier, initiating the SDT procedure on at least one random access channel, RACH, resource that is not configured for SDT.
  • the means for initiating the SDT procedure comprises means for, based on determining that there is no uplink SDT data in a buffer, initiating the SDT procedure on the at least one RACH resource that is not configured for SDT.
  • the apparatus further comprises means for, prior to transmitting the request message comprising the second identifier, based on determining that there is uplink SDT data in a buffer, initiating the SDT procedure on at least one RACH resource configured for SDT.
  • the means for initiating the SDT procedure comprises: means for further based on reference signal received power (RSRP) of communication link is above an RSRP threshold, initiating the SDT procedure.
  • the means for initiating the SDT procedure comprises: means for further based on RSRP of communication link is below an RSRP threshold, initiating the SDT procedure.
  • RSRP reference signal received power
  • the apparatus further comprises means for receiving, from the network device, a paging message comprising the second identifier; and means for, prior to transmitting the request message, based on determining that there is no uplink SDT data in a buffer and RSRP of communication link is below an RSRP threshold or there is uplink non-SDT data in a buffer, initiating the non-SDT procedure on at least one RACH resource that is not configured for SDT.
  • the means for transmitting the request message comprises means for transmitting, to the network device, the request message comprising the first identifier.
  • the apparatus further comprises means for, based on determining that there is no uplink data in a buffer and RSRP of communication link is below an RSRP threshold, set a cause in the request message to a first cause value indicating that the non-SDT procedure is for mobile terminated (MT) access.
  • the apparatus further comprises means for, based on determining that there is uplink non-SDT data in a buffer, setting a cause in the request message to a second cause value indicating that the non-SDT procedure is for mobile originated (MO) access.
  • the apparatus further comprises means for receiving, from the network device, a paging message comprising the first identifier; and means for initiating the non-SDT procedure on at least one RACH resource that is not configured for SDT, and the means for transmitting the request message comprises means for transmitting, to the network device, the request message comprising the first identifier.
  • the apparatus further comprises means for, prior to transmitting the request message, based on determining that there is uplink SDT data in a buffer and RSRP of communication link is above an RSRP threshold, initiating the SDT procedure on at least one RACH resource that is not configured for SDT, the SDT procedure being a mobile originated (MO) -SDT procedure, and the means for transmitting the request message comprises means for transmitting, to the network device, the request message comprising the second identifier.
  • MO mobile originated
  • the RSRP threshold is different for MT-SDT than for MO-SDT.
  • the first and second identifiers are full inactive radio network temporary identifiers (I-RNTIs) or short I-RNTIs for an SDT procedure.
  • I-RNTIs full inactive radio network temporary identifiers
  • short I-RNTIs for an SDT procedure.
  • the message is a release message or a reconfiguration message.
  • the apparatus further comprises means for performing other steps in some embodiments of the method 400.
  • the means comprises at least one processor and at least one memory including computer program code. The at least one memory and computer program code are configured to, with the at least one processor, cause the performance of the apparatus.
  • an apparatus capable of performing the method 500 may comprise means for performing the respective steps of the method 500.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises means for transmitting, to a terminal device, a message comprising at least a first identifier of the terminal device for a non-small data transmission (non-SDT) procedure and a second identifier of the terminal device for an SDT procedure; and means for receiving, from the terminal device, a request message comprising the first identifier or the second identifier.
  • non-SDT non-small data transmission
  • the apparatus further comprises means for, prior to receiving the request message, transmitting, to the terminal device, a paging message comprising the second identifier.
  • the apparatus further comprises means for, after transmitting the paging message comprising the second identifier, determine that the SDT procedure is initiated on at least one random access channel, RACH, resource that is not configured for SDT.
  • the apparatus further comprises means for, after transmitting the paging message comprising the second identifier, based on determining that the non-SDT procedure is initiated on at least one RACH resource that is not configured for SDT and the received request message comprises the first identifier, determine that reference signal received power (RSRP) of communication link at the terminal device is below an RSRP threshold or there is uplink non-SDT data at the terminal device to be transmitted; and means for configuring the terminal device to enter a connected state.
  • RSRP reference signal received power
  • the means for determining that there is uplink non-SDT data at the terminal device to be transmitted comprises means for, based on determining that a cause in the request message is set to a second cause value indicating that the non-SDT procedure is for mobile originated (MO) access, determining that there is uplink non-SDT data at the terminal device to be transmitted.
  • the RSRP threshold is different for MT-SDT than for MO-SDT.
  • the apparatus further comprises means for, after transmitting the paging message comprising the second identifier, determine that the non-SDT procedure is initiated on at least one RACH resource that is not configured for SDT and the received request message comprises the first identifier; means for determining that a cause in the request message is set to a first cause value indicating the non-SDT procedure is for mobile terminated (MT) access; and means for transmitting, to the terminal device, SDT data without configuring the terminal device to enter a connected state.
  • MT mobile terminated
  • the apparatus further comprises means for, after transmitting the paging message comprising the second identifier, based on determining that the SDT procedure is initiated on at least one RACH resource that is not configured for SDT and the received request message comprises the second identifier, determining that there is no uplink SDT data at the terminal device to be transmitted; and means for transmitting, to the terminal device, SDT data without configuring the terminal device to a connected state.
  • the apparatus further comprises means for, after transmitting the paging message comprising the second identifier, based on determining that the SDT procedure is initiated on at least one RACH resource configured for SDT and the received request message comprises the second identifier, determining that there is uplink SDT data at the terminal device to be transmitted and the terminal device has received the paging message comprising the second identifier.
  • the apparatus further comprises means for, prior to receiving the request message, transmitting, to the terminal device, a paging message comprising the first identifier, and means for, after transmitting the paging message comprising the first identifier, determining that the non-SDT procedure is initiated on at least one RACH resource that is not configured for SDT.
  • the apparatus further comprises means for, prior to receiving the request message comprising the second identifier, determining that the SDT procedure is initiated on at least one RACH resource that is not configured for SDT, the SDT procedure being a mobile originated (MO) -SDT procedure.
  • the first and second identifiers are full inactive radio network temporary identifiers (I-RNTIs) or short I-RNTIs for an SDT procedure.
  • I-RNTIs full inactive radio network temporary identifiers
  • short I-RNTIs for an SDT procedure.
  • the message is a release message or a reconfiguration message.
  • the apparatus further comprises means for performing other steps in some embodiments of the method 500.
  • the means comprises at least one processor and at least one memory including computer program code. The at least one memory and computer program code are configured to, with the at least one processor, cause the performance of the apparatus.
  • FIG. 6 illustrates a simplified block diagram of a device 600 that is suitable for implementing some example embodiments of the present disclosure.
  • the device 600 may be provided to implement the communication device, for example, the terminal device 110, or the network device 120 as shown in FIG. 1.
  • the device 600 includes one or more processors 610, one or more memories 620 coupled to the processor 610, and one or more communication modules 640 coupled to the processor 610.
  • the communication module 640 is for bidirectional communications.
  • the communication module 640 has at least one antenna to facilitate communication.
  • the communication interface may represent any interface that is necessary for communication with other network elements.
  • the processor 610 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 600 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • the memory 620 may include one or more non-volatile memories and one or more volatile memories.
  • the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 624, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , and other magnetic storage and/or optical storage.
  • the volatile memories include, but are not limited to, a random access memory (RAM) 622 and other volatile memories that will not last in the power-down duration.
  • a computer program 630 includes computer executable instructions that are executed by the associated processor 610.
  • the program 630 may be stored in the ROM 624.
  • the processor 610 may perform any suitable actions and processing by loading the program 630 into the RAM 622.
  • the embodiments of the present disclosure may be implemented by means of the program 630 so that the device 600 may perform any process of the disclosure as discussed with reference to FIGS. 2 to 5.
  • the embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
  • the program 630 may be tangibly contained in a computer readable medium which may be included in the device 600 (such as in the memory 620) or other storage devices that are accessible by the device 600.
  • the device 600 may load the program 630 from the computer readable medium to the RAM 622 for execution.
  • the computer readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.
  • FIG. 7 illustrates a block diagram of an example of a computer readable medium 700 in accordance with some example embodiments of the present disclosure.
  • the computer readable medium 700 has the program 630 stored thereon. It is noted that although the computer readable medium 700 is depicted in form of CD or DVD in FIG. 7, the computer readable medium 700 may be in any other form suitable for carry or hold the program 630.
  • various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the method as described above with reference to any of FIGS. 4-5.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above.
  • Examples of the carrier include a signal, computer readable medium, and the like.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • non-transitory is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .

Landscapes

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

Abstract

Des modes de réalisation de la présente divulgation concernent l'identification pour la transmission de petites quantités de données (SDT). Un dispositif terminal reçoit, en provenance d'un dispositif de réseau, un message comprenant au moins un premier identifiant du dispositif terminal pour une procédure autre que de transmission de petites quantités de données (non-SDT) et un second identifiant du dispositif terminal pour une procédure SDT. De plus, le dispositif terminal transmet, au dispositif de réseau, un message de demande comprenant le premier identifiant ou le second identifiant. Par conséquent, il est possible d'éviter un surdébit de signalisation supplémentaire, d'économiser la consommation d'énergie et d'améliorer l'efficacité de transmission.
PCT/CN2022/129346 2022-11-02 2022-11-02 Identification pour transmission de petites quantités de données Ceased WO2024092574A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2022/129346 WO2024092574A1 (fr) 2022-11-02 2022-11-02 Identification pour transmission de petites quantités de données
CN202280100190.7A CN119895984A (zh) 2022-11-02 2022-11-02 用于小数据传输的标识

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/129346 WO2024092574A1 (fr) 2022-11-02 2022-11-02 Identification pour transmission de petites quantités de données

Publications (1)

Publication Number Publication Date
WO2024092574A1 true WO2024092574A1 (fr) 2024-05-10

Family

ID=84358064

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/129346 Ceased WO2024092574A1 (fr) 2022-11-02 2022-11-02 Identification pour transmission de petites quantités de données

Country Status (2)

Country Link
CN (1) CN119895984A (fr)
WO (1) WO2024092574A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220022266A1 (en) * 2020-07-17 2022-01-20 Samsung Electronics Co., Ltd. Method and apparatus for random access procedure for small data transmission in wireless communication system
WO2022075782A1 (fr) * 2020-10-07 2022-04-14 Samsung Electronics Co., Ltd. Procédé de traitement de support radioélectrique de transmission non sdt (transmission de petites données) pendant une transmission sdt et appareil associé
WO2022151239A1 (fr) * 2021-01-14 2022-07-21 Lenovo (Beijing) Limited Procédé et appareil de traitement de transmission de 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)

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220022266A1 (en) * 2020-07-17 2022-01-20 Samsung Electronics Co., Ltd. Method and apparatus for random access procedure for small data transmission in wireless communication system
WO2022075782A1 (fr) * 2020-10-07 2022-04-14 Samsung Electronics Co., Ltd. Procédé de traitement de support radioélectrique de transmission non sdt (transmission de petites données) pendant une transmission sdt et appareil associé
WO2022151239A1 (fr) * 2021-01-14 2022-07-21 Lenovo (Beijing) Limited Procédé et appareil de traitement de transmission de 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)

Also Published As

Publication number Publication date
CN119895984A (zh) 2025-04-25

Similar Documents

Publication Publication Date Title
KR102501134B1 (ko) 무선 통신들에서의 유연한 다운링크 제어 신호 모니터링
WO2022056693A1 (fr) Procédé, dispositif et support de stockage informatique de communication
US12363730B2 (en) Scheduling request and random access triggering for sdt
WO2024092574A1 (fr) Identification pour transmission de petites quantités de données
US20250016545A1 (en) Restrictions for rna update procedure during sdt procedure
US20240267975A1 (en) Small data transmission
WO2024152181A1 (fr) Transmission de petites données
US12484105B2 (en) Devices, methods and apparatuses for data transmission
WO2024152356A1 (fr) Procédés et appareils de transmission de petites données
WO2024092665A1 (fr) Commande de transmission de petites données
US12507251B2 (en) Scheduling request and random access triggering for SDTN
US12494888B2 (en) Cell activation triggered layer 3 reporting
US12289624B2 (en) Restrictions for RNA update procedure during SDT procedure
US12507306B2 (en) Method, device and computer storage medium of communication
WO2023155117A1 (fr) Sélection de ressources d'accès pour une transmission de petites données
WO2024207349A1 (fr) Transmission de petites données à terminaison mobile
WO2024152358A1 (fr) Sélection ou resélection de cellule initiée par réseau
US20250097930A1 (en) Mechanism for configured grant transmission
WO2022198624A1 (fr) Régulation sélective de surcharge de rach
HK40114630A (en) Scheduling request and random access triggering for sdt
CN119946855A (zh) 探测参考信号资源释放
EP4406346A1 (fr) Mise à jour de paramètre en vue d'une tentative de reprise de connexion
CA3228363A1 (fr) Communication pour une transmission de petites donnees

Legal Events

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

Ref document number: 22802887

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202280100190.7

Country of ref document: CN

WWP Wipo information: published in national office

Ref document number: 202280100190.7

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 202547048661

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 202547048661

Country of ref document: IN

122 Ep: pct application non-entry in european phase

Ref document number: 22802887

Country of ref document: EP

Kind code of ref document: A1