WO2025217821A1 - Dispositifs et procédés de transmission en sub-band full duplex - Google Patents

Dispositifs et procédés de transmission en sub-band full duplex

Info

Publication number
WO2025217821A1
WO2025217821A1 PCT/CN2024/088135 CN2024088135W WO2025217821A1 WO 2025217821 A1 WO2025217821 A1 WO 2025217821A1 CN 2024088135 W CN2024088135 W CN 2024088135W WO 2025217821 A1 WO2025217821 A1 WO 2025217821A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
sbfd
random access
access procedure
configuration information
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/088135
Other languages
English (en)
Inventor
Bohang ZHANG
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/088135 priority Critical patent/WO2025217821A1/fr
Publication of WO2025217821A1 publication Critical patent/WO2025217821A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H04L27/2605—Symbol extensions, e.g. Zero Tail, Unique Word [UW]
    • 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/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • 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/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • 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
    • 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
    • H04L5/1469—Two-way operation using the same type of signal, i.e. duplex using time-sharing
    • 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/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT
    • H04L5/0012—Hopping in multicarrier systems
    • 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/0001—Arrangements for dividing the transmission path
    • H04L5/0026—Division using four or more dimensions, e.g. beam steering or quasi-co-location [QCL]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • Example embodiments of the present disclosure generally relate to the field of communication techniques and in particular, to devices and methods for sub-band full duplex (SBFD) related transmission.
  • SBFD sub-band full duplex
  • Duplex communications have been proposed and developed. Generally, there are two duplexing modes: Frequency Division Duplex (FDD) for paired bands and Time Division Duplex (TDD) for unpaired bands.
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • SBFD has been proposed as a scheme of an enhanced duplex operation.
  • a terminal device comprising: a processor configured to cause the terminal device to: receive, from a network device, configuration information for a random access procedure to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether a random access procedure across a SBFD resource and a non-SBFD resource is allowed to be continued, or information about at least one resource on which the random access procedure is to be continued, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and transmit, to the network device, a message related to the random access procedure based on the configuration information.
  • SBFD sub-band full duplex
  • a network device comprising: a processor configured to cause the network device to: transmit, to a terminal device, configuration information for a random access procedure to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether a random access procedure across a SBFD resource and a non-SBFD resource is allowed to be continued, or information about at least one resource on which the random access procedure is to be continued, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and receive, from the terminal device, a message related to the random access procedure based on the configuration information.
  • SBFD sub-band full duplex
  • a terminal device comprising: a processor configured to cause the terminal device to: in response to a failure of receiving, from a network device, a message in a first random access procedure performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, select a random backoff time from an updated backoff time range, the updated backoff time range being determined based on a slot configured for uplink transmission which is after the SBFD resource in time domain; and transmit, to the network device, a random access preamble for a second random access procedure after the first random access procedure at the random backoff time.
  • SBFD sub-band full duplex
  • a terminal device comprising: a processor configured to cause the terminal device to: receive, from a network device, configuration information for an uplink transmission to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether the uplink transmission across a SBFD resource and a non-SBFD resource is allowed to be performed, or information about at least one resource on which the uplink transmission is to be performed, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and transmit, to the network device, the uplink transmission based on the configuration information.
  • SBFD sub-band full duplex
  • a network device comprising: a processor configured to cause the network device to: transmit, to a terminal device, configuration information for an uplink transmission to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether the uplink transmission across a SBFD resource and a non-SBFD resource is allowed to be performed, or information about at least one resource on which the uplink transmission is to be performed, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and receive, from the terminal device, the uplink transmission based on the configuration information.
  • SBFD sub-band full duplex
  • a communication method performed by a terminal device.
  • the method comprises: receiving, from a network device, configuration information for a random access procedure to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether a random access procedure across a SBFD resource and a non-SBFD resource is allowed to be continued, or information about at least one resource on which the random access procedure is to be continued, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and transmitting, to the network device, a message related to the random access procedure based on the configuration information.
  • SBFD sub-band full duplex
  • a communication method performed by a network device.
  • the method comprises: transmitting, to a terminal device, configuration information for a random access procedure to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether a random access procedure across a SBFD resource and a non-SBFD resource is allowed to be continued, or information about at least one resource on which the random access procedure is to be continued, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and receiving, from the terminal device, a message related to the random access procedure based on the configuration information.
  • SBFD sub-band full duplex
  • a communication method performed by a terminal device.
  • the method comprises: in response to a failure of receiving, from a network device, a message in a first random access procedure performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, selecting a random backoff time from an updated backoff time range, the updated backoff time range being determined based on a slot configured for uplink transmission which is after the SBFD resource in time domain; and transmitting, to the network device, a random access preamble for a second random access procedure after the first random access procedure at the random backoff time.
  • SBFD sub-band full duplex
  • a communication method performed by a terminal device.
  • the method comprises: receiving, from a network device, configuration information for an uplink transmission to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether the uplink transmission across a SBFD resource and a non-SBFD resource is allowed to be performed, or information about at least one resource on which the uplink transmission is to be performed, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and transmitting, to the network device, the uplink transmission based on the configuration information.
  • SBFD sub-band full duplex
  • a communication method performed by a network device.
  • the method comprises: transmitting, to a terminal device, configuration information for an uplink transmission to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether the uplink transmission across a SBFD resource and a non-SBFD resource is allowed to be performed, or information about at least one resource on which the uplink transmission is to be performed, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and receiving, from the terminal device, the uplink transmission based on the configuration information.
  • SBFD sub-band 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 carry out the method according to the sixth, seventh, eighth, ninth, or tenth aspect.
  • FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented
  • FIG. 2 illustrates a schematic diagram of an example of a random access procedure performed across SBFD slot and non-SBFD slot;
  • FIG. 3A illustrates a signaling flow of a random access procedure performed across SBFD slot and non-SBFD slot in accordance with some embodiments of the present disclosure
  • FIG. 3B illustrates a signaling flow of uplink transmission performed across SBFD slot and non-SBFD slot in accordance with some embodiments of the present disclosure
  • FIG. 4 illustrates a signaling flow of a random access procedure across SBFD in accordance with some embodiments of the present disclosure
  • FIG. 5 illustrates a flowchart of a method implemented at a terminal device according to some example embodiments of the present disclosure
  • FIG. 6 illustrates a flowchart of a method implemented at a network device according to some example embodiments of the present disclosure
  • FIG. 7 illustrates a flowchart of a method implemented at a terminal device according to some example embodiments of the present disclosure
  • FIG. 8 illustrates a flowchart of a method implemented at a terminal device according to some example embodiments of the present disclosure
  • FIG. 9 illustrates a flowchart of a method implemented at a network device according to some example embodiments of the present disclosure.
  • FIG. 10 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)
  • 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.
  • 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.
  • FIG. 2 illustrates a schematic diagram 200 of an example of a random access procedure performed across SBFD slot and non-SBFD slot.
  • SBFD resource for example, SBFD slots/symbols
  • Non-SBFD resource for example, Non-SBFD slots/symbols
  • DL or UL i.e., legacy/full DL/UL/flexible slots
  • FIG. 2 there illustrates one SBFD resource 202, and two non-SBFD resources 201 and 203. Both the non-SBFD resources 201 and 203 are for uplink (UL) transmission.
  • guard resource (s) may be used to separate UL sub-bands and DL sub-bands.
  • the guard resource (s) may be caused as guardband (s) in some cases.
  • RA random access
  • BW UL bandwidth
  • embodiments of the present disclosure propose solutions for controlling whether a terminal device can transmit within the SBFD slots and what to do with RA if the terminal device is not able to transmit within SBFD slots, so as to allow the terminal device to know its remapped time and frequency locations within SBFD slots.
  • the RA procedure 211 may be indicated with a resource 212 (named “RA continuation (CONT) ” ) in the non-SBFD resource 203 for UL transmission.
  • another RA procedure 221 may be indicated with a resource 222 for UL transmission in the SBFD resource 202 to continue the RA procedure.
  • a RA procedure with message 3 reception 231 may be indicated with a resource 232 for UL transmission in the SBFD resource 202 to continue the RA procedure.
  • FIG. 3A illustrates a signaling flow 300A of a random access procedure performed across SBFD slot and non-SBFD slot in accordance with some embodiments of the present disclosure.
  • the signaling flow 300A will be discussed with reference to FIG. 1, for example, by using the terminal device 110 (e.g., UE) and the network device 120 (e.g., gNB) .
  • the terminal device 110 e.g., UE
  • the network device 120 e.g., gNB
  • the network device 120 transmits (305) , to the terminal device 110, configuration information for a random access procedure to be performed across a SBFD resource and a non-SBFD resource.
  • the configuration information includes an indication whether a random access procedure across a SBFD resource and a non-SBFD resource is allowed to be continued, and/or information about at least one resource on which the random access procedure is to be continued, and/or other necessary information.
  • the at least one resource includes at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain.
  • the terminal device 110 receives (310) the configuration information from the network device 120. Accordingly, the terminal device 110 will have the knowledge about whether a random access procedure across a SBFD resource and a non-SBFD resource is allowed to be continued, for example, according to the explicit indication whether a random access procedure across a SBFD resource and a non-SBFD resource is allowed to be continued. Alternatively, if the terminal device 110 receives the information about at least one resource on which the random access procedure is to be continued, it may know that the random access procedure across a SBFD resource and a non-SBFD resource is allowed based on such “implicit” way of indication.
  • the transmission of the configuration information may be implemented in several ways. For example, it may be included in a random access response in the random access procedure, for example, Message 2 in a 4-step random access procedure. In this case, the configuration information may be indicated by one or more bits newly-added to the random access response.
  • the configuration information may be included in downlink control information for the random access response.
  • the configuration information may be indicated by reserved bits in the downlink control information and/or additional bits added to the downlink control information.
  • two of reserved bits in Message 2 of a 4-step random access procedure (Msg2) DCI may be selected to be used as information bits.
  • Msg2 RAR the reserved bits - (16 -A) bits for operation in a cell without shared spectrum access in frequency range 1 and frequency range 2-1, (18 -A) for operation in a cell with shared spectrum access in frequency range 1 or for operation in a cell in frequency range 2-2, where the value of A is the number of bits for the field of 'LSBs of SFN' as defined above. Wherein, the value of A may be taken as 2.
  • additional two bits can be added into reserved bits of information.
  • two of the reserved bits in Msg2 RAR can be selected to be used as information bits. Current MAC RAR does not have extra reserved bits available, so a new octet may be needed.
  • the information about at least one resource included in the configuration information may include either frequency information or time information of the at least one resource, or both.
  • indications for remapped SBFD RBs are needed.
  • the indication frequency location for remapping may be required.
  • the indication time location for remapping may be required.
  • the frequency information can be added to Msg2 DCI/RAR.
  • a 2-bit indication whether the RA is allowed to be continued occupies 2 reserved bits in Msg2 DCI, and if there are 14 reserved bits in Msg2 DCI, 12 reserved bits may remain. the reserved bits may be enough for frequency resource remapping. If not enough, there may be a need to change to RACH-ConfigCommon for set indications of frequency resources. In some embodiments, it may be possible with 12 bits if bandwidth of SBFD is narrow enough to not allow so many options (waiting on other RAN for BW size) .
  • frequency resources may be set to very basic design tables with default config values set in RACH-ConfigCommon, possible to limit down to 4 bits instead.
  • the frequency information is added to Msg2 RAR, with 14 bits usually required for frequency, 2 information bits combined with 14 bits for frequency will form 16 bits which forms a new octet.
  • a plurality of candidate frequency positions may be predetermined, e.g., according to specification, or preconfigured based on a RRC message, system information or other suitable message from the network device. Accordingly, the frequency information may just include an indication (for example, an index) of one or more candidate frequency positions. In this way, a frequency position allocated to the terminal device 110 can be indicated in a flexible way with very few bits.
  • exact values can be set through RRC or predetermined indicator values (like frequency hopping indicator) .
  • the length of the indication (1 or 2 bits) may be shortened at the cost of flexibility and it may be applicable if PUSCH can be a lot smaller in SBFD subject to RAN4 response.
  • the frequency information may be indicated through Msg4 DCI. If no reserved bits are available, some additional bits may be added to DCI 1_0 for this format.
  • the frequency information may be indicated through a frequency hopping-like indication. For example, exact values may be set through RRC or predetermined indicator values (like frequency hopping indicator) .
  • this can shorten the length of the indication (1 or 2 bits) at the cost of flexibility, and can extend to generalized PUCCH applications. For PUCCH that is a lot smaller in SBFD subject to RAN4 response, this embodiment may be also applicable.
  • the terminal device is allowed to continue RA across SBFD and non SBFD slots, leading to decreased RA latency.
  • an indication which indicates time location for RA remapping may be required, and thus may be included in the configuration information.
  • the frequency may need to be constantly remapped, and it is possible only minor timing adjustments may be required.
  • the reserved bits in Msg2 DCI may not be enough, and may require a new DCI format like frequency hopping indicator.
  • different amounts of octets may be required.
  • SBFD contention based random access the following to TS 38.133 6.2.2.2.4 UE behaviour when configured with SBFD may be added:
  • a UE configured with SBFD carrier shall use RACH configuration for the SBFD carrier contained in the RRC dedicated signalling. If the cell for the random access procedure is configured with SBFD, the UE shall transmit or re-transmit PRACH preamble on the SBFD carrier if the SS-RSRP measured by the UE on the DL carrier is higher than the rsrp-ThresholdSSB as defined in TS 38.331.
  • embodiments of the present disclosure propose the following.
  • the random access procedure is initiated to establish uplink time synchronization for a UE which either has not acquired or has lost its uplink synchronization, or to convey UE’s request Other SI, or for beam failure recovery.
  • the random access is specified in clause X of TS 38.213 and the control of the RACH transmission is specified in clause X of TS 38.321.
  • Two types of procedure are defined for the random access, the 4-step RA type, and the 2-step RA type (not yet confirmed, may need taking out) .
  • the decision on which type of procedure to adopt is as described in clause x of TS 38.321.
  • the configuration information may include a first threshold for a receiving power of a synchronization signal.
  • the first threshold may be larger than a first reference threshold of a receiving power of a synchronization signal determined based on one or more SBFD configurations of adjacent cells of a serving cell of the terminal device.
  • the terminal device 110 transmits (315) , to the network device 120, a message related to the random access procedure. Accordingly, the network device 120 receives (320) such message from the terminal device 110.
  • the message transmitted to the network device 120 may be, for example, a connection setup request in the random access procedure, for example, Message 3 in a 4-step random access procedure.
  • the message may be an acknowledgment to a connection setup response (for example, Message 4 in a 4-step random access procedure) in the random access procedure.
  • the message may include a retransmission of a preamble (e.g., Message 1 in a 4-step random access procedure or Message A in a 2-step random access procedure) in the random access procedure, or a preamble in a new random access procedure.
  • the netwrok device 120 informs the terminal device 110 (e.g., UE) if it is able to transmit inside SBFD slots for RA or to continue transmitting after SBFD slots.
  • the terminal device 110 e.g., UE
  • the above embodiments of the present disclosure allows UE to continue RA across SBFD and non SBFD slots, leading to decreased RA latency.
  • FIG. 3B illustrates a signaling flow 300B of uplink transmission performed across SBFD slot and non-SBFD slot in accordance with some embodiments of the present disclosure.
  • the signaling flow 300B will be discussed with reference to FIG. 1, for example, by using the terminal device 110 (e.g., UE) and the network device 120 (e.g., gNB) .
  • the terminal device 110 e.g., UE
  • the network device 120 e.g., gNB
  • the network device 120 transmits to the network device 110 transmits (355) , to the terminal device 110, configuration information for an uplink transmission to be performed across a SBFD resource and a non-SBFD resource.
  • the configuration information includes an indication whether the uplink transmission across a SBFD resource and a non-SBFD resource is allowed to be performed, and/or information about at least one resource on which the uplink transmission is to be performed, and/or other necessary information.
  • the at least one resource includes at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain.
  • the terminal device 110 receives (360) the configuration information from the network device 120. Accordingly, the terminal device 110 will have the knowledge about whether the uplink transmission across a SBFD resource and a non-SBFD resource is allowed to be continued, for example, according to the explicit indication whether the uplink transmission across a SBFD resource and a non-SBFD resource is allowed to be continued. Alternatively, if the terminal device 110 receives the information about at least one resource on which the uplink transmission is to be continued, it may know that the uplink transmission across a SBFD resource and a non-SBFD resource is allowed based on such “implicit” way of indication.
  • the transmission of the configuration information may be implemented in several ways. For example, it may be included in downlink control information transmitted from the network device 120. In this case, the configuration information may be indicated by reserved bits in the downlink control information and/or additional bits added to the downlink control information.
  • the information about at least one resource included in the configuration information may include either frequency information or time information of the at least one resource, or both.
  • a plurality of candidate frequency positions may be predetermined, e.g., according to specification, or preconfigured based on a RRC message, system information or other suitable message from the network device 120. Accordingly, the frequency information may just include an indication (for example, an index) of one or more candidate frequency positions. In this way, a frequency position allocated to the terminal device 110 can be indicated in a flexible way with very few bits.
  • the terminal device 110 Based on the configuration information received (360) from the network device 120, the terminal device 110 transmits (365) the uplink transmission to the network device 120. Accordingly, the network device 120 receives (370) the uplink transmission from the terminal device 110.
  • FIG. 4 illustrates a signaling flow 400 of a random access procedure across SBFD in accordance with some embodiments of the present disclosure.
  • the signaling flow 400 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 first detects whether a first random access procedure performed across a SBFD resource and a non-SBFD resource is successful. In response to a failure of receiving the message in the first random access procedure, the terminal device 110 selects (405) a random backoff time from an updated backoff time range.
  • the updated backoff time range may be determined based on a slot configured for uplink transmission which is after the SBFD resource in time domain. In some implementations, the updated backoff time range may be determined by adjusting a preconfigured backoff time range with a starting time of the slot.
  • the message in the first random access procedure may be, for example, a random access response in the first random access procedure, or a connection setup response in the first random access procedure.
  • the terminal device 110 transmits (410) , to the network device 120, a random access preamble for a second random access procedure after the first random access procedure at the random backoff time.
  • the network device 120 receives (415) the random access preamble and thus know the second random access procedure starts.
  • the terminal device 110 may determine that the failure of receiving the message in the first random access procedure occurs.
  • the terminal device 110 may determine that the failure of receiving the message in the first random access procedure occurs.
  • the message in the first random access procedure comprises at least one of: a random access response in the first random access procedure, or a connection setup response in the first random access procedure.
  • embodiments of the present disclosure set rules for random backoff time for Random access response reception or RA procedure, which ensures contention resolution specifications works with SBFD.
  • rules for random backoff time for Random access response reception may be set to ensure contention resolution specifications works with SBFD.
  • the UE may be allowed to continue RA across SBFD and non SBFD slots, so that RA latency can be decreased.
  • the random backoff time may be changed to uniform distribution between 0 and the PREAMBLE_BACKOFF+starting Time for the next slot configured for UL in tdd-UL-DL-ConfigCommon.
  • the random backoff time may be selected from the updated backoff time range as follows:
  • PREAMBLE_BACKOFF indicates the maximum value for the random backoff time
  • the updated is obtain based on a preconfigured backoff time range:
  • the random backoff time may be selected according to a uniform distribution between 0 and the PREAMBLE_BACKOFF. This indictates that RA starting outside of SBFD slots resolves its contention resolutions scheme outside of SBFD slots. It is worth noting that temporal position doesn't change SBFD's UE behavior.
  • rules for random backoff time for RA procedure may be set to ensure contention resolution specifications works with SBFD.
  • the random backoff time may be changed to uniform distribution between 0 and the PREAMBLE_BACKOFF+starting Time for the next slot configured for UL in tdd-UL-DL-ConfigCommon.
  • the random backoff time may be selected according to a uniform distribution between 0 and the PREAMBLE_BACKOFF. This dictates that RA starting outside of SBFD slots resolves its contention resolutions scheme outside of SBFD slots. It is worth noting that time location will not change UE behavior for SBFD.
  • FIG. 5 illustrates a flowchart of a communication method 500 implemented at a terminal device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 500 will be described from the perspective of the terminal device 110 in FIG. 1.
  • the terminal device 110 receives, from a network device, configuration information for a random access procedure to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether a random access procedure across a SBFD resource and a non-SBFD resource is allowed to be continued, or information about at least one resource on which the random access procedure is to be continued, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain.
  • SBFD sub-band full duplex
  • the terminal device 110 transmits, to the network device, a message related to the random access procedure based on the configuration information.
  • the configuration information is comprised in at least one of: a random access response in the random access procedure, or downlink control information for the random access response.
  • the configuration information is indicated by reserved bits in the downlink control information, or wherein the configuration information is indicated by one or more bits added to the random access response.
  • the information about at least one resource comprises at least one of frequency information or time information of the at least one resource.
  • the frequency information comprises an indication of at least one of candidate frequency positions, wherein the candidate frequency positions are predetermined or preconfigured based on at least one of a RRC message or system information from the network device.
  • the configuration information further comprises at least one of: a first threshold for a receiving power of a synchronization signal, the first threshold being larger than a first reference threshold of a receiving power of a synchronization signal determined based on one or more SBFD configurations of adjacent cells of a serving cell of the terminal device; a second threshold for a receiving power of a synchronization signal for a preamble in the random access procedure, the second threshold being larger than a second reference threshold of a receiving power of a synchronization signal for a preamble determined based on one or more SBFD configurations of the adjacent cells; a third threshold for a receiving power of a preamble in the random access procedure, the third threshold being larger than a third reference threshold determined based on one or more SBFD configurations of the adjacent cells; or a fourth threshold for a receiving power of a random access response in the random access procedure, the fourth threshold being less than a fourth reference threshold determined based on one or more SBFD configurations of the adjacent cells.
  • the message transmitted to the network device comprises at least one of: a connection setup request in the random access procedure, an acknowledgment to a connection setup response in the random access procedure, or a retransmission of a preamble in the random access procedure.
  • FIG. 6 illustrates a flowchart of a communication method 600 implemented at a network device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 600 will be described from the perspective of the network device 120 in FIG. 1.
  • the network device 120 transmits, to a terminal device, configuration information for a random access procedure to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether a random access procedure across a SBFD resource and a non-SBFD resource is allowed to be continued, or information about at least one resource on which the random access procedure is to be continued, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain.
  • SBFD sub-band full duplex
  • the network device 120 receives, from the terminal device, a message related to the random access procedure based on the configuration information.
  • the configuration information is comprised in at least one of: a random access response in the random access procedure, or downlink control information for the random access response.
  • the configuration information is indicated by reserved bits in the downlink control information, or wherein the configuration information is indicated by one or more bits added to the random access response.
  • the information about at least one resource comprises at least one of frequency information or time information of the at least one resource.
  • the frequency information comprises an indication of at least one of candidate frequency positions, wherein the candidate frequency positions are predetermined or preconfigured based on at least one of a RRC message or system information from the network device.
  • the configuration information further comprises at least one of: a first threshold for a receiving power of a synchronization signal, the first threshold being larger than a first reference threshold of a receiving power of a synchronization signal determined based on one or more SBFD configurations of adjacent cells of a serving cell of the terminal device; a second threshold for a receiving power of a synchronization signal for a preamble in the random access procedure, the second threshold being larger than a second reference threshold of a receiving power of a synchronization signal for a preamble determined based on one or more SBFD configurations of the adjacent cells; a third threshold for a receiving power of a preamble in the random access procedure, the third threshold being larger than a third reference threshold determined based on one or more SBFD configurations of the adjacent cells; or a fourth threshold for a receiving power of a random access response in the random access procedure, the fourth threshold being less than a fourth reference threshold determined based on one or more SBFD configurations of the adjacent cells.
  • the message transmitted to the network device comprises at least one of: a connection setup request in the random access procedure, an acknowledgment to a connection setup response in the random access procedure, or a retransmission of a preamble in the random access procedure.
  • FIG. 7 illustrates a flowchart of a communication method 700 implemented at a terminal device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 700 will be described from the perspective of the terminal device 110 in FIG. 1.
  • the terminal device 110 in response to a failure of receiving, from a network device, a message in a first random access procedure performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, selects a random backoff time from an updated backoff time range, the updated backoff time range being determined based on a slot configured for uplink transmission which is after the SBFD resource in time domain.
  • SBFD sub-band full duplex
  • the terminal device 110 transmits, to the network device, a random access preamble for a second random access procedure after the first random access procedure at the random backoff time.
  • the failure of receiving the message in the first random access procedure comprises at least one of the following events: a random access response in the first random access procedure is not received but a timer configured for the random access response expires, or a connection setup response in the first random access procedure is unsuccessfully received.
  • the updated backoff time range is determined by adjusting a preconfigured backoff time range with a starting time of the slot.
  • the message in the first random access procedure comprises at least one of: a random access response in the first random access procedure, or a connection setup response in the first random access procedure.
  • FIG. 8 illustrates a flowchart of a communication method 800 implemented at a terminal device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 800 will be described from the perspective of the terminal device 110 in FIG. 1.
  • the terminal device 110 receive, from a network device, configuration information for an uplink transmission to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether the uplink transmission across a SBFD resource and a non-SBFD resource is allowed to be performed, or information about at least one resource on which the uplink transmission is to be performed, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain.
  • SBFD sub-band full duplex
  • the terminal device 110 transmits, to the network device, the uplink transmission based on the configuration information.
  • FIG. 9 illustrates a flowchart of a communication method 900 implemented at a network device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 900 will be described from the perspective of the network device 120 in FIG. 1.
  • the network device 120 transmits, to a terminal device, configuration information for an uplink transmission to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether the uplink transmission across a SBFD resource and a non-SBFD resource is allowed to be performed, or information about at least one resource on which the uplink transmission is to be performed, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain.
  • SBFD sub-band full duplex
  • the network device 120 receives, from the terminal device, the uplink transmission based on the configuration information.
  • FIG. 10 is a simplified block diagram of a device 1000 that is suitable for implementing embodiments of the present disclosure.
  • the device 1000 can be considered as a further example implementation of any of the devices as shown in FIG. 1. Accordingly, the device 1000 can be implemented at or as at least a part of the terminal device 110 or the network device 120.
  • 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 1020 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 to 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 comprising a circuitry.
  • the circuitry is configured to: receive, from a network device, configuration information for a random access procedure to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether a random access procedure across a SBFD resource and a non-SBFD resource is allowed to be continued, or information about at least one resource on which the random access procedure is to be continued, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and transmit, to the network device, a message related to the random access procedure based on the configuration information.
  • 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, configuration information for a random access procedure to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether a random access procedure across a SBFD resource and a non-SBFD resource is allowed to be continued, or information about at least one resource on which the random access procedure is to be continued, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and receive, from the terminal device, a message related to the random access procedure based on the configuration information.
  • the circuitry may be configured to perform any method implemented by the network device as discussed above.
  • a terminal device comprising a circuitry.
  • the circuitry is configured to: in response to a failure of receiving, from a network device, a message in a first random access procedure performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, select a random backoff time from an updated backoff time range, the updated backoff time range being determined based on a slot configured for uplink transmission which is after the SBFD resource in time domain; and transmit, to the network device, a random access preamble for a second random access procedure after the first random access procedure at the random backoff time.
  • 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, configuration information for an uplink transmission to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether the uplink transmission across a SBFD resource and a non-SBFD resource is allowed to be performed, or information about at least one resource on which the uplink transmission is to be performed, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and transmit, to the network device, the uplink transmission based on the configuration information.
  • 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, configuration information for an uplink transmission to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether the uplink transmission across a SBFD resource and a non-SBFD resource is allowed to be performed, or information about at least one resource on which the uplink transmission is to be performed, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and receive, from the terminal device, the uplink transmission based on the configuration information.
  • the circuitry may be configured to perform any method implemented by the network 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 needed 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 apparatus comprises means for receiving, from a network device, configuration information for a random access procedure to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: means for an indication whether a random access procedure across a SBFD resource and a non-SBFD resource is allowed to be continued, or means for information about at least one resource on which the random access procedure is to be continued, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and means for transmitting, to the network device, a message related to the random access procedure based on the configuration information.
  • SBFD sub-band full duplex
  • the first apparatus may comprise means for performing the respective operations of the method 500. In some example embodiments, the first apparatus may further comprise means for performing other operations in some example embodiments of the method 500.
  • the means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
  • a network apparatus comprises means for transmitting, to a terminal device, configuration information for a random access procedure to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: means for an indication whether a random access procedure across a SBFD resource and a non-SBFD resource is allowed to be continued, or means for information about at least one resource on which the random access procedure is to be continued, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and means for receiving, from the terminal device, a message related to the random access procedure based on the configuration information.
  • SBFD sub-band full duplex
  • the second apparatus may comprise means for performing the respective operations of the method 600. In some example embodiments, the second apparatus may further comprise means for performing other operations in some example embodiments of the method 600.
  • the means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
  • a terminal apparatus comprises means for in response to a failure of receiving, from a network device, a message in a first random access procedure performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, selecting a random backoff time from an updated backoff time range, the updated backoff time range being determined based on a slot configured for uplink transmission which is after the SBFD resource in time domain; and means for transmitting, to the network device, a random access preamble for a second random access procedure after the first random access procedure at the random backoff time.
  • the third apparatus may comprise means for performing the respective operations of the method 700.
  • the third apparatus may further comprise means for performing other operations in some example embodiments of the method 700.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • a terminal apparatus comprises means for receiving, from a network device, configuration information for an uplink transmission to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: means for an indication whether the uplink transmission across a SBFD resource and a non-SBFD resource is allowed to be performed, or means for information about at least one resource on which the uplink transmission is to be performed, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and means for transmitting, to the network device, the uplink transmission based on the configuration information.
  • SBFD sub-band full duplex
  • the fourth apparatus may comprise means for performing the respective operations of the method 800. In some example embodiments, the fourth apparatus may further comprise means for performing other operations in some example embodiments of the method 800.
  • the means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
  • a network apparatus comprises means for transmitting, to a terminal device, configuration information for an uplink transmission to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: means for an indication whether the uplink transmission across a SBFD resource and a non-SBFD resource is allowed to be performed, or means for information about at least one resource on which the uplink transmission is to be performed, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and means for receiving, from the terminal device, the uplink transmission based on the configuration information.
  • SBFD sub-band full duplex
  • the fifth apparatus may comprise means for performing the respective operations of the method 900. In some example embodiments, the fifth apparatus may further comprise means for performing other operations in some example embodiments of the method 900.
  • the means may be implemented in any suitable form. For example, 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, configuration information for a random access procedure to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of:an indication whether a random access procedure across a SBFD resource and a non-SBFD resource is allowed to be continued, or information about at least one resource on which the random access procedure is to be continued, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and transmit, to the network device, a message related to the random access procedure based on the configuration information.
  • SBFD sub-band full duplex
  • the configuration information is comprised in at least one of: a random access response in the random access procedure, or downlink control information for the random access response.
  • the configuration information is indicated by reserved bits in the downlink control information, or wherein the configuration information is indicated by one or more bits added to the random access response.
  • the information about at least one resource comprises at least one of frequency information or time information of the at least one resource.
  • the frequency information comprises an indication of at least one of candidate frequency positions, wherein the candidate frequency positions are predetermined or preconfigured based on at least one of a RRC message or system information from the network device.
  • the configuration information further comprises at least one of: a first threshold for a receiving power of a synchronization signal, the first threshold being larger than a first reference threshold of a receiving power of a synchronization signal determined based on one or more SBFD configurations of adjacent cells of a serving cell of the terminal device; a second threshold for a receiving power of a synchronization signal for a preamble in the random access procedure, the second threshold being larger than a second reference threshold of a receiving power of a synchronization signal for a preamble determined based on one or more SBFD configurations of the adjacent cells; a third threshold for a receiving power of a preamble in the random access procedure, the third threshold being larger than a third reference threshold determined based on one or more SBFD configurations of the adjacent cells; or a fourth threshold for a receiving power of a random access response in the random access procedure, the fourth threshold being less than a fourth reference threshold determined based on one or more SBFD configurations of the adjacent cells.
  • the message transmitted to the network device comprises at least one of: a connection setup request in the random access procedure, an acknowledgment to a connection setup response in the random access procedure, or a retransmission of a preamble in the random access procedure.
  • a network device comprising: a processor configured to cause the network device to: transmit, to a terminal device, configuration information for a random access procedure to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether a random access procedure across a SBFD resource and a non- SBFD resource is allowed to be continued, or information about at least one resource on which the random access procedure is to be continued, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and receive, from the terminal device, a message related to the random access procedure based on the configuration information.
  • SBFD sub-band full duplex
  • the configuration information is comprised in at least one of: a random access response in the random access procedure, or downlink control information for the random access response.
  • the configuration information is indicated by reserved bits in the downlink control information, or wherein the configuration information is indicated by one or more bits added to the random access response.
  • the information about at least one resource comprises at least one of frequency information or time information of the at least one resource.
  • the frequency information comprises an indication of at least one of candidate frequency positions, wherein the candidate frequency positions are predetermined or preconfigured based on at least one of a RRC message or system information from the network device.
  • the configuration information further comprises at least one of: a first threshold for a receiving power of a synchronization signal, the first threshold being larger than a first reference threshold of a receiving power of a synchronization signal determined based on one or more SBFD configurations of adjacent cells of a serving cell of the terminal device; a second threshold for a receiving power of a synchronization signal for a preamble in the random access procedure, the second threshold being larger than a second reference threshold of a receiving power of a synchronization signal for a preamble determined based on one or more SBFD configurations of the adjacent cells; a third threshold for a receiving power of a preamble in the random access procedure, the third threshold being larger than a third reference threshold determined based on one or more SBFD configurations of the adjacent cells; or a fourth threshold for a receiving power of a random access response in the random access procedure, the fourth threshold being less than a fourth reference threshold determined based on one or more SBFD configurations of the adjacent cells.
  • the message transmitted to the network device comprises at least one of: a connection setup request in the random access procedure, an acknowledgment to a connection setup response in the random access procedure, or a retransmission of a preamble in the random access procedure.
  • a terminal device comprising: a processor configured to cause the terminal device to: in response to a failure of receiving, from a network device, a message in a first random access procedure performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, select a random backoff time from an updated backoff time range, the updated backoff time range being determined based on a slot configured for uplink transmission which is after the SBFD resource in time domain; and transmit, to the network device, a random access preamble for a second random access procedure after the first random access procedure at the random backoff time.
  • SBFD sub-band full duplex
  • the failure of receiving the message in the first random access procedure comprises at least one of the following events: a random access response in the first random access procedure is not received but a timer configured for the random access response expires, or a connection setup response in the first random access procedure is unsuccessfully received.
  • the updated backoff time range is determined by adjusting a preconfigured backoff time range with a starting time of the slot.
  • the message in the first random access procedure comprises at least one of: a random access response in the first random access procedure, or a connection setup response in the first random access procedure.
  • a terminal device comprising: a processor configured to cause the terminal device to: receive, from a network device, configuration information for an uplink transmission to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether the uplink transmission across a SBFD resource and a non-SBFD resource is allowed to be performed, or information about at least one resource on which the uplink transmission is to be performed, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and transmit, to the network device, the uplink transmission based on the configuration information.
  • SBFD sub-band full duplex
  • a network device comprising: a processor configured to cause the network device to: transmit, to a terminal device, configuration information for an uplink transmission to be performed across a sub-band full duplex (SBFD) resource and a non-SBFD resource, the configuration information comprising at least one of: an indication whether the uplink transmission across a SBFD resource and a non-SBFD resource is allowed to be performed, or information about at least one resource on which the uplink transmission is to be performed, wherein the at least one resource comprises at least a part of the SBFD resource or a non-SBFD resource after the SBFD resource in time domain; and receive, from the terminal device, the uplink transmission based on the configuration information.
  • SBFD sub-band full duplex
  • 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 10.
  • 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)
  • 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 pour une transmission en sub-band full duplex (SBFD) Dans un procédé, un dispositif terminal reçoit, en provenance d'un dispositif de réseau, des informations de configuration pour une procédure d'accès aléatoire à effectuer à travers une ressource SBFD et une ressource non SBFD. Les informations de configuration comprennent au moins l'un des éléments suivants : une indication précisant si une procédure d'accès aléatoire à travers une ressource SBFD et une ressource non SBFD est autorisée à être poursuivie, ou des informations concernant au moins une ressource sur laquelle la procédure d'accès aléatoire doit être poursuivie, la ou les ressources comprenant au moins une partie de la ressource SBFD ou une ressource non SBFD après la ressource SBFD dans le domaine temporel. Le dispositif terminal transmet ensuite, au dispositif de réseau, un message relatif à la procédure d'accès aléatoire sur la base des informations de configuration.
PCT/CN2024/088135 2024-04-16 2024-04-16 Dispositifs et procédés de transmission en sub-band full duplex Pending WO2025217821A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/088135 WO2025217821A1 (fr) 2024-04-16 2024-04-16 Dispositifs et procédés de transmission en sub-band full duplex

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/088135 WO2025217821A1 (fr) 2024-04-16 2024-04-16 Dispositifs et procédés de transmission en sub-band full duplex

Publications (1)

Publication Number Publication Date
WO2025217821A1 true WO2025217821A1 (fr) 2025-10-23

Family

ID=97402827

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/088135 Pending WO2025217821A1 (fr) 2024-04-16 2024-04-16 Dispositifs et procédés de transmission en sub-band full duplex

Country Status (1)

Country Link
WO (1) WO2025217821A1 (fr)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116488781A (zh) * 2022-01-17 2023-07-25 华为技术有限公司 通信方法和通信装置
WO2023148773A1 (fr) * 2022-02-03 2023-08-10 Centre Of Excellence In Wireless Technology Mise en œuvre d'un duplexage complet de sous-bande dans un réseau cellulaire
CN116830518A (zh) * 2023-05-08 2023-09-29 北京小米移动软件有限公司 接收、接收指示方法和装置、通信装置及存储介质
CN116830739A (zh) * 2023-05-09 2023-09-29 北京小米移动软件有限公司 通信方法、装置、设备及存储介质
CN116848923A (zh) * 2023-05-08 2023-10-03 北京小米移动软件有限公司 发送确定、发送指示方法和装置、通信装置及存储介质
CN117296428A (zh) * 2023-08-10 2023-12-26 北京小米移动软件有限公司 上行传输资源的确定方法和通信装置、设备及存储介质
CN117856994A (zh) * 2022-09-30 2024-04-09 维沃移动通信有限公司 灵活双工sbfd信息指示方法、终端及网络侧设备

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116488781A (zh) * 2022-01-17 2023-07-25 华为技术有限公司 通信方法和通信装置
WO2023148773A1 (fr) * 2022-02-03 2023-08-10 Centre Of Excellence In Wireless Technology Mise en œuvre d'un duplexage complet de sous-bande dans un réseau cellulaire
CN117856994A (zh) * 2022-09-30 2024-04-09 维沃移动通信有限公司 灵活双工sbfd信息指示方法、终端及网络侧设备
CN116830518A (zh) * 2023-05-08 2023-09-29 北京小米移动软件有限公司 接收、接收指示方法和装置、通信装置及存储介质
CN116848923A (zh) * 2023-05-08 2023-10-03 北京小米移动软件有限公司 发送确定、发送指示方法和装置、通信装置及存储介质
CN116830739A (zh) * 2023-05-09 2023-09-29 北京小米移动软件有限公司 通信方法、装置、设备及存储介质
CN117296428A (zh) * 2023-08-10 2023-12-26 北京小米移动软件有限公司 上行传输资源的确定方法和通信装置、设备及存储介质

Similar Documents

Publication Publication Date Title
WO2023245669A1 (fr) Procédé, dispositif et support de stockage informatique de communication
US20250175810A1 (en) Methods, devices, and computer readable medium for communication
WO2024192688A1 (fr) Dispositif, procédé et support lisible par ordinateur pour communication
US20250175951A1 (en) Methods, devices, and computer readable medium for communication
WO2023184273A1 (fr) Procédé, dispositif, et support de stockage informatique destinés à la communication
WO2023133829A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2025217821A1 (fr) Dispositifs et procédés de transmission en sub-band full duplex
US20250175963A1 (en) Method, device and computer redable medium of communication
WO2025213424A1 (fr) Dispositif, procédé et support lisible par ordinateur pour les communications
WO2025199686A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications
WO2025030289A1 (fr) Dispositifs et procédés de communication
WO2025020196A1 (fr) Dispositifs et procédés de communication
WO2025091402A1 (fr) Dispositifs et procédés de communication
WO2026065476A1 (fr) Dispositif, procédé et support lisible par ordinateur pour la communication
WO2025199980A1 (fr) Dispositifs et procédés de communication
WO2024229837A1 (fr) Dispositifs et procédés de communication
WO2024229830A1 (fr) Dispositifs, procédés, et support de communication
WO2025015446A1 (fr) Dispositifs et procédés de communication
WO2024197899A1 (fr) Procédés, dispositifs et support de communication
WO2024152214A1 (fr) Dispositif, procédé et support lisible par ordinateur pour configuration de ressources de liaison radio
WO2024197725A1 (fr) Dispositif et procédé de communication
WO2024103363A1 (fr) Procédé, dispositif et support d'enregistrement informatique de communication
WO2025231772A1 (fr) Dispositifs et procédés de communication
WO2025194468A1 (fr) Dispositifs et procédés de communication
WO2024103364A1 (fr) Procédé, dispositif et support d'enregistrement informatique de communication

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

Country of ref document: EP

Kind code of ref document: A1