SIDELINE: QUALITY OF SERVICE INFORMATION

TECHNICAL FIELD

The present invention relates to the field of mobile communication and to ensuring quality of service (QoS). In particular, the present invention relates to sidelink mobile communication and, more particularly, to vehicle to anything (V2X) services.

BACKGROUND

In the prior art, there are several types of V2X services, e.g.“broadcast periodic” (Common Awareness Messages (CAM)) or“non-periodic” applications (Decentralized Environmental Notification Messages (DENM)), or“session-based” V2X services (Cooperative Lane Merging (CLM), Cooperative Collision Avoidance (CCA), Cooperative Sensing, etc.) with different delay, capacity and reliability requirements as well as with different transmission modes (i.e. broadcast, multicast, unicast). Sidelink vehicle to vehicle (V2V) communication has demanding key performance indicators for many types of V2X services, especially safety and advanced driving. Thus, there is a need for complete QoS support in new radio (NR) sidelink, including QoS monitoring for 5G V2V broadcast/multicast/unicast transmission to support the demanded KPIs.

According to 3GPP TS 22.186, there is a need for optimizing multicast and unicast communication between user equipments (UEs) to support the demanding communication requirements, which many V2X use cases have (cf. 3GPP TS 22.186: The 3GPP system shall be able to optimize the communication between UEs supporting V2X application belonging to the same group and in proximity.)

NR V2X sidelink communication in particular needs to support a complete QoS framework including QoS parameters such as latency, reliability, priority, bit rate, etc. That is, in the field of sidelink communication, and in particular in the field of V2X, there is a need for a sidelink QoS feedback mechanism, which enables a UE to measure and report QoS metrics which the UE actually experiences in sidelink communication, as part of a sidelink QoS framework.

In long term evolution (LTE) V2X, there is no mechanism of QoS monitoring and feedback in sidelink communication. In current sidelink QoS frameworks (ProSe Per- Packet Priority (PPPP) / ProSe Per-Packet Reliability (PPPR) based), there is no monitoring or consideration of sidelink QoS information of broadcast/multicast transmissions (cf. 3GPP TS 23.285).

The existing Channel Busy Ratio (CBR) reporting mechanism may not be sufficient from a QoS perspective, as it can only indicate a rough channel occupation status but cannot directly indicate the actual QoS experienced in sidelink or allow a direct comparison between the QoS actually experienced by a UE and the NR V2X QoS requirements specified for the respective eV2X scenarios (cf. 3GPP TS 36.214).

Uu-based reporting/monitoring means schemes are not useful to know QoS experienced by users in PC5-based multicast/broadcast (cf. 3GPP TS 36.331). These means, e.g. Hybrid Automatic Repeat Request (HARQ) ACKs, are not sent to a base station (BS) in PC5 (thus Uu unicast signaling is not useful). Compared to Uu multicast/broadcast, in PC5, the Block Error Ratio (BLER) reporting scheme should not consider Multicast Broadcase Single Frequency Network (MBSFN) areas and Multicast Channel (MCH) channels, but to provide range-related information and distinguish between different transmitters.

That is, in view of the above-mentioned drawbacks of the prior art, there is a need for a mechanism for enabling sidelink QoS.

SUMMARY

In view of the above-mentioned problems and disadvantages, the present invention aims to improve the conventional sidelink communication. The present invention has the object to provide a sidelink device and method for providing sidelink QoS information, as well as a corresponding sidelink control device and method for providing sidelink QoS metrics.

The present invention in particular allows for optimizing sidelink communication (e.g. V2X communication) and for guaranteeing reliable sidelink communication, and if necessary, providing feedback to a network for potential adjustment of a QoS related configuration and/or policy.

In other words, an important aspect of the present invention is a way to enable sidelink QoS monitoring and feedback, in particular for V2X services, considering unicast, multicast and broadcast sidelink communications. According to the invention, a sidelink control device can enable sidelink QoS monitoring with or without a prior request from a UE or an application entity. The sidelink control device can configure sidelink QoS monitoring at the sidelink device, according to a type of a service (e.g. a V2X service), based on sidelink QoS metrics and monitoring goals. In addition, a sidelink device, and in particular a vehicle, can monitor and report sidelink QoS related information and/or sidelink QoS metrics to the sidelink control device, in particular based on a configuration received from the network. The present invention enables that a sidelink QoS metric can be calculated either at the sidelink control device, which is collecting QoS related information and/or sidelink QoS metrics from sidelink devices, or directly at the sidelink device.

Further, notifications of calculated sidelink QoS metrics, collected and/or processed by the sidelink control device, can be transmitted to sidelink devices, application entities or other network entities for different purposes (e.g. sidelink re-configuration, communication optimization, or application adaptation).

At least three types of sidelink QoS feedback (that can be combined) - which require different configurations, reporting and calculations - are supported by the present invention: session based sidelink QoS, location/area based sidelink QoS, and distance/range based sidelink QoS. These three types of QoS feedback for NR sidelink - which are optional features of the sidelink device according to the present invention - are described in the following in more detail:

Session based sidelink QoS:

QoS monitoring can be activated during session establishment of sidelink V2V Communication. A sidelink control device can define QoS metrics that should be monitored, and IDs of vehicles of a certain session. The sidelink devices (e.g. vehicles) of a certain session report sidelink QoS information to the sidelink control device.

Location/Area based sidelink QoS:

A sidelink control device can define areas where sidelink QoS monitoring is required. The sidelink control device can provide location/area configuration to the sidelink device together with QoS Metrics that should monitored. Sidelink devices (e.g. vehicles) that drive in the defined area/location can report sidelink QoS information with location information to the sidelink control device.

Distance/Range based Sidelink QoS:

A sidelink control device can define a range or a series of ranges according to which specific QoS metrics should be reported. Sidelink devices (e.g. vehicles) can report QoS information to the sidelink control device (e.g. for V2V communications) within specific ranges/distances (e.g. wherein the transmitting sidelink control device is the reference point).

All information that is provided by the sidelink control device to the sidelink device in the above three examples can also be preconfigured in the sidelink device.

Again, in different words, the present invention introduces a measurement and reporting framework for sidelink QoS management. The sidelink QoS feedback lifecycle according to the present invention may consist of the following steps:

- A sidelink control device can enable and configures sidelink QoS monitoring at a sidelink device, (e.g. a vehicle, according to a V2X service and communication optimization goals). - Sidelink devices monitor and report, based on the configuration received by the network.

- Notifications of calculated QoS metrics, collected and/or processed by the sidelink control device, could then be transmitted to a UE (e.g. for application layer adaptations), or a radio access network (RAN) or other core network (CN) nodes (e.g. for V2X optimization), or a RAN, (e.g. to decide sidelink re-configuration).

The sidelink QoS monitoring optionally could be periodic, or on-demand, or event- driven (e.g. based on a threshold value-change, or a location change).

A first aspect of the present invention provides a sidelink device for providing sidelink, quality of service, QoS, information, the sidelink device configured to obtain the sidelink QoS information based on a pre-configuration (e.g., during initial attachment, initial connection to an application/mobility/control server etc.) and/or a measurement request and/or connection establishment configuration, wherein the measurement request is obtained by from at least one of a network device; an operator-independent device; a sidelink device; and to provide information based on the sidelink QoS information to at least one of a network device; an operator-independent device; a sidelink device. The measurement request could be a dedicated message or part of another message sent by a network device, e.g., Radio Resource Control (RRC) reconfiguration message, session/service/connection establishment response message etc.

This is beneficial, since a predefined level of sidelink QoS can be maintained and guaranteed. Further, it provides the ability to monitor QoS for broadcast in a geographical region or system-wide, to optimize a system performance. Also, the sidelink QoS metric can be signaled/notified to further sidelink devices which may be useful to their performance (e.g. for communication layer adaptation, or even application layer adaptation). Further, the ability to monitor the QoS of a specific user for broadcast/multicast transmissions can be provided, in order to correct deviations from a QoS requested by that user. In addition, the ability to monitor the QoS for e.g. broadcast/multicast/unicast from all the users or a subset of them is provided, to correct deviations from a target performance. According to an alternative realization, the sidelink device may be configured to obtain the sidelink QoS information based on a connection establishment configuration, in particular a message obtained by the sidelink device when a connection is being established, wherein the connection is established between two or more sidelink devices; and to provide information based on the sidelink QoS information to at least one of a network device; an operator-independent device; a sidelink device. The connection establishment could be conducted with dedicated sidelink control plane or user plane signaling, e.g., RRC, PC5-S ProSe, and/or with the support of a network device and/or with the support of an operator-independent device.

The connection establishment may also include a link establishment and/or a sidelink bearer establishment.

The connection establishment may also refers to session establishment, service establishment, etc.

In a further implementation form of the first aspect, the connection establishment configuration can include information to monitor, by a sidelink device, sidelink communication. The information may be implemented by certain instructions.

In an implementation form of the first aspect, the sidelink device can be at least one of: a vehicle, a bicycle, a mobile communication device, Internet of Things (IoT) device, industrial device, roadside infrastructure, in particular a traffic light, a bridge, a camera, etc.

In a further implementation form of the first aspect, the network device can be a RAN device, in particular a base station, and/or a core network device. The network device can be an operator-independent device.

The network device may also be referred to as sidelink control device. However, the sidelink control device can also be another sidelink device. In a further implementation form of the first aspect, the information which is provided based on the sidelink QoS information can be also the sidelink QoS information as such.

In a further implementation form of the first aspect, the measurement request and/or the connection establishment configuration can relate to a service that is operated by the sidelink device.

This ensures that sidelink QoS information can be monitored based on a specific service, which allows for optimizing performance and reliability of that service.

In a further implementation form of the first aspect, the sidelink QoS information can be obtained based on sidelink communication, in particular multicast, unicast, and/or broadcast sidelink communication that is transmitted, received, and/or observed at the sidelink device.

This ensures that the sidelink device allows obtaining sidelink QoS information based on several types of sidelink communication.

In a further implementation form of the first aspect, the measurement request and/or the connection establishment configuration can indicate which resources or attributes of sidelink communication are to be monitored.

In a further implementation form of the first aspect, the sidelink device can be configured to obtain the sidelink QoS information based on the sidelink communication by monitoring the sidelink communication.

In a further implementation form of the first aspect, the sidelink device can be configured to, based on the measurement request and/or the connection establishment configuration, monitor the sidelink communication periodically, on-demand, or event- driven. This ensures that several types of monitoring can be configured, based on a user or provider need, to ensure that QoS is monitored, however only in a desired case, which helps to save resources. In a further implementation form of the first aspect, in the periodic case, the monitoring can be performed in predefined intervals.

In a further implementation form of the first aspect, in the on-demand case, the monitoring can be performed upon request, e.g. signaled in the measurement request, e.g. by a sidelink control device.

In a further implementation form of the first aspect, in the event-driven case, the monitoring can be performed when a predefined value exceeds or falls below a predefined threshold.

In a further implementation form of the first aspect, the sidelink device can be further configured to obtain, based on the sidelink QoS information and based on the pre configuration and/or the measurement request and/or the connection establishment configuration, a sidelink QoS metric, and transmit the sidelink QoS metric.

This ensures that the sidelink QoS metric also can be calculated in the sidelink device, thereby saving resources of the sidelink control device.

In a further implementation form of the first aspect, a sidelink QoS metric can include at least one of:

- a PRR: Packet Reception Ration of Unicast/Multicast/Broadcast (e.g. RAN calculated)

- a PIR: Packet Inter-Reception of Unicast/Multicast/Broadcast (e.g. UE Calculated)

- a Sidelink Packet Delay Budget

- a Sidelink bit rate

- a Sidelink packet error rate

- a Sidelink data rate In a further implementation form of the first aspect, a sidelink QoS metric could be calculated:

- Either at the sidelink device (e.g. PIR). In this case the sidelink device can report the sidelink QoS metric to a sidelink control device. In addition, the sidelink control device (e.g. a network/RAN) using individual QoS reporting has the capability to provide broader views, e.g. group QoS, or area QoS, statistics.

- Or at the sidelink control device (e.g. the network/RAN), based on reporting of the sidelink device (e.g. PRR).

In a further implementation form of the first aspect, the pre-configuration and/or the measurement request and/or the connection establishment configuration can include one or more identifier, ID, of one or more sidelink devices, and the sidelink device can be configured to obtain the sidelink QoS information based on the ID.

This allows for a flexible way to obtain sidelink QoS information based on a user or provider need, i.e. by signaling of IDs.

In a further implementation form of the first aspect, the sidelink devices indicated by the one or more ID can in particular relate to a certain sidelink session.

In a further implementation form of the first aspect, the pre-configuration and/or the measurement request and/or the connection establishment configuration can include information regarding one or more service flow identifiers associated to respective one or more service flows, and/or one or more link identifiers associated to respective one or more links, and/or one or more bearer identifiers associated to respective one or more bearers, and the sidelink device can be configured to obtain the sidelink QoS information based on the one or more service flow identifiers or one or more link identifiers or one or more bearer identifiers.

This allows for a flexible way to obtain sidelink QoS information based on a user or provider need, i.e. by signaling a service flow identifier.

In a further implementation form of the first aspect, the service flow identifier and/or sidelink radio bearer identifier and/or link identifier can in particular relate to a certain service and the sidelink devices involved in it as transmitting devices and/or receiving devices and/or as both.

In a further implementation form of the first aspect, the pre-configuration and/or the measurement request and/or the connection establishment configuration can include information regarding a geographic location, and the sidelink device can be configured to obtain the sidelink QoS information based on the geographic location.

This allows for a flexible way to obtain sidelink QoS information based on a user or provider need, i.e. by signaling a geographic location.

In a further implementation form of the first aspect, the geographic location can be the location of a sidelink device, in particular the location of this device and/or the location of another device, the location of a base station, etc.

In a further implementation form of the first aspect, the pre-configuration and/or the measurement request and/or the connection establishment configuration can include information regarding a geographic distance, and the sidelink device can be configured to obtain the sidelink QoS information based on the geographic distance.

This allows for a flexible way to obtain sidelink QoS information based on a user or provider need, i.e. by signaling a geographic distance.

In a further implementation form of the first aspect, the geographic distance can be a distance between the sidelink device and another sidelink device which is considered for obtaining sidelink QoS information.

A second aspect of the present invention provides a method for providing sidelink, quality of service, QoS, information, the method comprising the steps of obtaining, by the sidelink device, the sidelink QoS information based on a pre-configuration and/or a measurement request and/or a connection establishment configuration, wherein the measurement request is obtained from at least one of a network device; an operator- independent device; a sidelink device; and of providing information, by the sidelink device, based on the sidelink QoS information to at least one of a network device; an operator-independent device; a sidelink device.

According to an alternative realization, the sidelink device may configured to obtain the sidelink QoS information based on a connection establishment configuration, in particular a message obtained by the sidelink device when a connection is being established, wherein the connection is established between two or more sidelink devices; and to provide information based on the sidelink QoS information to at least one of a network device; an operator-independent device; a sidelink device. The connection establishment could be conducted with dedicated sidelink control plane or user plane signaling, e.g., RRC, PC5-S ProSe, and/or with the support of a network device and/or with the support of an operator- independent device.

The connection establishment may also include a link establishment and/or a sidelink bearer establishment.

The connection establishment may also refers to session establishment, service establishment, etc.

In a further implementation form of the first aspect, the connection establishment configuration can include information to monitor, by a sidelink device, sidelink communication. The information may be implemented by certain instructions.

In an implementation form of the second aspect, the network device can be a RAN device, in particular a base station, and/or a core network device. The network device can be an operator-independent device.

The network device may also be referred to as sidelink control device. However, the sidelink control device can also be another sidelink device.

In an implementation form of the second aspect, the information which is provided based on the sidelink QoS information can be also the sidelink QoS information as such. In an implementation form of the second aspect, the measurement request and/or the connection establishment configuration can relate to a service that is operated by the sidelink device.

In a further implementation form of the second aspect, the sidelink QoS information can be obtained based on sidelink communication, in particular multicast, unicast, and/or broadcast sidelink communication that is transmitted, received, and/or observed at the sidelink device.

In a further implementation form of the second aspect, the measurement request and/or the connection establishment configuration can indicate which resources or attributes of sidelink communication are to be monitored.

In a further implementation form of the second aspect, the method further can include obtaining, by the sidelink device, the sidelink QoS information based on the sidelink communication by monitoring the sidelink communication.

In a further implementation form of the second aspect, the method further can include monitoring, by the sidelink device, based on the measurement request and/or the connection establishment configuration, the sidelink communication periodically, on- demand, or event-driven.

In a further implementation form of the second aspect, in the periodic case, the monitoring can be performed in predefined intervals.

In a further implementation form of the second aspect, in the on-demand case, the monitoring can be performed upon request, e.g. signaled in the measurement request.

In a further implementation form of the second aspect, in the event-driven case, the monitoring can be performed when a predefined value exceeds or falls below a predefined threshold.

In a further implementation form of the second aspect, the method further can include obtaining, by the sidelink device, based on the sidelink QoS information and based on the pre-configuration and/or the measurement request and/or the connection establishment configuration, a sidelink QoS metric, and transmit the sidelink QoS metric.

In a further implementation form of the second aspect, a sidelink QoS metric can include at least one of:

- a PRR: Packet Reception Ratio of Unicast/Multicast/Broadcast (e.g. RAN calculated)

- a PIR: Packet Inter-Reception (e.g. UE Calculated) of Unicast/Multicast/Broadcast

- a Sidelink Packet Delay Budget

- a Sidelink bit rate.

- a Sidelink packet error rate

- a Sidelink data rate

In a further implementation form of the second aspect, a sidelink QoS metric could be calculated:

- Either at the sidelink device (e.g. PIR). In this case the sidelink device can report the sidelink QoS metric to a sidelink control device. In addition, the sidelink control device (e.g. a network/RAN) using individual QoS reporting has the capability to provide broader views, e.g. group QoS, or area QoS, statistics.

- Or at the sidelink control device (e.g. the network/RAN), based on reporting of the sidelink device (e.g. PRR).

In a further implementation form of the second aspect, the pre-configuration and/or the measurement request and/or the connection establishment configuration can include one or more identifier, ID, of one or more sidelink devices, and the method can further include obtaining, by the sidelink device, the sidelink QoS information based on the ID.

In a further implementation form of the second aspect, the sidelink devices indicated by the one or more ID can in particular relate to a certain sidelink session.

In a further implementation form of the second aspect, the pre-configuration and/or the measurement request and/or the connection establishment configuration can include information regarding one or more service flow identifiers associated to respective one or more service flows, and/or one or more link identifiers associated to respective one or more links, and/or one or more bearer identifiers associated to respective one or more bearers, and the sidelink device can be configured to obtain the sidelink QoS information based on the one or more service flow identifiers or one or more link identifiers or one or more bearer identifiers.

This allows for a flexible way to obtain sidelink QoS information based on a user or provider need, i.e. by signaling a service flow identifier. ln a further implementation form of the second aspect, the service flow identifier and/or sidelink radio bearer identifier and/or link identifier can in particular relate to a certain service and the sidelink devices involved in it as transmitting devices and/or receiving devices and/or as both. ln a further implementation form of the second aspect, the pre-configuration and/or the measurement request and/or the connection establishment configuration can include information regarding a geographic location, and the method can further include obtaining, by the sidelink device, the sidelink QoS information based on the geographic location. ln a further implementation form of the second aspect, the geographic location can be the location of a sidelink device, in particular the location of this device and/or the location of another device, the location of a base station, etc. ln a further implementation form of the second aspect, the pre-configuration and/or the measurement request and/or the connection establishment configuration can include information regarding a geographic distance, and the method can further include obtaining, by the sidelink device, the sidelink QoS information based on the geographic distance.

In a further implementation form of the second aspect, the geographic distance can be a distance between the sidelink device and another sidelink device which is considered for obtaining sidelink QoS information. The second aspect and its implementation forms include the same advantages as the first aspect and its implementation forms.

A third aspect of the present invention provides a sidelink control device for providing a sidelink, sidelink, quality of service, QoS, metric, the sidelink control device configured to, in particular obtain a measurement request and/or a connection establishment request and/or transmit the measurement request and/or a connection establishment configuration; receive or obtain sidelink QoS information based on the measurement request and/or the connection establishment configuration; and obtain the sidelink QoS metric based on the received sidelink QoS information.

This is beneficial, as it allows to configure the sidelink device by the sidelink control device, based on a measurement request, and to receive sidelink QoS information according to the request, and provide a sidelink QoS metric accordingly.

The connection establishment may also include a link establishment and/or a sidelink bearer establishment.

The connection establishment may also refers to session establishment, service establishment, etc.

In an implementation form of the third aspect, the sidelink control device can be a base station or another core network entity e.g., vehicle to anything (V2X) control function (CF). The sidelink control device can also be a network device, an operator- independent device, and/or a sidelink device.

In a further implementation form of the third aspect, the sidelink control device can be located in a radio access network, RAN, or in a core network, CN.

In a further implementation form of the third aspect, the measurement request and/or the connection establishment configuration can relate to a service, in particular a service operated by a sidelink device or by the sidelink control device. In a further implementation form of the third aspect, the measurement request and/or the connection establishment configuration can include instructions to monitor, by a sidelink device, sidelink communication periodically, on-demand, or event-driven.

In a further implementation form of the third aspect, the sidelink control device can be further configured to include a request for the sidelink QoS metric in the measurement request and/or the connection establishment configuration, and in particular to receive the sidelink QoS metric or information to obtain the sidelink QoS metric.

In a further implementation form of the third aspect, based on the information to obtain the sidelink QoS metric, the sidelink control device can calculate the metric on its own.

In a further implementation form of the third aspect, the measurement request and/or the connection establishment configuration can include one or more identifier, ID, of sidelink devices, wherein said sidelink devices in particular relate to a certain sidelink session.

In a further implementation form of the third aspect, the measurement request and/or the connection establishment configuration can include information regarding one or more service flow identifiers and/or one or more link identifiers and/or one or more bearer identifiers.

In a further implementation form of the third aspect, the measurement request and/or the connection establishment configuration can include information regarding a geographic location.

In a further implementation form of the third aspect, the measurement request and/or the connection establishment configuration can include information regarding a geographic distance.

In a further implementation form of the third aspect, the sidelink control device can be further configured to obtain information based on sidelink QoS information, and to provide information, based on said obtained information, to another sidelink device and/or another sidelink control device. The third aspect and its implementation forms include the same advantages as the first aspect and its implementation forms.

A fourth aspect of the present invention provides a method for providing a sidelink quality of service, QoS, metric, the method comprising the steps of, in particular obtaining, by a sidelink control device, a measurement request and/or a connection establishment request and/or transmitting, by the sidelink control device, the measurement request and/or a connection establishment configuration; receiving or obtaining, by the sidelink control device, sidelink QoS information based on the measurement request and/or the connection establishment configuration: and obtaining, by the sidelink control device, the sidelink QoS metric based on the received sidelink QoS information.

The connection establishment may also include a link establishment and/or a sidelink bearer establishment.

The connection establishment may also refers to session establishment, service establishment, etc.

In an implementation form of the fourth aspect, the sidelink control device can be a base station or another core network entity e.g., a vehicle to anything (V2X) control function (CF). The sidelink control device can also be a network device, an operator- independent device, or a sidelink device.

In a further implementation form of the fourth aspect, the sidelink control device can be located in a radio access network, RAN, or in a core network, CN.

In a further implementation form of the fourth aspect, the measurement request and/or the connection establishment configuration can relate to a service, in particular a service operated by a sidelink device or by the sidelink control device.

In a further implementation form of the fourth aspect, the measurement request and/or the connection establishment configuration can include instructions to monitor, by a sidelink device, sidelink communication periodically, on-demand, or event-driven. In a further implementation form of the fourth aspect, the method can further comprise including, by the sidelink control device, a request for the sidelink QoS metric in the measurement request and/or the connection establishment configuration, and in particular receiving, by the sidelink control device the sidelink QoS metric or information to obtain the sidelink QoS metric.

In a further implementation form of the fourth aspect, based on the information to obtain the sidelink QoS metric, the sidelink control device can calculate the metric on its own.

In a further implementation form of the fourth aspect, the measurement request and/or the connection establishment configuration can include one or more identifier, ID, of sidelink devices, wherein said sidelink devices in particular relate to a certain sidelink session.

In a further implementation form of the fourth aspect, the measurement request and/or the connection establishment configuration can include information regarding one or more service flow identifiers and/or one or more link identifiers and/or one or more bearer identifiers.

In a further implementation form of the fourth aspect, the measurement request and/or the connection establishment configuration can include information regarding a geographic location.

In a further implementation form of the fourth aspect, the measurement request and/or the connection establishment configuration can include information regarding a geographic distance.

In a further implementation form of the fourth aspect, the method further can include obtaining, by the sidelink control device, information based on sidelink QoS information, and to provide information, based on said obtained information, to another sidelink device and/or another sidelink control device. The fourth aspect and its implementation forms include the same advantages as the the first aspect and its implementation forms.

It has to be noted that all devices, elements, units and means described in the present application could be implemented in the software or hardware elements or any kind of combination thereof. All steps which are performed by the various entities described in the present application as well as the functionalities described to be performed by the various entities are intended to mean that the respective entity is adapted to or configured to perform the respective steps and functionalities. Even if, in the following description of specific embodiments, a specific functionality or step to be performed by external entities is not reflected in the description of a specific detailed element of that entity which performs that specific step or functionality, it should be clear for a skilled person that these methods and functionalities can be implemented in respective software or hardware elements, or any kind of combination thereof.

BRIEF DESCRIPTION OF DRAWINGS

The above-described aspects and implementation forms of the present invention will be explained in the following description of specific embodiments in relation to the enclosed drawings, in which

FIG. 1 shows a schematic view of a sidelink device according to an embodiment of the present invention.

FIG. 2 shows a schematic view of parameters that affect a monitoring configuration.

FIG. 3 shows a schematic view of modes of monitoring activation according to the present invention.

FIG. 4 shows a schematic view of an operating manner according to the present invention. FIG. 5 shows a schematic view of an operating manner according to the present invention.

FIG. 6 shows a schematic view of reporting information according to the present invention.

FIG. 7 shows a schematic view of sidelink QoS information report components according to the present invention. FIG. 8 shows a schematic view of inter-cell interaction for sidelink metrics calculation according to the present invention.

FIG. 9 shows a schematic view of core network calculation of sidelink QoS metrics according to the present invention.

FIG. 10 shows a schematic view of network case calculation of QoS metrics.

FIG. 11 shows a schematic view of a method according to an embodiment of the present invention.

FIG. 12 shows a schematic view of a sidelink control device according to an embodiment of the present invention.

FIG. 13 shows a schematic view of a method according to an embodiment of the present invention.

FIG. 14 shows a schematic view of an operating manner according to an embodiment of the present invention. DETAILED DESCRIPTION OF EMBODIMENTS

FIG. 1 shows a schematic view of a sidelink device 100 according to an embodiment of the present invention. The sidelink device 100 is for providing sidelink QoS information 101. To ensure this, the sidelink device 100 is configured to obtain the sidelink QoS information 101 based on a pre-configuration 102 and/or a measurement request 103 and/or a connection establishment configuration. The pre-configuration 102 can be pre-stored in the sidelink device 100 by any communication means and memory means available to the sidelink device 100. The measurement request 103 and/or a connection establishment configuration is obtained from at least one of a network device, an operator-independent device, a sidelink device. Such a device can e.g. be the sidelink control device 1200, which is going to be described in view of FIG.12 below. That is, the sidelink control device 1200 can e.g. be a network device, an operator- independent device, and/or a sidelink device.

To provide the sidelink QoS information 101, the sidelink device 100 is further configured to provide information 104 based on the sidelink QoS information 101 to at least one of a network device, an operator-independent device, a sidelink device. Again, this can be the sidelink control device 1200. The information 104 can also be the sidelink QoS information 101 as such.

The obtaining of the sidelink QoS information 101 can optionally be based on sidelink communication. In particular, to obtain the sidelink QoS information 101, the sidelink device 100 optionally can monitor any type of sidelink communication that is transmitted, received, and/or observed at the sidelink device 100. The sidelink communication optionally can e.g. be of a multicast, unicast, and/or broadcast type.

The sidelink device 100 can provide sidelink QoS information 101 to the sidelink control device 1200, so that the sidelink control devices 1200 determines sidelink QoS metrics from the sidelink QoS information 101. However, further optionally, the sidelink device 100 can also directly determine sidelink QoS metrics and provide them to the sidelink control device 1200. These sidelink control metrics can e.g. be determined according to the measurement request 103 that is received from the sidelink control device 1200 and/or based on a pre-configuration of the sidelink device 100 and/or a connection establishment configuration. As it is e.g. illustrated in view of FIG.2, different parameters can affect sidelink QoS and in particular V2V communication. Different sidelink services (in particular V2X services) and optimization goals require different sidelink QoS metrics to be monitored or calculated, and consequently information to be reported by the sidelink device 100. A sidelink control device 1200 can configure the reporting and feedback based on a type of a sidelink service (e.g. a V2X service) and a purpose of monitoring e.g. QoS notification, or prediction of QoS. FIG.2 presents parameters that affect a monitoring configuration (which is e.g. signaled in a measurement request 103 and/or a connection establishment configuration). The measurement request 103 and/or a connection establishment configuration therefore can be related to a specific service (e.g. a V2X service), that is operated by the sidelink device 100 and / or the sidelink control device 1200.

FIG. 3 shows a schematic view of modes of monitoring activation according to the present invention. As it is illustrated in particular in FIG. 3 A, 3B and 3C, the sidelink control device 1200 (e.g. a BS) can enable and configure sidelink QoS monitoring and reporting at the sidelink devices 100, 100’, considering a NR sidelink QoS metric to be calculated, a V2X service, a type of transmission (broadcast, unicast, multicast), and/or a type of feedback, e.g. relation of a sidelink device 100 to a sidelink session, to a target area, or a range from the sidelink device 100 to another device.

FIG. 3 also describes the general case of configuration of a sidelink device 100, 100’ by a sidelink control device 1200 (e.g. in a 5G system) for three alternative type of QoS feedback for sidelink communication: session-based sidelink QoS, location/area based sidelink QoS, distance/range based sidelink QoS.

For each one of the above types, a measurement request 103 message is sent by the sidelink control device 1200 with different parameters that configure the reporting at the sidelink devices 100, 100’. Distance/range based QoS can be also provided in the context of a session or at a specific location/area.

FIG. 4 describes a case in which a sidelink control device 1200 (e.g. a base station in a RAN) undertakes the interaction with sidelink devices 100, 100’, 100” and calculation or collection of sidelink QoS metrics. The first step involves the signaling to set sidelink QoS requirements for a service to enable QoS monitoring (i.e. the measurement request 103) and/or signaling connection establishment configuration. This can e.g. be done in the context of session establishment or dedicated signaling. The sidelink control device 1200 enables sidelink QoS monitoring (see box“Enable Sidelink QoS monitoring”) and configures the sidelink QoS monitoring and QoS related information reporting (e.g. each sidelink device 100, 100’, 100” may have a different Tx and Rx configuration) via measurement request 103 messages. The optional content of such messages is going to be described below. The sidelink devices 100, 100’, 100” send measurement reports with QoS related information 101, respectively information 104. The content depends on the type of QoS metric, service, or feedback type. The sidelink control device 1200 conducts QoS metric calculation/processing, based on the collected information. After this phase, the calculated QoS metrics could be reported to the sidelink devices 100, 100’, 100” or can be used by sidelink control device 1200 nodes for sidelink QoS management, optimization or notifications.

FIG. 5 describes the case that the configuration and/or calculation or collection of sidelink QoS metrics takes place at a V2X control function (CF). Any other 5G CN entity could be used instead of a V2X CF e.g. Session Management Function (SMF).

In particular, the sidelink control device 1200 can be implemented either by a BS (e.g. in a RAN or CN) alone, by a V2X CF alone, or by a combination of them. The sidelink control device 1200 can also be implemented by any other 5G entity or a combination of 5G entities.

In the following it is going to be described in detail, how a sidelink control device 1200 can configure monitoring and reporting of a sidelink device 100. This details in particular relate to a content of the measurement request 103 which is sent from the sidelink control device 1200 to the sidelink device 100.

The sidelink control device 1200 can configure the reporting policy of the sidelink device 100, based on a monitoring type (session based, area based, distance based) and a QoS metric (e.g., PRR, PIR, packet delay budget, bitrate, packer error rate). The reporting information parameters that can be configured by the sidelink control device 1200 are at least one of the following:

For transmitting information:

- V2X services considered (e.g. cooperative sensing, DENM)

- QoS metrics and parameters

For receiving information:

- Type of reporting (number of packets, timing, location)

For determining, whether the report aggregates packets received from all users, from a subset of them, or only from a specific user:

- Ranges of distances considered (one or multiple)

To configure the reporting, e.g. a RRC reporting policy / configuration signaling can be used that is provided per sidelink device 100, with the following information elements:

For reporting information configuration:

- Report config id (which can be an identifier of the configuration)

- Reporting periodicity (which can be a value in ms or indexes)

- Location area (which can be a zone or specific region where reporting is enabled)

- List of configured measurements

- Measurement id (which can be an id of this configured measurement)

- Service or metrics ids (which can be types of services or reporting types considered. Value“all” is possible.)

- V2X subchannels ids (which can be a sequence of subchannels considered. Value“all” is possible.)

- Trx config id (which can identify the UE transmitting QoS info configuration used)

- Rx config id (which can identifys the UE receiving QoS info configuration used)

- service flow identifiers (which can identify a specific service flow e.g., service type and/or involved UEs) - link identifiers

- connection identifiers

- bearer identifiers

For configuration of the transmitting info of the sidelink device 100:

- Trx config id (which can be an identifier of this configuration)

- Sps assumption [true/false] (wherein true means that transmitting info is not reported if the number of packets transmitted is equal to the number of semi-persistent allocated resources)

- Timing info config [all packets, none] (which can indicate if the generation time of each packet is included or not)

- Location info config [all packets, groups of packets in close positions, none] (which can indicate if location info is included for all measurements, some measurements in close positions or for not at all)

- Location delta (which means that, if“groups of packets in close positions” is selected above, location delta is the maximum distance between the packets grouped)

For configuration of receiving info of the sidelink device 100:

- Rx config id (which can be an identifier of this configuration)

- Transmitter ids (which can be a sequence of UEs IDS whose transmissions are considered. Value“all” is possible.)

- Timing info config [all packets, none] (which can indicate if the generation time of each packet is included or not)

- Edges for ranges of distances (which can be a sequence of increasing values. Value “inf’ is used to denote infinite value. Some possible values are, e.g. none, [0, inf], [0, 80] or [0, 20, 40, 80, inf].)

The configuration of transmitting and/or receiving info can optionally include service flow identifier and/or link identifier and/or connection identifier and/or bearer identifier to specify where exactly a specific configuration described above could be applied.

In view of FIG. 6, reporting of information from the sidelink device 100 to the sidelink control device 1200 is now going to be described. After the configuration of reporting to the sidelink device 100 (i.e. by means of the measurement request 103 and/or a connection establishment configuration), the sidelink device 100 reports sidelink QoS information 101, information 104 or sidelink QoS metrics to the sidelink control device 1200. For example, vehicles (i.e. sidelink devices 100) are configured by the network (i.e. the sidelink control device) to monitor and report sidelink QoS metrics or sidelink QoS information to the network (e.g. a BS). As it is illustrated in Fig. 6, in a communication system, each sidelink device 100, 100’, 100”, 100”’ can report to the sidelink control device 1200.

Sidelink QoS metrics that are monitored and calculated at the sidelink device (e.g. PIR), or sidelink QoS information monitored at the sidelink device 100 to enable calculation of sidelink QoS metrics at the sidelink control device 1200 (e.g. PRR calculation, sidelink multicast session PER/delay, requires reporting from different session nodes) can be reported to the sidelink control device 1200.

The sidelink QoS information report optionally can consist of two parts, as e.g. shown in FIG. 7:

a) QoS information of transmitting data (e.g. egress traffic) of a sidelink device b) QoS information of receiving data (e.g. ingress traffic) of a sidelink device

The contents of both parts are configurable, depending on selected QoS metrics, a feedback type, or a service type.

Both parts a) and b) can e.g. be included in the sidelink QoS information 101, in the information 104, or in sidelink QoS metrics, that are transmitted from the sidelink device 100 to the sidelink control device 1200.

The contents of a transmitting data QoS information report can be configured to include at least one of following:

- QoS metrics/parameter

- Parameter, e.g. a number of packets transmitted, egress bitrate

- Measure type, e.g. actual value or average value

- Service type (e.g. session-based V2X service/maneuver, CAM, DENM) - Timing information (e.g. list of generation times of packet transmitted)

- Location information, area of reporting (e.g. list of positions of packet transmitted)

- A list of positions, and for each item of the list the number of packets transmitted close to each position

- V2X subchannels (if report refers only to a subset of the V2X resource pools)

- Service flow identifier, link identifier, bearer identifier, connection identifier radio and/or channel information (e.g., CBR, received signal strength indicators, channel quality indicators, SL-RSRP, CSI etc).

The contents of receiving data QoS information report can be configured to include at least one of following:

- QoS metrics/parameter

- Parameter, e.g. a number of packets received, ingress bit rate, PIR, latency

- Measure type e.g. actual value or average value

- Service Type (e.g. session-based V2X service/maneuver, CAM, DENM)

- Timing information (e.g. list of generation times of packet received)

- Location information, area of reporting (e.g. list of positions of packet received, list of positions and monitored latency/PIR)

- Relevance distance / coverage range from Tx device

- V2X subchannels (if report refers only to a subset of the V2X resource pools)

- Service flow identifier, link identifier, bearer identifier, connection identifier

- radio and/or channel information (e.g., CBR, received signal strength indicators, channel quality indicators, SL-RSRP, CS1 etc).

Further, radio and/or channel information of transmitting data and receiving data QoS information could be used to estimate and/or calculate the sidelink QoS metrics. This could take place either at the sidelink control device based on received radio and/channel information or at the sidelink device. Additional QoS information could be used for the estimation and/or calculation of sidelink QoS metrics. ln view of F1G. 8 and F1G. 9 examples of inter-cell interaction for sidelink QoS metric calculation, and of core network calculation of sidelink QoS metric calculation are now going to be described. In many cases, sidelink devices 100 that communicate via sidelink will be attached at different cells/BSs. In this case, for the calculation of sidelink QoS metrics the BSs (i.e. the sidelink control devices 1200) have, as depicted in FIG.8, to exchange measurement reports and/or sidelink QoS metrics of the sidelink devices 100, 100’, 100”, 100”’ via Xn signaling or any other inter cell interface or via a core network function. The final QoS metric derivation from QoS related information reporting can be done by a BS (i.e. by the sidelink control device 1200).

According to another implementation, one or more UE IDs and/or one or more service flow identifiers and/or one or more link identifiers and/or one or more bearer identifiers and/or one or more connection identifiers could be used for the exchange of information between the cells/BSs.

Additionally, or alternatively, as it is shown in FIG. 9, a core network function can be involved that will collect measurement reports and/or sidelink QoS metrics from the sidelink devices 100 via control plane CN interfaces. A core entity undertakes the calculation of sidelink broadcast / sidelink QoS metrics (e.g. an AMF, V2X Control function), using the inputs that come from different BSs. The calculation results can be notified to these BSs.

According to another implementation, one or more UE IDs and/or one or more service flow identifiers and/or one or more link identifiers and/or one or more bearer identifiers and/or one or more connection identifiers could be used for the exchange of information between a core entity and the BSs.

In the following, a table of sidelink QoS metrics and information needed by a sidelink device 100 or by a sidelink control device 1200 to calculate each sidelink QoS metric, is presented. That is, each sidelink QoS metric shown in the table (in the leftmost column) can be included in the sidelink QoS metric that is calculated by the sidelink device 100 or by the sidelink control device 1200.

Further, the information which is required to calculate the sidelink QoS metric (indicated in the three rightmost columns of the table) can be obtained by the sidelink device 100 based on sidelink communication, e.g. by monitoring said sidelink communication (also, this information can also be directly obtained in the sidelink control device 1200). The obtained information can then be used in the sidelink device 100 to calculate the sidelink QoS metric or can be included in the sidelink QoS information 101 or in the information 104, where it is transmitted to the sidelink control device 1200 for calculation of the sidelink QoS metric in the sidelink control device 1200.

According to an example embodiment of the present invention, in the following section, calculation of PRR (based on the sidelink control device 1200) for 5G Sidelink broadcast/multicast QoS is going to be described. This section introduces Packet Reception Ratio (PRR) as a 5G sidelink QoS metric to monitor sidelink broadcast/multicast communication. It also provides methods that allow the network (i.e. the sidelink control device 1200) to calculate and maintain QoS metrics for multicast and broadcast sidelink communication among vehicles, located either at the RAN or at the Core Network.

Different options for PRR calculation can be used depending on the type of service and transmission mode:

- Option 1 : Average PRR for ranges of distances (broadcast).

- Option 2: Average PRR for a relevance area (broadcast).

- Option 3 : Per UE PRR for a relevance area (broadcast).

- Option 4: Average PER in a multicast group.

- Option 5: Per UE PER in a multicast group.

Each PRR option implies a different UE reporting configuration, and also a different calculation at the RAN is needed. An overview of the calculation procedure is e.g. shown in FIG. 10. As illustrated in FIG. 10, the following general steps are considered:

0) Configuration of UEs’ reporting to enable sidelink broadcast/multicast QoS monitoring.

1) Add to transmitted packets information about e.g. location of transmitting device and/or ID.

2) Reporting of info related to packets transmitted by the UE.

3) Check received packets and retrieve information about e.g. transmitting device and distance of transmission.

4) Reporting of info related to packets received by the UE.

5) Network Calculation of experienced QoS of sidelink V2V multicast/broadcast communications, according to PRR scheme selected.

6) Notification of calculated QoS (e.g. PRR) values to UEs for communication system optimization, application layer adaptations.

In an example embodiment of the present invention, it is now described how the receiving data information can be obtained via communication layer extensions: an optional method is determining how to monitor the information related to the received data packets by the reporting UE (i.e. by the sidelink device 100). In this sense the receiving data information can be obtained by each UE via:

- Application layer API: introduced at the UE convergence layer (between application layer and communication layer) to collect information at the receiver side for packets successfully transmitted. This option means that the APP layer of the receiver, after processing the received packets, may inform the communication layers through an API (e.g. convergence layer) about the number of application layer packets successfully (correctly and in due time) received indicating the distance from the transmitter of these packets. Alternatively, a service flow identifier (e.g., PFI in NR PC5, 3GPP Rel. 16) could be used to retrieve QoS information of an associated service flow at the application layer and/or the V2X layer of the receiver. The same also applies at the transmitter side.

- Communication layer header extensions: Other optional communication layer protocol head extensions are explained, for data packets exchanged via sidelink to allow the receiver side to collect information for the relevance area of packets successfully received. This option involves extending the headers of communication layer (user plane PC5 messages) so as to include location info of a transmitting device and/or ID (for instance, the service data adaptation protocol (SDAP) header). Besides, the same operations proposed for APP layer can be performed using communication layers.

Moreover, a service flow identifier (e.g., PFI in NR PC5, 3 GPP Rel. 16) and/or a link identifier and/or a bearer identifier could be used to retrieve QoS information from the application layer and/or the V2X layer of the receiver and/or the transmitter side. Also a service flow identifier (e.g., PFI in NR, 3GPP PC5 Rel. 16) and/or a link identifier and/or a bearer identifier could be used to retrieve QoS information from the communication layer of the receiver and/or the transmitter side.

FIG. 11 shows a schematic view of a method 1100 according to an embodiment of the present invention. The method 1100 is for providing sidelink QoS information 101 and comprises the following steps: The method 1100 comprises a first step of obtaining 1101, by a sidelink device 100, the sidelink QoS information 101 based on a pre-configuration 102 and/or a measurement request 103 and/or a connection establishment configuration, wherein the measurement request 103 and/or a connection establishment configuration is obtained from at least one of: a network device, an operator-independent device, a sidelink device.

The method 1100 comprises a second step of providing 1102, by the sidelink device 100, information 104 based on the sidelink QoS information 101 to at least one of: a network device, an operator-independent device, a sidelink device.

FIG. 12 shows a schematic view of a sidelink control device 1200 according to an embodiment of the present invention.

The sidelink control device 1200 is for providing a sidelink QoS metric 1201 and is configured to obtain a measurement request 1202 (to this end, it optionally includes all of the above described functionality regard a sidelink control device 1200). The sidelink control device 1200 is also configured to transmit the measurement request 1202 and/or a connection establishment configuration. The sidelink control device 1200 is further configured to receive sidelink QoS information 1203 based on the measurement request 1202 and/or a connection establishment configuration. Finally, the sidelink control device 1200 is configured to obtain the sidelink QoS metric 1201 based on the received sidelink QoS information 1203.

The measurement request 1202 that is transmitted by the sidelink control device 1200 is in particular the measurement request 103 that is obtained by the sidelink device 100.

The measurement request 1202 can be related to a specific service (e.g. a V2X service), that is operated by the sidelink device 100 and / or the sidelink control device 1200. The sidelink QoS information 1203 that is receive by the sidelink control device is the sidelink QoS information 101 or the information 104 that is transmitted by the sidelink device.

FIG. 13 shows a schematic view of a method 1300 according to an embodiment of the present invention. The method 1300 is for providing a sidelink QoS, metric 1201.

The method 1300 comprises the following steps: A first step of the method 1300 is obtaining 1301, by the sidelink control device 1200, a measurement request 1202. The method 1300 also comprises a step of transmitting 1302, by the sidelink control device 1200, the measurement request 1202. The method 1300 further comprises a step of receiving 1303, by the sidelink control device 1200, sidelink QoS information 1203 based on the measurement request 1202. The method 1300 comprises a last step of obtaining 1304, by the sidelink control device 1200, the sidelink QoS metric 1201 based on the received sidelink QoS information 1203.

FIG. 14 shows an example in which the calculation or collection of sidelink QoS metrics is based on the sidelink connection establishment configuration between the sidelink devices 100, 100’.

The application layer (e.g., V2X application layer) of sidelink device 100, after the triggering of an application service, may provide application requirements for the sidelink communication (e.g., PC5 QoS parameters and PFI) to the access stratum of the sidelink device 100. Then the sidelink device 100 triggers the Layer-2 link establishment procedure with sidelink device 100’. FIG. 14 shows a unicast link establishment example. This also applies to multicast and/or broadcast link establishments. During the link establishment procedure between the two sidelink devices 100, 100’, sidelink configuration parameters are exchanged between the sidelink control devices (100, 100’).

Using the connection establishment configuration, the sidelink devices 100 and 100’, can enable sidelink monitoring and configure measurement, monitoring and reporting of the sidelink communication between sidelink devices 100 and 100’. Sidelink QoS metrics that are monitored and calculated at the sidelink device, or sidelink QoS information monitored at the sidelink device 100 to enable calculation of sidelink QoS metrics (e.g. PRR, packet error rate, delay etc) can be reported to another sidelink device 100’ and/or the sidelink control device 1200. As it is illustrated in Fig. 14, each sidelink device (e.g., 100) can report sidelink QoS information 101, information 104 or sidelink QoS metrics to the other sidelink device (e.g., 100’) and/or the sidelink control device 1200. Also the sidelink control device 1200 can provide sidelink QoS metrics that are collected and/or processed and/or calculated to the sidelink control devices (100, 100’).

According to an embodiment of the present invention, for unicast, groupcast and broadcast sidelink (e.g., PC5) communication, the per-flow QoS model for sidelink QoS management could be applied. A sidelink QoS Flow is associated with a sidelink QoS rule that contains the sidelink QoS parameters (e.g., PQI, optionally range). Each sidelink QoS Flow has a PC5 QoS Flow Identifier (PFI). User Plane traffic with the same PFI receives the same traffic forwarding treatment (e.g. scheduling, admission threshold). In the case that different data packets may require different QoS treatments, the data packets shall be sent from the application layer (e.g., V2X layer) to the Access Stratum (AS) layer within PC5 QoS Flows identified by different PFIs.

A sidelink service can be established via PC5-S and/or RRC signaling and sidelink QoS slows are established. This means that activation of sidelink QoS monitoring could be realized upon or after the sidelink connection establishment (e.g., sidelink unicast link) and/or using information exchanged in the context of sidelink connection establishment and/or connection update. In this case service flow identifiers (e.g., PFIs) and/or link identifiers and/or bearer identifiers, or other flows identifiers may be used to configure sidelink QoS monitoring, and/or to obtain sidelink QoS metrics, QoS information, and/or to report sidelink QoS metrics and QoS information at sidelink control device and/or to a sidelink device.

More specifically, different configuration options could be considered. Through PC5-S exchanges for the establishment phase, both sides at PC5-S layer (i.e., UEs, sidelink devices) are aware of the PC5 QoS parameters and the PFIs of both sides. Thereinafter, with the establishment of the Sidelink Radio Bearers (SLRB), the Access Stratum (AS) of each sidelink device can map the SLRB ID with the corresponding QoS parameters and the PC5 QoS Flow (e.g., service flow identifiers, PFI), using RRC signaling. At the receiver side, data received over the established unicast link and the sidelink device can monitor the required QoS, by using the mapping between the SLRB ID and the service flows. The sidelink device that receives a packet, knows the SLRB ID that the packet traverses and the mapped PC5 QoS Flow (i.e., service flow identifier) as well as the corresponding QoS requirements at the AS. Based on the PC5-S and the PC5 RRC signalling the mapping between SLRB ID and QoS info (PFI, QoS requirements/parameters) is feasible. Hence, the receiving sidelink devices for each received data packet can check if the QoS requirements of the corresponding packet (at the specific SLRB ID) are met or not.

Alternatively, service flow identifiers (e.g., PFIs) and/or link identifiers, and/or bearer identifiers could be included in user plane data packets (e.g., added at the V2X layer headers, SDAP headers or any other header) of the transmitting sidelink device (e.g., UE). These identifiers can be used by the receiving device (e.g., UE) to check if the QoS requirements of the corresponding received data packet are met or not.

Information and configurations from the connection establishment (or update) could be used together with other configuration information that are pre-configured and/or obtained via a measurement request.

The sidelink connection establishment (e.g., or unicast link establishment) can take place using signaling either between two or more sidelink devices and/or with the support of a network entity (e.g., BS, core network entity, application server, cloud server etc),

In a further embodiment of the present invention, the network can configure the mapping of a PC5 QoS flow to SLRB. For the QoS flow which needs to be monitored, the network can configure this QoS flow to a DRB which only corresponds to this QoS flow, i.e. 1 : 1 mapping is used between the QoS flow which needs to be monitored and DRB, in this way, UE is easy to count the QoS metrics, i.e. data rate, delay and packet error rate. The present invention has been described in conjunction with various embodiments as examples as well as implementations. However, other variations can be understood and effected by those persons skilled in the art and practicing the claimed invention, from the studies of the drawings, this disclosure and the independent claims. In the claims as well as in the description the word“comprising” does not exclude other elements or steps and the indefinite article“a” or“an” does not exclude a plurality. A single element or other unit may fulfill the functions of several entities or items recited in the claims. The mere fact that certain measures are recited in the mutual different dependent claims does not indicate that a combination of these measures cannot be used in an advantageous implementation.