KR102412296B1 - Wireless device, wireless network node and method performed - Google Patents

Abstract

Embodiments herein relate to a method performed by a wireless network node (12) for handling communication between wireless devices via sidelinks in a wireless communication network. The wireless network node represents a set of one or more quality of service (QoS) requirements, each QoS requirement comprising a threshold value associated with a QoS characteristic, and the data satisfying each QoS requirement of the set of one or more QoS requirements. Configures a wireless device by indicating a mapping of one or more logical channel groups (LCGs) reserved for sidelink buffer status report (BSR) reporting.

Description

Wireless device, wireless network node and method performed

Embodiments herein relate to wireless devices, wireless network nodes, and methods performed in connection with wireless communications. In particular, embodiments herein relate to handling communication of wireless devices in a wireless communication network.

In a typical wireless communication network, a wireless device, also known as a wireless communication device, a mobile station, a station (STA) and/or a user equipment (UE), is connected to one or more cores via a Radio Access Network (RAN). It can communicate with core networks (CN). RAN covers a geographic area that is divided into service areas, also known as cells, each cell area served by a wireless network node, for example a Wi-Fi access point or a radio base station (RBS), which includes some In the network, it is also called, for example, NodeB, eNodeB or gNodeB. A cell is a geographic area over which radio coverage is provided by a radio network node. A wireless network node operates on a radio frequency to communicate via an air interface with a wireless device within range of the wireless network node. A wireless network node communicates with a wireless device via a downlink (DL), and the wireless device communicates with a wireless network node via an uplink (UL).

UMTS (Universal Mobile Telecommunications network) is a third generation (3G) communication network evolved from second generation (2G) Global System for Mobile Communications (GSM). A UMTS terrestrial radio access network (UTRAN) is essentially a RAN that uses wideband code division multiple access (WCDMA) and/or High Speed Packet Access (HSPA) for user equipment. In a forum known as the Third Generation Partnership Project (3GPP), telecommunication providers propose and agree standards for, for example, 3G networks, and explore improved data rates and wireless capacities and upcoming generation networks. In some RANs, as in UMTS, for example, several radio network nodes are connected to a radio network controller (RNC) or a base station controller, e.g. by landline or microwave. BSC), which oversees and coordinates the various activities of a plurality of wireless network nodes connected to these nodes. This type of connection is sometimes referred to as a backhaul connection. RNCs and BSCs are typically connected to one or more core networks.

The specification for an Evolved Packet System (EPS), also called a 4th generation (4G) network, has been completed within 3GPP, and this work continues in future 3GPP releases specifying, for example, 5th generation (5G) networks. . EPS includes an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as a Long Term Evolution (LTE) radio access network, and an Evolved Packet Core (EPC), also known as a System Architecture Evolution (SAE) core network. E-UTRAN/LTE is a variant of the 3GPP radio access network, where the radio network nodes are directly connected to the EPC core network rather than to the RNC. Generally, in E-UTRAN/LTE, the function of RNC is distributed between radio network nodes, for example eNodeBs of LTE and the core network. As such, the RAN of the EPS has an essentially "flat" architecture comprising radio network nodes directly connected to one or more core networks, ie these nodes are not connected to the RNC. To complement this, the E-UTRAN specification defines a direct interface between radio network nodes, and this interface is denoted as an X2 interface.

Due to new 5G technologies such as New Radio (NR), the use of very many transmit and receive antenna elements is attracting great attention as beamforming such as transmit-side and receive-side beamforming is available. Transmission-side beamforming means that the transmitter can amplify a signal transmitted in a selected direction while suppressing a signal transmitted in the other direction. Similarly, on the receiving side, the receiver can amplify a signal from a selected direction while suppressing unwanted signals from the other direction.

The 3GPP standard for communication is constantly being developed with different versions or releases. Rel. During 12, the LTE standard was extended with support for a device to device (D2D) feature, also referred to as a sidelink feature, targeting both commercial and public safety applications. Rel. 12 Some applications enabled by LTE are device discovery, where a wireless device broadcasts and detects a wireless device identity and a discovery message carrying the application identity to detect other wireless devices and associated applications. can detect the proximity of Another application consists of direct communication based on a direct terminated physical channel between wireless devices. In 3GPP, all these applications are defined under protection (umbrella) named ProSe (Proximity Services).

One potential extension of the ProSe framework consists in the support of Vehicle to Anything (V2x) communication, which includes any combination of direct communication between vehicles, pedestrians and infrastructure. V2x communication, when available, may use the network (NW) infrastructure, but at least basic V2x connectivity should be possible even when coverage is insufficient. Providing LTE-based V2x interfaces can be economically advantageous due to LTE's economies of scale, vehicle to infrastructure (V2I), and vehicle to pedestrians (V2P) compared to using dedicated V2x technology. ) and communication with the NW infrastructure, denoted as vehicle to vehicle (V2V) communication.

There are many research projects and field tests on connected vehicles in various countries or regions, including projects based on the use of existing cellular infrastructure.

V2x communication may carry both non-safety and safety information, where each application and service may be associated with a specific set of requirements in terms of, for example, latency, reliability, capacity, and the like. From an application point of view, V2x includes the following types of communication/service, see FIG. 1 .

V2V: It deals with communication between vehicles using V2V applications and is mainly broadcast based. V2V may be realized by direct communication between devices in each vehicle, or may be realized through an infrastructure such as a cellular network. An example of V2V is to repeatedly transmit a cooperative awareness message (CAM) with vehicle status information such as location, direction, and speed to other nearby vehicles, for example, every 100 ms-1 sec. Another example is to transmit a decentralized environmental notification message (DENM) that is an event-triggered message for warning the vehicle. These two examples are taken from the ETSI Intelligent Transport Systems (ITS) specification of V2x applications, which also specifies the conditions under which messages are generated. A key characteristic of V2V applications is the stringent requirements for latency, which can vary, for example, from 20 ms for pre-collision warning messages to 100 ms for other road safety services.

V2I: This includes communication between the vehicle and the RSU (Roadside Unit). RSUs are fixed transportation infrastructure entities that communicate with nearby vehicles. Examples of V2I include sending speed notifications from the RSU to the vehicle as well as queue information, collision risk alerts, and curve speed warnings. Due to the safety-related nature of V2I, delay requirements are similar to V2V requirements.

V2P: Use V2P applications to address communication between vehicles and vulnerable road users such as pedestrians. V2P typically occurs between separate vehicles and pedestrians, either directly or via an infrastructure such as a cellular network.

Vehicle to network (V2N): A V2N application is used to handle communication between a vehicle and a centralized application server or Intelligent Transportation System (ITS) traffic management center over an infrastructure such as a cellular network. One example is a false road condition warning that is sent to all vehicles in a large area, or traffic flow optimization where a V2N application suggests speed to a vehicle and adjusts traffic lights. Therefore, V2N messages should be controlled by a centralized entity, that is, a traffic management center, and provided to vehicles in a large area rather than a small area. Additionally, unlike V2V or V2I, latency requirements are more relaxed since they are not used for non-safety purposes in V2N, for example, typically a 1 second latency requirement is considered.

The aforementioned sidelink transmissions, also known as D2D transmissions or ProSe transmissions over an air interface called PC5 interface in the cellular spectrum, are described in Release Rel. It has been standardized in 3GPP since 12. 3GPP Rel. At 12, two different transmission modes were assigned to 3GPP. In one mode called mode-1, a wireless device in RRC_CONNECTED mode requests a D2D resource, and a wireless network node grants a resource through a Physical Downlink Control Channel (PDCCH) or dedicated signaling that transmits DL control information such as DCI5 (grant) In another mode, called mode-2, the wireless device uses system information block (SIB) signaling for transmission on a carrier other than the PCell (Primary Cell) or dedicated signaling for transmission on the PCell. Through the broadcast, a resource for transmission is autonomously selected from a pool of available resources provided by the broadcast. Thus, unlike the first operation (mode, ie, mode mode-1, the second operation (mode, ie, mode mode-2) may also be performed by the wireless device in RRC_IDLE mode, in some cases the wireless device out of coverage can also be performed by

Rel. At 14, the use of sidelink transmission is extended to the V2x domain. Rel. The original design of the sidelink physical layer of 12 aimed at a scenario in which a small number of wireless devices compete for the same physical resource in the spectrum to carry voice packets for mission critical push to talk (MCPTT) traffic, and the wireless devices mobility was assumed to be low. On the other hand, in V2x, sidelinks can cope with higher load scenarios, i.e. hundreds of cars potentially competing for physical resources, and high mobility of wireless devices to carry time or event triggered V2x messages such as CAM and DENM. should be able For this reason, 3GPP has discussed possible enhancements to the sidelink physical layer.

Rel. The first improvement specified in 14 is to introduce a new transmission mode called mode-3, which is similar to mode-1 in that it is a wireless network node that explicitly allocates sidelink resources to wireless devices. However, unlike mode-1, the wireless network node can semi-permanently configure the sidelink resource in the same way as Semi Persistent Scheduling (SPS), that is, the wireless network node, for example, for periodic transmission on a specific frequency resource. Allocate a sidelink grant.

A second improvement is to introduce so-called channel sensing and sensing aware wireless device autonomous resource allocation, which corresponds to a fourth mode called mode-4 transmission mode. Rel. 12 and Rel. 13 Unlike random resource selection, which is the basis of ProSe communication, V2V Rel. 14), the wireless device is expected to continuously detect the channel and search for resources in different parts of the spectrum with less interference. Such sensing aims to limit collisions between wireless devices.

In 3GPP, two types of sensing were considered.

수신된 전력에 기초한 센싱. 무선 디바이스는 특정 무선 자원 상에서 수신된 에너지를 측정한다.

Sensing based on received power. The wireless device measures the energy received on a particular radio resource.

o For example, based on these measurements, a wireless device is considered to be 'idle', i.e. whether its radio resources are being used by some other wireless device, i.e. 'busy' or not. to decide

o For example, a wireless device may use the measurement to estimate whether a transmitter is far away, eg, a weak signal, or near, eg, a strong signal.

패킷 콘텐츠에 기초한 센싱. 무선 디바이스는 패킷을 수신하여 이를 디코딩한다. 패킷으로부터 추출된 정보에 기초하여, 무선 디바이스는 무선 자원의 이용에 관한 일부 지식을 획득할 수 있다:

Sensing based on packet content. The wireless device receives the packet and decodes it. Based on the information extracted from the packet, the wireless device can obtain some knowledge about the use of radio resources:

o For example, by reading a scheduling assignment (SA) packet, the wireless device can know which radio resource is expecting data transmission and the priority level of the transmitter.

o For example, by reading a data packet, the wireless device can know the location of the transmitter, the identity (ID) of the transmitter, the type of transmitter, and the like.

In mode-4, the wireless device autonomously selects a transmission resource based on the detection result, but it is still possible for the wireless network node to signal some set of values that the wireless device is allowed to use for a particular transmission parameter. For example, for the number of physical resource blocks (PRBs) that the wireless device uses for transmission, the wireless network node may specify a minimum and maximum value, i.e., the wireless device may specify less than X values for transmission. Whether PRB or more than Y PRBs are not available and the wireless device can transmit; You can specify a maximum and minimum modulation and coding scheme (MCS), minimum and/or maximum transmit power, etc. that the wireless device can use. In other words, the wireless network node may limit the set of values that the wireless device may select for a particular transmission parameter. This set or limit on transmission parameters may be configured differently by the network for different wireless device conditions depending on, for example, wireless device speed or channel congestion conditions. Besides configuration by the wireless network node or the NW node in general, the set or limit may also be part of the pre-configuration. Pre-configuration may be used as an alternative to or as a complement to configuration by the wireless network node.

With respect to sidelink quality of service (QoS), it should be noted that each packet to be transmitted over the PC5 interface is indicated by a specific packet tag called PPPP (ProSe per packet priority) by the application layer. Each PPPP represents a priority assigned to a given sidelink packet by the application layer. In particular, each PPPP may assume a value of 1 to 8, where 1 represents the highest priority PPPP and 8 represents the lowest priority.

Depending on the PPPP assigned by the application layer, different RAN procedures apply. For example, for different PPPPs, different transmission parameters, eg, MCS, transmit power, number of PRBs, etc., may be applied by the wireless device according to the network configuration. PPPP can also be used to determine whether a particular pool or a particular carrier can be used depending on the interference or congestion situation experienced in the particular pool. In this way, a kind of admission control procedure based on PPPP can be performed, so that, for example, PPPP with higher priority must be transmitted on the least congested carrier or pool to increase the probability of correct reception. do.

At the MAC (medium access control) layer, the PPPP is mapped to a logical channel identity (LCID) by the wireless device for logical channel prioritization when building a MAC protocol data unit (PDU). . PPPP is also mapped to different logical channel groups (LCG) according to network configuration, and is used for sidelink (SL) buffer status report (BSR), so that a wireless network node can schedule a wireless device. When appropriate, an appropriate sidelink grant may be provided.

The air interface framework, such as the interface Uu quality of service (QoS) framework, is dependent on the data rate, e.g., Guarantee bit rate (GBR) or non-GBR, packet delay budget, reliability, i.e., the packet error rate ( It should be noted that different performance requirements such as packet error rate (PER) are associated with each quality class index (QCI). However, unlike the Uu QoS framework, up to the current Rel.14, performance requirements other than PPPP are not associated with sidelink packets. Therefore, there is no sidelink capability indicator other than PPPP in the current sidelink framework. This may limit the ability of the existing scheduling assignment procedure, for example for mode-3 and mode-4, to properly serve a given wireless device. In practice, PPPP exclusively indicates the priority at which a given packet must be served by the wireless network node scheduler for wireless network node-scheduler random access (RA) or by the wireless device for wireless device autonomous RA. . However, in some cases certain operations may be performed, for example configuring SL packet duplication over different SL carriers to increase the probability of correct reception, or a more conservative encoding ( It may be useful to know the reliability requirements of a given SL packet so that conservative encoding can be adopted. Similarly, if a high data rate is desired, a larger number of carriers may be used, or more aggressive encoding and larger bandwidth may be allocated.

Therefore, in the legacy sidelink framework, the wireless device reports the LCG associated with the PPPP of the packet currently in the wireless device SL buffer directly to the network of the SL BSR. As such, the network can only recognize the PPPP of packets in the SL buffer, and no indication of reliability, data rate or other performance requirements can be retrieved. Additionally, there is no signaling from the wireless network node to enable the wireless device to replicate packets.

It is an object of the present specification to provide a mechanism that enables device-to-device communication in a wireless communication network in an efficient manner.

According to an aspect, according to an embodiment of the present invention, this object is achieved by providing a method performed by a wireless network node for handling communication between wireless devices via sidelinks in a wireless communication network. The wireless network node represents a set of one or more quality of service (QoS) requirements, each QoS requirement comprising a threshold value associated with a QoS characteristic, and the data satisfying each QoS requirement of the set of one or more QoS requirements. It represents the mapping of one or more logical channel groups (LCGs) reserved for sidelink buffer status report (BSR) reporting. Accordingly, a wireless network node may configure a wireless device by indicating one or more sets of QoS. For each of these QoS of interest, the wireless network node may reserve one or more LCGs for BSR reporting of the sidelink. Thereafter, the wireless network node may receive an indication from the wireless device in the buffer status report, which indicates the QoS requirements or characteristics of the packet. An indication is associated with a logical channel. The wireless network node may then process the communication of the wireless device's sidelink in view of the received indication.

According to another aspect, according to an embodiment of the present invention, this object is achieved by providing a method performed by a wireless device for handling communication between wireless devices via a sidelink in a wireless communication network. The wireless device may configure, for example, from pre-configuration or reception, a set of one or more QoS requirements, each QoS requirement comprising a threshold value associated with a QoS characteristic, and each QoS requirement of the set of one or more QoS requirements. Configure mapping of one or more LCGs reserved for BSR reporting of sidelinks for data that satisfies Accordingly, the wireless device is configured with one or more sets of QoS, wherein for each of these QoS, one or more LCGs are reserved for BSR reporting for the sidelink. The wireless device may send an indication to the wireless network node in the buffer status report, which indication indicates QoS requirements or characteristics of the packet. An indication is associated with a logical channel.

Also provided herein is a computer program product comprising instructions that, when executed on at least one processor, cause the at least one processor to perform either of a method as performed by a wireless network node or a wireless device. Additionally, as described herein, store a computer program product comprising instructions that, when executed on at least one processor, cause the at least one processor to perform either of a method as performed by a wireless network node or a wireless device. A computer-readable storage medium is provided.

According to another aspect, according to an embodiment of the present invention, this object is achieved by providing a wireless network node that handles communication between wireless devices via sidelinks in a wireless communication network, wherein the wireless network node has one or more QoS configured to configure the wireless device by indicating a set of requirements, each QoS requirement being one reserved for BSR reporting of a sidelink for data that satisfies each QoS requirement of the one or more sets of QoS requirements By indicating the mapping of the LCG above, it includes a threshold value associated with QoS characteristics.

According to another aspect, according to an embodiment of the present invention, this object is achieved by providing a wireless device that handles communication between wireless devices via a sidelink in a wireless communication network. The wireless device may configure, from preconfiguration or reception, a set of one or more QoS requirements, each QoS requirement comprising a threshold value associated with a QoS characteristic, and a set of one or more QoS requirements that satisfy each of the set of QoS requirements. and configure mapping to the radio network node one or more LCGs reserved for BSR reporting of sidelinks for data.

Embodiments herein provide a method for a wireless device to report a plurality of indications, eg, sidelink QoS indicators such as data rate, reliability, latency, etc., to a wireless network node.

A wireless network node may have a tool to retrieve some SL QoS indicators other than just PPPP, so that an appropriate scheduling decision can be made, for example, the wireless network node is the SL for which the wireless device requires high reliability delivery. You can enable sidelink packet duplication when you have packets in the buffer, or you can enable one or more carriers depending on the data rate of the packets to be transmitted. Decisions about actual transmission parameters, eg, MCS, TX power, number of PRBs, etc. adopted by the wireless device, may also be affected. Accordingly, embodiments herein enable device-to-device communication in a wireless communication network in an efficient manner.

Hereinafter, embodiments will be described in more detail with reference to the accompanying drawings.
1 is a schematic diagram illustrating different vehicle communications.
2 is a schematic schematic diagram illustrating a wireless communication network according to an embodiment of the present specification.
3A shows a combined flowchart and signaling scheme according to an embodiment of the present specification.
3B illustrates a mapping between QoS and LCG in accordance with some embodiments herein.
3C illustrates the mapping of different QoS of packets to LCGs in accordance with some embodiments herein.
4 shows the mapping of LCGs to different sets of LCGs for different QoS characteristics.
5 shows group reporting in MAC CE.
6 shows a schematic flowchart illustrating a method performed by a wireless network node according to an embodiment of the present disclosure;
7 shows a schematic flow diagram illustrating a method performed by a wireless device according to an embodiment of the present disclosure;
8 is a block diagram illustrating a wireless network node according to an embodiment of the present specification.
9 is a block diagram illustrating a wireless device according to an embodiment of the present specification.
10 illustrates a communication network coupled to a host computer through an intermediate network in accordance with some embodiments.
11 illustrates a host computer communicating with a user equipment via a base station over a partial wireless connection in accordance with some embodiments.
12 illustrates a method implemented in a communication system including a host computer, a base station, and a user equipment in accordance with some embodiments.
13 illustrates a method implemented in a communication system including a host computer, a base station, and a user equipment in accordance with some embodiments.
14 illustrates a method implemented in a communication system including a host computer, a base station, and a user equipment in accordance with some embodiments.
15 illustrates a method implemented in a communication system including a host computer, a base station, and a user equipment in accordance with some embodiments.

BACKGROUND OF THE INVENTION Embodiments herein relate generally to wireless communication networks. 2 is a schematic schematic diagram showing a wireless communication network 1 . The wireless communication network 1 includes one or more RANs and one or more CNs. The wireless communication network 1 may use one or many different technologies. While the embodiments herein relate to recent technology trends of particular interest in the 5G context, the embodiments also relate to existing technologies such as, for example, LTE and Wideband Code Division Multiple Access (WCDMA). It is applicable to the further development of the wireless communication system of

In the wireless communication network 1, to communicate with each other via a sidelink, such as a device-to-device terminal in a vehicle, for example a mobile station, a non-access point (non-AP) STA, an STA, a user equipment and/or a wireless terminal. A configured wireless device, eg, wireless device 10 , and another or second wireless device 10 ′ may be configured to communicate from the NW, eg for V2x communication. A person skilled in the art will recognize that a “wireless device” is any terminal, wireless communication terminal, user equipment, NB-loT device, Machine Type Communication (MTC) device, device-to-device (D2D) terminal, or node, such as a smart phone. , a laptop, cell phone, sensor, relay, mobile tablet, or even a small base station capable of communicating using wireless communication with a wireless network node or wireless device. An embodiment of the present specification shows that the first wireless device 10 may be a vehicle, and the second wireless device 10 ′ is a stop sign (V2I), a wireless network node (V2N), a device on a pedestrian (V2P). ), or V2X (vehicle to anything) communication, which can be other vehicles (V2V) or vice versa.

The radio communication network 1 comprises a radio network node 12 which provides radio coverage over a geographic area, service area 11 of a first radio access technology (RAT), such as NR. The wireless network node 12 configures a sidelink for the wireless device. The wireless network node 12 includes an access node, an access controller, a base station, for example a wireless base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a base transceiver station, a wireless remote unit, Access point base station, base station router, wireless local area network (WLAN) access point or AP STA (Access Point Station), transmission arrangement of wireless base station, standalone access point, or for example the first wireless access technology used and a transmit/receive point, such as any other network unit or node capable of communicating with a wireless device within the area served by the wireless network node 12 according to the terminology. As an alternative, the wireless network node 12 may be, for example, a Distributed Node (DN), for example a function contained in the cloud may be used to perform or partially perform the method herein. . The wireless network node 12 may be referred to as a serving radio network node, where the service area may be referred to as a serving cell, and the serving network node may transmit DL to and from the wireless device 10 and UL from the wireless device 10 . It communicates with the wireless device 10 in the form of a transmission. It should be noted that a service area may be represented as a cell, beam, beam group, etc. to define an area of radio coverage.

The following mainly focuses on specific QoS performance requirements or characteristics, such as data rate, reliability, latency, to which specific sidelink packets may be associated, for example. However, the embodiments herein can be easily generalized to other QoS requirements, also referred to as QoS indicators. According to an embodiment of the present specification, the wireless network node 12 represents one or more sets of QoS requirements, each QoS requirement comprising a threshold value associated with a QoS characteristic, each QoS of the set of one or more QoS requirements. Configure the wireless device 10 by indicating a mapping of one or more LCGs reserved for BSR reporting of sidelinks to data that meets the requirements. A method according to an embodiment of the present specification is performed by a wireless device 10 and a wireless network node 12 .

3A shows a combined flowchart and signaling scheme according to an embodiment of the present specification.

act 300 . The pre-configuration of the wireless network node 12 or wireless device 10 may represent one or more sets of QoS requirements. Any possible QoS requirements that are specified may be significant. For each of these QoS requirements of interest, pre-configuration of the wireless network node 12 or wireless device 10 may reserve one or more LCGs for BSR reporting for data that meets the respective QoS requirements. . For example, the wireless network node 12 may send an indication to the wireless device 10, ie, use a specific LCG to report the buffer status of data that certain QoS requirements have been met, and other QoS requirements. It may instruct the wireless device 10 to use the second LCG to report the buffer status of the satisfied data.

Given that a given packet may have multiple QoS characteristics of interest, wireless device 10 may map such a packet to multiple LCGs, where each LCG corresponds to one QoS characteristic of this packet. . Since these packets are mapped to one single LCID for logical channel prioritization by the wireless device 10 anyway, the wireless device 10 can map this single LCID to multiple LCGs according to the procedure described above. This method means that the wireless device 10 can maintain an independent buffer state for each LCG, ie, each QoS requirement, to determine the amount of data available in a buffer with a particular QoS requirement.

Alternatively or additionally, depending on the pre-configuration of the wireless network node 12 or wireless device 10, one or more QoS requirements may be prioritized over other requirements. For example, the wireless network node 12 may indicate that a first QoS requirement, eg, a reliability such as a first level of PPPR, is prioritized regardless of other QoS requirements of this packet. In this case, the wireless device 10 only sends these packets that meet the QoS requirements to a single LCG, that is, to the LCG reserved by the (pre)configuration to report data that meets that QoS requirement, such as a set reliability value. can be mapped.

Alternatively or additionally, one specific QoS requirement may be prioritized, which may be (pre)configured only if the corresponding QoS value is above a threshold value. For example, if the PPPR of the packet is less than the PPPR threshold (or greater than depending on whether the high priority has a low or high value), this means that the PPPR of the packet is irrelevant. may ignore the PPPR of a packet for at least LCG mapping, and may not update any buffer state of any LCG associated with a specific value of PPPR. Every packet may be mapped to at least one LCG. An embodiment of the present specification allows a packet to be mapped to an LCG based on the QoS of the packet, for example, the LCG may be for a packet with PPPR>4, for example. However, a packet may have a number of QoS requirements associated with it, e.g. a value for PPPR (R for reliability) and a value for PPPP (P for priority), so that, in this specification, high reliability Although a packet is allowed to be mapped to a particular LCG, the same packet may be mapped to a different LCG, eg an LCG for priority >2. Otherwise, the wireless device 10 may update the buffer status of the LCG associated with the PPPR by considering the packet. Note that 'buffer status' also deals with buffer size, for example.

The threshold values described above may be (pre)configured differently for different SL services and/or different destination identities (IDs). In this way, given that the wireless device 10 has to transmit packets corresponding to a particular service or particular destination, the wireless device 10 determines that the QoS requirements of these packets are related to the packet destination and/or service concerned. You can update the buffer status of that particular destination and/or service only if present.

Action 301 . The wireless device 10 may trigger a BSR of a packet between the wireless device 10 and another wireless device, such as the second wireless device 10', eg, when the level of a buffer for the packet in the PPPR is reached. do.

act 302 . Wireless device 10 may then further transmit an indication indicating QoS requirements, also referred to as QoS characteristics associated with the sidelink. This indication is associated with a logical channel, for example, a logical channel ID (LCID) or a logical channel group (LCG), for example, the indication may be an LCID or LCG. The indication may be included in the BSR for the wireless network node 12 .

In one approach, the wireless network node 12 may provide a mapping between these QoS requirements and specific LCGs to specific QoS requirements. As there may be multiple QoS requirements, each of these QoS requirements may be mapped to a different set of LCGs. The LCG set contains all LCGs, eg up to 4 associated with specific QoS requirements.

Such a configuration indication may be provided by dedicated signaling or broadcast signaling. When the wireless device receives the configuration indication, the wireless device 10 determines one or more performance characteristics of the packet in the buffer and associates each individual performance characteristic with one of the LCGs in the LCG set configured for that particular performance characteristic.

The LCGs of one or more LCG sets may then be reported to the radio network node 12 in the SL BSR. Accordingly, the wireless device 10 may transmit an indication that it is an LCG to the wireless network node 12 .

Depending on how the different LCG sets are represented, different methods can be envisaged for the design of the SL BSR reported to the MAC Control Element (CE).

Action 303. Thereafter, the wireless network node 12 may process the communication of the wireless device 10 in view of the received indication, and the wireless network node responds if the wireless device has a packet in the SL buffer that requires high reliability transfer. Link packet replication may be enabled, or one or more carriers may be enabled depending on the data rate of the packets to be transmitted. Decisions about actual transmission parameters, eg, the number of MCS, transmission (Tx) power, and PRBs employed by the wireless device 10 may also be affected. For example, the wireless network node 12 may set up packet replication for all packets having a reliability requirement of a particular relevance.

Figure 3b shows a possible configuration of the mapping between the LCG to be used for BSR reporting for a specific destination ID X and different QoS tags. Certain priority tags such as PPPP are mapped to reserved logical channel groups such as LCG1,2,3, while other priority tags (reliability tags) such as PPPR are mapped to one reserved LCG such as LCG 4. In the case of a specific destination index, e.g. ID X, there is at least a specific PPPR irrelevant for LCG mapping, and thus in any buffer state calculation by the wireless device 10 of any LCG associated with a specific value of PPPR. may not be considered.

In Fig. 3c, for example, if a packet with PPPR/PPP higher than a certain value is specified to be prioritized over any other QoS tag, X bytes of the packet are added to the current buffer size of LCG1 or LCG4/ or may be included in the calculation. In another embodiment described above, X bytes are instead added to the buffer size of both LCG1 and LCG4. As already shown in FIG. 3C , when PPPR has a low priority, for example, PPPR 4 or less, a packet may be mapped only to LCG1 or LCG2 or LCG3.

In one method, each LCG set is represented by a specific number of groups of LCGs, and each LCG in the set is identified by a specific ID. Different sets of LCGs are mapped to different LCG IDs, for example in consecutive order. For example, QoS requirements related to PPPP are mapped to LCG1, LCG2, LCG3, LCG4. Reliability-related QoS requirements are mapped to LCG5, LCG6, LCG7, and LCG8. Different QoS requirements related to a given V2X service indicated by the destination index in the SL BSR MAC are also the same. For each destination index that identifies the V2X service type, one or more logical channel groups associated with the QoS of interest of the destination index are associated. (pre) configuration may indicate QoS of interest for each V2X service type, so that the wireless device and/or wireless network node reports the QoS of interest for a specific V2X service type that the wireless device 10 needs to transmit will be set immediately.

Thus, upon receiving the SL BSR, the wireless network node 12 may understand the amount of data corresponding to the different QoS characteristics available in the wireless device 10 sidelink buffer for transmission for a particular destination index. .

The mapping between QoS requirements and LCGs or sets or groups of LCGs may be provided or pre-configured by the NW, and different sets of LCGs may contain different numbers of LCGs.

Thus, according to this method, the SL BSR may look like FIG. 4 , where different octets corresponding to different LCG IDs are mapped to groups of different QoS characteristics or requirements. In Fig. 4, for simplicity, four LCGs are considered, in which LCG1-2 is mapped to PPPP and LCG3-4 is mapped to reliability. Considering the N destination indexes, the X LCG and Y QoS characteristics of interest, the SL BSR MAC CE will forward the maximum N*X*Y buffer size status to the wireless network node 12 .

In another method, the LCG ID is the same across sets or groups of different LCGs for different QoS characteristics or requirements, and unlike the previous method, different SL BSR MAC CEs may be used to report different QoS related BSRs. Each SL BSR MAC CE may carry different QoS related information, and is uniquely identified by a dedicated LCID value in the MAC header. According to different SL BSR triggering conditions, the wireless device 10 may trigger an SL BSR MAC CE associated with a QoS characteristic or other characteristic, thereby adding a specific LCID value configured to indicate a specific MAC CE in the MAC subheader. .

In another method, the LCG ID is the same across sets or groups of different LCGs for different QoS characteristics or requirements, and unlike the previous method, the same SL BSR MAC CE is used to report the BSRs associated with different QoS. This means that each group or set of LCGs is assigned an ID that exclusively represents the group. This may be a wireless network node 12 or pre-configuration or specification to indicate a group ID associated with each QoS indicator or requirement. According to different SL BSR triggering conditions, the wireless device 10 may trigger an SL BSR MAC CE associated with a QoS characteristic or other characteristic, thereby adding a specific configured group ID with which the LCG is associated. For example, in SL BSR MAC CE, some specific fields, for example, 'G' field may be used to indicate a specific group, that is, 'G=00' may indicate PPPP related information, and 'G= 01' may indicate reliability-related information. How many 'G' bits should be reserved to indicate groups of different QoS may depend on the amount of QoS requirements of interest.

5 shows a group report of MAC CE.

In another method, one LCG in one LCG set consists of a logical channel identifier that is assigned to a given QoS requirement of the packet. Here the logical channel identity may be different according to different sets of QoS requirements. For example, based on PPPP, a given packet may be mapped to a generic logical channel ID (LCID) by a MAC entity that is eventually grouped into a specific LCG set A by the wireless device 10, while at the same time the same packet may be mapped to a MAC entity It can be mapped to another logical channel tag belonging to another LCG set B by LCG set A is used by the MAC entity for logical channel prioritization, whereas LCG set B is used to report the buffer status of certain QoS requirements to the wireless network node 12 according to one of the MAC CE designs described above. .

In another embodiment, the (pre) configuration maps specific packets with specific QoS characteristics to specific LCIDs according to QoS characteristics of interest. For example, if a packet has very strict reliability requirements and relaxed latency requirements, these packets are mapped to a specific set of LCIDs that are dedicated/reserved for packets with strict reliability requirements. The LCG to which this LCID set may be mapped may also be reserved.

As an example, this is taken in the case of packet duplication, ie the same packet is transmitted twice on different carriers. The wireless network node 12 may configure packet replication for all packets with reliability requirements of a specific relevance, such as PPPR (ProSe Per Packet Reliability) such as PPPR1 and PPPR2.

One copy of a duplicate packet may be mapped to an LCID considering one QoS characteristic, for example PPPP, while another copy of the duplicate packet may be mapped to an LCID considering a reliability characteristic, for example PPPR1/2. . The MAC entity may be configured such that one of its replicas with PPPR1 maps to one of the available LCIDs based on PPPP, but the other replica maps to another reserved LCID based on PPPR, which in this case is PPPR1. Similarly, if there are other packets with PPPR2 to be transmitted, these packets may be mapped to a specific LCID based on the associated PPPP, and to another reserved LCID based on the associated PPPR, which in this case is PPPR2. This latter LCID may or may not be the same as the LCID associated with the previous packet with PPPR1. A set of LCIDs dedicated to an associated PPPR, in this case PPPR1 and PPPR2, can be grouped into a specific LCG ID that can be dedicated exclusively to an LCID with an associated PPPR. The wireless device 10 may not assign the LCID of a packet with an irrelevant QoS requirement to an LCG ID that is reserved for the LCID of a packet with the relevant QoS requirement, ie, PPPR1 and PPPR2 in this case. In one embodiment, the wireless device 10 may indicate to the network an LCID reserved for packets with specific QoS characteristics, for example via RRC signaling.

In this case, the MAC CE design may be similar to the design of FIG. 4 , where one or more specific LCGs associated with a specific LCG group by the wireless network node 12 require specific QoS by the wireless network node 12 . It is identified as conveying information about the buffer state of the For example, in FIG. 4 , groups of LCG3 and LCG4 are identified by the wireless network node 12 as carrying information related to reliability requirements.

The triggering condition for the SL BSR can be the same as the triggering condition for the legacy BSR, e.g. periodic triggering or new data takes precedence over any other logical channel with data already available in the buffer. It becomes available for high logical channels.

When the same packet is mapped to one or more different sets of logical channel groups corresponding to different QoS, the packets may or may not trigger SL BSR according to the priority of these packets in different mapped sets of associated logical channel groups. For example, if a packet has the highest priority in at least one of the LCGs belonging to one LCG set to which the packet is allocated, the SL BSR will be triggered if a packet has the highest priority over all other packets in any LCG belonging to the same LCG set.

For example, as in FIG. 4 , consider that two sets of LCGs, LCG1 and 2, are related to priority characteristics, and LCG3 and 4 are related to reliability. If a packet with LCID belonging to LCG1 is received and there is no other data in the current buffer, SL BSR is triggered. If another packet with LCID 2 belonging to LCG2 is received, the SL BSR is not triggered because there is already a packet with the highest priority in the UE buffer. When another packet with LCID 3 belonging to LCG3 is received, the other two packets in the UE buffer have the highest LCID priority but belong to different LCG sets, so the SL BSR is triggered.

Method operations performed by the wireless network node 12 for handling communication between wireless devices via sidelinks in a wireless communication network according to some embodiments will now be described with reference to the flowchart shown in FIG.

The actions need not be taken in the order noted below, but may be taken in any suitable order. Actions performed in some embodiments are indicated as dashed boxes.

act 600 . The wireless network node 12 represents one or more sets of QoS requirements, each QoS requirement including a threshold value associated with a QoS characteristic, and satisfies each QoS requirement of the set of one or more QoS requirements. Configures the wireless device 10 by indicating the mapping of one or more LCGs reserved for BSR reporting of the sidelink to the data to be sent. QoS requirements may indicate levels associated with QoS characteristics. The wireless network node 12 is a sender, e.g. two pieces of information: what QoS requirements the wireless device 10 should consider when performing mapping, and which QoS requirements should be mapped The wireless device 10 is configured by transmitting a certain level of for example; All data with a PPPP of 3 or higher is mapped to a specific LCG. Thereafter, the radio network node 12 may also transmit an indication of which LCG should be associated with the above-mentioned traffic. Thus, by indicating to the wireless device 10 to use a particular LCG to report the buffer status of data with particular QoS characteristics, the set may include one or more QoS requirements. Given that a given packet may have multiple QoS requirements of interest, wireless network node 12 may configure wireless device 10 to map such packets to multiple LCGs, where each LCG is Corresponds to one QoS characteristic of this packet. Alternatively or additionally, each QoS requirement may be mapped to a different LCG. Wireless network node 12 may indicate to a wireless device that one or more QoS requirements are prioritized over other QoS requirements, for example, wireless network node 12 may indicate that certain QoS requirements are prioritized over other QoS requirements. It is possible to configure the wireless device 10 to be integrated. The wireless network node 12 may configure the wireless device 10 in which one particular QoS characteristic is prioritized when the corresponding QoS value exceeds a certain (pre)configurable threshold value. In one method, the threshold may be configured differently (pre) for different SL services and/or different destination IDs.

Action 601 . The wireless network node 12 may receive an indication from the wireless device 10 in the BSR, which is an LCG mapped to the satisfied QoS requirements of the packet, eg, this indication indicates the packet's quality of service. (QoS) Represents a requirement or characteristic. An indication is associated with a logical channel.

Action 602 . The wireless network node 12 may then process the communication of the sidelink of the wireless device 10 in view of the received indication. In one embodiment, upon receiving the BSR with the LCG corresponding to the different QoS characteristics, the wireless network node 12 may perform a specific operation related to sidelink communication. For example, if the BSR indicates that the wireless device 10 has a packet with a high PPPR, alternatively, if the PPPR exceeds a certain threshold and has a high data amount, the wireless network node 12 will Packet replication for (10) can be configured. Configuration may occur via RRC (Radio resource control) signaling or MAC CE.

For example, the wireless network node 12 may copy which packets to the wireless device 10 based on the reliability of the packets, eg, all packets with a reliability higher than a certain value should be replicated. can be explicitly indicated. If this is done via MAC CE, the MAC CE may contain a set of bits, for example one octet, where each bit represents a PPPR for which packet replication should be activated. If the value of the bit is 1, the wireless device performs packet replication for the corresponding PPPR, otherwise does not perform. Similarly, the wireless network node 12 may indicate to the wireless device 10 to stop replicating if the wireless device 10 does not have high-reliability packets or the number of such packets is lower than a threshold value.

In another embodiment, the wireless network node 12 does not signal for which QoS the wireless device 10 should start replicating, such as PPPR. Assuming that the radio network node 12 has previously indicated that it is an associated PPPR and an associated LCG mapping, the radio network node 12 indicates that the LCG mapping indicates that packet replication over the sidelink should be allowed for all relevant PPPRs provided. You can simply send a flag. If this is done via MAC CE, the MAC CE may be a zero bit MAC CE.

For example, the wireless network node 12 has, for example, two mappings:

Mapping A: all traffic with priority 3 or higher must be mapped to LCG 1;

Mapping B: All traffic requiring confidence 2 or higher must be mapped to LCG 2;

A packet with priority 2 and reliability 5 proceeds to LCG 1 (satisfying mapping A, but not mapping B).

A packet with a priority of 4 and a reliability of 2 proceeds to LCG 2 (satisfying mapping B, but not mapping A).

A packet having a priority of 2 and a reliability of 2 may proceed to both LCG1 and LCG2. Basically, when wireless device 10 calculates and reports how much data is available in LCG1, it includes these packets, but will also include these packets when calculating how much data is available in LCG2. Alternatively, a packet with priority 2 and reliability 2 may be mapped to only one of LCG1 and LCG2 depending on which QoS characteristic is prioritized, the prioritization being based on radio network node signaling or "pre-configuration" can do.

A method operation performed by the wireless device 10 for handling communication between wireless devices via a sidelink in a wireless communication network according to some embodiments will now be described with reference to the flowchart shown in FIG. 7 . Actions performed in some embodiments are indicated by dashed boxes.

Act 700 . The wireless device 10 configures, from pre-configuration or reception, a set of one or more QoS requirements, each QoS requirement comprising a threshold or level associated with a QoS characteristic, and a QoS of each of the one or more sets of QoS requirements. Configure mapping of one or more LCGs reserved for BSR reporting of sidelinks on data that meets the requirements to the radio network node. This set may contain one or more QoS requirements. Accordingly, the wireless device 10 is configured or receives, from the wireless network node 12, one or more QoS sets of interest mapped to one or more LCGs for BSR reporting. In another way, all possible QoS specified is of interest. The indication may indicate one or more QoS requirements of the packet in the buffer associated with the buffer status report, wherein the one or more QoS requirements include at least one of reliability, latency, and data rate; An indication is associated with a logical channel. The wireless device 10 is configured or may be configured such that one or more QoS requirements are prioritized over one or more other QoS requirements.

Action 701. The wireless device 10 may trigger the BSR.

Act 702 . The wireless device 10 may determine one or more QoS requirements of the packets in the buffer.

Action 703. The wireless device 10 may then map each one or more QoS requirements to a different configured LCG.

Act 704 . The wireless device 10 may send an indication to the wireless network node 12 in the buffer status report, which is an LCG mapped to the satisfied QoS requirements of the packet, for example, the indication is the QoS requirements of the packet. Represents an item or characteristic and is associated with a logical channel.

8 is a block diagram illustrating a wireless network node 12 shown in two embodiments for handling communication between wireless devices via sidelinks in a wireless communication network according to an embodiment of the present specification.

The wireless network node 12 may include processing circuitry 801 configured to perform the methods herein, eg, one or more processors.

The wireless network node 12 may include a configuration unit 800 . The wireless network node 12, processing circuitry 801 and/or configuration unit 800 represents a set of one or more QoS requirements, each QoS requirement comprising a threshold value associated with a QoS characteristic, for example: Mapping of one or more LCGs reserved for BSR reporting of sidelinks for data that meets each QoS requirement among a set of one or more QoS requirements with one or more QoS sets mapped to one or more LCGs for BSR reporting It is adapted to configure the wireless network node 12 by indicating. In another way, all possible QoS specified is of interest. This set may include one or more QoS requirements. Wireless network node 12, processing circuitry 801 and/or configuration unit 800 may be configured to indicate to wireless device 10 that one or more QoS requirements are prioritized over other QoS requirements. .

The wireless network node 12 includes a receiving unit 802 . For example, it may include a receiver module or a transceiver module. The wireless network node 12 , the processing circuitry 801 and/or the receiving unit 802 may be configured to receive an indication from the wireless device 10 in the BSR, which indication indicates the satisfied QoS requirements of packets in the BSR. LCG mapped to, for example, this indication indicates the quality of service (QoS) requirements or characteristics of the packet and is associated with a logical channel. Each QoS requirement may be mapped to a different LCG. QoS requirements may indicate levels associated with QoS characteristics.

The wireless network node 12 may include a handling unit 803 . The wireless network node 12 , the processing circuitry 801 and/or the handling unit 803 may be configured to handle communication of the sidelink of the wireless device 10 taking into account the received indication. The wireless network node 12 may further include a communication interface including, for example, one or more antennas.

The wireless network node 12 further includes a memory 804 . The memory includes one or more units used to store data for, for example, instructions, configuration indications, mappings of LCGs, LCIDs, applications for performing the methods disclosed herein when executed, and the like.

A method according to an embodiment described herein for a wireless network node 12, when executed on at least one processor, comprises the at least one processor as being performed by the wireless network node 12. Each is implemented by, for example, a computer program product 805 or a computer program comprising portions of instructions, ie, software code, to perform the operations. The computer program product 805 may be stored on a computer-readable storage medium 806 , such as a disk, a universal serial bus (USB) stick, or the like. A computer-readable storage medium 806 having stored thereon a computer program product, when executed on at least one processor, causes the at least one processor to perform the operations described herein as performed by the wireless network node 12 . command may be included. In some embodiments, the computer-readable storage medium may be a transitory or non-transitory computer-readable storage medium.

9 is an example in two embodiments to handle communication between a wireless device and another wireless device through a sidelink in a wireless communication network according to an embodiment of the present specification, for example in V2X (vehicle to anything) communication It is a block diagram showing a wireless device 10.

The wireless device 10 may include processing circuitry 901, such as one or more processors, configured to perform the methods herein.

The wireless device 10 may include a configuration unit 900 . The wireless device 10 , the processing circuitry 901 and/or the configuration unit 900 is adapted to configure or receive a set of one or more QoS requirements from a pre-configuration or reception, wherein each QoS requirement is a QoS characteristic. and mapping, to the wireless network node, one or more LCGs reserved for BSR reporting of sidelinks for data that meets each QoS requirement in the set of one or more QoS requirements. Such a set may include one or more QoS requirements and may receive, for example, from the wireless network node 12, one or more sets of QoS of interest mapped to one or more LCGs for BSR reporting. In another way, all possible QoS specified is of interest. Wireless device 10 , processing circuitry 901 , and/or configuration unit 900 may be configured such that one or more QoS requirements are prioritized over other one or more QoS requirements.

The wireless device 10 may include, for example, a transmitting unit 902 , such as a transmitter module or a transceiver module. The wireless device 10, the processing circuitry 901 and/or the transmitting unit 902 may be configured to transmit an indication in the BSR to the wireless network node, the indication being the LCG mapped to the satisfied QoS requirements of the packet; For example, it represents the quality of service (QoS) requirements or characteristics of a packet and is associated with a logical channel. The indication may indicate one or more QoS requirements of the packet in the buffer associated with the buffer status report, wherein the one or more QoS requirements include at least one of reliability, latency, and data rate; Here, the indication is associated with a logical channel.

The wireless device 10 may include a triggering unit 903 . The wireless device 10 , the processing circuitry 901 , and/or the triggering unit 903 may be configured to trigger the BSR. The wireless device 10 , the processing circuitry 901 and/or the triggering unit 903 may be configured to determine one or more QoS requirements of packets in the buffer; It may be configured to map each one or more QoS requirements to a different LCG as configured.

The wireless device 10 further includes a memory 904 . The memory includes one or more units used to store data for, for example, instructions, configuration instructions, mapping information, QoS information, applications for performing the methods disclosed herein when executed, and the like. Wireless device 10 may further include a communication interface including, for example, one or more antennas.

A method according to an embodiment described herein for a wireless device 10, when executed on at least one processor, causes the at least one processor to perform the operations described herein as performed by the wireless device 10 . each embodied by, for example, computer program product 905 or a computer program comprising portions of software code, ie, instructions to cause it to be executed. The computer program product 905 may be stored on a computer-readable storage medium 906 , such as a disk, USB stick, or the like. A computer readable storage medium 906 having stored thereon a computer program product, when executed on at least one processor, causes the at least one processor to perform the operations described herein as performed by the wireless device 10 . It may contain instructions. In some embodiments, the computer-readable storage medium may be a transitory or non-transitory computer-readable storage medium.

In some embodiments, the more general term “wireless network node” is used, which may correspond to any type of wireless network node or any network node that communicates with a wireless device and/or other network node. Examples of network nodes include NodeB, MeNB, SeNB, a network node belonging to a master cell group (MCG) or a secondary cell group (SCG), a base station (BS), such as an MSR BS. Multi-standard radio (MSR) radio node, eNodeB, network controller, radio-network controller (RNC), base station controller (BSC), relay, donor node control relay, base transceiver station (BTS) , an access point (AP), a transmission point, a transmission node, a remote radio unit (RRU), a remote radio head (RRH), a node of a distributed antenna system (DAS), and the like.

In some embodiments, the non-limiting term wireless device or user equipment (UE) is used to refer to any type of wireless device that communicates with network nodes and/or other wireless devices in a cellular or mobile communication system. Examples of UE include target device, device to device (D2D) UE, ProSe UE (proximity capable UE), machine type UE or UE capable of machine to machine (M2M) communication, tablet, mobile terminal , smart phone, LEE (laptop embedded equipped), LME (laptop mounted equipment), USB dongle, etc.

Embodiments are applicable to any RAT or multi-RAT system, where the wireless device is a signal (eg data), eg New Radio (NR), Wi-Fi, Long Term Evolution (LTE), LTE- Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB) ), which only mentions a few possible implementations.

As will be readily appreciated by those familiar with communication design, the functional means or units may be implemented using digital logic and/or one or more microcontrollers, microprocessors or other digital hardware. In some embodiments, some or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC) or two or more separate devices with appropriate hardware and/or a software interface between them. Some functions may be implemented, for example, on a processor shared with other functional components of a wireless device or network node.

Alternatively, some functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software in conjunction with appropriate software or firmware. Accordingly, the term "processor" or "controller" as used herein does not exclusively refer to hardware capable of executing software, but implicitly, without limitation, digital signal processor (DSP) hardware and/or programs or May contain application data. Other hardware, conventional and custom strings, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

Any suitable step, method, feature, function or advantage disclosed herein may be performed via one or more functional units or modules of one or more virtual devices. Each virtual device may include a number of such functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware that may include a digital signal processor (DSP), special purpose digital logic, and the like. . The processing circuitry may be configured to execute program code stored in a memory, such memory as one or more read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. It can contain any type of memory. The program code stored in the memory includes program instructions for executing one or more telecommunication and/or data communication protocols as well as instructions for performing one or more techniques described herein. In some implementations, processing circuitry may be used to cause each functional unit to perform a corresponding function in accordance with one or more embodiments of the present disclosure.

Embodiment 1. A first embodiment herein may disclose a wireless network node comprising processing circuitry and a memory, wherein the processing circuitry comprises: one or more services, each QoS requirement comprising a threshold value associated with a QoS characteristic One or more logical channel groups representing a set of quality (QoS) requirements, and reserved for buffer status report (BSR) reporting of sidelinks for data that meets each QoS requirement of one or more sets of QoS requirements ( LCG) by indicating the mapping of the wireless device is configured.

Embodiment 2. The wireless network node according to embodiment 1, wherein the set includes one or more QoS requirements.

Embodiment 3. In the wireless network node according to embodiment 1, the processing circuit comprises:

receive an indication from the wireless device in the buffer status report, the indication being an LCG mapped to the packet's satisfied QoS requirements;

and handle communication of a sidelink of the wireless device in view of the received indication.

Embodiment 4. In the wireless network node according to embodiment 1, the processing circuit comprises:

and indicate to the wireless device that one or more QoS requirements are prioritized over other one or more QoS requirements.

Embodiment 5. In the wireless network node according to embodiment 1, each QoS requirement is mapped to a different LCG.

Embodiment 6. In the wireless network node according to embodiment 1, a QoS requirement indicates a level associated with a QoS characteristic.

Embodiment 7. In a second embodiment disclosing a wireless device comprising processing circuitry and a memory, the processing circuitry comprises:

a set of one or more quality of service (QoS) requirements, each QoS requirement including a threshold value associated with a QoS characteristic, and a set of one or more QoS requirements that satisfy each QoS requirement of the set, from preconfiguration or reception and configure mapping of one or more logical channel groups (LCGs) reserved for sidelink buffer status report (BSR) reporting to wireless network nodes for data.

Embodiment 8. The wireless device according to embodiment 2, wherein the set comprises one or more QoS requirements.

Embodiment 9. The wireless device according to embodiment 2, wherein the processing circuit comprises:

and send to the wireless network node an indication in the buffer status report, the indication being an LCG mapped to the satisfied QoS requirements of the packet.

Embodiment 10. The wireless device according to embodiment 2, wherein the indication indicates one or more quality of service (QoS) requirements of a packet in a buffer associated with a buffer status report, wherein the one or more QoS requirements are of reliability, latency and data rate. at least one; An indication is associated with a logical channel.

Embodiment 11. The wireless device according to embodiment 2, wherein the processing circuit comprises:

determine one or more QoS requirements of the packet in the buffer;

and to map one or more QoS requirements to different LCGs as configured.

Embodiment 12 The wireless device according to embodiment 2, wherein the processing circuitry is further configured to configure the one or more QoS requirements to be prioritized over the other one or more QoS requirements.

Embodiment 13 A third embodiment of the present specification may disclose a wireless network node including a configuration unit, wherein the configuration unit includes:

Each QoS requirement represents a set of one or more quality of service (QoS) requirements including a threshold value associated with a QoS characteristic, and a sidelink to data that satisfies each QoS requirement of the one or more sets of QoS requirements. configured to configure the wireless device by indicating a mapping of one or more logical channel groups (LCGs) reserved for buffer status report (BSR) reporting.

Embodiment 14. The wireless network node according to embodiment 3, wherein the set includes one or more QoS requirements.

Embodiment 15. In the wireless network node according to embodiment 3,

a unit unit configured to receive an indication from the wireless device in the buffer status report, the indication being an LCG mapped to a satisfied QoS requirement of the packet;

and a handling unit configured to handle communication of a sidelink of the wireless device in view of the received indication.

Embodiment 16. The wireless network node according to embodiment 3, wherein the configuration unit comprises:

and indicate to the wireless device that one or more QoS requirements are prioritized over other one or more QoS requirements.

Embodiment 17. The wireless network node according to embodiment 3, wherein each QoS requirement is mapped to a different LCG.

Embodiment 18. The wireless network node according to embodiment 3, wherein the QoS requirement indicates a level associated with a QoS characteristic.

Embodiment 19 In a fourth embodiment disclosing a wireless device comprising a configuration unit, the configuration unit comprises:

a set of one or more quality of service (QoS) requirements, each QoS requirement including a threshold value associated with a QoS characteristic, and a set of one or more QoS requirements that satisfy each QoS requirement of the set, from preconfiguration or reception and configure mapping of one or more logical channel groups (LCGs) reserved for sidelink buffer status report (BSR) reporting to wireless network nodes for data.

Embodiment 20 The wireless device according to embodiment 4, wherein the set includes one or more QoS requirements.

Embodiment 21. A wireless device according to embodiment 4, comprising:

and a sending unit, configured to transmit, to the wireless network node, an indication in the buffer status report, the indication being an LCG mapped to a satisfied QoS requirement of the packet.

Embodiment 22. The wireless device according to embodiment 4, wherein the indication indicates one or more quality of service (QoS) requirements of a packet in a buffer associated with a buffer status report, wherein the one or more QoS requirements are of reliability, latency and data rate. at least one; An indication is associated with a logical channel.

Embodiment 23. The wireless device according to embodiment 4, wherein the configuration unit comprises:

determine one or more QoS requirements of the packet in the buffer;

and to map one or more QoS requirements to different LCGs as configured.

Embodiment 24 The wireless device according to embodiment 4, wherein the configuring unit is further configured to configure the one or more QoS requirements to be prioritized over the other one or more QoS requirements.

Referring to FIG. 8A , according to one embodiment, a communication system includes an access network 3211 , such as a radio access network, and a communication network 3210 , such as a 3GPP type cellular network, including a core network 3214 . The access network 3211 includes a plurality of base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs, or other types of wireless access points, examples of wireless network node 12 herein, each of which is Corresponding coverage areas 3213a, 3213b, 3213c are defined. Each of the base stations 3212a , 3212b , 3212c may be connected to the core network 3214 via a wired or wireless connection 3215 . A first user equipment (UE) 3291 , an example of a UE 10 located in the coverage area 3213c , may wirelessly connect to or paged by a corresponding base station 3212c . A second UE 3292 in the coverage area 3213a is wirelessly connectable to a corresponding base station 3212a. Although a plurality of UEs 3291 , 3292 are shown in this example, the disclosed embodiment is equally applicable to a situation in which a single UE is within a coverage area or a single UE connects to a corresponding base station 3212 .

The communication network 3210 is itself coupled to a host computer 3230, which may be implemented in hardware and/or hardware in a standalone server, a cloud implemented server, a distributed server, or as a processing resource in a server farm. . The host computer 3230 may be owned or controlled by the service provider, or may be operated by or on behalf of the service provider. The connections 3221 , 3222 between the communication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may be via an optional intermediate network 3220 . Intermediate network 3220 may be one or a combination of one or more of public, private, or hosted networks; Intermediate network 3220, if present, may be a backbone network or the Internet; In particular, the intermediate network 3220 may include two or more subnetworks (not shown).

The communication system of FIG. 8A enables a connection between a host computer 3230 and one of the overall connected UEs 3291 , 3292 . The connection may be described as an over-the-top (OTT) connection 3250 . The host computer 3230 and the connected UEs 3291, 3292 use the access network 3211, the core network 3214, any intermediate network 3220, and possibly additional infrastructure (not shown) as intermediaries. to pass data and/or signaling over the OTT connection 3250 . The OTT connection 3250 may be transparent in that the participating communication devices through which the OTT connection 3250 passes are not aware of the routing of uplink and downlink communications. For example, the base station 3212 may be involved in the past routing of incoming downlink communications with data originating from the host computer 3230 to be forwarded (eg, handed over) to the connected UE 3291 . may not or may not need to be notified. Similarly, the base station 3212 does not need to know the future routing of outgoing uplink communications from the UE 3291 towards the host computer 3230 .

According to one embodiment, an exemplary implementation of the UE, base station and host computer discussed in the previous paragraph will now be described with reference to FIG. 8B . In the communication system 3300 , a host computer 3310 includes hardware 3315 including a communication interface 3316 configured to establish and maintain wired or wireless connections with interfaces of different communication devices of the communication system 3300 . . The host computer 3310 further includes processing circuitry 3318, which may have storage and/or processing capabilities. In particular, processing circuitry 3318 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations of these (not shown) adapted to execute instructions. The host computer 3310 may be stored on or accessible by the host computer 3310 , and further includes software 3311 executable by the processing circuitry 3318 . Software 3311 includes a host application 3312 . Host application 3312 may be operable to provide services to remote users, such as UE 3330 , connecting via OTT connection 3350 terminating at UE 3330 and host computer 3310 . When providing services to remote users, host application 3312 may provide user data that is transmitted using OTT connection 3350 .

The communication system 3300 further includes a base station 3320 that is provided in the communication system and includes hardware 3325 that enables communication with a host computer 3310 and a UE 3330 . Hardware 3325 includes communication interface 3326 for establishing and maintaining wired or wireless connections with interfaces of different communication devices of communication system 3300, as well as a coverage area served by base station 3320 (Fig. 8B). and a wireless interface 3327 for establishing and maintaining at least a wireless connection 3370 with a UE 3330 located at (not shown). Communication interface 3326 may be configured to facilitate connection 3360 to host computer 3310 . Connection 3360 may be direct or may pass through a core network of the communication system (not shown in FIG. 8B ) and/or one or more intermediate networks external to the communication system. In the illustrated embodiment, the hardware 3325 of the base station 3320 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations of these (not shown) adapted to execute instructions. processing circuitry 3328 capable of being Base station 3320 also has software 3321 stored therein or accessible through an external connection.

The communication system 3300 further includes the UE 3330 already mentioned. Its hardware 3335 may include a wireless interface 3337 configured to establish and maintain a wireless connection 3370 with a base station serving the coverage area in which the UE 3330 is currently located. Hardware 3335 of UE 3330 further includes processing circuitry 3338, which includes one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or those (not shown) adapted to execute instructions. may include a combination of UE 3330 further includes software 3331 stored on or accessible by UE 3330 , executable by processing circuitry 3338 . Software 3331 includes a client application 3332 . The client application 3332 may operate to provide services to human or non-human users via the UE 3330 with the support of the host computer 3310 . At host computer 3310 , executing host application 3312 may communicate with UE 3330 and executing client application 3332 via OTT connection 3350 terminating at host computer 3310 . When providing a service to a user, the client application 3332 may receive request data from the host application 3312 and provide the user data in response to the request data. The OTT connection 3350 may transmit both request data and user data. The client application 3332 may interact with the user to generate user data it provides.

Host computer 3310, base station 3320, and UE 3330 shown in FIG. 8B are host computer 3230, one of base stations 3212a, 3212b, 3212c, and one of UEs 3291 and 3292 in FIG. 8A, respectively. It is noted that may be equal to That is, the internal operation of this entity may be as shown in FIG. 8B, and independently, the peripheral network topology may be that of FIG. 8A.

In FIG. 8B , OTT connection 3350 illustrates communication between host computer 3310 and user equipment 3330 via base station 3320 without an explicit reference to and precise routing of messages through any intermediate devices. shown abstractly. The network infrastructure may determine the routing, which may be configured to hide from the service provider running the UE 3330 or the host computer 3310 or both. While the OTT connection 3350 is active, the network infrastructure may further take decisions to dynamically change routing (eg, based on load balancing considerations or reconfiguration of the network).

The wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments enhance the performance of OTT services provided to the UE 3330 using the OTT connection 3350 where the wireless connection 3370 forms the last segment. More precisely, the teachings of this embodiment can improve the latency that multiple QoS can be considered during communication, thus providing advantages such as reduced latency and good response.

Measurement procedures may be provided to monitor data rate, latency, and other factors that one or more embodiments improve upon. There may also be an optional network function for reconfiguring the OTT connection 3350 between the host computer 3310 and the UE 3330 in response to a change in the measurement result. The measurement procedure and/or network function for reconfiguring the OTT connection 3350 may be implemented in software 3311 of the host computer 3310 or software 3311 of the UE 3330 or both. In an embodiment, a sensor (not shown) may be located within or in connection with a communication device through which the OTT connection 3350 passes; A sensor may participate in a measurement procedure by supplying a value of an exemplified monitored quantity or by supplying a value of another physical quantity from which the software 3311 , 3331 may calculate or estimate the monitored quantity. Reconfiguration of OTT connection 3350 may include message format, retransmission settings, preferred routing, and the like; The reconfiguration need not affect base station 3320 , which may not be known or recognizable to base station 3320 . Such procedures and functions are known in the art and can be practiced. In certain embodiments, the measurements may include proprietary UE signaling that facilitates measurements of the host computer 3310, such as throughput, propagation time, delay, and the like. Measurements may be implemented such that messages, particularly empty or "dummy" messages, are sent using OTT connection 3350 while software 3311 , 3331 monitors propagation times, errors, etc.

9 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which may be described with reference to FIGS. 8A and 8B . For simplicity of the present disclosure, only the drawing reference to FIG. 9 will be included in this section. In a first step 3410 of the method, the host computer provides user data. In an optional sub-step 3411 of the first step 3410, the host computer provides user data by executing the host application. In a second step 3420 , the host computer initiates transmission carrying user data back to the UE. In an optional third step 3430, the base station transmits to the UE the user data carried in the host computer-initiated transmission in accordance with the teachings of the embodiments described throughout this disclosure. In an optional fourth step 3440 , the UE executes a client application associated with the host application executed by the host computer.

10 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which may be described with reference to FIGS. 8A and 8B . For simplicity of the present disclosure, only the drawing reference to FIG. 10 will be included in this section. In a first step 3510 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing the host application. In a second step 3520, the host computer initiates transmission carrying user data back to the UE. Transmissions may pass through a base station in accordance with the teachings of embodiments described throughout this disclosure. In an optional third step 3530 , the UE receives user data carried in the transmission.

11 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which may be described with reference to FIGS. 8A and 8B . For simplicity of the present disclosure, only the drawing reference to FIG. 11 will be included in this section. In an optional first step 3610 of the method, the UE receives input data provided by a host computer. Additionally or alternatively, in an optional second step 3620 , the UE provides user data. In an optional sub-step 3621 of the second step 3620 , the UE provides user data by executing a client application. In a further optional sub-step 3611 of the first step 3610, the UE executes a client application that provides user data in response to received input data provided by the host computer. When providing user data, the executed client application may further take user input received from the user into account. Regardless of the particular manner in which the user data has been provided, the UE, in an optional third sub-step 3630 , initiates transmission of the user data to the host computer. In a fourth step 3640 of the method, the host computer receives user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

12 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which may be described with reference to FIGS. 8A and 8B . For simplicity of the present disclosure, only the drawing reference to FIG. 12 will be included in this section. In an optional first step 3710 of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In an optional second step 3720, the base station initiates transmission of the received user data to the host computer. In a third step 3730, the host computer receives the user data carried in the transmission initiated by the base station.

It will be understood that the foregoing description and accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.

Abbreviation Explanation
3G Third Generation of Mobile Telecommunications Technology
BSM Basic Safety Messages
BW bandwidth
BSR Buffer Status Reporting
CAM Cooperative Awareness Message
CBR Channel Busy Ratio
DPTF data packet transmission format
D2D device-to-device communication
DENM Decentralized Environmental Notification Message
DSRC-only short-range communication
eNB eNodeB
ETSI European Telecommunications Standards Institute
LTE Long-Term Evolution
NW Network
RS reference signal
TF transmission format
SAE Society of the Automotive Engineers
UE User Equipment
V2I vehicle-to-infrastructure
V2P Vehicles vs. Pedestrians
V2V vehicle-to-vehicle (vehicle) communication
V2x Vehicle-to-anything-you-can-imagine
wrt with respect to
SPS Semi Persistent Scheduling
DMRS demodulation reference signal
OCC Orthogonal Cover Codes
PDCCH Physical Downlink Control Channel
DBS delay-based scheduler
MAC Media Access Control
MAC CE MAC Control Element
PUSCH Physical Uplink Shared Channel
PUCCH Physical Uplink Control Channel
PDU packet data unit
3GPP Third Generation Partnership Project
LCID Logical Channel Identity
MAC Media Access Control
MAC CE Media Access Control - Control Elements
RRC radio resource control
IP Internet Protocol
PPPP ProSe Per Packet Priority
PPPR ProSe Per Packet Reliability
ProSe Proximity Services
PRB Physical Resource Block
SL side link
SPS Semi-Persistent Scheduling
UL Uplink
DL downlink
LCG logical channel group
SFN system frame number
TTI Transmission Time Interval
SCI sidelink control information
CA carrier aggregation
SLRB sidelink radio bearer
UICC Universal Integrated Circuit Card
ME mobile device
ID identifier
PDB Packet Delay Budget
CBR Congestion Busy Ratio
SDU service data unit
PDU protocol data unit
BLER block error rate

Claims (26)

A method performed by a wireless network node configured to handle sidelink communication between wireless devices in a wireless communication network, the method comprising:
A wireless device comprising: a plurality of QoS requirements comprising at least one quality of service (QoS) requirement of a first type and at least one QoS requirement of a second type different from the first type; and
transmitting a configuration representing a mapping between a plurality of QoS requirements and a plurality of logical channel groups (LCGs) arranged for sidelink communication of data packets meeting the QoS requirements, wherein the mapping comprises:
a first mapping between at least one QoS requirement of a first type and a first portion of the LCG;
a second mapping between at least one QoS requirement of a second type and a second portion of the LCG, wherein the second portion does not overlap the first portion. The method of claim 1,
The first type of QoS requirement is each packet priority level (PPPP),
A second type of QoS requirement is a respective Packet Reliability Level (PPPR). The method of claim 1,
receiving, from the wireless device, a sidelink buffer status report (BSR) indicating a particular one of the LCGs having one or more data packets available to the wireless device;
determining, based on the mapping, QoS requirements associated with the data packets available in the particular LCG; and
and handling side communications of the wireless device in accordance with the determined QoS requirements. 4. The method of claim 3,
The determined QoS requirement is a high packet reliability level (PPPR);
and processing the sidelink communication according to the determined QoS requirement comprises sending to the wireless device an indication to perform packet replication for sidelink transmissions of available data packets. The method of claim 1,
One of the first and second types of QoS requirements with respect to selecting, at the wireless device, an LCG for a sidelink BSR for a data packet having both a first type of QoS requirement and a second type of QoS requirement transmitting a prioritization indication that is prioritized over the other of the first type and the second type. A method performed by a wireless device configured for sidelink communication with another wireless device in a wireless communication network, the method comprising:
a plurality of QoS requirements, comprising at least one quality of service (QoS) requirement of a first type and at least one QoS requirement of a second type different from the first type, from a wireless network node in the wireless communication network; and
receiving a configuration representing a mapping between a plurality of QoS requirements and a plurality of logical channel groups (LCGs) arranged for sidelink communication of data packets that satisfy the QoS requirements, wherein the mapping comprises:
a first mapping between at least one QoS requirement of a first type and a first portion of the LCG;
receiving a second mapping between at least one QoS requirement of a second type and a second portion of the LCG, wherein the second portion does not overlap the first portion; and
transmitting the sidelink BSR to the wireless network node according to the configuration. 7. The method of claim 6,
The first type of QoS requirement is each packet priority level (PPPP),
A second type of QoS requirement is a respective Packet Reliability Level (PPPR). 7. The method of claim 6,
determining, based on the mapping, an LCG associated with QoS requirements of data packets usable for sidelink transmission by the wireless device;
The sidelink BSR indicates the determined LCG. 9. The method of claim 8,
QoS requirements are High Packet Reliability Level (PPPR);
and receiving, from the wireless network node in response to the BSR, an indication to perform packet replication on a sidelink transmission of an available data packet. 7. The method of claim 6,
of the first and second types of QoS requirements with respect to selecting, from the wireless network node, an LCG for a sidelink BSR for a data packet having both a QoS requirement of a first type and a QoS requirement of a second type receiving a prioritization indication in which one is prioritized over the other of the first type and the second type;
and transmitting the sitelink BSR is further based on the prioritization indication. A wireless network node configured to handle sidelink communications between wireless devices in a wireless communications network, comprising:
communication interface; and
processing circuitry operatively coupled to the communication interface, whereby the processing circuitry and the communication interface include:
A wireless device comprising: a plurality of QoS requirements comprising at least one quality of service (QoS) requirement of a first type and at least one QoS requirement of a second type different from the first type; and
transmit a configuration indicating a mapping between a plurality of QoS requirements and a plurality of logical channel groups (LCGs) arranged for sidelink communication of data packets meeting the QoS requirements, wherein the mapping comprises:
a first mapping between at least one QoS requirement of a first type and a first portion of the LCG;
a second mapping between at least one QoS requirement of a second type and a second portion of the LCG, wherein the second portion is configured not to overlap the first portion. 12. The method of claim 11,
The first type of QoS requirement is each packet priority level (PPPP),
A second type of QoS requirement is a respective packet reliability level (PPPR). 12. The method of claim 11,
The processing circuit and communication interface are:
receive, from the wireless device, a sidelink buffer status report (BSR) indicating a particular one of the LCGs having one or more data packets available to the wireless device;
determine, based on the mapping, QoS requirements associated with data packets available in a particular LCG; and
and handle side communications of the wireless device according to the determined QoS requirement. 14. The method of claim 13,
The determined QoS requirement is a high packet reliability level (PPPR);
processing circuitry and communication interface,
and process the sidelink communication according to a QoS requirement determined based on sending to the wireless device an indication to perform packet replication for a sidelink transmission of an available data packet. 12. The method of claim 11,
processing circuitry and communication interface,
One of the first and second types of QoS requirements with respect to selecting, at the wireless device, an LCG for a sidelink BSR for a data packet having both a first type of QoS requirement and a second type of QoS requirement is further configured to transmit a prioritization indication to be prioritized over another of the first type and the second type. A wireless device configured for sidelink communication with another wireless device in a wireless communication network, comprising:
communication interface; and
processing circuitry operatively coupled to the communication interface, whereby the processing circuitry and the communication interface include:
a plurality of QoS requirements, comprising at least one quality of service (QoS) requirement of a first type and at least one QoS requirement of a second type different from the first type, from a wireless network node in the wireless communication network; and
Receive a configuration representing a mapping between a plurality of QoS requirements and a plurality of logical channel groups (LCGs) arranged for sidelink communication of data packets meeting the QoS requirements, wherein the mapping comprises:
a first mapping between at least one QoS requirement of a first type and a first portion of the LCG;
a second mapping between at least one QoS requirement of a second type and a second portion of the LCG, wherein the second portion does not overlap the first portion; and
and transmit the sidelink BSR to the wireless network node according to the configuration. 17. The method of claim 16,
The first type of QoS requirement is each packet priority level (PPPP),
A second type of QoS requirement is a respective Packet Reliability Level (PPPR). 17. The method of claim 16,
processing circuitry and communication interface,
determine, based on the mapping, an LCG associated with a QoS requirement of the data packet usable for sidelink transmission by the wireless device;
The sidelink BSR indicates the determined LCG. 19. The method of claim 18,
QoS requirements are High Packet Reliability Level (PPPR);
processing circuitry and communication interface,
and receive, from the wireless network node in response to the BSR, an indication to perform packet replication on a sidelink transmission of an available data packet. 17. The method of claim 16,
processing circuitry and communication interface,
of the first and second types of QoS requirements with respect to selecting, from the wireless network node, an LCG for a sidelink BSR for a data packet having both a QoS requirement of a first type and a QoS requirement of a second type one is further configured to receive a prioritization indication to be prioritized over the other of the first type and the second type;
processing circuitry and communication interface,
and transmit the sitelink BSR further based on the prioritization indication. delete delete delete delete delete delete

Images