[go: up one dir, main page]

WO2025231772A1 - Dispositifs et procédés de communication - Google Patents

Dispositifs et procédés de communication

Info

Publication number
WO2025231772A1
WO2025231772A1 PCT/CN2024/092103 CN2024092103W WO2025231772A1 WO 2025231772 A1 WO2025231772 A1 WO 2025231772A1 CN 2024092103 W CN2024092103 W CN 2024092103W WO 2025231772 A1 WO2025231772 A1 WO 2025231772A1
Authority
WO
WIPO (PCT)
Prior art keywords
mac
terminal device
subheader
sdu
index
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.)
Pending
Application number
PCT/CN2024/092103
Other languages
English (en)
Inventor
Li Zhang
Zonghui XIE
Gang Wang
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.)
NEC Corp
Original Assignee
NEC Corp
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 NEC Corp filed Critical NEC Corp
Priority to PCT/CN2024/092103 priority Critical patent/WO2025231772A1/fr
Publication of WO2025231772A1 publication Critical patent/WO2025231772A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control

Definitions

  • Example embodiments of the present disclosure generally relate to the field of communication techniques and in particular, to devices and methods for enhanced early data transmission (EDT) .
  • EDT enhanced early data transmission
  • IoT Internet of Things
  • NTN Non-Terrestrial Networks
  • EDT enhanced early data transmission
  • This strategy supports uplink capacity enhancements and explore advanced multiplexing techniques of multiple UEs, potentially reducing the necessary uplink and downlink signaling to complete EDT transactions, which is expected to improve the communication processes and increase efficiency in IoT networks. Therefore, it is worth studying the enhancements for early data transmission, as they hold significant potential to optimize IoT operations and resource utilization in networks.
  • embodiments of the present disclosure provide a solution for enhanced EDT.
  • a terminal device comprising: a processor, configured to cause the terminal device to: receive, from a network device, a downlink message associated with early data transmission, wherein the downlink message associated with the early data transmission comprises at least one of: a backoff indication for the early data transmission, a subcarrier index for the early data transmission, an index of a parameter in code domain, a timing advance for the for the early data transmission, an identity of contention resolution, or a medium access control (MAC) service data unit (SDU) .
  • MAC medium access control
  • a terminal device comprising: a processor, configured to cause the terminal device to: receive, from a network device, a configuration for physical uplink shared channel (PUSCH) resource, wherein the configuration indicates a plurality of PUSCH resources, and each of the plurality of PUSCH resources is configured with an identity and one or more subcarriers; and determine a PUSCH resource from the plurality of PUSCH resources based on a capability of the terminal device and the configuration.
  • PUSCH physical uplink shared channel
  • a terminal device comprising: a processor, configured to cause the terminal device to: transmit, to a network device, data on a physical uplink shared channel (PUSCH) during an early data transmission procedure with a first power; and in response to the transmission of the data on the PUSCH being failed, transmit the data to the network device with a second power, wherein the second power is higher than the first power.
  • PUSCH physical uplink shared channel
  • a terminal device comprising: a processor, configured to cause the terminal device to: determine a target transmission type from a plurality of transmission types, wherein the plurality of transmission types comprise a first type of early data transmission, a second type of early data transmission and a preconfigured uplink resource (PUR) transmission type; and transmit, to a network device, data based on the target transmission type.
  • a processor configured to cause the terminal device to: determine a target transmission type from a plurality of transmission types, wherein the plurality of transmission types comprise a first type of early data transmission, a second type of early data transmission and a preconfigured uplink resource (PUR) transmission type; and transmit, to a network device, data based on the target transmission type.
  • PUR preconfigured uplink resource
  • a terminal device comprising: a processor, configured to cause the terminal device to: determine that a radio network temporary identity is related to physical uplink shared channel (PUSCH) transmission based on one of: a radio network temporary identity space for the PUSCH transmission or a physical downlink control channel (PDCCH) search space for the PDSCH transmission.
  • PUSCH physical uplink shared channel
  • PDCCH physical downlink control channel
  • a network device comprising: a processor, configured to cause the network device to: transmit, to a terminal device, a downlink message associated with early data transmission, wherein the downlink message associated with the early data transmission comprises at least one of: a backoff indication for the early data transmission, a subcarrier index for the early data transmission, an index of a parameter in code domain, a timing advance for the for the early data transmission, an identity of contention resolution, or a medium access control (MAC) service data unit (SDU) .
  • MAC medium access control
  • a terminal device comprising: a processor, configured to cause the terminal device to: transmit, to a terminal device, a configuration for physical uplink shared channel (PUSCH) resource, wherein the configuration indicates a plurality of PUSCH resources, and each of the plurality of PUSCH resources is configured with an identity and one or more subcarriers.
  • PUSCH physical uplink shared channel
  • a communication method performed by a terminal device.
  • the method comprises: receiving, from a network device, a downlink message associated with early data transmission, wherein the downlink message associated with the early data transmission comprises at least one of: a backoff indication for the early data transmission, a subcarrier index for the early data transmission, an index of a parameter in code domain, a timing advance for the for the early data transmission, an identity of contention resolution, or a medium access control (MAC) service data unit (SDU) .
  • MAC medium access control
  • a communication method performed by a terminal device.
  • the method comprises: receiving, from a network device, a configuration for physical uplink shared channel (PUSCH) resource, wherein the configuration indicates a plurality of PUSCH resources, and each of the plurality of PUSCH resources is configured with an identity and one or more subcarriers; and determining a PUSCH resource from the plurality of PUSCH resources based on a capability of the terminal device and the configuration.
  • PUSCH physical uplink shared channel
  • a communication method performed by a terminal device.
  • the method comprises: transmitting, to a network device, data on a physical uplink shared channel (PUSCH) during an early data transmissoin procedure with a first power; and in response to the transmission of the data on the PUSCH being failed, transmitting the data to the network device with a second power, wherein the second power is higher than the first power.
  • PUSCH physical uplink shared channel
  • a communication method performed by a terminal device. The method comprises: determining a target transmission type from a plurality of transmission types, wherein the plurality of transmission types comprise a first type of early data transmission, a second type of early data transmission and a preconfigured uplink resource (PUR) transmission type; and transmitting, to a network device, data based on the target transmission type.
  • PUR preconfigured uplink resource
  • a communication method performed by a terminal device.
  • the method comprises: determining that a radio network temporary identity is related to physical uplink shared channel (PUSCH) transmission based on one of: a radio network temporary identity space for the PUSCH transmission or a physical downlink control channel (PDCCH) search space for the PDSCH transmission.
  • PUSCH physical uplink shared channel
  • PDCCH physical downlink control channel
  • a communication method performed by a network device.
  • the method comprises: transmitting, to a terminal device, a downlink message associated with early data transmission, wherein the downlink message associated with the early data transmission comprises at least one of: a backoff indication for the early data transmission, a subcarrier index for the early data transmission, an index of a parameter in code domain, a timing advance for the early data transmission, an identity of contention resolution, or a medium access control (MAC) service data unit (SDU) .
  • MAC medium access control
  • a communication method performed by a network device.
  • the method comprises: transmitting, to a terminal device, a configuration for physical uplink shared channel (PUSCH) resource, wherein the configuration indicates a plurality of PUSCH resources, and each of the plurality of PUSCH resources is configured with an identity and one or more subcarriers.
  • PUSCH physical uplink shared channel
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to carry out the method according to any of the eighth, ninth, tenth, eleventh, twelfth, thirteenth, or fourteenth aspect.
  • FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented
  • FIG. 2 illustrates a signaling flow of an enhanced EDT in accordance with some embodiments of the present disclosure
  • FIG. 3 illustrates a schematic diagram of a new medium access control control element (MAC CE) being defined in accordance with some embodiments of the present disclosure
  • FIG. 4A illustrates a schematic diagram of a combination way including only timing advance (TA) command and contention resolution identity (ID) in accordance with some embodiments of the present disclosure
  • FIG. 4B illustrates a schematic diagram of another combination way including orthogonal cover codes (OCC) index, TA and contention resolution ID in accordance with some embodiments of the present disclosure
  • FIG. 5 illustrates a schematic diagram of a MAC protocol data unit (PDU) design for MAC header and MAC service data unit (SDU) , where OCC is included in MAC CE, in accordance with some embodiments of the present disclosure
  • FIG. 6 illustrates a schematic diagram of another MAC PDU design for MAC header and MAC SDU, where OCC index is as a MAC subheader, in accordance with some embodiments of the present disclosure
  • FIG. 7 illustrates a schematic diagram of another MAC PDU design for MAC header and MAC SDU, where OCC is included in MAC CE, in accordance with some embodiments of the present disclosure
  • FIG. 8A illustrates a schematic diagram of the order of MAC subheader and the order of MAC CE and MAC SDU in accordance with some embodiments of the present disclosure
  • FIG. 8B illustrates a schematic diagram of the order of MAC subPDUs in accordance with some embodiments of the present disclosure
  • FIG. 9A illustrates a schematic diagram of another order of MAC subheader and another order of MAC CE and MAC SDU in accordance with some embodiments of the present disclosure
  • FIG. 9B illustrates a schematic diagram of another order of MAC subPDUs in accordance with some embodiments of the present disclosure.
  • FIG. 10A illustrates a schematic diagram of an OCC index indicated in MAC subheader
  • FIG. 10B illustrates a schematic diagram of an OCC index indicated by DCI
  • FIG. 11 illustrates a signaling flow of an enhanced EDT in another case in accordance with some embodiments of the present disclosure
  • FIG. 12 illustrates a signaling flow of an enhanced EDT in another case in accordance with some embodiments of the present disclosure
  • FIG. 13 illustrates a signaling flow of an enhanced EDT in another case in accordance with some embodiments of the present disclosure
  • FIG. 14 illustrates a signaling flow of an enhanced EDT in another case in accordance with some embodiments of the present disclosure
  • FIG. 15 illustrates a flowchart of a communication method implemented at a terminal device according to some example embodiments of the present disclosure
  • FIG. 16 illustrates a flowchart of a communication method implemented at a terminal device according to some example embodiments of the present disclosure
  • FIG. 17 illustrates a flowchart of a communication method implemented at a terminal device according to some example embodiments of the present disclosure
  • FIG. 18 illustrates a flowchart of a communication method implemented at a terminal device according to some example embodiments of the present disclosure
  • FIG. 19 illustrates a flowchart of a communication method implemented at a terminal device according to some example embodiments of the present disclosure
  • FIG. 20 illustrates a flowchart of a communication method implemented at a network device according to some example embodiments of the present disclosure
  • FIG. 21 illustrates a flowchart of a communication method implemented at a network device according to some example embodiments of the present disclosure.
  • FIG. 22 illustrates a simplified block diagram of an apparatus that is suitable for implementing example embodiments of the present disclosure.
  • terminal device refers to any device having wireless or wired communication capabilities.
  • the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, devices on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , extended Reality (XR) devices including different types of realities such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) , the unmanned aerial vehicle (UAV) commonly known as
  • UE user equipment
  • the ‘terminal device’ can further has ‘multicast/broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporate one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM.
  • SIM Subscriber Identity Module
  • the term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.
  • network device refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate.
  • a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , and the like.
  • NodeB Node B
  • eNodeB or eNB evolved NodeB
  • gNB next generation NodeB
  • TRP transmission reception point
  • RRU remote radio unit
  • RH radio head
  • RRH remote radio head
  • IAB node a low power node such as a fe
  • the terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • AI Artificial intelligence
  • Machine learning capability it generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • the terminal or the network device may work on several frequency ranges, e.g., FR1 (e.g., 450 MHz to 6000 MHz) , FR2 (e.g., 24.25GHz to 52.6GHz) , frequency band larger than 100 GHz as well as Tera Hertz (THz) . It can further work on licensed/unlicensed/shared spectrum.
  • FR1 e.g., 450 MHz to 6000 MHz
  • FR2 e.g., 24.25GHz to 52.6GHz
  • THz Tera Hertz
  • the terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario.
  • MR-DC Multi-Radio Dual Connectivity
  • the terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.
  • the embodiments of the present disclosure may be performed in test equipment, e.g., signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator.
  • the terminal device may be connected with a first network device and a second network device.
  • One of the first network device and the second network device may be a master node and the other one may be a secondary node.
  • the first network device and the second network device may use different radio access technologies (RATs) .
  • the first network device may be a first RAT device and the second network device may be a second RAT device.
  • the first RAT device is eNB and the second RAT device is gNB.
  • Information related with different RATs may be transmitted to the terminal device from at least one of the first network device or the second network device.
  • first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device.
  • information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device.
  • Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
  • the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’
  • the term ‘based on’ is to be read as ‘at least in part based on. ’
  • the term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’
  • the term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’
  • the terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
  • values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
  • the term “resource, ” “transmission resource, ” “uplink resource, ” or “downlink resource” may refer to any resource for performing a communication, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other resource enabling a communication, and the like.
  • a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.
  • EDT refers to Early Data Transmission, a feature in cellular networks designed to expedite the data transmission process, particularly in scenarios where low latency and rapid data exchange are critical. EDT is primarily implemented within the context of communication technologies to enhance the responsiveness and efficiency of the network.
  • MAC PDU refers to the Medium Access Control Protocol Data Unit, a key component in the data communication layers of cellular networks.
  • the MAC PDU is the data unit used by the Medium Access Control (MAC) layer to encapsulate higher-layer data and control information for transmission across the physical layer of the network.
  • MAC Medium Access Control
  • MAC CE refers to the Medium Access Control Control Element, an integral component used within the MAC (Medium Access Control) layer in cellular network technologies.
  • MAC CEs are specialized messages embedded within the MAC Protocol Data Unit (PDU) and are used to convey control information between the network and User Equipment (UE) .
  • PDU Protocol Data Unit
  • UE User Equipment
  • OCC refers to Orthogonal Cover Codes, a technique employed in wireless communication systems to allow multiple User Equipments (UEs) to share the same physical resources (such as time and frequency) for signal transmission while maintaining minimal interference among them.
  • OCCs are particularly significant in communication systems that use narrowband transmission techniques, such as narrowband Internet of Things (NB-IoT) .
  • NB-IoT narrowband Internet of Things
  • TA Timing Advance
  • UE user equipment
  • RP reference point
  • PUSCH refers to the Physical Uplink Shared Channel, a key component in the uplink transmission architecture of cellular networks.
  • the PUSCH is used by UEs to transmit data, such as voice, video, or other user-specific information, as well as control information to the base station or gNB.
  • RSRP Reference Signal Received Power
  • RSRP is the average power of the resource elements that carry cell-specific reference signals over the entire bandwidth and is primarily used for cell selection and handover decisions.
  • RRC Radio Resource Control
  • the RRC layer is responsible for the establishment, maintenance, and release of the Radio Bearer, which is the connection between the terminal device and the network device.
  • agreements for enhanced EDT may include the followings.
  • NB-IoT Narrowband Internet of Things
  • eMTC enhanced machine-type communication
  • C-plane control plane
  • U-plane user plane
  • CloT evolved packet system CloT evolved packet system
  • the challenge lies in optimizing the multiplexing of downlink MAC PDUs, the selection of single and multi-tone transmission for NB, and the indication of OCC index.
  • the present disclosure provides solutions for enhanced EDT, including downlink message multiplexing, single tone and multi-tone selection for PUSCH, power ramping for PUSCH, OCC index indication for PUSCH and priorities for EDT, PUR, and enhanced EDT. These solutions significantly improve the efficiency of transmitting downlink message of enhanced EDT procedure, help UE select PUSCH resource based on UE capability and adjust the power for PUSCH.
  • FIG. 1 illustrates a schematic diagram of an example communication environment 100 in which example embodiments of the present disclosure can be implemented.
  • a plurality of communication devices including a terminal device 110 and a network device 120, can communicate with each other.
  • the terminal device 110 may be a UE and the network device 120 may be a base station serving the UE.
  • the serving area of the network device 120 may be called a cell 102.
  • the communication environment 100 may include any suitable number of devices configured to implementing example embodiments of the present disclosure. Although not shown, it would be appreciated that one or more additional devices may be located in the cell 102, and one or more additional cells may be deployed in the communication environment 100. It is noted that although illustrated as a network device, the network device 120 may be another device than a network device. Although illustrated as a terminal device, the terminal device 110 may be other device than a terminal device.
  • terminal device 110 operating as a UE
  • network device 120 operating as a base station
  • operations described in connection with a terminal device may be implemented at a network device or other device
  • operations described in connection with a network device may be implemented at a terminal device or other device.
  • 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 network device 120 is a transmitting (TX) device (or a transmitter)
  • the terminal device 110 is a receiving (RX) device (or a receiver)
  • the terminal device 110 is a TX device (or a transmitter) and the network device 120 is a RX device (or a receiver) .
  • the communications in the communication environment 100 may conform to any suitable standards including, but not limited to, Global System for Mobile Communications (GSM) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , New Radio (NR) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , GSM EDGE Radio Access Network (GERAN) , Machine Type Communication (MTC) and the like.
  • GSM Global System for Mobile Communications
  • LTE Long Term Evolution
  • LTE-Evolution LTE-Advanced
  • NR New Radio
  • WCDMA Wideband Code Division Multiple Access
  • CDMA Code Division Multiple Access
  • GERAN GSM EDGE Radio Access Network
  • MTC Machine Type Communication
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.
  • downlink message of enhanced EDT procedure backoff, TA and contention resolution ID may be indicated for NB.
  • MAC SDU may also exist.
  • downlink message from multiple UEs may be multiplexed into one MAC PDU.
  • the present disclosure can consider how to multiplex these information into one MAC PDU, and may transmit downlink message of enhanced EDT procedure effectively.
  • FIG. 2 illustrates a signaling flow 200 of an enhanced EDT between the terminal device and the network device in accordance with some embodiments of the present disclosure.
  • the signaling flow 200 will be discussed with reference to FIG. 1, for example, by using the terminal device 110 and the network device 120.
  • the network device 120 transmits (2005) the downlink message associated with the early data transmission to the terminal device 110.
  • the terminal device 110 receives (2005) , from the network device 120, a downlink message associated with early data transmission.
  • the network device 120 may perform (2010) the early data transmission.
  • the terminal device 110 may receive (2020) data for the early data transmission from the network device 120.
  • the downlink message associated with the early data transmission includes at least one of the following: a backoff indication for the early data transmission, a subcarrier index for the early data transmission, an index of a parameter in code domain, a timing advance for the early data transmission, an identity of contention resolution, or a medium access control (MAC) service data unit (SDU) .
  • MAC medium access control
  • the backoff indication may be as a MAC subheader.
  • the parameter in code domain may be OCC, and OCC index (i.e., the index of the parameter in code domain) may be indicated by a new MAC CE or a subheader.
  • OCC index i.e., the index of the parameter in code domain
  • MAC SDU RRCEarlyDataComplete can be included for CP, and RRCConnectionRelease and possible data can be included for UP.
  • the downlink message may include the backoff indication, the timing advance, the identity of contention resolution and the MAC SDU.
  • OCC index can be indicated by DCI or RNTI
  • the downlink message may include the backoff indication, the timing advance, the identity of contention resolution, and the MAC SDU.
  • backoff indication may be placed in the first subheader, then contention resolution ID MAC CE, and TA MAC CE may follow the backoff indication. Then MAC SDU may follow.
  • the backoff indication, the identity of contention resolution, the timing advance and the MAC SDU included in the downlink message may be in sequence.
  • the backoff indication, a MAC control element (CE) including the identity of contention resolution and the timing advance, and the MAC SDU included in the downlink message may be in sequence.
  • the downlink message may include the backoff indication, the index of the parameter in code domain, the timing advance, the identity of contention resolution, and a MAC protocol data unit (PDU) .
  • the OCC index may be included, and the order may be as following.
  • the backoff indication, the index of the parameter in code domain, the identity of contention resolution, the timing advance and the MAC SDU included in the downlink message may be in sequence.
  • the backoff indication, the index of the parameter in code domain, a MAC CE including the identity of contention resolution and the timing advance, and the MAC SDU included in the downlink message may be in sequence.
  • the backoff indication, a MAC CE including the identity of contention resolution, the timing advance and the index of the parameter in code domain, and the MAC SDU included in the downlink message may be in sequence.
  • the downlink message may include the backoff indication, the subcarrier index, the timing advance, the identity of contention resolution, and the MAC SDU.
  • the subcarrier index may be included, and the order may be as following.
  • the backoff indication, the subcarrier index, the identity of contention resolution, the timing advance and the MAC SDU included in the downlink message may be in sequence.
  • the backoff indication, the subcarrier index, a MAC control element (CE) including the identity of contention resolution and the timing advance, and the MAC SDU included in the downlink message may be in sequence.
  • CE MAC control element
  • an absolute TA value is indicated via random access response (RAR) and relative TA value is indicated by a MAC CE.
  • RAR random access response
  • the absolute TA value is indicated in other ways as the followings.
  • a dedicated MAC CE may be used to indicate the timing advance (TA) for the early data transmission.
  • the dedicated MAC CE may be defined as shown in FIG. 3, and absolute TA value may be indicated by the dedicated MAC CE.
  • a MAC CE may include the timing advance for the early data transmission and the identity of contention resolution. In this case, TA and contention resolution ID may be combined into one MAC CE, as shown in FIG. 4A and FIG. 4B.
  • the combination way shown in FIG. 4A and FIG. 4B is similar to success RAR within 2-step procedure.
  • only TA and contention resolution ID may be combined into one MAC CE
  • the OCC index, TA and contention resolution ID may be combined into one MAC CE.
  • the downlink message includes the backoff indication, the index of the parameter in code domain, the identity of contention resolution, and the MAC SDU.
  • the OCC index may be included in MAC CE.
  • the backoff indication may be indicated by a MAC subheader, and an order for MAC header may be the MAC subheader for the backoff indication, subheaders for all MAC CEs and subheaders for all MAC SDUs, as shown in FIG. 5.
  • all MAC CEs may be placed after all MAC headers and before all MAC SDUs, and each MAC CE may be associated with one MAC SDU, as shown in FIG. 5.
  • the first MAC SDU may be corresponded to the first MAC CE; and the second MAC SDU may be corresponded to the second MAC CE.
  • This MAC PDU design is similar to LTE.
  • the OCC index is as a MAC subheader.
  • the backoff indication may be indicated by a first MAC subheader
  • the index of the parameter in code domain may be indicated by a second MAC subheader.
  • an order for MAC header may be: the first MAC subheader for the backoff indication, the second MAC subheader for the index of the parameters in code domain, subheaders for all MAC CEs and subheaders for all MAC SDUs, as shown in FIG. 6.
  • All MAC CEs may be placed after all MAC headers and before all MAC SDUs as shown in FIG. 6, and each index of the parameter in code domain is associated with one identity of contention resolution, one timing advance and one MAC SDU.
  • contention resolution ID MAC CE1 and TA MAC CE 2 may be corresponded to the first OCC index
  • contention resolution ID, and MAC CE 3 and TA MAC CE 4 may correspond to the second OCC index.
  • This MAC PDU design is similar to LTE.
  • OCC index may be included in MAC CE.
  • the backoff indication may be indicated by a first MAC subPDU, and the first MAC subPDU only includes backoff indication subheader.
  • one MAC subPDU may be used for indicating the identity of the contention resolution, the timing advance and the corresponding MAC SDU.
  • MAC subPDU including backoff indication subheader may be placed in the first place.
  • MAC subPDU including MAC CE and MAC SDU can be placed after MAC subPDU including backoff indication subheader.
  • the corresponding order may be MAC CE subheader and MAC CE, MAC SDU subheader and MAC SDU, as shown in FIG. 7.
  • all MAC subheaders may be placed before all MAC CEs and MAC SDUs and all MAC CEs may be placed before all MAC SDUs and after all MAC subheaders.
  • an order of MAC subheader may be a subheader of the backoff indication, a subheader of MAC CE and a subheader of MAC SDU.
  • an order of MAC CE and MAC SDU may be MAC CE 1, MAC CE 2, ... MAC CE n, MAC SDU 1, MAC SDU 2, ... MAC SDU k, as shown in FIG. 8A.
  • an order of MAC subPDU may be a MAC subPDU for the backoff indication, a MAC subPDU for MAC CE, and a MAC subPDU for MAC SDU, as shown in FIG. 8B.
  • backoff indication subheader may only include backoff indication subheader.
  • MAC subPDU for MAC CE may include a subheader for MAC CE and the MAC CE
  • the MAC subPDU for MAC SDU may include a subheader for MAC SDU and the MAC SDU.
  • each MAC subPDU may be associated with one or more MAC SDUs, as shown in FIG. 8B.
  • all MAC subheaders may be placed before all MAC CEs and MAC SDUs and all MAC CEs may be placed before all MAC SDUs and after all MAC subheaders.
  • an order of MAC subheader may be a subheader of the backoff indication, a subheader for the subcarrier, a subheader of MAC CE and a subheader of MAC SDU.
  • an order of MAC CE and MAC SDU may be MAC CE 1, MAC CE 2, ... MAC CE n, MAC SDU 1, MAC SDU 2, ... MAC SDU k, as shown in FIG. 9A.
  • an order of MAC subPDU may be a MAC subPDU for the backoff indication, a MAC subPDU for MAC CE, and a MAC subPDU for MAC SDU as shown in FIG. 9B.
  • backoff indication subheader may only include backoff indication subheader
  • subcarrier index subheader only may include subcarrier index.
  • MAC subPDU for MAC CE may include a subheader for MAC CE and the MAC CE
  • the MAC subPDU for MAC SDU may include a subheader for MAC SDU and the MAC SDU.
  • each MAC subPDU may be associated with one or more MAC SDUs, as shown in FIG. 9B.
  • PUSCH resource pool may be as code domain resource. If a plurality of indexes of the parameter in code domain are configured for a PUSCH resource pool, when the terminal device 110 selects an index of the parameter in code domain, in order to identify downlink message, the index of the parameter in code domain needs to be indicated to the terminal device 110.
  • the index of the parameter in code domain may be indicated in a radio network temporary identity (RNTI) , which means that the index of the parameter in code domain can be used for calculating RNTI.
  • RNTI radio network temporary identity
  • the index of the parameter in code domain may be indicated in a dedicated MAC CE.
  • a dedicated MAC CE can be used for indicating the index of the parameter in code domain, and an octet may be shown as FIG. 10A.
  • the index of the parameter in code domain may be indicated in a MAC subheader, as shown in FIG. 10B.
  • the index of the parameter in code domain is indicated by downlink control information (DCI) .
  • DCI downlink control information
  • PUSCH physical uplink shared channel
  • tone for each subcarrier set can be configured, i.e. single tone or multi-tone
  • the terminal device 110 may select PUSCH resource based on terminal device capability.
  • FIG. 11 illustrates a signaling flow 1100 of an enhanced EDT between the terminal device and the network device in accordance with some embodiments of the present disclosure.
  • the signaling flow 1100 will be discussed with reference to FIG. 1, for example, by using the terminal device 110 and the network device 120.
  • the network device 120 transmits (11005) the configuration for physical uplink shared channel (PUSCH) resource to the terminal device 110.
  • the terminal device 110 receives (11005) , from the network device 120, a configuration for PUSCH resource.
  • the configuration indicates a plurality of PUSCH resources, and each of the plurality of PUSCH resources is configured with an identity and one or more subcarriers.
  • PUSCH resource pool may include carrier index, subcarrier index, OCC index and so on.
  • PUSCH resource selection procedure is as below.
  • the terminal device determines (11006) a PUSCH resource from the plurality of PUSCH resources based on a capability of the terminal device 110 and the configuration. For example, in some embodiments, the terminal device 110 may select (11010) a coverage enhancement level based on a reference signal received power (RSRP) threshold and a measured RSRP value. In some embodiments, if the coverage enhancement level is selected, the terminal device 110 may select (11015) a carrier based on a probability distribution. In some embodiments, if the carrier is selected, the terminal device 110 may select (11020) a PUSCH resource set in the carrier according to whether the terminal device supports multi-tone. If the terminal device 110 supports the multi-tone, the terminal device 110 may select (11020) PUSCH resources according to the multi-tone.
  • RSRP reference signal received power
  • the terminal device 110 may select (11020) PUSCH resources corresponding to a single tone. In some embodiments, if a plurality of multi-tone PUSCH resources are configured, the terminal device 110 may select (11020) a PUSCH resource.
  • the terminal device 110 may select (11025) an index of the parameters in code domain within the PUSCH resource. In some other embodiments, the terminal device 110 may select (11025) the index of the parameters in code domain based on a probability value.
  • power may be increased by the introduced power ramping step.
  • the terminal device may perform the next preamble transmission with the higher power.
  • the power for PUSCH may be adjusted, which can increase the receiving probability of PUSCH.
  • FIG. 12 illustrates a signaling flow 1200 of an enhanced EDT between the terminal device and the network device in accordance with some embodiments of the present disclosure.
  • the signaling flow 1200 will be discussed with reference to FIG. 1, for example, by using the terminal device 110 and the network device 120.
  • the terminal device 110 transmits (12005) , to the network device 120, data on a physical uplink shared channel (PUSCH) during an early data transmission procedure with a first power.
  • the network device 120 receives (12005) the data on PUSCH with the first power.
  • PUSCH physical uplink shared channel
  • the network device 120 may transmit (12010) , to the network device, information indicating a power ramping step. Then the terminal device 110 may determine (12015) a second power. If the transmission of the data on the PUSCH is failed, the terminal device 110 may transmit (12020) the data on the physical uplink shared channel (PUSCH) with the second power. In some embodiments, the second power may be determined based on the first power and a value of a counter for the PUSCH transmission.
  • the power ramping step may be configured by a system information block (SIB) or radio resource control (RRC) message.
  • SIB system information block
  • RRC radio resource control
  • the maximum transmission number of PUSCH may be configured by a system information block (SIB) or radio resource control (RRC) message.
  • a counter for transmission on the PUSCH may be initiated as a predetermined number. For example, the PUSCH_TRANSMISSION_COUNTER is initiated as 1.
  • a contention resolution may be not successful, if at least one of the following is met: a contention resolution timer expires, or a contention resolution identity included in a MAC CE does not match a portion of bits of a common control channel (CCCH) service data unit (SDU) transmitted. For example, a contention resolution timer expires, or a contention resolution identity included in a MAC CE does not match 48 first bits of a CCCH SDU transmitted.
  • CCCH common control channel
  • SDU service data unit
  • a counter for the PUSCH transmission may be incremented by 1. For example, if contention resolution is not successful and PUSCH transmission number does not reach the configured maximum number, PUSCH_TRANSMISSION_COUNTER is incremented by 1.
  • PUSCH_TRANSMISSION_COUNTER can participate in calculation, for example MSG3_RECEIVED_TARGET_POWER is set to (PUSCH_TRANSMISSION_COUNTER-1) *powerRampingStepForPUSCH.
  • EDT Early Data Transmission
  • PUR Preconfigured Uplink Resource
  • FIG. 13 illustrates a signaling flow 1300 of an enhanced EDT between the terminal device and the network device in accordance with some embodiments of the present disclosure.
  • the signaling flow 1300 will be discussed with reference to FIG. 1, for example, by using the terminal device 110 and the network device 120.
  • the terminal device 110 determines (13005) a target transmission type from a plurality of transmission types.
  • the plurality of transmission types include a first type of early data transmission, a second type of early data transmission and a preconfigured uplink resource (PUR) transmission type.
  • PUR preconfigured uplink resource
  • the terminal device 110 may determine the target transmission type based on priority information of the plurality of transmission types.
  • the priority information may be transmitted in a system information block or radio resource control message.
  • priorities of the plurality of transmission types in descending order may be the PUR transmission type, the second type of early data transmission, and the first type of early data transmission. In this case, PUR transmission type has the highest priority. In some other embodiments, priorities of the plurality of transmission types in descending order may be the first type of early data transmission, the second type of early data transmission, and the PUR transmission type. In this case, the first type of early data transmission has the highest priority.
  • the terminal device 110 may initiate (13010) the first type of early data transmission. In some other embodiments, if a time gap between an initiation of a procedure of the second type of early data transmission and a first available PUSCH occasion for the procedure of the second type of early data transmission is larger than a threshold, the terminal device 110 may initiate (13010) the first type of early data transmission.
  • the terminal device may initiate (13015) the PUR transmission.
  • the PUR transmission may have a higher priority than the second type of early data transmission.
  • the terminal device may initiate (13020) the second type of early data transmission.
  • FIG. 14 illustrates a signaling flow 1400 of an enhanced EDT between the terminal device and the network device in accordance with some embodiments of the present disclosure.
  • the signaling flow 1400 will be discussed with reference to FIG. 1, for example, by using the terminal device 110 and the network device 120.
  • the radio network temporary identity (RNTI) space for the PUSCH transmission may be based on a radio network temporary identity space of a random access procedure or an early data transmission and an offset.
  • RNTI for PUSCH can be used on top of RA-RTI
  • a possible RNTI formula for PUSCH may be defined as the following:
  • RA-RNTI l+t_id+10*f_id+ 60* (SFN_id mod (Wmax/10) ) + 60 *40 (2400) ;
  • NB-IoT narrow band internet of thing
  • RA-RNTI 1 + floor (SFN_id/4) + 256*carrier_id + 256*256 (65536) ;
  • TDD time domain division
  • a dedicated PDCCH search space may be configured for the PUSCH transmission.
  • the different PDCCH search space may be used for PUCH of enhanced PUSCH.
  • FIG. 15 illustrates a flowchart of a communication method 1500 implemented at a terminal device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 1500 will be described from the perspective of the terminal device 110 in FIG. 1.
  • the terminal device receives, from a network device, a downlink message associated with early data transmission, wherein the downlink message associated with the early data transmission comprises at least one of: a backoff indication for the early data transmission, a subcarrier index for the early data transmission, an index of a parameter in code domain, a timing advance for the for the early data transmission, an identity of contention resolution, or a medium access control (MAC) service data unit (SDU) .
  • MAC medium access control
  • the terminal device receives data for the early data transmission based on the downlink message from the network device.
  • the downlink message comprises the backoff indication, the timing advance, the identity of contention resolution, and the MAC SDU, or the downlink message comprises the backoff indication, the index of the parameter in code domain, the timing advance, the identity of contention resolution, and a MAC protocol data unit (PDU) , or the downlink message comprises the backoff indication, the subcarrier index, the timing advance, the identity of contention resolution, and the MAC SDU.
  • PDU MAC protocol data unit
  • the backoff indication, the subcarrier index, the identity of contention resolution, the timing advance and the MAC SDU comprised in the downlink message are in sequence.
  • the backoff indication, the subcarrier index, a MAC control element (CE) comprising the identity of contention resolution and the timing advance, and the MAC SDU comprised in the downlink message are in sequence.
  • the backoff indication, the index of the parameter in code domain, the identity of contention resolution, the timing advance and the MAC SDU comprised in the downlink message are in sequence.
  • the backoff indication, the index of the parameter in code domain, a MAC CE comprising the identity of contention resolution and the timing advance, and the MAC SDU comprised in the downlink message are in sequence.
  • the backoff indication, a MAC CE comprising the identity of contention resolution, the timing advance and the index of the parameter in code domain, and the MAC SDU comprised in the downlink message are in sequence.
  • a MAC CE comprises the timing advance for the early data transmission and the identity of contention resolution.
  • the backoff indication is indicated by a MAC subheader
  • an order for MAC header is: the MAC subheader for the backoff indication, subheaders for all MAC CEs and subheaders for all MAC SDUs, all MAC CEs are placed after all MAC headers and before all MAC SDUs, and each MAC CE is associated with one MAC SDU.
  • the backoff indication is indicated by a first MAC subheader
  • the index of the parameter in code domain is indicated by a second MAC subheader
  • an order for MAC header is: the first MAC subheader for the backoff indication, the second MAC subheader for the index of the parameters in code domain, subheaders for all MAC CEs and subheaders for all MAC SDUs
  • all MAC CEs are placed after all MAC headers and before all MAC SDUs
  • each index of the parameter in code domain is associated with one identity of contention resolution, one timing advance and one MAC SDU.
  • the backoff indication is indicated by a first MAC subPDU, for each subcarrier index, one MAC subPDU is used for indicating the identity of the contention resolution, the timing advance and the corresponding MAC SDU.
  • the first MAC subPDU including the backoff indication is placed before a MAC subPDU including MAC CE or MAC SDU.
  • an order of MAC subPDUs including MAC CE or MAC SDU is a subheader of MAC CE and the MAC CE, and a subheader of MAC SDU and the MAC SDU.
  • all MAC subheaders are placed before all MAC CEs and MAC SDUs and all MAC CEs are placed before all MAC SDUs and after all MAC subheaders.
  • an order of MAC subheader is: a subheader of the backoff indication, a subheader of MAC CE and a subheader of MAC SDU.
  • an order of MAC subheader is: a subheader of the backoff indication, a subheader for the subcarrier index, a subheader of MAC CE and a subheader of MAC SDU.
  • an order of MAC subPDU is: a MAC subPDU for the backoff indication, a MAC subPDU for MAC CE, and a MAC subPDU for MAC SDU.
  • the MAC subPDU for MAC CE comprises a subheader for MAC CE and the MAC CE
  • the MAC subPDU for MAC SDU comprises a subheader for MAC SDU and the MAC SDU.
  • each MAC subPDU is associated with one or more MAC SDUs.
  • the index of the parameter in code domain is indicated in a radio network temporary identity, or the index of the parameter in code domain is indicated in a dedicated MAC CE, or the index of the parameter in code domain is indicated in a MAC subheader, or the index of the parameter in code domain is indicated by downlink control information.
  • FIG. 16 illustrates a flowchart of a communication method 1600 implemented at a terminal device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 1600 will be described from the perspective of the terminal device 110 in FIG. 1.
  • the terminal device receives, from a network device, a configuration for physical uplink shared channel (PUSCH) resource, wherein the configuration indicates a plurality of PUSCH resources, and each of the plurality of PUSCH resources is configured with an identity and one or more subcarriers.
  • PUSCH physical uplink shared channel
  • the terminal device determines a PUSCH resource from the plurality of PUSCH resources based on a capability of the terminal device and the configuration.
  • the method 1600 further includes selecting a coverage enhancement level based on a reference signal received power (RSRP) threshold and a measured RSRP value.
  • RSRP reference signal received power
  • the method 1600 further includes in response to the coverage enhancement level being selected, selecting a carrier based on a probability distribution.
  • the method 1600 further includes in response to the carrier being selected, selecting a PUSCH resource set in the carrier according to whether the terminal device supports multi-tone; in response to the terminal device supporting the multi-tone, selecting PUSCH resources according to the multi-tone; or in response to the terminal device not supporting the multi-tone, selecting PUSCH resources corresponding to a single tone.
  • the method 1600 further includes in response to a plurality of multi-tone PUSCH resources being configured, selecting a PUSCH resource.
  • the method 1600 further includes in response to that a plurality of indexes of a parameter in code domain being configured and a PUSCH resource being selected, selecting an index of the parameters in code domain within the PUSCH resource; or selecting the index of the parameters in code domain based on a probability value.
  • FIG. 17 illustrates a flowchart of a communication method 1700 implemented at a terminal device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 1700 will be described from the perspective of the terminal device 110 in FIG. 1.
  • the terminal device transmits, to a network device, data on a physical uplink shared channel (PUSCH) during an early data transmission procedure with a first power.
  • PUSCH physical uplink shared channel
  • the terminal device transmits the data to the network device with a second power, wherein the second power is higher than the first power.
  • the method 1700 further includes receiving, from the network device, information indicating a power ramping step; and determining the second power based on the first power and the power ramping step.
  • the power ramping step is configured by a system information block or radio resource control (RRC) message.
  • RRC radio resource control
  • a counter for transmission on the PUSCH is initiated as a predetermined number.
  • a contention resolution is not successful, in response to at least one of the following being met: a contention resolution timer expires, or a contention resolution identity included in a MAC CE does not match a portion of bits of a common control channel (CCCH) service data unit (SDU) transmitted.
  • CCCH common control channel
  • SDU service data unit
  • a counter for the PUSCH transmission is incremented by 1.
  • the second power is determined based on the first power and a value of the counter for the PUSCH transmission.
  • FIG. 18 illustrates a flowchart of a communication method 1800 implemented at a terminal device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 1800 will be described from the perspective of the terminal device 110 in FIG. 1.
  • the terminal device determines a target transmission type from a plurality of transmission types, wherein the plurality of transmission types comprise a first type of early data transmission, a second type of early data transmission and a preconfigured uplink resource (PUR) transmission type.
  • the plurality of transmission types comprise a first type of early data transmission, a second type of early data transmission and a preconfigured uplink resource (PUR) transmission type.
  • PUR preconfigured uplink resource
  • the terminal device transmits, to a network device, data based on the target transmission type.
  • the method 1800 further includes determining the target transmission type based on priority information of the plurality of transmission types.
  • the priority information is transmitted in a system information block or radio resource control message.
  • priorities of the plurality of transmission types in descending order are the PUR transmission type, the second type of early data transmission, and the first type of early data transmission.
  • priorities of the plurality of transmission types in descending order are the first type of early data transmission, the second type of early data transmission, and the PUR transmission type.
  • the method 1800 further includes: in response to a time gap between an initiation of a PUR transmission and a first available PUSCH occasion for initial PUR transmission is larger than a threshold, initiating the first type of early data transmission.
  • the method 1800 further includes: in response to a time gap between an initiation of a procedure of the second type of early data transmission and a first available PUSCH occasion for the procedure of the second type of early data transmission is larger than a threshold, initiating the first type of early data transmission.
  • the method 1800 further includes: in response to a time gap between an initiation of a PUR transmission and a first available PUSCH occasion for initial the PUR transmission is not larger than a threshold, initiating the PUR transmission.
  • the method 1800 further includes: in response to a time gap between an initiation of a procedure of the second type of early data transmission and a first available PUSCH occasion for the procedure of the second type of early data transmission is larger than a threshold, initiating the second type of early data transmission.
  • the PUR transmission has a higher priority than the second type of early data transmission.
  • FIG. 19 illustrates a flowchart of a communication method 1900 implemented at a terminal device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 1900 will be described from the perspective of the terminal device 110 in FIG. 1.
  • the terminal device determines that a radio network temporary identity is related to physical uplink shared channel (PUSCH) transmission based on one of:a radio network temporary identity space for the PUSCH transmission or a physical downlink control channel (PDCCH) search space for the PDSCH transmission.
  • PUSCH physical uplink shared channel
  • PDCCH physical downlink control channel
  • the radio network temporary identity space for the PUSCH transmission is based on a radio network temporary identity space of a random access procedure or an early data transmission and an offset.
  • a dedicated PDCCH search space is configured for the PUSCH transmission.
  • FIG. 20 illustrates a flowchart of a communication method 2000 implemented at a network device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 2000 will be described from the perspective of the network device 120 in FIG. 1.
  • the network device 120 transmits, to a terminal device, a downlink message associated with early data transmission, wherein the downlink message associated with the early data transmission comprises at least one of: a backoff indication for the early data transmission, a subcarrier index for the early data transmission, an index of a parameter in code domain, a timing advance for the for the early data transmission, an identity of contention resolution, or a medium access control (MAC) service data unit (SDU) .
  • MAC medium access control
  • the netwrok device 120 may perform the early data transmision. For example, the netwrok device 120 may transmit data for the early data transmision to the terminal device 110.
  • FIG. 21 illustrates a flowchart of a communication method 2100 implemented at a network device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 2100 will be described from the perspective of the network device 120 in FIG. 1.
  • the network device 120 transmits, to a terminal device, a configuration for physical uplink shared channel (PUSCH) resource, wherein the configuration indicates a plurality of PUSCH resources, and each of the plurality of PUSCH resources is configured with an identity and one or more subcarriers.
  • PUSCH physical uplink shared channel
  • FIG. 22 is a simplified block diagram of a device 2200 that is suitable for implementing embodiments of the present disclosure.
  • the device 2200 can be considered as a further example implementation of any of the devices as shown in FIG. 1. Accordingly, the device 2200 can be implemented at or as at least a part of the terminal device 110 or the network device 120.
  • the device 2200 includes a processor 2210, a memory 2220 coupled to the processor 2210, a suitable transceiver 2240 coupled to the processor 2210, and a communication interface coupled to the transceiver 2240.
  • the memory 2220 stores at least a part of a program 2230.
  • the transceiver 2240 may be for bidirectional communications or a unidirectional communication based on requirements.
  • the transceiver 2240 may include at least one of a transmitter 2242 and a receiver 2244.
  • the transmitter 2242 and the receiver 2244 may be functional modules or physical entities.
  • the transceiver 2240 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones.
  • the communication interface may represent any interface that is necessary for communication with other network elements, such as X2/Xn interface for bidirectional communications between eNBs/gNBs, S1/NG interface for communication between a Mobility Management Entity (MME) /Access and Mobility Management Function (AMF) /SGW/UPF and the eNB/gNB, Un interface for communication between the eNB/gNB and a relay node (RN) , or Uu interface for communication between the eNB/gNB and a terminal device.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • RN relay node
  • Uu interface for communication between the eNB/gNB and a terminal device.
  • the program 2230 is assumed to include program instructions that, when executed by the associated processor 2210, enable the device 2200 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGS. 1 to 21.
  • the embodiments herein may be implemented by computer software executable by the processor 2210 of the device 2200, or by hardware, or by a combination of software and hardware.
  • the processor 2210 may be configured to implement various embodiments of the present disclosure.
  • a combination of the processor 2210 and memory 2220 may form processing means 2250 adapted to implement various embodiments of the present disclosure.
  • the memory 2220 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 2220 is shown in the device 2200, there may be several physically distinct memory modules in the device 2200.
  • the processor 2210 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 2200 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.
  • a terminal device comprising a circuitry.
  • the circuitry is configured to: receive, from a network device, a downlink message associated with early data transmission, wherein the downlink message associated with the early data transmission comprises at least one of: a backoff indication for the early data transmission, a subcarrier index for the early data transmission, an index of a parameter in code domain, a timing advance for the for the early data transmission, an identity of contention resolution, or a medium access control (MAC) service data unit (SDU) .
  • the circuitry may be configured to perform any method implemented by the terminal device as discussed above.
  • a terminal device comprising a circuitry.
  • the circuitry is configured to: receive, from a network device, a configuration for physical uplink shared channel (PUSCH) resource, wherein the configuration indicates a plurality of PUSCH resources, and each of the plurality of PUSCH resources is configured with an identity and one or more subcarriers; and determine a PUSCH resource from the plurality of PUSCH resources based on a capability of the terminal device and the configuration.
  • the circuitry may be configured to perform any method implemented by the terminal device as discussed above.
  • a terminal device comprising a circuitry.
  • the circuitry is configured to: transmit, to a network device, data on a physical uplink shared channel (PUSCH) during an early data transmission procedure with a first power; and in response to the transmission of the data on the PUSCH being failed, transmit the data to the network device with a second power, wherein the second power is higher than the first power.
  • the circuitry may be configured to perform any method implemented by the terminal device as discussed above.
  • a terminal device comprising a circuitry.
  • the circuitry is configured to: determine a target transmission type from a plurality of transmission types, wherein the plurality of transmission types comprise a first type of early data transmission, a second type of early data transmission and a preconfigured uplink resource (PUR) transmission type; and transmit, to a network device, data based on the target transmission type.
  • the circuitry may be configured to perform any method implemented by the terminal device as discussed above.
  • a terminal device comprising a circuitry.
  • the circuitry is configured to: determine that a radio network temporary identity is related to physical uplink shared channel (PUSCH) transmission based on one of: a radio network temporary identity space for the PUSCH transmission or a physical downlink control channel (PDCCH) search space for the PDCCH transmission.
  • PUSCH physical uplink shared channel
  • PDCCH physical downlink control channel
  • the circuitry may be configured to perform any method implemented by the terminal device as discussed above.
  • a network device comprising a circuitry.
  • the circuitry is configured to: transmit, to a terminal device, a downlink message associated with early data transmission, wherein the downlink message associated with the early data transmission comprises at least one of: a backoff indication for the early data transmission, a subcarrier index for the early data transmission, an index of a parameter in code domain, a timing advance for the for the early data transmission, an identity of contention resolution, or a medium access control (MAC) service data unit (SDU) .
  • the circuitry may be configured to perform any method implemented by the network device as discussed above.
  • a network device comprising a circuitry.
  • the circuitry is configured to: transmit, to a terminal device, a configuration for physical uplink shared channel (PUSCH) resource, wherein the configuration indicates a plurality of PUSCH resources, and each of the plurality of PUSCH resources is configured with an identity and one or more subcarriers.
  • PUSCH physical uplink shared channel
  • the circuitry may be configured to perform any method implemented by the terminal device as discussed above.
  • circuitry used herein may refer to hardware circuits and/or combinations of hardware circuits and software.
  • the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware.
  • the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions.
  • the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not ne eded for operation.
  • the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.
  • a terminal device comprises means for receiving, from a network device, a downlink message associated with early data transmission, wherein the downlink message associated with the early data transmission comprises at least one of: a backoff indication for the early data transmission, a subcarrier index for the early data transmission, an index of a parameter in code domain, a timing advance for the for the early data transmission, an identity of contention resolution, or a medium access control (MAC) service data unit (SDU) .
  • the terminal device may comprise means for performing the respective operations of the method 1500.
  • the terminal device may further comprise means for performing other operations in some example embodiments of the method 1500.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • a terminal device comprises means for receiving, from a network device, a configuration for physical uplink shared channel (PUSCH) resource, wherein the configuration indicates a plurality of PUSCH resources, and each of the plurality of PUSCH resources is configured with an identity and one or more subcarriers; and means for determining a PUSCH resource from the plurality of PUSCH resources based on a capability of the terminal device and the configuration.
  • the terminal device s may comprise means for performing the respective operations of the method 1600.
  • the terminal device may further comprise means for performing other operations in some example embodiments of the method 1600.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • a terminal device comprises means for transmitting, to a network device, data on a physical uplink shared channel (PUSCH) during an early datat transmission procedure with a first power; and means for in response to the transmission of the data on the PUSCH being failed, transmitting the data to the network device with a second power, wherein the second power is higher than the first power.
  • the terminal device may comprise means for performing the respective operations of the method 1700.
  • the terminal device may further comprise means for performing other operations in some example embodiments of the method 1700.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • a terminal device comprises means for determining a target transmission type from a plurality of transmission types, wherein the plurality of transmission types comprise a first type of early data transmission, a second type of early data transmission and a preconfigured uplink resource (PUR) transmission type; and means for transmitting, to a network device, data based on the target transmission type.
  • the terminal device may comprise means for performing the respective operations of the method 1800.
  • the terminal device may further comprise means for performing other operations in some example embodiments of the method 1800.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • a terminal device comprises means for determining that a radio network temporary identity is related to physical uplink shared channel (PUSCH) transmission based on one of: a radio network temporary identity space for the PUSCH transmission or a physical downlink control channel (PDCCH) search space for the PDCCH transmission.
  • PUSCH physical uplink shared channel
  • PDCCH physical downlink control channel
  • the terminal device may comprise means for performing the respective operations of the method 1900.
  • the terminal device may further comprise means for performing other operations in some example embodiments of the method 1900.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • a network device comprises means for transmitting, to a terminal device, a downlink message associated with early data transmission, wherein the downlink message associated with the early data transmission comprises at least one of: a backoff indication for the early data transmission, a subcarrier index for the early data transmission, an index of a parameter in code domain, a timing advance for the for the early data transmission, an identity of contention resolution, or a medium access control (MAC) service data unit (SDU) .
  • the network device may comprise means for performing the respective operations of the method 2000.
  • the network device may further comprise means for performing other operations in some example embodiments of the method 2000.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • a network device comprises means for transmitting, to a terminal device, a configuration for physical uplink shared channel (PUSCH) resource, wherein the configuration indicates a plurality of PUSCH resources, and each of the plurality of PUSCH resources is configured with an identity and one or more subcarriers.
  • the network device may comprise means for performing the respective operations of the method 2100.
  • the network device may further comprise means for performing other operations in some example embodiments of the method 2100.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • embodiments of the present disclosure provide the following aspects.
  • a terminal device comprising: a processor, configured to cause the terminal device to: receive, from a network device, a downlink message associated with early data transmission, wherein the downlink message associated with the early data transmission comprises at least one off a backoff indication for the early data transmission, a subcarrier index for the early data transmission, an index of a parameter in code domain, a timing advance for the for the early data transmission, an identity of contention resolution, or a medium access control (MAC) service data unit (SDU) .
  • MAC medium access control
  • the downlink message comprises the backoff indication, the timing advance, the identity of contention resolution, and the MAC SDU, or wherein the downlink message comprises the backoff indication, the index of the parameter in code domain, the timing advance, the identity of contention resolution, and a MAC protocol data unit (PDU) , or wherein the downlink message comprises the backoff indication, the subcarrier index, the timing advance, the identity of contention resolution, and the MAC SDU.
  • PDU MAC protocol data unit
  • the backoff indication, the subcarrier index, the identity of contention resolution, the timing advance and the MAC SDU comprised in the downlink message are in sequence.
  • the backoff indication, the subcarrier index, a MAC control element (CE) comprising the identity of contention resolution and the timing advance, and the MAC SDU comprised in the downlink message are in sequence.
  • the backoffindication, the index of the parameter in code domain, the identity of contention resolution, the timing advance and the MAC SDU comprised in the downlink message are in sequence.
  • the backoffindication, the index of the parameter in code domain, a MAC CE comprising the identity of contention resolution and the timing advance, and the MAC SDU comprised in the downlink message are in sequence.
  • the backoffindication, a MAC CE comprising the identity of contention resolution, the timing advance and the index of the parameter in code domain, and the MAC SDU comprised in the downlink message are in sequence.
  • a dedicated MAC CE is used to indicate the timing advance for the early data transmission.
  • a MAC CE comprises the timing advance for the early data transmission and the identity of contention resolution.
  • the backoff indication is indicated by a MAC subheader
  • an order for MAC header is: the MAC subheader for the backoff indication, subheaders for all MAC CEs and subheaders for all MAC SDUs, all MAC CEs are placed after all MAC headers and before all MAC SDUs, and each MAC CE is associated with one MAC SDU.
  • the backoff indication is indicated by a first MAC subheader
  • the index of the parameter in code domain is indicated by a second MAC subheader
  • an order for MAC header is: the first MAC subheader for the backoffindication, the second MAC subheader for the index of the parameters in code domain, subheaders for all MAC CEs and subheaders for all MAC SDUs
  • all MAC CEs are placed after all MAC headers and before all MAC SDUs
  • each index of the parameter in code domain is associated with one identity of contention resolution, one timing advance and one MAC SDU.
  • the backoff indication is indicated by a first MAC subPDU, for each subcarrier index, one MAC subPDU is used for indicating the identity of the contention resolution, the timing advance and the corresponding MAC SDU.
  • the first MAC subPDU including the backoff indication is placed before a MAC subPDU including MAC CE or MAC SDU.
  • an order of MAC subPDUs including MAC CE or MAC SDU is a subheader of MAC CE and the MAC CE, and a subheader of MAC SDU and the MAC SDU.
  • all MAC subheaders are placed before all MAC CEs and MAC SDUs and all MAC CEs are placed before all MAC SDUs and after all MAC subheaders.
  • an order of MAC subheader is: a subheader of the backoff indication, a subheader of MAC CE and a subheader of MAC SDU.
  • an order of MAC subheader is: a subheader of the backoff indication, a subheader for the subcarrier index, a subheader of MAC CE and a subheader of MAC SDU.
  • an order of MAC subPDU is: a MAC subPDU for the backoff indication, a MAC subPDU for MAC CE, and a MAC subPDU for MAC SDU.
  • the MAC subPDU for MAC CE comprises a subheader for MAC CE and the MAC CE
  • the MAC subPDU for MAC SDU comprises a subheader for MAC SDU and the MAC SDU.
  • each MAC subPDU is associated with one or more MAC SDUs.
  • the index of the parameter in code domain is indicated in a radio network temporary identity, or wherein the index of the parameter in code domain is indicated in a dedicated MAC CE, or wherein the index of the parameter in code domain is indicated in a MAC subheader, or wherein the index of the parameter in code domain is indicated by downlink control information.
  • a terminal device comprising: a processor, configured to cause the terminal device to: receive, from a network device, a configuration for physical uplink shared channel (PUSCH) resource, wherein the configuration indicates a plurality of PUSCH resources, and each of the plurality of PUSCH resources is configured with an identity and one or more subcarriers; and determine a PUSCH resource from the plurality of PUSCH resources based on a capability of the terminal device and the configuration.
  • PUSCH physical uplink shared channel
  • the terminal device is caused to: select a coverage enhancement level based on a reference signal received power (RSRP) threshold and a measured RSRP value.
  • RSRP reference signal received power
  • the terminal device is caused to: in response to the coverage enhancement level being selected, select a carrier based on a probability distribution.
  • the terminal device is caused to: in response to the carrier being selected, select a PUSCH resource set in the carrier according to whether the terminal device supports multi-tone; in response to the terminal device supporting the multi-tone, select PUSCH resources according to the multi-tone; or in response to the terminal device not supporting the multi-tone, select PUSCH resources corresponding to a single tone.
  • the terminal device is caused to: in response to a plurality of multi-tone PUSCH resources being configured, select a PUSCH resource.
  • the terminal device is caused to: in response to that a plurality of indexes of a parameter in code domain being configured and a PUSCH resource being selected, select an index of the parameters in code domain within the PUSCH resource; or select the index of the parameters in code domain based on a probability value.
  • a terminal device comprising: a processor, configured to cause the terminal device to: transmit, to a network device, data on a physical uplink shared channel (PUSCH) during an early data transmission procedure with a first power; and in response to the transmission of the data on the PUSCH being failed, transmit the data to the network device with a second power, wherein the second power is higher than the first power.
  • PUSCH physical uplink shared channel
  • the terminal device is caused to: receive, from the network device, information indicating a power ramping step; and determine the second power based on the first power and the power ramping step.
  • the power ramping step is configured by a system information block or radio resource control (RRC) message.
  • RRC radio resource control
  • a counter for transmission on the PUSCH is initiated as a predetermined number.
  • a contention resolution is not successful, in response to at least one of the following being met: a contention resolution timer expires, or a contention resolution identity included in a MAC CE does not match a portion of bits of a common control channel (CCCH) service data unit (SDU) transmitted.
  • CCCH common control channel
  • SDU service data unit
  • a counter for the PUSCH transmission is incremented by 1.
  • the second power is determined based on the first power and a value of the counter for the PUSCH transmission.
  • a terminal device comprising: a processor, configured to cause the terminal device to: determine a target transmission type from a plurality of transmission types, wherein the plurality of transmission types comprise a first type of early data transmission, a second type of early data transmission and a preconfigured uplink resource (PUR) transmission type; and transmit, to a network device, data based on the target transmission type.
  • a processor configured to cause the terminal device to: determine a target transmission type from a plurality of transmission types, wherein the plurality of transmission types comprise a first type of early data transmission, a second type of early data transmission and a preconfigured uplink resource (PUR) transmission type; and transmit, to a network device, data based on the target transmission type.
  • PUR preconfigured uplink resource
  • the terminal device is caused to: determine the target transmission type based on priority information of the plurality of transmission types.
  • the priority information is transmitted in a system information block or radio resource control message.
  • priorities of the plurality of transmission types in descending order are the PUR transmission type, the second type of early data transmission, and the first type of early data transmission.
  • priorities of the plurality of transmission types in descending order are the first type of early data transmission, the second type of early data transmission, and the PUR transmission type.
  • the terminal device is caused to: in response to a time gap between an initiation of a PUR transmission and a first available PUSCH occasion for initial PUR transmission is larger than a threshold, initiate the first type of early data transmission.
  • the terminal device is caused to: in response to a time gap between an initiation of a procedure of the second type of early data transmission and a first available PUSCH occasion for the procedure of the second type of early data transmission is larger than a threshold, initiate the first type of early data transmission.
  • the terminal device is caused to: in response to a time gap between an initiation of a PUR transmission and a first available PUSCH occasion for initial the PUR transmission is not larger than a threshold, initiate the PUR transmission.
  • the terminal device is caused to: in response to a time gap between an initiation of a procedure of the second type of early data transmission and a first available PUSCH occasion for the procedure of the second type of early data transmission is larger than a threshold, initiate the second type of early data transmission.
  • the PUR transmission has a higher priority than the second type of early data transmission.
  • a terminal device comprising: a processor, configured to cause the terminal device to: determine that a radio network temporary identity is related to physical uplink shared channel (PUSCH) transmission based on one of:a radio network temporary identity space for the PUSCH transmission or a physical downlink control channel (PDCCH) search space for the PDSCH transmission.
  • PUSCH physical uplink shared channel
  • PDCCH physical downlink control channel
  • the radio network temporary identity space for the PUSCH transmission is based on a radio network temporary identity space of a random access procedure or an early data transmission and an offset.
  • a dedicated PDCCH search space is configured for the PUSCH transmission.
  • a network device comprising: a processor, configured to cause the network device to: transmit, to a terminal device, a downlink message associated with early data transmission, wherein the downlink message associated with the early data transmission comprises at least one of: a backoff indication for the early data transmission, a subcarrier index for the early data transmission, an index of a parameter in code domain, a timing advance for the for the early data transmission, an identity of contention resolution, or a medium access control (MAC) service data unit (SDU) .
  • MAC medium access control
  • a network device comprising: a processor, configured to cause the terminal device to: transmit, to a terminal device, a configuration for physical uplink shared channel (PUSCH) resource, wherein the configuration indicates a plurality of PUSCH resources, and each of the plurality of PUSCH resources is configured with an identity and one or more subcarriers.
  • PUSCH physical uplink shared channel
  • a terminal device comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the device to perform the method implemented by the terminal device discussed above.
  • a network device comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the device to perform the method implemented by the network device discussed above.
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the terminal device discussed above.
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the network device discussed above.
  • a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the terminal device discussed above.
  • a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the network device discussed above.
  • 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 representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods 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 process or method as described above with reference to FIGS. 1 to 22.
  • 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 above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • the machine readable medium may be a machine readable signal medium or a machine readable storage medium.
  • a machine 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.
  • machine readable storage medium More specific examples of the machine 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.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM portable compact disc read-only memory
  • magnetic storage device or any suitable combination of the foregoing.

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 une solution pour une EDT améliorée. Dans une solution, un dispositif terminal reçoit, en provenance d'un dispositif de réseau, un message de liaison descendante associé à une transmission de données précoce, le message de liaison descendante associé à la transmission de données précoce comprenant : une indication de réduction de puissance pour la transmission de données précoce, et/ou un indice de sous-porteuse pour la transmission de données précoce, et/ou un indice d'un paramètre dans le domaine de code, et/ou une avance temporelle pour la transmission de données précoce, et/ou une identité de résolution de contention, et/ou une unité de données de service (SDU) de contrôle d'accès au support (MAC).
PCT/CN2024/092103 2024-05-09 2024-05-09 Dispositifs et procédés de communication Pending WO2025231772A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/092103 WO2025231772A1 (fr) 2024-05-09 2024-05-09 Dispositifs et procédés de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/092103 WO2025231772A1 (fr) 2024-05-09 2024-05-09 Dispositifs et procédés de communication

Publications (1)

Publication Number Publication Date
WO2025231772A1 true WO2025231772A1 (fr) 2025-11-13

Family

ID=97674206

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/092103 Pending WO2025231772A1 (fr) 2024-05-09 2024-05-09 Dispositifs et procédés de communication

Country Status (1)

Country Link
WO (1) WO2025231772A1 (fr)

Similar Documents

Publication Publication Date Title
US20250142425A1 (en) Method, device and computer storage medium of communication
WO2023178624A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024192688A1 (fr) Dispositif, procédé et support lisible par ordinateur pour communication
WO2023201490A1 (fr) Procédé, dispositif et support de stockage informatique destinés à la communication
WO2025231772A1 (fr) Dispositifs et procédés de communication
WO2023184273A1 (fr) Procédé, dispositif, et support de stockage informatique destinés à la communication
US20250350981A1 (en) Method, device and computer storage medium of communication
WO2025020196A1 (fr) Dispositifs et procédés de communication
WO2025217821A1 (fr) Dispositifs et procédés de transmission en sub-band full duplex
WO2025213424A1 (fr) Dispositif, procédé et support lisible par ordinateur pour les communications
WO2025091275A1 (fr) Dispositifs et procédés de communication
WO2024168570A1 (fr) Dispositifs et procédés de communication
WO2024130677A1 (fr) Dispositif et procédé de communication
WO2023168603A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2025059945A1 (fr) Dispositifs et procédés de communication
WO2023178694A1 (fr) Procédé, dispositif et support lisible par ordinateur destinés aux communications
WO2025091402A1 (fr) Dispositifs et procédés de communication
WO2023240484A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2025199695A1 (fr) Dispositifs et procédés de communication
WO2025160991A1 (fr) Dispositifs et procédés de transmission de nprach
WO2025199686A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications
WO2025194468A1 (fr) Dispositifs et procédés de communication
WO2023141941A1 (fr) Procédés, dispositifs et support lisible par ordinateur pour des communications
WO2024138395A1 (fr) Dispositif et procédé de communication
WO2025030289A1 (fr) Dispositifs et procédés de communication