Methods and devices for subband-based full-duplex random access
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2026-02-06
- Publication Date
- 2026-08-13
Smart Images

Figure SE2026050087_13082026_PF_FP_ABST
Abstract
Description
[0001] Telefonaktiebolaget LM Ericsson (pu bl) 1 / 54
[0002] P112973WO01
[0003] Methods and devices for subband-based full-duplex random access
[0004] Technical Field
[0005] The present disclosure relates to a technique for subband-based full-duplex (also: subband full-duplex or SBFD) random access (RA). More specifically, and without limitation, methods and devices for random access and for configuring such random access are provided.
[0006] Background
[0007] High-performance mobile communications systems, e.g. specified by the Third Generation Partnership Project (3GPP) or guided by frameworks such as the O-RAN Alliance, evolve to address growing demands for data throughput, low latency, and efficient utilization of spectrum. In line with these technical specifications, wireless radio access technologies increasingly adopt diverse duplexing schemes to improve coverage, quality of service, and overall system capacity.
[0008] In such next-generation radio access networks, seamless connectivity and coordination between user equipment (UE) and network nodes are crucial.
[0009] Achieving robust transmission requires scalable mechanisms that account for interference, channel conditions, and dynamic spectrum allocation. These aspects become even more pivotal when subband-based full-duplex (SBFD) concepts are introduced.
[0010] However, existing techniques do not adequately reconciling resource usage across subband divisions for random access procedures, especially for network requirements such as range extension.
[0011] Summary
[0012] Accordingly, there is a need for a subband-based full-duplex radio access technique that enables range-extended random access. The proposed solutions enable an SBFD-aware UE to perform random access in an SBFD cell in which SBFD random access is enabled. Thereby, the SBFD-aware UE can leverage SBFD RATelefonaktiebolaget LM Ericsson (pu bl) 2 / 54
[0013] P112973WO01
[0014] occasions (ROs) and avoid legacy ROs, in turn allowing for longer range and better coverage and increased RA capacity and reduced RA latency for the network. As to a first aspect, a method performed by a radio device for random access (RA) in a radio access network (RAN) is provided. The method comprises: obtaining from a network node in the RAN an uplink grant allocating a resource for a first transmission of a message in a RA procedure, wherein a symbol type of the allocated resource is either SBFD or non-subband-full-duplex (non-SBFD); and transmitting one or more repeated transmissions of the message in a subsequent required number of slots, each repeated transmission being restricted to a valid symbol type being the symbol type of the allocated resource of the first transmission.
[0015] The first aspect may be implemented alone or in combination with any one of the embodiments in the following embodiments.
[0016] In one embodiment, a slot is counted in the required number of slots based on a slot counting rule associated with the valid symbol type.
[0017] In one embodiment, the slot counting rule associated with the valid symbol type comprises at least one of: in case the valid symbol type is SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all SBFD symbol; in case the valid symbol type is non-SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all non-SBFD symbol; or a slot containing a transmission that is not in the valid symbol type is not counted in the required number of slots.
[0018] In one embodiment, the message is message-3 of the RA procedure.
[0019] In one embodiment, the method may further comprise: counting the required number of slots to reach a required number of repeated transmissions of the message.
[0020] In one embodiment, the valid symbol type is non-SBFD, and a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a physical uplink control channel (PUSCH) of the repeated transmission does not include a symbolTelefonaktiebolaget LM Ericsson (pu bl) 3 / 54
[0021] P112973WO01
[0022] - indicated as downlink by tdd-UL-DL-ConfigurationCommon, and / or
[0023] - indicated as a symbol of an SS / PBCH block, SSB, with index provided by ssb- PositionsInBurst and / or
[0024] - indicated as a symbol type being SBFD by tdd-UL-DL-ConfigurationCommon.
[0025] In one embodiment, the valid symbol type is SBFD, and a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a PUSCH of the repeated transmission only includes symbols indicated as SBFD symbols by tdd-UL-DL-ConfigurationCommon.
[0026] In one embodiment, the valid symbol type is SBFD, and a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a PUSCH of the repeated transmission does not include a symbol
[0027] - indicated as a non-SBFD symbol by tdd-UL-DL-ConfigurationCommon and / or
[0028] - indicated as a symbol of an SS / PBCH block, SSB, by ssb-PositionsInBurst.
[0029] By consistent handling of repeated message transmissions in random access, embodiments can maintain robust communication performance (e.g., for range extension).
[0030] As to a second aspect, a method performed by a network node for random access in a radio access network is provided. The method comprises: providing to a radio device in the RAN an uplink grant allocating a resource for a first transmission of a message in a RA procedure, wherein a symbol type of the allocated resource is either SBFD or non-SBFD; and receiving one or more repeated transmissions of the message in a subsequent required number of slots, each repeated transmission being restricted to a valid symbol type being the symbol type of the allocated resource of the first transmission.
[0031] The second aspect may be implemented alone or in combination with any one of the embodiments in the following embodiments.
[0032] In one embodiment, a slot is counted in the required number of slots based on a slot counting rule associated with the valid symbol type.Telefonaktiebolaget LM Ericsson (pu bl) 4 / 54
[0033] P112973WO01
[0034] In one embodiment, the slot counting rule associated with the valid symbol type comprises at least one of: in case the valid symbol type is SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all SBFD symbol; in case the valid symbol type is non-SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all non-SBFD symbol; or a slot containing a transmission that is not in the valid symbol type is not counted in the required number of slots.
[0035] In one embodiment, the message is message-3 of the RA procedure.
[0036] In one embodiment, the method may comprise: counting the required number of slots to reach a required number of repeated transmissions of the message.
[0037] In one embodiment, the valid symbol type is non-SBFD, and a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a PUSCH of the repeated transmission does not include a symbol
[0038] - indicated as downlink by tdd-UL-DL-ConfigurationCommon, and / or
[0039] - indicated as a symbol of an SS / PBCH block, SSB, with index provided by ssb- PositionsInBurst and / or
[0040] - indicated as a symbol type being SBFD by tdd-UL-DL-ConfigurationCommon.
[0041] In one embodiment, the valid symbol type is SBFD, and a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a PUSCH of the repeated transmission only includes symbols indicated as SBFD symbols by tdd-UL-DL-ConfigurationCommon.
[0042] In one embodiment, the valid symbol type is SBFD, and a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a PUSCH of the repeated transmission does not include a symbol
[0043] - indicated as a non-SBFD symbol by tdd-UL-DL-ConfigurationCommon and / or
[0044] - indicated as a symbol of an SS / PBCH block, SSB, by ssb-PositionsInBurst.Telefonaktiebolaget LM Ericsson (pu bl) 5 / 54
[0045] P112973WO01
[0046] The second aspect may further comprise any feature and / or any step disclosed in the context of the first aspect, or a feature and / or step corresponding thereto, e.g., a receiver counterpart to a transmitter feature or step.
[0047] Alternatively or in addition, any aspect may be implemented as a method of slot counting for message transmission (e.g., repetitions of Msg3) in PUSCH in Subband Full Duplex (SBFD), e.g., in SBFD random access and / or Msg3 PUSCH repetitions.
[0048] Alternatively or in addition, any embodiment may be a method for slot counting that takes into account a slot type, e.g. with respect to SBFD and non-SBFD symbols, included in the slot.
[0049] Alternatively or in addition, implementations of the methods may modify an existing slot counting, e.g. for Msg3 repetitions, such that it is possible to differentiate the counter between SBFD and non-SBFD symbols.
[0050] As to a third aspect, a radio device comprising memory operable to store instructions and processing circuitry operable to execute the instructions is provided. The radio device is operable to: obtain, from a network node in a RAN, an uplink grant allocating a resource for a first transmission of a message in a RA procedure, wherein a symbol type of the allocated resource is either SBFD or non-SBFD; and transmit one or more repeated transmissions of the message in a subsequent required number of slots, each repeated transmission being restricted to a valid symbol type being the valid symbol type of the allocated resource of the first transmission.
[0051] In one embodiment, a slot is counted in the required number of slots based on a slot counting rule associated with the valid symbol type.
[0052] In one embodiment, the slot counting rule associated with the valid symbol type comprises at least one of: in case the valid symbol type is SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all SBFD symbol; in case the valid symbol type is non-SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all non-SBFD symbol; or a slot containing a transmission that is not in the valid symbol type is not counted in the required number of slots.Telefonaktiebolaget LM Ericsson (pu bl) 6 / 54
[0053] P112973WO01
[0054] In one embodiment, the message is message-3 of the RA procedure.
[0055] In one embodiment, the radio device is further configured to count the required number of slots to reach a required number of repeated transmissions of the message.
[0056] In one embodiment, the valid symbol type is non-SBFD, and a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a PUSCH of the repeated transmission does not include a symbol
[0057] - indicated as downlink by tdd-UL-DL-ConfigurationCommon, and / or
[0058] - indicated as a symbol of an SS / PBCH block, SSB, with index provided by ssb- PositionsInBurst and / or
[0059] - indicated as a symbol type being SBFD by tdd-UL-DL-ConfigurationCommon.
[0060] In one embodiment, the valid symbol type is SBFD, and a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a PUSCH of the repeated transmission only includes symbols indicated as SBFD symbols by tdd-UL-DL-ConfigurationCommon.
[0061] In one embodiment, the valid symbol type is SBFD, and a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a PUSCH of the repeated transmission does not include a symbol
[0062] - indicated as a non-SBFD symbol by tdd-UL-DL-ConfigurationCommon and / or
[0063] - indicated as a symbol of an SS / PBCH block, SSB, by ssb-PositionsInBurst.
[0064] According to a fourth aspect, a radio device for RA in a RAN is provided. The radio device is configured to: obtain, from a network node in the RAN, an uplink grant allocating a resource for a first transmission of a message in a RA procedure, a symbol type of the allocated resource is either SBFD or non-SBFD; and transmit one or more repeated transmissions of the message in a subsequent requiredTelefonaktiebolaget LM Ericsson (pu bl) 7 / 54
[0065] P112973WO01
[0066] number of slots, each repeated transmission being restricted to a valid symbol type being the symbol type of the allocated resource of the first transmission.
[0067] In further embodiments, the radio device is configured to comprise any feature and / or perform any step disclosed in the context of the first aspect.
[0068] According to a fifth aspect, a network node comprising memory operable to store instructions and processing circuitry operable to execute the instructions is provided, such that the network node is operable to: provide, to a radio device, an uplink grant allocating a resource for a first transmission of a message in a RA procedure, wherein a symbol type of the allocated resource is either SBFD or non-SBFD; and receive one or more repeated transmissions of the message in a subsequent required number of slots, each repeated transmission being restricted to a valid symbol type being the symbol type of the allocated resource of the first transmission.
[0069] In one embodiment, a slot is counted in the required number of slots based on a slot counting rule associated with the valid symbol type.
[0070] In one embodiment, the slot counting rule associated with the valid symbol type comprises at least one of: in case the valid symbol type is SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all SBFD symbol; in case the valid symbol type is non-SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all non-SBFD symbol; or a slot containing a transmission that is not in the valid symbol type is not counted in the required number of slots.
[0071] In one embodiment, the message is message-3 of the RA procedure.
[0072] In one embodiment, the network node is further operable to count the required number of slots to reach a required number of repeated transmissions of the message.
[0073] In one embodiment, the valid symbol type is non-SBFD, and a slot is counted in the required number of slots for transmitting the repeated transmission of theTelefonaktiebolaget LM Ericsson (pu bl) 8 / 54
[0074] P112973WO01
[0075] message if the slot allocated for a PUSCH of the repeated transmission does not include a symbol
[0076] - indicated as downlink by tdd-UL-DL-ConfigurationCommon, and / or
[0077] - indicated as a symbol of an SS / PBCH block, SSB, with index provided by ssb- PositionsInBurst and / or
[0078] - indicated as a symbol type being SBFD by tdd-UL-DL-ConfigurationCommon.
[0079] In one embodiment, the valid symbol type is SBFD, and a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a PUSCH of the repeated transmission only includes symbols indicated as SBFD symbols by tdd-UL-DL-ConfigurationCommon.
[0080] In one embodiment, the valid symbol type is SBFD, and a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a PUSCH of the repeated transmission does not include a symbol
[0081] - indicated as a non-SBFD symbol by tdd-UL-DL-ConfigurationCommon and / or
[0082] - indicated as a symbol of an SS / PBCH block, SSB, by ssb-PositionsInBurst.
[0083] According to a sixth aspect, a network node in a RAN is provided. The network node is configured to: provide, to a radio device, an uplink grant allocating a resource for a first transmission of a message in a RA procedure, wherein a symbol type of the allocated resource is either SBFD or non-SBFD; and receive one or more repeated transmissions of the message in a subsequent required number of slots, each repeated transmission being restricted to a valid symbol type being the symbol type of the allocated resource of the first transmission.
[0084] In further embodiments, the network node is configured to comprise any feature and / or perform any step disclosed in the context of the second aspect.
[0085] Brief Description of the Drawings
[0086] Further details of embodiments of the technique are described with reference to the enclosed drawings, wherein:Telefonaktiebolaget LM Ericsson (pu bl) 9 / 54
[0087] P112973WO01
[0088] Fig. 1 shows a schematic block diagram of an embodiment of a device for random access;
[0089] Fig. 2 shows a schematic block diagram of an embodiment of a device for supporting, providing, or configuring random access;
[0090] Fig. 3 shows a flowchart for a method of performing random access, which method may be implementable by the device of Fig. 1;
[0091] Fig. 4 shows a flowchart for a method of supporting, providing, or configuring random access, which method may be implementable by the device of Fig. 2;
[0092] Fig. 5 schematically illustrates a first example of a radio network comprising embodiments of the devices of Figs. 1 and 2 performing the methods of Figs. 3 and 4;
[0093] Fig. 6 schematically illustrates a time-frequency grid of radio resources used or usable in any embodiment;
[0094] Figs. 7 to 9 schematically illustrates FDD and TDD;
[0095] Fig. 10 schematically illustrates FDD and TDD;
[0096] Fig. 11 schematically illustrates lEs for indicating UL and DL and Flexible configurations of slots and symbols;
[0097] Figs. 12 to 14 schematically illustrate example configurations on the slot level;
[0098] Figs. 15 and 16 schematically illustrate a non-SBFD configuration in time and frequency;
[0099] Figs. 17 and 18 schematically illustrate an SBFD configuration in time and frequency;
[0100] Figs. 19 and 20 schematically illustrate guardbands in two different SBFD
[0101] configurations;Telefonaktiebolaget LM Ericsson (pu bl) 10 / 54
[0102] P112973WO01
[0103] Figs. 21 and 22 illustrate example of counting slot for repeated message transmission depending on symbol type;
[0104] Fig. 23 shows a flowchart for a method of performing random access, which method may be implementable by the device of Fig. 1;
[0105] Fig. 24 shows a flowchart for a method of supporting, providing, or configuring random access, which method may be implementable by the device of Fig. 2;
[0106] Fig. 25 shows a schematic block diagram of a radio device embodying the device of Fig. 1;
[0107] Fig. 26 shows a schematic block diagram of a radio access network or network node embodying the device of Fig. 2; and
[0108] Fig. 27 schematically illustrates an example telecommunication network connected via an intermediate network to a host computer.
[0109] Detailed Description
[0110] In the following description, for purposes of explanation and not limitation, specific details are set forth, such as a specific network environment in order to provide a thorough understanding of the technique disclosed herein. It will be apparent to one skilled in the art that the technique may be practiced in other embodiments that depart from these specific details. Moreover, while the following embodiments are primarily described for a New Radio (NR) or 5G implementation, it is readily apparent that the technique described herein may also be implemented for any other radio communication technique, including a Wireless Local Area Network (WLAN) implementation according to the standard family IEEE 802.11, 3GPP LTE (e.g., LTE-Advanced or a related radio access technique such as MulteFire), for Bluetooth according to the Bluetooth Special Interest Group (SIG), particularly Bluetooth Low Energy, Bluetooth Mesh Networking and Bluetooth broadcasting, for Z-Wave according to the Z-Wave Alliance or for ZigBee based on IEEE 802.15.4.Telefonaktiebolaget LM Ericsson (pu bl) 11 / 54
[0111] P112973WO01
[0112] Moreover, those skilled in the art will appreciate that the functions, steps, units and modules explained herein may be implemented using software functioning in conjunction with a programmed microprocessor, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Digital Signal Processor (DSP) or a general purpose computer, e.g., including an Advanced RISC Machine (ARM). It will also be appreciated that, while the following embodiments are primarily described in context with methods and devices, the invention may also be embodied in a computer program product as well as in a system comprising at least one computer processor and memory coupled to the at least one processor, wherein the memory is encoded with one or more programs that may perform the functions and steps or implement the units and modules disclosed herein.
[0113] Without limitation, for example in a 3GPP implementation, any "radio device" may be a user equipment (UE).
[0114] The technique may be applied in the context of 3GPP New Radio (NR).
[0115] The technique may be implemented in accordance with a 3GPP specification, e.g., based on 3GPP release 18 or 19, optionally including modifications thereof. The technique may be implemented for 3GPP NR according to a modification of the 3GPP document TS 38.213, version 18.5.0.
[0116] Any radio device may be a user equipment (UE), e.g., according to a 3GPP specification. The radio device and the RAN may be wirelessly connected in an uplink (UL) and / or a downlink (DL) through a Uu interface.
[0117] The radio device and / or the network node or any other node of the RAN may form, or may be part of, a radio network, e.g., according to the Third Generation Partnership Project (3GPP) or according to the standard family IEEE 802.11 (Wi-Fi). The first method aspect and the second method aspect may be performed by one or more embodiments of the radio device and the network node (e.g., a base station or a relay radio device), respectively.
[0118] The RAN may comprise one or more network node (e.g., base stations), e.g., performing the second method aspect. Alternatively or in addition, the radio network may be a vehicular, ad hoc and / or mesh network comprising two or more radio devices, e.g., acting as the remote radio device and / or the relay radio device.Telefonaktiebolaget LM Ericsson (pu bl) 12 / 54
[0119] P112973WO01
[0120] Any of the radio devices may be a 3GPP user equipment (UE) or a Wi-Fi station (STA). The radio device may be a mobile or portable station, a device for machinetype communication (MTC), a device for narrowband Internet of Things (NB-loT) or a combination thereof. Examples for the UE and the mobile station include a mobile phone, a tablet computer and a self-driving vehicle. Examples for the portable station include a laptop computer and a television set. Examples for the MTC device or the NB-loT device include robots, sensors and / or actuators, e.g., in manufacturing, automotive communication and home automation. The MTC device or the NB-loT device may be implemented in a manufacturing plant, household appliances and consumer electronics.
[0121] Whenever referring to the RAN, the RAN may be implemented by one or more network nodes. The network node (e.g., a base station) may encompass any station that is configured to provide radio access to any of the radio devices. The base stations may also be referred to as cell, transmission and reception point (TRP), radio access node or access point (AP). The base station and / or the relay radio device may provide a data link to a host computer providing the user data to the remote radio device or gathering user data from the remote radio device. Examples for the base stations may include a 3G base station or Node B, 4G base station or eNodeB, a 5G base station or gNodeB, a Wi-Fi AP and a network controller (e.g., according to Bluetooth, ZigBee or Z-Wave).
[0122] The RAN may be implemented according to the Global System for Mobile Communications (GSM), the Universal Mobile Telecommunications System (UMTS), 3GPP Long Term Evolution (LTE) and / or 3GPP New Radio (NR).
[0123] Any aspect of the technique may be implemented on a Physical Layer (PHY), a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, a packet data convergence protocol (PDCP) layer, and / or a Radio Resource Control (RRC) layer of a protocol stack for the radio communication.
[0124] Herein, referring to a protocol of a layer may also refer to the corresponding layer in the protocol stack. Vice versa, referring to a layer of the protocol stack may also refer to the corresponding protocol of the layer. Any protocol may be implemented by a corresponding method.Telefonaktiebolaget LM Ericsson (pu bl) 13 / 54
[0125] P112973WO01
[0126] As to another aspect, a computer program product is provided. The computer program product comprises program code portions for performing any one of the steps of the method aspect disclosed herein when the computer program product is executed by one or more computing devices. The computer program product may be stored on a computer-readable recording medium. The computer program product may also be provided for download, e.g., via the radio network, the RAN, the Internet and / or the host computer. Alternatively, or in addition, the method may be encoded in a Field-Programmable Gate Array (FPGA) and / or an Application-Specific Integrated Circuit (ASIC), or the functionality may be provided for download by means of a hardware description language.
[0127] As to a first device aspect, a device according embodiment 23 or 25 is provided. The device may be configured to perform any one of the steps of the first method aspect. As to a further first device aspect, the device may comprise processing circuitry (e.g., at least one processor and a memory). Said memory comprises instructions executable by said at least one processor whereby the device is operative to perform any one of the steps of the first method aspect.
[0128] As to a second device aspect, a device according embodiment 27 or 29 is provided. The device may be configured to perform any one of the steps of the second method aspect. As to a further first device aspect, the device may comprise processing circuitry (e.g., at least one processor and a memory). Said memory comprises instructions executable by said at least one processor whereby the device is operative to perform any one of the steps of the first method aspect.
[0129] As to a still further aspect a communication system including a host computer is provided. The host computer comprises a processing circuitry configured to provide user data, e.g., included in the first and / or second data of the multi-layer transmission. The host computer further comprises a communication interface configured to forward the first and / or second data to a cellular network (e.g., the RAN and / or the base station) for transmission to a UE. A processing circuitry of the cellular network is configured to execute any one of the steps of the first and / or second method aspects. The UE comprises a radio interface and processing circuitry, which is configured to execute any one of the steps of the first and / or second method aspects.Telefonaktiebolaget LM Ericsson (pu bl) 14 / 54
[0130] P112973WO01
[0131] The communication system may further include the UE. Alternatively, or in addition, the cellular network may further include one or more base stations configured for radio communication with the UE and / or to provide a data link between the UE and the host computer using the first and / or second method aspects.
[0132] The processing circuitry of the host computer may be configured to execute a host application, thereby providing the first and / or second data and / or any host computer functionality described herein. Alternatively, or in addition, the processing circuitry of the UE may be configured to execute a client application associated with the host application.
[0133] Any one of the devices, the UE, the base station, the communication system or any node or station for embodying the technique may further include any feature disclosed in the context of the method aspect, and vice versa. Particularly, any one of the units and modules disclosed herein may be configured to perform or initiate one or more of the steps of the method aspect.
[0134] Fig. 1 schematically illustrates a block diagram of an embodiment of a device for performing the first method aspect according to any of embodiments 1 to 18. The device is generically referred to by reference sign 100.
[0135] The device 100 comprises modules as indicated in Fig. 1.
[0136] Any of the modules of the device 100 may be implemented by units configured to provide the corresponding functionality.
[0137] The device 100 may also be referred to as, or may be embodied by, the radio device (or briefly: UE). The radio device 100 and the network node may be in direct radio communication. The network node may be embodied by the below device 200.
[0138] Fig. 2 schematically illustrates a block diagram of an embodiment of a device for performing the second method aspect according to any of embodiments 19 to 21. The device is generically referred to by reference sign 200.
[0139] The device 200 comprises modules as indicated in Fig. 2.Telefonaktiebolaget LM Ericsson (pu bl) 15 / 54
[0140] P112973WO01
[0141] Any of the modules of the device 200 may be implemented by units configured to provide the corresponding functionality.
[0142] The device 200 may also be referred to as, or may be embodied by, the network node (or briefly: gNB). The radio device and the network node 200 may be in direct radio communication. The radio device may be embodied by the above-mentioned device 100.
[0143] Fig. 3 shows an example flowchart for a method 300 of embodiment 1.
[0144] Alternatively or in addition, the method 300 comprises the steps indicated in Fig. 3.
[0145] The method 300 may be performed by the device 100. For example, the modules 102 and 104 may perform the steps 302 and 304, respectively.
[0146] Fig. 4 shows an example flowchart for a method 400 of embodiment 19.
[0147] Alternatively or in addition, the method 400 comprises the steps indicated in Fig. 4.
[0148] The method 400 may be performed by the device 200. For example, the modules 202 and 204 may perform the steps 402 and 404, respectively.
[0149] In any aspect, the technique may be applied to uplink (UL), downlink (DL) or direct communications between radio devices, e.g., device-to-device (D2D) communications or sidelink (SL) communications.
[0150] Each of the random-accessing station 100 and random-accessed station 200 may be a radio device or network node (e.g., a base station). Herein, any radio device may be a mobile or portable station and / or any radio device wirelessly connectable to a base station or RAN, or to another radio device. For example, the radio device may be a user equipment (UE), a device for machine-type communication (MTC) or a device for (e.g., narrowband) Internet of Things (loT). Two or more radio devices may be configured to wirelessly connect to each other, e.g., in an ad hoc radio network or via a 3GPP SL connection. Furthermore, any base station may be a station providing radio access, may be part of a radio access network (RAN) and / or may be a node connected to the RAN for controlling theTelefonaktiebolaget LM Ericsson (pu bl) 16 / 54
[0151] P112973WO01
[0152] radio access. For example, the base station may be an access point, for example a Wi-Fi access point.
[0153] Fig. 5 schematically illustrates an example of a RAN 500 comprising embodiments of the network node 200, e.g., providing radio access in a cell 201, for an embodiment of the radio device 100.
[0154] Fig. 6 schematically illustrates a time-frequency grid of radio resources used or usable in any embodiment. Resource element (RE) 606 is the smallest unit in the grid. Symbols 610 may be aggregated in slots 608 in the time domain. Subcarriers 604 may be aggregated in resource blocks 602 in the frequency domain.
[0155] Any embodiment of any aspect may switch to FDD and / or TDD operation. Figs. 7 to 9 schematically illustrate frequency-division duplex (FDD) and time-division duplex (TDD).
[0156] Transmission and reception from a node, e.g. a terminal in a cellular system, can be multiplexed in the frequency domain or in the time domain (or combinations thereof). Frequency Division Duplex (FDD) as illustrated Fig. 7 implies that downlink and uplink transmission take place in different, sufficiently separated, frequency bands. Time Division Duplex (TDD), as illustrated in Fig. 9, implies that downlink and uplink transmission take place in different, non-overlapping time slots. Thus, TDD can operate in unpaired spectrum, whereas FDD requires paired spectrum. Half-duplex FDD (e.g., only from the perspective of the radio device) is indicated in Fig. 8.
[0157] Typically, the structure of the transmitted signal in a communication system is organized in the form of a frame structure. For example, NR uses ten equally sized slots per radio frame as illustrated in Fig. 10 for the case of 15 kHz subcarrier spacing.
[0158] In case of FDD operation (upper part of Fig. 10), there are two carrier frequencies, one for uplink transmission (fui.) and one for downlink transmission (for). At least with respect to the terminal in a cellular communication system, FDD can be either full duplex or half duplex. In the full duplex case, a terminal can transmit and receive simultaneously, while in half-duplex operation, the terminal cannot transmit and receive simultaneously (the base station is capable of simultaneousTelefonaktiebolaget LM Ericsson (pu bl) 17 / 54
[0159] P112973WO01
[0160] reception / transmission though, e.g. receiving from one terminal while simultaneously transmitting to another terminal). In LTE, a half-duplex terminal is monitoring / receiving in the downlink except when explicitly being instructed to transmit in a certain subframe.
[0161] In case of TDD operation (lower part of Fig. 10), there is only a single carrier frequency and uplink and downlink transmissions are always separated in time also on a cell basis. As the same carrier frequency is used for uplink and downlink transmission, both the base station and the mobile terminals need to switch from transmission to reception and vice versa. An essential aspect of any TDD system is to provide the possibility for a sufficiently large guard time where neither downlink nor uplink transmissions occur. This is required to avoid interference between uplink and downlink transmissions. For NR, this guard time is provided by special subframes, which are split into three parts: symbols for DL, a guard period (GP), and symbols for uplink. The remaining subframes are either allocated to uplink or downlink transmission.
[0162] Fig. 10 schematically illustrates uplink / downlink time / frequency structure in case of FDD or TDD.
[0163] In more detail, the following two information elements (lEs) are defined in current specifications. The TDD pattern is typically configured with at least the first IE and optionally the 2ndIE:
[0164] TDD-DL-UL-ConfigCommon (cell-specific)
[0165] TDD-DL-UL-ConfigDedicated (UE-specific)
[0166] The first IE is cell specific (common to all UEs) and is provided by broadcast signaling. It provides the number of slots in the TDD pattern via a reference subcarrier spacing and a periodicity such that the S-slot pattern repeats every S slots. This IE allows for very flexible configuration of the pattern characterized as follows:
[0167] A number of full downlink slots at the beginning of the pattern configured by the parameter nDownlinkSlots
[0168] A number of full uplink slots at the end of the pattern configured by the parameter nUplinkSlots
[0169] A number of downlink ('D') symbols following the full downlink slots configured by the parameter nDownlinkSymbolsTelefonaktiebolaget LM Ericsson (pu bl) 18 / 54
[0170] P112973WO01
[0171] A number of uplink ('U') symbols preceding the full downlink slots configured by the parameter nUplinkSlots
[0172] If there is a gap between the last downlink symbol and the first uplink symbol, then all symbols in the gap are characterized as flexible ('F'). A symbol classified as 'F' can be used for downlink or uplink. A UE determines the direction in one of the following two ways:
[0173] o Detecting a Downlink Control Information (DCI) that schedules / triggers a DL signal / channel, e.g., PDSCH, CSI-RS or schedules / triggers an UL signal / channel, e.g. PUSCH, SRS, etc.
[0174] o By dedicated (UE-specific) signaling of the IE TDD-DL-UL-ConfigDedicated. This parameter overrides some or all of the 'F' symbols in the pattern, thus providing a semi-static indication of whether a symbol is classified as 'D' or 'U'.
[0175] Optionally, a 2ndpattern that is concatenated to the first pattern can be configured as above. If a 2ndpattern is configured, the constraint is that the sum of the periodicities of the two patterns must evenly divide 20 ms.
[0176] Fig. 11 shows an exemplary TDD DL / UL pattern configured by TDD-DL-UL-ConfigCommon. It consists of 3 full ' D' slots, 1 full 'll' slot, with a mixed slot in between consisting of 4 'D' symbols and 3 'U' symbols. The remaining 7 symbols in the mixed slot are classified as 'F.'
[0177] If a UE is not configured with TDD-DL-UL-ConfigDedicated, then the pattern at the top of the diagram is what it assumes. As stated above, the network can make use of the ' F' symbols flexibly, by scheduling / triggering either an uplink or a downlink signal / channel in a UE specific manner. This allows for very dynamic behavior: the direction is not known to the UE a priori; rather, the direction becomes known once the UE detects a DCI scheduling / triggering a particular DL or UL signal / channel.
[0178] In contrast, the DL / UL direction for some or all of the 'F' symbols in a particular slot can be provided to the UE in a semi-static manner by RRC configuring the UE with TDD-DL-UL-ConfigDedicated. The lower part of Fig. 11 shows 3 exemplary configurations for overriding 'F' symbols in Slot 3. If the IE indicates 'allDownlink' or 'allUplink' for a particular slot (or slots), then all 'F' symbols in the slot are converted to either 'D' or 'U,' respectively. If the IE indicates 'explicit,' then a number of symbols at the beginning of the slot and / or a number of symbols at theTelefonaktiebolaget LM Ericsson (pu bl) 19 / 54
[0179] P112973WO01
[0180] end of the slot are indicated as 'D' and 'll,' respectively. In the example below, the first 7 and the last 5 are indicated as 'D' and 'U', which converts some of the 'F' symbols (but not all in this example) to ' D' and 'U .'
[0181] Fig. 11 schematically illustrates an exemplary TDD DL / UL pattern consisting of S = 5 slots.
[0182] The key behavior in the above is that the UE-specific IE TDD-DL-UL-ConfigDedicated can only override (i.e., specify ' D' or 'U') for symbols that are configured as 'F' by the cell-specific IE TDD-DL-UL-ConfigCommon. In other words, a UE does not expect to have a 'D' symbol converted to 'U' or vice versa.
[0183] Figs. 12 to 14 shows three additional exemplary TDD DL / UL patterns configured by TDD-DL-UL-ConfigCommon. In the first and second patterns, there are no 'F' symbols, hence according to current behavior in the Rel-17 specifications, the UE would not expect to be configured with TDD-DL-UL-ConfigDedicated. In the third pattern, all symbols in Slots 1, 2, and 3 are configured as 'F;' hence, the UE could be configured with TDD-DL-UL-ConfigDedicated to provide a direction ('D' or 'U') for any or all symbols in these 3 slots. Note that the current (Rel-17) specifications allow the dedicated configuration of the TDD pattern on a slot-specific basis. In other words, TDD-DL-UL-ConfigDedicated is not restricted to be the same in each slot where 'F' symbols are overridden.
[0184] Figs. 12 to 14 schematically illustrate three additional exemplary cell-specific TDD DL / UL patterns.
[0185] Any embodiment may operate according to subband full duplex (SBFD).
[0186] As described in the last section, in a conventional TDD system, entire carrier BW or all carriers in the same frequency band need to be utilizing the same DL transmission or UL reception directions. This is further illustrated in Figs. 15 to 16. Fig. 15 schematically illustrates a conventional TDD carrier. Fig. 16 schematically illustrate conventional TDD carrier systems.
[0187] For the Release 18 evolution of the NR system, 3GPP has decided to study the technical feasibilities and potential benefits of subband full duplex (SBFD)
[0188] systems.Telefonaktiebolaget LM Ericsson (pu bl) 20 / 54
[0189] P112973WO01
[0190] In such a system, a portion of a wide bandwidth carrier may be used for a different direction than that of the rest of the carrier. This is illustrated in the lefthand side of Figs. 17 to 18. That is, unlike a conventional TDD system as shown on the left-hand side of Figs. 15 to 16 where the entire bandwidth is used for DL transmission in the first three slots, the center portion of the SBFD carrier is used for UL reception while the rest of the carrier continues to be used for DL transmission as shown in the left-hand side of Figs. 17 to 18.
[0191] Similarly, instead of utilizing all carriers for the same DL or UL directions in a conventional TDD system as shown in the right-hand side of Figs. 15 to 16, some carriers in the SBFD system can be used for a different direction than that of the other carriers as shown in the right-hand side of Figs. 17 to 18.
[0192] In the 3GPP Rel-18 study, the scope has been limited such that in SBFD operation, only gNBs transmit DL and receive UL simultaneously. An individual UE is scheduled in only one direction (DL or UL) at a time.
[0193] Fig. 17 schematically illustrates a time-frequency domain of a subband full duplex (SBFD) carrier. Fig. 18 schematically illustrates a time-frequency domain of a subband full duplex (SBFD) carrier system.
[0194] In Release 19, RANI has agreed to configure one or more OFDM symbols of a slot with two or more "RB sets" (subbands) where each RB set corresponds to a frequency domain subband and has a defined transmission direction ('D' or 'U'). The RB sets may have gaps between them that serve as guardbands where neither DL or UL transmission occurs. Figs. 19 and 20 shows two exemplary RB set configurations, one with D-U-D configuration in Fig. 19 and the other with U-D-U configuration in Fig. 20. The RB sets are configured either by introduction of new RRC parameter(s) or enhancement of an existing RRC parameter, e.g., TDD-UL-DL-ConfigDedicated. In either case, the parameter(s) signal the size and frequency domain location of the RB sets as well as which symbols and / or slots in the TDD UL / DL pattern are configured with RB sets.
[0195] Any embodiment may include as the repeated message the message-3 (Msg3) repetitions in SBFD, e.g. using at least one of the following features. The radio device is referred to as UE for conciseness.Telefonaktiebolaget LM Ericsson (pu bl) 21 / 54
[0196] P112973WO01
[0197] A UE 100 can be configured by the network with Msg3 repetitions, in order to improve its coverage and improve decoding likelihood at the gNB. In order to do so, the UE must first determine which symbols and slots can be used for the repetitions. According to TS 38.213, version 18.4, clause 8.3, for unpaired spectrum only slots where the Msg3 repetition resources include symbols that does not include a DL symbol according to tdd-UL-DL-ConfigurationCommon or an SSB symbol according to ssb-PositionsInBurst
[0198]
[0199] _
[0200] In the Rel-19 work item on duplex evolution it has furthermore been agreed to only use Configuration 1 for Msg3 repetitions, i.e., either repetitions are aerformed over SBFD symbols or over non-SBFD symbols but not mixed:
[0201]
[0202] Telefonaktiebolaget LM Ericsson (pu bl) 22 / 54
[0203] P112973WO01
[0204]
[0205] Embodiments of the method 300 or 400, and the method 3000, 4000 can address at least one of the following problems with the existing technology.
[0206] The existing technical specification does not differentiate between SBFD and non-SBFD symbols as shown in the excerpt of TS 38.213. At the same time, RANI has agreed to differentiate between SBFD and non-SBFD symbols for Msg3 repetitions by mandating Msg3 repetitions to use Configuration 1, i.e., either SBFD symbols or non-SBFD symbols but not both. Hence, there is a need for a method that allows SBFD Configuration 1 to be integrated in the current slot counting framework.
[0207] Fig. 19 shows an exemplary configuration of 3 RB sets in an SBFD symbol configured as D-U-D. Fig. 20 shows an exemplary configuration of 3 RB sets in an SBFD symbol configured as U-D-U.
[0208] Based on the above description, an SBFD symbol is defined as a DL, UL1or F symbol that is configured with an SBFD UL subband and one or two SBFD DL subbands according to tdd-UL-DL-ConfigurationCommon. A non-SBFD symbol is
[0209] 1Not inRel-19.Telefonaktiebolaget LM Ericsson (pu bl) 23 / 54
[0210] P112973WO01
[0211] defined as a DL, UL or F symbol that is not configured with an SBFD UL subband and one or two SBFD DL subbands according to tdd-UL-DL-ConfigurationCommon.
[0212] In a variant of any embodiment, the slot counting may start from a slot n + k2+ A + 2^ • Keen, offset, and / or a slot indicated by the star (*) in each of Figs. 21 and 22.
[0213] The Example A in Fig. 21 and the Example B in Fig. 22 schematically illustrates a SBFD carrier system, respectively. Embodiments of the method 300 and 400 illustrated in Fig. 3 and Fig. 4, and embodiments of the method 3000 and 4000 illustrated in Fig. 23 and Fig. 24 may be exemplified by applying it to the Example A and B, wherein "legacy" Release 18 provides a reference example.
[0214] Any aspect may be implemented including at least one feature or step of the following embodiments.
[0215] The embodiments comprise methods on how to determine repetitions for Msg3 PUSCH transmissions for SBFD-aware UEs operating in a cell that is supporting SBFD and SBFD random access and how to determine that the methods should be applied.
[0216] Embodiments relating to application of methods for determination
[0217] In one embodiment, the methods are applied to cells in which SBFD operation is enabled.
[0218] In one embodiment, the methods are applied to cells in which SBFD random access is enabled.
[0219] In one embodiment, the methods are applied if the network provides an indication that SBFD random access is enabled.
[0220] In one embodiment, the methods are applied if an additional RACH configuration is provided by the network.
[0221] In one embodiment, SBFD or non-SBFD is determined by the scheduling location (e.g., frequency-time resource) of the first repetition. For example, SBFD or non-SBFD symbol type of the repeated transmission is determined by the scheduled symbol in the slot of the first repetition.
[0222] Moreover, in deviation from the existing technical specification (which only differentiates between paired and unpaired spectrum), embodiments may include the two SBFD options (e.g., SBFD or non-SBFD) in the unpaired part.Telefonaktiebolaget LM Ericsson (pu bl) 24 / 54
[0223] P112973WO01
[0224] Embodiments relating to determination of repetitions
[0225] In a first embodiment, in accordance with Configuration 1, Msg3 may be repeated in non-SBFD symbols. In a second embodiment, in accordance with Configuration 1, Msg3 may be repeated in SBFD symbols.
[0226] In one embodiment, repetitions of the Msg3 PUSCH transmission are determined as follows for non-SBFD symbols:
[0227] A repetition of the PUSCH transmission does not include a symbol indicated as downlink by tdd-UL-DL-ConfigurationCommon or indicated as a symbol of an SS / PBCH block with index provided by ssb- PositionsInBurst or indicated as an SBFD symbol by tdd-UL-DL- ConfiqurationCommon.
[0228] In one embodiment, assuming SSB symbols are not SBFD symbols, repetitions of the Msg3 PUSCH transmission are determined as follows for SBFD symbols:
[0229] A repetition of a Msg3 PUSCH transmission in SBFD symbols does not include a symbol indicated as a non-SBFD symbol by tdd-UL-DL- ConfiqurationCommon.
[0230] alternatively
[0231] A repetition of a Msg3 PUSCH transmission in SBFD symbols only includes symbols indicated as SBFD symbols by tdd-UL-DL- ConfiqurqtionCommon.
[0232] In one embodiment, assuming SSB symbols may be SBFD symbols, repetitions of the Msg3 PUSCH transmission are determined as follows for SBFD symbols:
[0233] A repetition of a Msg3 PUSCH transmission in SBFD symbols does not include a symbol indicated as a non-SBFD symbol by tdd-UL-DL- ConfiqurqtionCommon or indicated as a symbol of an SS / PBCH block with index provided by ssb-PositionsInBurst.
[0234] In one embodiment, an appending description considering both SBFD and non-SBFD cases of Configuration 1 may be provided:
[0235] A repetition of the PUSCH transmission does not include a symbol indicated as downlink by tdd-UL-DL-ConfigurqtionCommon or indicated as a symbol of an SS / PBCH block with index provided by ssb- PositionsInBurst or, for an SBFD-aware UE, does not include an SBFD symbol type different from the initial symbol of the Msg3 UL grant.Telefonaktiebolaget LM Ericsson (pu bl) 25 / 54
[0236] P112973WO01
[0237] Embodiments relating to signaling alternatives
[0238] In one of the embodiments, the valid symbol type for Msg3 PUSCH transmissions indicated explicitly or implicitly by the gNB. For the former, the gNB includes the indicator in the DCI (i.e., including DL assignments for the RAR message) or RAR. For the latter, there is no explicit indicator in the DCI or the RAR, instead, the UE derives the valid symbol type thorough the PUSCH resource allocated for Msg3 transmissions. As an example, if the resources are solely allocated in the non SBFD symbols, it means the valid symbol type is non SBFD symbol. If the resources are solely allocated in SBFD symbols, it means that the valid symbol type is SBFD symbol.
[0239] In one of the embodiments, the gNB may signal a second symbol type for Msg3 PUSCH retransmissions. The second symbol type is different from the symbol type for the initial PUSCH transmission. The second symbol type can be signaled by the gNB to the UE in the DCI (i.e., including PUSCH resources for Msg3 retransmissions) explicitly or implicitly. For the former, the gNB 200 includes the valid symbol type in the DCI. For the latter, there is no explicit indicator in the DCI or the RAR, instead, the UE derives the valid symbol type thorough the PUSCH resource allocated for Msg3 retransmissions.
[0240] In one of the embodiments, the gNB may signal a symbol type for a Msg3 PUSCH retransmission. The symbol type is different from the symbol type for the previous Msg3 PUSCH retransmission.
[0241] In one of the embodiments, the valid symbol type for a repetition of Msg3 initial transmission is determined based on the symbol type of the first transmission occasion of Msg3 initial transmission.
[0242] In one of the embodiments, the valid symbol type for a repetition of a Msg3 retransmission is determined based on the symbol type of the first transmission occasion of Msg3 initial transmission. For example, SBFD or non-SBFD symbol for a repetition of Msg3 is determined by the valid symbol type which is the symbol type of the allocated resource of the first transmission.
[0243] In one of the embodiments, the valid symbol type for a repetition of a Msg3 retransmission is determined based on the symbol type of the first transmission occasion of the Msg3 retransmission.
[0244] Legacy Slot Counting (Release 18)
[0245] In the legacy approach, the system may permit subband full duplex for other channels, but the slot-counting rules for Msg3 repetitions do not distinguishTelefonaktiebolaget LM Ericsson (pu bl) 26 / 54
[0246] P112973WO01
[0247] between SBFD (subband-full-duplex) symbols and non-SBFD symbols. Instead, the UE simply applies the conventional rule that a repetition slot cannot include any symbol configured as downlink according to the cell's TDD-DL-UL configuration, nor can it include a symbol reserved for an SS / PBCH block (SSB). Thus, if any part of a slot contains disallowed symbols, that entire slot is skipped for purposes of the Msg3 repetition count. The earliest set of consecutive slots containing permissible uplink-only (or flexi ble-as-u pli n k) symbols is selected for the repetitions.
[0248] In Example A of Fig. 21, the overall time grid would be conventionally used without further distinction between SBFD and non-SBFD opportunities. Once the conventional UE identifies which slots avoid downlink and SS / PBCH (SSB) symbols, the UE counts each such slot in turn until reaching the required number of Msg3 repetition transmissions.
[0249] An embodiment for Subband-Full-Duplex (SBFD) Slot Counting
[0250] While the skilled person can readily apply any of the embodiment described herein for the situation indicated as Example A in Fig. 21, the following description refers to a further exemplary embodiment.
[0251] In one variant of the embodiment, any SBFD slot counts provided it does not include an SSB.
[0252] In another variant, at least one of the following rules applies.
[0253] Under this embodiment —explicitly addressing SBFD for Msg3 repetitions— the UE 100 identifies not only whether an entire slot is reserved for downlink or uplink, but also whether the slot contains SBFD-type symbols or non-SBFD-type symbols.
[0254] According to "Configuration 1", a Msg3 PUSCH scheduled on SBFD symbols must repeat only on SBFD symbols. Put differently, any slot that includes a non-SBFD symbol during the prospective repetition window is automatically skipped, regardless of whether those symbols might have been flexible uplink or even unused.
[0255] Thus, for SBFD transmissions, the slot counting excludes all slots if they contain any non-SBFD symbols. The UE's first valid slot for Msg3 determines whether the repetition is SBFD-only (or not). Then the UE proceeds to count each subsequentTelefonaktiebolaget LM Ericsson (pu bl) 27 / 54
[0256] P112973WO01
[0257] slot containing exclusively SBFD uplink symbols. The earliest consecutive slots meeting that condition are used for NpuscHrepeattransmissions of Msg3.
[0258] In Example A of Fig. 21, the symbolic representation of "DL / SBFD" and "F / SBFD" squares highlights these SBFD subbands that can be used for Msg3 repetitions. The UE 100 only counts and / or traverses (in time) those SBFD slots exclusively— thus maintaining consistency with the requirement that the subband / full-duplex type not be mixed with non-SBFD-type symbols when the first Msg3 allocation is in SBFD.
[0259] An embodiment for Non-Subband-Full-Duplex Slot Counting
[0260] While the skilled person can readily apply any of the embodiment described herein for the situation indicated as Example A in Fig. 21, the following description refers to a further exemplary embodiment.
[0261] In one variant of the embodiment, the legacy counting is further restricted by excluding slots (e.g., mini-slots or symbols) that include an "F" (flexible) symbol.
[0262] In another variant, at least one of the following rules applies.
[0263] Under the complementary embodiment, if the first Msg3 occasion is scheduled fully outside of SBFD subbands, the slot counting is restricted to non-SBFD slots. This is analogous to the legacy approach— namely, the UE skips slots that contain any explicit downlink or SS / PBCH (SSB) symbols— but further excludes SBFD symbols when the UE 100 has been indicated to remain in non-SBFD mode for Msg3 repetitions. These mixed slots (i.e., containing SBFD symbols as well) are not usable for the next repetition if the UE is configured to remain strictly in a non-SBFD repetition pattern (e.g., again per "Configuration 1" constraints).
[0264] Hence, in Example A of Fig. 21, a run of "DL" or "F" squares that are not flagged as SBFD are counted— provided they do not include SS / PBCH (SSB) and remain usable as uplink during the time / frequency block. The UE 100 collects as many such slots as needed to satisfy the required NpuscHrepeattransmissions for Msg3.
[0265] In Example B of Fig. 22, the network node 200 configures a TDD-based frame with both downlink (DL) and uplink (UL) symbols, as well as symbols dedicated to subband full duplex (SBFD). While the same overall time-frequency layout is shown for "Legacy," "Subband-Full-Duplex," and "Non-Subband-Full-Duplex,"Telefonaktiebolaget LM Ericsson (pu bl) 28 / 54
[0266] P112973WO01
[0267] each case applies a different rule set for counting which slots are valid for Msg3 (i.e., Random Access response) PUSCH repetitions.
[0268] Legacy Interpretation (e.g., according to 3GPP NR Release 18)
[0269] Under a conventional Release 18 interpretation— even though SBFD was introduced in Rel-18— the legacy slot-counting mechanism does not differentiate between SBFD-type symbols and non-SBFD-type symbols. In other words, any slot that is labeled for uplink (or flexible, configured as uplink by DCI) is considered valid for Msg3 PUSCH repetitions, regardless of whether the slot includes subband splitting. Consequently, at least one of the following rules may apply:
[0270] 1. The UE 100 counts each successive uplink-capable slot starting from the slot indicated by the star (*) and / or indicated in the Msg2 (i.e., RAR UL grant or DCI with RA-RNTI orTC-RNTI).
[0271] 2. The UE 100 stops (i.e., does not include in the counting) only if it encounters a slot that explicitly contains only downlink symbols or if that slot carries an SS / PBCH block (SSB).
[0272] 3. There is no notion of filtering out a slot that contains differently directed subbands within the same symbol.
[0273] Thus, in some legacy approach, "subband" and "non-subband" uplink resources are effectively lumped together, and the slot-counting cycle always treats all uplink-labeled symbols as similar.
[0274] Subband-Full-Duplex (SBFD) Embodiment
[0275] In an SBFD embodiment, optionally applied to the situation of Example B, the network node 200 configures some symbols (e.g., certain frequency subbands) as uplink (UL) while simultaneously using the remaining subbands for downlink (DL). Because RANI has agreed that Msg3 repetitions must use consistency of "SBFD symbols only" or "non-SBFD symbols only" (Configuration 1), the UE 100 adapts its slot counting according to at least one of the follow rules:Telefonaktiebolaget LM Ericsson (pu bl) 29 / 54
[0276] P112973WO01
[0277] 1. When the UE's first Msg3 transmission occasion occurs completely in SBFD-type symbols, every subsequent repetition must also occur entirely in SBFD-type symbols.
[0278] 2. The UE 100 therefore identifies and counts only those slots in which the SBFD subband remains valid (i.e., there are no conflicting downlink subbands occupying the same resource blocks in the same symbols used for Msg3).
[0279] 3. If a slot has a mix of subband types— some "SBFD" and some "non-SBFD"— the UE includes that slot only if the frequency region and symbol region allocated to it matches the UE's initial SBFD frequency subbands.
[0280] 4. If the network node 200 signals that an SS / PBCH block (SSB) occupies any part of the same SBFD subband potentially used by the UE's Msg3, the UE 100 omits that slot from its (e.g., counting in accordance with existing TDD rules).
[0281] As a result, in Fig. 22 Example B, the SBFD embodiment skips counting slots that have no valid SBFD subband for the UE's Msg3 or that contain downlink subbands overlapping the UE's SBFD uplink region. This ensures the UE 100 remains strictly in UL-enabled SBFD portions.
[0282] Non-Subband-Full-Duplex (Non-SBFD) Embodiment
[0283] In a Non-SBFD embodiment (e.g., essentially conventional TDD with no subband splitting), the slot counting differs from both the Legacy and the SBFD approaches. Specifically, the UE 100 takes note of whether the Msg3 resource is composed of entirely UL (i.e., no SBFD splitting) or uses flexible symbols that become UL via DCL Alternatively or in addition, at least one of the following rules may be applies:
[0284] 1. Once the first transmission for Msg3 uses a "non-SBFD" uplink symbol, each follow-up repetition must only be scheduled in those slots that are fully uplink or have flexible symbols overridden as UL but never subdivided into an SBFD UL subband.
[0285] 2. If the UE detects that a slot is partially subdivided (i.e., part of the slot is SBFD), the UE 100 excludes that slot from its valid repetition count.Telefonaktiebolaget LM Ericsson (pu bl) 30 / 54
[0286] P112973WO01
[0287] 3. As with standard TDD operation, any slot that contains downlink symbols or SS / PBCH block (SSB) in the same symbol region allocated for Msg3 is likewise excluded.
[0288] Hence, for Example B in Fig. 22, those slots featuring (e.g., potentially) partial SBFD operation do not count toward the non-SBFD repetition sequence. The UE 100 waits for the next purely non-SBFD uplink slot, ensuring the repetition pattern is consistent with a non-SBFD direction.
[0289] Alternatively or in addition, by comparing these three approaches— Legacy, SBFD (as one embodiment), and Non-SBFD (as one embodiment)— at least one of the following distinguishing feature may apply:
[0290] • Legacy (Release 18) combines any UL region into a single slot-counting set, never excluding subband splits within an uplink-labeled symbol.
[0291] • An SBFD embodiment may exclude any slot if it does not contain a matching SBFD UL subband and symbol configuration. This may include that Msg3 repetitions remain confined to the same one or more frequency subbands originally scheduled for SBFD transmission.
[0292] • A non-SBFD embodiment may also focuses only on purely "non-split" uplink slots (or flexible symbols signaled as UL), explicitly skipping subband-split slots.
[0293] Fig. 23 shows a flowchart for a method 3000 of performing random access, which method may be implementable by the device of Fig. 1. The method 3000 performed by a radio device 100 for random access in a RAN 500 comprises: obtaining 3002, from a network node 200 in the RAN 500, an uplink grant allocating a resource for a first transmission of a message in a RA procedure, wherein a symbol type of the allocated resource is either SBFD or non-SBFD; and transmitting 3004 one or more repeated transmissions of the message in a subsequent required number of slots, each repeated transmission being restricted to a valid symbol type being the symbol type of the allocated resource of the first transmission. The radio device 100 may be an SBFD-aware UE.Telefonaktiebolaget LM Ericsson (pu bl) 31 / 54
[0294] P112973WO01
[0295] The method 3000 may be performed by the device 100. For example, the modules 102 and 104 may perform the steps 3002 and 3004, respectively.
[0296] Fig. 24 shows a flowchart for a method 4000 of performing random access, which method may be implementable by the device of Fig. 2. The method 4000 performed by a network node 200 for RA in a radio access network 500 comprises: providing 4002, to a radio device 100 in the RAN 500, an uplink grant allocating a resource for a first transmission of a message in a RA procedure, wherein a symbol type of the allocated resource is either SBFD or non-SBFD; and receiving 4004 one or more repeated transmissions of the message in a subsequent required number of slots, each repeated transmission being restricted to a valid symbol type being the symbol type of the allocated resource of the first transmission.
[0297] The method 4000 may be performed by the device 200. For example, the modules 202 and 204 may perform the steps 4002 and 4004, respectively.
[0298] In some embodiments, the message in the method 3000 and 4000 can be Msg 3 of the 4-step RA procedure, which is also known as PUSCH scheduled by RAR UL grant. In some other embodiments, the message may be Msg B of the 2-step RA procedure.
[0299] In some embodiments, the uplink grant in the method 3000 and 4000 may be provided by the network node 200 via a RAR message or a DCI message. As an example, for Msg3 initial transmission, the PUSCH resources may be allocated via the RAR UL grant, while for the subsequent retransmission of Msg3, the PUSCH resources may be scheduled by a DCI message (e.g., addressed to TC-RNTI).
[0300] In one of the embodiments of the method 3000, 4000, a slot is counted in the required number of slots based on a slot counting rule associated with the valid symbol type. For example, the slot counting rule associated with the valid symbol type may comprise at least one of following:
[0301] - in case the valid symbol type is SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all SBFD symbol;
[0302] - in case the valid symbol type is non-SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all non-SBFD symbol;Telefonaktiebolaget LM Ericsson (pu bl) 32 / 54
[0303] P112973WO01
[0304] a slot containing a transmission that is not in the valid symbol type is not counted in the required number of slots.
[0305] In one of the embodiments, the method 3000, 4000 may further comprises counting the required number of slots to reach a required number of repeated transmissions of the message, such as the required number of Msg 3 repetition transmissions.
[0306] In one of the embodiments of the method 3000, 4000, in case the valid symbol type is non-SBFD, a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a PUSCH of the repeated transmission does not include a symbol
[0307] - indicated as downlink by tdd-UL-DL-ConfigurationCommon, and / or
[0308] - indicated as a symbol of an SS / PBCH block, SSB, with index provided by ssb- PositionsInBurst and / or
[0309] - indicated as a symbol type being SBFD by tdd-UL-DL-ConfigurationCommon.
[0310] In one of the embodiments of the method 3000, 4000, in case the valid symbol type is SBFD, a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a PUSCH of the repeated transmission only includes symbols indicated as SBFD symbols, e.g., by tdd-UL-DL-ConfigurationCommon.
[0311] In one of the embodiments of the method 3000, 4000, in case the valid symbol type is SBFD, a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a PUSCH of the repeated transmission does not include a symbol
[0312] - indicated as a non-SBFD symbol by tdd-UL-DL-ConfigurationCommon and / or
[0313] - indicated as a symbol of an SS / PBCH block, SSB, by ssb-PositionsInBurst.
[0314] Fig. 25 shows a schematic block diagram for an embodiment of the device 100. The device 100 comprises processing circuitry, e.g., one or more processors 2304 for performing the method 300, 3000 and memory 2306 coupled to the processors 2304. For example, the memory 2306 may be encoded with instructions that implement at least one of the modules 102, 104.Telefonaktiebolaget LM Ericsson (pu bl) 33 / 54
[0315] P112973WO01
[0316] The one or more processors 2304 may be a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, microcode and / or encoded logic operable to provide, either alone or in conjunction with other components of the device 100, such as the memory 2306, transmitter functionality. For example, the one or more processors 2304 may execute instructions stored in the memory 2306. Such functionality may include providing various features and steps discussed herein, including any of the benefits disclosed herein. The expression "the device being operative to perform an action" may denote the device 100 being configured to perform the action.
[0317] As schematically illustrated in Fig. 25, the device 100 may be embodied by a transmitting station 2300, e.g., functioning as a transmitting base station or a transmitting UE. The transmitting station 2300 comprises a radio interface 2302 coupled to the device 100 for radio communication with one or more receiving stations, e.g., functioning as a receiving base station or a receiving UE.
[0318] In one embodiment, the radio device 100 comprising memory 2306 operable to store instructions and processing circuitry operable to execute the instructions, such that the radio device 100 is operable to: obtain, from a network node 200 in a RAN 500, an uplink grant allocating a resource for a first transmission of a message in a RA procedure, wherein a symbol type of the allocated resource is either SBFD or non-SBFD; and transmit one or more repeated transmissions of the message in a subsequent required number of slots, each repeated transmission being restricted to a valid symbol type being the valid symbol type of the allocated resource of the first transmission.
[0319] In one embodiment, the radio device 100 for RA in a RAN 500 is configured to: obtain, from a network node 200 in the RAN 500, an uplink grant allocating a resource for a first transmission of a message in a RA procedure, a symbol type of the allocated resource is either SBFD or non-SBFD; and transmit one or more repeated transmissions of the message in a subsequent required number of slots,Telefonaktiebolaget LM Ericsson (pu bl) 34 / 54
[0320] P112973WO01
[0321] each repeated transmission being restricted to a valid symbol type being the symbol type of the allocated resource of the first transmission.
[0322] In some embodiments, the radio device 100 is further operable to or configured to count a slot in the required number of slots based on a slot counting rule associated with the valid symbol type.
[0323] In some embodiments, the radio device 100 is further operable to or configured to count the required number of slots to reach a required number of repeated transmissions of the message, such as the required number of Msg 3 repetition transmissions.
[0324] In some embodiments, the radio device 100 is further operable to or configured to perform the steps of any further embodiments of Fig. 23.
[0325] Fig. 26 shows a schematic block diagram for an embodiment of the device 200. The device 200 comprises processing circuitry, e.g., one or more processors 2404 for performing the method 400, 4000 and memory 2406 coupled to the processors 2404. For example, the memory 2406 may be encoded with instructions that implement at least one of the modules 202, 204.
[0326] The one or more processors 2404 may be a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, microcode and / or encoded logic operable to provide, either alone or in conjunction with other components of the device 200, such as the memory 2406, receiver functionality. For example, the one or more processors 2404 may execute instructions stored in the memory 2406. Such functionality may include providing various features and steps discussed herein, including any of the benefits disclosed herein. The expression "the device being operative to perform an action" may denote the device 200 being configured to perform the action.
[0327] As schematically illustrated in Fig. 26, the device 200 may be embodied by a receiving station 2400, e.g., functioning as a receiving base station or a receiving UE. The receiving station 2400 comprises a radio interface 2402 coupled to theTelefonaktiebolaget LM Ericsson (pu bl) 35 / 54
[0328] P112973WO01
[0329] device 200 for radio communication with one or more transmitting stations, e.g., functioning as a transmitting base station or a transmitting UE.
[0330] In one embodiment, the device is a network node. The network node 200 comprises memory 2406 operable to store instructions and processing circuitry operable to execute the instructions, such that the network node 200 is operable to: provide, to a radio device 100, an uplink grant allocating a resource for a first transmission of a message in a RA procedure, wherein a symbol type of the allocated resource is either SBFD or non-SBFD; and receive one or more repeated transmissions of the message in a subsequent required number of slots, each repeated transmission being restricted to a valid symbol type being the symbol type of the allocated resource of the first transmission.
[0331] In one embodiment, the network node 200 in a RAN 500 is configured to: provide, to a radio device 100, an uplink grant allocating a resource for a first transmission of a message in a RA procedure, wherein a symbol type of the allocated resource is either SBFD or non-SBFD; and receive one or more repeated transmissions of the message in a subsequent required number of slots, each repeated transmission being restricted to a valid symbol type being the symbol type of the allocated resource of the first transmission.
[0332] In some embodiments, the network node 200 is further operable to or configured to count a slot in the required number of slots based on a slot counting rule associated with the valid symbol type.
[0333] In some embodiments, the network node 200 is further operable to or configured to count the required number of slots to reach a required number of repeated transmissions of the message, such as the required number of Msg 3 repetition transmissions.
[0334] In some embodiments, the network node 200 is further operable to or configured to perform the steps of any further embodiments of Fig. 24.
[0335] With reference to Fig. 27, in accordance with an embodiment, a communication system 2500 includes a telecommunication network 2510, such as a 3GPP-type cellular network, which comprises an access network 2511, such as a radio access network, and a core network 2514. The access network 2511 comprises a pluralityTelefonaktiebolaget LM Ericsson (pu bl) 36 / 54
[0336] P112973WO01
[0337] of base stations 2512a, 2512b, 2512c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 2513a, 2513b, 2513c. Each base station 2512a, 2512b, 2512c is connectable to the core network 2514 over a wired or wireless connection 2515. A first user equipment (UE) 2591 located in coverage area 2513c is configured to wirelessly connect to, or be paged by, the corresponding base station 2512c. A second UE 2592 in coverage area 2513a is wirelessly connectable to the corresponding base station 2512a. While a plurality of UEs 2591, 2592 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 2512.
[0338] Any of the base stations 2512 may embody the network node 200, and the UEs 2591, 2592 may embody the device 100.
[0339] The telecommunication network 2510 is itself connected to a host computer 2530, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 2530 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 2521, 2522 between the telecommunication network 2510 and the host computer 2530 may extend directly from the core network 2514 to the host computer 2530 or may go via an optional intermediate network 2520. The intermediate network 2520 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 2520, if any, may be a backbone network or the Internet; in particular, the intermediate network 2520 may comprise two or more sub-networks (not shown).
[0340] The communication system 2500 of Fig. 27 as a whole enables connectivity between one of the connected UEs 2591, 2592 and the host computer 2530. The connectivity may be described as an over-the-top (OTT) connection 2550. The host computer 2530 and the connected UEs 2591, 2592 are configured to communicate data and / or signaling via the OTT connection 2550, using the access network 2511, the core network 2514, any intermediate network 2520 and possible further infrastructure (not shown) as intermediaries. The OTT connection 2550 may be transparent in the sense that the participating communication devices through which the OTT connection 2550 passes are unaware of routing of uplink andTelefonaktiebolaget LM Ericsson (pu bl) 37 / 54
[0341] P112973WO01
[0342] downlink communications. For example, a base station 2512 need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 2530 to be forwarded (e.g., handed over) to a connected UE 2591. Similarly, the base station 2512 need not be aware of the future routing of an outgoing uplink communication originating from the UE 2591 towards the host computer 2530.
[0343] By virtue of the method 300 and 3000 being performed by any one of the UEs 2591 or 2592 and / or the method 400 and 4000 being performed by any one of the base stations 2512 (e.g., the network node 200), the performance or range of the OTT connection 2550 can be improved, e.g., in terms of increased throughput and / or reduced latency. More specifically, the host computer 2530 may indicate to the RAN 500 or the radio device 100 or the network node 200 (e.g., on an application layer) the need for triggering the RA procedure.
[0344] As has become apparent from above description, at least some embodiments of the technique enable an SBFD-aware UE to perform random access (RA) in an SBFD cell in which SBFD random access is enabled. Thereby, the SBFD-aware UE can leverage SBFD RA occasions (ROs) and avoid legacy ROs, in turn allowing for longer range and better coverage and increased RA capacity and reduced RA latency for the network.
[0345] Many advantages of the present invention will be fully understood from the foregoing description, and it will be apparent that various changes may be made in the form, construction and arrangement of the units and devices without departing from the scope of the invention and / or without sacrificing all of its advantages. Since the invention can be varied in many ways, it will be recognized that the invention should be limited only by the scope of the following
[0346] embodiments.Telefonaktiebolaget LM Ericsson (pu bl) 38 / 54
[0347] P112973WO01
[0348] List of Embodiments
[0349] 1. A method (300) performed by a radio device (100) for random access, RA, to a radio access network, RAN (500), the method (300) comprising:
[0350] obtaining (302), from a network node (200) of the RAN (500), a resource configuration that indicates a symbol type for a first transmission of a message in a RA procedure, the symbol type being either subband-full-duplex, SBFD, or non-subband-full-duplex, non-SBFD; and
[0351] transmitting (304) one or more repeated transmissions of the message in subsequent slots, each repeated transmission being restricted to the same symbol type.
[0352] By confining the one or more transmissions (i.e., the first and the repeated transmissions) to one symbol type, embodiments of the radio device can ensure consistent handling of random-access transmissions, improving coverage and / or reducing interference when subband-full-duplex resources are employed.
[0353] The same symbol type may refer to the symbol type of the first transmission and / or the symbol type indicated by the resource configuration.
[0354] Herein, "first transmission" may refer to the first transmission of the same message in the same RA procedure. Optionally, repetitions of the message may use different redundancy versions (e.g. at channel coding).
[0355] 2. The method (300) of embodiment 1, wherein the message is message-3 of the RA procedure.
[0356] The message may be a third message or message-3 in the RA (i.e., in the RA procedure). Alternatively or in addition, the message may be a response of the radio device to a RA response (or message-2) from the network node, wherein the RA response may be a response to a RA preamble (or message-1) initially transmitted by the radio device to the network node.
[0357] While the technique is primarily described for a 4-step RA procedure, embodiments of the technique may be readily applied to 2-step RA procedure.Telefonaktiebolaget LM Ericsson (pu bl) 39 / 54
[0358] P112973WO01
[0359] 3. The method (300) of embodiment 1 or 2, further comprising:
[0360] filtering out any slot that includes a symbol incompatible with the symbol type of the first transmission and / or that contains a synchronization signal block, SSB, so that only slots with the same symbol type are used for the one or more repeated transmissions.
[0361] The SSB or synchronization signal block may refer to Synchronization / PBCH block, e.g. wherein synchronization signal and PBCH (physical broadcast channel) are arranged in a single block of the time-frequency domain.
[0362] Embodiments of the method may ensure that no incompatible or reserved symbols (for example, downlink symbols or symbols carrying synchronization signals) interfere with the repeated transmissions, e.g., thereby enhancing reception reliability.
[0363] 4. The method (300) of any one of embodiments 1 to 3, further comprising:
[0364] counting a specified number of slots, optionally consecutive slots, in which the indicated symbol type is valid,
[0365] wherein those slots are used for the repeated transmissions (304).
[0366] Strictly counting only those slots meeting the symbol-type requirement may allow an embodiment of the radio device to methodically schedule the repeated transmissions, e.g., improving efficiency and reliability of the RA procedure.
[0367] 5. The method (300) of any one of embodiments 1 to 4, further comprising:
[0368] receiving, from the network node (200), a parameter indicating a cellspecific offset applicable to a starting slot for the first transmission or the repeated transmissions,
[0369] optionally wherein the radio device (100) applies the offset and verifies that each candidate slot contains only the indicated symbol type.
[0370] By incorporating a cell-specific offset, an embodiment of the method can ensure proper alignment of the repeated transmissions with cell-wide timing, thereby reducing collisions and improving throughput for transmissions (e.g., message-3 transmissions).Telefonaktiebolaget LM Ericsson (pu bl) 40 / 54
[0371] P112973WO01
[0372] 6. The method (300) of any one of embodiments 1 to 5, further comprising:
[0373] obtaining from the network node (200) a second resource configuration that indicates a different symbol type for repeated transmissions or a retransmission of the message, and optionally:
[0374] modifying the slot counting to exclude all slots that do not match the indicated different symbol type.
[0375] Allowing a transition to a different symbol type for later retransmissions accommodates changing network conditions (e.g., interference levels), thereby optimizing random-access performance under varying traffic loads.
[0376] 7. The method (300) of embodiment 6, wherein upon receiving the different symbol type for the repeated transmissions or the retransmission, the radio device (100) restarts a slot counting procedure from the earliest subsequent slot conforming to the indicated different symbol type.
[0377] The retransmission may avoid overlap with slots configured for the previous symbol type. Alternatively or in addition, dynamically restarting the slot counting may ensures that symbol-type transitions remain synchronized, e.g., preventing partial or incorrect overlaps between subband-full-duplex and non-subband-full-duplex slots.
[0378] The method may be performed responsive to or if subband-full-duplex (SBFD) operation is enabled by the network node. The network node may be a serving network node of the radio device.
[0379] 8. The method (300) of any one of embodiments 1 to 7, further comprising:
[0380] determining, optionally based on system information received from the network node (200), that subband-full-duplex operation is enabled by the network node (200), optionally in the serving cell of the network node (200), optionally in response, excluding from the repeated transmissions of the message any slot or symbol that is not indicated as subband-full-duplex and / or that is designated as a guard band.
[0381] Restricting transmissions to subband-full-duplex slots (and / or excluding guard bands) may allow embodiments of the radio device to exploit SBFD capabilities without introducing interference or relying on resources that are unavailable for uplink transmission.Telefonaktiebolaget LM Ericsson (pu bl) 41 / 54
[0382] P112973WO01
[0383] 9. The method of any one of embodiments 1 to 8, wherein the radio device (100) excludes any symbol, and / or slot comprising any symbol, allocated to a different frequency subband carrying signals in an opposite direction or in a downlink.
[0384] Embodiments of the radio device may ensure that uplink and downlink transmissions do not coincide within the same repetition occasion (e.g., any slot used for the repeated transmissions).
[0385] By prohibiting mixing of uplink and downlink directions in a single or each repetition of the transmission of the message, embodiments of the radio device can enhance isolation between directions, thereby increasing transmission reliability in subband-full-duplex deployments.
[0386] 10. The method of any one of embodiments 1 to 9, further comprising:
[0387] deriving an implicit or explicit indication of the symbol type for the repeated transmissions from a physical resource allocation used in the first transmission, and / or
[0388] wherein if only subband-full-duplex resources were allocated in the first transmission, the radio device (100) infers subband-full-duplex as the symbol type.
[0389] Inferring the symbol type based on the first allocation obviates the need for extra signaling, reducing configuration signaling overhead and / or ensuring that repeated transmissions remain aligned with the initially allocated symbol type.
[0390] 11. The method (300) of any one of embodiments 1 to 10, wherein the radio device (100) excludes from the slot counting and / or the repeated transmissions slots that comprise, or overlap with, a symbol configured for an alternate symbol type other than the symbol type and / or reserved for synchronization signals.
[0391] Embodiments may thereby preserve consistent usage of a single symbol type across all repetitions. Alternatively or in addition, eliminating partial overlap of differing symbol types can avoid conflicts in the transmission (e.g., message-3 transmission), mitigating interference and ensuring coherent random-access operation under subband-full-duplex or non-subband-full-duplex scenarios alike.Telefonaktiebolaget LM Ericsson (pu bl) 42 / 54
[0392] P112973WO01
[0393] 12. The method (300) of any one of embodiments 1 to 11, wherein the method (300) is performed if, optionally only if, or responsive to:
[0394] - the network node (200) serves the radio device (100) in a cell in which SBFD operation is enabled or in which RA is enabled, and / or
[0395] - the network node (200) provides an indication that SBFD RA is enabled, and / or - the network node (200) provides an additional RACH configuration.
[0396] In one embodiment, SBFD or non-SBFD is determined by the scheduling location of the first repetition.
[0397] 13. The method (300) of any one of embodiments 1 to 12, wherein the symbol type is non-SBFD, and
[0398] wherein the repeated transmission of the message are transmitted if a physical uplink control channel, PUSCH, of the transmission does not include a symbol
[0399] - indicated as downlink, optionally by tdd-UL-DL-ConfigurationCommon, and / or
[0400] - indicated as a symbol of an SS / PBCH block, SSB, with index provided by ssb- PositionsInBurst and / or
[0401] - indicated as a symbol type being SBFD, optionally by tdd-UL-DL- ConfigurationCommon.
[0402] 14. The method (300) of any one of embodiments 1 to 13, wherein the symbol type is SBFD, and
[0403] wherein the repeated transmission of the message are transmitted if a physical uplink control channel, PUSCH, of the transmission in one or more SBFD symbols does not include a symbol indicated as a non-SBFD symbol, optionally by tdd-UL-DL-ConfigurationCommon.
[0404] 15. The method (300) of any one of embodiments 1 to 14, wherein the symbol type is SBFD, and
[0405] wherein the repeated transmission of the message are transmitted if a physical uplink control channel, PUSCH, of the transmission in one or more SBFD symbols only includes symbols indicated as SBFD symbols, optionally by tdd-UL-DL-ConfigurationCommon.Telefonaktiebolaget LM Ericsson (pu bl) 43 / 54
[0406] P112973WO01
[0407] 16. The method (300) of any one of embodiments 1 to 15, wherein the symbol type is SBFD, and
[0408] wherein the repeated transmission of the message are transmitted if a physical uplink control channel, PUSCH, of the transmission in one or more SBFD symbols does not include a symbol
[0409] - indicated as a non-SBFD symbol, optionally by tdd-UL-DL- ConfigurationCommon and / or
[0410] - indicated as a symbol of an SS / PBCH block, SSB, optionally with index provided by ssb-PositionsInBurst.
[0411] 17. The method (300) of any one of embodiments 1 to 16, wherein the repeated transmission of the message are transmitted if a physical uplink control channel, PUSCH, of the transmission does not include a symbol
[0412] - indicated as downlink, optionally by by tdd-UL-DL-ConfigurationCommon and / or
[0413] - indicated as a symbol of an SS / PBCH block, SSB, optionally with index provided by ssb-PositionsInBurst and / or
[0414] having a symbol type different from the initial symbol of the first transmission.
[0415] 18. The method (300) of any one of embodiments 1 to 17, wherein the first transmission relates to scheduling grant received from the network node (200) in the RA procedure, optionally in a message-2 of the RA procedure.
[0416] 19. A method (400) performed by a network node (200) in a radio access network (500), the method (400) comprising:
[0417] providing (402) an indication to a radio device (100) of whether subbandbased full-duplex, SBFD, operation is enabled for an uplink message; and allocating (404) repeated uplink transmission resources for the radio device (100) such that the repeated transmissions use only one symbol type among SBFD symbols or non-SBFD symbols.
[0418] By signaling the availability of subband-based full-duplex (SBFD) operation and confining repeated transmissions to a single symbol type, embodiments of the network node can ensure compatibility with SBFD-aware procedures while avoiding conflicting uplink / downlink assignments, thus enabling robust and predictable scheduling of repeated uplink transmissions.Telefonaktiebolaget LM Ericsson (pu bl) 44 / 54
[0419] P112973WO01
[0420] 20. the method (400) of embodiment 19, the method (400) further comprising:
[0421] signaling, within a scheduling grant or RA response message, an explicit indicator that identifies which subband(s) and which symbol type are to be used by the radio device for said repeated uplink transmissions.
[0422] The scheduling grant or RA response message may be a message-2 of the RA procedure.
[0423] By providing an explicit indicator in the control or response message, the network node enables the radio device to unambiguously determine the frequency subband(s) and symbol direction (uplink only) for the repetitions, ensuring efficient utilization and reduced collision risk.
[0424] 21. The method (400) of embodiment 20, further comprising the features and the steps of any one of embodiments 2 to 18, or any feature or step corresponding thereto.
[0425] 22. A computer program product comprising program code portions for performing the steps of any one of the embodiments 1 to 18 and / or 19 to 21 when the computer program product is executed on one or more computing devices (1104; 1204), optionally stored on a computer-readable recording medium (1106; 1206).
[0426] 23. A radio device (100) comprising memory operable to store instructions and processing circuitry operable to execute the instructions, such that the radio device (100) is operable to:
[0427] obtain, from a network node (200) of a RAN (500), a resource configuration that indicates a symbol type for a first transmission of a message in a RA procedure, the symbol type being either subband-full-duplex, SBFD, or non-subband-full-duplex, non-SBFD; and
[0428] transmit one or more repeated transmissions of the message in subsequent slots, each repeated transmission being restricted to the same symbol type.
[0429] 24. The radio device (100) of embodiment 23, further operable to perform the steps of any one of embodiments 2 to 18.Telefonaktiebolaget LM Ericsson (pu bl) 45 / 54
[0430] P112973WO01
[0431] 25. A radio device (100) for random access, RA, to a radio access network, RAN (500), the radio device (100) being configured to:
[0432] obtain, from a network node (200) of the RAN (500), a resource configuration that indicates a symbol type for a first transmission of a message in a RA procedure, the symbol type being either subband-full-duplex, SBFD, or non-subband-full-duplex, non-SBFD; and
[0433] transmit one or more repeated transmissions of the message in subsequent slots, each repeated transmission being restricted to the same symbol type.
[0434] 26. The radio device (100) of embodiment 25, further configured to perform the steps of any one of embodiments 2 to 18.
[0435] 27. A network node (200) comprising memory operable to store instructions and processing circuitry operable to execute the instructions, such that the network node (200) is operable to:
[0436] provide an indication to a radio device (100) of whether subband-based full-duplex, SBFD, operation is enabled for an uplink message; and
[0437] allocate repeated uplink transmission resources for the radio device (100) such that the repeated transmissions use only one symbol type among SBFD symbols or non-SBFD symbols.
[0438] 28. The network node (200) of embodiment 27, further operable to perform any one of the steps of any one of embodiments 20 and 21.
[0439] 29. A network node (200) in a radio access network, RAN (500), the network node (200) being configured to:
[0440] provide an indication to a radio device (100) of whether subband-based full-duplex, SBFD, operation is enabled for an uplink message; and
[0441] allocate repeated uplink transmission resources for the radio device (100) such that the repeated transmissions use only one symbol type among SBFD symbols or non-SBFD symbols.
[0442] 30. The network node (200) of embodiment 29, further configured to perform the steps of any one of embodiment 20 and 21.
Claims
Telefonaktiebolaget LM Ericsson (pu bl) 46 / 54P112973WO01List of Claims1. A method (3000) performed by a radio device (100) for random access, RA, in a radio access network, RAN (500), the method (300) comprising:obtaining (3002), from a network node (200) in the RAN (500), an uplink grant allocating a resource for a first transmission of a message in a RA procedure, wherein a symbol type of the allocated resource is either subband-full-duplex, SBFD, or non-subband-full-duplex, non-SBFD; andtransmitting (3004) one or more repeated transmissions of the message in a subsequent required number of slots, each repeated transmission being restricted to a valid symbol type being the symbol type of the allocated resource of the first transmission.
2. The method (3000) of claim 1, wherein a slot is counted in the required number of slots based on a slot counting rule associated with the valid symbol type.
3. The method (3000) of claim 2, wherein the slot counting rule associated with the valid symbol type comprises at least one of:in case the valid symbol type is SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all SBFD symbol;in case the valid symbol type is non-SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all non-SBFD symbol; ora slot containing a transmission that is not in the valid symbol type is not counted in the required number of slots.
4. The method (3000) of any one of claims 1 to 3, wherein the message is message-3 of the RA procedure.
5. The method (3000) of any one of claims 1 to 4, further comprising:counting the required number of slots to reach a required number of repeated transmissions of the message.
6. The method (3000) of any one of claims 1 to 5, wherein the valid symbol type is non-SBFD, andTelefonaktiebolaget LM Ericsson (pu bl) 47 / 54P112973WO01wherein a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a physical uplink control channel, PUSCH, of the repeated transmission does not include a symbol - indicated as downlink by tdd-UL-DL-ConfigurationCommon, and / or- indicated as a symbol of an SS / PBCH block, SSB, with index provided by ssb- PositionsInBurst and / or- indicated as a symbol type being SBFD by tdd-UL-DL-ConfigurationCommon.
7. The method (3000) of any one of claims 1 to 6, wherein the valid symbol type is SBFD, andwherein a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a physical uplink control channel, PUSCH, of the repeated transmission only includes symbols indicated as SBFD symbols by tdd-UL-DL-ConfigurationCommon.
8. The method (3000) of any one of claims 1 to 7, wherein the valid symbol type is SBFD, andwherein a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a physical uplink control channel, PUSCH, of the repeated transmission does not include a symbol - indicated as a non-SBFD symbol by tdd-UL-DL-ConfigurationCommon and / or- indicated as a symbol of an SS / PBCH block, SSB, by ssb-PositionsInBurst.
9. A method (4000) performed by a network node (200) for random access, RA, in a radio access network (500), the method (400) comprising:providing (4002), to a radio device (100) in the RAN (500), an uplink grant allocating a resource for a first transmission of a message in a RA procedure, wherein a symbol type of the allocated resource is either subband-full-duplex, SBFD, or non-subband-full-duplex, non-SBFD; andreceiving (4004) one or more repeated transmissions of the message in a subsequent required number of slots, each repeated transmission being restricted to a valid symbol type being the symbol type of the allocated resource of the first transmission.Telefonaktiebolaget LM Ericsson (pu bl) 48 / 54P112973WO0110. The method (4000) of claim 9, wherein a slot is counted in the required number of slots based on a slot counting rule associated with the valid symbol type.
11. The method (4000) of claim 10, wherein the slot counting rule associated with the valid symbol type comprises at least one of:in case the valid symbol type is SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all SBFD symbol;in case the valid symbol type is non-SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all non-SBFD symbol; ora slot containing a transmission that is not in the valid symbol type is not counted in the required number of slots.
12. The method (4000) of any one of claims 9 to 11, wherein the message is message-3 of the RA procedure.
13. The method (4000) of any one of claims 9 to 12, further comprising:counting the required number of slots to reach a required number of repeated transmissions of the message.
14. The method (4000) of any one of claims 9 to 13, wherein the valid symbol type is non-SBFD, andwherein a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a physical uplink control channel, PUSCH, of the repeated transmission does not include a symbol - indicated as downlink by tdd-UL-DL-ConfigurationCommon, and / or- indicated as a symbol of an SS / PBCH block, SSB, with index provided by ssb- PositionsInBurst and / or- indicated as a symbol type being SBFD by tdd-UL-DL-ConfigurationCommon.
15. The method (4000) of any one of claims 9 to 14, wherein the valid symbol type is SBFD, andwherein a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a physical uplinkTelefonaktiebolaget LM Ericsson (pu bl) 49 / 54P112973WO01control channel, PUSCH, of the repeated transmission only includes symbols indicated as SBFD symbols by tdd-UL-DL-ConfigurationCommon.
16. The method (4000) of any one of claims 9 to 15, wherein the valid symbol type is SBFD, andwherein a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a physical uplink control channel, PUSCH, of the repeated transmission does not include a symbol - indicated as a non-SBFD symbol by tdd-UL-DL-ConfigurationCommon and / or- indicated as a symbol of an SS / PBCH block, SSB, by ssb-PositionsInBurst.
17. A radio device (100) comprising memory operable to store instructions and processing circuitry operable to execute the instructions, such that the radio device (100) is operable to:obtain, from a network node (200) in a RAN (500), an uplink grant allocating a resource for a first transmission of a message in a RA procedure, wherein a symbol type of the allocated resource is either subband-full-duplex, SBFD, or non-subband-full-duplex, non-SBFD; andtransmit one or more repeated transmissions of the message in a subsequent required number of slots, each repeated transmission being restricted to a valid symbol type being the valid symbol type of the allocated resource of the first transmission.
18. The radio device (100) of claims 17, wherein a slot is counted in the required number of slots based on a slot counting rule associated with the valid symbol type.
19. The radio device (100) of claims 18, wherein the slot counting rule associated with the valid symbol type comprises at least one of:in case the valid symbol type is SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all SBFD symbol;in case the valid symbol type is non-SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all non-SBFD symbol; orTelefonaktiebolaget LM Ericsson (pu bl) 50 / 54P112973WO01a slot containing a transmission that is not in the valid symbol type is not counted in the required number of slots.
20. The radio device (100) of any of claims 17 to 19, wherein the message is message-3 of the RA procedure.
21. The radio device (100) of any one of claims 17 to 20, further configured to count the required number of slots to reach a required number of repeated transmissions of the message.
22. The radio device (100) of any one of claims 17 to 21, wherein the valid symbol type is non-SBFD, andwherein a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a physical uplink control channel, PUSCH, of the repeated transmission does not include a symbol - indicated as downlink by tdd-UL-DL-ConfigurationCommon, and / or- indicated as a symbol of an SS / PBCH block, SSB, with index provided by ssb- PositionsInBurst and / or- indicated as a symbol type being SBFD by tdd-UL-DL-ConfigurationCommon.
23. The radio device (100) of any one of claims 17 to 22, wherein the valid symbol type is SBFD, andwherein a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a physical uplink control channel, PUSCH, of the repeated transmission only includes symbols indicated as SBFD symbols by tdd-UL-DL-ConfigurationCommon.
24. The radio device (100) of any one of claims 17 to 23, wherein the valid symbol type is SBFD, andwherein a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a physical uplink control channel, PUSCH, of the repeated transmission does not include a symbol - indicated as a non-SBFD symbol by tdd-UL-DL-ConfigurationCommon and / or- indicated as a symbol of an SS / PBCH block, SSB, by ssb-PositionsInBurst.Telefonaktiebolaget LM Ericsson (pu bl) 51 / 54P112973WO0125. A radio device (100) for random access, RA, in a radio access network, RAN (500), the radio device (100) being configured to:obtain, from a network node (200) in the RAN (500), an uplink grant allocating a resource for a first transmission of a message in a RA procedure, a symbol type of the allocated resource is either subband-full-duplex, SBFD, or non-subband-full-duplex, non-SBFD; andtransmit one or more repeated transmissions of the message in a subsequent required number of slots, each repeated transmission being restricted to a valid symbol type being the symbol type of the allocated resource of the first transmission.
26. The radio device (100) of claim 25, further configured to perform the steps of any one of claims 2 to 8.
27. A network node (200) comprising memory operable to store instructions and processing circuitry operable to execute the instructions, such that the network node (200) is operable to:provide, to a radio device (100), an uplink grant allocating a resource for a first transmission of a message in a RA procedure, wherein a symbol type of the allocated resource is either subband-full-duplex, SBFD, or non-subband-full-duplex, non-SBFD; andreceive one or more repeated transmissions of the message in a subsequent required number of slots, each repeated transmission being restricted to a valid symbol type being the symbol type of the allocated resource of the first transmission.
28. The network node (200) of claim 27, wherein a slot is counted in the required number of slots based on a slot counting rule associated with the valid symbol type.
29. The network node (200) of claim 28, wherein the slot counting rule associated with the valid symbol type comprises at least one of:in case the valid symbol type is SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all SBFD symbol;Telefonaktiebolaget LM Ericsson (pu bl) 52 / 54P112973WO01in case the valid symbol type is non-SBFD symbol, a slot is counted in the required number of slots if symbols allocated for each repeated transmission in the slot are all non-SBFD symbol; ora slot containing a transmission that is not in the valid symbol type is not counted in the required number of slots.
30. The network node (200) of any of claims 27 to 29, wherein the message is message-3 of the RA procedure.
31. The network node (200) of any of claims 27 to 30, further operable to count the required number of slots to reach a required number of repeated transmissions of the message.
32. The network node (200) of any of claims 27 to 31, wherein the valid symbol type is non-SBFD, andwherein a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a physical uplink control channel, PUSCH, of the repeated transmission does not include a symbol - indicated as downlink by tdd-UL-DL-ConfigurationCommon, and / or- indicated as a symbol of an SS / PBCH block, SSB, with index provided by ssb- PositionsInBurst and / or- indicated as a symbol type being SBFD by tdd-UL-DL-ConfigurationCommon.
33. The network node (200) of any of claims 27 to 32, wherein the valid symbol type is SBFD, andwherein a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a physical uplink control channel, PUSCH, of the repeated transmission only includes symbols indicated as SBFD symbols by tdd-UL-DL-ConfigurationCommon.
34. The network node (200) of any of claims 27 to 33, wherein the valid symbol type is SBFD, andwherein a slot is counted in the required number of slots for transmitting the repeated transmission of the message if the slot allocated for a physical uplink control channel, PUSCH, of the repeated transmission does not include a symbol - indicated as a non-SBFD symbol by tdd-UL-DL-ConfigurationCommonand / orTelefonaktiebolaget LM Ericsson (pu bl) 53 / 54P112973WO01indicated as a symbol of an SS / PBCH block, SSB, by ssb-PositionsInBurst.
35. A network node (200) in a radio access network, RAN (500), the network node (200) being configured to:provide, to a radio device (100), an uplink grant allocating a resource for a first transmission of a message in a RA procedure, wherein a symbol type of the allocated resource is either subband-full-duplex, SBFD, or non-subband-full-duplex, non-SBFD; andreceive one or more repeated transmissions of the message in a subsequent required number of slots, each repeated transmission being restricted to a valid symbol type being the symbol type of the allocated resource of the first transmission.
36. The network node (200) of claim 35, further configured to perform the steps of any one of claim 10 to 16.