HK40043631B

HK40043631B - Enhanced quality of service for v2x

Info

Publication number: HK40043631B
Application number: HK62021033245.3A
Authority: HK
Inventors: Elke Roth-Mandutz; Khaled Shawky Hassan Hussein; Shubhangi BHADAURIA; Martin Leyh
Original assignee: Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V.
Priority date: 2018-03-29
Filing date: 2019-03-28
Publication date: 2022-11-18

Description

The present invention relates to the field of wireless communication networks, and more specifically, to concepts for transmitting data for ultra-reliable low latency communications (URLLC). Some embodiments relate to an enhanced quality of service for V2X.

Fig. 1 is a schematic representation of an example of a wireless network 100 including a core network 102 and a radio access network 104. The radio access network 104 may include a plurality of base stations gNB₁ to gNB₅, each serving a specific area surrounding the base station schematically represented by respective cells 106₁ to 106₅. The base stations are provided to serve users within a cell. The term base station (BS) refers to as gNB in 5G networks, eNB in UMTS / LTE / LTE-A / LTE-A Pro, or just BS in other mobile communication standards. A user may be a stationary device or a mobile device. Further, the wireless communication system may 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 having embedded therein electronics, software, sensors, actuators, or the like as well as network connectivity that enable these devices to collect and exchange data across an existing network infrastructure. Fig. 1 shows an exemplary view of only five cells, however, the wireless communication system may include more such cells. Fig. 1 shows two users UE₁ and UE₂, also referred to as user equipment (UE), that are in cell 106₂ and that are served by base station gNB₂. Another user UE₃ is shown in cell 106₄ which is served by base station gNB₄. The arrows 108₁, 108₂ and 108₃ schematically represent uplink/downlink connections for transmitting data from a user UE₁, UE₂ and UE₃ to the base stations gNB₂, gNB₄ or for transmitting data from the base stations gNB₂, gNB₄ to the users UE₁, UE₂, UE₃. Users, such as mobile devices (e.g., vehicles comprising UEs), may further communicate directly with each other in both, coverage mode (e.g., LTE V2X mode 3; respectively D2D mode1 or NR V2X mode 1) and out-of-coverage mode (e.g., LTE V2X mode 4; respectively D2D mode 2 or NR V2X mode 2) using the PC5 interface (e.g., in case of D2D, LTE V2X/V2V or NR V2X/V2V), as will be discussed later on with respect to Figs. 3 and 4. Further, Fig. 1 shows two loT devices 110₁ and 110₂ in cell 106₄, which may be stationary or mobile devices. The loT device 110₁ accesses the wireless communication system via the base station gNB₄ to receive and transmit data as schematically represented by arrow 112₁. The loT device 110₂ accesses the wireless communication system via the user UE₃ as is schematically represented by arrow 112₂. The respective base station gNB₁ to gNB₅ may be connected to the core network 102, e.g. via the S1 interface, via respective backhaul links 114₁ to 114₅, which are schematically represented in Fig. 1 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 gNB₁ to gNB₅ may connected, e.g. via the S1 or X2 interface or XN interface in NR, with each other via respective backhaul links 116₁ to 116₅, which are schematically represented in Fig. 1 by the arrows pointing to "gNBs".

The wireless network or communication system depicted in Fig. 1 may be a heterogeneous network having two distinct overlaid networks, a network of macro cells with each macro cell including a macro base station, like base station eNB₁ to eNB₅, and a network of small cell base stations (not shown in Fig. 1), like femto or pico base stations.

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 and uplink shared channels (PDSCH, PUSCH) carrying user specific data, also referred to as downlink and uplink payload data, the physical broadcast channel (PBCH) carrying for example a master information block (MIB) and a system information block (SIB), the physical downlink and uplink control channels (PDCCH, PUCCH) carrying for example the downlink control information (DCI), etc. For the uplink, the physical channels may further include the physical randomaccess channel (PRACH or RACH) used by UEs for accessing the network once a UE synchronized and obtained the MIB and SIB. The physical signals may comprise reference signals (RS), synchronization signals and the like. The resource grid may comprise a frame or radioframe having a certain duration, like 10 milliseconds, 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., 2 subframes with a length of 1 millisecond. Each subframe may include two slots of 6 or 7 OFDM symbols depending on the cyclic prefix (CP) length. A frame may also consists of a smaller number of OFDM symbols, e.g. if utilizing shortened transmission time intervals (sTTI) or a mini-slot / non-slot-based frame structure comprising of 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 (OFDMA) system, or any other IFFT-based signal with or without CP, e.g. DFT-s-OFDM. Other waveforms, like nonorthogonal waveforms for multiple access, e.g. filter-bank multicarrier (FBMC), generalized frequency division multiplexing (GFDM) or universal filtered multi carrier (UFMC), may be used. The wireless communication system may operate, e.g., in accordance with the LTE-Advanced pro standard or the 5G or NR (New Radio) standard.

In the wireless communication network as shown in Fig. 1 the radio access network 104 may be a heterogeneous network including a network of primary cells, each including a primary base station, also referred to as a macro base station. Further, a plurality of secondary base stations, also referred to as small cell base stations, may be provided for each of the macro cells. Fig. 2 is a schematic representation of a cell, like cell 106₁ in Fig. 1, having two distinct overlaid networks, the networks comprising a macro cell network including the macro cell 106₁, and a small cell network. Although Fig. 2 represents only a single macro cell, it is noted that one or more of the other cells in Fig. 1 may also use the overlaid networks. The small cell network comprises a plurality of small cell base stations SeNB₁ to SeNB₅ each operating within a respective area 120₁ to 120₅, also referring as the coverage area of the small cell. The small cell base stations SeNB₁ to SeNB₅ may be controlled by the macro cell base station MeNB₁ to which the respective small cell base stations SeNB₁ to SeNB₅ are connected via respective backhaul links 122₁ to 122₅. Rather than connecting the small cell base stations via the backhaul links to the macro cell base station, one or more of the small cell base stations may be coupled to the core network via respective backhaul links. Fig. 2 further shows a user equipment UE being served by the macro cell base station MeNB₁ as indicated by arrow 124₁ and by the small cell base station SeNB₁, as indicated schematically by the arrow 124₂.

In mobile communication networks, for example in networks like those described above with reference to Fig. 1 and Fig. 2, like a 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, pedestrians or network infrastructure (V2I). Other UEs may not be vehicular related UEs but may comprise any of the above mentioned devices. Such devices may also communicate directly with each other using the sidelink channels (i.e., direct communication, such as D2D or V2X communication, where V2X could be seen as special form of D2D, e.g., D2D with mobility).

When considering two UEs directly communicating with each other over the sidelink, both UEs may be served by the same base station, i.e., 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 a "in coverage" scenario. In accordance with other examples, both UEs that communicate over the sidelink may not be served by a base station which 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 or in Fig. 2, rather, it means that these UEs are not connected to a base station, for example, they are not in a RRC connected state. Yet another scenario is called a "partial coverage" scenario, in accordance with which one of the two UEs which communicate with each other over the sidelink, is served by a base station, while the other UE is not served by the base station. In each of the above-mentioned scenarios, the UEs and/or the BS should have knowledge about the resources to be used for the sidelink communication among the UEs.

Fig. 3 shows a schematic representation of a situation in which two UEs directly communicating with each other are both in coverage of 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 or Fig. 2. 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 (this also works for any scenario where the 2 UEs are connected to different gNBs). 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. The BS schedules and assigns the resources to be used within a given resource pool for the V2V communication over the sidelink. The UE operates in this mode only when in coverage and in an RRC_CONNECTED state. This configuration is also referred to as a mode 3 configuration (e.g., for LTE V2X, for D2D this is referred to as mode 1). For NR V2X (from release 16 onwards) this is referred to as mode 1.

Fig. 4 shows a scenario in which the UEs are out of coverage of a BS, i.e., the respective UEs directly communicating with each other may or may not be connected to a base station (i.e. they also may be physically within the coverage of a cell of a wireless communication network and could even be in either RRC_CONNECTED or RRC_IDLE state). Three vehicles 206, 208 and 210 are shown directly communicating with each other over a sidelink, e.g., using the PC5 interfaces. The scheduling and/or interference management of the V2V traffic is based on algorithms implemented in the UEs and/or (partially) pre-configured by the network. This configuration is also referred to as a mode 4 configuration (e.g., for LTE V2X). For D2D this is referred to as mode 2. For NR V2X this is referred to as mode 2.

As mentioned above, the scenario in Fig. 4 which is an out-of-coverage scenario does not mean that the respective mode 4 UEs (e.g., for LTE V2X; respectively mode 2 for D2D or NR V2X) have to be outside of the coverage of a base station, rather, it means that the respective mode 4 UEs are not served by a base station or are not connected to the base station of the coverage area. Thus, there may be situations in which, within the coverage area 200 shown in Fig. 3, in addition to the mode 3 UEs 202, 204 (e.g., for LTE V2X; respectively mode 1 for D2D or NR V2X) also mode 4 UEs 206, 208, 210 (e.g., for LTE V2X; respectively mode 2 for D2D or NR V2X) are present. Since the mode 4 UEs 206-210 schedule their resources autonomously and are not connected to the network, the base station is not aware of resources used by the mode 4 UEs 206-210 for the sidelink communication and, likewise, the mode 4 UEs 206-210 are not aware of resources scheduled by the base station gNB to the mode 3 UEs 202, 204 for a sidelink communication. Thus, resource collisions among the UEs in the respective modes and among mode 4 UEs may occur.

In wireless communication networks as described above with reference to Fig. 1 to Fig. 4, the current (e.g., LTE) V2X specification of 3GPP supports 2 modes:

Mode 3: resource provisioning via eNB. A UE is connected to an eNB supporting V2X operation and obtains its resources from the eNB
Mode 4: autonomous mode / distributed scheduling. A UE is required to detect suitable resources by itself. Currently a one-second sensing operation is needed prior to using any resources for transmission.

In wireless communication networks, the sidelink specification of 3GPPfor ProSe or D2D (starting from release 12), supports 2 modes:

Mode 1: resource provisioning via eNB or a gNB. A UE is connected to an eNB or a gNB supporting sidelink configuration and obtains its resources from the eNB or the gNB.
Mode 2: A UE is required to detect suitable resources by itself.

In wireless communication networks, the NR sidelink V2X specification of 3GPP (starting with release 16) supports 2 modes:

Mode 1: resource provisioning via gNB or eNB. A UE is connected to gNB or eNB supporting sidelink configuration and obtains its resources from any of them.
Mode 2: A UE is required to detect suitable resources by itself. The UE determines, i.e. BS does not schedule, SL transmission resource(s) within SL resources configured by BS/network or pre-configured SL resources [13].

The so-called emergency pool is a special resource pool that can be used for very limited purposes (e.g. during handover) by UEs that have no configured resources for transmission.

Current 3GPP specifications include the priority handling based on the PPPP, which includes preferred scheduling and selection of PPPP associated resource pools for data transmission.

V2X, V2V, D2D, and sidelinks are described in [1, 3, 4]. Grant-free transmission in the sidelinks (transmission mode 2 for D2D and mode 4 for LTE V2X) is described in [2, 5].

Regarding network slicing, it was agreed (RAN2) that the UE supports currently a maximum of 8 slices in parallel. However, the network may need to support multiple e.g. hundreds of slices [7].

To enhance the reliability, packet duplication is already foreseen in the specification. The scheme how best to implement the packet duplication, especially regarding the new topic resource pool sharing mode 3 (e.g., for LTE V2X; additionally mode 1 for D2D or mode 1 for NR V2X) and mode 4 (e.g., for LTE V2X; additionally mode 2 for D2D or mode 2 NR V2X), is still open.

In [17], a solution for QoS support over PC5 by re-using the PPPP and PPPR mechanism is described.

In [18] packet duplication for PC5 is described.

Therefore, it is the object of the present invention to provide a concept for implementing the packet duplication, especially regarding the new topic resource pool sharing mode 3 and mode 4 for LTE V2X and/or mode 1 and mode 2 for NR V2X and D2D.

This object is solved by the independent claims.

Advantageous implementations are addressed in the dependent claims.

Embodiments provide a transceiver for a wireless communication system, wherein the transceiver is configured to communicate with at least one other transceiver of the wireless communication system using sidelink resource pools [e.g., mode 3 resource pool, mode 4 resource pool, shared resource pool, unshared resource pool or exceptional resource pool] of the wireless communication system, wherein the transceiver is configured to transmit a data packet on one of the sidelink resource pools of the wireless communication system to the other transceiver of the wireless communication system, wherein the transceiver is configured to, if a PPPR value (PPRR = ProSe per packet reliability) associated with said data packet or with data contained in said data packet indicates a high reliability [of said data packet], to re-transmit said data packet at least on once on another sidelink resource pool of the sidelink resource pools of the wireless communication system.

For example, for NR-V2X, a per-packet priority (similar to PPPP or PPPR as in LTE, e.g. any QoS metric) is being specified at least for non-unicast (e.g., broadcast or groupcast) communication scenarios.

For example, for NR V2X for unicast and possibly groupcast communication a bearer based model is being specified using other QoS metrics, e.g., 5QI, or PQI or VQI, or any other QoS flow values [14], [15], [16].

In embodiments, a number of re-transmissions of said data packet depends on the PPPR value.

In embodiments, the transceiver is configured to obtain [e.g., to receive, to determine, or to extract from said data packet] the PPPR value associated with said data packet or with the data contained in said data packet.

In embodiments, the sidelink resource pools of the wireless communication system are at least two out of a mode 3 resource pool, a mode 4 resource pool, a shared resource pool, an unshared resource pool or an exceptional resource pool.

In embodiments, the PPPR value ranges from 1 to 8, wherein a PPPR value of 1 indicates the highest reliability and a PPPR value of 8 indicates the lowest reliability.

In embodiments, the transceiver is configured to retransmit said data packet at least once, if the PPPR value exceeds a predefined threshold.

Thereby, note that, as PPPR value mapping to reliability is upside down, i.e. 1 is highest, 8 is lowest priority, "exceeding the threshold" refers to a PPPR value being equal to or smaller than a predefined PPPR value.

In detail, the priority threshold indicates the upper bound of the PPPP range which is associated with the configurations in cbr-Configlndex and in tx-ConfiglndexList. The upper bounds of the PPPR ranges are configured in ascending order for consecutive entries of SL-PPPR-TxConfiglndex in SL-CBR-PPPR-TxConfigList. For the first entry of SL-PPPR-TxConfiglndex, the lower bound of the PPPR range is 1.

In embodiments, the transceiver is configured to retransmit said data packet at least once, if the PPPR value indicates a reliability that is equal to or higher than a predefined reliability

For example, for NR-V2X, the transceiver is configured

For per packet based QoS model: to retransmit said data packet at least once
For the bearer based QoS model: to setup a parallel or multiple bearer if the QoS metric e.g. 5QI, PQI, VQI or PPPP or PPPR or any other QoS metric value exceeds a predefined threshold. [TS 23.501], [TR 23.786], [16]

In embodiments, the transceiver is served by a central transceiver, for example, a base station, of the wireless communication system, wherein the transceiver is configured to operate in (e.g., LTE) V2X Mode 3, in which scheduling of resources for the communication with the at least one other transceiver is performed by the central transceiver, wherein the transceiver is configured to transmit the data packet on a (e.g., LTE) V2X mode 3 resource pool of the sidelink resource pools of the wireless communication system, and wherein the transceiver is configured to re-transmit the data packet at least once on a (e.g., LTE) V2X mode 4 resource pool, a shared resource pool, an unshared resource pool or an exceptional resource pool of the sidelink resource pools of the wireless communication system.

In embodiments, the transceiver is served by a central transceiver, for example, a base station, of the wireless communication system, wherein the transceiver is configured to operate in NR V2X mode 1, in which scheduling of resources for the communication with the at least one other transceiver is performed by the central transceiver, wherein the transceiver is configured to transmit the data packet on a NR V2X mode 1 resource pool of the sidelink resource pools of the wireless communication system, and wherein the transceiver is configured to re-transmit the data packet at least once on the same or a different mode 1 NR V2X resource pool, the same or a different mode 3 LTE V2X resource pool, a LTE V2X mode 4 resource pool, a shared resource pool, an unshared resource pool or an exceptional resource pool of the sidelink resource pools of the wireless communication system.

In embodiments, the transceiver is served by a central transceiver, for example, a base station, of the wireless communication system, wherein the transceiver is configured to operate in D2D mode 1, in which scheduling of resources for the communication with the at least one other transceiver is performed by the central transceiver, wherein the transceiver is configured to transmit the data packet on the same or different D2D mode 1 resource pool of the sidelink resource pools of the wireless communication system, and wherein the transceiver is configured to re-transmit the data packet at least once on a D2D mode 2 resource pool, a shared resource pool, an unshared resource pool or an exceptional resource pool of the sidelink resource pools of the wireless communication system.

In embodiments, the transceiver is configured to operate in (e.g., LTE) V2X Mode 4, wherein the transceiver is configured to schedule resources for the sidelink communication autonomously, wherein the transceiver is configured to transmit the data packet on a (e.g., LTE) V2X mode 4 resource pool of the sidelink resource pools of the wireless communication system, and wherein the transceiver is configured to re-transmit the data packet at least once on a (e.g., LTE) V2X mode 3 resource pool, a shared resource pool, an unshared resource pool or an exceptional resource pool of the sidelink resource pools of the wireless communication system.

In embodiments, the transceiver is configured to operate in NR V2X Mode 2, wherein the transceiver is configured to schedule resources for the sidelink communication autonomously, wherein the transceiver is configured to transmit the data packet on a NR V2X mode 2 resource pool of the sidelink resource pools of the wireless communication system, and wherein the transceiver is configured to re-transmit the data packet at least once on a NR V2X mode 2 resource pool, a NR V2X mode 1 resource pool, a LTE V2X mode 4 resource pool, a LTE V2X mode 3 resource pool, a shared resource pool, an unshared resource pool or an exceptional resource pool of the sidelink resource pools of the wireless communication system.

In embodiments, the transceiver is configured to operate in D2D Mode 2, wherein the transceiver is configured to schedule resources for the sidelink communication autonomously, wherein the transceiver is configured to transmit the data packet on a D2D mode 2 resource pool of the sidelink resource pools of the wireless communication system, wherein the transceiver is configured to re-transmit the data packet at least once on a D2D mode 2 resource pool, a D2D mode 1 resource pool, a shared resource pool, an unshared resource pool or an exceptional resource pool of the sidelink resource pools of the wireless communication system.

In embodiments, the transceiver is configured to, in case RLF (Radio Link Failure)/no-sensing information or handover is available, to transmit said data packet on an exceptional resource pool of the sidelink resource pools of the wireless communication system, and to re-transmit said data packet at least once on a previously [e.g., prior to RLF/no-sensing information or handover available] used resource pool of the sidelink resource pools of the wireless communication system.

In embodiments, the transceiver is configured to, in case of carrier aggregation, to transmit said data packet on a component carrier, and to re-transmit said data packet at least once on another component carrier.

Further embodiments provide a transceiver for a wireless communication system, wherein the transceiver is configured to communicate with at least one other transceiver of the wireless communication system, wherein the transceiver is configured to transmit a data packet on a component carrier to the other transceiver of the wireless communication system, wherein the transceiver is configured to, if a PPPR value associated with said data packet or with data contained in said data packet indicates a high reliability, to re-transmit said data packet at least once on at least one other component carrier.

In embodiments, the transceiver is configured to retransmit said data packet at least once, if the PPPR value indicates a reliability that is equal to or higher than a predefined reliability or threshold.

In embodiments, the transceiver is served by a central transceiver, for example, a base station, of the wireless communication system, wherein the transceiver is configured to operate in LTE V2X mode 3, NR V2X mode 1 or D2D mode 1 in which scheduling of resources for the communication with the at least one other transceiver is performed by the central transceiver.

In embodiments, the transceiver is configured to operate in LTE V2X Mode 4, NR V2X mode 2 or D2D mode 2, wherein the transceiver is configured to schedule resources for the sidelink communication autonomously.

In embodiments, the transceiver is configured to operate using carrier aggregation.

Further embodiments provide a transceiver for a wireless communication system, wherein the transceiver is configured to communicate with at least one other transceiver of the wireless communication system using sidelink resource pools of the wireless communication system, wherein the transceiver is configured to transmit a data packet on one of the sidelink resource pools of the wireless communication system to the other transceiver of the wireless communication system, wherein the transceiver is configured to, if a PPPR value associated with said data packet or with data contained in said data packet indicates a high reliability, to re-transmit said data packet at least once

on another sidelink resource pool of the sidelink resource pools of the wireless communication system,
or, in case of carrier aggregation, on another component carrier,
or on the same resource pool of the sidelink resource pools of the wireless communication system, but on different carriers.

Further embodiments provide a method for transmitting data packets in a wireless communication system between at least two transceivers communicating with each other using sidelink resource pools [e.g., mode 3 resource pool, mode 4 resource pool, shared resource pool, unshared resource pool or exceptional resource pool] of the wireless communication system. The method comprises a step of transmitting a data packet on one of the sidelink resource pools of the wireless communication system to the other transceiver of the wireless communication system. Further, the method comprises a step of re-transmitting said data packet at least once on another sidelink resource pool of the sidelink resource pools of the wireless communication system, if a PPPR value associated with said data packet or with data contained in said data packet indicates a high reliability [of said data packet].

Further embodiments provide a method for transmitting data packets in a wireless communication system between at least two transceivers communicating with each other. The method comprises a step of transmitting a data packet on a component carrier to the other transceiver of the wireless communication system. Further, the method comprises a step of re-transmitting said data packet at least once on at least one other component carrier, if a PPPR value associated with said data packet or with data contained in said data packet indicates a high reliability.

Further embodiments provide a method for transmitting data packets in a wireless communication system between at least two transceivers communicating with each other using sidelink resource pools of the wireless communication system. The method comprises a step of transmitting a data packet on one of the sidelink resource pools of the wireless communication system to the other transceiver of the wireless communication system. Further, the method comprises a step of re-transmitting said data packet, if a PPPR value associated with said data packet or with data contained in said data packet indicates a high reliability, at least once

Further embodiments provide a high priority data handling considering the required reliability for packet duplication on shared/unshared/exceptional resource pools by using PPPR.

Further embodiments use PPPR information for network slicing.

Further embodiments use the PPPR value to allow resource reservation in the consecutive resource pool by adding pseudo data in the current resource pool (SCI).

Since Rel-13, ProSe per packet priority (PPPP) has been defined for maintaining QoS in V2X. The application layer sets the priority for every V2X messages and passes this to the lower layers. The MAC layer then does the logical channel prioritization and maps the logical channels to transport channels based on the priorities. The PPPP takes into account the latency required both in eNB and the UE. Recently, in order to maintain and support the stringent requirements of the advanced use cases ProSe per packet reliability (PPPR) has been defined. With PPPR the reliability can now be taken into account for satisfying the defined requirement between 90% to 99.999%.

Embodiments include:

o Using transmission pools for duplicating packets by taking into account the PPPR information∘ In case of a (e.g., LTE V2X) mode 3 based UE, the PPPR information can be provided to the eNB by the UE for resource reservation.∘ In case of (e.g., LTE V2X) mode 4 based UE, the UE can either do sensing for allocating the resources or a grant-free access according to the PPPR or any combination of PPPR and CBR.∘ Packets with the low PPPR (i.e. requesting high reliability) can then be duplicated on the shared resource pool or in the same mode but on different carriers (if the UE supports CA).∘ During a handover or a resource reselection or even during normal operation (if allowed), if low PPPR and / or low PPPP value messages occur (demanding high reliability and low latency) then the exceptional pool can be used for packet duplication plus the last (pre)configured resource pool.
∘ A mapping for each network slice demanding a defined latency and / or reliability to a PPPP and / or PPPR value, respectively. This way the RAN can ensure the best fitting handling to ensure the demanded latency and reliability for the individual network slice.
∘ Allowing resource reservation restricted to high reliability requests (i.e. low PPPR values) in the consecutive resource pool by adding pseudo data in the current resource pool.

Embodiments provide a mechanism to

o Enhance the existing QoS by using new schemes based on the PPPR both in layer 2&3.

Embodiments contribute to

∘ Enhancing the QoS in the RAN by using new approaches based on the PPPR to guarantee the required reliability
∘ The use of priority schemes for assisting packet duplication in V2X.
∘ the use of the PPPR/PPPP to assess packet sharing between resource pool for Mode 3 and Mode 4, i.e., ∘ When PPPR threshold is reached, perform packet duplication on the shared resources∘ If PPPP threshold is reached, transmit different packets on the selected pools
∘ Enhancing the QoS for network slices by mapping the slice specific latency and reliability requirements to the PPPP and PPPR, respectively and to ensure the most appropriate processing in RAN to fulfill the requirements.

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

Fig. 1: shows a schematic representation of an example of a wireless communication system;
Fig. 2: is a schematic representation of a cell, like cell 1061 in Fig. 1, having two distinct overlaid networks, the networks comprising a macro cell network including the macro cell 1061, and a small cell network;
Fig. 3: shows a schematic representation of a situation in which UEs directly communicating with each other are in coverage of a base station;
Fig. 4: shows a scenario in which UEs directly communicating with each other are not are not in coverage of a base station, i.e., are not connected to a base station;
Fig. 5a: shows a schematic block diagram of a transceiver for a wireless communication network, according to an embodiment of the present invention;
Fig. 5b: shows a schematic diagram of an example of a duplication scheme for packet 1 (P1) with highest reliability (lowest PPPR);
Fig. 6: shows a schematic diagram of an input for the decision on packet duplication;
Fig. 7: shows a schematic diagram of mapping of network slices to PPPP / PPPR for RAB priority handling;
Fig. 8: shows a flowchart of a method for transmitting data packets in a wireless communication system between at least two transceivers communicating with each other using sidelink resource pools, according to an embodiment of the present invention,
Fig. 9: shows a flowchart of a method for transmitting data packets in a wireless communication system between at least two transceivers communicating with each other using sidelink resource pools, according to a further embodiment of the present invention,
Fig. 10: shows a flowchart of a method for transmitting data packets in a wireless communication system between at least two transceivers communicating with each other using sidelink resource pools, according to a further embodiment of the present invention, and
Fig. 11: 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.

Fig. 5a shows a schematic block diagram of a transceiver 109₁ (e.g., a UE of a device or vehicle) of a wireless communication system 100, according to an embodiment of the present invention. The transceiver 109₁ is configured to communicate 111₁₂ with at least one other transceiver 109₂ of the wireless communication system 100 using sidelink resource pools of the wireless communication system 100.

Thereby, the transceiver 109₁ can be configured to transmit a data packet on one of the sidelink resource pools of the wireless communication system 100 to the other transceiver 109₂ of the wireless communication system 100, wherein the transceiver 109₁ can be configured to, if a PPPR value associated with said data packet or with data contained in said data packet indicates a high reliability, to re-transmit said data packet at least once

on another sidelink resource pool of the sidelink resource pools of the wireless communication system 100,
or on the same resource pool of the sidelink resource pools of the wireless communication system, but on different carriers.

In case of carrier aggregation (CA), the transceiver 109₁ also (e.g., alternatively or additionally) can be configured to transmit the data packet on a component carrier (e.g., a first component carrier) to the other transceiver 109₂ of the wireless communication system 100, wherein the transceiver can be configured to, if a PPPR value associated with said data packet or with data contained in said data packet indicates a high reliability, to re-transmit said data packet at least once on at least one other component carrier (e.g., a second component carrier different from the first component carrier).

In embodiments, the transceiver 109₁ can be configured to retransmit said data packet at least once, if the PPPR value indicates a reliability (or priority) that is equal to or higher than a predefined reliability or threshold.

Note that, in some communication standards, a PPPR value of 1 may indicate the highest reliability (or priority), wherein a PPPR value of 8 may indicate the lowest priority.

In this case, the transceiver 109₁ can be configured to retransmit said data packet at least once, if the PPPR value is equal to or smaller than the predefined reliability or threshold, such as, for example, 4 (or 3, or 2, or 1). Naturally, also other predefined reliability values or thresholds may apply in dependence on the employed communication standard.

For example, in case of 3GPP TS23.285. the predefined reliability values or thresholds can be 1 to 8.

As indicated in Fig. 5a by way of example, the communication system 100 optionally may comprise a base station, such as gNB or eNB. Thereby, the transceiver 109₁ and ,e.g., also the other transceiver 109₂ can be configured to communicate 111₁ and 111₂ with the base station, when the transceivers 109₁ and 109₂ are in-coverage of the base station. The transceivers 109₁ and 109₂ (or at least one of the transceivers 109₁ and 109₂) also could be out-of-coverage of the base station. In both cases, i.e. in coverage mode and in out-of-coverage mode, the transceiver 109₁ can be configured to communicate directly (= sidelink communication) with the other transceiver 109₂ of the wireless communication system 100, e.g., using a sidelink resource pool of the wireless communication system.

In dependence on the employed wireless communication standard, the in-coverage mode can be referred to as LTE V2X mode 3 or NR V2X mode 1 or D2D mode 1, wherein the out-of-coverage mode can be referred to as V2X mode 4 or NR V2X mode 2 or D2D mode 2.

Subsequently, embodiments of the transceiver 109₁ are described in further detail. Thereby, in the following description, it is primarily made reference to a communication standard in which the in-coverage and out-of-coverage modes are referred to as LTE V2X modes 3 and 4, respectively, to explain the functionality of the transceiver 109₁ in the corresponding in-coverage and out-of-coverage modes. Naturally, the following description does also apply to other wireless communication standards in which the in-coverage and out-of-coverage modes are referred to as, for example, NR V2X mode 1 and NR V2X mode 2, or D2D mode 1 and D2D mode 2, respectively.

The idea is specifically related to V2X services demanding highly reliable data transmission. High reliability is indicated by the newly introduced PPPR.

Currently neither the range nor the mappings of the PPPR value to the requested reliability are finally defined. It is assumed that the same setting may apply as for the PPPP for the given description. However, if the final PPPR definition would be different, the description would need to be read using the final definition.

The PPPR (based on PPPP) would thus range from 1 to 8, where 1 indicated the highest reliability and 8 respectively, the lowest reliability.

The most common approach to improve the reliability is packet duplication, which is already defined for V2X. However, the idea of how to interpret the PPPR as well as the scheme for packet duplication based on the PPPR are no readily defined and therefore invented as described below.

Embodiment 1

Embodiments provide high priority data handling considering the required reliability for packet duplication on shared/unshared/exceptional resource pools by using PPPR.

During the currently ongoing Rel. 15 V2X specification one major topic is the definition of resource pool sharing between mode 3 and mode 4. During the last RAN2#101 meeting it was agreed that mode 3 UEs are allowed to share Mode 4 UE resource pools. Prerequisite for the mode 3 UEs is the sensing of the mode 4 resource pools prior to data transmission to reduce the risk of interfering with Mode 4 UE data transmission.

Fig. 5b shows a schematic diagram of an example of a duplication scheme for packet 1 (P1) with highest reliability (lowest PPPR).

In detail, Fig. 5b shows in a diagram a transmission of a data packet 300 on a sidelink resource pool 302₁ of the wireless communication system, wherein the data packet 300 is retransmitted on another resource pool 302₂ of the wireless communication system. Thereby, the ordinate denotes the frequency and the abscissa the time. As shown in Fig. 5b, the data packet 300 can be re-transmitted one or two times on the other resource pool 302₂. Retransmissions of the data packet are indicated in Fig. 5b with reference numerals 300(1) and 300(2).

As indicated in Fig. 5b, embodiments use the shared resource pools for packet duplications 300(2) and 300(3) for V2X services demanding high reliability indicated by the PPPR.

If high reliability is indicated for V2X data transmission on the sidelink, the duplicated packets 300(2) and 300(3) could be transmitted on the shared or any type of unshared resource pool. In detail the idea includes for resource pool use:

1. In case of a mode 3 UE 109₁ and high reliability (indicated by the PPPR), the mode 3 UE 109₁ could transmit the data 300 on resource pool 1 (302₁) in Fig. 5b (e.g. the mode 3 resource pool) and the duplicated packet 300(2) or 200(3) in addition on the resource pool 2 (3022) in Fig. 5b (e.g. the shared resource pool)).
2. In case of a mode 4 UE 109₁ and high reliability (indicated by the PPPR), the mode 4 UE 109₁ could transmit the data 300 on the resource pool 1 (302₁) in Fig. 5b (e.g. the mode 4 resource pool) and the duplicated packet 300(1) or 300(2) in addition on the resource pool 2 (302₂) in Fig. 5b (e.g. the shared resource pool)
3. Either mode 3 or mode 4, in case of RLF/no-sensing information available or handover, after high reliability indication (indicated by the PPPR) threshold is triggered, the UE 109₁ selects to duplicate resources transmitted on the legacy exceptional resource pool (say resource pool 1 (300₁) in Fig. 5b) on a (pre)configured resources or last used resources (say resource pool 2 (300₂) in Fig. 5b).
4. Either mode 3 or mode 4, in case of carrier aggregation (CA), after high reliability indication (indicated by the PPPR) threshold is triggered, the UE 109₁ selects to duplicate resources transmitted on component carrier #i (CC-i) (say resource pool 1 (302₁) in Fig. 5b) on another CC-ii (say resource pool 2 (302₂) in Fig. 5b) or more CC and more pools; if - and only if - carrier aggregation is possible
5. The duplicated data packet(s) 300(1) and 200(2) could be transmitted either on
- the shared resource pool or
- the exceptional pool
- on the associated mode 3 / 4 resource pool or
- on any combination of the shared, the associated mode 3 or 4 and / or the exceptional resource pool one or multiple times.

The following table describes all possible scenarios for resource pool 1 and 2 in Fig. 5b:

Scenario	Resource Pool 1	Resource Pool 2
Mode 3 share Mode 4 resources	Mode 3	Mode 4	Original data transmission on RP of Mode 3 and duplication happens on Mode 4
Mode 4 share Mode 3 resources	Mode 4	Mode 3	Original data transmission on RP of Mode 4 and duplication happens on Mode 3
RLF/no-sensing information available/hand over	Exceptional Resource Pool	Any available (previously used) resource pool or the ITS frequency band	Data transmission of duplicated resources may be altered by the availability of resource pool 2, e.g., based on sensing or previous CBR values
Carrier aggregation	Main/previously used CC	Secondary or more CCs

Fig. 6 shows a schematic diagram of an input for the decision on packet duplication.

In detail, the idea includes for the packet duplication scheme:

1. The decision on duplicated multiple transmissions 300(2) and 300(3) depend on the PPPR value (representing the requested reliability) and may also consider in addition the channel load (Fig. 6). The channel load could be deduced from the SL-CBR (SL-CBR = sidelink channel busy ratio).
2. In case both the PPPP and SL-CBR are considered, the packet duplication decision could be: IF SL-CBR > SL-CBR-threshold) IF (PPPR > PPPR-threshold) duplicate packet(s);
3. Optional, depending on PPPR or SL-CBR & PPPR combination, a multiplication factor may be selected to transmit the same packet 300, 300(2) and 300(3) multiple times as given by the multiplication factor
4. In case the packet 300 is transmitted more than one time, there could be a fixed offset using a periodic transmission for the next packet transmission 300(2) and 300(3) or random bursts for packet transmission (see Fig. 5b)
5. The duplicated packet 300(2), 300(3) could be sent on the shared pool either
- In the same period as the "original" packet 300 (which implies that sensing might not yet be performed). This could be applicable in case low latency is indicated e.g. by a low PPPP.
- Deferred in the current or next secondary resource pool by a defined or random offset.
- In one of the consecutive secondary resource pools, this may apply if low latency is not required. This could ensure the use of the sensing mechanism to possibly avoid interfering with other UEs 109₂ data transmission (and thus, increase the probability for successful data transmission).
6. How to decide on packet duplication / multiplication based on the PPPR or the PPPR / CL-CBR combination could either be hardcoded or configurable. One example for a configurable threshold based mapping is explained in this list (see item 2.). Additionally, a SL_CBR-PPPR table may apply [2] - similar to the SL-CBR-PPPP-TxConfigList information element for the PPPP to identify whether packet duplication should be performed. Using this list also the information, how often the packets should be transmitted, could be derived. A freely configurable or pre-defined or hard-coded table could be used to provide the mapping of the PPPR value to the packet duplication. Note: in mode 3 the packet duplication will be controlled by the base station using e.g. either RRC signaling or MAC CE (control element) or both of them.

Embodiment 2

In embodiments, the PPPR information is used for network slicing.

From Rel 15 onwards also the new concept of network slicing applies for the RAN.

Fig. 7 shows a schematic diagram of mapping of network slices to PPPP / PPPR for RAB (Radio Access Bearer) priority handling.

Each network slice typically represents a service, e.g. mobile broadband or V2X with a defined set of parameters. The detailed handling for network slices in RAN is not yet defined.

To ensure the demanded latency and reliability for each network slice, the requested latency / reliability could be mapped for each network slice to a PPPP and PPPR value, respectively.

This could be applied at least for any V2X related service slice, but may not be limited to it.

Using either the already defined mechanisms for the PPPP as well as the new schemes for the PPPR (as proposed in embodiment 1 and 2) or any combination of the 2 schemes, each network slice could be processed in the RAN in a way to ensure meeting the requested reliability and latency.

How to map each network slice to the PPPP and / or PPPR could either be hardcoded or configurable.

Either a freely configurable or pre-defined or hard-coded table could be used to provide this mapping.
Or thresholds could be used to for the defined latency / reliability per service slice to map to the best fitting PPPP and / or PPPR, respectively.

Embodiment 3

In embodiments, the PPPR value is used to allow resource reservation in the consecutive resource pool by adding pseudo data in the current resource pool (SCI).

In addition to packet duplication, high reliability (indicated by low PPPR) could also be ensured by resource reservation of mode 4 UEs in the next resource pool.

The idea is here to add pseudo data in the mode 4 resource pool (e.g. to the SCI), to indicate resource pool usage for sensing mode 3 UEs (trying to use the mode 4 resource pool for sharing) as well as other mode 4 UEs.

As a result, the sensing UEs will not transmit data in the consecutive mode 4 resource pool. Thus, the mode 4 UE adding pseudo data (e.g. in the SCI) will increase the reliability for critical (highly reliable) in the consecutive resource pool, i.e. increase the probability of successful data transmission avoiding collision with data packets from other mode 3 or 4 UEs.

However, the mechanism could be strongly limited to very high reliability requesting services (low PPPR), which requires the transmission of defined data (e.g. positioning or further important details in case of emergency) to avoid wasting of resources.

Embodiments described herein can be implemented, for example, in V2X, D2D, mMTC, URLLC, and critical communication.

Fig. 8 shows a flowchart of a method 400 for transmitting data packets in a wireless communication system between at least two transceivers communicating with each other using sidelink resource pools (e.g., mode 3 resource pool, mode 4 resource pool, shared resource pool, unshared resource pool or exceptional resource pool) of the wireless communication system. The method 400 comprises a step 402 of transmitting a data packet on one of the sidelink resource pools of the wireless communication system to the other transceiver of the wireless communication system. Further, the method 400 comprises a step 404 of re-transmitting said data packet at least once on another sidelink resource pool of the sidelink resource pools of the wireless communication system, if a PPPR value associated with said data packet or with data contained in said data packet indicates a high reliability [of said data packet].

Fig. 9 shows a flowchart of a method 410 for transmitting data packets in a wireless communication system between at least two transceivers communicating with each other. The method 410 comprises a step 412 of transmitting a data packet on a component carrier to the other transceiver of the wireless communication system. Further, the method 410 comprises a step 414 of re-transmitting said data packet at least once on at least one other component carrier, if a PPPR value associated with said data packet or with data contained in said data packet indicates a high reliability.

Fig. 10 shows a flowchart of a method 420 for transmitting data packets in a wireless communication system between at least two transceivers communicating with each other using sidelink resource pools of the wireless communication system. The method 420 comprises a step 422 of transmitting a data packet on one of the sidelink resource pools of the wireless communication system to the other transceiver of the wireless communication system. Further, the method 420 comprises a step 424 of re-transmitting said data packet, if a PPPR value associated with said data packet or with data contained in said data packet indicates a high reliability, at least once

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. 11 illustrates an example of a computer system 350. The units or modules as well as the steps of the methods performed by these units may execute on one or more computer systems 350. The computer system 350 includes one or more processors 352, like a special purpose or a general purpose digital signal processor. The processor 352 is connected to a communication infrastructure 354, like a bus or a network. The computer system 350 includes a main memory 356, e.g., a random access memory (RAM), and a secondary memory 358, e.g., a hard disk drive and/or a removable storage drive. The secondary memory 358 may allow computer programs or other instructions to be loaded into the computer system 350. The computer system 350 may further include a communications interface 360 to allow software and data to be transferred between computer system 350 and external devices. The communication may be in the form 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 362.

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 350. The computer programs, also referred to as computer control logic, are stored in main memory 356 and/or secondary memory 358. Computer programs may also be received via the communications interface 360. The computer program, when executed, enables the computer system 350 to implement the present invention. In particular, the computer program, when executed, enables processor 352 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 350. Where the disclosure is implemented using software, the software may be stored in a computer program product and loaded into computer system 350 using a removable storage drive, an interface, like communications interface 360.

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.

List of References

[1] 3GPP TS 36.213 Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures; V14.5.0
[2] 3GPP TS 36.331 Evolved Universal Terrestrial Radio Access (E-UTRA) - Radio Resource Control (RRC); V14
[3] 3GPP TS 36.211 Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation, v 14.3.0
[4] 3GPP TS 36.212 Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding, v 14.3.0
[5] 3GPP TS 36.321 Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification, v 14.3.0
[6] EP 3 273 634 A1 Improved support of Quality of Service for V2X Transmissions
[7] TDoc R2-18xxxx: Email discussion report on [101#34][LTE/5GC] Slicing, (ongoing), planned for WG2 #101Bis meeting, April 2018
[8] 3GPP TR 23.285 Architecture enhancements for V2X services; V15.1.0
[9] 3GPP TS 36.300 Packet Data Convergence Protocol (PDCP) specification; V15.3.0
[10] TDoc R2-18xxxx: draft Report from [101#72][LTE/V2X] Packet duplication, (ongoing), planned for WG2 #101Bis meeting, April 2018
[11] 3GPP TS 36.323 Packet Data Convergence Protocol (PDCP) specification, V15.1.0
[12] 3GPP TS 36.321 Medium Access Control (MAC) protocol specification, V15.3.0
[13] 3GPP TS 38.885 Study on NR Vehicle-to-Everything (V2X), V2.0.0
[14] 3GPP TS 23.501 System architecture for the 5G System (5GS)
[15] 3GPP TR 23.786 Study on architecture enhancements for the Evolved Packet System (EPS) and the 5G System (5GS) to support advanced V2X services
[16] 3GPP TS 23.287 Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services
[17] MOTOROLA MOBILITY ET AL: "Solution for Key Issue #4: Re-use PPPP mechanism for enhanced V2X",3GPP DRAFT; S2-182161_5G_QOS_SUPPORT, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE,vol. SA WG2, no. Montreal, Canada; 20180226 - 2018030220 February 2018 (2018-02-20), XP051408687, Retrieved from the Internet:URL:http://www.3gpp.org/ftp/tsg%5Fsa/WG2%5FArch/TSGS2%5F126%5FM ontreal/Docs/[retrieved on 2018-02-20]
[18] ERICSSON: "Packet duplication for PC5",3GPP DRAFT; R2-1803525 -PACKET DUPLICATION FOR PC5, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIAANTIPOLIS CEDEX ; FRANCE,vol. RAN WG2, no. Athens, Greece; 20180226 - 2018030216 February 2018 (2018-02-16), XP051400563, Retrieved from the Internet: URL: http://www.3gpp.org/ftp/tsg%5Fran/WG2%5FRL2/TSGR2%5F101/Docs/[retrieved on 2018-02-16]

List of Abbreviations

BS: Base Station
CBR: Channel Busy Ratio
D2D: Device-to-Device
EN: Emergency Notification
EP: Exceptional Pool
eNB: Evolved Node B (base station)
gNB: Next generation Node B (base station)
FDM: Frequency Division Multiplexing
LTE: Long-Term Evolution
PC5: Interface using the Sidelink Channel for D2D communication
PPPP: ProSe per packet priority
PPPR: ProSe per packet reliability
PRB: Physical Resource Block
ProSe: Proximity Services
RA: Resource Allocation
SCI: Sidelink Control Information
SL: Sidelink
sTTI: Short Transmission Time Interval
TDM: Time Division Multiplexing
TDMA: Time Division Multiple Access
UE: User Entity (User Terminal or User Equipment)
URLLC: Ultra-Reliable Low-Latency Communication
V2V: Vehicle-to-vehicle
V2I: Vehicle-to-infrastructure
V2P: Vehicle-to-pedestrian
V2N: Vehicle-to-network
V2X: Vehicle-to-everything, i.e., V2V, V2I, V2P, V2N

Claims

A transceiver (109₁) for a wireless communication system (100),
wherein the transceiver (109₁) is configured to communicate with at least one other transceiver (109₂) of the wireless communication system (100) using sidelink resource pools (302₁,302₂) of the wireless communication system (100),

wherein the transceiver (109₁) is configured to transmit a data packet (300) on one of the sidelink resource pools (302₁,302₂) of the wireless communication system (100) to the other transceiver (109₂) of the wireless communication system (100),

wherein the transceiver (109₁) is configured to, if a PPPR value associated with said data packet (300) or with data contained in said data packet (300) indicates a high reliability, to re-transmit said data packet (300) at least once (300(2),300(3))
- on another sidelink resource pool (302₂) of the sidelink resource pools (302₁,302₂) of the wireless communication system (100),

- or on at least one other component carrier,

- or on the same resource pool of the sidelink resource pools (302₁,302₂) of the wireless communication system (100), but on different carriers.
The transceiver (109₁) according to the preceding claim, wherein a number of re-transmissions of said data packet (300) depends on the PPPR value.
The transceiver (109₁) according to one of the preceding claims, wherein the transceiver (109₁) is configured to obtain the PPPR value associated with said data packet (300) or with the data contained in said data packet (300).
The transceiver (109₁) according to one of the preceding claims, wherein the sidelink resource pools (302₁,302₂) of the wireless communication system (100) are at least two out of a mode 3 resource pool, a mode 4 resource pool, a shared resource pool, an unshared resource pool or an exceptional resource pool.
The transceiver (109₁) according to one of the preceding claims,
wherein the PPPR value ranges from 1 to 8;

wherein a PPPR value of 1 indicates the highest reliability and a PPPR value of 8 indicates the lowest reliability.
The transceiver (109₁) according to one of the preceding claims, wherein the transceiver (109₁) is configured to retransmit said data packet (300) at least once (300(2),300(3)), if the PPPR value exceeds a predefined threshold.
The transceiver (109₁) according to one of the preceding claims, wherein the transceiver (109₁) is configured to retransmit said data packet (300) at least once (300(2),300(3)), if the PPPR value indicates a reliability that is equal to or higher than a predefined reliability or threshold.
The transceiver (109₁) according to one of the preceding claims 1 to 7,
wherein the transceiver (109₁) is served by a central transceiver, for example, a base station, of the wireless communication system (100), wherein the transceiver (109₁) is configured to operate in V2X Mode 3, in which scheduling of resources for the communication with the at least one other transceiver (109₂) is performed by the central transceiver,

wherein the transceiver (109₁) is configured to transmit the data packet (300) on a V2X mode 3 resource pool of the sidelink resource pools (302₁,302₂) of the wireless communication system (100), and

wherein the transceiver (109₁) is configured to re-transmit the data packet (300) at least once (300(3),300(3)) on a V2X mode 4 resource pool, a shared resource pool, anunshared resource pool or an exceptional resource pool of the sidelink resource pools of the wireless communication system.
The transceiver (109₁) according to one of the preceding claims 1 to 7,
wherein the transceiver (109₁) is served by a central transceiver, for example, a base station, of the wireless communication system (200), wherein the transceiver (109₁) is configured to operate in NR V2X mode 1, in which scheduling of resources for the communication with the at least one other transceiver (109₂) is performed by the central transceiver,

wherein the transceiver (109₁) is configured to transmit the data packet (300) on a NR V2X mode 1 resource pool of the sidelink resource pools of the wireless communication system, and

wherein the transceiver (109₁) is configured to re-transmit the data packet (300) at least once (300(2),300(3)) on another or the same NR V2X mode 1 resource pool, a NR V2X mode 2 resource pool, a shared resource pool, an unshared resource pool or an exceptional resource pool of the sidelink resource pools of the wireless communication system.
The transceiver (109₁) according to one of the preceding claims 1 to 7,
wherein the transceiver (109₁) is served by a central transceiver, for example, a base station, of the wireless communication system (100), wherein the transceiver (109₁) is configured to operate in D2D mode 1, in which scheduling of resources for the communication with the at least one other transceiver (109₂) is performed by the central transceiver,

wherein the transceiver (109₁) is configured to transmit the data packet (300) on a D2D mode 1 resource pool of the sidelink resource pools of the wireless communication system, and

wherein the transceiver (109₁) is configured to re-transmit the data packet (300) at least once (300(2),300(3)) on another or the same D2D mode 1 resource pool, a D2D mode 2 resource pool, a shared resource pool, an unshared resource pool or an exceptional resource pool of the sidelink resource pools of the wireless communication system.
The transceiver (109₁) according to one of the preceding claims 1 to 7,
wherein the transceiver (109₁) is configured to operate in V2X Mode 4, wherein the transceiver (109₁) is configured to schedule resources for the sidelink communication autonomously;

wherein the transceiver (109₁) is configured to transmit the data packet (300) on a V2X mode 4 resource pool of the sidelink resource pools (302₁,302₂) of the wireless communication system (100), and

wherein the transceiver (109₁) is configured to re-transmit the data packet (300) at least once on a V2X mode 3 resource pool, a shared resource pool, an unshared resource pool or an exceptional resource pool of the sidelink resource pools of the wireless communication system.
The transceiver (109₁) according to one of the preceding claims 1 to 7,
wherein the transceiver (109₁) is configured to operate in NR V2X Mode 2, wherein the transceiver (109₁) is configured to schedule resources for the sidelink communication autonomously;

wherein the transceiver (109₁) is configured to transmit the data packet (300) on a NR V2X mode 2 resource pool of the sidelink resource pools (302₁,302₂) of the wireless communication system (100), and

wherein the transceiver (109₁) is configured to re-transmit the data packet (300) at least once (300(2),300(3)) on another or the same NR V2X mode 2 resource pool, a NR V2X mode 1 resource pool, a shared resource pool, an unshared resource pool or an exceptional resource pool of the sidelink resource pools of the wireless communication system.
The transceiver (109₁) according to one of the preceding claims 1 to 7,
wherein the transceiver (109₁) is configured to operate in D2D Mode 2, wherein the transceiver (109₁) is configured to schedule resources for the sidelink communication autonomously;

wherein the transceiver (109₁) is configured to transmit the data packet on a D2D mode 2 resource pool of the sidelink resource pools (302₁,302₂) of the wireless communication system (100), and

wherein the transceiver (109₁) is configured to re-transmit the data packet (300) at least once (300(2),300(3)) on another or the same D2D mode 2 resource pool, a D2D mode 1 resource pool, a shared resource pool, an unshared resource pool or an exceptional resource pool of the sidelink resource pools of the wireless communication system.
The transceiver (109₁) according to one of the preceding claims, wherein the transceiver (109₁) is configured to, in case RLF/no-sensing information or handover is available, to transmit said data packet (300) on an exceptional resource pool of the sidelink resource pools of the wireless communication system (100), and to re-transmit said data packet at least once on a previously used resource pool of the sidelink resource pools of the wireless communication system (100).
A method (400) for transmitting data packets in a wireless communication system (100) between at least two transceivers (109₁,109₂) communicating with each other using sidelink resource pools (302₁,302₂) of the wireless communication system (100), the method comprising:
transmitting (402) a data packet (300) on one of the sidelink resource pools (302₁,302₂) of the wireless communication system (100) to the other transceiver (109₂) of the wireless communication system (100); and

re-transmitting (404) said data packet (300), if a PPPR value associated with said data packet or with data contained in said data packet indicates a high reliability, at least once (300(2),300(3))
- on another sidelink resource pool of the sidelink resource pools (302₁,302₂) of the wireless communication system (100),

- or on at least one other component carrier,

- or on the same resource pool of the sidelink resource pools (302₁,302₂) of the wireless communication system (100), but on different carriers.
Computer program for performing the method according to claim 15, when running on a computer or microprocessor.