[go: up one dir, main page]

WO2025118281A1 - Dispositif, procédé et support lisible par ordinateur pour des communications - Google Patents

Dispositif, procédé et support lisible par ordinateur pour des communications Download PDF

Info

Publication number
WO2025118281A1
WO2025118281A1 PCT/CN2023/137536 CN2023137536W WO2025118281A1 WO 2025118281 A1 WO2025118281 A1 WO 2025118281A1 CN 2023137536 W CN2023137536 W CN 2023137536W WO 2025118281 A1 WO2025118281 A1 WO 2025118281A1
Authority
WO
WIPO (PCT)
Prior art keywords
sbfd
pos
terminal device
time unit
pbch blocks
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/CN2023/137536
Other languages
English (en)
Inventor
Xincai LI
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/CN2023/137536 priority Critical patent/WO2025118281A1/fr
Publication of WO2025118281A1 publication Critical patent/WO2025118281A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/115—Grant-free or autonomous transmission
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/14—Two-way operation using the same type of signal, i.e. duplex
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows

Definitions

  • Embodiments of the present disclosure generally relate to the field of communication, and in particular, to devices, methods and computer readable medium for transmission enhancement.
  • a time unit (for example, a symbol, slot, sub-frame, frame, and so on) can be divided into a plurality of frequency subbands in the frequency domain.
  • the plurality of frequency subbands may be respectively used for different link directions, for example, uplink (UL) or downlink (DL) .
  • This time unit may be also referred to as subband non-overlapping full duplex (SBFD) time unit.
  • SBFD subband non-overlapping full duplex
  • a device for communication for example, a network device or a terminal device
  • devices for example, the Internet of Things, IoT, devices and so on
  • IoT Internet of Things
  • devices may communicate only rarely, send small amounts of data, and then stay quiet.
  • the payload data from an IoT device can be relatively small compared to the control signaling required to send the payload data over the radio interface, making a connection for the small data transmission becomes a concern for both the network and the device due to the control signaling overhead.
  • SDT small data transmission
  • the SDT is a procedure which allows data and/or signaling transmission while the device remains in inactive state without transitioning to connected state.
  • the SDT may be enhanced with respect to the SBFD time unit.
  • example embodiments of the present disclosure relate to devices, methods, and computer readable medium for transmission enhancement.
  • a terminal device comprising a processor.
  • the processor is configured to cause the terminal device to determine whether a physical uplink shared channel (PUSCH) occasion (PO) on a subband non-overlapping full duplex (SBFD) time unit is valid.
  • the SBFD time unit is configured with frequency subbands for different link directions.
  • the terminal device is further caused to transmit, in the PO and to a network device, an uplink transmission based on determining that the PO is valid.
  • a network device comprising a processor.
  • the processor is configured to cause the network device to determine whether a physical uplink shared channel (PUSCH) occasion (PO) on a subband non-overlapping full duplex (SBFD) time unit is valid.
  • the SBFD time unit is configured with frequency subbands for different link directions.
  • the network device is further caused to receive, in the PO and from a terminal device, an uplink transmission based on determining that the PO is valid.
  • a method implemented at a terminal device determines whether a physical uplink shared channel (PUSCH) occasion (PO) on a subband non-overlapping full duplex (SBFD) time unit is valid.
  • the SBFD time unit is configured with frequency subbands for different link directions. Based on determining that the PO is valid, the terminal device further transmits, in the PO, an uplink transmission to a network device.
  • PUSCH physical uplink shared channel
  • SBFD subband non-overlapping full duplex
  • a method implemented at a network device determines whether a physical uplink shared channel (PUSCH) occasion (PO) on a subband non-overlapping full duplex (SBFD) time unit is valid.
  • the SBFD time unit is configured with frequency subbands for different link directions. Based on determining that the PO is valid, the network device further receives, in the PO, an uplink transmission from a terminal device.
  • PUSCH physical uplink shared channel
  • SBFD subband non-overlapping full duplex
  • 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 of any of the third aspect to the fourth aspect.
  • Fig. 1 illustrates an example environment in which some embodiments of the present disclosure can be implemented
  • Fig. 2 illustrates an example signaling process for transmission enhancement related according to some embodiments of the present disclosure
  • Figs. 3a to 3b illustrate examples of the determination of valid POs or invalid POs according to some embodiments of the present disclosure
  • Fig. 4 illustrates example POs configured on the SBFD time units according to some embodiments of the present disclosure
  • Fig. 5 illustrates example additional parameters for indicating POs on SBFD time units according to some embodiments of the present disclosure
  • Fig. 6a to 6f illustrate examples of the mapping relationships between the POs and the SSBs according to some embodiments of the present disclosure
  • Fig. 7a to Fig. 7b illustrate examples of SDT retransmissions on SBFD time units according to some embodiments of the present disclosure
  • Fig. 8 illustrates a flowchart of an example method implemented at a terminal device according to some embodiments of the present disclosure
  • Fig. 9 illustrates a flowchart of an example method implemented at a network device according to some embodiments of the present disclosure
  • Fig. 10 illustrates a simplified block diagram of a device 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, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Small Data Transmission (SDT) , mobility, Multicast and Broadcast Services (MBS) , positioning, dynamic/flexible duplex in commercial networks, reduced capability (RedCap) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eX
  • 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 be also incorporated 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, a wireless device or a reduced capability terminal device.
  • the term “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) , Network-controlled Repeaters, 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
  • 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.
  • the terminal or the network device may work on several frequency ranges, e.g. FR1 (410 MHz –7125 MHz) , FR2 (24.25 GHz to 71 GHz) , 71 GHz to 114 GHz, and frequency band larger than 100 GHz as well as Tera Hertz (THz) . It can further work on licensed/unlicensed/shared spectrum.
  • 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 network device may have the function of network energy saving, Self-Organizing Networks (SON) /Minimization of Drive Tests (MDT) .
  • the terminal may have the function of power saving.
  • 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 and 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.
  • 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 needed for operation.
  • 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.
  • the subband and the frequency subband may be used interchangeable without any limitation.
  • the group size of a RBG may be also referred to as the RBG size without any limitation.
  • the control channel may be interchangeably used with the physical downlink control channel (PDCCH) without any limitation.
  • PDCCH physical downlink control channel
  • the slot/symbol configured with SBFD communication or configuration may be also referred to as SBFD slot/symbol, and the slot/symbol not configured with SBFD communication may be also referred to as non-SBFD slot/symbol.
  • the non-SBFD time unit may comprise UL slot/symbol and/or DL slot/symbol.
  • resource Physical Resource Block (PRB) or resource block” used herein may refer to a resource base unit in the frequency domain.
  • PRB Physical Resource Block
  • SBFD aware UE used herein may refer to the terminal device which obtains the SBFD configuration for time units, for example, the subband division or location of the time units, and supports the SBFD operations with the network device.
  • frequency subband and “subband” can be used interchangeably without any limitation.
  • the frequency subband configured for the uplink communication in the SBFD time unit may be also referred to be as “uplink (UL) subband” .
  • the frequency subband configured for the downlink communication in the SBFD time unit may be also referred to be as “downlink (DL) subband” .
  • the time unit may be any metric of the time domain.
  • the time unit may be a frame, a subframe, a slot, or a symbol.
  • the time unit may be any other time duration.
  • the expression “frequency resources within a subband of the SBFD time unit” only refers that the resources are located within the subband with respect to the frequency domain, however, the time duration of the resources is unnecessary to be limited in the SBFD time unit.
  • the time domain resource allocation (TDRA) list may indicate symbols for the downlink shared channel reception in at least one slot.
  • TDRA list and “TDRA table” can be interchangeably used in this disclosure.
  • frequency domain resource allocation used herein may refer to a frequency resource configuration information which indicates frequency resources that are allocated to the terminal device or data/control channel.
  • downlink (DL) shared channel and “physical downlink shared channel (PDSCH) ” can be used interchangeably.
  • uplink (UL) control channel” and “physical uplink shared channel (PUSCH) ” can be used interchangeably.
  • synchronization signal (SS) /physical broadcast channel (PBCH) block may be also referred to as “SSB” .
  • the SDT may be enhanced with respect to the SBFD time unit.
  • the terminal device only can transmit the SDT on an uplink (UL) time unit.
  • UL uplink
  • a downlink (DL) time unit or a flexible time unit may be configured as an SBFD time unit. That is, there may be further UL resources configured in the SBFD time units compared to the resources only configured in the UL time units.
  • a terminal device determines whether a physical uplink shared channel (PUSCH) occasion (PO) on a subband non-overlapping full duplex (SBFD) time unit is valid.
  • the SBFD time unit is configured with frequency subbands for different link directions. Based on determining that the PO is valid, the terminal device further transmits, in the PO, an uplink transmission to a network device.
  • PUSCH physical uplink shared channel
  • SBFD subband non-overlapping full duplex
  • the SDT can be transmitted on POs that are configured on the SBFD time unit.
  • using SBFD symbols to transmit SDT can provide more UL resources to increase the SDT PUSCH transmission reliability and to reduce the SDT latency.
  • Fig. 1 illustrates an example environment 100 in which example embodiments of the present disclosure can be implemented.
  • the environment 100 which may be a part of a communication network, comprises a terminal device 110, a network device 120.
  • the communication network may include NTN, NB-IoT and/or eMTC.
  • the communication network may include any other possible communication network. It is to be understood that the number of network devices and terminal devices is given only for the purpose of illustration without suggesting any limitations.
  • the communication network may include any suitable number of network devices and/or terminal devices adapted for implementing embodiments of the present disclosure. Although not shown, it would be appreciated that one or more terminal devices may be located in the environment 100. Without any limitation, the network device 120 supports the SBFD communication.
  • the network device 120 m ay transmit downlink (DL) channel to the terminal device 110 and receive UL channel from another terminal device 130 in the SBFD time unit, simultaneously.
  • the non-SBFD time unit may be UL only time unit or DL only time unit.
  • Fig. 1 the number of units and other objects in Fig. 1 is provided merely for the purpose of illustration without implying any limitations to the device environment 100.
  • the device environment 100 may include any suitable number of functionality units configured to implement example embodiments of the subject disclosure.
  • one or more terminal devices may be located in the device environment 100.
  • Fig. 2 illustrates an example signaling process 200 for transmission enhancement according to some embodiments of the present disclosure.
  • the process 200 will be described with reference to Fig. 1.
  • the SDT may include random access SDT and configured grant (CG) SDT.
  • CG SDT on SBFD symbols at least the following aspects may be considered: the determination of the valid of the POs on SBFD symbols, the manner of configuring or determining the SDT CG PUSCH resource on SBFD symbols, and the mapping relationship between synchronization signal (SS) /physical broadcast channel (PBCH) blocks and the POs on SBFD symbols.
  • SS synchronization signal
  • PBCH physical broadcast channel
  • the terminal device 110 may determine that the POs configured on the SBFD time unit are valid. Otherwise, if the second set of resources is not completely within the uplink subband of the SBFD time units, the terminal device 110 may determine that the POs configured on the SBFD time unis are invalid.
  • the determination of valid of POs relates to physical random access channel (PRACH) occasions.
  • PRACH physical random access channel
  • the terminal device 110 may determine these POs as valid. If the second set of resources is not completely within the uplink subband and/or the second set of resources overlaps with the valid PRACH occasion, the terminal device 110 may determine these POs configured on the SBFD time units as invalid. In this case, the POs configured on the time units other than the UL time units may be also determined as valid. Only for discussion clarity, the determination of valid POs is further discussed with reference to Figs. 3a and 3b.
  • Figs. 3a to 3b illustrate examples of the determination of valid POs or invalid POs according to some embodiments of the present disclosure.
  • the terminal devices can consider the PUSCH occasion overlapping (or colliding) with DL symbols that are configured with UL subband for SBFD operation as valid if the configured PUSCH resource is within the UL subband of the SBFD symbols.
  • SIB1 system information block 1
  • the terminal devices receive the system information block 1 (SIB1) signaling that configures the UL subband location in frequency and time domain on the DL symbols or flexible symbols, then the PO on these DL or flexible symbols may be considered as valid. Otherwise, it is considered as invalid. That is, the POs on the DL time unit 310 configured with UL subband may be considered as valid.
  • the POs on the flexible time unit 320 configured with UL subband may be considered as valid.
  • the above embodiments may be also expressed as below.
  • a configured grant (CG) configuration is common to SBFD time units and non-SBFD time units.
  • CG configured grant
  • the PO may be considered as invalid.
  • the terminal device 110 may not transmit SDT on the PO overlapped with DL subband/guardband. That is, if the frequency resources allocated to the PO exceed the UL subband bandwidth edge on the SBFD symbols, then these POs are invalid.
  • the frequency resources of the PO do not overlap with a valid PRACH occasion in the SBFD time units, the PO may be considered as valid.
  • a PUSCH occasion may be valid if the PUSCH occasion does not precede an SS/PBCH block in the PUSCH slot or SBFD slot, and starts at least N_ “gap” symbols after a last SS/PBCH block symbol, where N_ “gap” is provided in the following Table 1.
  • the above embodiments relate to the determination of the valid of POs on the SBFD time units.
  • the resource allocation of the POs on the time units including the SBFD time units and the non-SBFD time units may be also improved.
  • the network device 120 may transmit (201) a configured grant (CG) configuration 203 for POs to the terminal device 110.
  • the terminal device 110 may receive (205) the CG configuration 203 accordingly.
  • the CG configuration 203 may indicate the resources allocated to the POs on the SBFD time units and the non-SBFD time units.
  • the terminal device 110 may use these POs and associated DMRS resources on the SBFD time units to perform the SDT (including the initial and retransmission SDT) .
  • each PO is associated with an index of a SS/PBCH block.
  • the SS/PBCH block associated with the PUSCH transmission is quasi-colocation (QCL) with respect to the average gain and the QCL 'typeA' or 'typeD' properties. Only for discussion purposes, the above embodiments are further discussed with reference to Fig. 4.
  • Fig. 4 illustrates example POs configured on the SBFD time units according to some embodiments of the present disclosure.
  • the configured PO resources are within the UL subband of the SBFD slots (#N and #N+P) .
  • the terminal device 110 may transmit SDT PUSCH#1 405 in SBFD slot N, and transmit SDT PUSCH#2 407 in SBFD slot # (N+P) .
  • SSB#1 401 may be associated with SDT PUSCH#1 405 and SSB#2 403 may be associated with SDT PUSCH#2 407.
  • the CG configuration may comprise a common resource configuration indicating the resources allocated to the PO on the SBFD time unit and a non-SBFD time unit.
  • the POs configured on the SBFD time units and non-SBFD time units may be allocated with the same frequency resources. Then, as mentioned above, the terminal device 110 may determine whether the POs are valid based on the frequency position of the frequency resources, as mentioned above.
  • the CG configuration may further comprise at least one additional parameter for indicating the POs on the SBFD time units.
  • the CG configuration may further comprise additional parameters dedicated to the POs on the SBFD time units.
  • the terminal device 110 may determine the POs on the SBFD time unit using the common resource configuration.
  • the POs on the SBFD time unit may be the same as the further POs on the non-SBFD time unit in the frequency domain.
  • the terminal device 110 may determine the POs on the SBFD time unit using both the common resource configuration and the additional parameters. With the additional parameters, the resources allocated to the POs on the SBFD time units may be adjusted into the UL subband of the SBFD time units. In this case, the POs on the SBFD time units may be adjusted to be valid in advance.
  • a common CG configuration for SBFD slot and non- SBFD slot is determined for a terminal device, and additional configurations/parameters may be added in ConfiguredGrantConfig IE for PO or PUSCH transmission determination on SBFD time units.
  • ConfiguredGrantConfig IE for PO or PUSCH transmission determination on SBFD time units.
  • the above additional parameters may include at least one offset value relative to the parameters of the common resource configuration.
  • some offset values such as frequency offset, time offset, and MCS offset relative to the CG PUSCH configuration on non-SBFD symbols can be predefined or configured or indicated for SDT POs on the SBFD symbols.
  • the terminal device 110 may determine the CG resources allocated to POs on the SBFD time units based on the configured value (for example, the common resource configuration) for non-SBFD symbols and these predefined or configured offset values.
  • a MCS offset value may be predefined or configured for SDT PO (or SDT PUSCH) , this MCS offset may be used by the terminal device 110 to determine the MCS of the SDT PUSCH transmitted on the SBFD time units.
  • the MCS value offset may be relative to the MCS of latest transmitted PUSCH on the non-SBFD symbols. In this way, the inter/intra-subband cross link interference (CLI) may be reduced. If the MCS of the latest transmitted PUSCH (as show by block 401) on non-SBFD symbols is M, and the predefined or configured MCS offset value is N, then the MCS for PUSCH transmitted on the SBFD symbols may be M-N. Only for discussion clarity, the offset values are further discussed with reference to Fig. 5.
  • Fig. 5 illustrates example additional parameters for indicating POs on SBFD time units according to some embodiments of the present disclosure.
  • the level of the MCS for the latest transmitted PUSCH 401 is 16 and the predefined MCS offset for CG PUSCH is 4, then the level of the MCS applied to the CG PUSCH transmission 403 on the SBFD symbols is 12.
  • the resources for POs on the SBFD time unit may be the same as the POs on the non-SBFD time units based on the common resource configuration.
  • the resources for POs on the SBFD time unit may be determined based on the common resource configuration and additional parameters dedicated to the SBFD time units.
  • the network device 120 may also transmit (201) a first CG configuration for POs configured on a non-SBFD time unit, and a second CG configuration for POs configured on an SBFD time unit.
  • the first CG configuration may indicate the first set of resources allocated to POs configured on the non-SBFD time units.
  • the second CG configuration may indicate the second set of resources allocated to POs configured on the SBFD time units.
  • separate SDT PUSCH configurations may be determined for SBFD symbols and non-SBFD symbols.
  • a new SDT PUSCH configuration IE for SBFD symbol/slot such as CG-SDT-Configuration-SBFD can be configured through a dedicated radio resource control (RRC) connection release message for the terminal device 110 to transmit SDT PUSCH on SBFD symbols.
  • RRC radio resource control
  • the terminal device 110 transmits, in this PO, (230) an uplink transmission 235 to the network device 120.
  • the uplink transmission 235 may be the SDT. That is, based on determining that a PO on the SBFD time unit is valid, the terminal device 110 may transmit, in this PO, SDT to the network device 120 while the terminal device 110 is at the idle mode or the inactive mode. In turn, the network device 120 receives (240) the uplink transmission 235 accordingly.
  • an association between indexes of SS/PBCH blocks from the network device 120 and the indexes of the POs for transmitting the SDT should be determined 225.
  • the POs configured on the SBFD time units may be referred to as a first plurality of POs
  • the POs configured on the non-SBFD time units may be referred to as a second plurality of POs.
  • the determination of association between the SS/PBCH blocks and the POs is discussed in detail with respect to Figs. 6a to 6f.
  • the first plurality of POs and the second plurality of POs may be numbered uniformly.
  • a plurality of synchronization signal (SS) /physical broadcast channel (PBCH) blocks are mapped, in the same mapping relationship, to the first plurality of POs and the second plurality of POs that are numbered uniformly. That is, the first plurality of POs and the second plurality of POs are not distinguished with respect to the mapping between POs and the SSBs.
  • SS synchronization signal
  • PBCH physical broadcast channel
  • the sdt-SSB-Subset that indicates a subset of SSBs and ConfiguredGrantConfig are common for SBFD symbols and non-SBFD symbols.
  • one mapping relationship is defined.
  • the POs for SBFD slot/symbol and non-SBFD slot/symbol are unified numbered and mapped with SSBs.
  • the configured value for the mapping number N may be chosen from ⁇ onesixteen, oneEighth, oneFourth, half, one, two, four, eight ⁇ for SBFD aware terminal device.
  • the terminal device 110 may be provided, by sdt-SSB-Subset, a number of SS/PBCH block indexes N_PUSCH ⁇ (SS/PBCH) , in order to map to a number of valid POs during an association period.
  • the terminal device 110 may determine N_PUSCH ⁇ (SS/PBCH) from the value of ssb-PositionsInBurst in SIB1 or by ServingCellConfigCommon.
  • the SS/PBCH block indexes provided by sdt-SSB-Subset in SIB1 or in ServingCellConfigCommon are mapped to valid POs and associated DMRS resources in the following order:
  • DMRS_ID is determined first in an ascending order of a DMRS port index and second in an ascending order of a DMRS sequence index
  • mapping relationship between the SS/PBCH blocks and the POs is further discussed with reference to Fig. 6a.
  • Fig. 6a illustrates an example of the mapping relationships between the POs and the SSBs according to some embodiments of the present disclosure.
  • the SSB and the SS/PBCH blocks may be used interchangeably.
  • SSB#1 601 is associated with PO #1 605 in SBFD slot#N
  • SSB#2 603 is associated with PO #2 607 in UL only slot# (N+P) . In this way, more POs on the SBFD time unit can be provided for SDT.
  • the first plurality of POs and the second plurality of POs are independently mapped with the SS/PBCH blocks.
  • SS/PBCH blocks are mapped, in a first mapping relationship, to the first plurality of POs
  • the SS/PBCH blocks are mapped, in the second mapping relationship, to the second plurality of POs.
  • a first PO of the first plurality of POs may be used for transmitting a transport block having a first redundancy version (RV) and a second PO of the second plurality of POs is used for transmitting the same transport block having a second RV.
  • RV redundancy version
  • Fig. 6b illustrates another example of the mapping relationships between the POs and the SSBs according to some embodiments of the present disclosure.
  • the CG PUSCH for SDT may be separately configured for SBFD time units and non-SBFD time units.
  • two mapping relationships are defined.
  • the SS/PBCH block indexes provided by sdt-SSB-Subset in SIB1 or in ServingCellConfigCommon may be mapped to the PO in SBFD slot and non-SBFD slot separately based on the two mapping relationships.
  • the CG PUSCHs on the SBFD slot and non-SBFD slot may carry different RVs for the same TB.
  • the configured value of sdt-SSB-PerCG-PUSCH is 1, which is one SSB is associated with one PO in one mapping relationship. Since the SSB is mapped to POs on the SBFD time units and POs on the non-SBFD time units separately, even if the configured value of sdt-SSB-PerCG-PUSCH is 1, the SSB 611 may be associated with two PUSCHs, and the two PUSCHs include one PUSCH 613 on an SBFD symbol and another one PUSCH 615 on a non-SBFD symbol.
  • the terminal device 110 may transmit two PUSCHs on SBFD symbols and non-SBFD symbols respectively, and the PUSCH can carry the same transport block with different redundancy versions and the RV number may be predefined.
  • the PUSCH transmitted on the SBFD symbols PO1 613 may carry the redundancy version number 0, and the PUSCH transmitted on the non-SBFD symbols PO2 615 may have the redundancy version number 2. In this way, the reliability and coverage of the SDT PUSCH can be improved.
  • the SSBs may be divided into two sets of SSBs, and the mapping between SSBs and POs may be performed between the two sets of SSBs and the first/second plurality of POs.
  • one of the two sets of SSBs may be given by the CG configuration, and the other set of SSBs may be the actually transmitted SSBs, this embodiment is further discussed with reference to Fig. 6c.
  • the two sets of SSBs may be determined directly, and this embodiment is further discussed with reference to Fig. 6d.
  • a CG configuration may indicate a subset of SS/PBCH blocks, and this subset of SS/PBCH blocks is one of the above two sets of SSBs.
  • SS/PBCH blocks in the indicated subset of SS/PBCH blocks may be mapped to one of the first plurality of POs or the second plurality of POs, for example, the first plurality of POs or the second plurality of POs.
  • SS/PBCH blocks of the SS/PBCH blocks which are actually transmitted (these actually transmitted SS/PBCH blocks may be the other one of the two sets of SSBs) by the network device 120 may be mapped to the other one of the first plurality of POs or the second plurality of POs.
  • Fig. 6c illustrates a further example of the mapping relationship between the POs and the SSBs according to some embodiments of the present disclosure.
  • sdt-SSB-Subset 621 For SBFD aware terminal device, sdt-SSB-Subset 621 always provided, and the SSB index in this subset 621 are configured for SBFD symbols. The SSBs in this subset 621 are associated with the SDT CG PUSCH resources 625 on the SBFD symbols.
  • UE determines all actually transmitted SSB N_PUSCH ⁇ (SS/PBCH) 623 for non-SBFD symbols from the value of ssb-PositionsInBurst in SIB1 or by ServingCellConfigCommon, and the N_PUSCH ⁇ (SS/PBCH) 623 are associated with the SDT CG PUSCH resources 627 on the non-SBFD symbols.
  • the mapping relationships are separately performed for SBFD symbols and non-SBFD symbols.
  • the SSBs may be directly divided into a first subset of SS/PBCH blocks and a second subset of SSBs without depending on SS/PBCH block subset indicated by the CG configuration.
  • SS/PBCH blocks in the first subset of SS/PBCH blocks are mapped to one of the first plurality of POs or the second plurality of POs.
  • SS/PBCH blocks in the second subset of SS/PBCH blocks are mapped to the other one of the first plurality of POs or the second plurality of POs.
  • Fig. 6d illustrates a yet example of the mapping relationship between the POs and the SSBs according to some embodiments of the present disclosure.
  • both SSB set and SDT CG PUSCH are separately configured and numbered for SBFD symbols and non-SBFD symbols. That is, two sdt-SSB-Subsets 631 and 633 and two ConfiguredGrantConfig IEs (wherein one is for SBFD time units and the other one is for non-SBFD time units) are configured for SBFD aware terminal device.
  • the SSB indexes and PO indexes are separately numbered for SBFD time units or non-SBFD time units.
  • the above embodiments may be also expressed as below.
  • the mapping is performed in a group of SS/PBCH blocks using the same mapping relationship.
  • the mapping should be performed in a group of SS/PBCH blocks using a respective mapping relationship between SS/PBCH blocks in the group of SSBs and the POs.
  • a first group of SS/PBCH blocks are mapped to POs in the first plurality of POs in a mapping relationship
  • a second group of SS/PBCH blocks are mapped to POs in the second plurality of POs in the same mapping relationship.
  • the first group of SS/PBCH blocks and the second group of SS/PBCH blocks are the same or different.
  • the POs in the SBFD time units or the POs in the non-SBFD time units may be mapped with a corresponding group of SSBs, respectively, and the mapping relationship for the POs on the SBFD time units or the non-SBFD time units is the same.
  • the above embodiment is further discussed with reference to Fig. 6e.
  • Fig. 6e illustrates one more example of the mapping relationships between the POs and the SSBs according to some embodiments of the present disclosure.
  • a terminal device that is indicated to release a dedicated RRC connection is, by respective more than one ConfiguredGrantConfig, provided more than one configurations for CG Type 1 POs on the UL subband of SBFD time units and UL only slot.
  • These POs are uniformly numbered and mapped with the common SSB set that is provided by sdt-SSB-Subset, ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon.
  • the mapping number “N” between the SSBs and POs is above one, multiple SSBs may be associated with one PO.
  • the SSB indexed that are provided by sdt-SSB-Subset may be divided into two groups. Then, the SSB indexes in one group may be mapped to the POs in SBFD symbols, and the SSB indexes in the other group may be mapped to the POs in non-SBFD symbols.
  • the SSB number/index in the two groups may be same or different.
  • the mapping order is in the increasing order of DMRS resource indexes within a PUSCH occasion.
  • the mapping order is in the increasing order of frequency resource indexes in a PO.
  • the mapping order is in the increasing order of time resource indexes for time resource.
  • the number of configured SSBs is 8, then half of these SSBs may be associated with the POs in SBFD symbols and the left SSBs may be associated with the POs in non-SBFD symbols.
  • the first group 641 of SSBs are mapped to POs (PO#1 645 and PO#2 647) in SBFD slot, and the second group 643 of SSBs are mapped to POs (PO#3 648 and PO#4 649) in non-SBFD slot.
  • a mapping relationship for the POs on the SBFD time units and another mapping relationship for the POs on the non-SBFD time units may be different.
  • SS/PBCH blocks may be mapped to POs in the first plurality of POs in a third mapping relationship.
  • SS/PBCH blocks may be mapped to POs in the second plurality of POs in a fourth mapping relationship.
  • this embodiment is further discussed with reference to Fig. 6f.
  • Fig. 6f illustrates an additional example of the mapping relationships between the POs and the SSBs according to some embodiments of the present disclosure.
  • a common SSB set is configured for SBFD symbols and non-SBFD symbols.
  • a terminal device that is indicated to release a dedicated RRC connection is provided, by respective more than one ConfiguredGrantConfig, more than one configurations for CG Type 1 POs on the UL subband of SBFD time units and UL only slot.
  • the PO indexes are separately numbered for SBFD symbols and non-SBFD symbols.
  • the mapping relationship may be separately performed for SBFD symbols and non-SBFD symbols.
  • the number N of SS/PBCH block indexes associated with one PO may be separately configured for SBFD symbols and non-SBFD symbols.
  • one SSB index may be mapped to the POs that are in both SBFD symbols and non-SBFD symbols.
  • a parameter “SBFD-sdt-SSB-PerCG-PUSCH” may be newly defined for SBFD aware terminal device to configure the mapping ratio for SSB and CG-PUSCH for SDT in SBFD time units.
  • the mapping number N 1, that is each SSB mapped to one PO in non-SBFD symbols.
  • the SSB#1 651 is mapped to the PO#1 655 and PO#2 656 in the SBFD time units.
  • the SSB#2 653 is mapped to the PO#3 657 and PO#4 658 in the SBFD time units.
  • the SSB#1 651 is mapped to the PO#1 659 in the SBFD time units.
  • the SSB#2 653 is mapped to PO#2 660 in the non-SBFD time units. In this way, the index of POs may be extended.
  • the SDT may be required to be retransmitted.
  • the terminal device 110 only can transmit the SDT retransmission after the timer for the retransmission expires. In this case, there may be a longer delay of the SDT retransmission.
  • the terminal device 110 may receive control information (for example, downlink control channel, DCI) from the network device 120, and the control information schedules a retransmission of a SDT within an uplink subband of an SBFD time unit. Then, the terminal device 110 may transmit to the network device 120 the retransmission of the SDT within the uplink subband of the SBFD time unit before the timer for the retransmission expires.
  • control information for example, downlink control channel, DCI
  • DCI downlink control channel
  • Fig. 7a illustrates an example of SDT retransmissions on SBFD time units according to some embodiments of the present disclosure.
  • the terminal device 110 receives CS-RNTI scrambled DCI that schedules SDT PUSCH retransmission within the UL subband resource on the SBFD time units and before the cg-SDT-RetransmissionTimer expires, the terminal device 110 may transmit the SDT PUSCH retransmission on the UL subband of the SBFD symbols.
  • the initial SDT PUSCH#1 is transmitted on the UL subband in slot #N.
  • the terminal device 110 receives DCI1 701 scheduling PUSCH#1 retransmission on the UL subband of SBFD slot #M.
  • the initial SDT PUSCH#2 is transmitted on the UL subband in slot #M, and the scheduled PUSCH #1 retransmission 703 is transmitted accordingly.
  • the terminal device 110 receives DCI2 705 scheduling PUSCH#2 retransmission on the UL subband of SBFD slot #P. Then, the terminal device 110 may transmit PUSCH #2 retransmission 707 accordingly. In this way, the delay of SDT PUSCH retransmission can be reduced.
  • the terminal device 110 may autonomously transmit the SDT retransmission if there are retransmission resources configured on the UL subband of the SBFD time unit that is before the expiration of the timer.
  • the terminal device 110 may transmit, before a timer for a retransmission of a SDT expires, a retransmission of SDT within an uplink subband of a second SBFD time unit autonomously.
  • the second SBFD time unit may be earlier than the closest next non-SBFD time unit having a PO. For discussion purposes, this embodiment is further discussed with reference to Fig. 7b.
  • Fig. 7b illustrates another example of SDT retransmissions on SBFD time units according to some embodiments of the present disclosure.
  • the terminal device 110 may autonomously transmit the SDT PUSCH retransmission on the UL subband of these SBFD time units if the FDRA for CG PUSCH is within the UL subband of the SBFD symbols.
  • the SDT initial PUSCH transmission is transmitted on slot#N and before the timer expires, the terminal device does not receive C-RNTI scrambled DCI scheduling new PUSCH or does not receive CS-RNTI scrambled DCI schedule SDT PUSCH retransmission.
  • the terminal device 110 only can transmit SDT PUSCH retransmission autonomously after the timer expires.
  • the terminal device may transmit the SDT PUSCH retransmission autonomously based on the same FDRA in the SBFD time units which are before the expiration of the timer. In this way, the overhead of DCI and the delay of the SDT PUSCH delay can be reduced.
  • the terminal device 110 may monitor DCI in the downlink subband of the SBFD time unit.
  • the terminal device 110 may monitor a downlink control channel (for example, a physical downlink control channel, PDCCH) from the network device 120 in the first SDT-search space.
  • a downlink control channel for example, a physical downlink control channel, PDCCH
  • the terminal device 110 may be provided by sdt-SearchSpace-SBFD a dedicated CSS set to monitor the PDCCH on SBFD DL subband, for example, after contention resolution as described in clause 8.4, PDCCH for detection of a DCI format 0_0 or DCI format 1_0 with CRC scrambled by C-RNTI for scheduling respective PUSCH transmissions or PDSCH receptions.
  • the terminal device 110 may monitor the downlink control channel from the network device 120 based on a second SDT-search space (which may be common to the SBFD time units and the non-SBFD time units) or a PDCCH common search space (CSS) set.
  • a second SDT-search space which may be common to the SBFD time units and the non-SBFD time units
  • a PDCCH common search space (CSS) set.
  • the terminal device 110 may monitor PDCCH according to a CSS set provided by sdt-SearchSpace or a Type1-PDCCH CSS set as described in clause 10.1 of TS 38.213.
  • the terminal device 110 may assume that the DM-RS antenna port is associated with the PDCCH receptions, the DM-RS antenna port is associated with the PDSCH receptions, and the SS/PBCH block associated is with the PRACH transmission are quasi co-located with respect to average gain and quasi co-location 'typeA' or 'typeD' properties.
  • this disclosure further includes PUSCH allocation/configuration in UL subband of SBFD symbols; valid PO determination on SBFD symbols; the PO mapping relationship with SSB for PO in SBFD symbols; the SDT PUSCH re-transmission; and a dedicated CSS set can be configured for UE to monitor the PDCCH on SBFD symbols.
  • Fig. 8 illustrates a flowchart of a method 800 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure.
  • the method 800 can be implemented at the terminal device 110 shown in Fig. 1.
  • the method 800 will be described with reference to Fig. 1. It is to be understood that the method 800 may include additional acts not shown and/or may omit some shown acts, and the scope of the present disclosure is not limited in this regard.
  • the terminal device 110 determines whether a physical uplink shared channel (PUSCH) occasion (PO) on a subband non-overlapping full duplex (SBFD) time unit is valid.
  • the SBFD time unit is configured with frequency subbands for different link directions.
  • the terminal device 110 further transmits, in the PO, an uplink transmission to a network device 120.
  • the uplink transmission comprises a small data transmission (SDT) that is transmitted by the terminal device at an idle mode or an inactive mode.
  • SDT small data transmission
  • the terminal device 110 further receives, from the network device 120, a configured grant (CG) configuration for POs.
  • the CG configuration comprises a common resource configuration indicating the resources allocated to the PO on the SBFD time unit and a non-SBFD time unit.
  • the CG configuration further comprises at least one additional parameter for indicating the POs on the SBFD time unit.
  • the terminal device 110 may further determine the POs on the SBFD time unit using the common resource configuration and the at least one additional parameter.
  • the terminal device 110 may further determine the POs on the SBFD time unit using the common resource configuration.
  • the at least one additional parameter comprises an offset value relative to parameters of the common resource configuration.
  • the terminal device 110 may further receive, from the network device 120, a first CG configuration for POs on a non-SBFD time unit and a second CG configuration for POs on the SBFD time unit.
  • the terminal device 110 may determine whether the PO on the SBFD time unit is valid by determining whether a second set of resources allocated to the PO on the SBFD time unit is within an uplink subband of the SBFD time unit. The terminal device 110 may determine that the PO is valid based on determining that the second set of resources is within the uplink subband and that the second set of resources does not overlap with a valid physical random access channel (PRACH) occasion. Alternatively, the terminal device 110 may determine that the PO is invalid based on determining that the second set of resources is not within the uplink subband and/or that the second set of resources overlaps with the valid PRACH occasion.
  • PRACH physical random access channel
  • the PO is one of a first plurality of POs on SBFD time units, and a second plurality of POs on non-SBFD time units.
  • the first plurality of POs and the second plurality of POs are numbered uniformly, and a plurality of synchronization signal (SS) /physical broadcast channel (PBCH) blocks are mapped, in a same mapping relationship, to the first plurality of POs and the second plurality of POs that are numbered uniformly.
  • SS synchronization signal
  • PBCH physical broadcast channel
  • SS/PBCH blocks are mapped, in a first mapping relationship, to the first plurality of POs
  • the SS/PBCH blocks are mapped, in the second mapping relationship, to the second plurality of POs
  • a first PO of the first plurality of POs is used for transmitting a transport block having a first redundancy version (RV)
  • a second PO of the second plurality of POs is used for transmitting the same transport block having a second RV.
  • RV redundancy version
  • a CG configuration indicates a subset of SS/PBCH blocks.
  • SS/PBCH blocks in the indicated subset of SS/PBCH blocks are mapped to one of the first plurality of POs or the second plurality of POs, and SS/PBCH blocks of the actually transmitted SS/PBCH blocks are mapped to the other one of the first plurality of POs or the second plurality of POs.
  • a plurality of SS/PBCH blocks is divided a first subset of SS/PBCH blocks and a second subset of SS/PBCH blocks, and wherein: SS/PBCH blocks in the first subset of SS/PBCH blocks are mapped to one of the first plurality of POs or the second plurality of POs, and SS/PBCH blocks in the second subset of SS/PBCH blocks are mapped to the other one of the first plurality of POs or the second plurality of POs.
  • a first group of SS/PBCH blocks are mapped to POs in the first plurality of POs in a mapping relationship; and a second group of SS/PBCH blocks are mapped to POs in the second plurality of POs in the same mapping relationship, and wherein the first group of SS/PBCH blocks and the second group of SS/PBCH blocks are the same or different.
  • SS/PBCH blocks are mapped to POs in the first plurality of POs in a third mapping relationship; and SS/PBCH blocks are mapped to POs in the second plurality of POs in a fourth mapping relationship.
  • the terminal device 110 may receive, from the network device, control information scheduling a retransmission of a SDT within an uplink subband of a first SBFD time unit; and transmit, before a timer for the retransmission expires, the retransmission of the SDT within the uplink subband of the first SBFD time unit.
  • the resources allocated to POs is within an uplink subband of SBFD time units in the frequency domain.
  • the terminal device 110 may further transmit, before a timer for a retransmission of a SDT expires, a retransmission of SDT within an uplink subband of a second SBFD time unit autonomously.
  • the second SBFD time unit is earlier than the closest next non-SBFD time unit having a PO.
  • the terminal device 110 may monitor, during the SBFD time unit, a downlink control channel from the network device in the first SDT-search space for the SBFD time unit.
  • the terminal device 110 may monitor the downlink control channel from the network device based on a second SDT-search space or a physical downlink control channel (PDCCH) common search space (CSS) set.
  • PDCCH physical downlink control channel
  • SCS common search space
  • Fig. 9 illustrates a flowchart of a method 900 of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • the method 900 can be implemented at the network device 120 shown in Fig. 1.
  • the method 900 will be described with reference to Fig. 1. It is to be understood that the method 900 may include additional acts not shown and/or may omit some shown acts, and the scope of the present disclosure is not limited in this regard.
  • the network device 120 determines whether a physical uplink shared channel (PUSCH) occasion (PO) on a subband non-overlapping full duplex (SBFD) time unit is valid.
  • the SBFD time unit is configured with frequency subbands for different link directions.
  • the network device 120 further receives, in the PO, an uplink transmission from a terminal device 110.
  • the uplink transmission comprises a small data transmission (SDT) that is transmitted by the terminal device at an idle mode or an inactive mode.
  • SDT small data transmission
  • the network device 120 may transmit, to the terminal device, a configured grant (CG) configuration for POs, wherein the CG configuration comprises a common resource configuration indicating the resources allocated to the PO on the SBFD time unit and a non-SBFD time unit.
  • CG configured grant
  • the CG configuration further comprises at least one additional parameter for indicating the POs on the SBFD time unit.
  • the network device 120 may transmit, to the terminal device, a first CG configuration for POs on a non-SBFD time unit and a second CG configuration for POs on the SBFD time unit.
  • the network device120 may determine whether the PO on the SBFD time unit is valid by determining whether a second set of resources allocated to the PO on the SBFD time unit is within an uplink subband of the SBFD time unit.
  • the terminal device 120 may determine that the PO is valid based on determining that the second set of resources is within the uplink subband and that the second set of resources does not overlap with a valid physical random access channel (PRACH) occasion.
  • PRACH physical random access channel
  • the network device 120 may determine that the PO is invalid based on determining that the second set of resources is not within the uplink subband and/or that the second set of resources overlaps with the valid PRACH occasion.
  • the PO is one of a first plurality of POs scheduled on SBFD time units, and a second plurality of POs is scheduled on non-SBFD time units.
  • the first plurality of POs and the second plurality of POs are numbered uniformly, and a plurality of synchronization signal (SS) /physical broadcast channel (PBCH) blocks are mapped, in a same mapping relationship, to the first plurality of POs and the second plurality of POs that are numbered uniformly.
  • SS synchronization signal
  • PBCH physical broadcast channel
  • SS/PBCH blocks are mapped, in a first mapping relationship, to the first plurality of POs
  • the SS/PBCH blocks are mapped, in the second mapping relationship, to the second plurality of POs
  • a first PO of the first plurality of POs is used for transmitting a transport block having a first redundancy version (RV)
  • a second PO of the second plurality of POs is used for transmitting the same transport block having a second RV.
  • RV redundancy version
  • a CG indicates a subset of SS/PBCH blocks
  • SS/PBCH blocks in the indicated subset of SS/PBCH blocks are mapped to one of the first plurality of POs or the second plurality of POs
  • SS/PBCH blocks of the actually transmitted SS/PBCH blocks are mapped to the other one of the first plurality of POs or the second plurality of POs.
  • a plurality of SS/PBCH blocks is divided a first subset of SS/PBCH blocks and a second subset of SS/PBCH blocks, and wherein: SS/PBCH blocks in the first subset of SS/PBCH blocks are mapped to one of the first plurality of POs or the second plurality of POs, and SS/PBCH blocks in the second subset of SS/PBCH blocks are mapped to the other one of the first plurality of POs or the second plurality of POs.
  • a first group of SS/PBCH blocks are mapped to POs in the first plurality of POs in a mapping relationship; and a second group of SS/PBCH blocks are mapped to POs in the second plurality of POs in the same mapping relationship, and wherein the first group of SS/PBCH blocks and the second group of SS/PBCH blocks are the same or different.
  • SS/PBCH blocks are mapped to POs in the first plurality of POs in a third mapping relationship; and SS/PBCH blocks are mapped to POs in the second plurality of POs in a fourth mapping relationship.
  • the network device 120 may transmit, to the terminal device, control information scheduling a retransmission of a SDT within an uplink subband of a first SBFD time unit; and receive, before a timer for the retransmission expires, the retransmission of the SDT within the uplink subband of the first SBFD time unit.
  • the resources allocated to POs is within an uplink subband of SBFD time units in the frequency domain.
  • the network device 120 may receive, before a timer for a retransmission of a SDT expires, a retransmission of SDT within an uplink subband of a second SBFD time unit, wherein the second SBFD time unit is earlier than the closest next non-SBFD time unit having a PO.
  • the network device 120 may transmit, during the SBFD time unit, a downlink control channel to the terminal device in the first SDT-search space for the SBFD time unit.
  • the network device 120 may transmit the downlink control channel to the terminal device based on a second SDT-search space or a physical downlink control channel (PDCCH) common search space (CSS) set.
  • PDCCH physical downlink control channel
  • SCS common search space
  • Fig. 10 is a simplified block diagram of a device 1000 that is suitable for implementing some embodiments of the present disclosure.
  • the device 1000 can be considered as a further example embodiment of the terminal device 110 or network device 120 as shown in Fig. 1. Accordingly, the device 1000 can be implemented at or as at least a part of the above network devices or terminal devices.
  • the device 1000 includes a processor 1010, a memory 1020 coupled to the processor 1010, a suitable transceiver 1040 coupled to the processor 1010, and a communication interface coupled to the transceiver 1040.
  • the memory 1010 stores at least a part of a program 1030.
  • the transceiver 1040 may be for bidirectional communications or a unidirectional communication based on requirements.
  • the transceiver 1040 may include at least one of a transmitter 1042 and a receiver 1044.
  • the transmitter 1042 and the receiver 1044 may be functional modules or physical entities.
  • the transceiver 1040 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 1030 is assumed to include program instructions that, when executed by the associated processor 1010, enable the device 1000 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to Figs. 1-9.
  • the embodiments herein may be implemented by computer software executable by the processor 1010 of the device 1000, or by hardware, or by a combination of software and hardware.
  • the processor 1010 may be configured to implement various embodiments of the present disclosure.
  • a combination of the processor 1010 and memory 1020 may form processing means 1050 adapted to implement various embodiments of the present disclosure.
  • the memory 1020 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 1020 is shown in the device 1000, there may be several physically distinct memory modules in the device 1000.
  • the processor 1010 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 1000 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 comprises circuitry configured to perform a method 800.
  • a network device comprises circuitry configured to perform a method 900.
  • the components included in the apparatuses and/or devices of the present disclosure may be implemented in various manners, including software, hardware, firmware, or any combination thereof.
  • one or more units may be implemented using software and/or firmware, for example, machine-executable instructions stored on the storage medium.
  • parts or all of the units in the apparatuses and/or devices may be implemented, at least in part, by one or more hardware logic components.
  • FPGAs Field-programmable Gate Arrays
  • ASICs Application-specific Integrated Circuits
  • ASSPs Application-specific Standard Products
  • SOCs System-on-a-chip systems
  • CPLDs Complex Programmable Logic Devices
  • 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, technique terminal devices 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 any of Figs. 2 to 17.
  • 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.
  • embodiments of the present disclosure may provide the following solutions.
  • a terminal device comprising: a processor, and the processor is configured to cause the terminal device to: determine whether a physical uplink shared channel (PUSCH) occasion (PO) on a subband non-overlapping full duplex (SBFD) time unit is valid, wherein the SBFD time unit is configured with frequency subbands for different link directions; and transmit, in the PO and to a network device, an uplink transmission based on determining that the PO is valid.
  • PUSCH physical uplink shared channel
  • SBFD subband non-overlapping full duplex
  • the uplink transmission comprises a small data transmission (SDT) that is transmitted by the terminal device at an idle mode or an inactive mode.
  • SDT small data transmission
  • the terminal device is further caused to: receive, from the network device, a configured grant (CG) configuration for POs, wherein the CG configuration comprises a common resource configuration indicating the resources allocated to the PO on the SBFD time unit and a non-SBFD time unit.
  • CG configured grant
  • the CG configuration further comprises at least one additional parameter for indicating the POs on the SBFD time unit.
  • the terminal device is further caused to: in a case that the CG configuration comprises the at least one additional parameter and the common resource configuration, determine the POs on the SBFD time unit using the common resource configuration and the at least one additional parameter; or in a case that the CG configuration comprises the common resource configuration, determine the POs on the SBFD time unit using the common resource configuration.
  • the at least one additional parameter comprises an offset value relative to parameters of the common resource configuration.
  • the terminal device is further caused to: receive, from the network device, a first CG configuration for POs on a non-SBFD time unit and a second CG configuration for POs on the SBFD time unit.
  • the terminal device is caused to determine whether the PO on the SBFD time unit is valid by determining whether a second set of resources allocated to the PO on the SBFD time unit is within an uplink subband of the SBFD time unit, and wherein the terminal device is further caused to: determine that the PO is valid based on determining that the second set of resources is within the uplink subband and that the second set of resources does not overlap with a valid physical random access channel (PRACH) occasion; or determine that the PO is invalid based on determining that the second set of resources is not within the uplink subband and/or that the second set of resources overlaps with the valid PRACH occasion.
  • PRACH physical random access channel
  • the PO is one of a first plurality of POs on SBFD time units, and a second plurality of POs on non-SBFD time units.
  • the first plurality of POs and the second plurality of POs are numbered uniformly, and a plurality of synchronization signal (SS) /physical broadcast channel (PBCH) blocks are mapped, in a same mapping relationship, to the first plurality of POs and the second plurality of POs that are numbered uniformly.
  • SS synchronization signal
  • PBCH physical broadcast channel
  • SS/PBCH blocks are mapped, in a first mapping relationship, to the first plurality of POs
  • the SS/PBCH blocks are mapped, in the second mapping relationship, to the second plurality of POs
  • a first PO of the first plurality of POs is used for transmitting a transport block having a first redundancy version (RV)
  • a second PO of the second plurality of POs is used for transmitting the same transport block having a second RV.
  • a CG configuration indicates a subset of SS/PBCH blocks
  • SS/PBCH blocks in the indicated subset of SS/PBCH blocks are mapped to one of the first plurality of POs or the second plurality of POs
  • SS/PBCH blocks of the actually transmitted SS/PBCH blocks are mapped to the other one of the first plurality of POs or the second plurality of POs.
  • a plurality of SS/PBCH blocks is divided a first subset of SS/PBCH blocks and a second subset of SS/PBCH blocks, and wherein: SS/PBCH blocks in the first subset of SS/PBCH blocks are mapped to one of the first plurality of POs or the second plurality of POs, and SS/PBCH blocks in the second subset of SS/PBCH blocks are mapped to the other one of the first plurality of POs or the second plurality of POs.
  • a first group of SS/PBCH blocks are mapped to POs in the first plurality of POs in a mapping relationship; and a second group of SS/PBCH blocks are mapped to POs in the second plurality of POs in the same mapping relationship, and wherein the first group of SS/PBCH blocks and the second group of SS/PBCH blocks are the same or different.
  • SS/PBCH blocks are mapped to POs in the first plurality of POs in a third mapping relationship; and SS/PBCH blocks are mapped to POs in the second plurality of POs in a fourth mapping relationship.
  • the terminal device is further caused to: receive, from the network device, control information scheduling a retransmission of a SDT within an uplink subband of a first SBFD time unit; and transmit, before a timer for the retransmission expires, the retransmission of the SDT within the uplink subband of the first SBFD time unit.
  • the terminal device is further caused to: transmit, before a timer for a retransmission of a SDT expires, a retransmission of SDT within an uplink subband of a second SBFD time unit autonomously, wherein the second SBFD time unit is earlier than the closest next non-SBFD time unit having a PO.
  • the terminal device is further caused to: in a case that a first SDT-search space for the SBFD time unit is configured, monitor, during the SBFD time unit, a downlink control channel from the network device in the first SDT-search space for the SBFD time unit; or monitor the downlink control channel from the network device based on a second SDT-search space or a physical downlink control channel (PDCCH) common search space (CSS) set.
  • a first SDT-search space for the SBFD time unit is configured, monitor, during the SBFD time unit, a downlink control channel from the network device in the first SDT-search space for the SBFD time unit; or monitor the downlink control channel from the network device based on a second SDT-search space or a physical downlink control channel (PDCCH) common search space (CSS) set.
  • PDCCH physical downlink control channel
  • SCS common search space
  • a network device comprising: a processor, and the processor is configured to cause the network device to: determine whether a physical uplink shared channel (PUSCH) occasion (PO) on a subband non-overlapping full duplex (SBFD) time unit is valid, wherein the SBFD time unit is configured with frequency subbands for different link directions; and receive, in the PO and from a terminal device, an uplink transmission based on determining that the PO is valid.
  • PUSCH physical uplink shared channel
  • SBFD subband non-overlapping full duplex
  • the uplink transmission comprises a small data transmission (SDT) that is transmitted by the terminal device at an idle mode or an inactive mode.
  • SDT small data transmission
  • the network device is further caused to: transmit, to the terminal device, a configured grant (CG) configuration for POs, wherein the CG configuration comprises a common resource configuration indicating the resources allocated to the PO on the SBFD time unit and a non-SBFD time unit.
  • CG configured grant
  • the CG configuration further comprises at least one additional parameter for indicating the POs on the SBFD time unit.
  • the at least one additional parameter comprises an offset value relative to parameters of the common resource configuration.
  • the network device is further caused to: transmit, to the terminal device, a first CG configuration for POs on a non-SBFD time unit and a second CG configuration for POs on the SBFD time unit.
  • the network device is caused to determine whether the PO on the SBFD time unit is valid by determining whether a second set of resources allocated to the PO on the SBFD time unit is within an uplink subband of the SBFD time unit, and wherein the terminal device is further caused to: determine that the PO is valid based on determining that the second set of resources is within the uplink subband and that the second set of resources does not overlap with a valid physical random access channel (PRACH) occasion; or determine that the PO is invalid based on determining that the second set of resources is not within the uplink subband and/or that the second set of resources overlaps with the valid PRACH occasion.
  • PRACH physical random access channel
  • the PO is one of a first plurality of POs scheduled on SBFD time units, and a second plurality of POs is scheduled on non-SBFD time units.
  • the first plurality of POs and the second plurality of POs are numbered uniformly, and a plurality of synchronization signal (SS) /physical broadcast channel (PBCH) blocks are mapped, in a same mapping relationship, to the first plurality of POs and the second plurality of POs that are numbered uniformly.
  • SS synchronization signal
  • PBCH physical broadcast channel
  • SS/PBCH blocks are mapped, in a first mapping relationship, to the first plurality of POs
  • the SS/PBCH blocks are mapped, in the second mapping relationship, to the second plurality of POs
  • a first PO of the first plurality of POs is used for transmitting a transport block having a first redundancy version (RV)
  • a second PO of the second plurality of POs is used for transmitting the same transport block having a second RV.
  • a CG indicates a subset of SS/PBCH blocks
  • SS/PBCH blocks in the indicated subset of SS/PBCH blocks are mapped to one of the first plurality of POs or the second plurality of POs
  • SS/PBCH blocks of the actually transmitted SS/PBCH blocks are mapped to the other one of the first plurality of POs or the second plurality of POs.
  • a plurality of SS/PBCH blocks is divided a first subset of SS/PBCH blocks and a second subset of SS/PBCH blocks, and wherein: SS/PBCH blocks in the first subset of SS/PBCH blocks are mapped to one of the first plurality of POs or the second plurality of POs, and SS/PBCH blocks in the second subset of SS/PBCH blocks are mapped to the other one of the first plurality of POs or the second plurality of POs.
  • a first group of SS/PBCH blocks are mapped to POs in the first plurality of POs in a mapping relationship; and a second group of SS/PBCH blocks are mapped to POs in the second plurality of POs in the same mapping relationship, and wherein the first group of SS/PBCH blocks and the second group of SS/PBCH blocks are the same or different.
  • SS/PBCH blocks are mapped to POs in the first plurality of POs in a third mapping relationship; and SS/PBCH blocks are mapped to POs in the second plurality of POs in a fourth mapping relationship.
  • the network device is further caused to: transmit, to the terminal device, control information scheduling a retransmission of a SDT within an uplink subband of a first SBFD time unit; and receive, before a timer for the retransmission expires, the retransmission of the SDT within the uplink subband of the first SBFD time unit.
  • the network device is further caused to: receive, before a timer for a retransmission of a SDT expires, a retransmission of SDT within an uplink subband of a second SBFD time unit, wherein the second SBFD time unit is earlier than the closest next non-SBFD time unit having a PO.
  • the network device is further caused to: in a case that a first SDT-search space for the SBFD time unit is configured, transmit, during the SBFD time unit, a downlink control channel to the terminal device in the first SDT-search space for the SBFD time unit; or transmit the downlink control channel to the terminal device based on a second SDT-search space or a physical downlink control channel (PDCCH) common search space (CSS) set.
  • a first SDT-search space for the SBFD time unit is configured, transmit, during the SBFD time unit, a downlink control channel to the terminal device in the first SDT-search space for the SBFD time unit; or transmit the downlink control channel to the terminal device based on a second SDT-search space or a physical downlink control channel (PDCCH) common search space (CSS) set.
  • PDCCH physical downlink control channel
  • SCS common search space
  • a method of communication comprising: determining whether a physical uplink shared channel (PUSCH) occasion (PO) on a subband non-overlapping full duplex (SBFD) time unit is valid, wherein the SBFD time unit is configured with frequency subbands for different link directions; and transmitting, in the PO and to a network device, an uplink transmission based on determining that the PO is valid.
  • PUSCH physical uplink shared channel
  • SBFD subband non-overlapping full duplex
  • a method of communication comprising: determining whether a physical uplink shared channel (PUSCH) occasion (PO) on a subband non-overlapping full duplex (SBFD) time unit is valid, wherein the SBFD time unit is configured with frequency subbands for different link directions; and receiving, in the PO and from a terminal device, an uplink transmission based on determining that the PO is valid.
  • PUSCH physical uplink shared channel
  • SBFD subband non-overlapping full duplex
  • 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 according to the above methods.

Landscapes

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

Abstract

Des modes de réalisation de la présente divulgation concernent des dispositifs, des procédés et un support lisible par ordinateur visant à l'amélioration des transmissions. Selon des modes de réalisation de la présente divulgation, le dispositif terminal détermine si une occasion de canal partagé de liaison montante physique (PUSCH) (PO) sur une unité de temps de duplex intégral sans chevauchement de sous-bande (SBFD) est valide. L'unité de temps SBFD est configurée avec des sous-bandes de fréquence pour différentes directions de liaison. Sur la base de la détermination du fait que la PO est valide, le dispositif terminal transmet en outre, dans la PO, une transmission de liaison montante à un dispositif de réseau. De cette manière, la transmission de petites données (SDT) peut être améliorée.
PCT/CN2023/137536 2023-12-08 2023-12-08 Dispositif, procédé et support lisible par ordinateur pour des communications Pending WO2025118281A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/137536 WO2025118281A1 (fr) 2023-12-08 2023-12-08 Dispositif, procédé et support lisible par ordinateur pour des communications

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/137536 WO2025118281A1 (fr) 2023-12-08 2023-12-08 Dispositif, procédé et support lisible par ordinateur pour des communications

Publications (1)

Publication Number Publication Date
WO2025118281A1 true WO2025118281A1 (fr) 2025-06-12

Family

ID=95981485

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/137536 Pending WO2025118281A1 (fr) 2023-12-08 2023-12-08 Dispositif, procédé et support lisible par ordinateur pour des communications

Country Status (1)

Country Link
WO (1) WO2025118281A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114667705A (zh) * 2019-10-14 2022-06-24 高通股份有限公司 用于两步随机接入信道(rach)的物理上行链路共享信道(pusch)时机验证的系统和方法
US20230224880A1 (en) * 2022-03-17 2023-07-13 Intel Corporation Techniques for downlink and uplink resource mapping for full duplex and non-cell defining synchronization signal block
CN116548053A (zh) * 2020-12-29 2023-08-04 鸿颖创新有限公司 小数据传输方法及相关设备
US20230254829A1 (en) * 2022-04-15 2023-08-10 Intel Corporation Uplink (ul) transmissions in full duplex (fd) systems
CN116848922A (zh) * 2023-05-12 2023-10-03 北京小米移动软件有限公司 确定、配置上行免授权资源的方法、及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114667705A (zh) * 2019-10-14 2022-06-24 高通股份有限公司 用于两步随机接入信道(rach)的物理上行链路共享信道(pusch)时机验证的系统和方法
CN116548053A (zh) * 2020-12-29 2023-08-04 鸿颖创新有限公司 小数据传输方法及相关设备
US20230224880A1 (en) * 2022-03-17 2023-07-13 Intel Corporation Techniques for downlink and uplink resource mapping for full duplex and non-cell defining synchronization signal block
US20230254829A1 (en) * 2022-04-15 2023-08-10 Intel Corporation Uplink (ul) transmissions in full duplex (fd) systems
CN116848922A (zh) * 2023-05-12 2023-10-03 北京小米移动软件有限公司 确定、配置上行免授权资源的方法、及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "On SBFD in NR systems", 3GPP DRAFT; R1-2302795, vol. 3GPP RAN 1, 8 April 2023 (2023-04-08), pages 1 - 24, XP052352279 *

Similar Documents

Publication Publication Date Title
WO2024192688A1 (fr) Dispositif, procédé et support lisible par ordinateur pour communication
WO2024007314A1 (fr) Procédés, dispositifs et support destinés aux communications
WO2023150981A1 (fr) Procédés, dispositifs, et support lisible par ordinateur pour des communications
WO2025010546A1 (fr) Dispositif, procédé et support lisible par ordinateur pour les communications
WO2024212117A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications
WO2024000584A1 (fr) Procédé, dispositif et support lisible par ordinateur pour communication sur liaison latérale
US20250212185A1 (en) Method, device and computer storage medium of communication
WO2025118281A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications
US20250176016A1 (en) Method, device and computer readable medium for communications
WO2025030515A1 (fr) Dispositif, procédé et support lisible par ordinateur pour les communications
WO2025091391A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications
WO2025065189A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications
WO2025199686A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications
WO2024130610A1 (fr) Procédé, dispositif et support lisible par ordinateur destinés à des communications
WO2025213424A1 (fr) Dispositif, procédé et support lisible par ordinateur pour les communications
WO2023236178A1 (fr) Procédé, dispositif et support lisible par ordinateur pour des communications de liaison latérale
WO2025152159A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications
WO2025030330A1 (fr) Dispositif, procédé et support lisible par ordinateur pour les communications
WO2024065771A1 (fr) Procédés, dispositifs et support de communication
US20250142603A1 (en) Method, device and computer readable medium for communications
WO2025156117A1 (fr) Dispositifs, procédés, et support de communication
US20250212228A1 (en) Methods, devices and computer readable media for communications
WO2024152214A1 (fr) Dispositif, procédé et support lisible par ordinateur pour configuration de ressources de liaison radio
WO2025025001A1 (fr) Dispositifs, procédés et supports lisibles par ordinateur pour communication de liaison latérale
WO2025025011A1 (fr) Dispositifs, procédés et supports lisibles par ordinateur pour communication de liaison latérale

Legal Events

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

Ref document number: 23960592

Country of ref document: EP

Kind code of ref document: A1