DE102021108923A1 - DISCONTINUOUS RECEPTION OPERATIONS VIA NR SIDELINK - Google Patents

Abstract

Apparatus for a New Radio (NR) user equipment (UE) comprising a radio frequency (RF) interface and one or more processors coupled to the RF interface and configured to control a physical sidelink control channel Monitor (PSCCH) during an active period of a discontinuous receive (DRX) cycle; decode the PSCCH containing a Sidelink Control Information (SCI) message; decode the SCI message; and determine whether to receive a transmission over the PSCCH based on the decoded SCI message.

Description

Cross reference to related application

This patent application claims the benefit and priority of U.S. Provisional Application No. 63 / 008,468 , submitted on April 10, 2020.

Technical area

Various aspects can generally relate to the field of wireless communications.

background

In order to meet the significant market interest in energy savings during Sidelink (SL) operation, there is a need to consider methods for defining efficient mechanisms to provide discontinuous reception functionality (DRX) via New Radio (NR) SL. To that end, a general overview of a new SL-DRX mechanism is provided in this disclosure. We also go into the rationale and benefits for adopting such a scheme for mission-critical, such as vehicle-to-everything (V2X) and public safety, as well as non-mission-critical, such as vehicle-to-everything (V2X) and public safety. B. Commercial use, cases for a variety of User Equipment (UE) types.

Figure list

• 1 einen beispielhaften diskontinuierlichen Empfangszyklus für den Betrieb der NR-Funkschnittstelle illustriert.
• 2 einen beispielhaften diskontinuierlichen Empfangszyklus für den SL-Betrieb ill ustri ert.
• 3 einen beispielhaften Signalisierungsfluss für den Austausch der SL-DRX-Konfiguration illustriert.
• 4 ein beispielhaftes SL-Ressourcenpool-Design zeigt.
• 5 beispielhafte Stufen der Dekodierung von Sidelink-Steuerungsinformationen für den SL-Betrieb illustriert.
• 6 ein Netzwerk gemäß verschiedener Aspekte der vorliegenden Offenbarung ill ustri ert.
• 7 schematisch ein Drahtlos-Netzwerk gemäß verschiedenen Aspekten der vorliegenden Offenbarung zeigt.
• 8 ein Blockdiagramm ist, das Hardware-Ressourcen gemäß Aspekten der vorliegenden Offenbarung veranschaulicht.
• 9 einen beispielhaften Prozess gemäß verschiedenen Aspekten der vorliegenden Offenbarung illustriert.

In the drawings, like reference characters generally refer to the same parts throughout the different views. The drawings are not necessarily to scale, with emphasis generally on illustrating the example principles of the disclosure. In the following description, various aspects of the disclosure are described with reference to the following drawings, in which:

• 1 illustrates an exemplary discontinuous receive cycle for the operation of the NR radio interface.
• 2 an exemplary discontinuous receive cycle for the SL operation illustrated.
• 3 illustrates an exemplary signaling flow for the exchange of the SL-DRX configuration.
• 4th shows an exemplary SL resource pool design.
• 5 illustrates exemplary levels of decoding sidelink control information for SL operation.
• 6th a network illustrated in accordance with various aspects of the present disclosure.
• 7th schematically shows a wireless network according to various aspects of the present disclosure.
• 8th Figure 4 is a block diagram illustrating hardware resources in accordance with aspects of the present disclosure.
• 9 illustrates an exemplary process in accordance with various aspects of the present disclosure.

Detailed description

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or like elements. In the following description, for purposes of explanation and not limitation, specific details such as particular structures, architectures, interfaces, techniques, etc. are set forth in order to provide a thorough understanding of the various aspects of the various aspects. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various aspects can be practiced in other examples that depart from these specific details. In certain cases, descriptions of known devices, circuits, and methods are omitted in order not to obscure the description of the various aspects with unnecessary detail. For the purposes of this document, the terms “A or B” and “A / B” mean (A), (B) or (A and B).

In order to meet the significant market interest in energy saving during SL operation, there is a need to consider methods for defining efficient mechanisms in order to provide discontinuous reception functionality via NR SL. To that end, a general overview of a new SL-DRX mechanism is provided in this disclosure. We also discuss the motivations and benefits for adopting such a scheme for mission critical (V2X and public safety) as well as non-mission critical (including commercial use cases) for a variety of UE types.

• - Untersuchen kritischer Anwendungsfälle für einen verbesserten Stromsparbetrieb über NR SL;
• - Entwickeln und Vorschlagen der Verwendung des DRX-Mechanismus über NR SL, um Strom zu sparen unter Berücksichtigung dieser Anwendungsfälle zu ermöglichen; und
• - Diskussion der Auswirkungen unterschiedlicher Netzwerkabdeckung und Betriebsart(en) über SL und Bereitstellen von Lösungen für einen effektiven DRX-Betrieb in solchen Szenarien.

Aspects of this revelation:

• - Investigate critical use cases for improved power saving operation via NR SL;
• - Develop and propose the use of the DRX mechanism via NR SL to stream to enable savings taking into account these use cases; and
• - Discussion of the effects of different network coverage and operating mode (s) via SL and provision of solutions for effective DRX operation in such scenarios.

As 5G networks are built around the world and the first set of standards for NR SL has been finalized, there is an increasing interest in the market to further develop and improve the work that has been done to date. In the field of self-driving and autonomous vehicles, the solutions developed here could be valuable to enable efficient operation of remote-controlled and / or autonomous vehicles with UE (V-UE), as well as to convey power-saving functions for more environmentally friendly and efficient operation.

Most of the NR-V2X use cases outlined in Rel-16 (e.g. TS 38.211), such as platooning and advanced driving, as well as the solutions previously developed as part of the 3rd Generation Partnership Project (3GPP) do not make any assumptions about the energy saving capabilities for the V-UE involved in the SL operation. Most of the schemes and mechanisms that have been defined to meet the key requirements simply assume that the V-UEs always listen for transmissions over SL when they are interested in a particular set of services. In most cases, this is a reasonable assumption as these devices are typically vehicles such as cars or trucks on the road, or Road Side Units (RSUs) that are physically connected to the network. In most cases, the cellular modem is in the vehicle and uses the battery to supply itself. As such, power saving (and SL capability to some extent) is usually not an urgent concern. This is in contrast to "normal" cell phone operation, where power consumption is an essential aspect that must be taken into account. For Long-Term-Evolution (LTE) radio interface operation, the UE does not monitor the downlink (DL) channel continuously, but instead carries out discontinuous reception in order to switch off the radio device periodically, primarily to save battery power. The DRX mechanism has been part of cellular standards for some time and has evolved significantly over the years.

• - Netzwerkgesteuerter interaktiver Dienst (NCIS), der sich auf den Datenaustausch für interaktive Sitzungen (z.B. auf virtuellen Ressourcen (VR) basierende interaktive Dienste) zwischen Geräten konzentriert (sowohl für Proximity- als auch Non-Proximity-Fälle);
• - Lücken-Analyse für Zug-Mobilfunk-Kommumikationssysteme (MONASTERYEND), mit strengen Anforderungen an Datenrate, Latenzzeit und Zuverlässigkeit für Bahnkommunikationssysteme der nächsten Generation.
• - Enhanced Relays for Energy efficiency and Extensive Coverage (REFEC), wobei viele verschiedene Szenarien und Vertikalen wie inHome, SmartFarming, SmartFactories, Public Safety ins Auge gefasst werden. Viele von ihnen sind neu, während andere bereits in früheren Generationen von beweglichen Netzwerken abgedeckt wurden. Allerdings ist eine umfangreichere Abdeckung mit guter Energieeffizienz erforderlich im Vergleich zu dem, was frühere Generationen (dritte Generation (3G), vierte Generation (4G)) bieten konnten.
• - Audio-Visual Service Production (AVPROD), die sich auf Live-Audio- und Video-Präsentationen und Streaming-Anwendungsfälle konzentriert.

Beyond the first group of use cases, which formed the basis of the entire 3GPP standard development in Rel-16, additional considerations must be made, both in relation to the types of applications that must be operated via NR SL as well as in Reference to the type of equipment that is intended to perform these services. With respect to the former, there is concern that the requirements and operating scenarios for public safety and V2X services are not fully supported in Rel-16 and Rel-17 aims to support advanced V2X services and proximity-based services in the fifth Generation (5G). Additionally, other commercial use cases that should be considered for the Rel-17 work include:

• - Network controlled interactive service (NCIS), which focuses on data exchange for interactive sessions (e.g. virtual resource (VR) based interactive services) between devices (for both proximity and non-proximity cases);
• - Gap analysis for train mobile radio communication systems (MONASTERYEND), with strict requirements for data rate, latency and reliability for next generation train communication systems.
• - Enhanced Relays for Energy efficiency and Extensive Coverage (REFEC), taking into account many different scenarios and verticals such as inHome, SmartFarming, SmartFactories, Public Safety. Many of them are new, while others were covered by moving networks in previous generations. However, more extensive coverage with good energy efficiency is required compared to what previous generations (third generation (3G), fourth generation (4G)) could offer.
• - Audio-Visual Service Production (AVPROD), which focuses on live audio and video presentations and streaming use cases.

Considering the above-mentioned use cases, it should be obvious that the devices in question are far from the V-UEs that are provided in the Rel-16 SL design. That brings us to the second point, the types of devices. As the above use cases show, the devices aren't just limited to cars where battery power isn't an issue. Instead, they can range from fixed wireless devices in sports arenas, fast moving trains, or handheld devices very similar to a cell phone. In short, the assumptions about form factor and power consumption profiles in Rel-16 (and earlier) NR V2X work no longer apply. This brings us to the power saving aspects of this disclosure.

It is evident that power saving enables UEs with battery limitations to perform SL operations in an energy efficient manner. Rel-16 NR SL is based on the assumption of “always-on” when UEs operate SL and focuses, for example, only on UEs that are installed in vehicles with sufficient battery capacity. Therefore, energy saving solutions in Rel-17 are required for Vulnerable Road Users (VRUs) in V2X use cases and for UEs in public safety and commercial use cases where the power consumption in the UEs is to be reduced. Such a solution uses the concept of discontinuous reception, ie the UE switches off its receiving radio (RX) periodically in order to save power. The most obvious question, of course, is how the UE decides on this periodic shutdown in order to avoid missing critical data that could be intended for it during the shutdown time. Before we go into the details, it should be noted that such a mechanism has been around since LTE via the Uu connection. In NR Uu, the UE can be configured by the network to discontinuously monitor the Downlink Physical Control Channel (PDCCH) based on the configurable parameters provided to the UE. The overall cycle of the UE performing DRX is in 1 shown. 1 Figure 10 shows an example DRX cycle 100 for NR Uu operation.

While it seems easy to extend the same functionality to SL as well, there are a number of different considerations to consider:

While Uu has a well-defined concept of directionality, e.g. uplink (UL) and DL and a master-slave-like architecture, it is not that clear when it comes to SL. For example, a UE in unicast mode can act both as a master and as a slave when it comes to providing the peer UE with the configuration of the access layer (AS). The situation is also different for groupcast and broadcast, as there is no well-defined term for a master node on the AS layer.

For Uu there are different procedures for the states CONNECTED vs. IDLE / INACTIVE. For SL, where the UE is regularly expected to operate both in coverage and out of coverage, a more uniform and robust DRX mechanism needs to be considered, taking into account both coverage and mobility of typical UEs.

There are currently two different operating modes for SL with regard to the use of resources for the transmission, e.g. mode 1 (network-controlled) and mode 2 (autonomous resource selection). For the RX UE this means that it has to potentially monitor transmissions across one (or more) resource pools if it is interested in a particular SL service. This is in contrast to the UE which monitors specific PDCCH opportunities for Uu based on the DRX configuration provided by the network. Even if the UE can be provided with a corresponding configuration for SL, it is an open question how the UE can be restricted to monitoring certain resource pools or time-frequency resources within a certain pool when performing DRX.

To this end, this disclosure attempts to address the above problems and to discuss how a DRX mechanism can be supported over SL, taking into account the set of services described in the previous section.

A general description of SL-DRX operation

• - ON-DURATION: Dauer, die das UE nach dem Aufwachen wartet, um den Physikalischen Sidelink-Steuerungskanal (Physical Sidelink Control Channel - PSCCH) zu überwachen. Wenn das UE erfolgreich einen PSCCH dekodiert, die SL Control Information (SCI) dekodiert und feststellt, dass es am Empfang der entsprechenden Übertragung über den Physikalischen Sidelink-Geteilter-Kanal (Physical Sidelink Shared Channel - PSSCH) interessiert ist, bleibt das UE wach und startet den Inaktivitäts-Timer;
• - INAKTIVITÄTS-TIMER: Dauer, die das UE wartet, um einen PSCCH erfolgreich zu dekodieren, ab der letzten erfolgreichen Dekodierung des PSCCH, andernfalls kann es wieder in den Ruhezustand gehen. Das UE startet den Inaktivitäts-Timer nach einer einzelnen erfolgreichen Dekodierung eines PSCCH neu (und bestimmt, den PSSCH auf Basis der SCI zu dekodieren). Dies kann anwendbar sein für:
  • o Entweder nur für die erste/erstmalige Übertragung
  • o Oder sowohl für die erste Übertragung als auch für alle nachfolgenden Übertragungen
• - RETRANSMISSION-TIMER: Dauer, bis eine erneute Übertragung über PSSCH erwartet werden kann,
• - CYCLE: gibt die periodische Wiederholung der Einschaltdauer gefolgt von einer möglichen Inaktivitätsdauer an, z.B. die gesamte DRX-Zyklusdauer;
• - ACTIVE-TIME: Zeitdauer, die die UE PSCCH überwacht. Dies weist die „Ein-Dauer“ des DRX-Zyklus auf, die Zeit, in der die UE kontinuierlichen Empfang durchführt, während der Inaktivitäts-Timer noch nicht abgelaufen ist, und die Zeit, in der das UE kontinuierlichen Empfang durchführt, während sie auf eine erneute Übertragungsmöglichkeit wartet.
• - INAKTIVZEIT: die Zeitdauer, in der das UE die Überwachung des PSCCH überspringt und das Funkgerät ausgeschaltet ist. Effektiv das Komplement der Aktivzeit.

The generalized operation of Uu can be adapted for SL, whereby a typical SL-DRX operation can be characterized by:

• ON-DURATION: Duration the UE waits after waking up to monitor the Physical Sidelink Control Channel (PSCCH). If the UE successfully decodes a PSCCH, decodes the SL Control Information (SCI) and determines that it is interested in receiving the corresponding transmission over the Physical Sidelink Shared Channel (PSSCH), the UE stays awake and starts the inactivity timer;
• - INACTIVITY TIMER: Duration that the UE waits in order to successfully decode a PSCCH, from the last successful decoding of the PSCCH, otherwise it can go into the idle state again. The UE restarts the inactivity timer after a single successful decoding of a PSCCH (and determines to decode the PSSCH based on the SCI). This can be applicable for:
  • o Either only for the first / first-time transfer
  • o Or both for the first transmission and for all subsequent transmissions
• - RETRANSMISSION-TIMER: Duration until a new transmission via PSSCH can be expected,
• - CYCLE: gives the periodic repetition of the duty cycle followed by a possible one Inactivity duration, e.g. the total DRX cycle duration;
• - ACTIVE-TIME: Duration monitored by the UE PSCCH. This includes the "on-duration" of the DRX cycle, the time the UE performs continuous reception while the inactivity timer has not expired, and the time the UE performs continuous reception while on another transmission option is waiting.
• - INACTIVE TIME: the length of time the UE skips the monitoring of the PSCCH and the radio is switched off. Effectively the complement of the active time.

Aspect 1: Treatment of the inactivity timer taking into account the need for PSCCH decoding

It should be noted that, in contrast to the Uu case, it is very likely that the UE is not interested in decoding the PSSCH or in further monitoring of the PSCCH (e.g. broadcast transmissions) even after successful decoding of an SCI from another UE . In this case, it is advisable to let the UE run the inactivity timer instead of resetting it. 2 below shows the similar overall cycle 206 for SL DRX 204 based on the in 1 where the UE decides to do DRX after sending the SCI over PSCCH 202 has read.

Aspect 2: Occupation type and / or resource allocation mode specific DRX operation

• - Für Unicast, bei dem eine dedizierte LTE-V2X (PC5) Radio Resource Control (RRC)-Verbindung zwischen den Peer UEs über SL aufgebaut wird, geht es zunächst um den Austausch der relevanten Konfiguration, die in diesem Fall auch die DRX-bezogene Konfiguration aufweist. Die UEs müssen dann diese Informationen in irgendeiner Weise vermitteln, so dass sie den DRX-Zyklus kennen und wissen, wann sie es sich jeweils leisten können, das Funkgerät abzuschalten (z.B. in den Schlafmodus/inaktive Zeit zu gehen), um Energie zu sparen.
  • ◯ Typischerweise ist in diesem Fall der Signalisierungsfluss 300 in 3 dargestellt. Diese Vermittlung kann durchgeführt werden, wenn das Peer-UE 304 eine PC5-RRC-Rekonfigurationsvollständigkeitsnachricht 308 an das initiierende UE 302 sendet, gemäß der Art und Weise, wie die generalisierte AS-Konfiguration in Rel-16 V2X vermittelt wird.
  • ◯ Alternativ, da die Uu-DRX-Konfiguration vom Netzwerk für jede UE unabhängig bereitgestellt wird, besteht eine weitere Option darin, sich darauf zu verlassen, dass das Netzwerk auch die SL-DRX-Konfiguration bereitstellt. In diesem Fall kann jedes UE die SL DRX-Konfiguration, die von seinem diensterbringenden Next Generation Node-B (gNB) bereitgestellt wird, unabhängig nutzen, ohne sich gegenseitig zu informieren.
• - Im Falle von Groupcast geht Rel-16 V2X davon aus, dass die Gruppenerstellung und - verwaltung von den oberen Schichten (z.B. oberhalb der AS-Schicht) durchgeführt wird, so dass die AS-Schicht die Identität der Gruppenmitglieder nur kennen kann, wenn sie von den oberen Schichten bereitgestellt wird. Wenn dies der Fall ist, kann die SL DRX-Konfiguration von den Gruppenmitgliedern gemeinsam genutzt werden. Wie im Fall von Unicast kann dies geschehen:
  • ◯ Entweder durch die Gruppenmitglieder selbst (typischerweise der Gruppenleiter), wobei der Gruppenleiter die gewünschte SL DRX-Konfiguration, die für die gesamte Gruppe verwendet werden soll, mit neu definierten gruppencast-spezifischen PC5-RRC-Nachrichten angeben kann
  • ◯ Alternativ kann die Konfiguration zwischen den UEs der Gruppenmitglieder ausgetauscht werden, indem einzelne Unicast-Links über PC5 eingerichtet werden.
  • ◯ Oder sie ist, ähnlich wie im Unicast-Fall, jedem Gruppenmitglied einzeln vom Netz bereitgestellt.
• - Beim Broadcast sind die Dinge etwas einfacher, da das UE selbst bestimmen kann, ob es an dem Empfang von SL-Übertragungen für einen Dienst interessiert ist. Daher kann die DRX-Konfiguration sehr viel flexibler sein als im Fall von Uu. So kann z.B. ein Fußgänger-UE (P-UE), das kein Interesse am Empfang von SL-Rundfunkübertragungen hat, wenn es stationär ist, einfach das Funkgerät ausschalten, um Energie zu sparen.

The next aspect to consider is how the DRX operation is to be affected by the occupancy type and operating mode of the UE. In Rel-16 V2X, SL operation can be carried out in a unicast, groupcast or broadcast type. In any case, there are several aspects to consider if SL DRX is applicable:

• - For unicast, in which a dedicated LTE-V2X (PC5) Radio Resource Control (RRC) connection is established between the peer UEs via SL, the first thing to do is to exchange the relevant configuration, which in this case also includes the DRX-related configuration Has configuration. The UEs then have to convey this information in some way so that they know the DRX cycle and when they can afford to switch off the radio (e.g. go into sleep mode / inactive time) in order to save energy.
  • ◯ The signaling flow is typical in this case 300 in 3 shown. This mediation can be performed when the peer UE 304 a PC5 RRC reconfiguration complete message 308 to the initiating UE 302 sends, according to the way in which the generalized AS configuration is conveyed in Rel-16 V2X.
  • ◯ Alternatively, since the network provides the Uu-DRX configuration for each UE independently, another option is to rely on the network to also provide the SL-DRX configuration. In this case, each UE can use the SL DRX configuration provided by its serving Next Generation Node-B (gNB) independently without informing each other.
• - In the case of Groupcast, Rel-16 V2X assumes that the group creation and management is carried out by the upper layers (e.g. above the AS layer) so that the AS layer can only know the identity of the group members if they provided by the upper layers. If this is the case, the SL DRX configuration can be shared among the group members. As in the case of unicast, this can be done:
  • ◯ Either by the group members themselves (typically the group leader), whereby the group leader can specify the desired SL DRX configuration to be used for the entire group with newly defined group cast-specific PC5-RRC messages
  • ◯ Alternatively, the configuration can be exchanged between the UEs of the group members by setting up individual unicast links via PC5.
  • ◯ Or, similar to the unicast case, it is made available to each group member individually from the network.
• Things are a little simpler with broadcast as the UE can determine for itself whether it is interested in receiving SL transmissions for a service. Therefore, the DRX configuration can be much more flexible than in the case of Uu. For example, a pedestrian UE (P-UE) that is not interested in receiving SL radio transmissions when it is stationary can simply switch off the radio to save energy.

• - Für UEs, die im Modus 1 betrieben werden, war das allgemeine Prinzip bisher, sich auf die Netzwerkkonfiguration für fast die gesamte Konfiguration der AS-Schicht (gemäß Nachrichten-Authentikationscode (Message Authentication Code - MAC), Funkverbindungssteuerung (Radio Link Control - RLC) und Paketdaten-Konvergenzprotokoll (Packet Data Convergence Protocol - PDCP)) und die Dienstgüte (QoS) zu verlassen. Gemäß einer ähnlichen Überlegung denken wir, dass dasselbe auch für die DRX-Konfiguration anwendbar sein kann. Insbesondere in Kombination mit den oben vorgeschlagenen Lösungen wäre der einfachste Weg, dass die SL-DRX-Konfiguration dem UE über Uu-RRC-Signalisierung für Modus 1 bereitgestellt wird. Gemäß Unicast kann diese Konfiguration entweder als Teil der AS-Schicht-Konfiguration an das Peer-UE während des PC5-Verbindungsaufbaus weitergeleitet werden oder über eine neu definierte Nachricht wie RRCInformationSidelink/RRCDRXRequestSidelink. In beiden Fällen kann davon ausgegangen werden, dass beide UEs die DRX-Muster des jeweils anderen kennen. Das gleiche Prinzip kann auch für Groupcast angewendet werden; aber angesichts des Signalisierungsaufwands, der für den Austausch der DRX-Konfiguration erforderlich ist, besteht eine Alternative darin, dass das Netzwerk diese Konfiguration nur dem UE des Gruppenkopfes bereitgestellt ist, das diese Konfiguration anschließend an alle Gruppenmitglieder weiterleitet. Dies hat auch zur Folge, dass alle Gruppenmitglieder die gleiche SL-DRX-Konfiguration und -Parameter usw. verwenden würden, was seine eigenen Vor- und Nachteile hat. Für Broadcast gelten ähnliche Prinzipien wie für Unicast, mit der Ausnahme, dass das UE aufgrund der inhärenten Natur des Best-Effort-Betriebs keine Notwendigkeit zum Austausch oder zur Weiterleitung an andere UEs besteht.

The other factor to consider for SL DRX is the mode of resource allocation. There are two SL resource allocation modes supported: mode 1 and mode 2. In mode 1, the SL resource allocation is provided by the network. In mode 2, the UE decides on the SL transmission resources and the timing in the resource pool. This is also related to the coverage status of the UE, since mode 1 clearly only applies to UE in CONNECTED mode, while mode 2 is applicable to CONNECTED, IDLE / INACTIVE and out-of-coverage.

• - For UEs that are operated in mode 1, the general principle so far has been to focus on the network configuration for almost the entire configuration of the AS layer (according to the message authentication code (MAC), radio link control (RLC ) and Packet Data Convergence Protocol (PDCP) and quality of service (QoS). Based on a similar consideration, we think that the same can also be applicable for the DRX configuration. In particular in combination with the solutions proposed above, the simplest way would be for the SL-DRX configuration to be provided to the UE via Uu-RRC signaling for mode 1. According to unicast, this configuration can either be forwarded as part of the AS layer configuration to the peer UE during the PC5 connection setup or via a newly defined message such as RRCInformationSidelink / RRCDRXRequestSidelink. In both cases, it can be assumed that both UEs know each other's DRX patterns. The same principle can also be used for Groupcast; but in view of the signaling overhead that is required for the exchange of the DRX configuration, an alternative is that the network is only provided with this configuration to the UE of the group head, which then forwards this configuration to all group members. This also means that all group members would use the same SL-DRX configuration and parameters, etc., which has its own advantages and disadvantages. Similar principles apply to broadcast as to unicast, with the exception that, due to the inherent nature of best effort, the UE has no need to exchange or relay to other UEs.

Since for mode 2, in contrast to mode 1, no assumptions can be made about the coverage of the UE, the general direction in order to obtain the AS-layer configuration for the SL operation was to the SIB signaling for the IDLE / INACTIVE mode and pre-configured for UEs out of coverage. This two-part type of configuration acquisition based on operating mode and coverage is important for UEs in vehicles because of their movement profile. Therefore, a similar mechanism can be adopted for the provision of the SL-DRX configuration.

It can also be argued that, unlike some of the parameters associated with the SL MAC / RLC / PDCP configuration, the SL DRX mainly affects the power consumption profile of the individual UE and can be left to the UE implementation. In this case, a UE that is involved in the unicast / groupcast operation can simply exchange a self-created DRX configuration with the peer UE / group members

Aspect 3: SL Bandwidth Part (BWP) and Resource Pool Monitoring

The procedures for resource allocation for transmission and monitoring for reception via SL differ fundamentally from Uu. Since the SL operation takes place via an essentially shared medium, in the case of mode 2 operation there is competition between the UEs for the resources to carry out the transmission. The reception via SL is also dependent on monitoring the control channel (PSCCH) for transmissions from other UEs and decoding the PSSCH accordingly. The two channels in addition to the Physical Sidelink Feedback Control Channel (PSFCH) have a resource pool that essentially has a number of time-frequency resources that according to FIG 4th are divided into specific slots. 4th is an example of the SL resource pool design 400 in Rel-16 V2X.

According to 5 the PSCCH applies a two-stage SCI design in Rel-16 V2X 500 at. The first stage 502 consists of the more important information needed for detection and includes the SCI send priority, PSSCH resource allocation, resource reservation period and DMRS-related information. The second stage 504 SCI contains more specific information for decoding the PSSCH, such as the process identifier (ID) of the hybrid automatic repeat request (HARQ), the network device interface (NDI) and the source and target IDs of layer 1 (L1). The UE uses the 2-stage 504 SCIs to correctly decode the data transmission intended for itself. A generalized visualization of the foregoing is in 5 shown.

1. 1. Das UE kann die Überwachung des gesamten PSCCH einstellen, d.h. sowohl die erste als auch die zweite Stufe SCI werden während der Aus-Dauer nicht dekodiert. Dies ist das engste Analogon zum Uu-ähnlichen Betrieb.
2. 2. Das UE kann die SCI der ersten Stufe überwachen und dann, basierend auf der Prioritätsanzeige und der Ressourcenreservierung darin, die Dauer bestimmen, für die das Funkgerät ausgeschaltet werden kann. Insbesondere kann ein Schwellenwert für die SCI-Priorität definiert und für das UE eingerichtet werden, so dass das UE nur dann entscheidet, das Funkgerät abzuschalten, wenn die Priorität niedriger als der Schwellenwert ist. In diesem Fall schaltet das UE das Funkgerät so lange aus, bis die Ressource freigegeben, d.h. nicht mehr reserviert ist. Dadurch wird sichergestellt, dass das UE immer in der Lage ist, periodische Übertragungen mit hoher Priorität zu empfangen, während es DRX durchführt.

There are at least two different options that can be used for DRX operation:

1. 1. The UE can stop monitoring the entire PSCCH, ie neither the first nor the second level SCI are decoded during the off period. This is the closest analog of the Uu-like operation.
2. 2. The UE can monitor the SCI of the first stage and then, based on the priority indication and the resource reservation therein, determine the duration for which the radio can be switched off. In particular, a threshold value for the SCI priority can be defined and set up for the UE so that the UE only decides to switch off the radio device if the priority is lower than the threshold value. In this case, the UE switches the radio off until the resource is released, ie no longer reserved. This ensures that the UE is always able to receive periodic high priority transmissions while it is performing DRX.

The second facet of this aspect concerns the SL BWP operation. In Rel-16 V2X only a single SL BWP is supported and a single carrier operation is agreed. In the future, it is expected that multi-carrier operation will be supported for SL, with the focus being on the support of services with increased requirements in terms of data rate and reliability. To this end, we think that the SL-DRX mechanism can follow the Uu behavior, with each MAC unit performing the DRX independently for the active BWP.

the 6-8 illustrate various systems, devices, and components that can implement aspects of the disclosed aspects.

6th illustrates a network 600 according to various aspects. The network 600 can be operated in a way that complies with the technical specifications of 3GPP for LTE or 5G / NR systems. However, the example aspects are not restricted in this regard, and the aspects described can also apply to other networks that benefit from the principles described here, such as future 3GPP systems or the like.

The network 600 can a UE 602 which can have any mobile or non-mobile computing device that is configured to connect to a radio access network (RAN) 604 Communicate over an over-the-air connection. The UE 602 a smartphone, a tablet computer, a portable computing device, a desktop computer, a laptop computer, an infotainment device in the vehicle, an entertainment device in the vehicle, an instrument cluster, a head-up display device, an onboard Diagnostic device, a mobile dashtop device, mobile data terminal, electronic engine management system, electronic / engine control unit, electronic / engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked device, machine-type communication device, M2M or D2D device, IoT device, etc., but is not limited to.

In some aspects, the network can 600 have a plurality of UEs that are directly coupled to one another via an SL interface. The UEs can be machine-to-machine (M2M) / device-to-device (D2D) devices that communicate over physical SL channels, such as, but not limited to, Physical Sidelink Broadcast Channel - PSBCH), Physical Sidelink Downlink Channel (PSDCH), PSSCH, PSCCH, PSFCH, etc.

In some aspects, the UE 602 additionally communicate with an access point (AP) 606 via an over-the-air connection. The AP 606 can manage a wireless local area network (WLAN) connection, which can be used to take part / all of the network traffic from the RAN 604 to relieve. The connection between the UE 602 and the AP 606 can conform to any IEEE 802.11 protocol, with the AP 606 could be a Wireless Fidelity (Wi-Fi®) router. In some aspects, the UE 602 , the RAN 604 and the AP 606 use a cellular WLAN aggregation (e.g. LTE-WLAN-Aggregation (LWA) / LTE / WLAN Radio Level Integration with IPsec Tunnel (LWIP)). With cellular WLAN aggregation, the UE 602 from the RAN 604 configured to use both cellular and WiFi resources.

The RAN 604 can have one or more access nodes, e.g. the access network (AN) 608 . AT 608 can use air interface protocols for the UE 602 terminate by having access layer protocols including RRC, PDCP, RLC, MAC and L1 protocols. In this way, the AN 608 a data / voice connection between the channel number (CN) 620 and the UE 602 enable. In some aspects, the AN 608 be implemented in a discrete device or as one or more software entities running on server computers, for example as part of a virtual network that can be referred to as a cloud radio access network (CRAN) or a virtual baseband unit pool . The AN 608 can be referred to as base station (BS), gNB, RAN node, eNB, ngevolved NodeB (eNB), NodeB, RSU, transceiver point (TRxP), transceiver point (TRP), etc. The AN 608 can be a macro cell base station or be a base station with low power in order to provide femtocells, picocells or similar cells that have smaller coverage areas, lower user capacities or higher bandwidths compared to macro cells.

In aspects in which the RAN 604 has a plurality of ANs, these can be accessed via an X2 interface (if the RAN 604 is an LTE-RAN) or an Xn interface (if the RAN 604 a 5G-RAN) must be coupled to one another. The X2 / Xn interfaces, which in some aspects can be divided into control / user plane interfaces, can enable the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination etc.

The ANs of the RAN 604 can each manage one or more cells, cell groups, component carriers, etc. to the UE 602 provide an air interface for network access. The UE 602 may be connected to a plurality of cells simultaneously from the same or different ANs of the RAN 604 to be provided. For example, the UE 602 and the RAN 604 Use carrier aggregation to provide the UE 602 enable connection to a plurality of component carriers, each corresponding to a P-cell or Scell. In dual connectivity scenarios, a first AN can be a master node providing a master cell group (MCG) and a second AN can be a secondary node providing a secondary cell group (SCG). The first / second ANs can be any combination of eNB, gNB, ng-eNB, etc.

The RAN 604 can provide the air interface via a licensed spectrum or an unlicensed spectrum. For operation in the unlicensed spectrum, the nodes LAA, eLAA and / or feLA mechanisms for licensed assisted access (LAA), the extended LAA (eLAA) and / or feLAA mechanisms based on the carrier aggregation (CA) - Use technology with PCells / Scells. Prior to accessing the unlicensed spectrum, the nodes can perform media / carrier detection operations based, for example, on a listen-before-talk (LBT) protocol.

In V2X scenarios, the UE 602 or AN 608 be or act as an RSU, which can refer to any traffic infrastructure unit used for V2X communication. An RSU can be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by a UE can be referred to as a “UE-Type RSU”; an eNB can be referred to as "eNB type RSU"; a gNB can be referred to as "gNB type RSU"; and the same. In one example, an RSU is a computing device that is coupled to radio frequency circuitry located on the roadside that provides connectivity to the UEs of passing vehicles. The RSU may also have internal data storage circuitry to store intersection geometry, traffic statistics, media, and applications / software for capturing and controlling ongoing vehicle and pedestrian traffic. The RSU can provide the very low latency communication required for high speed events such as accident avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU can provide other cellular / WLAN communication services. The components of the RSU can be housed in a weatherproof housing suitable for outdoor installation and can have a network interface control unit to provide a wired connection (e.g. Ethernet) to a traffic light controller or a backhaul network.

In some aspects, the RAN 604 an LTE-RAN 610 with eNBs, for example eNB 612. The LTE RAN 610 An LTE air interface can be provided with the following features: SCS of 15 kHz; Control Plane (CP) Orthogonal Frequency Division Multiplexing (OFDM) waveform for Downlink (DL) and Single Carrier Frequency Division Multiple Access (SC-FDMA) waveform for Uplink (UL); Turbo codes for data and Tail-Biting Convolutional Codes (TBCC) for control; etc. The LTE air interface can rely on the CSI reference signal (CSI-RS) for CSI acquisition and beam management; the PDSCH / PDCCH demodulation reference signal (DMRS) for the PDSCH / PDCCH demodulation; and to the cell reference signal (CRS) for cell search and initial acquisition, channel quality measurements and channel estimation for coherent demodulation / detection at the UE. The LTE air interface can work on bands below 6 GHz.

In some aspects, the RAN 604 an NG-RAN 614 with gNBs, for example gNB 616, or ng-eNBs, for example ng-eNB 618 , be. The gNB 616 can connect to 5G-capable UEs via a 5G-NR interface. The gNB 616 can connect to a 5G core via an NG interface, which can have an N2 interface or an N3 interface. The ng-eNB 618 can also connect to the 5G core via an NG (Next Generation) interface, but can be connected to a UE via an LTE air interface. The gNB 616 and the ng-eNB 618 can connect to one another via an Xn interface.

In some aspects, the NG interface can be split into two parts, an NG-U interface (NG-U), which carries traffic data between the nodes of the NG-RAN 614 and a user level (User Plane Function - UPF) 648 (e.g. N3 interface) transmits, and an NG-C interface (NG-C), which is a signaling interface between the nodes of the NG-RAN 614 and an Access and Mobility Management Function (AMF) 644 (e.g. N2 interface) is.

The NG-RAN 614 can provide a 5G NR air interface with the following features: variable SCS; CP-OFDM for DL, CP-OFDM and Discrete Fourier Transform spread OFDM (DFT-s-OFDM) for UL; Polar, repetition, simplex and reed-Muller codes for control and LDPC for data. Similar to the LTE air interface, the 5G-NR air interface can be based on CSI-RS, PDSCH / PDCCH DMRS. The 5G-NR air interface cannot use CRS, but can use PBCH DMRS for PBCH demodulation, Phase Tracking Reference Signals (PTRS) for phase tracking for PDSCH, and Tracking Reference Signal for time tracking. The 5G NR air interface can operate on FR1 bands, which have bands below 6 GHz, or FR2 bands, which have bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may comprise a synchronization signal block (SSB) which is a portion of a downlink resource grid that comprises the primary synchronization signal / sideband synchronization signal / physical broadcast channel (PSS / SSS / PBCH).

In some aspects, the 5G NR air interface can use BWPs for different purposes. For example, BWP can be used for dynamic subcarrier synchronization (SCS) adjustment. For example, the UE 602 be set up with several BWPs, each BWP configuration having a different SCS. If the UE 602 a BWP change is indicated, the SCS of the transfer is also changed. Another use case example for BWP relates to energy saving. In particular, several BWPs can be used for the UE 602 be set up with a different number of frequency resources (e.g. Physical Resource Blocks - PRBs) to support data transmission under different traffic load scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with a low traffic load and at the same time enables power savings at the UE 602 and in some cases with the gNB 616 . A BWP that contains a larger number of PRBs can be used for scenarios with a higher traffic load.

The RAN 604 is communicative with the CN 620 coupled, which has network elements, the various functions to support data and telecommunication services for customers / subscribers (e.g. users of the UE 602 ) provide. The components of the CN 620 can be implemented in a physical node or in separate physical nodes. In some aspects, Network Functions Virtualization (NFV) can be used to implement some or all of the functions performed by the network elements of the CN 620 provided to virtualize on physical computing / storage resources in servers, switches, etc. A logical instantiation of the CN 620 can be referred to as a network slice, and a logical instantiation of part of the CN 620 can be referred to as a network sub-slice.

In some aspects, the CN 620 an LTE CN 622 which can also be referred to as Evolved Packet Core (EPC). The LTE CN 622 can a Mobility Management Entity (MME) 624 , a serving gateway (SGW) 626 , a serving GPRS support node (SGSN) 628 , a home subscriber server (HSS) 630 , a packet data network gateway (PGW) 632 and a Policy Control and Charging Rules Function (PCRF) 634 that are coupled to one another via interfaces (or "reference points"), as shown. The functions of the elements of the LTE CN 622 can be briefly introduced as follows.

The MME 624 can implement mobility management functions to a current location of the UE 602 track to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

The SGW 626 can terminate an S1 interface to the RAN and data packets between the RAN and the LTE CN 622 routes. The SGW 626 can be a local mobility anchor point for inter-RAN node handover and can also provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful intercept, charging, and enforcing some policies.

The SGSN 628 can find the location of the UE 602 track and perform security functions and access control. In addition, the SGSN 628 the inter-EPC node signaling for mobility between different ones Perform radio access technology (RAT) networks; the selection of the packet data network (PDN) and the S-GW according to the specifications of the MME 624 ; the MME selection for handover; etc. The S3 reference point between the MME 624 and the SGSN 628 can enable the exchange of user and bearer information for inter-3GPP access network mobility in the idle / active state.

The HSS 630 may have a database for network users, including subscription-related information to aid in the handling of communication sessions by the network entities. The HSS 630 can provide support for routing / roaming, authentication, authorization, name / addressing resolution, location dependencies, etc. An S6a reference point between the HSS 630 and the MME 624 can transfer subscription and authentication data for authentication / authorization of user access to the LTE CN 620 enable.

The PGW 632 can be an SGi interface to a data network (DN) 636 schedule that an application / content server 638 may have. The PGW 632 can send data packets between the LTE CN 622 and the data network 636 forward onto. The PGW 632 can with the SGW 626 be coupled via an S5 reference point in order to facilitate tunneling at the user level and tunnel management. The PGW 632 may also have a node for the enforcement of guidelines and the collection of charge data (eg Charging Enforcement Function (PCEF)). In addition, the SGi reference point between the PGW 632 and the data network 636 an operator-external public, a private PDN or an operator-internal packet data network, e.g. for the provision of IMS services. The PGW 632 can with a PCRF 634 be coupled via a Gx reference point.

The PCRF 634 is the element of policy and charge control of the LTE CN 622 . The PCRF 634 can communicate with the app / content server 638 be coupled to determine suitable QoS and charging parameters for service flows. The PCRF 632 can provide associated rules in a PCEF (via the Gx reference point) with a suitable traffic flow template (TFT) and QoS Class of Identifier (QCI).

In some aspects, the CN 620 a 5GC 640 be. The 5GC 640 can an authentication server function (AUSF) 642 , AMF 644 , Session management function (SMF) 646 , User Plane Function (UPF) 648 , Network Slice Selection Function (NSSF) 650 , Network exposure function (NEF) 652 have Network Function (NF) Repository Function (NRF) 654 , Policy Control Function (PCF) 656 , Unified Data Management (UDM) 658 and Application Function (AF) 660 Coupled with one another via interfaces (or "reference points") as shown. The functions of the elements of the 5GC 640 can be briefly presented as follows.

The AUSF 642 can provide data for the authentication of the UE 602 store and handle authentication-related functions. The AUSF 642 can enable a common authentication framework for different types of access. In addition to communicating with other elements of the 5GC 640 Via reference points, as shown, the AUSF 642 have a Nausf service based interface.

The AMF 644 there can be other functions of the 5GC 640 enable with the UE 602 and the RAN 604 to communicate and notify of mobility events related to the UE 602 to subscribe. The AMF 644 can be used for registration management (e.g. for the registration of the UE 602 ), connection management, availability management, mobility management, lawful interception of AMF-related events and access authentication and authorization. The AMF 644 can facilitate the transport of Session Management (SM) messages between the UE 602 and the Session Management Function (SMF) 646 and act as a transparent proxy for routing SM messages. AMF 644 can also transport Short Message Service (-SMS) messages between the UE 602 and an SMS function (SMSF). AMF 644 can with the AUSF 642 and the UE 602 interact to perform various security anchor and context management functions. In addition, AMF 644 be a termination point of a RAN-CP interface, which is an N2 reference point between the RAN 604 and the AMF 644 can have or be; and the AMF 644 can be a termination point of the NAS ( N1 ) Signaling and performing NAS encryption and integrity protection. The AMF 644 can also do NAS signaling with the UE 602 support via an N3 interworking function (IWF) interface.

The SMF 646 can be responsible for SM (e.g. session setup, tunnel management between user plane function - UPF) 648 and on 608 ); Assignment and management of UE IP addresses (including optional authorization); Selection and control of the user plane (UP) function; Configure traffic control on UPF 648 to get traffic to the right destination; Termination of Interfaces to control functions; Control of parts of policy enforcement, billing and QoS; legally compliant interception (for SM events and interface to the Layer Indicator (LI) system); Termination of SM parts of NAS messages; Downlink data notification; Initiation of AN-specific SM information that is sent via AMF 644 via N2 to AN 608 be sent; and determining the session and service continuity mode (SSC) of a session. SM can refer to the management of a Protocol Data Unit (PDU) session, and a PDU session or "session" can refer to a PDU link service that enables the exchange of PDUs between the UE 602 and the data network 636 provides or enables.

The UPF 648 Can be used as an anchor point for intra-RAT and inter-RAT mobility, as an external PDU session connection point to the data network 636 and serve as a branch point to support multi-homed PDU sessions. The UPF 648 can also perform packet routing and forwarding, perform packet inspection, enforce the part of the policy rules for the user level, intercept packets lawfully (UP collection), create traffic usage reports, perform QoS handling for a user level (e.g. packet filtering, gating, UL / DL rate enforcement) ), Carry out uplink traffic check (e.g. assignment of service data flow to QoS (SDF-to-QoS)), carry out packet marking on the transport level in the uplink and downlink and carry out downlink packet buffering and triggering of downlink data notifications. UPF 648 may have an uplink classifier to support the routing of traffic flows to a data network.

The NSSF 650 can select a set of network slice instances that the UE 602 serve. The NSSF 650 can also determine allowed Network Slice Selection Assistance Information (NSSAI) and the mapping to the subscribed single NSSAIs (S-NSSAIs), if necessary. The NSSF 650 can also determine the AMF rate required to operate the UE 602 to be used, or a list of candidate AMFs based on appropriate configuration and possibly by querying the NRF 654 . The selection of a set of network slice instances for the UE 602 can from the AMF 644 , where the UE 602 is registered by interacting with the NSSF 650 triggered, which can lead to a change in the AMF. The NSSF 650 can with the AMF 644 interact via an N22 reference point; and it can communicate with another NSSF on a visited network via an N31 reference point (not shown). In addition, the NSSF 650 have an Nnssf service based interface.

The Network Exposure Function (NEF) 652 can services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, AFs (e.g. AF 660 ), Edge computing or fog computing systems etc. securely deploy. In such aspects, the NEF 652 authenticate, authorize or throttle the AFs. The NEF 652 can also provide information related to the AF 660 and translate information exchanged with internal network functions. For example, the NEF 652 Translate between an AF service identifier and internal 5GC information. The NEF 652 can also receive information from other NFs based on the exposed capabilities of other NFs. This information can be found in the NEF 652 as structured data or in a data storage NF using standardized interfaces. The stored information can then be used by the NEF 652 passed on to other NFs and AFs or used for other purposes, such as analysis. In addition, the NEF 652 have an Nnef service based interface.

The NRF 654 can support service discovery functions, receive NF discovery requests from NF instances and provide the information of the discovered NF instances to the NF instances. The NRF 654 also manages information about available NF instances and their supported services. As used herein, the terms “instantiating”, “instantiating” and the like can relate to the creation of an instance, and an “instance” can relate to a specific occurrence of an object that can occur, for example, during the execution of program code. In addition, the NRF 654 have the nnrf service based interface.

The Policy Control Function (PCF) 656 can provide control level functions to enforce policy rules and can also support a unified policy framework to control network behavior. The PCF 656 Can also implement a front end for access to subscription information that is used for policy decisions in a Unified Data Repository (UDR) of Unified Data Management (UDM) 658 are relevant. In addition to communicating with functions via reference points, as shown, the PCF 656 an npcf service based interface.

The UDM 658 can manage subscription-related information to facilitate the handling of communication sessions by the Support network entities, and can subscribe data to the UE 602 to save. For example, subscription data can be shared between the UDM 658 and the AMF 644 communicated. The UDM 658 can have two parts, an application front end and a UDR. The UDR can store subscription data and policy data for the UDM 658 and the PCF 656 and / or structured data for exposure and application data (including PFDs for application discovery, application requirement information for multiple UEs 602 ) for the NEF 652 to save. The Nudr service-based interface can be used by the UDR 221 issued to the UDM 658 , the PCF 656 and the NEF 652 to enable access to a specific set of the stored data as well as the reading, updating (e.g. adding, changing), deleting and subscribing to notifications of relevant data changes in the UDR. The UDM may have a UDM front end (UDM-FE) that is responsible for processing credentials, site management, subscription management, and so on. Several different front ends can serve the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs the processing of authentication credentials, the handling of the user identification, the access authorization, the management of the registration / mobility and the subscription management. In addition to communicating with other NFs via reference points, as shown, the UDM 658 have the nudm service based interface.

The AF 660 can provide application influence on traffic routing, provide access to NEFs, and interact with the policy framework to control the policy.

In some aspects, the 5GC 640 Enable edge computing by selecting operator / third party services to be geographically close to a point where the UE 602 connected to the network. This can reduce latency and load on the network. To provide edge computing implementations, the 5GC 640 can use a UPF 648 near the UE 602 Select and route traffic from the UPF 648 to the data network 636 Carry out via the N6 interface. This can be based on the UE subscription data, the UE location and information provided by the AF 660 are provided. In this way, the AF 660 Influence the UPF (re-) selection and the traffic routing. Based on the deployment of the network operator, if the AF 660 is regarded as a trustworthy body, the AF 660 allow you to interact directly with relevant NFs. In addition, the AF 660 have an NF service-based interface.

The data network 636 may have various network operator services, Internet access, or third-party services that can be provided by one or more servers, such as application / content servers 638 .

7th schematically illustrates a wireless network 700 according to various aspects. The wireless network 700 can a UE 702 in wireless communication with an AN 704 exhibit. The UE 702 and the AN 704 may be similar and substantially interchangeable with like components described elsewhere herein.

The UE 702 can have a connection 706 with the AN 704 be communicatively coupled. The connection 706 is shown as an air interface to enable communicative coupling and can be consistent with cellular communication protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.

The UE 702 can be a host platform 708 having that with a modem platform 710 is coupled. The host platform 708 can be an application processing circuit 712 having that with a protocol processing circuit 714 the fashion platform 710 can be coupled. The application processing circuit 712 can have different applications for the UE 702 run, send / receive application data. The application processing circuit 712 can also implement one or more layer operations to send / receive application data to / from a data network. These layer operations can have transport (eg UDP) and Internet (eg IP) operations

The protocol processing circuit 714 may implement one or more layer operations to facilitate the transmission or reception of data over the link 706 to facilitate. The one from the protocol processing circuit 714 implemented layer operations can have, for example, MAC, RLC, PDCP, RRC and NAS operations.

The fashion platform 710 can also have a digital baseband circuit 716 that can implement one or more layer operations that are “below” layer operations that are performed by the protocol processing circuit 714 run on a network protocol stack. These operations can include, for example, PHY operations one or more HARQ-ACK functions, scrambling / descrambling, coding / decoding, layer mapping / de-mapping, modulation symbol mapping, determination of the received symbols / bit metrics, precoding / decoding of multi-antenna connections, one or more space-time -, spatial-frequency or spatial encodings, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, blind decoding of control channel signals and other related functions.

The fashion platform 710 can also have a transmission circuit 718 , a receiving circuit 720 , an RF circuit 722 and an RF front end (RFFE) 724 have one or more antenna fields 726 may contain or be associated with them. In short, the transmission circuit can 718 a digital-to-analog converter, a mixer, intermediate frequency components, etc. The receiving circuit 720 can have an analog-to-digital converter, mixer, IF components, etc.; the RF circuit 722 may include a low noise amplifier, a power amplifier, power tracking components, etc .; the RFFE 724 can have filters (e.g. surface / bulk acoustic wave filters), switches, antenna tuners, beam shaping components (e.g. phase array antenna components), etc. The selection and arrangement of the components of the transmission circuit 718 , the receiving circuit 720 , the RF circuit 722 , the RFFE 724 and the antenna panels 726 (commonly referred to as "transmit / receive components") can be specific to the details of a particular implementation, such as whether the communication is TDM or FDM, in mmWave or sub-6 GHz frequencies, etc. In some aspects, the Transmit / receive components can be arranged in several parallel transmit / receive chains, they can be accommodated in the same or in different chips / modules, etc.

In some aspects, the protocol processing circuit 714 have one or more instances of control circuits (not shown) in order to provide control functions for the transmitting / receiving components.

UE reception can be through and via the antenna fields 726 who have favourited RFFE 724 who have favourited RF circuit 722 , the receiving circuit 720 who have favourited digital baseband circuit 716 and the protocol processing circuit 714 getting produced. In some aspects the antenna fields 726 a transfer from the contractor 704 by receive beamforming of signals received from a plurality of antenna / antenna elements of the one or more antenna arrays 726 be received.

A UE transmission can through and over the protocol processing circuit 714 who have favourited digital baseband circuit 716 , the transmission circuit 718 who have favourited RF circuit 722 who have favourited RFFE 724 and the antenna fields 726 being constructed. In some aspects, the transmission components of the UE 704 apply a spatial filter to the data to be transmitted in order to form a transmit beam that is emitted by the antenna elements of the antenna arrays 726 is sent out.

Similar to the UE 702 can the AN 704 a host platform 728 having that with a modem platform 730 is coupled. The host platform 728 can be an application processing circuit 732 having that with a circuit for protocol processing 734 the fashion platform 730 is coupled. The modem platform may also have a digital baseband circuit 736 , a transmission circuit 738 , a receiving circuit 740 , an RF circuit 742 , an RFFE circuit 744 and antenna fields 746 exhibit. The components of the AN 704 can be similar and essentially interchangeable with components of the UE of the same name 702 be. In addition to performing data transmission / reception as described above, the components of the AN 708 perform various logical functions that have, for example, RNC functions, such as the management of radio bearers, the dynamic management of uplink and downlink radio resources and the planning of data packets.

8th 13 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and performing one or more of the methods discussed herein, according to some example aspects. In particular shows 8th a schematic representation of hardware resources 800 that have one or more processors (or processor cores) 810 , one or more storage / storage devices 820 and one or more communication resources 830 each of which has a bus 840 or other interface circuits can be communicatively coupled. For aspects where node virtualization (e.g. NFV) is used, a hypervisor 802 be executed in order to provide an execution environment for one or more network slices / sub-slices to the hardware resources 800 to use.

The processors 810 can e.g. B. a processor 812 and a processor 814 exhibit. The processors 810 For example, a central processing unit (CPU), a RISC processor (Reduced Instruction Set Computing), a CISC processor (Complex Complex Instruction Set Computing, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, an RFIC (Radio Frequency Integrated Circuit), any other processor (including those discussed herein), or any suitable Have a combination thereof.

The storage / storage devices 820 may include main memory, disk storage, or any suitable combination thereof. The memory / storage devices 820 can have any type of volatile, non-volatile or semi-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, etc.

The communication resources 830 may include control units, components or other suitable devices to communicate with one or more peripheral devices 804 or one or more databases 806 or other network elements over a network 808 to communicate. The communication resources 830 can, for example, have wired communication components (e.g. for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components and other communication components.

The instructions 850 may have software, a program, an application, an applet, an app, or other executable code to run at least one of the processors 810 cause one or more of the methods discussed here to be performed. The instructions 850 can be fully or partially in at least one of the processors 810 (e.g. in the processor's cache memory), in the storage devices 820 or in a suitable combination thereof. In addition, any part of the instructions can 850 from any combination of the peripheral devices 804 or the databases 806 to the hardware resources 800 be transmitted. The memory of the processors are accordingly 810 who have favourited Storage / Storage Devices 820 who have favourited Peripherals 804 and the databases 806 Examples of computer readable and machine readable media.

In some aspects, the electronic device (s), network (s), system (s), chip (s) or component (s), or parts or implementations thereof the 6-8 or any other figure herein may be adapted to perform one or more processes, techniques, or methods as described herein, or parts thereof. Such a process is in 9 shown.

The process at 901 may include determining SL DRX configuration information. The SL DRX configuration information can set up a UE for SL DRX communication based on the cast type of communication (e.g. unicast, groupcast or broadcast) as well as the operating mode (e.g. mode 1 or mode 2). The SL DRX can be determined by a UE receiving information from an access network or a peer UE, or it can be generated autonomously.

The process may further include using an SL based on the SL DRX configuration information at 902. For example, the UE can enter parts of a DRX cycle based on the SL DRX configuration. In some aspects, the UE can decode an SCI during a one-part and selectively enter the inactive part of the DRX cycle based on whether the SCI was sent by a particular UE of interest indicating that the SL communication contains content of particular interest, or the SCI has a priority above a predetermined threshold priority.

In this way, the UE can operate in an energy efficient manner.

For one or more aspects, at least one of the components illustrated in one or more of the preceding figures can be configured to carry out one or more operations, techniques, processes and / or methods according to the following example section. For example, as described above in connection with one or more of the preceding figures, the baseband circuit can be set up in such a way that it operates in accordance with one or more of the examples listed below. As a further example, the circuit associated with a UE, a base station, a network element, etc., as described above in accordance with one or more of the preceding figures, can be set up in such a way that it operates in accordance with one or more of the examples listed below in the example section.

EXAMPLES

Example 1 may include a method of operating a UE, the method comprising: using discontinuous reception (DRX) in NR SL communication.

Example 2 may include the method of Example 1 or any other example herein, further: maintaining an INACTIVITY timer for the Stop monitoring a PSCCH and stop decoding SCI to conserve radio power.

Example 3 may include the method of Example 2 or any other example herein, further comprising: resetting the inactivity timer or running the inactivity timer based on whether the UE is interested in certain broadcast traffic determined based on the content within the SCI will.

Example 4 may include the method of Example 1 or another example herein, further comprising: Setting up SL DRX based on occupation type.

Example 4.1 may include the method of Example 4 or another example herein, where the cast type is a unicast type and the method includes: exchanging, sending or receiving the SL DRX configuration as part of an AS layer configuration exchange during the PC5 RRC connection setup procedure.

Example 4.2 may include the method of Example 4 or any other example herein, where the cast type is a groupcast type, the UE is a group member, and the method further includes: transmitting the SL DRX configuration to member UEs via PC5 -RRC signaling in a groupcast fashion.

Example 4.3 may include the method of Example 4, or another example herein, wherein the cast type is a broadcast type, and the method includes: determining a SL-DRX configuration of the UE based on whether the UE is on a particular service is interested in a SL.

Example 4.4 may include the method of Example 4 or any other example herein, further comprising: receiving an indication of an SL DRX configuration of the UE from a network via dedicated signaling or broadcast SIB.

Example 4.5 may include the method of Example 4 or another example herein, further comprising: determining a SL DRX configuration of the UE based on a pre-configuration.

Example 5 may include the method of Example 1 or another example herein, further comprising: performing a configuration of SL DRX based on a resource allocation mode.

Example 5.1 may comprise the method of Example 5 or another example herein, wherein for the network configured resource allocation mode (e.g. mode 1) the method comprises: receiving DRX configuration information from a radio access network node via dedicated signaling.

Example 5.2 may have the method of example 5 or another example herein, wherein for the autonomous resource selection mode (e.g. mode 2) the method comprises the following: Receiving DRX configuration information from the SIB signaling when the device is in IDLE / INACTIVE Mode is located; or identify DRX configuration information based on a pre-configured setting when out of coverage.

Example 5.3 may include the method of Example 5 or any other example herein, further comprising: determining how to generate the configuration based on a UE-specific implementation.

Example 6 may have the method of Example 1 or another example herein, further comprising: Monitoring SCI via PSCCH.

Example 6.1 may include the method of Example 6 or any other example herein, further comprising: stopping monitoring of an entirety of PSCCH, e.g., both the first and second stages of SCI.

Example 6.2 may include the method of Example 6 or any other example herein, further comprising: monitoring a first stage SCI and then shutdown based on a (pre) established priority threshold and priority and the resource reservation interval monitored within the SCI of the radio until the resource reservation expires.

Example 7 includes a method of operating a UE, the method comprising: decoding SCI received during a one-duration portion of a DRX cycle to determine an identity of a sending UE; and determining, based on the identity, whether to enter an inactive portion of the DRX cycle.

Example 8 may include a method of operating a first UE, the method comprising: exchanging / sending / receiving DRX configuration information with / to / from a second UE via an SL.

Example 8.1 may include the method of Example 8, or any other example herein, with the DRX configuration information as part of building a dedicated PC5 RRC Connection can be exchanged / transmitted / received via the SL.

Example 8.1.1 may include the method of Example 8.1 or another example herein, further comprising: creating an SL-DRX configuration at the first UE; and transmitting the DRX configuration information to share the SL-DRX configuration with the second UE.

Example 8.1.2 may include the method of Example 8.1 or another example herein, further comprising: transmitting the DRX configuration information to the second UE to request an SL-DRX configuration; and receiving an acknowledgment from the second UE to confirm the SL-DRX configuration.

Example 8.1.2.1 may include the method of example 8.1.2 or another example herein, wherein the DRX configuration information is to be transmitted to the second UE in an RRC reconfiguration SL message.

Example 8.1.2.2 may include the method of Example 8.1.2 or another example herein, wherein the acknowledgment is received from the second UE in an RRC reconfiguration completion SL message.

Example 8.2 may include the method of Example 8 or another example herein, where the first UE is a group leader of a groupcast and the first UE is to send the DRX configuration information to members of the groupcast in a groupcast-specific PC5 RRC message.

Example 8.3 may include the method of Example 8 or another example where the SL communication is unicast and the DRX configuration information is sent as part of an AS layer configuration to the second UE during PC5 connection setup or using a message such as RRCInformationSidelink / RRCDRXRequestSidelink.

Example 9 may include operating a gNB, the method comprising: encoding DRX configuration information in a message; and transmitting the message to a UE to set up the UE with an SL-DRX configuration for SL communication.

Example 9.1 may include the method of Example 9, or any other example herein, where the SL-DRX configuration is for unicast or groupcast SL communication.

Example 9.2 may include the method of Example 9, or another example herein, where the SL-DRX configuration is for Groupcast SL communication and the UE is the group leader.

Example 9.3 may include the method of example 9 or another example herein, further: establishment of resource allocations for SL communication by the UE, wherein the message is transmitted via Uu RRC signaling.

Example 10 may include a method of operating a UE, the method comprising: receiving PSCCH during a one-duration portion of a DRX cycle; Decoding a first stage of the PSCCH to determine an SCI priority; Determining whether the SCI priority is greater than a predetermined threshold priority; and entering an inactive portion of the DRX cycle based on the determination of whether the SCI priority is greater than the predetermined threshold priority.

Example 11 may include apparatus that includes means for carrying out one or more elements of a method described in, or relating to, any of Examples 1-10, or any other method or process described herein.

Example 12 may include one or more non-transitory computer-readable media containing instructions to cause an electronic device, when the instructions are executed by one or more processors of the electronic device, to perform one or more elements of a method described in any of Examples 1 -10 or related thereto, or any other method or process described herein.

Example 13 may include apparatus that includes logic, modules, or circuitry to carry out one or more elements of a method described in, or relating to, any of Examples 1-10, or any other method or any of the methods described herein different process.

Example 14 may include a method, technique, or process as described in or related to any of Examples 1-10, or portions or portions thereof.

Example 15 may include an apparatus comprising: one or more processors and one or more computer readable media containing instructions that, when executed by the one or more processors, cause the one or more processors to perform the method , technique, or process as described in any of Examples 1-10 or associated with it, or to carry out parts thereof.

Example 16 may include a signal as described in or associated with any of Examples 1-10, or portions or portions thereof.

Example 17 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or associated with any of Examples 1-10, or portions thereof, or otherwise described in the present disclosure.

Example 18 may include a signal encoded with data as described or related to any of Examples 1-10, or portions or portions thereof, or otherwise described in the present disclosure.

Example 19 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described or related to any of Examples 1-10, or with sections or parts thereof, or as otherwise described in the present disclosure.

Example 20 may include an electromagnetic signal carrying computer-readable instructions, the execution of the computer-readable instructions by one or more processors serving to cause the one or more processors to use the method, techniques, or process according to any of Examples 1- 10 or parts thereof.

Example 21 may comprise a computer program containing instructions, the execution of the program by a processing element serving to cause the processing element to use the method, technique or process as described in or related to any of Examples 1-10, or To carry out parts of it.

Example 22 may include a signal on a wireless network as shown and described herein.

Example 23 may include a method of communicating on a wireless network as shown and described herein.

Example 24 may include a system for providing wireless communication as shown and described herein.

Example 25 may include an apparatus for providing wireless communication as illustrated and described herein.

Each of the examples described above can be combined with any other example (or any combination of examples), unless expressly stated otherwise. The foregoing description of one or more implementations has been presented for purposes of illustration and description, but is not intended to be exhaustive or to limit the scope of the aspects to the precise form disclosed. Modifications and variations are possible in light of the above teachings or can be learned from practice of the various aspects.

For the purposes of this document, the following terms and definitions apply to the examples and aspects discussed here.

As used herein, the term “circuit” refers to, is part of, or comprises hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and / or memory (shared, dedicated or group), an application-specific integrated circuit (ASIC), a field-programmable component (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic component (PLD), a complex PLD (CPLD), a PLD with high Capacity (HCPLD), a structured ASIC or a programmable SoC), digital signal processors (DSPs), etc. that are set up to provide the functionality described. In some aspects, the circuit can execute one or more software or firmware programs to provide at least a portion of the functionality described. The term "circuit" can also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. According to these aspects, the combination of hardware elements and program code can be referred to as a certain type of circuit.

As used herein, the term “processor circuit” refers to a circuit that is or is capable of sequentially and automatically executing a series of arithmetic or logical operations or recording, storing and / or transmitting digital data Part of it or has one. The processor circuit can have one or more processor cores for executing instructions and one or more memory structures for storing program and have data information. The term "processor circuit" can refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core -Processor and / or any other device capable of executing or otherwise operating computer-executable instructions such as program code, software modules and / or functional processes. The processing circuit can have further hardware accelerators, which can be microprocessors, programmable processing devices or the like. The one or more hardware accelerators can have, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms “application circuits” and / or “baseband circuits” can be viewed as synonymous with “processor circuits” and can be designated as such.

As used herein, the term “interface circuit” refers to a circuit that enables the exchange of information between two or more components or devices, is part of them, or has such a circuit. The term “interface circuit” can refer to one or more hardware interfaces, e.g. buses, I / O interfaces, interfaces of peripheral components, network interface cards and / or the like.

As used herein, the term “user device” or “UE” refers to a device with radio communication capabilities and can describe a remote user of network resources on a communication network. The term "user device" or "UE" can be used as a synonym for client, mobile device, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio, reconfigurable radio , reconfigurable mobile device, etc., and can be referred to as such. Additionally, the term “user device” or “UE” can include any type of wireless / wired device or any computing device that includes a wireless communication interface.

As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" can be used as a synonym for a networked computer, network hardware, network equipment, network node, router, switch, hub, bridge, radio network control unit, RAN device, RAN node, gateway, server, virtualized VNF, NFVI and / or The same can be considered and / or referred to.

As used herein, the term “computer system” refers to any type of interconnected electronic device, computing device, or component thereof. In addition, the term “computer system” and / or “system” can refer to various components of a computer that are communicatively coupled to one another. In addition, the term “computer system” and / or “system” can refer to a plurality of computer devices and / or a plurality of computer systems that are communicatively coupled to one another and are set up to share computer and / or network resources.

The term “device”, “computing device” or the like, as used here, refers to a computing device or computer system with program code (e.g. software or firmware) that is specially designed to provide a particular computer resource. A “virtual device” is an image of a virtual machine that is implemented by a hypervisor-equipped device that virtualizes or emulates a computing device or is otherwise designed to provide a particular computing resource.

The term "resource" as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment and / or a physical or virtual component within a specific device, such as computing devices, mechanical devices, storage space, processor / CPU -Time, processor / CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input / output operations, ports or network jacks, channel / link assignment, throughput, memory usage, storage, network, database and applications, workload units and / or the like. A “hardware resource” can refer to computing, storage and / or network resources provided by one or more physical hardware element (s). A “virtualized resource” can refer to computing, storage, and / or network resources provided by a virtualization infrastructure for an application, device, system, and so on. The term “network resource” or “communication resource” may refer to resources that computing devices / systems can access over a communication network. The term “system resources” can refer to any type of shared device that provides services and can include computer and / or network resources. System resources can be viewed as a set of related functions, network data objects or services that can be accessed via a server are considered, such system resources being located on a single host or multiple hosts and being uniquely identifiable.

The term “channel” as used here refers to any tangible or intangible transmission medium that is used to transmit data or a data stream. The term "channel" can be synonymous and / or synonymous with "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "connection", "data connection", "carrier", " Radio Frequency Carrier ”and / or any other similar term used to designate a path or medium over which data is transmitted. In addition, as used herein, the term “link” refers to a connection between two devices over a RAT for the purpose of transmitting and receiving information.

The terms “instantiating”, “instantiating” and the like used here refer to the creation of an instance. An "instance" also refers to a specific occurrence of an object that can occur, for example, during the execution of program code.

The terms “coupled”, “communicatively coupled” and derivatives thereof are used here. The term “coupled” can mean that two or more elements are in direct physical or electrical contact with one another, can mean that two or more elements are indirectly in contact with one another but still cooperate or interact with one another, and / or can mean that one or more other elements between the elements that are considered to be coupled, coupled or connected to one another. The term “directly coupled” can mean that two or more elements are in direct contact with one another. The term “communicatively coupled” can mean that two or more elements can be in contact with one another via a communication medium, including via a wired or other connection link, via a wireless communication channel or link, and / or the like.

The term “information element” refers to a structure element that contains one or more fields. The term “field” refers to the individual content of an information element or to a data element that contains content.

The term “SMTC” refers to an SSB-based measurement timing configuration that is set up with SSB-MeasurementTimingConfiguration.

The term “SSB” refers to an SS / PBCH block.

The term "primary cell" refers to the MCG cell operating on the primary frequency on which the UE is either performing the initial connection establishment procedure or initiating the connection establishment procedure.

The term “primary SCG cell” refers to the SCG cell in which the UE carries out random access when it carries out the reconfiguration procedure with sync for DC operation.

The term “secondary cell” refers to a cell that provides additional radio resources in addition to a special cell for a UE established with CA.

The term “secondary cell group” refers to the subset of serving cells that have the PSCell and zero or more secondary cells for a UE that is set up with DC.

The term “serving cell” refers to the primary cell for a UE in RRC_CONNECTED that is not set up with CA / DC as there is only one serving cell including the primary cell.

The term “serving cell” or “serving cells” refers to the set of cells that includes the special cell (s) and all secondary cells for a UE in RRC CONNECTED that is established with CA / DC.

The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise the term “Special Cell” refers to the Pcell.

QUOTES INCLUDED IN THE DESCRIPTION

This list of the documents listed by the applicant was generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Patent literature cited

• US 63/008468 [0001]

Claims (10)

Apparatus for a New Radio (NR) user equipment (UE) having a radio frequency (RF) interface and one or more processors coupled to the RF interface and configured to: Monitoring a physical sidelink control channel (PSCCH) during an active period of a discontinuous sidelink (SL) receive cycle (DRX); Decoding the PSCCH containing sidelink control information (SCI); Decoding the SCI message; and Determine whether to receive a transmission over the PSCCH based on the decoded SCI message. The device according to Claim 1 further arranged to remain active to decode the PSCCH to receive the transmission. The device according to one of the Claims 1 or 2 further configured to start an inactivity timer, the inactivity timer measuring a time since the PSCCH was last successfully decoded; and / or further set up to compare an inactivity timer measurement with an inactivity threshold. The device according to one of the Claims 1 until 3 wherein the inactivity timer measurement is greater than the inactivity threshold; is optionally further set up to switch to an inactive mode based on the comparison of the inactivity timer measurement with the inactivity threshold value. The device according to one of the Claims 1 until 4th further configured to determine a communication type and reconfigure the SL DRX based on a communication type; The device according to Claim 5 where the communication type is unicast communication; and the device is further configured to: receive an LTE-V2X radio resource controller (PC5-RRC) request message from a further UE; to set up a dedicated PC5 RRC connection between the NR UE and the further UE; receive an SL message from the further UE that has a discontinuous sidelink (SL) receive cycle (DRX) of the further UE; and reconfiguring a SL-DRX cycle of the NR UE according to the SL-DRX cycle of the further UE; optionally, the device is also set up to send an SL message to the further UE, the SL message indicating that the reconfiguration of the SL-DRX cycle of the NR UE has been completed. The device according to Claim 6 , the SL DRX cycle of the NR UE and the SL DRX cycle of the further UE coinciding. The device according to Claim 5 , the communication type being multicast communication; and the device is further configured: to determine a plurality of further UEs, wherein the plurality of further UEs are part of the multicast group; establish an LTE-V2X radio resource controller (PC5-RRC) connection between the NR UE and each of the plurality of other UEs; and send an SL message including SL-DRX cycle reconfiguration; optionally, the device is further set up to receive a confirmation SL message from at least one of the plurality of further UEs, the confirmation SL message indicating completion of the SL-DRX cycle reconfiguration. The device according to Claim 5 , the communication type being multicast communication; and the apparatus is further configured to: receive an SL message having an SL-DRX cycle reconfiguration from a network; and reconfigure the SL-DRX cycle according to the SL-DRX cycle reconfiguration; where optionally a base transceiver station (BTS) of the network sends the SL message. A method of operating a UE, the method comprising: Receiving PSCCH during an on-duration portion of a DRX cycle, decoding a first stage of the PSCCH to determine an SCI priority; Determining whether the SCI priority is greater than a predetermined threshold priority; and Entering an inactive portion of the DRX cycle based on a determination of whether the SCI priority is greater than the predetermined threshold priority.

Images