WO2022084372A1 - Sidelink operation based on geographical areas - Google Patents

Abstract

Embodiments provide a first transceiver of a wireless communication system, wherein the first transceiver is configured to perform, in a geographical area, a communication over a sidelink in a frequency band that is not restricted for sidelink-communication only, wherein the frequency band is either one out of: - one or more available frequency bands that are available for sidelink-communication in said geographical area, - different from one or more prohibited frequency bands that are prohibited for sidelink-communication in said geographical area.

Description

Sidelink Operation based on Geographical Areas

Description

Embodiments of the present application relate to the field of wireless communication, and more specifically, to sidelink operation based on geographical areas.

Fig. 1 is a schematic representation of an example of a terrestrial wireless network 100 including, as is shown in Fig. 1(a), a core network 102 and one or more radio access networks RAN1 , RAN2, ... RANN. Fig. 1 (b) is a schematic representation of an example of a radio access network RANn that may include one or more base stations gNB1 to gNB5, each serving a specific area surrounding the base station schematically represented by respective cells 1061 to 1065. The base stations are provided to serve users within a cell. The term base station, BS, refers to a gNB in 5G networks, an eNB in UMTS/LTE/LTE-A/ LTE-A Pro, or just a BS in other mobile communication standards. A user may be a stationary device or a mobile device. The wireless communication system may also be accessed by mobile or stationary loT devices which connect to a base station or to a user. The mobile devices or the loT devices may include physical devices, ground based vehicles, such as robots or cars, aerial vehicles, such as manned or unmanned aerial vehicles (UAVs), the latter also referred to as drones, buildings and other items or devices having embedded therein electronics, software, sensors, actuators, or the like as well as network connectivity that enables these devices to collect and exchange data across an existing network infrastructure. Fig. 1(b) shows an exemplary view of five cells, however, the RANn may include more or less such cells, and RANn may also include only one base station. Fig. 1(b) shows two users UE1 and UE2, also referred to as user equipment, UE, that are in cell 1062 and that are served by base station gNB2. Another user UE3 is shown in cell 1064 which is served by base station gNB4. The arrows 1081 , 1082 and 1083 schematically represent uplink/downlink connections for transmitting data from a user UE1 , UE2 and UE3 to the base stations gNB2, gNB4 or for transmitting data from the base stations gNB2, gNB4 to the users UE1 , UE2, UE3. Further, Fig. 1 (b) shows two loT devices 1101 and 1102 in cell 1064, which may be stationary or mobile devices. The loT device 1101 accesses the wireless communication system via the base station gNB4 to receive and transmit data as schematically represented by arrow 1121. The loT device 1102 accesses the wireless communication system via the user UE3 as is schematically represented by arrow 1122. The respective base station gNB1 to gNB5 may be connected to the core network 102, e.g., via the S1 interface, via respective backhaul links 1141 to 1145, which are schematically represented in Fig. 1(b) by the arrows pointing to “core”. The core network 102 may be connected to one or more external networks. Further, some or all of the respective base station gNB1 to gNB5 may connected, e.g., via the S1 or X2 interface or the XN interface in NR, with each other via respective backhaul links 1161 to 1165, which are schematically represented in Fig. 1 (b) by the arrows pointing to “gNBs”.

For data transmission a physical resource grid may be used. The physical resource grid may comprise a set of resource elements to which various physical channels and physical signals are mapped. For example, the physical channels may include the physical downlink, uplink and sidelink shared channels (PDSCH, PLISCH, PSSCH) carrying user specific data, also referred to as downlink, uplink and sidelink payload data, the physical broadcast channel (PBCH) carrying for example a master information block (MIB), the physical downlink shared channel (PDSCH) carrying for example a system information block (SIB), the physical downlink, uplink and sidelink control channels (PDCCH, PLICCH, PSSCH) carrying for example the downlink control information (DCI), the uplink control information (UCI) and the sidelink control information (SCI). For the uplink, the physical channels, or more precisely the transport channels according to 3GPP, may further include the physical random access channel (PRACH or RACH) used by UEs for accessing the network once a UE is synchronized and has obtained the MIB and SIB. The physical signals may comprise reference signals or symbols (RS), synchronization signals and the like. The resource grid may comprise a frame or radio frame having a certain duration in the time domain and having a given bandwidth in the frequency domain. The frame may have a certain number of subframes of a predefined length, e.g., 1ms. Each subframe may include one or more slots of 12 or 14 OFDM symbols depending on the cyclic prefix (CP) length. All OFDM symbols may be used for DL or UL or only a subset, e.g., when utilizing shortened transmission time intervals (sTTI) or a mini- slot/non-slot-based frame structure comprising just a few OFDM symbols.

The wireless communication system may be any single-tone or multicarrier system using frequency-division multiplexing, like the orthogonal frequency-division multiplexing (OFDM) system, the orthogonal frequency-division multiple access (OFDM A) system, or any other IFFT-based signal with or without CP, e.g., DFT-s-OFDM. Other waveforms, like non- orthogonal waveforms for multiple access, e.g., filter-bank multicarrier (FBMC), generalized frequency division multiplexing (GFDM) or universal filtered multi carrier (LIFMC), may be used. The wireless communication system may operate, e.g., in accordance with the LTE- Advanced pro standard or the NR (5G), New Radio, standard. The wireless network or communication system depicted in Fig. 1 may by a heterogeneous network having distinct overlaid networks, e.g., a network of macro cells with each macro cell including a macro base station, like base station gNB1 to gNB5, and a network of small cell base stations (not shown in Fig. 1), like femto or pico base stations.

In addition to the above described terrestrial wireless network also non-terrestrial wireless communication networks exist including spaceborne transceivers, like satellites, and/or airborne transceivers, like unmanned aircraft systems. The non-terrestrial wireless communication network or system may operate in a similar way as the terrestrial system described above with reference to Fig. 1 , for example in accordance with the LTE-Advanced Pro standard or the NR (5G), new radio, standard.

In mobile communication networks, for example in a network like that described above with reference to Fig. 1 , like an LTE or 5G/NR network, there may be UEs that communicate directly with each other over one or more sidelink (SL) channels, e.g., using the PC5 interface. UEs that communicate directly with each other over the sidelink may include vehicles communicating directly with other vehicles (V2V communication), vehicles communicating with other entities of the wireless communication network (V2X communication), for example roadside entities, like traffic lights, traffic signs, or pedestrians. Other UEs may not be vehicular related UEs and may comprise any of the above-mentioned devices. Such devices may also communicate directly with each other (D2D communication) using the SL channels.

When considering two UEs directly communicating with each other over the sidelink, both UEs may be served by the same base station so that the base station may provide sidelink resource allocation configuration or assistance for the UEs. For example, both UEs may be within the coverage area of a base station, like one of the base stations depicted in Fig. 1. This is referred to as an “in-coverage” scenario. Another scenario is referred to as an “out-of-coverage” scenario. It is noted that “out-of-coverage” does not mean that the two UEs are not within one of the cells depicted in Fig. 1 , rather, it means that these UEs - may not be connected to a base station, for example, they are not in an RRC connected state, so that the UEs do not receive from the base station any sidelink resource allocation configuration or assistance, and/or - may be connected to the base station, but, for one or more reasons, the base station may not provide sidelink resource allocation configuration or assistance for the UEs, and/or - may be connected to the base station that may not support NR V2X services, e.g., GSM, UMTS, LTE base stations. When considering two UEs directly communicating with each other over the sidelink, e.g., using the PC5 interface, one of the UEs may also be connected with a BS, and may relay information from the BS to the other UE via the sidelink interface. The relaying may be performed in the same frequency band (in-band-relay) or another frequency band (out-of-band relay) may be used. In the first case, communication on the Uu and on the sidelink may be decoupled using different time slots as in time division duplex, TDD, systems.

Fig. 2 is a schematic representation of an in-coverage scenario in which two UEs directly communicating with each other are both connected to a base station. The base station gNB has a coverage area that is schematically represented by the circle 200 which, basically, corresponds to the cell schematically represented in Fig. 1. The UEs directly communicating with each other include a first vehicle 202 and a second vehicle 204 both in the coverage area 200 of the base station gNB. Both vehicles 202, 204 are connected to the base station gNB and, in addition, they are connected directly with each other over the PC5 interface. The scheduling and/or interference management of the V2V traffic is assisted by the gNB via control signaling over the Uu interface, which is the radio interface between the base station and the UEs. In other words, the gNB provides SL resource allocation configuration or assistance for the UEs, and the gNB assigns the resources to be used for the V2V communication over the sidelink. This configuration is also referred to as a mode 1 configuration in NR V2X or as a mode 3 configuration in LTE V2X.

Fig. 3 is a schematic representation of an out-of-coverage scenario in which the UEs directly communicating with each other are either not connected to a base station, although they may be physically within a cell of a wireless communication network, or some or all of the UEs directly communicating with each other are to a base station but the base station does not provide for the SL resource allocation configuration or assistance. Three vehicles 206, 208 and 210 are shown directly communicating with each other over a sidelink, e.g., using the PC5 interface. The scheduling and/or interference management of the V2V traffic is based on algorithms implemented between the vehicles. This configuration is also referred to as a mode 2 configuration in NR V2X or as a mode 4 configuration in LTE V2X. As mentioned above, the scenario in Fig. 3 which is the out-of-coverage scenario does not necessarily mean that the respective mode 2 UEs (in NR) or mode 4 UEs (in LTE) are outside of the coverage 200 of a base station, rather, it means that the respective mode 2 UEs (in NR) or mode 4 UEs (in LTE) are not served by a base station, are not connected to the base station of the coverage area, or are connected to the base station but receive no SL resource allocation configuration or assistance from the base station. Thus, there may be situations in which, within the coverage area 200 shown in Fig. 2, in addition to the NR mode 1 or LTE mode 3 UEs 202, 204 also NR mode 2 or LTE mode 4 UEs 206, 208, 210 are present.

Naturally, it is also possible that the first vehicle 202 is covered by the gNB, i.e., connected with Uu to the gNB, wherein the second vehicle 204 is not covered by the gNB and only connected via the PC5 interface to the first vehicle 202, or that the second vehicle is connected via the PC5 interface to the first vehicle 202 but via Uu to another gNB, as will become clear from the discussion of Figs. 4 and 5.

Fig. 4 is a schematic representation of a scenario in which two UEs directly communicating with each, wherein only one of the two UEs is connected to a base station. The base station gNB has a coverage area that is schematically represented by the circle 200 which, basically, corresponds to the cell schematically represented in Fig. 1. The UEs directly communicating with each other include a first vehicle 202 and a second vehicle 204, wherein only the first vehicle 202 is in the coverage area 200 of the base station gNB. Both vehicles 202, 204 are connected directly with each other over the PC5 interface.

Fig. 5 is a schematic representation of a scenario in which two UEs directly communicating with each, wherein the two UEs are connected to different base stations. The first base station gNB1 has a coverage area that is schematically represented by the first circle 2001 , wherein the second station gNB2 has a coverage area that is schematically represented by the second circle 2002. The UEs directly communicating with each other include a first vehicle 202 and a second vehicle 204, wherein the first vehicle 202 is in the coverage area 2001 of the first base station gNB1 and connected to the first base station gNB1 via the Uu interface, wherein the second vehicle 204 is in the coverage area 2002 of the second base station gNB2 and connected to the second base station gNB2 via the Uu interface.

With introduction of the sidelink in Rel-14 for LTE and in Rel-16 for NR, resource allocation in out-of-coverage is limited to the ITS-band, band 47 (5.9 GHz). For NR V2X, additionally a second ITS-band, band n38 (2.6 GHz) is specified for sidelink.

Note that, ITS is a term used by ETSI for 5.9 GHz and 60 GHz ITS bands. The n38 band may not consistently referred to as ITS band, see [17],

For Rel-17 within the WID for SL Enhancements [1] one RAN2 topic is to ensure that sidelink operation can be confined to a predetermined geographic area(s) for a given frequency range within non-ITS bands, for out-of-coverage areas. In [12], clause 5 evaluations have been performed for adjacent channel co-existence scenarios. It has been found that for coexistence in licensed spectrum for FR1 , that without power control NR V2X cannot exist with NR Uu in licensed spectrum, as in this case the throughput degradation is unacceptable for the victim NR BS. Therefore, the PC5-based NR V2X service is regarded as within acceptable operating limits for adjacent channel coexistence scenarios in licensed spectrum when the entire band is allocated for SL in a given region or when SL operation in a TDD band is in sync with the non-V2X operation in the same band.

Therefore, there is the need for a mechanism that confines sidelink operation to predetermined geographic areas for given frequency ranges within non-ITS/licensed bands. This applies specifically for areas where there is no network coverage.

It is noted that the information in the above section is only for enhancing the understanding of the background of the invention and therefore it may contain information that does not form prior art and is already known to a person of ordinary skill in the art.

Embodiments of the present invention are described herein making reference to the appended drawings.

Fig. 1 is a schematic representation of an example of a wireless communication system;

Fig. 2 is a schematic representation of an in-coverage scenario in which UEs directly communicating with each other are connected to a base station;

Fig. 3 is a schematic representation of an out-of-coverage scenario in which UEs directly communicating with each other receive no SL resource allocation configuration or assistance from a base station;

Fig. 4 is a schematic representation of a partial out-of-coverage scenario in which some of the UEs directly communicating with each other receive no SL resource allocation configuration or assistance from a base station;

Fig. 5 is a schematic representation of an in-coverage scenario in which UEs directly communicating with each other are connected to different base stations;

Fig. 6 is a schematic representation of zones in Rel-14 LTE V2X; Fig. 7 is a schematic representation of a wireless communication system comprising a transceiver, like a base station or a relay, and a plurality of communication devices, like UEs, according to an embodiment;

Fig. 8a-b are schematic representations of an algorithm for determining if a point is located inside or outside of a polygon, wherein in Fig. 8a it is assumed that the point is located inside the polygon, wherein in Fig. 8b it is assumed that the point is located outside the polygon;

Fig. 9 shows an illustrative view of a no transmission area between an out-of-coverage area and in-coverage area by non-ITS band; and

Fig. 10 illustrates an example of a computer system on which units or modules as well as the steps of the methods described in accordance with the inventive approach may execute.

Equal or equivalent elements or elements with equal or equivalent functionality are denoted in the following description by equal or equivalent reference numerals.

In the following description, a plurality of details are set forth to provide a more thorough explanation of embodiments of the present invention. However, it will be apparent to one skilled in the art that embodiments of the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form rather than in detail in order to avoid obscuring embodiments of the present invention. In addition, features of the different embodiments described hereinafter may be combined with each other, unless specifically noted otherwise.

1. Background

Subsequently, an overview over the specification of geographical areas in sidelink communications and in mobile communications in general is provided as well as the frequency bands used for sidelink communication.

1.1. Zones - general Zones were introduced in LTE V2X in Rel. 14 to facilitate resource allocation based on geographical position for sidelink communications for UEs which are out-of-coverage. With rel. 16 NR sidelink zones were introduced to determine the distance of a transmitting UE for the purpose to decide if a HARQ response shall be sent or not.

Both rel. 14 and rel. 16 zone concepts are based on a rectangular grid of zone clusters. Since the zone IDs are determined involving a modulo operation, they are unique only within one cluster and repeated in all other clusters. Rel. 14 and 16 differ in the zone sizes and the cluster dimension (up to 4 x 4 for rel. 14 and fixed to 64 x 64 for rel. 16, but the principle is the same.

1.2. Zones in Rel-14/15

The motivation of the zone concept is geo-based transmission resource selection for spectrum sharing, i.e. , reuse of spectrum resources at different geographical locations. This shall reduce the impact from near-far problem, in-band emission and co-channel interference. Each zone is associated with a different resource pool for transmission, i.e., a subset of spectrum resources.

In rel- 14 the zone length and width can be configured between 5 and 500 m. The 2-dimensional cluster can be configured consisting of 1 to 4 zones in longitudinal and lateral direction. From these 4 parameters the zone ID is computed by x1= Floor (x I L) Mod Nx; y1= Floor (y / W) Mod Ny; Zone_id = y1 * Nx + x1. In other words the zone ID is unique only within a cluster and is repeated in other clusters. The maximum cluster size is 4x4, i.e., only up to 16 IDs are possible as illustrated in Fig. 6. In detail, Fig. 6 is a schematic representation of zones in Rel- 14 LTE V2X.

The idea is that the same resource pools are reused in the distance given by the cluster size. For example, if the length of a zone is 20 m, its width 10 m and the longitudinal and lateral number of zones of a cluster is 4 for both, the minimum distance where a resource pool is reused is 4 x 10 m = 40 m in lateral direction.

1.3. Zones in Rel-16 (NR)

In rel. 16, the motivation for the zone concept changed from resource selection to distance estimation for groupcast HARQ. That means, if a receiver cannot decode a message a NACK is only sent if the distance to the transmitter is below a configured limit. The zones are simplified in rel. 16 by specifying quadratic zones, i.e., length and width are equal and the cluster sizes is fixed to 64 x 64 zones. Consequently, only one parameter for the zone size is defined.

Referring to rel. 16 the maximum uniqueness range is 3.2 km in rel. 16 (64 x 50 m (max. zone size) = 3.2 km. That means, if a geo area would be determined by zone IDs only, the UE cannot determine its absolute position. That means, the absolute geo position according to LPP protocol or as used in geo reporting must somehow be involved.

The zone ID is only unique in a zone cluster since it is derived by modulo the cluster size. The maximum cluster size or distance between equal IDs is 64 x 50 m = 3.2 km. Due to this ambiguity it is not suitable for localization in greater areas.

1.4. Operating bands for V2X / Sidelink Communications

1.4.1. ITS-Band

On December 17, 2003 the European Commission adopted a Report and Order establishing licensing and service rules for the Dedicated Short Range Communications (DSRC) Service in the Intelligent Transportation Systems (ITS) Radio Service in the 5.850-5.925 GHz band (5.9 GHz band) which is 3GPP band 47 [10], There is also a co-primary Federal Government radio location allocation (for use by high-powered military services) in the 5.850-5.925 GHz band, a co-primary fixed satellite (earth-to-space) allocation, and the amateur service has a secondary allocation in the band. Industrial, Scientific and Medical (ISM) equipment may also operate in the 5.850-5.875 MHz portion of the band.

The 5.9 GHz band is currently the only band used for NR PC5 and 802.11 p. As additional ITS band 3GPP specifies the 2.570-2.620 GHz band (2.6 GHz band) which is 3GPP band 38 [10], Note: Band 47 and 38 can be used for ITS services. See [18],

Consequently, any other NR band in chapter 5.2 of 38.101-1 are non-ITS and unlicensed bands are non-ITS, too.

1.4.2 LTE V2X For LTE V2X, band 47 (5855 - 5925 MHz) is specified for PC5 I sidelink in half-duplex mode [11], The channel bandwidths in band 47 can be 10 and 20 MHz ([11], Table 5.6.1-1 and 5.6G.1-1) and intra-band multicarrier operation is supported.

Additionally, inter-band concurrent V2X operating bands are defined, where PC5 is performed on band 47 in half-duplex mode and concurrent LTE uplink/downlink for Uu on bands 3, 7, 8 in FDD or band 39 and 41 TDD mode, respectively ([11], Table 5.5G-2).

1.4.3. NR Sidelink

Geographical areas in NR sidelink are described in [10], clause 5.2 and clause 5.2E.

For NR V2X, the band n47 (5855 - 5925 MHz, TDD) is defined similar as for LTE V2X (Table 5.2-1) for PC5 interface. This band is the ITS (3GPP unlicensed) band used for V2X service. There is no expected network deployment in this bandi. Channel bandwidth of 10, 20, 30 and 40 MHz are supported in band n47 for different Sub-Carrier Spacing (SCS) 15, 30 and 60 kHz (38.101-1 , clause 5.3E.2).

In addition, NR operating band n38 (UL/DL 2570 MHz - 2620 MHz, TDD mode) is specified for V2X PC5 operation. According to [10] clause 5.2, Table 5.2-1 : when band (n38) is used for V2X SL service, the band is exclusively used for NR V2X in particular regions. In NR licensed bands (n38), the NR V2X UE shall be operated synchronous with adjacent NR UE in the licensed band.

For inter-band concurrent operation of NR V2X with NR UL/DL, a combination of Uu on band n71 (UL: 663 MHz - 698 MHz, DL: 617 MHz - 652 MHz, FDD) with n47 (PC5) is specified.

In [12], clause 5 evaluations have been performed for adjacent channel co-existence scenarios. As a conclusion ([12], clause 5.4), the PC5-based NR V2X service will be within acceptable operating limits for adjacent channel coexistence scenarios in ITS spectrum of n47 and in licensed spectrum either when the entire band is allocated for SL in a given region or when SL operation in a TDD band in sync with the non-V2X operation in the same band.

To band 47: There is no expected network deployment [10]; therefore it is assumed that TDD cannot (yet) be supported and no geographical area needs to be defined.

2. Embodiments Data transmission for sidelink V2X safety-critical services in out-of-coverage scenarios typically use ITS-bands. Therefore, in accordance with embodiments, non-ITS-bands in out- of-coverage could be used for any other service or type of data transmission.

In accordance with embodiments, non-ITS frequency bands may be allowed I prohibited only in defined geographical areas, due to regional limitations or interference. Therefore, in embodiments, a mapping of non-ITS bands to geographical areas for sidelink out-of-coverage is provided.

Embodiments of the present invention may be implemented in a wireless communication system as depicted in Figs. 1-5 including base stations and users, like mobile terminals or loT devices. Fig. 7 is a schematic representation of a wireless communication system including a central transceiver, like a base station, and one or more transceivers 302₁ to 302_n, like user devices, UEs. The central transceiver 300 and the transceivers 302 may communicate via one or more wireless communication links or channels 304a, 304b, 304c, like a radio link. The central transceiver 300 may include one or more antennas ANTT or an antenna array having a plurality of antenna elements, a signal processor 300a and a transceiver unit 300b, coupled with each other. The transceivers 302 include one or more antennas ANTR or an antenna array having a plurality of antennas, a signal processor 302ai, 302a_n, and a transceiver unit 302b₁, 302b_n coupled with each other. The base station 300 and the UEs 302 may communicate via respective first wireless communication links 304a and 304b, like a radio link using the Uu interface, while the UEs 302 may communicate with each other via a second wireless communication link 304c, like a radio link using the PC5 interface. When the UEs are not served by the base station, are not be connected to a base station, for example, they are not in an RRC connected state, or, more generally, when no SL resource allocation configuration or assistance is provided by a base station, the UEs may communicate with each other over the sidelink. The system, the one or more UEs and the base stations may operate in accordance with the inventive teachings described herein.

Embodiments provide a first transceiver [e.g., UE] of a wireless communication system, wherein the first transceiver is configured to perform, in a geographical area [e.g., when located in the geographical area], a communication [e.g., a transmission and/or reception] over a sidelink in a frequency band that is not restricted [e.g., reserved] for sidelink-communication only [e.g., in a non-ITS-band], wherein the frequency band is either one out of - one or more available frequency bands [e.g., available non-ITS-bands] that are available [e.g., allowed] for sidelink-communication in said geographical area, different from one or more prohibited frequency bands [e.g., prohibited non-ITS-bands] - that are prohibited for sidelink-communication in said geographical area. In embodiments, the first transceiver is configured to operate in a [e.g., new radio, NR] sidelink out of coverage scenario [e.g., NR sidelink mode 2] [e.g., in which resources for the communication over the sidelink are (pre-)configured by the wireless communication system or allocated or scheduled autonomously by the first transceiver], wherein the first transceiver is configured to perform, in the sidelink out of coverage scenario, the communication over the sidelink in the frequency band that is not restricted for sidelink-communication only. Further embodiments provide a first transceiver [e.g., UE] of a wireless communication system, wherein the first transceiver is configured to operate in a [e.g., new radio, NR] sidelink out of coverage scenario [e.g., NR sidelink mode 2] [e.g., in which resources for the communication over the sidelink are (pre-)configured by the wireless communication system or allocated or scheduled autonomously by the first transceiver], wherein the first transceiver is configured to perform, in the sidelink out of coverage scenario, a communication [e.g., a transmission and/or reception] over the sidelink in a frequency band that is not restricted [e.g., reserved] for sidelink-communication only [e.g., in a non-ITS-band], wherein the frequency band is either one out of - one or more available frequency bands [e.g., available non-ITS-bands] that are available [e.g., allowed] for sidelink-communication, - different from one or more prohibited frequency bands [e.g., prohibited non-ITS-bands] that are prohibited for sidelink-communication. In embodiments, the first transceiver is configured to detect the sidelink out of coverage scenario based on Uu radio signals measurements or detection attempts. In embodiments, the first transceiver is configured to only perform the communication over the sidelink in said frequency band if the Uu radio signal measurements indicate that the first transceiver maintains a predefined distance with respect to other transceivers of the wireless communication system that are communicating via the Uu interface. Further embodiment provide a second transceiver [e.g., other UE, gNB, relay, satellite, IAB node, intelligent node, network node, RSU] of a wireless communication system, wherein the second transceiver is configured to transmit a configuration message to a first transceiver of the wireless communication system, wherein the configuration message comprises a configuration message comprising a configuration information describing at least one out of - one or more available frequency bands [e.g., available non-ITS-bands] that are available for sidelink-communication [e.g., in a geographical area], - one or more prohibited frequency bands [e.g., prohibited non-ITS-bands] that are prohibited for sidelink-communication [e.g., in said geographical area], wherein the one or more frequency bands and/or the one or more prohibited frequency bands are not restricted for sidelink-communication only [e.g., are non-ITS-bands]. Subsequently, further embodiments of the first transceivers and the second transceiver are described. In embodiments, the first transceiver is configured to detect the sidelink out of coverage scenario based on radio signal measurements or detection attempts. In embodiments, the frequency band that is not restricted for sidelink-communication only is a non-ITS-band [e.g., a frequency band different from an ITS-band]. In embodiments, the first transceiver is configured to perform said communication over the sidelink in said frequency band for a service different than services relating to transport and traffic management. In embodiments, the first transceiver is configured to select, for the communication over the sidelink in said geographical area, the frequency band in dependence on - the one or more available frequency bands [e.g., allowed non-ITS-bands] that are available for sidelink-communication in said geographical area, such that the frequency band is one out of the one or more available frequency bands, or - the one or more prohibited frequency bands [e.g., prohibited non-ITS-bands] that are prohibited for sidelink-communication in said geographical area, such that the frequency band is different from the one or more prohibited frequency bands. In embodiments, the first transceiver is configured to select the frequency band further in dependence on at least one out of - a quality criterion [e.g., QoS], - a priority criterion [e.g., service type priority], - a type of service criterion, - an upper layer signaling, - a required data rate, - a network slice, - multi RAT aspects, - co-existence problem. In embodiments, the first transceiver is configured to determine whether the first transceiver is located within the geographical area, wherein the first transceiver is configured to perform the communication over the sidelink using said frequency band if the first transceiver is located within the geographical area.

In embodiments, the one or more available frequency bands and/or the one or more prohibited frequency bands for said geographical area are preconfigured.

In embodiments, the first transceiver is configured to receive from a second transceiver of the wireless communication system a configuration message comprising a configuration information defining - the geographical area, and/or - the one or more available frequency bands and/or the one or more prohibited frequency bands for said geographical area.

In embodiments, the first transceiver is configured to receive the configuration message from the second transceiver over the sidelink [e.g., via relays or assistance messages] in a sidelink out of coverage scenario.

In embodiments, the first transceiver is configured to receive the configuration message from the second transceiver via a downlink [e.g., system information] in a [e.g., previous] in coverage scenario.

In embodiments, the configuration message further defines at least one available resource pool [e.g., mode specific, dedicated, shared, normal or exceptional resource pool] of the one or more available frequency bands.

In embodiments, the configuration information describes one or more zone IDs defining one or more geographical zones that - overlap with said geographical area, - define a circumference of said geographical area, or - define vertexes of said geographical area.

In embodiments, the configuration information further describes a reference location uniquely defining a location of the geographical area in combination with the one or more zone IDs. In embodiments, the reference location is one out of - a geographical reference coordinate point, - a cell ID, - an ID of a mobile network defined area [e.g., validity area or tracking / paging area], - gNB position, - ZIP code.

In embodiments, the configuration information describes at least one geographical coordinate point defining the geographical area.

In embodiments, the at least one geographical coordinate points include a plurality of absolute geographical coordinate points spanning a polygon defining the geographical area.

In embodiments, the geographical coordinate points include at least one absolute geographical coordinate point and a plurality of relative geographical coordinate points associated with the at least one absolute geographical coordinate point, wherein the plurality of relative geographical coordinate points [e.g., and optionally the at least one absolute geographical coordinate point] span a polygon defining the geographical area.

In embodiments, the configuration information further describes a shape that together with the at least one [e.g., absolute] geographical coordinate point defines the geographical area.

In embodiments, the configuration information maps - the geographical area, and - the one or more available frequency bands and/or the one or more prohibited frequency bands.

In embodiments, the configuration information defines - at least two geographical areas, and - one or more available frequency bands and/or the one or more prohibited frequency bands for each of the two geographical areas.

In embodiments, the first transceiver is configured to determine in which of the at least two geographical areas the first transceiver is located, wherein the first transceiver is configured to select the frequency band in dependence on - the one or more available frequency bands [e.g., allowed non-ITS-bands] that are available for sidelink-communication in the geographical area of the at least two geographical areas in which the first transceiver is located, - the one or more prohibited frequency bands [e.g., prohibited non-ITS-bands] that are prohibited for sidelink-communication in the geographical area of the at least two geographical areas in which the first transceiver is located. In embodiments, the geographical area is a political, operator specified or geographical exposed area. In embodiments, the frequency band that is not restricted for sidelink-communication is one out of - an uplink band, - a downlink band, - a FDD band, - a TDD band, - a supplementary uplink band, - a supplementary downlink band. In embodiments, the first transceiver is configured to perform the communication over the sidelink using at least one bandwidth part of the frequency band that is not restricted for sidelink-communication only [e.g., non-ITS-band] and at least one bandwidth part of the frequency band that is restricted for sidelink-communication only [e.g., ITS-band] [e.g., carrier aggregation]. In embodiments, the first transceiver is configured to access the frequency band based on one out of - a short sensing before a sidelink transmission, - a discontinuous sensing before a sidelink transmission, - a random access. In embodiments, the first transceiver is a mobile transceiver. In embodiments, the first transceiver is an user equipment, UE. Further embodiments provide a method for operating a first transceiver of a wireless communication system. The method comprises a step of performing, in a geographical area [e.g., when located in the geographical area], a communication [e.g., a transmission and/or reception] over a sidelink in a frequency band that is not restricted [e.g., reserved] for sidelink- communication only [e.g., in a non-ITS-band], wherein the frequency band is either one out of - one or more available frequency bands [e.g., available non-ITS-bands] that are available [e.g., allowed] for sidelink-communication in said geographical area, - different from one or more prohibited frequency bands [e.g., prohibited non-ITS-bands] that are prohibited for sidelink-communication in said geographical area. Further embodiments provide a method for operating a first transceiver of a wireless communication system. The method comprises a step of operating the first transceiver in a [e.g., new radio, NR] sidelink out of coverage scenario [e.g., NR sidelink mode 2] [e.g., in which resources for the communication over the sidelink are (pre-)configured by the wireless communication system or allocated or scheduled autonomously by the first transceiver]. Further, the method comprises a step of performing, in the sidelink out of coverage scenario, a communication [e.g., a transmission and/or reception] over the sidelink in a frequency band that is not restricted [e.g., reserved] for sidelink-communication only [e.g., in a non-ITS-band], wherein the frequency band is either one out of - one or more available frequency bands [e.g., available non-ITS-bands] that are available [e.g., allowed] for sidelink-communication, - different from one or more prohibited frequency bands [e.g., prohibited non-ITS-bands] that are prohibited for sidelink-communication. Further embodiments provide a method for operating a second transceiver of a wireless communication system. The method comprises a step of transmitting a configuration message to a first transceiver of the wireless communication system, wherein the configuration message comprises a configuration message comprising a configuration information describing at least one out of - one or more available frequency bands [e.g., available non-ITS-bands] that are available for sidelink-communication [e.g., in a geographical area], - one or more prohibited frequency bands [e.g., prohibited non-ITS-bands] that are prohibited for sidelink-communication [e.g., in said geographical area], wherein the one or more frequency bands and/or the one or more prohibited frequency bands are not restricted for sidelink-communication only [e.g., are non-ITS-bands]. In accordance with embodiments, a UE in an out-of-coverage scenario is instructed to confine sidelink operation to given non-ITS band in a predetermined geographic area(s), where • the allowed or prohibited non-ITS-bands are associated to one or multiple geographical area(s), and/or

• this association can either be (pre-)defined in the UE and/or a UE may receive this information or updates on allowed I prohibited non-ITS bands, e.g., (1) in an incoverage scenario, on accessing, e.g., a new PLMN, new network function(s), cell, cluster etc., (2) in an out-of-coverage scenario from other entities (e.g., UEs, satellite, network function(s)), and/or (3) via the policy information from the network function, and/or

• the selection of the non-ITS-band may be based on defined criteria, e.g., the service type priority, QoS, and/or

• sidelink carrier aggregation can be used for non-ITS and ITS-bands.

In embodiments, for geographical areas at least one of the following options may apply:

• overlapping zones, e.g., adapting the R16 small sized zone parameters, e.g., by adding a size factor,

• using geo coordinate points to define geographical areas,

• PLMNs, countries, states, geographical areas, e.g., oceans, lakes, mountain (ranges),

• new area shapes, e.g., polygons.

In embodiments, confinement to a geographical area can be UE centric or gNB centric.

In embodiments, UE centric confinement can be used in out-of-coverage, partial coverage or in-coverage. It implies the definition and signaling of such area from the gNB to the UE. An area definition can be based on, for example:

• reuse of the zone concept,

• geo coordinates, such as absolute coordinates (e.g., all 48 bits used for all coordinates), or relative coordinates to a reference point (e.g., only one coordinate with 48 bits), other coordinated are relative coordinates (e.g., less bits needed) - see section 2.1.1.,

• other metrics, like cell ID, out-of-coverage detection, etc.

In embodiments, gNB centric confinement can be used in partial coverage or in-coverage or for mode 2 UEs in-coverage. It implies reporting the UE position to the gNB. The gNB compares this with the confinement area and signals permission or non-permission of non-ITS operation. The other option could be that the gNB is aware of, for example, the UEs location and provides it with the information about the accessible non-ITS or ITS frequency bands. This signaling can be triggered from, e.g., network function in the core network and directed via gNB. 2.1. Geographic area confinement 2.1.1. Geographic area confinement based on zone concept In embodiments, the zone concept can be reused to define geographical areas for confinement. The following options are available. According to a first option, lists of zone IDs can be used where the corresponding zones overlap with the confinement area. According to a second option, a list of the zone IDs can be used, where the corresponding zones overlap with the circumference of the confinement area. The responsible entity, e.g., the UE, determines the zones that are located inside the circumference. According to a third option a list of zone IDs can be used that overlap with vertexes defining a polygon. The responsible entity, e.g., the UE, can determine a point inside or outside of the polygon with an algorithm, for example, as described in section 2.1.2. In embodiments, responsible entity is the device that determines if the location of a UE is inside or outside of a confinement area. If the responsible entity is a UE, the lists of zone IDs have to be signaled to it. Zones in Rel-16 have a granularity given by their lateral size, e.g., 50 m x 50 m. Therefore, each geographical point within the confinement area, on its circumference or any of its vertices, if the area is represented by a polygon, is identified by the zone that includes such a point, i.e., overlaps with it. In other words, any point inside a zone is represented by the whole zone. Zones in NR sidelink are defined by their zone ID which maps to the position of the UE given by the geodesic distance in longitude x and latitude y between UE's current location and geographical coordinates (0, 0) according to WGS84 model [13]: Zone_id = (Floor (y / L) Mod 64) * 64 + Floor (x / L) Mod 64 where L is the length and width of a zone configured by IE SL-ZoneConfig [6]. The area where all IDs exist is a cluster of 64 x 64 zones. Consequently, according to the formula above, zone ID values are in the range of 0 … 4095. Thus, zone IDs are more coding efficient than geo coordinates, since only 12 bit are needed. On the other hand, zone IDs periodically repeat in all adjacent clusters, i.e., zone IDs are ambiguous due to the modulo operation in its calculation. Assuming the maximum zone size of L = 50 m means a square zone area of 3.2 km lateral length in which zone IDs are unique. In the following subsections possible solutions for using any type of zones are elaborated. 2.1.1.1. Resolution of ambiguous geographical locations using zone IDs As explained above, due to the ambiguous repetition of the zone IDs, e.g., after a certain distance of 3.2km square, the geographic location of a zone on the globe cannot be uniquely determined. To avoid that the confined area is identified at periodic positions, in embodiments, additional parameters can be combined with and added to the lists of zone IDs. That can be, for example, an absolute geo coordinate point associated with the confined area. This reference coordinate point is close to the confinement area, preferably at its center of gravity. In embodiments, the reference can be a geographic location coordinate as described in section 2.1.2. coded with, for example, 48 bits, that ensures an accuracy of <3 m. It is possible to lower the number of bits using the following methods. A first method is to reduce the location accuracy for the purpose of defining a confinement area. For example, comparing with the zone concept using 50 m sized zones the number of bits per coordinate axis can be reduced to 24 – log₂(50/3) = 20 bits, i.e., 40 bits for the whole coordinate. This corresponds to a truncation of the binary values for latitude and longitude of a number of least significant bits (LSBs). A second method is by keeping the accuracy the number of bits can be reduced sacrificing uniqueness, i.e., introducing ambiguity into the geographic coordinates. This corresponds to a truncation of the binary values for latitude and longitude of a number of most significant bits (MSBs). The ambiguity can be resolved if wide area position information is used. This can be the PLMN, the country, tracking area, etc. A third method is the combination of the first method and the second method above, i.e., truncation of the binary values for latitude and longitude on the LSB and MSB side.

In embodiments, in order to exclude an ambiguous area, the responsible entity can take a uniqueness range into account, which may be given by a maximum distance limit between the UEs location and the reference point. I.e., if a zone ID would indicate a location in a confinement area but the uniqueness range is exceeded it must be one of the ambiguous areas and thus outside the confinement area.

In embodiments, the maximum distance limit can be given implicitly by the maximum zone cluster size, e.g., 3.2 km, or explicitly by signaling.

In embodiments, additional extensions of the zone IDs by a reference point to make it unique can be at least one out of:

• the cell ID of the cell the UE currently camps on (in-coverage),

• the cell ID of the last cell the UE camped on prior to out-of-coverage detection,

• similar to the cell ID, also the ID of the validity area or tracking I paging area, or any other mobile network defined area or the gNB geographic position may be used for in and out-of-coverage,

• ZIP code of the current area.

2.1.1.2. Area extension - multiple zone IDs

Since zone IDs are unique only within the zone cluster as defined in R16 by 64 x 64 zones, the zone concept seems to be suitable only for smaller areas, i.e., up to 3.2 km x 3.2 km.

However it is possible to extend the confinement area definition with multiple lists of zone IDs and their associated reference points. Preferably, these lists define areas directly adjacent to each other or partly overlapping.

2.1.1.3. Overlapping or extended zone configurations

Using zones for area confinement has to fulfill different requirements than for distance estimation for group HARQ feedback of the Rel-16 zones. The Rel-16 zone size was limited to max. 50 m in latitude and longitude. The range of NR Rel-16 zone size is given as 5m, 10m, 20m, 30m, 40m, 50m; the length and the width of the NR R16 zones are identical, i.e., NR SL zones are quadratic. The Rel-16 small zone sizes were defined to achieve higher resolution for the distance. This limited Rel-16 zone size is usually not applicable to define geographical areas to allocate or restrict (ranges of) frequency bands. The same frequency band(s) are expected to be applicable in much larger areas than the max. 50 m in square to allow using the same frequency band over a longer period or within a larger area(s). This is required to avoid, e.g., signaling and performance impact due to continuous changes in frequency bands / resource pools, resources, sub channels etc. An additional layer / grid of zones, e.g., in addition to the existing R16 (HARQ feedback) zones, adds a second overlapping layer / grid of zones, where the size of the zones are typically expected to be different, i.e., larger to associated frequency bands to zones. As the zones may need to be uniquely identified (i.e., unambiguous zone IDs), solutions to insure unique identification of the zone as described in section 2.1.1.1. may apply for any of the mentioned variants below. In case the range of zone ID is sufficient to allocate unique zone IDs, the zone ID itself is sufficient. No further extension is required. Subsequently, different embodiments of defining zones based on R16 zones as geographic areas to associate non-ITS bands with appropriate zone sizes are described. According to a first embodiment, the range of the zone length / width, defined in Rel-16 as sl- ZoneLength-r16 to, e.g., 100 m, can be extended, e.g., up to several km. Two zone length values can be transmitted. One value, i.e., the lower one, refers to the HARQ operation, while the second value, i.e., the larger one, is used to associate the allowed and / or prohibited frequency bands or including the possible RPs. This overlapping new grid of zones demands new zone IDs for unique identification. In case the 12 bit used zone IDs (e.g., up to 4096) are not sufficient to ensure unique zone IDs, the number of bits could either be extended to, e.g., 16 bits or the zone ID could be extended, see section 2.1.1.1. According to a second embodiments, a cluster of Rel-16 zones can be used as geographical area adding a new overlay grid to the zone based R16 zones. The cluster size for Rel-16 defined zones is fixed to 64 x 64 zones. Resulting are quadratic clusters, ranging in cluster size from a minimum of 320m (64 x 5m) to a maximum of 3.2 km (64 x 50 m). Thereby, the cluster can be identified by a new cluster ID uniquely identifying the cluster. Similar to the new zone ID described in the first embodiment, the number of bits required to defined the cluster ID may range from 12 bits (up to 4096 clusters ) to, e.g., 16 bits or even more depending on the maximum number of clusters (e.g., to ensure unique cluster IDs, if required). ID could be extended, see section 2.1.1.1. The allowed / non-allowed frequency bands can be mapped to one or multiple cluster(s).

According to a third embodiment, a multiplication factor can be added to the NR zone size to multiply the size of the Rel-16 NR zone. The multiplication factors for SL zone size can be in the range of, e.g., 2 to, e.g., 1.000 or even exceeding 1.000. Resulting are quadratic enlarged zone with a multiple in size compared to the R16 zones. Thereby, the zone with increased size can be identified as follows:

• The left upper R16 zone ID of the enlarged zone could be used to identify the enlarged zone. Alternatively, any R16 zone ID with enlarged zone could be seen as valid to map to an associated list of frequency bands.

• The allowed / no*n-allowed frequency bands could be mapped to, e.g., the left upper R16 zone ID of the enlarged cluster of zones. Alternatively, all R16 zone IDs within the enlarged zone, could be identified as valid zone to map to one list of allowed / not allowed frequency bands.

• The allowed / non-allowed frequency bands could be mapped to, e.g., one (e.g., upper left) R16 zone.

For example, via a higher layer signaling only one value needs to be signaled to the UE which would the factor along with the usual zone configuration. Hence, the bits can be saved because only the factor needs to be added, anything else remains unchanged.

According to a fourth embodiment, an overlapping new zone with different zone shape can be added, see section 2.1.2.2. A new overlapping grid of zones may be used allowing different new zone formats, such as rectangular (e.g., demanding length and width to define the zone), circular, or any polygon formats using geographic coordinated points, see section 2.1.2.

Subsequently, an example of possible higher layer signaling is provided. For example, in the RRC the IE SL-ZoneConfig in the RRC can be used to configure the zone ID related parameters or a new SL-AreaConfig is introduced. Thereby, in the below example, elements being highlighted in yellow may be provided, modified or changed according to the inventive approach described herein.

Note that any of the above mentioned solutions also apply to any possible geographical area configuration by any higher layer signaling, e.g., via RRC in Rel-16 or Rel-14 SL zone configuration. Any additional IE elements can be added.

2.1 ,2. Geo coordinate points

Geo coordinate points are the most accurate parameters for positioning and are unambiguous. For example, a coordinate of a geographical point with uncertainty of less than 3 meters can be coded with 48 bits, 24 bits for latitude and longitude each [14],

The confined area can be defined by a polygon. The vertices of the polygon can be signaled in the following ways:

• A list of absolute geo coordinates. The LTE Positioning Protocol (LPP) [14] already provides the information element polygon which conveys a list of geo coordinate points describing a geographic shape.

• A reference point and a list of relative geo coordinates to a reference point. The reference point can be one of the vertexes, or an arbitrary point not belonging to the set of vertices. The UE can determine if its position is within the polygon or not. An example for such an algorithm is derived from the residue theorem. A pole is represented by the UE position and the path integral by the angles between the points. The algorithm is the described by (1) computing the angles between UE position and pairs of successive vertices, i.e., angle between first and second vertex and UE position, between second and third, third and fourth, and so on until last and first vertex, (2) summing the angles, (3) wherein, if the sum is 2TT, then the point is inside the polygon and outside if it is 0.

The algorithm is illustrated in Figs. 8a and 8b. Specifically, Figs. 8a and 8b show an illustrative view of an algorithm for determining if a point 402 is located inside or outside of a polygon 404, wherein in Fig. 8a it is assumed that the point 402 is located inside the polygon 404, wherein in Fig. 8b it is assumed that the point 402 is located outside the polygon 404.

An advantage of this algorithm is that the list of vertex points can be of any order.

2.1.2.1. Information size for signaling of geographical coordinates and zone IDs

A single geo coordinate point requires four times the number of bits (e.g., 48 bits) than a zone ID (e.g., 12 bits). However, when defining a confined area, the list of geo coordinate points would usually be shorter than the list of zone IDs. For example, a confined area may be well defined by a polygon with in the order of, for example, 10 points. A list of all zone IDs overlapping with a mid-sized confined area may be in the order of 100 to 1000. Even if only the circumference is signaled an order of up to 100 may be possible.

That means, although the number of bits for a single point is much higher the whole list of geo coordinate points may be much less. Using a reference with relative vertices reduces the total number of bits of the list further. For example, if the maximum distance between relative points is assumed to be less than, for example, 10 km only 24 bits are needed per point, i.e., the list size would be cut by almost one half.

2.1.2.2. Enhanced shape / format of the geographical area

The Rel-16 zones are limited to a guadratic format needed to determine the distance between UEs for HARQ feedback. For geographical areas used for resource allocation, the zone format can be optimized based on, for example, environmental and radio traffic conditions, congestion, service types, QoS etc. It can be flexible and adapted to the given conditions and scenarios. Using geo coordinates, shapes can be defined as a generalization of zones. While zones are square and their edges oriented in parallel to longitude and latitude, geo coordinates based shapes allow much more flexibility. Examples of shapes are

• circle,

• ellipse

• regular polygons, e.g., triangle, square, pentagon, hexagon, heptagon, rectangle, etc.,

• parallelogram.

For example, the simplest possible shape of a circle as a geographical area, requires only the following two parameters to define a geographic area: (1) the geographic coordinates of a reference point, which is assumed to be the center point of the circle, and (2) the distance of the center point to the circle boundary.

This reduced set will reduce the signaling data load, e.g., the number of bytes is strongly limited when initiating or sending updates on mapping of geographic area(s) to frequency bands.

Other shapes like regular polygons, i.e., isosceles triangle, square or polygons with equal edges require (1) a geographic coordinate of a reference point, which is assumed to be the center point of the shape, and (2) a vector consisting of two coordinates represented by distances to the reference point.

The vector allows to rotate the shape to an arbitrary orientation. For example, a square must not be oriented in parallel to longitude and latitude. Of course, if a fixed orientation is specified the vector is reduced to a single distance.

Ellipsis and parallelograms are examples that require (1) a geo. coordinate of a reference point, which is assumed to be the center point of the shape or one of the vertexes, and (2) two vectors consisting of two coordinates represented by distances to the reference point.

In case of an ellipse the reference point is the center of the shape and the two vectors describe the principal and secondary axes. In case of a parallelogram the reference point is a vertex and the two vectors span the plane of the confinement area. Note that a rectangle is a special case of a parallelogram. Fehler! Verweisquelle konnte nicht gefunden werden. provides an overview of examples of shapes and the required parameters that determine their position and orientation on the globe.

Table 1 : Table in a UE to find the allowed/not allowed frequency bands a confined area

See also section 2.3.2., where the mapping table includes an example for the circle shaped geographic area.

The shape concept can be extended to define areas with higher irregularity by combining a set of different shapes. Preferably, these shapes define areas directly adjacent to each other or partly overlapping.

2.1.3. Confinement without geographic area definition

An area where sidelink operation in non-ITS bands is allowed can be detected without configuration of zones or geo coordinate points. This can be done for example by detecting out-of-coverage. If out-of-coverage is detected safely the band is silent and can be used for any other purpose without interfering other systems. That means, no explicit confinement to geographic area is needed and the UE optimally adapts the confinement even if the environment and conditions change. For example, path loss may change with weather conditions or atmospheric conditions may lead to radio wave overreach, so that the confinement area changes shape and size. As preference the sidelink can be operated in the same band where the measurements are done for out-of-coverage detection. According to reciprocity this ensures that the sidelink transmission has the same coverage area as the measurements, i.e. , the downlink of the intended RAT, so that the transmission does not cause interference in its coverage area.

In addition a list of prohibited non-ITS bands could apply. In this case, even if a band is identified as being available due to out-of-coverage, the listed band is not allowed to be used.

2.1.3.1. Criteria / metrics for out-of-coverage detection Criteria or metrics suitable for out-of-coverage detection may be based on, for example, radio signal measurements, such as RSRP, RSRQ, and/or failing detection of SSB.

In case of RSRP and RSRQ, the criteria for cell selection or reselection can be reused with some modifications. In principle those criteria can be stricter. The corresponding equations specified in [15] include offset parameters and a minimum level or quality. Such parameters can be used for adjustment.

If a UE uses the non-ITS band for sidelink transmission it may cause interference to the receiver of a UE in-coverage operating in the mode intended for the band, i.e. , Uu interface with TDD or FDD. Therefore, if a UE intends to operate its sidelink in the same frequency range it has used for out-of-coverage detection measurements careful adjustment is needed to keep a sufficient distance between out-of-coverage UEs and UEs in-coverage of the non-ITS band. In other words, the adjustment of criterion S or R for cell selection and reselection of the incoverage UE and the adjustment of the out-of-coverage detection of the UE operating sidelink on the non-ITS band can ensure an area between in and out-of-coverage where no transmission is allowed. Consequently, this approach only works with 5g (LTE) bands, i.e., not for all non-ITS bands. For example, TV bands are non-ITS and the detection of receivers is not possible, the detection of transmitter is also useless for TV broadcast.

Fig. 9 shows an illustrative view of a no transmission area 500 between an out-of-coverage area 502 and in-coverage area 504 by non-ITS band.

For 5G bands, the transmit power can be strictly controlled if the UE recognizes that it is out- of-coverage and want to use the cellular bands. For example, knowing the transmission power of gNB, find the path loss and if the UE is going to use the same bands of downlink, it can control its power to be sure that its transmission will be just a noise for in-coverage UEs. For this, the UE may estimate the cell size (e.g., knowing the TX power of the gNB and path loss) and consider its distance from the cell edge.

If the non-ITS band is an FFD band the UE may also use the corresponding uplink band, assuming that out-of-coverage detection measurements on the downlink band can be applied to the uplink. This assures that its transmission will be just a noise to the receiver of the gNB. However, the out-of-coverage sidelink communication may still suffer from the uplink communication of in-coverage UEs.

Another criterion can be based on SSB detection. If it is not possible to find a synchronization signal at all out-of-coverage is indicated. 2.1.4. Alternative definitions of areas

To confine non-ITS-band(s) in defined geographical areas, these areas may also be mapped to political, operator specified, geographical exposed areas or within these boundaries. Also existing network specific areas may apply. Examples of these areas to map allowed I not allowed non-ITS bands for sidelink out-of-coverage use are listed below:

A first example is PLMN. For PLMN, the mobile network code (MNC), optionally in combination with the mobile country code (MCC), may apply to identify a geographical area. For example, per PLMN one list of allowed I not-allowed non-ITS bands is given (e.g., provided by the system information), the UE will take this list into account for the selection of non-ITS bands in out-of-coverage. This list of allowed I not-allowed non-ITS bands may apply for the UE as long as the UE is registered in this PLMN. The UE may only update this list of allowed I not-allowed non-ITS bands, once it changes the PLMN (e.g., is successfully registered in another PLMN, e.g., based on the system information of the new PLMN).

A second example is a country, state or any other politically defined region. For the political defined regions above, the MCC, optionally in combination with the MNC, may apply to identify a geographical area. Similar to the scenario for the PLMN, this list may apply as long as the UE is within this politically defined region, i.e. , as long as it has not successfully registered at another PLMN within another country, state, etc.

A third example are company or factory areas (e.g., campus, privately owned areas, here campus networks) or any other type of non-public or private network. Identification of these areas may either use (1) MNC or any code to identify a private network, optionally with MCC (see bullet item “PLMN”), or (2) geographical area coordinates, see fourth example below.

A fourth example are geographical (exposed) areas, such as sea, ocean, city areas, country side, lakes, mountain (ranges). Geographical coordinate points (e.g., see section 2.1.2.) can be used to define any of these area. Examples may be oceans, out-of-coverage of any PLMN, where a different setting of non-ITS bands may apply.

A fifth example are network specific areas, such as (1) a validity area (e.g., consisting of one or multiple cells), (2) cell(s), cluster of cells, zone(s), cluster of zones, or (3) RAN area, tracking area, RAN notification area, UE registration area. In general, related to, e.g., PLMNs, politically defined and any other geographic area, also other events, such long time periods in out-of-coverage or other received notifications, messages, may also effect a modification of the list of allowed I not-allowed non-ITS bands, causing, for example, fallback to a pre-determined list or to prohibit any non-ITS bands from usage as long as no further notification I event is received.

2.2. Non-ITS frequency band related aspects

2.2.1. Non ITS-bands

Non-ITS bands are usually reserved for and occupied by the other modes like llu, FDD, TDD or WiFi. It could consider FR1 and I or FR2 (e.g., above 6 GHz frequency bands). Usually it is not foreseen or forbidden to operate PC5 on these bands - at least not for V2X services. However, in case of out-of-coverage, the sidelink can operate in non-ITS bands since it does not interfere with the RAT intended and specified for that.

Any part of a non-ITS band can be used, for example the uplink or downlink band of an FDD band, a TDD band, supplementary uplink (SUL) or downlink (SDL).

2.2.2. Criteria for selection / usage of specific non-ITS band(s)

In case of out-of-coverage, the UE in mode 2 typically uses the ITS-band for intelligent transport services. In addition, the UE or network can use one or multiple or a range of non- ITS-frequency band(s) based on defined criteria or scenarios.

The allowed usage of non-ITS-band(s), e.g., selected allowed or any allowed non-ITS band or a combination of non-ITS and ITS-band(s), in out-of-coverage scenarios may depend on:

• A specific service, e.g., for entertainment services, downloading big data consuming services. Defined services may only be allowed to use non-ITS-band resources I resource pools.

• Upper layer dependent decision, e.g., demanding high data rates.

• A required data rate.

• 5QI, QoS or any other quality based service I setting or given priority, For example, high priority or high quality-of-service demanding transmissions may have preference to use the ITS-band. However, in case of high load (e.g., exceeding an SINR threshold), UEs may transmit also high priority date on a non-ITS band.

• The network slice. • Considering multi-RAT aspects, e.g., LTE, NR frequency bands.

• Consider co-existence problem.

The configuration of these non-ITS bands can be provided, for example, based on the operator’s policy. This would be operator specific providing

• a static preconfigured list of non-ITS bands to the UE via, e.g., network functions, e.g., based on the UEs supported service, other services being currently supported via this non-ITS band, or

• semi-static higher layer signaling, e.g., by RRC or PC5-RRC signaling, which conveys the information dedicatedly to the UE, or

• can be up to network implementation.

An operator specific configuration may apply to specify given frequency range within non-ITS bands. The simple case would be a TDD band since it is used in UL and DL.

2.2.3. Combining ITS / non-ITS bands (sidelink carrier aggregation)

A non-ITS band could be regarded as an additional carrier to the currently allowed ITS-bands in out-of-coverage. This could be considered as sidelink carrier aggregation (inter-band CA).

Sidelink carrier aggregation may consider a combination of multiple bandwidth parts, and/or could allow to add one to multiple carriers (e.g., max. 32 carriers).

2.3. Mapping of frequency bands to geographical areas

Mapping the range or individual non-ITS frequency bands to geographical areas can be done on different layers using multiple formats. Different approaches are elaborated in the following subsections.

2.3.1. Signaling of mapping geographic area (s') to frequency bands

The lEs defined in the previous sections are all applicable here as well.

The mapping of non-ITS bands to geographic area(s) can be initially provided and updated, in case of (1) out-of-coverage, e.g., via the relays or assistance messages in case of, e.g., groupcast, and/or (2) in-coverage, e.g., via system information. In addition, for the SL on non-ITS bands specific resource pools (RP) could be defined. In addition to common SL non-ITS-band RPs, these RPs may be further segregated based on, for example, cast type, priority, QoS 15QI, type of service.

In embodiments, the setup I configuration of allowed or not allowed frequency bands per geographical area(s) can be (pre-)configured in the UE.

In embodiments, the setup I configuration of allowed or not allowed frequency bands per geographical area(s) can be received from other UEs in discovery procedure (e.g., out-of- coverage scenarios).

In embodiments, the setup I configuration of allowed or not allowed frequency bands per geographical area(s) can be transmitted by the network to the UE (e.g., also considering the scenario of a relaying UE or RSU or IAB node or satellite, e.g., in case of out-of-coverage on

• network access, e.g., first time entering a new network,

• successful accessing a new cell (e.g., successfully performed handover), cluster of cells, validity area,

• only to cell-edge user which may move to out-of-coverage,

• UE triggered, relay-assisted, groupcast (e.g., distribute configuration within group), discovery procedure,

• appended in UE assistance information,

• appended to UE capability information).

In embodiments, the setup I configuration of allowed or not allowed frequency bands per geographical area(s) can be based on core network function providing policies to allow I prohibit UEs to access defined frequency bands in given geographic area(s), see [16], for example, using service area restrictions (e.g., pre-configured and/or dynamically assigned) could add based on a defined network slice.

In embodiments, the setup I configuration of allowed or not allowed frequency bands per geographical area(s) can be a new intelligent node, e.g., new UE capability (e.g., groupcast) or RSU or relay node or network function with enhanced capability to manage both the usage of ITS and non-ITS bands, e.g., using Al.

2.3.2. RRC / MAC In the non-ITS bands existing resource allocation mechanism, e.g., the resource pools, could be used by indicating to the LJE via higher layer signaling first the non-ITS band to look up the resource pool.

This resource pool can be mode specific, dedicated, shared, normal or exceptional for both TX and RX LJE. This could be done via higher layer signaling, for example, the RRC, MAC.

For example, via RRC it could be done by appending the non-ITS band list and the associated resource pool ID in the ResourcePool Information Element. For example, the IE SL- ResourcePool specifies the configuration information for NR sidelink communication resource pool.

Subsequently, an example of the SL-ResourcePool information element is provided. Thereby, in the below example, elements being highlighted in yellow may be provided, modified or changed according to the inventive approach described herein.

Another option could be to define resource pools specific to non-ITS bands. The higher layer signaling can send this RP ID via, e.g., RRC.

Another option could be the conveying of the non-ITS band frequency list via for, example, an IE FrequencylnfoSL-SIB similar to FrequencylnfoUL-SIB. Otherwise it could be added to any of the SIB. i

Subsequently, an example of the FrequencylnfoSL-SIB information element is provided. Thereby, in the below example, elements being highlighted in yellow may be provided, modified or changed according to the inventive approach described herein.

2.3.3. Mapping table

On a more abstract level (e.g., without signaling details), the following table shows examples how to associate a geographical area to frequency bands.

The table may use the following columns, where additional columns may apply and the mentioned columns may be optional.

A first column can describe the reference point (e.g., geo. coordinate of gNB (e.g., current or last gNB prior to out-of-coverage as the reference point) to calculate distance from the center of cell) or any other type of reference point, see section 2.1.1.1. A second column (optional) can describe the distance from reference point to access the predefined non-ITS bands.

A third column can describe coordinates to define the geographical area shape for non-ITS access. For example, for circles a geographic location and radius can be used. In order to add a possible ambiguity (e.g. , for zones), any type of ref. point may be added, see section 2.1.1.1 .

A fourth column can describe frequency bands, which describe allowed or not allowed frequency ranges, i.e. , start and end frequencies (e.g., non-ITS bands); instead of the range of frequencies, this list many also include separate (e.g., comma separated) frequency bands. Additionally, a reference to a blacklist or whitelist of frequency bands may be used. See the following section.

A fifth column can indicated allowed I not allowed (frequency bands). This can be an option as the frequency bands included in the preceding column could be defined to include either the allowed or not allowed frequency bands only. Then this column is not needed.

A sixth column may include optional fields, such as type of resource allocation, type of service allowed to be used, QoS I priority, e.g., when a threshold for the priority is exceed, in order to allow high priority transmissions on defined bands only, and/or other criteria as described, for example, in section 2.2.2.

Table 2 shows an example of above mentioned table in each UE to access non-ITS bands in confined areas.

Table 2: Table in a UE to find the allowed/not allowed frequency bands a confined area The content of the table could be converted and sent I signaled on any higher layer (MAC, RRC or above) and / or (in addition) on the physical layer.

2.3.4 Black or whitelistinq of allowed I not allowed frequency band

A way to define the allowed I not allowed frequency bands could be the use of whitelist and I or blacklist.

A whitelist can list the allowed frequency band(s) or range of frequency band(s), e.g., for one or multiple geographical area(s).

A blacklist can list the not allowed frequency band(s) or range of frequency band(s), e.g., for one or multiple geographical area(s).

2.3.5. Confinement modes

An area of confinement can be either UE centric or gNB centric, depending on which side is responsible to determine if the UE is in the defined geographical area or outside.

An UE centric confinement is possible in all kinds of coverage, out-of-coverage, partial coverage and in-coverage. In this case, the area definition and/or corresponding parameters can be signaled to the UE.

A gNB centric confinement is possible in partial coverage and in-coverage. In this case, the UE signals its position to the gNB and RAN responds with a corresponding permission or prohibition for sidelink operation.

2.3.5.1. Type of medium access with respect to the non-ITS band

Continuous sensing can be useless if unlicensed bands are used. A short sensing before the transmission might be a better approach.

Random access might also be configured by network for some geographical areas with low density of users (e.g., based on historical vehicles traffic in some parts of roads)

2.4. Further embodiments According to embodiments, additionally available/allowed frequency bands allow to boost the transmission capacity. In addition, restricting the allowed frequency may reduce I avoid possible interference.

Embodiments can be implemented in sidelink communication in outdoor (e.g., for V2X) or indoor (e.g., industrial communication) to boost the sidelink transmission capacity by allowing additional frequency bands or limit possible interference by not-allowing defined frequency bands.

Although some aspects of the described concept have been described in the context of an apparatus, it is clear that these aspects also represent a description of the corresponding method, where a block or a device corresponds to a method step or a feature of a method step. Analogously, aspects described in the context of a method step also represent a description of a corresponding block or item or feature of a corresponding apparatus.

Various elements and features of the present invention may be implemented in hardware using analog and/or digital circuits, in software, through the execution of instructions by one or more general purpose or special-purpose processors, or as a combination of hardware and software. For example, embodiments of the present invention may be implemented in the environment of a computer system or another processing system. Fig. 10 illustrates an example of a computer system 500. The units or modules as well as the steps of the methods performed by these units may execute on one or more computer systems 500. The computer system 500 includes one or more processors 502, like a special purpose or a general-purpose digital signal processor. The processor 502 is connected to a communication infrastructure 504, like a bus or a network. The computer system 500 includes a main memory 506, e.g., a random-access memory (RAM), and a secondary memory 508, e.g., a hard disk drive and/or a removable storage drive. The secondary memory 508 may allow computer programs or other instructions to be loaded into the computer system 500. The computer system 500 may further include a communications interface 510 to allow software and data to be transferred between computer system 500 and external devices. The communication may be in the from electronic, electromagnetic, optical, or other signals capable of being handled by a communications interface. The communication may use a wire or a cable, fiber optics, a phone line, a cellular phone link, an RF link and other communications channels 512.

The terms “computer program medium” and “computer readable medium” are used to generally refer to tangible storage media such as removable storage units or a hard disk installed in a hard disk drive. These computer program products are means for providing software to the computer system 500. The computer programs, also referred to as computer control logic, are stored in main memory 506 and/or secondary memory 508. Computer programs may also be received via the communications interface 510. The computer program, when executed, enables the computer system 500 to implement the present invention. In particular, the computer program, when executed, enables processor 502 to implement the processes of the present invention, such as any of the methods described herein. Accordingly, such a computer program may represent a controller of the computer system 500. Where the disclosure is implemented using software, the software may be stored in a computer program product and loaded into computer system 500 using a removable storage drive, an interface, like communications interface 510.

The implementation in hardware or in software may be performed using a digital storage medium, for example cloud storage, a floppy disk, a DVD, a Blue-Ray, a CD, a ROM, a PROM, an EPROM, an EEPROM or a FLASH memory, having electronically readable control signals stored thereon, which cooperate (or are capable of cooperating) with a programmable computer system such that the respective method is performed. Therefore, the digital storage medium may be computer readable.

Some embodiments according to the invention comprise a data carrier having electronically readable control signals, which are capable of cooperating with a programmable computer system, such that one of the methods described herein is performed.

Generally, embodiments of the present invention may be implemented as a computer program product with a program code, the program code being operative for performing one of the methods when the computer program product runs on a computer. The program code may for example be stored on a machine-readable carrier.

Other embodiments comprise the computer program for performing one of the methods described herein, stored on a machine-readable carrier. In other words, an embodiment of the inventive method is, therefore, a computer program having a program code for performing one of the methods described herein, when the computer program runs on a computer.

A further embodiment of the inventive methods is, therefore, a data carrier (or a digital storage medium, or a computer-readable medium) comprising, recorded thereon, the computer program for performing one of the methods described herein. A further embodiment of the inventive method is, therefore, a data stream or a sequence of signals representing the computer program for performing one of the methods described herein. The data stream or the sequence of signals may for example be configured to be transferred via a data communication connection, for example via the Internet. A further embodiment comprises a processing means, for example a computer, or a programmable logic device, configured to or adapted to perform one of the methods described herein. A further embodiment comprises a computer having installed thereon the computer program for performing one of the methods described herein.

In some embodiments, a programmable logic device (for example a field programmable gate array) may be used to perform some or all of the functionalities of the methods described herein. In some embodiments, a field programmable gate array may cooperate with a microprocessor in order to perform one of the methods described herein. Generally, the methods are preferably performed by any hardware apparatus.

The above described embodiments are merely illustrative for the principles of the present invention. It is understood that modifications and variations of the arrangements and the details described herein are apparent to others skilled in the art. It is the intent, therefore, to be limited only by the scope of the impending patent claims and not by the specific details presented by way of description and explanation of the embodiments herein.

References

[1] RP-193231 : New WID on NR sidelink enhancement, Dec. 2019

[2] TR 38.885

[3] TS 36.300

[4] TS 23.303

[5] TS 36.331

[6] TS 38.331

[7] TS 38.214

[8] TR 37.985

[9] TS 38.213

[10] TS 38.101-1, rev. 16.4.0

[11] TS 36.101

[12] TR 38.886 V16.1.0 (2020-09): V2X Services based on NR;

User Equipment (UE) radio transmission and reception

[13] Military Standard WGS84 Metric MIL-STD-2401 (11 January 1994): "Military

Standard Department of Defence World Geodetic System (WGS)"

[14] TS 37.355

[15] TS 38.304

[16] TS 23.501

[17] https://www.etsi.org/technologies/automotive-intelligent-transport

[18] https://www.fcc.gov/wireless/bureau-divisions/mobility-division/dedicated-short- range-communications-dsrc-service

Abbreviations

3GPP third generation partnership project

5QI 5G QoS identifier

AAIM aircraft autonomous integrity monitoring

AL alert limit

AMF access and mobility management function

ARAIM advanced receiver autonomous integrity monitoring

BS base station

BWP bandwidth part

CBG code block group

CQI channel quality indicator

CSI-RS channel state information-reference signal

D2D device-to-device

DAI downlink assignment index

DCI downlink control information

DL downlink

DRX discontinuous reception

FFT fast Fourier transform gNB next generation node B - base station

GNSS global navigation satellite system

HARQ hybrid automatic repeat request

IE information element loT internet of things

ITS intelligent transportation systems

LTE long term evolution

MAC medium access control

MCR minimum communication range

MCS modulation and coding scheme

MIB master information block

MMC mobile country code

MNC mobile network code NACK negative acknowledgement

NB node B

NR new radio, 5G

NTN non-terrestrial network

NW network

OFDM orthogonal frequency-division multiplexing

OFDMA orthogonal frequency-division multiple access

PBCH physical broadcast channel

PC5 sidelink interface

PDCCH physical downlink control channel

PDSCH physical downlink shared channel

PL protection level

PLMN public land mobile network

PPP point-to-point protocol

PRACH physical random access channel

PRB physical resource block

PRS public regulated services (Gallileo)

PSCCH physical sidelink control channel

PSFCH physical sidelink feedback channel

PLICCH physical uplink control channel

P-UE pedestrian UE, in embodiments not limited to pedestrians, but represents any UE with a need to save power, e.g., electrical cars, cyclists, etc.

PLISCH physical uplink shared channel

QoS quality of service

RAIM receiver autonomous integrity monitoring

RAN radio access networks

RAT radio access technology

RNTI radio network temporary identifier

RS reference symbols/signal

RSRP reference signal received power

RSRQ reference signal received quality

RTK real time kinematics

RTT round trip time SBAS space-based augmentation systems

SBI service based interface

SCI sidelink control information

SDL supplementary downlink

SI system information

SIB system information block

SINR signal-to-interference ratio

SL sidelink

SSB synchronization signal/PBCH block

SSR state space representation

SUL supplementary uplink

TDD time division duplex

TDOA time difference of arrival

TIR target integrity risk

TRP transmission reception point

TTA time-to-alert

TTI transmission time interval

UAV unmanned aerial vehicle

UCI uplink control information

UE user equipment

UL uplink

UMTS universal mobile telecommunication system

V2V vehicle-to-vehicle

V2X vehicle-to-everything

VRB virtual resource block

VRU vulnerable road user

V-UE vehicular UE

WLAN wireless local area network

Claims

Claims 1. First transceiver of a wireless communication system, wherein the first transceiver is configured to perform, in a geographical area, a communication over a sidelink in a frequency band that is not restricted for sidelink- communication only, wherein the frequency band is either one out of - one or more available frequency bands that are available for sidelink- communication in said geographical area, - different from one or more prohibited frequency bands that are prohibited for sidelink-communication in said geographical area.

2. First transceiver according to the preceding claim, wherein the first transceiver is configured to operate in a sidelink out of coverage scenario, wherein the first transceiver is configured to perform, in the sidelink out of coverage scenario, the communication over the sidelink in the frequency band that is not restricted for sidelink-communication only.

3. First transceiver according to the preceding claim, wherein the first transceiver is configured to detect the sidelink out of coverage scenario based on radio signal measurements or detection attempts.

4. First transceiver according to one of the preceding claims, wherein the frequency band that is not restricted for sidelink-communication only is a non-ITS-band.

5. First transceiver according to one of the preceding claims, wherein the first transceiver is configured to perform said communication over the sidelink in said frequency band for a service different than services relating to transport and traffic management.

6. First transceiver according to one of the preceding claims, wherein the first transceiver is configured to select, for the communication over the sidelink in said geographical area, the frequency band in dependence on - the one or more available frequency bands that are available for sidelink- communication in said geographical area, such that the frequency band is one out of the one or more available frequency bands, or - the one or more prohibited frequency bands that are prohibited for sidelink- communication in said geographical area, such that the frequency band is different from the one or more prohibited frequency bands.

7. First transceiver according to the preceding claim, wherein the first transceiver is configured to select the frequency band further in dependence on at least one out of - a quality criterion, - a priority criterion, - a type of service criterion, - an upper layer signaling, - a required data rate, - a network slice, - multi RAT aspects, - co-existence problem.

8. First transceiver according to one of the preceding claims, wherein the first transceiver is configured to determine whether the first transceiver is located within the geographical area, wherein the first transceiver is configured to perform the communication over the sidelink using said frequency band if the first transceiver is located within the geographical area.

9. First transceiver according to one of the preceding claims, wherein the one or more available frequency bands and/or the one or more prohibited frequency bands for said geographical area are preconfigured.

10. First transceiver according to one of the preceding claims, wherein the first transceiver is configured to receive from a second transceiver of the wireless communication system a configuration message comprising a configuration information defining - the geographical area, and/or - the one or more available frequency bands and/or the one or more prohibited frequency bands for said geographical area.

11. First transceiver according to claim 10, wherein the first transceiver is configured to receive the configuration message from the second transceiver over the sidelink in a sidelink out of coverage scenario.

12. First transceiver according to claim 10, or wherein the first transceiver is configured to receive the configuration message from the second transceiver via a downlink in a in coverage scenario.

13. First transceiver according to one of the claims 10 to 12, wherein the configuration message further defines at least one available resource pool of the one or more available frequency bands.

14. First transceiver according to claim 10, wherein the configuration information describes one or more zone IDs defining one or more geographical zones that - overlap with said geographical area, - define a circumference of said geographical area, or - define vertexes of said geographical area.

15. First transceiver according to claim 14, wherein the configuration information further describes a reference location uniquely defining a location of the geographical area in combination with the one or more zone IDs.

16. First transceiver according to claim 15, wherein the reference location is one out of - a geographical reference coordinate point, - a cell ID, - an ID of a mobile network defined area. - gNB position, - ZIP code.

17. First transceiver according to claim 10, wherein the configuration information describes at least one geographical coordinate point defining the geographical area.

18. First transceiver according to claim 17, wherein the at least one geographical coordinate points include a plurality of absolute geographical coordinate points spanning a polygon defining the geographical area.

19. First transceiver according to claim 17, wherein the geographical coordinate points include at least one absolute geographical coordinate point and a plurality of relative geographical coordinate points associated with the at least one absolute geographical coordinate point, wherein the plurality of relative geographical coordinate points span a polygon defining the geographical area.

20. First transceiver according to claim 17, wherein the configuration information further describes a shape that together with the at least one geographical coordinate point defines the geographical area.

21. First transceiver according to one of the claims 10 to 20, wherein the configuration information maps - the geographical area, and - the one or more available frequency bands and/or the one or more prohibited frequency bands.

22. First transceiver according to one of the claims 10 to 21, wherein the configuration information defines - at least two geographical areas, and - one or more available frequency bands and/or the one or more prohibited frequency bands for each of the two geographical areas.

23. First transceiver according to the preceding claim, wherein the first transceiver is configured to determine in which of the at least two geographical areas the first transceiver is located, wherein the first transceiver is configured to select the frequency band in dependence on - the one or more available frequency bands that are available for sidelink- communication in the geographical area of the at least two geographical areas in which the first transceiver is located, - the one or more prohibited frequency bands that are prohibited for sidelink- communication in the geographical area of the at least two geographical areas in which the first transceiver is located.

24. First transceiver according to one of the claims 1 to 10, wherein the geographical area is a political, operator specified or geographical exposed area.

25 First transceiver according to one of the preceding claims wherein the frequency band that is not restricted for sidelink-communication is one out of - an uplink band, - a downlink band, - a FDD band, - a TDD band, - a supplementary uplink band, - a supplementary downlink band.

26. First transceiver according to one of the preceding claims, wherein the first transceiver is configured to perform the communication over the sidelink using at least one bandwidth part of the frequency band that is not restricted for sidelink-communication only and at least one bandwidth part of the frequency band that is restricted for sidelink-communication only.

27. First transceiver according to one of the preceding claims, wherein the first transceiver is configured to access the frequency band based on one out of - a short sensing before a sidelink transmission, - a discontinuous sensing before a sidelink transmission, - a random access.

28. First transceiver according to one of the preceding claims, wherein the first transceiver is a mobile transceiver.

29. First transceiver according to one of the preceding claims, wherein the first transceiver is an user equipment, UE.

30. First transceiver of a wireless communication system, wherein the first transceiver is configured to operate in a sidelink out of coverage scenario wherein the first transceiver is configured to perform, in the sidelink out of coverage scenario, a communication over the sidelink in a frequency band that is not restricted for sidelink-communication only, wherein the frequency band is either one out of - one or more available frequency bands that are available for sidelink- communication, - different from one or more prohibited frequency bands that are prohibited for sidelink-communication.

31. First transceiver according to the preceding claim, wherein the first transceiver is configured to detect the sidelink out of coverage scenario based on Uu radio signals measurements or detection attempts.

32. First transceiver according to the preceding claim, wherein the first transceiver is configured to only perform the communication over the sidelink in said frequency band if the Uu radio signal measurements indicate that the first transceiver maintains a predefined distance with respect to other transceivers of the wireless communication system that are communicating via the Uu interface.

33. Second transceiver of a wireless communication system, wherein the second transceiver is configured to transmit a configuration message to a first transceiver of the wireless communication system, wherein the configuration message comprises a configuration message comprising a configuration information describing at least one out of - one or more available frequency bands that are available for sidelink- communication, - one or more prohibited frequency bands that are prohibited for sidelink- communication, wherein the one or more frequency bands and/or the one or more prohibited frequency bands are not restricted for sidelink-communication only.

34. Wireless communication system, comprising: a first transceiver according to one of the preceding claims, and a second transceiver according to one of the preceding claims.

35. Method for operating a first transceiver of a wireless communication system, the method comprising: performing, in a geographical area, a communication over a sidelink in a frequency band that is not restricted for sidelink-communication only, wherein the frequency band is either one out of - one or more available frequency bands that are available for sidelink- communication in said geographical area, - different from one or more prohibited frequency bands that are prohibited for sidelink-communication in said geographical area.

36. Method for operating a first transceiver of a wireless communication system, the method comprising: operating the first transceiver in a sidelink out of coverage scenario, performing, in the sidelink out of coverage scenario, a communication over the sidelink in a frequency band that is not restricted for sidelink-communication only, wherein the frequency band is either one out of - one or more available frequency bands that are available for sidelink- communication, - different from one or more prohibited frequency bands that are prohibited for sidelink-communication.

37. Method for operating a second transceiver of a wireless communication system, the method comprising: transmitting a configuration message to a first transceiver of the wireless communication system, wherein the configuration message comprises a configuration message comprising a configuration information describing at least one out of - one or more available frequency bands that are available for sidelink- communication, - one or more prohibited frequency bands that are prohibited for sidelink- communication, wherein the one or more frequency bands and/or the one or more prohibited frequency bands are not restricted for sidelink-communication only.

38. Computer program for performing a method according to one of the preceding claims.