The examples and non-limiting example embodiments relate generally to communications and, more particularly, to a method for mitigating duplexing issues in sidelink carrier aggregation.
It is known to facilitate communication between terminal devices in a communication network.
An apparatus includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: determine whether the apparatus is expected to perform communication on a first carrier within a time interval, and communication on a second carrier within the time interval; determine whether there is a conflict between at least one symbol of the first carrier and at least one symbol of the second carrier within the time interval; determine at least one scheme to use for performing communication with at least one user equipment, when there is the conflict between the at least one symbol of the first carrier and the at least one symbol of the second carrier within the time interval; and perform the communication with the at least one user equipment using the at least one scheme.
An apparatus includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from at least one user equipment, an indication that the at least one user equipment is using at least one scheme to perform communication with the apparatus, when there is the conflict between at least one symbol of a first carrier and at least one symbol of a second carrier within a time interval; and perform the communication with the at least one user equipment with use of the at least one scheme, when there is the conflict between at least one symbol of the first carrier and at least one symbol of the second carrier within the time interval.
An apparatus includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: serve a coverage area comprising at least one first user equipment and at least one second user equipment; receive a configuration from the at least one second user equipment; and transmit the configuration to the at least one first user equipment; wherein the configuration indicates at least one of: a capability of the at least one second user equipment to perform within a time interval the communication on a first carrier and communication on a second carrier, that the at least one second user equipment supports at least one scheme for performing communication with at least one first user equipment, when there is the conflict between at least one symbol of the first carrier and at least one symbol of the second carrier within the time interval, or at least one parameter of the at least one scheme for performing communication with the at least one first user equipment.
The foregoing aspects and other features are explained in the following description, taken in connection with the accompanying drawings.
Turning to
The RAN node 170 in this example is a base station that provides access for wireless devices such as the UE 110 to the wireless network 100. The RAN node 170 may be, for example, a base station for 5G, also called New Radio (NR). In 5G, the RAN node 170 may be a NG-RAN node, which is defined as either a gNB or an ng-eNB. A gNB is a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface (such as connection 131) to a 5GC (such as, for example, the network element(s) 190). The ng-eNB is a node providing E-UTRA user plane and control plane protocol terminations towards the UE, and connected via the NG interface (such as connection 131) to the 5GC. The NG-RAN node may include multiple gNBs, which may also include a central unit (CU) (gNB-CU) 196 and distributed unit(s) (DUs) (gNB-DUs), of which DU 195 is shown. Note that the DU 195 may include or be coupled to and control a radio unit (RU). The gNB-CU 196 is a logical node hosting radio resource control (RRC), SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that control the operation of one or more gNB-DUs. The gNB-CU 196 terminates the F1 interface connected with the gNB-DU 195. The F1 interface is illustrated as reference 198, although reference 198 also illustrates a link between remote elements of the RAN node 170 and centralized elements of the RAN node 170, such as between the gNB-CU 196 and the gNB-DU 195. The gNB-DU 195 is a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CU 196. One gNB-CU 196 supports one or multiple cells. One cell may be supported with one gNB-DU 195, or one cell may be supported/shared with multiple DUs under RAN sharing. The gNB-DU 195 terminates the F1 interface 198 connected with the gNB-CU 196. Note that the DU 195 is considered to include the transceiver 160, e.g., as part of a RU, but some examples of this may have the transceiver 160 as part of a separate RU, e.g., under control of and connected to the DU 195. The RAN node 170 may also be an eNB (evolved NodeB) base station, for LTE (long term evolution), or any other suitable base station or node.
The RAN node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces (N/W I/F(s)) 161, and one or more transceivers 160 interconnected through one or more buses 157. Each of the one or more transceivers 160 includes a receiver, Rx, 162 and a transmitter, Tx, 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153. The CU 196 may include the processor(s) 152, one or more memories 155, and network interfaces 161. Note that the DU 195 may also contain its own memory/memories and processor(s), and/or other hardware, but these are not shown.
The RAN node 170 includes a module 150, comprising one of or both parts 150-1 and/or 150-2, which may be implemented in a number of ways. The module 150 may be implemented in hardware as module 150-1, such as being implemented as part of the one or more processors 152. The module 150-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the module 150 may be implemented as module 150-2, which is implemented as computer program code 153 and is executed by the one or more processors 152. For instance, the one or more memories 155 and the computer program code 153 are configured to, with the one or more processors 152, cause the RAN node 170 to perform one or more of the operations as described herein. Note that the functionality of the module 150 may be distributed, such as being distributed between the DU 195 and the CU 196, or be implemented solely in the DU 195.
The one or more network interfaces 161 communicate over a network such as via the links 176 and 131. Two or more gNBs 170 may communicate using, e.g., link 176. The link 176 may be wired or wireless or both and may implement, for example, an Xn interface for 5G, an X2 interface for LTE, or other suitable interface for other standards.
The one or more buses 157 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, wireless channels, and the like. For example, the one or more transceivers 160 may be implemented as a remote radio head (RRH) 195 for LTE or a distributed unit (DU) 195 for gNB implementation for 5G, with the other elements of the RAN node 170 possibly being physically in a different location from the RRH/DU 195, and the one or more buses 157 could be implemented in part as, for example, fiber optic cable or other suitable network connection to connect the other elements (e.g., a central unit (CU), gNB-CU 196) of the RAN node 170 to the RRH/DU 195. Reference 198 also indicates those suitable network link(s).
A RAN node/gNB can comprise one or more TRPs to which the methods described herein may be applied.
A relay node in NR is called an integrated access and backhaul node. A mobile termination part of the IAB node facilitates the backhaul (parent link) connection. In other words, the mobile termination part comprises the functionality which carries UE functionalities. The distributed unit part of the IAB node facilitates the so called access link (child link) connections (i.e. for access link UEs, and backhaul for other IAB nodes, in the case of multi-hop IAB). In other words, the distributed unit part is responsible for certain base station functionalities. The IAB scenario may follow the so called split architecture, where the central unit hosts the higher layer protocols to the UE and terminates the control plane and user plane interfaces to the 5G core network.
It is noted that the description herein indicates that “cells” perform functions, but it should be clear that equipment which forms the cell may perform the functions. The cell makes up part of a base station. That is, there can be multiple cells per base station. For example, there could be three cells for a single carrier frequency and associated bandwidth, each cell covering one-third of a 360 degree area so that the single base station's coverage area covers an approximate oval or circle. Furthermore, each cell can correspond to a single carrier and a base station may use multiple carriers. So if there are three 120 degree cells per carrier and two carriers, then the base station has a total of 6 cells.
The wireless network 100 may include a network element or elements 190 that may include core network functionality, and which provides connectivity via a link or links 181 with a further network, such as a telephone network and/or a data communications network (e.g., the Internet). Such core network functionality for 5G may include location management functions (LMF(s)) and/or access and mobility management function(s) (AMF(S)) and/or user plane functions (UPF(s)) and/or session management function(s) (SMF(s)). Such core network functionality for LTE may include MME (mobility management entity)/SGW (serving gateway) functionality. Such core network functionality may include SON (self-organizing/optimizing network) functionality. These are merely example functions that may be supported by the network element(s) 190, and note that both 5G and LTE functions might be supported. The RAN node 170 is coupled via a link 131 to the network element 190. The link 131 may be implemented as, e.g., an NG interface for 5G, or an SI interface for LTE, or other suitable interface for other standards. The network element 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N/W I/F(s)) 180, interconnected through one or more buses 185. The one or more memories 171 include computer program code 173. Computer program code 173 may include SON and/or MRO functionality 172.
The wireless network 100 may implement network virtualization, which is the process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, or a virtual network. Network virtualization involves platform virtualization, often combined with resource virtualization. Network virtualization is categorized as either external, combining many networks, or parts of networks, into a virtual unit, or internal, providing network-like functionality to software containers on a single system. Note that the virtualized entities that result from the network virtualization are still implemented, at some level, using hardware such as processors 152 or 175 and memories 155 and 171, and also such virtualized entities create technical effects.
The computer readable memories 125, 155, and 171 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, non-transitory memory, transitory memory, fixed memory and removable memory. The computer readable memories 125, 155, and 171 may be means for performing storage functions. The processors 120, 152, and 175 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multi-core processor architecture, as non-limiting examples. The processors 120, 152, and 175 may be means for performing functions, such as controlling the UE 110, RAN node 170, network element(s) 190, and other functions as described herein.
In general, the various example embodiments of the user equipment 110 can include, but are not limited to, cellular telephones such as smart phones, tablets, personal digital assistants (PDAs) having wireless communication capabilities, portable computers having wireless communication capabilities, image capture devices such as digital cameras having wireless communication capabilities, gaming devices having wireless communication capabilities, music storage and playback devices having wireless communication capabilities, internet appliances including those permitting wireless internet access and browsing, tablets with wireless communication capabilities, head mounted displays such as those that implement virtual/augmented/mixed reality, as well as portable units or terminals that incorporate combinations of such functions. The UE 110 can also be a vehicle such as a car, or a UE mounted in a vehicle, a UAV such as e.g. a drone, or a UE mounted in a UAV. The user equipment 110 may be terminal device, such as mobile phone, mobile device, sensor device etc., the terminal device being a device used by the user or not used by the user.
UE 110, RAN node 170, and/or network element(s) 190, (and associated memories, computer program code and modules) may be configured to implement (e.g. in part) the methods described herein, including a method for mitigating duplexing issues in sidelink carrier aggregation. Thus, computer program code 123, module 140-1, module 140-2, and other elements/features shown in
Having thus introduced a suitable but non-limiting technical context for the practice of the example embodiments, the example embodiments are now described with greater specificity.
The examples described herein relate to a method where a sidelink UE is configured for carrier aggregation and performs steps/signaling. In particular, the UE is configured to determine conflicting symbols in SL CA transmissions depending on its capability. This way the UE determines whether it should perform a transmission/reception of a channel on a first carrier and initiate also a transmission/reception interval on a second carrier. Related to this is the determination of if there is a conflict on the symbols where simultaneous transmission/reception occurs.
There are two main 3GPP sidelink technologies for vehicle-to-everything (V2X) direct communications: 3GPP Rel-14/15 LTE-V2X PC5 mode 4 and 3GPP Rel-16/17 5G NR-V2X PC5 mode 2.
Rel-14/15 LTE-V2X PC5 mode 4 employs discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) for sidelink at the PHY layer. Time-frequency radio resources are divided into subframes in the time domain and sub-channels in the frequency domain. LTE-V2X supports only 15-kHz sub-carrier spacing (SCS). Each subframe is 1-ms in length and consists of 14 DFT-s-OFDM symbols. Each sub-channel consists of multiple contiguous physical resource blocks (PRBs), where each PRB occupies 180 kHz and consists of 12 subcarriers with 15 kHz SCS, and the size of the sub-channel (i.e., the number of PRBs per sub-channel) is (pre-) configurable. To cope with high Doppler caused by high relative speed in vehicular scenarios, the density of demodulation reference signal (DMRS), which is used for frequency offset compensation and channel estimation, is set to four per subframe. Each user equipment (UE) broadcasts data (TB: transport block) in the physical sidelink shared channel (PSSCH) as well as sidelink control information (SCI) Format 1 in the physical sidelink control channel (PSCCH). PSCCH occupies two contiguous PRBs, whereas the number of PRBs for PSSCH is (pre-) configured. SCI Format 1 contains necessary information to decode its corresponding TB in PSSCH and facilitate UE autonomous resource selection. The resource reservation interval can be set to one of the allowed values (20, 50, 100, 200, 300, . . . , 1000 ms). PSCCH and the corresponding PSSCH need to be transmitted in the same subframe in either adjacent or non-adjacent PRBs in the frequency domain.
The resource selection procedure is specified in 3GPP TS 36.213 and TS 36.321.
Referring to
Rel-15 LTE-V2X PC5 mode 4 supports sidelink carrier aggregation (SL CA). Multiple sidelink carriers (i.e., multiple V2X channels) can be used to increase the throughput and/or improve the reliability. To increase the throughput, multiple MAC PDUs can be transmitted on multiple sidelink carriers. To improve the reliability, PDCP duplication is supported, in which the same PDCP packet is transmitted on multiple sidelink carriers. 3GPP TS 36.321 Clause 5.14.1.5 specifies the Tx carrier (re-) selection procedure to (re-) select sidelink carriers for transmission based on the measured CBR for each sidelink carrier. In the Tx carrier (re-) selection procedure, the Tx UE considers sidelink carriers as candidate sidelink carriers if the measured CBR of the sidelink carrier is below a (pre-) configured CBR threshold (associated with priority). Then, Tx UE selects one or more sidelink carrier(s) among the candidate sidelink carriers with increasing order of CBR from the lowest CBR. It is left to UE implementation how many sidelink carriers Tx UE selects based on UE capability. For each selected sidelink carrier, LTE SL CA reuses the sensing and resource selection procedure in Rel-14 LTE-V2X PC5 mode 4 (i.e., UE selects resources independently on each involved carrier based on Rel-14 sensing and resource selection procedure. The Rel-14 resource selection procedure does, however, take into account the Tx UE capability on whether it can transmit on multiple carriers at a time or not, such that the resource procedure does not select resources for transmission that violate the Tx UE capabilities. The same sidelink carriers are used at least until the process triggers Tx carrier re-selection.
Rel-16/17 5G NR-V2X PC5 mode 2 employs orthogonal frequency division multiplexing (OFDM) at the PHY layer. Time-frequency radio resources are divided into slots in the time domain and sub-channels in the frequency domain. NR-V2X supports SCSs of 15·2m kHz, where m is the OFDM numerology m={0, 1, 2, 3, 4}. For sub-6 GHz frequency, SCSs of 15, 30, and 60 kHz (i.e., m={0, 1, 2}) are supported, whereas for above 6 GHZ frequency, SCSs of 60, 120, and 240 kHz (i.e., m={2, 3, 4}) are supported. Each slot is ½″ ms length and consists of 14 OFDM symbols. Each sub-channel consists of multiple contiguous physical resource blocks (PRBs), where each PRB occupies 180·2m kHz and consists of 12 subcarriers with 15·2m KHz SCS, and the size of sub-channel (i.e., the number of PRBs per sub-channel) is (pre-) configurable. To support multiple SCSs and different Doppler spreads, multiple DMRS density options (2˜4 DMRS symbols per slot) are supported. Each UE transmit 1st-stage SCI (SCI format 1-A) in the PSCCH and data (TB: transport block) as well as 2nd-stage SCI (SCI format 2-A or 2-B) in the PSSCH. HARQ feedback (ACK/NACK or NACK only) may be transmitted.
The resource selection procedure is specified in 3GPP 38.213, TS 38.214, and TS 38.321.
Referring to
As further shown in
In order for a UE to perform sensing and obtain the necessary information to receive other UEs' packets, the UE needs to decode SCI first. In Rel-16, there are 1st-stage SCI (SCI format 1-A) and 2nd-stage SCI (SCI format 2-A or 2-B) as defined in 3GPP TS 38.212. 1st-stage SCI carries resource reservation information for future transmissions, as well as information about resource allocation and MCS for PSSCH, DMRS pattern, 2nd-stage SCI format, etc. 2nd-stage SCI carries control information for HARQ procedures, source/destination IDs, necessary information for distance-based groupcast (UE's zone ID and communication range requirement), etc. Based on resource reservation contained in 1st-stage SCI, each UE avoids using reserved time/frequency resources by other UEs for its resource (re-) selection.
In Rel-17 5G NR-V2X PC5 mode 2, inter-UE coordination (IUC) is introduced, in which a UE-A sends coordination information about resources to a UE-B, and then the UE-B utilizes that information for its resource (re-) selection. The following schemes of inter-UE coordination are supported (1-2 as follows):
There is a one-to-one mapping between a PSSCH resource and a PSFCH resource. This allows a receiver and transmitter to determine which PSSCH resource (slot and sub-channel) the information in the PSFCH resource refers to. When more than one sub-channel are used in PSSCH, then multiple PSFCH resources are also used.
Rel-16/17 5G NR-V2X PC5 mode 2 does not support sidelink carrier aggregation.
In Rel-16 (the work item “5G V2X with NR sidelink”), PSFCH for sidelink communication was specified to carry HARQ feedback over the sidelink (at the physical layer) from a UE which is an intended recipient of a PSSCH transmission (henceforth an Rx UE) to the UE which performed the transmission (henceforth a Tx UE).
PSFCH transmits a Zadoff-Chu sequence in one PRB repeated over two OFDM symbols, the first of which can be used for AGC, near the end of the sidelink resource in a slot. An example of slot format of PSCCH, PSSCH, and PSFCH is provided in
The time resources for PSFCH are (pre-) configured to occur once in every 1, 2, or 4 slots. HARQ feedback is disabled if periodicity is set to 0 (see SL-PSFCH-Config in TS 38.331). The HARQ feedback resource (PSFCH) is derived from the resource location of PSCCH/PSSCH.
For PSSCH-to-HARQ timing, the gNB 170 configures a parameter K with the unit of slot. The time occasion for PSFCH is determined from K. For a PSSCH transmission with its last symbol in slot n, HARQ feedback is in slot n+a where a is the smallest integer larger than or equal to K with the condition that slot n+a contains PSFCH resources, for example, if the period of PSFCH resources is configured as 1, and K is configured as 2. For a PSSCH transmitted in slot 1, the time occasion for the corresponding PSFCH is slot 3.
In SL-CA it may happen that the PSFCH is configured differently for each of the carriers, e.g., with different periodicity (4 options are supported in current SL specification, as mentioning previously) or different subcarrier spacings over the different carriers (e.g., due to a legacy configuration in one of the carriers, or because one carrier coexists with LTE and uses 15 kHz and another carrier uses 30 kHz).
A half-duplexing issue may arise when mismatch occurs, depending on the UE capability related to transmitting and receiving simultaneously on different component carriers (CC) s, band combinations, and switching time. Receiving and transmitting simultaneously is particularly challenging when the frequency separation between CCs is low.
As an example, as shown in
As another example, as shown in
Power control may also be affected if UE 110 needs to switch on in the other carrier in the middle of the slot, while transmitting in another carrier.
A trivial solution could be to only configure carriers with similar configuration. However that solution may not be always applicable, for example, in case there is a legacy deployment which cannot be changed in certain carriers.
Rel-14/15 LTE-V2X supports carrier aggregation, however it does not support PSFCH, and there is also a single subcarrier spacing supported, so the discussed issue is not covered in LTE. Rel-16/17 5G NR PC5 mode 2 does not support sidelink carrier aggregation, so the issue is not present and not covered in 5G NR sidelink either.
Described herein is a method for a SL UE configured for carrier aggregation, that includes the following (1-3):
The UE 110 may decide if/when to apply one of the schemes depending, e.g., on capability, timing and priorities of the channels on the different carriers, and UE 110 may indicate if it applies the scheme (more details described herein). Alternatively or in addition, the one or more scheme(s) to apply may be decided by network configuration, e.g. via RRC configuration, or may be decided via pre-configuration in the terminal or USIM.
Thus, as shown in
The solution may be implemented or specified including steps according to the flowchart depicted in
Alternatively, the capability and scheme configuration can be exchanged through the network (e.g. through a gNB, access point, or base station such as RAN node 170).
At 904, UE1110 determines conflicting symbols, based on reserved PSCCH/PSFCH resources, and expected PSFCH reception/transmissions. At 906, UE1110 prepares PSCCH/PSFCH transmission applying puncturing, rate matching and/or a subslot scheme. At 908, UE1110 transmits to UE2110-2 whether UE1110 is applying puncturing, rate matching or a subslot scheme (e.g., via PSCCH) for a channel in a certain carrier. At 910, UE1110-1 transmits PSCCH or PSFCH to UE2110-2 based on the applied scheme.
Accordingly, the examples described herein include communication between a user equipment and another user equipment configured for carrier aggregation, and the communication of the another user equipment with the user equipment comprises transmission or reception over a channel of the first carrier and transmission or reception over a channel of the second carrier, wherein the channel of the first carrier and the channel of the second carrier comprises a physical sidelink control channel, a physical sidelink shared channel, a physical sidelink feedback channel, or a sidelink synchronization signal block. The sidelink synchronization signal block (S-SSB) may carry a physical sidelink broadcast channel (PSBCH) as well as a sidelink primary synchronization signal (S-PSS) and a sidelink secondary synchronization signal (S-SSS).
In an embodiment, the SL UEs indicate capability related to simultaneous reception/transmission between sets of carriers, e.g., via RRC signaling, via MAC signaling, during capability transfer, during RRC connection setup as a part of a RRC connection setup complete message, or as part of UE assistance information, or during RP configuration. The capability can also be mandatory for a certain version or release of the standard, or associated with another capability e.g., with SL CA capability or defined as a default or fallback capability.
The UE may indicate whether it can transmit in a channel (e.g., PSFCH) and receive in another channel (e.g. PSSCH) simultaneously between groups of carriers. In some cases, the UE may be capable of such between one group of carriers (e.g. which are far separated in frequency), while it is not capable of such between another group of carriers (e.g., which are close to each other in frequency, or which are operated under a same front-end component on the UE).
The UE may also indicate whether it has the capability of initiating a transmission (e.g., PSFCH) in a carrier during an ongoing transmission (e.g. PSSCH) in another carrier. Instead or in addition, the UE may also indicate if it can initiate a reception in a carrier during an ongoing reception in another carrier.
The UE may also indicate the switch time between transmission and reception, and/or indicate whether it supports a predefined switch time requirement.
The UE may also indicate capability related to whether it supports transmitting/receiving rate matched transmission, and/or receiving transmission in a subslot. Not indicating this capability may imply the UE is a legacy UE which does not support the scheme.
In one embodiment, a UE may detect the capability of an RX UE and applies the corresponding scheme. E.g., if RX UE is not capable of decoding rate matched or subslot transmission, the TX UE applies puncturing. In this case, the TX UE may apply a lower MCS in order to increase the chance of successful reception of the slot with punctured symbol(s).
In another embodiment, the UE may decide whether to apply the scheme depending on the priority of the channels to be transmitted/received over the different carriers. In some cases, if priority of one channel is higher, or much higher, than the other (e.g., the priority difference is higher than a certain threshold), the UE may completely skip transmitting/receiving one or more of the channel(s) which is/are leading to conflict among another carrier, or different carriers.
In another embodiment, the UE may decide whether to apply the scheme depending on the timing occasion where conflicting symbol(s) occur (recall, a conflicting symbol refers to a symbol time duration where the UE expects to receive and transmit on different carriers simultaneously but does not have the capability to do so). In some cases, if conflicting symbol(s) occur in the beginning of the slot, e.g., overlapping with PSCCH and the RX UE does not have capability to decode in subslot after conflicting symbols, the TX UE may skip one or more of the channels (it may be predefined which channel it should skip, or if the priorities are different, the TX UE skips the one with lowest priority).
In another embodiment, the occasions where guard symbols on one carrier overlap with non-guard symbols in another carrier may also be considered conflicting symbols, depending e.g., on switching time. If switching time is long and the UE has to switch between transmission and reception over the different carriers, the guard symbols may also be punctured, and/or not used in rate-matching and/or subslot tx/rx.
In another embodiment, if the TX and/or the RX UEs do not support the transmission scheme, the UEs determine based on configuration or a pre-defined rule to not use the slots where the conflict occurs. E.g., the slots where the conflict occurs are excluded from the candidate resource set.
In another embodiment, if the TX UE does not comprehend the RX UE's indicated capabilities, e.g., due to future extensions, the UEs may make use of a pre-defined fallback or default transmission scheme.
In another embodiment, the TX UE and/or RX may change their capabilities by adding or removing capabilities in a reconfiguration message or upon capability enquiry to change the transmission scheme e.g., depending on the outcome of previous transmission occasions.
In another embodiment, the TX UE and/or RX UE may decide whether or not to apply the scheme(s) depending on the target destination of their transmissions when conflicting symbols occur. For example, even when conflicting symbols occur (e.g., PSCCH/PSSCH transmission by the TX UE on one carrier and PSFCH transmission by the RX UE on another carrier), if the RX UE is not a target UE of PSCCH/PSSCH transmission by the TX UE, the TX UE does not apply the scheme. Similarly, instead or in addition, if the TX UE is not a target UE of PSFCH transmission by the RX UE, the RX UE does not apply the scheme.
In another embodiment, the TX UE and/or RX UE may decide whether or not to apply one or more scheme(s) based on measurements related to the other UE, e.g. RSRP, RSSI, energy level. For example, the scheme(s) could be performed by the TX UE and/or RX UE only if the measured RSRP, RSSI, and/or energy level from the other UE exceeds one or more threshold(s), or is below one or more threshold(s).
In another embodiment, the TX UE and/or RX UE may decide whether or not to apply one or more scheme(s) based on the distance between the two UEs, for example by making use of geographical positioning information. In one embodiment, the scheme(s) may be performed by the RX UE and/or TX UE only if the distance is lower than a threshold, or only if the distance is higher than a threshold.
There are several advantages and technical effects of the herein described solution. The solution provides means for a UE to handle conflicting situations (e.g. due to half-duplexing) when communicating using multiple carriers. Without use of at least one of the herein described schemes, there may be ambiguity as pairs of transmitter and receiver UEs may not have a common way to overcome the issue in case at least one of the involved UEs is not capable of transmitting/receiving multiple channels simultaneously in different carriers.
The herein described solution may have specification impact on 3GPP specification, and may be part of the SL CA work item in Rel-18.
Scheme(s) 1030 of the control module 1006 implements performance of the herein described schemes. Scheme(s) indication 1040 may facilitate transmitting, to at least one user equipment (e.g. UE 110), an indication that the apparatus 1000 is using the at least one scheme to perform the communication with the at least one user equipment, when there is the conflict between the at least one symbol of a first carrier and the at least one symbol of a second carrier within a time interval. Scheme(s) indication 1040 may facilitate receiving, from at least one user equipment (e.g. UE 110) or the network (e.g. RAN node 170 or network element(s) 190), an indication that the at least one user equipment is using at least one scheme to perform communication with the apparatus 1000, when there is the conflict between at least one symbol of a first carrier and at least one symbol of a second carrier within a time interval.
The apparatus 1000 includes a display and/or I/O interface 1008, which includes user interface (UI) circuitry and elements, that may be used to display aspects or a status of the methods described herein (e.g., as one of the methods is being performed or at a subsequent time), or to receive input from a user such as with using a keypad, camera, touchscreen, touch area, microphone, biometric recognition, one or more sensors, etc. The apparatus 1000 includes one or more communication e.g. network (N/W) interfaces (I/F(s)) 1010. The communication I/F(s) 1010 may be wired and/or wireless and communicate over the Internet/other network(s) via any communication technique including via one or more links 1024. The link(s) 1024 may be the link(s) 131 and/or 176 from
The transceiver 1016 comprises one or more transmitters 1018 and one or more receivers 1020. The transceiver 1016 and/or communication I/F(s) 1010 may comprise standard well-known components such as an amplifier, filter, frequency-converter, (de) modulator, and encoder/decoder circuitries and one or more antennas, such as antennas 1014 used for communication over wireless link 1026.
The control module 1006 of the apparatus 1000 comprises one of or both parts 1006-1 and/or 1006-2, which may be implemented in a number of ways. The control module 1006 may be implemented in hardware as control module 1006-1, such as being implemented as part of the one or more processors 1002. The control module 1006-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the control module 1006 may be implemented as control module 1006-2, which is implemented as computer program code (having corresponding instructions) 1005 and is executed by the one or more processors 1002. For instance, the one or more memories 1004 store instructions that, when executed by the one or more processors 1002, cause the apparatus 1000 to perform one or more of the operations as described herein. Furthermore, the one or more processors 1002, one or more memories 1004, and example algorithms (e.g., as flowcharts and/or signaling diagrams), encoded as instructions, programs, or code, are means for causing performance of the operations described herein.
The apparatus 1000 to implement the functionality of control 1006 may be UE 110, RAN node 170 (e.g. gNB), or network element(s) 190. Thus, processor 1002 may correspond to processor(s) 120, processor(s) 152 and/or processor(s) 175, memory 1004 may correspond to one or more memories 125, one or more memories 155 and/or one or more memories 171, computer program code 1005 may correspond to computer program code 123, computer program code 153, and/or computer program code 173, control module 1006 may correspond to module 140-1, module 140-2, module 150-1, and/or module 150-2, and communication I/F(s) 1010 and/or transceiver 1016 may correspond to transceiver 130, antenna(s) 128, transceiver 160, antenna(s) 158, N/W I/F(s) 161, and/or N/W I/F(s) 180. Alternatively, apparatus 1000 and its elements may not correspond to either of UE 110, RAN node 170, or network element(s) 190 and their respective elements, as apparatus 1000 may be part of a self-organizing/optimizing network (SON) node or other node, such as a node in a cloud. Apparatus 1000 may also correspond to UE2110-2.
The apparatus 1000 may also be distributed throughout the network (e.g. 100) including within and between apparatus 1000 and any network element (such as a network control element (NCE) 190 and/or the RAN node 170 and/or the UE 110).
Interface 1012 enables data communication and signaling between the various items of apparatus 1000, as shown in
The following examples are provided and described herein.
References to a ‘computer’, ‘processor’, etc. should be understood to encompass not only computers having different architectures such as single/multi-processor architectures and sequential or parallel architectures but also specialized circuits such as field-programmable gate arrays (FPGAs), application specific circuits (ASICs), signal processing devices and other processing circuitry. References to computer program, instructions, code etc. should be understood to encompass software for a programmable processor or firmware such as, for example, the programmable content of a hardware device whether instructions for a processor, or configuration settings for a fixed-function device, gate array or programmable logic device etc.
The memories as described herein may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, non-transitory memory, transitory memory, fixed memory and removable memory. The memories may comprise a database for storing data.
As used herein, the term ‘circuitry’ may refer to the following: (a) hardware circuit implementations, such as implementations in analog and/or digital circuitry, and (b) combinations of circuits and software (and/or firmware), such as (as applicable): (i) a combination of processor(s) or (ii) portions of processor(s)/software including digital signal processor(s), software, and memories that work together to cause an apparatus to perform various functions, and (c) circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present. As a further example, as used herein, the term ‘circuitry’ would also cover an implementation of merely a processor (or multiple processors) or a portion of a processor and its (or their) accompanying software and/or firmware. The term ‘circuitry’ would also cover, for example and if applicable to the particular element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or another network device.
It should be understood that the foregoing description is only illustrative. Various alternatives and modifications may be devised by those skilled in the art. For example, features recited in the various dependent claims could be combined with each other in any suitable combination(s). In addition, features from different example embodiments described above could be selectively combined into a new example embodiment. Accordingly, this description is intended to embrace all such alternatives, modifications and variances which fall within the scope of the appended claims.
The following acronyms and abbreviations that may be found in the specification and/or the drawing figures are given as follows (the abbreviations and acronyms may be appended with each other or with other characters using e.g. a dash, hyphen, slash, or number, and may be case insensitive):
This application claims priority to U.S. Provisional Application No. 63/461,442, filed Apr. 24, 2023, which is hereby incorporated by reference in its entirety.
Number | Date | Country | |
---|---|---|---|
63461442 | Apr 2023 | US |