[go: up one dir, main page]

WO2022104589A1 - Procédé et appareil pour la transmission de petites données - Google Patents

Procédé et appareil pour la transmission de petites données Download PDF

Info

Publication number
WO2022104589A1
WO2022104589A1 PCT/CN2020/129755 CN2020129755W WO2022104589A1 WO 2022104589 A1 WO2022104589 A1 WO 2022104589A1 CN 2020129755 W CN2020129755 W CN 2020129755W WO 2022104589 A1 WO2022104589 A1 WO 2022104589A1
Authority
WO
WIPO (PCT)
Prior art keywords
sdt
resource
lbt failure
bwp
consistent
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/CN2020/129755
Other languages
English (en)
Inventor
Ran YUE
Lianhai WU
Jie Shi
Haiming Wang
Yu Zhang
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.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing Ltd
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 Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to PCT/CN2020/129755 priority Critical patent/WO2022104589A1/fr
Publication of WO2022104589A1 publication Critical patent/WO2022104589A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • 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
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H04W74/0836—Random access procedures, e.g. with 4-step access with 2-step access
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • Embodiments of the present application generally relate to wireless communication technology, especially to a method and apparatus for small data transmission (SDT) , e.g., for 5G new radio on unlicensed spectrum (NR-U) uplink transmission.
  • SDT small data transmission
  • NR-U unlicensed spectrum
  • a base station (BS) and a user equipment (UE) may operate in both licensed and unlicensed spectrum.
  • Listen before talk (LBT) is a channel access technique used for transmission on an unlicensed spectrum.
  • LBT procedure is required to be performed before a transmitter (e.g., a BS or a UE) can start a transmission on an unlicensed spectrum.
  • LBT is executed based on performing energy detection on a certain channel. Only when a LBT procedure generates a success result, the transmitter can start the transmission on the channel and occupy the channel up to a certain channel occupancy time; otherwise, the transmitter cannot start the transmission and continue performing LBT until a LBT procedure generates a successful result.
  • Small data transmission may be performed when a UE is in radio resource control (RRC) _INACTIVE state or in idle state.
  • RRC radio resource control
  • Embodiments of the present application provide a method and apparatus for data transmission, e.g., for 5G new radio on NR-U uplink transmission.
  • An embodiment of the present application provides a method.
  • the method may include: receiving listen before talk (LBT) failure indications for small data transmission (SDT) ; triggering consistent LBT failure for a first uplink (UL) resource for SDT in response to a number of the LBT failure indications exceeding or being equal to a predetermined threshold within a predetermined time duration for the first UL resource for SDT; and performing a recovery procedure by switching the SDT from the first UL resource to a second UL resource in response to the consistent LBT failure for the first UL resource for SDT being triggered.
  • LBT listen before talk
  • UL uplink
  • performing the recovery procedure further comprises: initiating a random access channel (RACH) procedure if there is no UL resource available for the SDT or any UL transmission.
  • RACH random access channel
  • the method may further include: receiving configuration information for the consistent LBT failure for SDT by a system broadcast message or radio resource control (RRC) signaling, wherein the configuration information indicates at least one of the predetermined threshold corresponding to a maximum number of the LBT failure indications received and the predetermined time duration corresponding to time duration for monitoring LBT failure for SDT.
  • RRC radio resource control
  • the first UL resource is one of the following: a UL pre-configured resource for SDT; a physical uplink shared channel (PUSCH) resource and PRACH resource during a random access channel (RACH) procedure for SDT; and any other UL resource for SDT.
  • PUSCH physical uplink shared channel
  • RACH random access channel
  • the method may further include at least one of: detecting the consistent LBT failure per UL pre-configured resource for SDT by counting the LBT failure indications for all UL transmissions; detecting the consistent LBT failure per UL bandwidth part (BWP) for SDT by counting the LBT failure indications for all UL transmissions; and detecting the consistent LBT failure per physical random access channel (PRACH) index, per MsgA PUSCH configuration, or Msg3 PUSCH configuration by counting the LBT failure indications for all UL transmissions.
  • BWP bandwidth part
  • PRACH physical random access channel
  • each of the LBT failure indications comprises information indicating the LBT failure indication is for which UL pre-configured resource, which UL BWP, which PRACH index, which MsgA PUSCH configuration, or which Msg3 PUSCH configuration.
  • the consistent LBT failure is triggered for UL pre-configured resource for SDT, an UL BWP, PRACH index, MsgA PUSCH configuration, or Msg3 PUSCH configuration, when the counted number of the LBT failure indications exceeds or is equal to the predetermined threshold within the predetermined time duration for SDT.
  • switching the SDT from the first UL resource to the second UL resource comprises: in the case of a plurality of UL resources for SDT being configured or available and information about which UL BWP the UL resources for SDT belong to being not configured, selecting the second UL resource for switching is in an order of priority for switching: each UL pre-configured resource for SDT which has not been indicated LBT failure, each MsgA resource including PRACH resource and MsgA PUSCH resource during a 2-step RACH procedure for SDT which has not been indicated LBT failure, each PRACH resource during a RACH procedure for SDT which has not been indicated LBT failure, and each PRACH resource during a RACH procedure not for SDT which has not been indicated LBT failure.
  • switching the SDT from the first UL resource to the second UL resource comprises: in the case of a plurality of UL resources for SDT being configured or available and information about which UL BWP the UL resources for SDT belong to being configured, selecting the second UL resource for switching is in an order of priority for switching: each UL pre-configured resource for SDT on a same BWP as the first UL resource which has not been indicated LBT failure, each MsgA resource including PRACH resource and MsgA PUSCH resource during a 2-step RACH procedure for SDT on a same BWP as the first UL resource which has not been indicated LBT failure, each PRACH resource during a RACH procedure for SDT on a same BWP as the first UL resource which has not been indicated LBT failure, each UL pre-configured resource for SDT on another BWP which has not been indicated LBT failure, each MsgA resource including PRACH resource and MsgA PUSCH resource during a 2-step RACH procedure
  • the method may further include: in the case that only a first UL pre-configured resource on a first UL BWP is configured and activated for SDT and the consistent LBT failure for the first UL pre-configured resource for SDT is triggered, autonomously switching the SDT from the first UL pre-configured resource to a second UL pre-configured resource on a second UL BWP which has not been indicated LBT failure.
  • the method may further include: in the case that there is no the second UL pre-configured resource on the second UL BWP, autonomously switching the SDT from the first UL pre-configured resource to a third UL BWP with random access (RA) configuration which has not been indicated LBT failure.
  • RA random access
  • the method may further include: in the case that a plurality of UL pre-configured resources on a first UL BWP are configured for SDT and at least one UL pre-configured resource of the plurality of UL pre-configured resources is activated and the consistent LBT failure for each of the plurality of UL pre-configured resources for SDT on the first BWP is triggered, autonomously switching the SDT to a second UL pre-configured resource on a second UL BWP with or without RA configuration which has not been indicated LBT failure.
  • the method may further include: in the case that there is no the second UL pre-configured resource on the second UL BWP, autonomously switching the SDT to a third UL BWP with RA configuration which has not been indicated LBT failure.
  • the method may further include: initiating UL pre-configured resource based SDT or a RACH based SDT or a random access procedure.
  • the method may further include: indicating a consistent LBT failure for SDT to upper layers when there is no the second UL resource for switching.
  • the method may further include: canceling the triggered consistent LBT failure if a MAC PDU is transmitted and LBT failure indication is not received and this MAC PDU includes the LBT failure indication or this MAC PDU is transmitted on the second UL resource, or if consistent LBT failure is triggered and not cancelled and a random access procedure is considered successfully completed, or a preamble or a MAC PDU in a random access procedure is transmitted, or if configuration information for the consistent LBT failure for SDT is reconfigured by upper layers.
  • the method may include: transmitting configuration information for monitoring consistent listen before talk (LBT) failure for small data transmission (SDT) ; and receiving uplink transmission for SDT; wherein the configuration information comprises at least one of a maximum number of LBT failure indications for SDT that may be received by a user equipment (UE) and time duration for monitoring LBT failure for SDT.
  • LBT listen before talk
  • SDT small data transmission
  • UE user equipment
  • the configuration information is transmitted via a system broadcast message or radio resource control (RRC) signaling.
  • RRC radio resource control
  • the apparatus may include at least one non-transitory computer-readable medium having computer executable instructions stored therein; at least one receiver; at least one transmitter; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiver and the at least one transmitter.
  • the computer executable instructions are programmed to implement the above method with the at least one receiver, the at least one transmitter and the at least one processor.
  • Embodiments of the present application provide a mechanism for handling consistent LBT failure when SDT is performed which can detect consistent LBT failure and recovery from the consistent LBT failure in SDT case.
  • FIG. 1 illustrates a wireless communication system according to some embodiments of the present application
  • FIG. 2 illustrates a flow chart of a method for handling consistent LBT failure during small data transmission according to some embodiments of the present application
  • FIG. 3 illustrates an apparatus according to some embodiments of the present application.
  • FIG. 4 illustrates another apparatus according to some other embodiments of the present application.
  • FIG. 1 illustrates a wireless communication system according to some embodiments of the present application.
  • the wireless communication system can include at least one base station (BS) , at least one UE, and a core network (CN) node.
  • BS base station
  • UE UE
  • a core network (CN) node e.g., a BS (e.g., BS 102) and a UE (UE 101) are depicted in FIG. 1, one skilled in the art will recognize that any number of the BSs and UEs may be included in the wireless communication system.
  • the BS 102 may be distributed over a geographic region and may communicate with the CN node 103 via an interface.
  • the UE 101 may be a computing device, such as a desktop computer, a laptop computer, a personal digital assistant (PDA) , a tablet computer, a smart television (e.g., a television connected to the Internet) , a set-top box, a game console, a security system (including security cameras) , a vehicle on-board computer, a network device (e.g., router, switch, and modem) , or the like.
  • a computing device such as a desktop computer, a laptop computer, a personal digital assistant (PDA) , a tablet computer, a smart television (e.g., a television connected to the Internet) , a set-top box, a game console, a security system (including security cameras) , a vehicle on-board computer, a network device (e.g., router, switch, and modem) , or the like.
  • the UE 101 may be a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a device having a subscriber identity module, a personal computer, a selective call receiver, or any other device that is capable of sending and receiving communication signals on a wireless network.
  • the UE 201 may be a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, or the like.
  • the UE 101 may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or described using other terminology used in the art.
  • the BS 102 may communicate with a CN node 103 via an interface.
  • the BS 102 may also be referred to as an access point, an access terminal, a base, a base unit, a macro cell, a Node-B, an evolved Node B (eNB) , a gNB, a Home Node-B, a relay node, or a device, or described using other terminology used in the art.
  • the BS 102 is generally part of a radio access network that may include one or more controllers communicably coupled to one or more corresponding BS (s) .
  • the CN node 103 can be a mobility management entity (MME) or a serving gateway (S-GW) .
  • MME mobility management entity
  • S-GW serving gateway
  • the CN node 103 may include a mobility management function (AMF) or a user plane function (UPF) .
  • AMF mobility management function
  • UPF user plane function
  • the wireless communication system may be compatible with any type of network that is capable of sending and receiving wireless communication signals.
  • the wireless communication system 100 is compatible with a wireless communication network, a cellular telephone network, a time division multiple access (TDMA) -based network, a code division multiple access (CDMA) -based network, an orthogonal frequency division multiple access (OFDMA) -based network, a LTE network, a 3rd generation partnership project (3GPP) -based network, a 3GPP 5G network, a satellite communications network, a high altitude platform network, and/or other communications networks.
  • TDMA time division multiple access
  • CDMA code division multiple access
  • OFDMA orthogonal frequency division multiple access
  • the wireless communication system is compatible with the 5G new radio of the 3GPP protocol, wherein BS 102 transmits data using an OFDM modulation scheme on the downlink (DL) and UE 101 transmit data on the uplink (UL) using a single-carrier frequency division multiple access (SC-FDMA) or OFDM scheme. More generally, however, the wireless communication system may implement some other open or proprietary communication protocols, for example, WiMAX, WiFi, among other protocols.
  • the BS 102 may communicate using other communication protocols, such as the IEEE 802.11 family of wireless communication protocols. Further, in some embodiments of the present application, the BS 102 may communicate over licensed spectrums, whereas in other embodiments the BS 102 may communicate over unlicensed spectrums. Embodiments of the present application are not intended to be limited to the implementation of any particular wireless communication system architecture or protocol. In yet some embodiments of the present application, the BS 102 may communicate with UE 101 using the 3GPP 5G protocols.
  • the UE 101 is in RRC_IDLE mode or in RRC_INACTIVE state.
  • the UE 101 connects to the BS 102, and the BS 102 transmits the small data to the CN node 103 via the interface.
  • the data transmission or small data transmission may mean that a UE in inactive mode or idle mode could transmit the data to the network side (or network) , or receive the data from the network side.
  • the data transmission may include at least one of an uplink (UL) data transmission and downlink (DL) data transmission.
  • the inactive or idle UE may receive a suspend message or release message from the network and then go back to the inactive or idle mode.
  • the inactive or idle UE may receive a suspend message or release message from the network and the UE still stay in inactive or idle mode during the data transmission procedure.
  • the suspend message or release message is an RRC message.
  • the data size in such data transmission may be no larger than the maximum transport block (TB) size that can be applied in one transmission, as defined in standard (s) or protocol (s) . Small data transmission is one of such scenarios.
  • the solutions on licensed carriers can be reused for NR-U if applicable.
  • the MAC entity For each activated Serving Cell configured with lbt-FailureRecoveryConfig, the MAC entity shall:
  • the consistent LBT failure recovery is configured per serving cell and the consistent LBT failure is detected per UL BWP.
  • the SDT can only be performed on the pre-configured UL resource (s) or the granted RACH resource (in 2-step RACH procedure or 4-step RACH procedure) but not on the whole BWP, thus the LBT failure detection on the whole BWP seems not necessary during SDT. Therefore, it is necessary to optimize the procedure with a LBT failure recovery mechanism for SDT. Therefore, how to detect the LBT failure and configure the related parameters will be discussed in the following description.
  • the consistent LBT failure for all UL BWP (s) with random access (RA) configuration will lead to radio link failure (RLF) and RRC re-establishment eventually. It is beneficial to avoid data loss and latency introduced by RRC re-establishment if a LBT failure can be recovered before RLF.
  • the LBT failure is recovered by initializing a RACH or a PUSCH transmission.
  • FIG. 2 illustrates a flow chart of a method for handling consistent LBT failure during small data transmission according to some embodiments of the present application.
  • the method in FIG. 2 is performed between a BS (e.g., BS 102 in FIG. 1) and a UE (e.g., UE 101 in FIG. 1) .
  • a BS e.g., BS 102 in FIG. 1
  • a UE e.g., UE 101 in FIG. 1
  • the BS may transmit configuration information for the consistent LBT failure for SDT.
  • the configuration information for the consistent LBT failure for SDT may be transmitted by system broadcast message or RRC signaling.
  • the configuration information for the consistent LBT failure for SDT may be configured with the SDT configuration.
  • the configuration information may at least include the following parameters: the maximum number of LBT failure indications received from lower layers for consistent LBT failure detection when doing SDT (such as, lbt-FailureInstanceMaxCount-SDT) and the time duration for consistent LBT failure detection when doing SDT (such as, lbt-FailureDetectionTimer-SDT) . These parameters can be used for RACH based SDT and/or pre-configured UL resource based (configured grant (CG) type 1 based) SDT for the consistent LBT failure detection.
  • CG configured grant
  • step 210 may not be performed if the configuration information has been transmitted to the UE in advance, or predefined in the specification.
  • the consistent LBT failure for SDT may be detected per UL resource for SDT by counting LBT failure indications.
  • the UE may receive LBT failure indications for SDT.
  • the lower layer (such as physical layer) of the UE may detect a LBT failure for SDT and indicate the LBT failure for SDT to MAC layer of the UE.
  • the UE may trigger the consistent LBT failure for the UL resource for SDT in response to a number of the LBT failure indications exceeding or being equal to a predetermined threshold within predetermined time duration for the UL resource for SDT.
  • the predetermined threshold may correspond to the maximum number of the LBT failure indications (lbt-FailureInstanceMaxCount-SDT) and the predetermined time duration may correspond to time duration for monitoring LBT failure for SDT (lbt-FailureDetectionTimer-SDT) .
  • a counter for LBT failure indication for SDT may be configured to be set to 0 initially and to counter the number of the LBT failure indications.
  • the counter can be configured per UL resource, per BWP, or per serving cell.
  • the UE when the UE receives the configured maximum number of LBT failure indications within the configured time duration for the UL resource, the consistent LBT failure is triggered for the UL resource for SDT.
  • the maximum number of LBT failure indications and the time duration for the UL resource are configured in the configuration information for the consistent LBT failure for SDT, such as, by network (NW) via RRC layer.
  • the UL resource may be a UL pre-configured resource for SDT, a physical uplink shared channel (PUSCH) resource and PRACH resource during a RACH procedure for SDT, or any other UL resource for SDT.
  • the RACH procedure for SDT may include 2-step RACH procedure or 4-step RACH procedure.
  • the lower layer of the UE may detect LBT failure for all UL transmissions per UL pre-configured resource, per UL bandwidth part (BWP) , or per physical random access channel (PRACH) index, per MsgA PUSCH configuration, or Msg3 PUSCH configuration, and indicate each LBT failure to the MAC entity.
  • BWP UL bandwidth part
  • PRACH physical random access channel
  • each of the LBT failure indications may include information indicating the LBT failure indication is for which UL pre-configured resource, which UL BWP, which PRACH index (or PRACH configuration index) , which MsgA PUSCH configuration, or which Msg3 PUSCH allocation. For example, if the LBT failure is indicated per UL pre-configured resource, the indication should include that the LBT failure indication is for which UL pre-configured resource.
  • the LBT failure is indicated as legacy (for example, by 1 bit)
  • a note may be added, for example, the LBT on multi-subband should base on the sequence of subband frequency from low to high, or some pre-configured sequence which can be mapped to the UL pre-configured resource, in order to indicate the LBT failure is for which subband , or the LBT failure is for which UL pre-configured resource.
  • the note is to provide a specific indication to the counter of LBT failure.
  • the MAC entity may detect the consistent LBT failure by counting the LBT failure indications for all UL transmissions.
  • the MAC entity may detect the consistent LBT failure per UL pre-configured resource for SDT by counting the LBT failure indications for all UL transmissions; detect the consistent LBT failure per UL bandwidth part (BWP) for SDT by counting the LBT failure indications for all UL transmissions; or detect the consistent LBT failure per physical random access channel (PRACH) index, per MsgA PUSCH configuration, or Msg3 PUSCH configuration by counting the LBT failure indications for all UL transmissions.
  • BWP bandwidth part
  • PRACH physical random access channel
  • the UE may perform a recovery procedure in response to the consistent LBT failure for the UL resource for SDT being triggered.
  • the UE may perform a recovery procedure by switching the SDT from the UL resource to another UL resource. However, if there is no UL resource available for the SDT or any UL transmission, the UE may initiate a random access channel (RACH) procedure.
  • RACH random access channel
  • the MAC entity of the UE may select the UL resource for switching is in an order of priority for switching: each UL pre-configured resource for SDT which has not been indicated LBT failure, each MsgA resource including PRACH resource and MsgA PUSCH resource during a 2-step RACH procedure for SDT which has not been indicated LBT failure, each PRACH resource during a RACH procedure (4-step RACH procedure) for SDT which has not been indicated LBT failure, and each PRACH resource during a RACH procedure not for SDT which has not been indicated LBT failure.
  • the order of priority for switching can be specified by 3GPP specification or configured/broadcasted by the network (NW) .
  • the MAC entity of the UE may select the UL resource for SDT for switching from any one of the following UL resources: each UL pre-configured resource for SDT which has not been indicated LBT failure, each MsgA resource including PRACH resource and MsgA PUSCH resource during a 2-step RACH procedure for SDT which has not been indicated LBT failure, each PRACH resource during a RACH procedure (4-step RACH procedure) for SDT which has not been indicated LBT failure, and each PRACH resource during a RACH procedure not for SDT which has not been indicated LBT failure. That is, in this embodiment, the UL resources for SDT for switching do not need to be sorted.
  • the MAC entity of the UE may select the second UL resource for switching is in an order of priority for switching: each UL pre-configured resource for SDT on the same BWP which has not been indicated LBT failure, each MsgA resource including PRACH resource and MsgA PUSCH resource during a 2-step RACH procedure for SDT on the same BWP which has not been indicated LBT failure, each PRACH resource during a RACH procedure (4-step RACH procedure) for SDT on the same BWP which has not been indicated LBT failure, each UL pre-configured resource for SDT on another BWP which has not been indicated LBT failure, each MsgA resource including PRACH resource and MsgA PUSCH resource during a 2-step RACH procedure for SDT on another BWP which has not been indicated LBT failure, each PRACH resource during a RACH procedure
  • the MAC entity of the UE may select the UL resource for SDT for switching from any one of the following UL resources: each UL pre-configured resource for SDT on the same BWP which has not been indicated LBT failure, each MsgA resource including PRACH resource and MsgA PUSCH resource during a 2-step RACH procedure for SDT on the same BWP which has not been indicated LBT failure, each PRACH resource during a RACH procedure (4-step RACH procedure) for SDT on the same BWP which has not been indicated LBT failure, each UL pre-configured resource for SDT on another BWP which has not been indicated LBT failure, each MsgA resource including PRACH resource and MsgA PUSCH resource during a 2-step RACH procedure for SDT on another BWP which has not been indicated LBT failure, each PRACH resource during a
  • the MAC entity of the UE autonomously switches the SDT from the first UL pre-configured resource to a second UL pre-configured resource on a second UL BWP which has not been indicated LBT failure.
  • a first UL pre-configured resource e.g. pre-configured CG type1 resource
  • the MAC entity of the UE autonomously switches the SDT from the first UL pre-configured resource to a second UL pre-configured resource on a second UL BWP which has not been indicated LBT failure.
  • the MAC entity of the UE autonomously switches the SDT from the first UL pre-configured resource to a third UL BWP with random access (RA) configuration which has not been indicated LBT failure. It could be up to the UE implementation to switch the SDT to the second UL pre-configured resource on the second UL BWP with or without RA configuration which has not been indicated LBT failure, or switch the SDT to the second UL pre-configured resource on the second UL BWP with RA configuration prior to the second UL BWP without RA configuration which has not been indicated LBT failure.
  • RA random access
  • the MAC entity of the UE autonomously switches the SDT to a second UL pre-configured resource on a second UL BWP with or without RA configuration which has not been indicated LBT failure. Furthermore, in the case that there is no the second UL pre-configured resource on the second UL BWP, the MAC entity of the UE autonomously switches the SDT to a third UL BWP with RA configuration which has not been indicated LBT failure.
  • the MAC entity of the UE autonomously switches the SDT from the pre-configured CG type1 resource to another pre-configured CG type1 resource, if configured.
  • the MAC entity of the UE autonomously switches the SDT from the pre-configured CG type1 resource to an UL BWP, on same carrier in this serving cell, configured with PRACH occasion for SDT and for which consistent LBT failure has not been triggered.
  • the MAC entity of the UE autonomously switches the SDT from the pre-configured CG type1 resource to an UL BWP, on same carrier in this serving cell, configured with PRACH occasion and for which consistent LBT failure has not been triggered.
  • the MAC entity of the UE autonomously switches the SDT from the PRACH configuration index and/or the MsgA PUSCH configuration to an UL BWP, on same carrier in this serving cell, configured with PRACH occasion for SDT and for which consistent LBT failure has not been triggered.
  • the MAC entity of the UE autonomously switches the SDT from the PRACH configuration index and/or the MsgA PUSCH configuration to an UL BWP, on same carrier in this serving cell, configured with PRACH occasion and for which consistent LBT failure has not been triggered.
  • the MAC entity of the UE autonomously switches the SDT from the active UL BWP to an UL BWP, on same carrier in this serving cell, configured with PRACH occasion for SDT and for which consistent LBT failure has not been triggered, or to an UL BWP, on same carrier in this serving cell, configured with PRACH occasion and for which consistent LBT failure has not been triggered.
  • the MAC entity of the UE autonomously switches the SDT to a UL pre-configured resource on a second UL BWP with or without RA configuration which has not been indicated LBT failure.
  • the UE may initiate the corresponding UL transmission, for example, UL pre-configured resource based SDT or a RACH based SDT or a random access procedure, by switching the SDT from the UL resource to the selected UL resource. Accordingly, the BS may receive the UL transmission for SDT.
  • the MAC entity of the UE may indicate a consistent LBT failure for SDT to upper layers (such as RRC layer) .
  • a MAC PDU is transmitted and LBT failure indication is not received from lower layers and this MAC PDU includes the LBT failure indication or this MAC PDU is transmitted on the switched UL resource (and the switching is trigged by consistent LBT failure) , or if consistent LBT failure is triggered and not cancelled and a random access procedure is considered successfully completed, or a preamble or a MAC PDU in a random access procedure is transmitted, or if the configuration information for the consistent LBT failure for SDT (such as, lbt-FailureRecoveryConfig-SDT) is reconfigured by upper layers (such as, RRC layer) , the MAC entity of the UE may cancel the triggered consistent LBT failure.
  • the configuration information for the consistent LBT failure for SDT such as, lbt-FailureRecoveryConfig-SDT
  • the MAC entity of the UE may set LBT_COUNTER_SDT to 0.
  • FIG. 3 illustrates an apparatus according to some embodiments of the present application.
  • the apparatus 300 may be the UE 101 as illustrated in FIG. 1 or other embodiments of the present application.
  • the apparatus 300 may include a receiver 301, a transmitter 303, a processer 305, and a non-transitory computer-readable medium 307.
  • the non-transitory computer-readable medium 307 has computer executable instructions stored therein.
  • the processer 305 is configured to be coupled to the non-transitory computer readable medium 307, the receiver 301, and the transmitter 303.
  • the apparatus 300 may include more computer-readable mediums, receiver, transmitter and processors in some other embodiments of the present application according to practical requirements.
  • the receiver 301 and the transmitter 303 are integrated into a single device, such as a transceiver.
  • the apparatus 300 may further include an input device, a memory, and/or other components.
  • the non-transitory computer-readable medium 307 may have stored thereon computer-executable instructions to cause the apparatus 300 to implement the method according to embodiments of the present application.
  • FIG. 4 illustrates another apparatus according to some embodiments of the present application.
  • the apparatus 400 may be the BS 102 as illustrated in FIG. 1 or other embodiments of the present application.
  • the apparatus 400 may include a receiver 401, a transmitter 403, a processer 405, and a non-transitory computer-readable medium 407.
  • the non-transitory computer-readable medium 407 has computer executable instructions stored therein.
  • the processer 405 is configured to be coupled to the non-transitory computer readable medium 407, the receiver 401, and the transmitter 403. It is contemplated that the apparatus 400 may include more computer-readable mediums, receiver, transmitter and processors in some other embodiments of the present application according to practical requirements.
  • the receiver 401 and the transmitter 403 are integrated into a single device, such as a transceiver.
  • the apparatus 400 may further include an input device, a memory, and/or other components.
  • the non-transitory computer-readable medium 407 may have stored thereon computer-executable instructions to cause the apparatus 400 to implement the method according to embodiments of the present application.
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • the steps of a method may reside as one or any combination or set of codes and/or instructions on a non-transitory computer-readable medium, which may be incorporated into a computer program product.
  • the terms “comprises, “ “comprising, “ or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
  • An element proceeded by “a, “ “an, “ or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element.
  • the term “another” is defined as at least a second or more.
  • the terms “including, “ “having, “ and the like, as used herein, are defined as “comprising. "

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 demande concernent un procédé et un appareil pour la transmission de petites données. Dans un mode de réalisation de la présente demande, le procédé consiste à : recevoir des indications d'échec d'une procédure LBT (écouter avant de parler) pour une transmission de petites données (SDT) ; déclencher un échec de LBT cohérent pour une première ressource de liaison montante (UL) pour une SDT en réponse au fait qu'un nombre d'indications d'échec est égal ou supérieur à un seuil prédéterminé pendant une durée prédéterminée pour la première ressource UL pour la SDT; et réaliser une procédure de reprise en commutant la SDT de la première ressource UL à une seconde ressource UL en réponse au déclenchement de l'échec de LBT cohérent pour la première ressource UL pour la SDT.
PCT/CN2020/129755 2020-11-18 2020-11-18 Procédé et appareil pour la transmission de petites données Ceased WO2022104589A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/129755 WO2022104589A1 (fr) 2020-11-18 2020-11-18 Procédé et appareil pour la transmission de petites données

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/129755 WO2022104589A1 (fr) 2020-11-18 2020-11-18 Procédé et appareil pour la transmission de petites données

Publications (1)

Publication Number Publication Date
WO2022104589A1 true WO2022104589A1 (fr) 2022-05-27

Family

ID=81708183

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/129755 Ceased WO2022104589A1 (fr) 2020-11-18 2020-11-18 Procédé et appareil pour la transmission de petites données

Country Status (1)

Country Link
WO (1) WO2022104589A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2024503227A (ja) * 2021-01-11 2024-01-25 中興通訊股▲ふん▼有限公司 無線ネットワーク内におけるスモールデータ伝送のための方法、デバイス、およびシステム

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200154480A1 (en) * 2018-11-13 2020-05-14 Mediatek Singapore Pte. Ltd. Method And Apparatus For Detecting Consistent Listen Before Talk Failure In Mobile Communications
US20200221495A1 (en) * 2019-01-09 2020-07-09 FG Innovation Company Limited Method and apparatus for lbt failure detection
CN111800888A (zh) * 2019-08-13 2020-10-20 维沃移动通信有限公司 一种sdt处理方法、设备及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200154480A1 (en) * 2018-11-13 2020-05-14 Mediatek Singapore Pte. Ltd. Method And Apparatus For Detecting Consistent Listen Before Talk Failure In Mobile Communications
US20200221495A1 (en) * 2019-01-09 2020-07-09 FG Innovation Company Limited Method and apparatus for lbt failure detection
CN111800888A (zh) * 2019-08-13 2020-10-20 维沃移动通信有限公司 一种sdt处理方法、设备及系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "Detecting and Handling of UL LBT failures", 3GPP DRAFT; R2-1912625-DETECTING AND HANDLING OF UL LBT FAILURES, vol. RAN WG2, 4 October 2019 (2019-10-04), Chongqing, China, pages 1 - 5, XP051790664 *
MEDIATEK INC: "On consistent LBT failures", 3GPP DRAFT; R2-1913260 - ON CONSISTENT LBT FAILURES, vol. RAN WG2, 3 October 2019 (2019-10-03), Chongqing, China, pages 1 - 5, XP051791272 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2024503227A (ja) * 2021-01-11 2024-01-25 中興通訊股▲ふん▼有限公司 無線ネットワーク内におけるスモールデータ伝送のための方法、デバイス、およびシステム
JP7703661B2 (ja) 2021-01-11 2025-07-07 中興通訊股▲ふん▼有限公司 無線ネットワーク内におけるスモールデータ伝送のための方法、デバイス、およびシステム

Similar Documents

Publication Publication Date Title
US20230141380A1 (en) Method and apparatus for sidelink resource re-evaluation
US20230413345A1 (en) Method and apparatus for small data transmission
WO2022151239A1 (fr) Procédé et appareil de traitement de transmission de données
WO2022082584A1 (fr) Procédés et appareils pour un mécanisme de désactivation de scg et un mécanisme d'activation de scg dans un scénario mr-dc
US20230328835A1 (en) Methods and apparatuses for a data transmission and a rnau procedure of a ue in rrc inactive state
CN112806086A (zh) 一种随机接入方法、设备及存储介质
US20230058891A1 (en) Information sending method, information receiving method, terminal and network device
WO2022104589A1 (fr) Procédé et appareil pour la transmission de petites données
WO2022151068A1 (fr) Procédé et appareil pour un traitement de secours pour des données disponibles
US20240373276A1 (en) Method and apparatus for data transmission in non-connected state
WO2022155961A1 (fr) Procédé et appareil pour configurer des temporisateurs et effectuer une transmission de données dans une procédure sdt
US20250024510A1 (en) Methods and apparatuses of a mro mechanism for ul coverage enhancement and network slicing procedures
US20240172017A1 (en) Methods and apparatuses for a rlf processing procedure and a phr procedure in a deactivated sn case
EP4378212A1 (fr) Configuration de repli conditionnel pour mcg-rlf
US12507317B2 (en) Methods and apparatuses for a SCG deactivation mechanism and a SCG activation mechanism in a MR-DC scenario
WO2022120570A1 (fr) Procédé et appareil de rapport de ressource d'autorisation configurée
WO2024065529A9 (fr) Procédés et appareils pour un mécanisme d'amélioration de surveillance de pdcch pour un trafic xr
WO2022134027A1 (fr) Procédé et appareil pour un traitement d'informations dans une procédure de transmission de petites données
WO2022193128A1 (fr) Procédés et appareils pour une procédure de traitement de rlf et une procédure de phr en cas de sn désactivé
WO2022205344A1 (fr) Procédé et appareil de gestion de l'arrivée d'une transmission de non petites données
US20240057172A1 (en) Methods and apparatuses for a user equipment (ue) triggered secondary cell group (scg) activation procedure
US20240073968A1 (en) Method and apparatus for handling fallback of data transmission
WO2022052104A1 (fr) Procédés et appareils d'optimisation d'une interruption ho de liaison montante

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: 20961880

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 06/09/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20961880

Country of ref document: EP

Kind code of ref document: A1