Patent Description:
In Third Generation Partnership Project (3GPP), the Dual Connectivity (DC) solution has been specified, both for Long Term Evolution (LTE) and between LTE and Fifth Generation (<NUM>) New Radio (NR). In DC, two nodes are involved, a Master Node (MN, or Master enhanced or evolved Node B (eNB) (MeNB)) and a Secondary Node (SN, or Secondary eNB (SeNB)). Multi-connectivity (MC) is the case when there are more than two nodes involved. Also, it has been proposed in 3GPP that DC is used in Ultra Reliable Low Latency Communications (URLLC) cases to enhance the robustness and to avoid connection interruptions.

There are different ways to deploy a <NUM> NR network with or without interworking with LTE (also referred to as Evolved Universal Terrestrial Radio Access (E-UTRA)) and Evolved Packet Core (EPC). In principle, NR and LTE can be deployed without any interworking, denoted by NR Stand-Alone (SA) operation. That is, the NR base station (gNB) in NR can be connected to the <NUM> Core Network (CN) (5GCN), and the eNB in LTE can be connected to the EPC with no interconnection between the two. On the other hand, the first supported version of NR is the so-called EN-DC (E-UTRAN-NR DC). In such a deployment, DC between NR and LTE is applied with LTE as the master and NR as the secondary node. The Radio Access Network (RAN) node (gNB) supporting NR may not have a control plane connection to the core network (EPC), but instead may rely on LTE as the MN (MeNB). This is also called "Non-standalone NR. " Notice that, in this case, the functionality of an NR cell is limited and would be used for connected mode User Equipments (UEs) as a booster and/or diversity leg, but an RRC_IDLE UE cannot camp on these NR cells.

With introduction of 5GC, other options may be also valid. As mentioned above, Option <NUM> supports standalone NR deployment where the gNB is connected to the 5GC. Similarly, LTE can also be connected to the 5GCN (also known as enhanced LTE (eLTE), E-UTRA/5GC, or LTE/5GCN, with the node referred to as a Next Generation eNB (NG-eNB)). In these cases, both NR and LTE are seen as part of the Next Generation RAN (NG-RAN) (and thus both the NG-eNB and the gNB can be referred to as NG-RAN nodes). Other variants of DC between LTE and NR which will be standardized as part of NG-RAN connected to 5GC, are denoted by Multi-Radio DC (MR-DC). Thus, under the MR-DC umbrella are:.

As migration for these options may differ for different operators, it is possible to have deployments with multiple options in parallel in the same network. In combination with DC solutions between LTE and NR, it is also possible to support Carrier Aggregation (CA) in each cell group (i.e., Master Cell Group (MCG) and Secondary Cell Group (SCG)) and DC between nodes on the same Radio Access Technology (RAT) (e.g., NR-NR DC). For the LTE cells, a consequence of these different deployments is the co-existence of LTE cells associated to eNBs connected to EPC, 5GC, or both EPC/5GC.

As noted earlier, DC is standardized for both LTE and EN-DC. LTE DC and EN-DC are designed differently when it comes to which nodes control what. Basically, there are two options: centralized solutions such as LTE DC, and decentralized solutions such as EN-DC.

The main difference between DC in LTE DC and EN-DC is that, in EN-DC, the SN has a separate Radio Resource Control (RRC) entity (NR RRC). This means that the SN can also control the UE, sometimes without the knowledge of the MN, but often with the need to coordinate with the MN. In LTE DC, the RRC decisions are always coming from the MN (MN to UE). Note, however, that the SN still decides the configuration of the SN since it is only the SN itself that has knowledge of the resources, capabilities, etc. of the SN.

For EN-DC, the major changes compared to LTE DC are as follows:.

The SN is sometimes referred to as a Secondary gNB (SgNB) (where gNB is an NR base station), and the MN as MeNB in case the LTE is the MN and NR is the SN. In the other case where NR is the MN and LTE is the SN, the corresponding terms are SeNB and Master gNB (MgNB).

Split RRC messages are mainly used for creating diversity, and the sender can decide to either choose one of the links for scheduling the RRC messages or can duplicate the message over both links. In the downlink, the path switching between the MCG or SCG legs, or duplication of both, is left to network implementation. On the other hand, for the uplink, the network configures the UE to use the MCG, SCG, or both legs. The terms "leg," "path," and "Radio Link Control (RLC) bearer" are used interchangeably throughout this document.

Inter-node RRC messages are RRC messages that are sent either across the X2-, Xn-, or the NG-interface, either to or from the gNB, i.e., a single 'logical channel' is used for all RRC messages transferred across network nodes. The information could originate from or be destined for another RAT. In this regard, Table <NUM> below provides an excerpt from 3GPP Technical Specification (TS) <NUM> V15.

Cellular Intelligent Transport Systems (ITS) (C-ITS) aim to define a new cellular ecosystem for the delivery of vehicular services and their dissemination. Such an ecosystem includes both short range and long range V2X service transmissions. In particular, short range communication involves transmissions over a Device-to-Device (D2D) link (also defined as a Sidelink (SL) or PC5 interface in 3GPP), towards other vehicular UEs or Road Side Units (RSUs). On the other hand, for long range transmission, it considers the transmission over the Uu interface between a UE and a base station, in which case packets may be disseminated to different ITS service providers, which could be road traffic authorities, road operators, automotive Original Equipment Manufacturers (OEMs), cellular operators, etc..

When it comes to the SL interface, the first standardization effort in 3GPP dates back to Release (Rel) <NUM>, targeting public safety use cases. Since then, a number of enhancements have been introduced with the objective of enlarging the use cases that could benefit from the D2D technology. Particularly, in LTE Rel-<NUM> and Rel-<NUM>, the extensions for the D2D work consists of supporting V2X communication, including any combination of direct communication between vehicles (Vehicle-to-Vehicle (V2V)), pedestrians (Vehicle-to-Pedestrian (V2P)), and infrastructure (Vehicle-to-Infrastructure (V2I)).

In RAN#<NUM>, a new Study Item named "Study on NR V2X" was approved to study the enhancement to support advanced V2X services beyond services supported in LTE Rel-<NUM> V2X. One of the objectives for NR V2X design is to study technical solutions for Quality of Service (QoS) management of the radio interface including both Uu (i.e., network-to-vehicle UE communication) and SL (i.e., vehicle UE-to-vehicle UE communication) used for V2X operations.

While LTE V2X mainly aims at traffic safety services, NR V2X has a much broader scope that not only includes basic safety services, but also targets non-safety applications such as extended sensor/data sharing between vehicles, with the objective of strengthening the perception of the surrounding environment of vehicles. Hence, a new set of applications have been captured in 3GPP Technical Report (TR) <NUM> V16. <NUM> that would require an enhanced NR system and new NR SL framework. These applications include advanced driving, vehicle platooning, cooperative maneuvers between vehicles, and remote driving.

In this new context, the expected requirements to meet the needed data rate, capacity, reliability, latency, communication range, and speed are made more stringent. Additionally, both PC5 and Uu communication interfaces could be used to support the advanced V2X use cases, taking into account radio conditions and the environment where the enhanced V2X (eV2X) scenario takes place. For example, given the variety of services that can be transmitted over the SL, a robust QoS framework which takes into account the different performance requirements of the different V2X services seems to be needed. Additionally, NR protocols to handle more robust and reliable communication should be designed. All of these issues are currently under the investigation of 3GPP in NR Rel-<NUM>.

In NR, a SL QoS flow model is adopted. At the Non-Access Stratum (NAS) layer, the UE maps one V2X packet into the corresponding SL QoS flow and then maps to an SL radio bearer at the Service Data Adaptation Protocol (SDAP) layer.

In NR, SL Radio Bearer (SLRB) configuration, including the SL QoS flow to SLRB mapping, is either preconfigured or configured by the network when the UE is in coverage. For instance, when the UE wants to establish a new SL QoS flow/SLRB for a new service, the UE can send a request to the associated gNB. The request can include the QoS information of the service. The gNB then determines the appropriate SLRB configuration to support such an SL QoS flow. After receiving the SLRB configuration from the gNB, the UE establishes the local SLRB accordingly and prepares for data transmission over the SL. Note that to enable successful reception at the reception (RX) UE, the transmission (TX) UE might have to inform the RX UE regarding necessary parameters (e.g., sequence number space for Packet Data Convergence Protocol (PDCP)/RLC) before the data transmission starts.

RRC operation depends on the UE specific states. A UE is in either in RRC_CONNECTED state, RRC_INACTIVE state, or RRC_IDLE state. The different RRC states have different amounts of radio resources associated with them that the UE may use in that specific state. In RRC_INACTIVE and RRC_IDLE state, UE controlled mobility based on network configuration is adopted (i.e., the UE acquires System Information Block (SIB), performs neighboring cell measurements and cell selection and re-selection, and monitors a paging occasion). An inactive UE stores the UE inactive Access Stratum (AS) context and performs RAN-based Notification Area (RNA) updates.

In RRC_CONNECTED state, however, network-controlled mobility is performed. In fact, the RAN node can receive paging assistance information related to potential paging triggers, such as QoS flows or signaling, from the 5GCN. The UE is thus known by the network at the node/cell level, and a UE specific bearer is established upon which UE specific data and/or control signaling could be communicated. For example, the RAN can configure UE-specific RNAs that make it possible to reduce the total signaling load by configuring small RNAs for stationary UEs (optimized for low paging load) and, especially, larger RNAs for moving UEs (optimized for vehicular UEs).

Furthermore, if, e.g., there is no traffic transmission and/or reception for a certain time period, the network can initiate the RRC connection release procedure to transmit a UE in RRC_CONNECTED to RRC_IDLE; or to RRC_INACTIVE if SRB2 and at least one Data Radio Bearer (DRB) is set up in RRC_CONNECTED.

There are two different Resource Allocation (RA) procedures for V2X on SL, i.e., network-controlled RA (so called "mode <NUM>" in LTE and "mode <NUM>" in NR) and autonomous RA (so called "mode <NUM>" in LTE and "mode <NUM>" in NR). The transmission resources are selected within a resource pool which is, e.g., predefined or configured by the network.

With network-controlled RA, NG-RAN is in charge of scheduling SL resource(s) to be used by the UE for SL transmission(s). The UE sends an SL Buffer Status Report (BSR) to the network to inform the network about SL data available for transmission in the SL buffers associated with the Medium Access Control (MAC) entity. The network then signals the resource allocation to the UE using Downlink Control Information (DCI). Network-controlled (or mode <NUM>) RA may be realized via dynamic scheduling signalling via the Physical Downlink Control Channel (PDCCH), or by semi-persistent scheduling in which the gNB provides one or more configured SL grants. Both type-<NUM> and type-<NUM> configured SL grants are supported.

With autonomous RA, each device independently decides which SL radio resources to use for SL operations based on, e.g., sensing. For both RA modes, SL Control Information (SCI) is transmitted on the Physical Sidelink Control Channel (PSCCH) to indicate the assigned SL resources for the PSSCH. Unlike network-controlled RA, which can only be performed when the UE is in RRC_CONNECTED state, autonomous RA (or mode <NUM>) can be performed both when the UE is in RRC_CONNECTED state and when the UE is in INACTIVE/IDLE state, and also when the UE is under Uu coverage and out-of-coverage. In particular, when the UE is in RRC_CONNECTED state, the SL resource pool can be configured with dedicated RRC signalling, while for IDLE/INACTIVE mode operations, the UE shall rely on the SL resource pool provisioned in the broadcasting signal, i.e., SIB.

Currently, as part of the NR-V2X study item, 3GPP is investigating possible extension of such mode <NUM>. For example, 3GPP is considering the possibility of introducing a new UE functionality in which a UE, under certain conditions (e.g., for groupcast SL communication), is allowed to provision other UEs with a mode <NUM> pool to be used for SL communication (e.g., for SL communication within a group of UEs, such as a platoon of vehicles).

Configured grant is supported for NR SL, for both type <NUM> and type <NUM>. With configured grant, the gNB can allocate SL resources for multiple (periodical) transmissions to the UE. Type <NUM> configured grant is configured and activated directly via dedicated RRC signaling. Type <NUM> configured grant is configured via dedicated RRC signaling, but only activated/released via DCI transmitted on PDCCH.

<NPL>", discusses agreements on NR SL QoS and SLRB configurations.

Devices and methods are disclosed herein for enabling a Sidelink (SL) User Equipment (UE) to send a Radio Resource Control (RRC) message to the network in order to request an RRC procedure in association with an SL. Embodiments of a method implemented in an SL UE are disclosed herein. The claimed invention includes a method implemented in a User Equipment as defined in claim <NUM>.

The RRC procedure comprises either an SL configuration procedure or an SL configuration update procedure. In some embodiments, detecting the trigger for sending the RRC message comprises detecting one or more criteria, the one or more criteria comprising a criterion that an SL Radio Bearer (SLRB) reconfiguration is needed, a criterion that there is a new SL Quality of Service (QoS) flow but no QoS mapping for the new SL QoS flow, a criterion that a new SL QoS mapping is needed, a criterion of a change in an SL-related UE context at the SL UE, or a criterion of performance of one or more autonomous SL-related actions by the SL UE. In some embodiments, the criterion of performance of the one or more autonomous SL-related actions by the SL UE comprises a criterion of autonomously deciding a new SL-related QoS mapping rule or a criterion of autonomously updating an SL-related UE context.

In some embodiments, sending the RRC information or message to the network node comprises sending the RRC message to the network node upon detecting the trigger. According to some embodiments, detecting the trigger for sending the RRC message comprises detecting the trigger for sending the RRC message while the SL UE is in an idle or inactive state, and sending the RRC message to the network node comprises sending the RRC message to the network node upon detecting the trigger and transitioning from the idle or inactive state to a connected state. In some embodiments, sending the RRC message to the network node comprises sending the RRC message to the network node when in a connected state, and the RRC message comprises an existing SL-related RRC message. Some such embodiments provide that the existing SL-related RRC message comprises a SidelinkUEInformation message.

In some embodiments, sending the RRC message to the network node comprises sending the RRC message to the network node when in a connected state, and the RRC message comprises an existing NR or Long Term Evolution (LTE) RRC message. Some such embodiments provide that the existing NR or LTE RRC message comprises a UEAssistanceInformation message, a ULInformationTransfer message, or a ULInformationTransferMRDC message. In some embodiments, sending the RRC message to the network node comprises sending the RRC message to the network node when in a connected state, and the RRC message comprises a new RRC message that is common for two or more Radio Access Technologies (RATs). According to some embodiments, sending the RRC message to the network node comprises sending the RRC message to the network node when in a connected state, and the RRC message comprises a new RRC message that is for SL only.

In some embodiments, sending the RRC information or message to the network node comprises sending the RRC message to the network node when in an idle or inactive state, and the RRC message comprises an existing RRC message. Some such embodiments provide that the existing RRC message comprises an RRCResumeRequest message or an RRCSetupRequest message. In some embodiments, sending the RRC message to the network node comprises sending the RRC message to the network node when in an idle or inactive state, and the RRC message comprises a new RRC message that is common for two or more RATs. According to some embodiments, sending the RRC message to the network node comprises sending the RRC message to the network node when in an idle or inactive state, and the RRC message comprises a new RRC message that is used for SL only.

In some embodiments, the RRC message comprises a flag that indicates a request for a new SLRB configuration. Some embodiments provide that the RRC message comprises QoS flow information for one or more QoS flows at the SL UE. According to some embodiments, the RRC message further comprises an indication of one or more new QoS mappings needed for the one or more QoS flows. In some embodiments, the RRC message comprises a new SL-related UE context for the SL UE.

According to some embodiments, the method further comprises receiving a response from either the network node or another network node. In some embodiments, the response comprises one or more SL-related configurations or one or more updates to one or more SL-related configurations. Some embodiments provide that the method further comprises taking one or more actions based on the response. In some embodiments, the network node comprises a base station. According to some embodiments, the SL UE uses Dual Connectivity (DC), and the network node comprises a Master Node (MN) of the SL UE. Some embodiments provide that the SL UE uses DC, and the network node comprises a Secondary Node (SN) of the SL UE.

The claimed invention provides also a SL UE as defined in claim <NUM>.

The claimed invention also provides a method implemented in a network node as defined in claim <NUM>. The method further comprises taking one or more actions based on the RRC message. According to some embodiments, the one or more actions comprise sending the RRC message or information in the RRC message to another network node. In some embodiments, the one or more actions comprise sending a response to the SL UE, and the response comprises the one or more SL-related configurations for the SL UE or one or more updates to the one or more SL-related configurations for the SL UE.

In some embodiments, the RRC message comprises either the request for the RRC procedure related to the one or more SL-related configurations, or the message that both requests the RRC procedure related to the one or more SL-related configurations and comprises the information about the one or more changes made by the SL UE related to the one or more SL configurations. In some embodiments, receiving the RRC message from the SL UE comprises receiving the RRC message from the SL UE while the SL UE is in a connected state, and the RRC message comprises an existing SL-related RRC message. According to some such embodiments, the existing SL-related RRC message comprises a SidelinkUEInformation message.

In some embodiments, receiving the RRC message from the SL UE comprises receiving the RRC message from the SL UE while the SL UE is in a connected state, and the RRC message comprises an existing NR or LTE RRC message. Some such embodiments provide that the existing NR or LTE RRC message comprises a UEAssistanceInformation message, a ULInformationTransfer message, or a ULInformationTransferMRDC message. In some embodiments, receiving the RRC message from the SL UE comprises receiving the RRC message from the SL UE while the SL UE is in a connected state, and the RRC message comprises a new RRC message that is common for two or more RATs. Some embodiments provide that receiving the RRC message from the SL UE comprises receiving the RRC message from the SL UE while the SL UE is in a connected state, and the RRC message comprises a new RRC message that is for SL only. According to some embodiments, receiving the RRC message from the SL UE comprises receiving the RRC message from the SL UE while the SL UE is in an idle or inactive state, and the RRC message comprises an existing RRC message. In some such embodiments, the existing RRC message comprises an RRCResumeRequest message or an RRCSetupRequest message.

In some embodiments, receiving the RRC message from the SL UE comprises receiving the RRC message from the SL UE while the SL UE is in an idle or inactive state, and the RRC message comprises a new RRC message that is common for two or more RATs. According to some embodiments, receiving the RRC message from the SL UE comprises receiving the RRC message from the SL UE while the SL UE is in an idle or inactive state, and the RRC message comprises a new RRC message that is used for SL only. Some embodiments provide that the RRC message comprises a flag that indicates a request for a new SLRB configuration. In some embodiments, the RRC message comprises QoS flow information for one or more QoS flows at the SL UE. Some such embodiments provide that the RRC message further comprises an indication of one or more new QoS mappings needed for the one or more QoS flows.

In some embodiments, the RRC message comprises a new SL-related UE context for the SL UE. Some embodiments provide that the network node comprises a base station. According to some embodiments, the SL UE uses DC, and the base station comprises an MN of the SL UE. In some embodiments, the SL UE uses DC, and the base station comprises an SN of the SL UE.

The claimed invention provides also a base station as defined in claim <NUM>. The base station is adapted to receive an RRC message from an SL UE, wherein the RRC message is a request for an RRC procedure related to one or more SL-related configurations, a message comprising information about one or more changes made by the SL UE related to one or more SL configurations, or a message that both requests the RRC procedure related to the one or more SL-related configurations and comprises the information about the one or more changes made by the SL UE related to the one or more SL configurations, wherein the RRC procedure comprises either an SL configuration procedure or an SL configuration update procedure. The base station is further adapted to take one or more actions based on the RRC message. In some embodiments, the base station is also adapted to perform any of the steps attributed to the base station in the above-disclosed methods.

Radio Access Node: As used herein, a "radio access node" or "radio network node" is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (<NUM>) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a lowpower base station (e.g., a micro base station, a pico base station, a home eNB, or the like), and a relay node.

Core Network Node: As used herein, a "core network node" is any type of node in a Core Network (CN) or any node that implements a CN function. Some examples of a CN node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a CN node include a node implementing a Access and Mobility Function (AMF), a User Plane (UP) Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.

Sidelink Wireless Device: As used herein, a "sidelink wireless device," "sidelink capable wireless device," "sidelink UE," or "sidelink capable UE" is a wireless device or UE capable of Sidelink (SL) communication.

Network Node: As used herein, a "network node" is any node that is either part of the RAN or the CN of a cellular communications network/system.

In NR, SL Radio Bearer (SLRB) configuration, including the SL Quality of Service (QoS) flow to SLRB mapping, is either preconfigured or configured by the network when the UE is in coverage. For this latter case, at the moment, there is no signaling support on how the UE may request an SLRB reconfiguration or new SLRB configuration to support a new SL QoS flow. This lack of signaling not only impacts the SLRB configuration to the QoS flow mapping, but it may also impact other Radio Resource Control (RRC) procedures, e.g., updating the UE SL context at the network side. In particular, if the UE is not able to request a certain RRC procedure to the network, this will lead to SL (re)configuration errors, connectivity interruptions, and signaling overhead.

Systems and methods are disclosed herein for enabling an SL UE to send an RRC message to the network in order to request an RRC procedure in association with an SL from the network (or to just send an indication to the network), e.g., when certain circumstances happen (e.g., when new QoS flows pop up in the SL UE, SL UE context becomes un-synchronized with that one stored at the gNB/eNB, or a new SLRB configuration is required). The requested RRC procedure is a new SL configuration or an SL configuration update. The same RRC procedure can also be used to send an indication to the network by the SL UE. In this way, (re)configuration errors, connectivity interruption, and signaling overhead among the SL UEs and the network can be prevented.

In some embodiments, an SL UE may request an RRC procedure (or send just an indication) to the network when certain circumstances happen (e.g., new QoS flows pop up in the SL UE, SL UE context becomes un-synchronized with the one stored at the NR Base Station (gNB) / enhanced or evolved Node B (eNB), or a new SLRB configuration is required). Some example benefits of embodiments of the present disclosure may include:.

In this regard, <FIG> illustrates one example of a cellular communications system <NUM> in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications system <NUM> is a <NUM> System (5GS) including an NR RAN. However, the present disclosure is not limited thereto. Rather, embodiments of the present disclosure may be implemented in other types of wireless communications systems that enable SL communications. In this example, the RAN includes a base station <NUM>, which in <NUM> NR is referred to as a gNB or Next Generation RAN (NG-RAN) node, controlling a corresponding cell. The cellular communications system <NUM> also includes a core network <NUM>, which in the 5GS is referred to as the <NUM> CN (5GCN). The core network <NUM> may alternatively be the Evolved Packet Core (EPC). The base station <NUM> is connected to the core network <NUM>.

The cellular communications system <NUM> also includes SL wireless devices <NUM>-<NUM> and <NUM>-<NUM>, which are also referred to herein as SL UEs <NUM>-<NUM> and <NUM>-<NUM>. In this example, the SL UE <NUM>-<NUM> has a cellular link to the base station <NUM> and an SL to the other SL UE <NUM>-<NUM>.

Now, a description of some example embodiments will be provided. Note that the following embodiments are described for NR, but they may be applied to LTE or any other Radio Access Technology (RAT). Further, the NG-RAN nodes may be connected to the 5GC or to the EPC. In case of Dual Connectivity (DC), the disclosed solution can be applied to all the Multi-Radio DC (MR-DC) options as described in, e.g., 3GPP Technical Specification (TS) <NUM> V15.

Embodiments are disclosed herein for enabling an SL UE (e.g., the SL UE <NUM>-<NUM>) to send an RRC message to the network (e.g., to the base station <NUM>) in order to request an RRC procedure or inform the network about some change(s) or situation(s) in SL communications. The requested RRC procedure may be (but is not limited to) a new SL configuration or a configuration update. The same RRC procedure can also be used to send an indication to the network by the SL UE. Alternatively, the SL UE may decide itself to take some action(s) (e.g., decide a new QoS mapping rule) and then inform the network via an (e.g., new) RRC message.

In this regard, <FIG> illustrates the operation of the base station <NUM> and the SL UE <NUM>-<NUM> in accordance with various embodiments of the present disclosure. As illustrated, the SL UE <NUM>-<NUM> detects a trigger (e.g., detects one or more triggering events or conditions) for sending an RRC message to the network for requesting an RRC procedure for SL-related configurations (SL configuration or SL configuration update) and/or for sending an RRC message to the network with an indication (e.g., information that indicates, to the network, one or more SL-related configurations autonomously made, changed, or updated by the SL UE) (step <NUM>). In some embodiments, the SL UE <NUM>-<NUM> detects a trigger for sending an RRC message to the network for requesting an RRC procedure for SL-related configurations. This detection is the detection that one or more (e.g., predefined or preconfigured) criteria for triggering this RRC procedure request are satisfied. In one embodiment, the one or more (e.g., predefined or preconfigured) criteria for triggering the RRC procedure request for SL-related configurations by the SL UE <NUM>-<NUM> include the need of an SLRB reconfiguration, e.g., due to changed radio conditions or (re)configuration errors. In another embodiment, the one or more (e.g., predefined or preconfigured) criteria for triggering the RRC procedure request for SL-related configurations by the SL UE <NUM>-<NUM> is when there is a new SL QoS flow but there is no clear QoS mapping (i.e., SL QoS flow to SL SLRB), or a new SL QoS mapping is needed from the network (e.g., the current SL SLRB cannot fulfill the SL QoS flow requirement). In another embodiment, the one or more (e.g., predefined or preconfigured) criteria for triggering the RRC procedure request for SL-related configurations by the SL UE <NUM>-<NUM> is when the SL-related UE context has changed at the SL UE <NUM>-<NUM> side (e.g., update of the destination L2 Identity (ID) or new SL unicast link) and this needs to be updated at the network side (e.g., to prevent a wrong SL-related UE context retrieval or sending during handover procedure).

In another embodiment, the trigger for the RRC procedure (e.g., the trigger for an RRC procedure request for SL-related configurations) is the performance, by the SL UE <NUM>-<NUM>, of an autonomous action(s) such as, e.g., deciding a new QoS mapping rule or updating the SL-related UE context autonomously. Upon the SL UE <NUM>-<NUM> performing an autonomous action(s) (e.g., deciding a new QoS mapping rule or updating the SL-related UE context autonomously), the SL UE <NUM>-<NUM> detects this trigger for the RRC procedure request for SL-related configurations in order to inform the network of the change(s) that have happened. In another embodiment, the SL UE <NUM>-<NUM> performs autonomous actions when in RRC_IDLE/RRC_INACTIVE states or out of coverage, but triggers the RRC procedure over Uu once the SL UE <NUM>-<NUM> enters the RRC_CONNECTED state for informing the network of the SL-related changes that have happened.

Upon detecting the trigger, the SL UE <NUM>-<NUM> sends the triggered RRC message (e.g., a message requesting an RRC procedure or a message including an indication) to the base station <NUM> (step <NUM>). As discussed above, the SL UE <NUM>-<NUM> may send the RRC message immediately upon detecting the trigger or at some later time (e.g., after transitioning from RRC_IDLE/RRC_INACTIVE state to RRC_CONNECTED state).

In one embodiment, when the UE is in RRC_CONNECTED state, the RRC message in step <NUM> is transmitted over the Uu interface for requesting and/or informing the SL-related configurations. In some embodiments, this RRC message sent over the Uu interface is an existing SL-related message such as the SidelinkUEInformation message. In one embodiment, when the UE is in RRC_CONNECTED state, the RRC message used for requesting and/or informing the SL-related configurations is an existing NR (or LTE) message such as the UEAssistanceInformation, ULInformationTransfer, or ULInformationTransferMRDC (i.e., if DC is enabled) message. In an alternative embodiment, when the SL UE <NUM>-<NUM> is in RRC_CONNECTED state, the RRC message used for requesting and/or informing the SL-related configurations is a new RRC message that is common for any RATs (SL, NR, or LTE). Further, in another embodiment, when the SL UE <NUM>-<NUM> is in RRC_CONNECTED state, the RRC message used for requesting and/or informing the SL-related configurations is a new RRC message that is used only in SL.

In one embodiment, when the SL UE <NUM>-<NUM> is in RRC_IDLE/RRC_INACTIVE state, the RRC message used for requesting and/or informing the SL-related configurations is an existing message such as RRCResumeRequest or the RRCSetupRequest message. In another embodiment, when the SL UE <NUM>-<NUM> is in RRC_IDLE/RRC_INACTIVE state, the RRC message used for requesting and/or informing the SL-related configurations is a new RRC message that is common for any RATs. In another embodiment, when the SL UE <NUM>-<NUM> is in RRC_IDLE/RRC_INACTIVE state, the RRC message used for requesting and/or informing the SL-related configurations is a new RRC message that is used only for SL.

In one embodiment, the content of the RRC message sent by the SL UE <NUM>-<NUM> used for requesting and/or informing the SL-related configurations includes a flag for requesting a new SLRB configuration. In another embodiment, the content of the RRC message sent by the SL UE <NUM>-<NUM> used for requesting and/or informing the SL-related configurations includes new QoS flow(s) information together with an indication of a new QoS mapping needed for the included QoS flow(s). In another embodiment, the content of the RRC message sent by the SL UE <NUM>-<NUM> used for requesting and/or informing the SL-related configurations includes a new SL-related UE context to be stored at the network side (e.g., the gNB, eNB, Next Generation eNB (NG-eNB)).

In one embodiment, the UE sends the RRC message for requesting SL-related configurations to the network via, e.g., SRB1. If DC is enabled, in another embodiment the UE could send such RRC message to the primary network node via, e.g., SRB1. In an alternative embodiment, the UE could send such RRC message to the secondary network node via, e.g., SRB3.

In another embodiment, the SL capable UE receives the response/acknowledgment for such RRC message from the primary node. In one embodiment, the SL capable UE receives the response/acknowledgment for such RRC message from a Secondary Node (SN).

Upon receiving the RRC message, the base station <NUM> performs one or more actions based on the RRC message (step <NUM>). In one embodiment, upon receiving the RRC message for requesting SL-related configurations from the SL capable UE, the base station <NUM> sends a response/acknowledgment to the SL UE <NUM>-<NUM>. In one embodiment, the response/acknowledgment is an existing RRC message such as (but not limited to) the RRCReconfiguration if the SL UE <NUM>-<NUM> is in RRC_CONNECTED state. Alternatively, in one embodiment, the response/acknowledgment is an existing RRC message such as (but not limited to) the RRCResume, RRCSetup, or Paging message if the SL UE <NUM>-<NUM> is in RRC_IDLE/RRC_INACTIVE.

In one embodiment, if DC is enabled, the base station <NUM> is the primary network node (e.g., the Master Node (MN)), and, upon receiving the RRC message for requesting SL-related configurations from the SL UE <NUM>-<NUM>, the primary network node (e.g., the MN) forwards the RRC message to the secondary node (e.g., the SN) via inter-node control messages. Further, in one embodiment, upon receiving the RRC message for requesting the SL-related configurations forwarded from the primary node (e.g., the MN), the secondary network node (e.g., the SN) generates an RRC message for triggering the requested RRC procedure and forwards the message to the primary node. The primary node then proceeds to forward the message by, e.g., embedding it in a Master Cell Group (MCG) RRC message to the SL UE <NUM>-<NUM> via, e.g., SRB1. In another embodiment, upon receiving the RRC message for requesting the SL-related configurations forwarded from the primary node (e.g., the MN), the secondary network node (e.g., the SN) sends a direct RRC message to trigger the requested RRC procedure to the SL UE <NUM>-<NUM> via, e.g., SRB3.

In another embodiment, if DC is enabled, the base station <NUM> is the secondary node (e.g., the SN), and, upon receiving the RRC message for requesting the SL-related configurations from the SL UE <NUM>-<NUM>, the secondary network node (e.g., the SN) forwards the RRC message to the primary node (e.g., the MN) via inter-node control messages. Further, in one embodiment, upon receiving the RRC message for requesting SL-related configurations forwarded from the secondary node (e.g., the SN), the primary network node (e.g., the MN) generates an RRC message for triggering the requested RRC procedure and forwards it to the SN. Then the SN proceeds to forward the message by, e.g., embedding it in a Secondary Cell Group (SCG) RRC message to the SL UE <NUM>-<NUM> via, e.g., SRB3. In one embodiment, upon receiving the RRC message for requesting SL-related configurations forwarded from the SN, the primary network node sends a direct RRC message to trigger the requested RRC procedure to the SL UE <NUM>-<NUM> via, e.g., SRB1.

In one embodiment, the SL UE <NUM>-<NUM> receives a response or acknowledgment from the network (e.g., either from the base station <NUM> or from another RAN node (e.g., SN)) (step <NUM>). Upon receiving the response/acknowledgment from the network, the SL UE <NUM>-<NUM> performs one or more actions (step <NUM>). For example, in some embodiments, the response or acknowledgement includes a configuration (e.g., SLRB configuration or QoS mapping rule), and the SL UE <NUM>-<NUM> applies the configuration (e.g., SLRB configuration or QoS mapping rule) received in the response or acknowledgement. As another example, upon receiving the response/acknowledgment from the network (e.g., either from the base station <NUM> or from another RAN node (e.g., SN)), the SL UE <NUM>-<NUM> goes to RRC_IDLE/RRC_INACTIVE. As yet another example, upon receiving the response/acknowledgment from the network (e.g., either from the base station <NUM> or from another RAN node (e.g., SN)), the SL UE <NUM>-<NUM> releases the SL communication. In another embodiment, upon receiving the response/acknowledgment from the network (e.g., either from the base station <NUM> or from another RAN node (e.g., SN)), the SL UE <NUM>-<NUM> performs no action.

<FIG> is a schematic block diagram of a radio access node <NUM> according to some embodiments of the present disclosure. The radio access node <NUM> may be, for example, a base station <NUM> (e.g., a gNB or NG-RAN node). As illustrated, the radio access node <NUM> includes a control system <NUM> that includes one or more processors <NUM> (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory <NUM>, and a network interface <NUM>. The one or more processors <NUM> are also referred to herein as processing circuitry. In addition, the radio access node <NUM> includes one or more radio units <NUM> that each includes one or more transmitters <NUM> and one or more receivers <NUM> coupled to one or more antennas <NUM>. The radio units <NUM> may be referred to as or be part of radio interface circuitry. In some embodiments, the radio unit(s) <NUM> is external to the control system <NUM> and connected to the control system <NUM> via, e.g., a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s) <NUM> and potentially the antenna(s) <NUM> are integrated together with the control system <NUM>. The one or more processors <NUM> operate to provide one or more functions of a radio access node <NUM> as described herein (e.g., one or more functions of the base station <NUM> as described above, e.g., with respect to <FIG>). In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory <NUM> and executed by the one or more processors <NUM>.

As used herein, a "virtualized" radio access node is an implementation of the radio access node <NUM> in which at least a portion of the functionality of the radio access node <NUM> is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the radio access node <NUM> includes the control system <NUM> that includes the one or more processors <NUM> (e.g., CPUs, ASICs, FPGAs, and/or the like), the memory <NUM>, the network interface <NUM>, and the one or more radio units <NUM> that each includes the one or more transmitters <NUM> and the one or more receivers <NUM> coupled to the one or more antennas <NUM>, as described above. The control system <NUM> is connected to the radio unit(s) <NUM> via, for example, an optical cable or the like. The control system <NUM> is connected to one or more processing nodes <NUM> coupled to or included as part of a network(s) <NUM> via the network interface <NUM>. Each processing node <NUM> includes one or more processors <NUM> (e.g., CPUs, ASICs, FPGAs, and/or the like), memory <NUM>, and a network interface <NUM>.

In this example, functions <NUM> of the radio access node <NUM> described herein (e.g., one or more functions of the base station <NUM> as described above, e.g., with respect to <FIG>) are implemented at the one or more processing nodes <NUM> or distributed across the control system <NUM> and the one or more processing nodes <NUM> in any desired manner. In some particular embodiments, some or all of the functions <NUM> of the radio access node <NUM> described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) <NUM>. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) <NUM> and the control system <NUM> is used in order to carry out at least some of the desired functions <NUM>. Notably, in some embodiments, the control system <NUM> may not be included, in which case the radio unit(s) <NUM> communicate directly with the processing node(s) <NUM> via an appropriate network interface(s).

In some embodiments, a computer program including instructions which, when executed by at least one processor, cause the at least one processor to carry out the functionality of the radio access node <NUM> or a node (e.g., a processing node <NUM>) implementing one or more of the functions <NUM> of the radio access node <NUM> (e.g., one or more functions of the base station <NUM> as described above, e.g., with respect to <FIG>) in a virtual environment according to any of the embodiments described herein is provided.

<FIG> is a schematic block diagram of a UE <NUM> according to some embodiments of the present disclosure. As illustrated, the UE <NUM> includes one or more processors <NUM> (e.g., CPUs, ASICs, FPGAs, and/or the like), memory <NUM>, and one or more transceivers <NUM> each including one or more transmitters <NUM> and one or more receivers <NUM> coupled to one or more antennas <NUM>. The transceiver(s) <NUM> includes radio-front end circuitry connected to the antenna(s) <NUM> that is configured to condition signals communicated between the antenna(s) <NUM> and the processor(s) <NUM>, as will be appreciated by one of ordinary skill in the art. The processors <NUM> are also referred to herein as processing circuitry. The transceivers <NUM> are also referred to herein as radio circuitry. In some embodiments, the functionality of the UE <NUM> described above (e.g., one or more functions of the SL UE <NUM>-<NUM> as described above, e.g., with respect to <FIG>) may be fully or partially implemented in software that is, e.g., stored in the memory <NUM> and executed by the processor(s) <NUM>. Note that the UE <NUM> may include additional components not illustrated in <FIG> such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the UE <NUM> and/or allowing output of information from the UE <NUM>), a power supply (e.g., a battery and associated power circuitry), etc..

Claim 1:
A method implemented in a Sidelink, SL, User Equipment, UE, (<NUM>-<NUM>), the method comprising:
detecting (<NUM>) a trigger for sending a Radio Resource Control, RRC, information, wherein the RRC information comprises one of:
• a request for an RRC procedure related to one or more SL-related communications; and
• a message that both requests the RRC procedure related to the one or more SL-related configurations and comprises the information that informs the network about the one or more changes made by the SL UE (<NUM>-<NUM>) related to the one or more SL communications; and
sending (<NUM>) the RRC information to a network node;
wherein the RRC procedure comprises either an SL configuration procedure or an SL configuration update procedure.