WO2020192935A1

WO2020192935A1 - Control unit and method for assisting side-link communication

Info

Publication number: WO2020192935A1
Application number: PCT/EP2019/057934
Authority: WO
Inventors: Emmanouil Pateromichelakis; Chan Zhou; Henrik Olofsson; Wenjie Peng; Jun Wang; Haiyan Luo
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2019-03-28
Filing date: 2019-03-28
Publication date: 2020-10-01

Abstract

The present invention relates to the fields of mobile communication, connected driving, Internet of vehicles (IoV), self-driving car, and autonomous car. More specifically, the present invention relates to side-link communication and network slicing. The present invention provides a control unit (100) for assisting side-link communication for at least one slice (101) of a communication network, wherein the control unit (100) is configured to configure, for the at least one slice (101), at least one side-link resource pool (102) based on an upper layer requirement (103) and/or a network requirement (104), and to provide a side-link resource pool configuration (105) to at least one terminal device.

Description

CONTROL UNIT AND METHOD FOR

ASSISTING SIDE-LINK COMMUNICATION

TECHNICAL FIELD

The present disclosure relates to the field of mobile communication. More specifically, the present disclosure relates to side-link (SL) communication and network slicing. In particular, the present disclosure relates to a control unit and a method for assisting side-link communication. The present disclosure also relates to a terminal device and a management entity for side-link communication.

BACKGROUND

Enhanced vehicular to everything (eV2X) can be seen as special 5G service type, which includes both safety and non-safety services, according to TS 22.186. Side-link transmission (over the PC5 interface) is a key operation mode for cellular-assisted vehicular to everything (aka C-V2X or 5G-V2X) services, whereas LTE-Uu or NR-Uu (the interface between a UE and the 5G-BS or gNB) can support the control plane (CP), and for some cases the User Plane (UP) for the communications between vehicles.

For the particular case of New Radio (NR), NR-PC5 may use unlicensed (e.g. ITS bands) or licensed spectrum; hence it can be seen as part of NR configuration. In particular, the side-link / PC5 interface between two or more vehicles (which comprises the resources and functions related to the communication over the PC5 interface) can be defined as a standalone NR Configuration option or as a part of NR Configuration comprising NR-PC5 and LTE-Uu or NR-Uu links.

The concept of network slicing is introduced in 5G to address the various requirements from multiple vertical industries assuming a shared network infrastructure. Network services can be customized based on the requirements of different use cases and thus increase the network operation efficiency. Network slicing is an end to end concept according to the current definition being discussed in 3GPP (cf. TR23.501). In this regard, the slicing granularity can be seen as overarching policies on top of Quality of Service (QoS) / service granularity, considering the business aspects of 5G network logical partitioning to meet the vertical requirements. V2X Standardized Slice Type (SST) was recently introduced for this purpose in SA2 (cf. TR23.786):

In this framework, two operation modes are defined. In the first operation mode, also indicated as Mode 1, a network node, such as a base station (e.g., RAN device, gNB, and the like) schedules side-link resource(s) to be used by an end device or User Equipment (UE), such as a vehicle or V-UE, for side-link transmission(s). In the second operation mode, also indicated as Mode 2, the end device determines the side-link transmission resource(s) within the side-link resources, which are configured by the network node, or within pre-configured side-link resources. In other words, in Mode 2 operation the network node does not schedule resources but rather configures resource pools, while the end device performs autonomous scheduling.

When applying slicing to V2X services in Mode 2 operation, if dedicated resource pools are scheduled per slice, it is not specified how the slice-specific resource pool pre-configuration and/or configurations/assignments are signaled to the end devices, so as to allow the UEs to know in which frequencies/sub-bands to transmit and/or receive data traffic.

To summarize, if slicing applies to V2X services over NR-PC5, this has impact on RAN for configuring/assigning/providing side-link resources to end devices in a slice-based manner, if one RAN configuration including NR-PC5 is utilized by at least one slice.

In the prior art, the problem of resource pool configuration is addressed without considering the slicing criterion.

Based on the NR principles for slice awareness (as stated in TS 38.300, section 16.3.1) the problem of resource management and isolation is a problem of network node, such as a RAN node, to manage radio resources. However this applies currently only for NR-Uu resources, since the granularity is per PDU session. The problem of how the RAN will be aware for the case when the RAN part of the Slice is an NR-PC5 resource and how RAN will configure the resource pools per slice has yet not be addressed.

As it is outlined in view of the above prior art solutions, the prior art lacks for a solution to communicate a side-link configuration in a versatile manner, based on various requirements. In particular, no solution is present to integrate network slicing into the communication of a side- link communication configuration.

SUMMARY

In view of the above-mentioned problems and disadvantages, devices and methods are provided to improve the conventional ways for side- link communication.

An object is achieved by the solution provided in the enclosed independent claims. Advantageous are further defined in the dependent claims.

According to a first aspect, the present invention provides a control unit for assisting side-link communication for at least one slice of a communication network, wherein the control unit is configured to configure, for the at least one slice, at least one side-link resource pool based on an upper layer requirement and/or a network requirement, and provide a side-link resource pool configuration to at least one terminal device.

In particular, the terminal device is a user equipment, UE.

In particular, by configuring the at least one side-link resource pool, the control unit generates a resource pool configuration.

In particular, the side-link communication is vehicle-to-vehicle (V2V) communication.

In particular, the side-link communication is vehicle-to-anything(V2X) communication.

In particular, the control unit is for cellular-assisted side-link communication.

In particular, the control unit may be a network node (e.g. a RAN node), and in particular a RAN node for a NR (5G) communication network, or it may be a fimction/software implemented in the node.

In particular, a RAN node can be, or can be implemented by means of at least one of the following: a Central Unit (CU), a Distributed Unit (DU), a gNB, an eNB, a Master Node (MN), a Secondary Node (SN), a RoadSide Unit (RSU). In this manner resource isolation between slices can be obtained, for example in the case that the control unit is implemented in a Ran node and where the RAN part of the slice is the link between end devices, for instance a sidelink such as the PC5, in particular the NR-PC5 interface. In this manner, the slicing principles apply also for the side-link V2X communications.

In an implementation, the control unit may configure a per slice resource pool for side-link V2X communications (in 1 :N and N:1 resource pool to slice mappings). The control unit may be configured to obtain the slice information of each session and map the slice traffic to different resource pools and/or resource pool configurations; communicate a resource pool configuration to an end device (via dedicated signaling, pre-configuration or system information broadcast); and notify of other involved nodes. The other node may, for example include at least one of the following:

a Central Unit (CU),

-a Distributed Unit (DU),

-a gNB,

-an eNB,

-a Master Node (MN)

-a Secondary Node (SN)

-a RoadSide Unit (RSU),

- a CN node

-an application-domain nodes.

In particular, a resource pool is a group of physical resources (e.g. resource blocks), for instance in the OFDMA time frequency resource grid.

In an implementation form of the first aspect, the upper layer requirement includes at least one application or service configuration parameter for a side-link communication.

In a further implementation form of the first aspect, the network requirement includes at least one network parameter, in particular a slice configuration information.

In a further implementation form of the first aspect, the at least one side-link resource pool configuration comprises at least one of the following parameters: Slice identifier and/or Network Slice Network Slice Selection Assistance Information (NSSAI) and/or S-NSSAI; Common Rx Pool List; Common Tx Pool List; Side-link Resource Pool Configuration information; Slice Radio Resource Management (RRM) Policies; Resource Selection information; Geographical Area; Time Validity; mode mapping information for mapping a session and/or a service to a first or a second operation mode.

In particular, the first operation mode may be referred to as mode 1, according to which scheduling is done by a base station (BS). In particular, the second operation mode may be referred to as mode 2, according to which scheduling is done by the terminal device which establishes the side-link connection.

In a further implementation form of the first aspect, the control unit is configured to provide the at least one side-link resource pool configuration to the mobile device using dedicated per terminal device signaling.

In particular, the side-link resource pool configuration can be transmitted via dedicated per terminal device (unicast) Radio Resource Control (RRC) signaling.

In a further implementation form of the first aspect, the dedicated per terminal device signaling comprises an RRC reconfiguration message including the side-link resource pool configuration.

In particular, the dedicated per terminal device RRC signaling can includes an RRC reconfiguration message. In particular, the RRC reconfiguration message can comprise at least one of the following parameters: Slice identifier and/or NSSAI and/or S-NSSAI; Common Rx Pool List; Common Tx Pool List; Side-link Resource Pool Configuration information; Slice RRM Policies; Resource Selection information; Geographical Area; Time Validity; mode mapping information for mapping a session and/or a service to a first or a second operation mode.

In a further implementation form of the first aspect, the control unit is configured to provide the side-link resource pool configuration to the mobile device by means of broadcast communication. In a further implementation form of the first aspect, the broadcast messages include System Information Block, SIB, information.

In particular, the SIB message is a SIB21 message.

In a further implementation form of the first aspect, the control unit is configured to provide the side-link resource pool configuration to a mobile device by means of a pre-configuration message comprising the side-link resource pool configuration.

In a further implementation form of the first aspect, the control unit is configured to provide the side-link resource pool configuration to a network node using at least one of X2, XnAP, FI, and NGAP signaling.

In particular, the network node may be a base station, a RAN, or a core network node/entity.

In a further implementation form of the first aspect, the control unit is configured to map a network slice to a corresponding side-link resource pool configuration.

According to a second aspect, the present invention provides a method for assisting side-link communication for at least one slice of a communication network, wherein the method comprises the steps of configuring, by a control unit, for the at least one slice, at least one side- link resource pool based on an upper layer requirement and/or a network requirement, and providing, by the control unit, a side-link resource pool configuration to at least one terminal device.

In particular, the terminal device is a user equipment, UE.

In particular, the side-link communication is vehicle-to-anything (V2X) communication. In particular, the control unit is for cellular-assisted side-link communication.

In particular, the control unit may be a network node (e.g. a RAN), or a fimction/software implemented in the node.

In an implementation form of the second aspect, the upper layer requirement includes at least one application or service configuration parameter for a side-link communication.

In a further implementation form of the second aspect, the network requirement includes at least one network parameter, in particular a slice configuration information.

In a further implementation form of the second aspect, the at least one side-link resource pool configuration comprises at least one of the following: Slice identifier and/or NSSAI and/or S- NSSAI; Common Rx Pool List; Common Tx Pool List; Side-link Resource Pool Configuration information; Slice RRM Policies; Resource Selection information; Geographical Area; Time Validity; mode mapping information for mapping a session and/or a service to a first or a second operation mode.

In a further implementation form of the second aspect, the method further includes providing, by the control unit, the at least one side-link resource pool configuration to the mobile device using dedicated per terminal device signaling.

In particular, the side-link resource pool configuration can be transmitted via dedicated per terminal device (unicast) RRC signaling. In a further implementation form of the second aspect, the dedicated per terminal device signaling comprises an RRC reconfiguration message including the side-link resource pool configuration.

In a further implementation form of the second aspect, the method further includes providing, by the control unit, the side-link resource pool configuration to the mobile device by means of broadcast communication.

In a further implementation form of the second aspect, the broadcast messages include System Information Block, SIB, information.

In particular, the SIB message is a SIB21 message.

In a further implementation form of the second aspect, the method further includes providing, by the control unit, the side-link resource pool configuration to a mobile device by means of a pre-configuration message comprising the side-link resource pool configuration.

In a further implementation form of the second aspect, the method further includes providing, by the control unit, the side-link resource pool configuration to a network node using at least one of X2, XnAP, FI, and NGAP signaling.

In a further implementation form of the second aspect, the method further includes mapping, by the control unit, a network slice to a corresponding side-link resource pool configuration. According to a third aspect, the present invention provides a mobile device for performing side- link communication for at least one slice of a communication network, wherein the mobile device is configured to obtain at least one side-link resource pool configuration, for the at least one slice, wherein the at least one side-link resource pool configuration is based on an upper layer requirement and/or a network requirement; and select resources for side-link communication based on the obtained at least one side-link resource pool configuration.

In an implementation form of the third aspect, the mobile device is further configured to provide the side-link resource pool configuration to another terminal device.

In particular, the mobile device is a user equipment, UE.

In particular, the terminal device is a user equipment, UE.

According to a fourth aspect, the present invention provides a method for performing side-link communication for at least one slice of a communication network, wherein the method comprises the steps of obtaining, by a mobile device, at least one side-link resource pool configuration, for the at least one slice, wherein the at least one side-link resource pool configuration is based on an upper layer requirement and/or a network requirement; and selecting, by the mobile device, resources for side-link communication based on the obtained at least one side-link resource pool configuration.

In an implementation form of the fourth aspect, the method further includes providing, by the mobile device, the side-link resource pool configuration to another terminal device.

In particular, the mobile device is a user equipment, UE.

In particular, the terminal device is a user equipment, UE.

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

BRIEF DESCRIPTION OF DRAWINGS

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

Fig. 1 shows a schematic view of a control unit according to an embodiment of the present invention,

Fig. 2 shows another schematic view of an operating scenario according to the present invention,

Fig. 3 shows another schematic view of an operating scenario according to the present invention,

Fig. 4 shows another schematic view of an operating scenario according to the present invention,

Fig. 5 shows another schematic view of an operating scenario according to the present invention,

Fig. 6 shows another schematic view of an operating scenario according to the present invention,

Fig. 7 shows another schematic view of an operating scenario according to the present invention,

Fig. 8 shows another schematic view of an operating scenario according to the present invention, Fig. 9 shows another schematic view of an operating scenario according to the present invention,

Fig. 10 shows a schematic view of a method according to an embodiment of the present invention,

Fig. 11 shows a schematic view of a mobile device according to an embodiment of the present invention,

Fig. 12 shows a schematic view of a method according to an embodiment of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS

Fig. 1 shows a control unit 100 according to an embodiment of the present invention.

The control unit 100 is for assisting side-link communication for at least one slice 101 of a communication network. Therefore, the control unit 100 is configured to configure, for the at least one slice 101, at least one side-link resource pool 102 based on an upper layer requirement 103 and/or a network requirement 104. Further, the control unit 100 is configured to provide a side-link resource pool configuration 105 to at least one terminal device.

In other words, by configuring the at least one side-link resource pool 102, the control unit 100 generates a side-link resource pool configuration 105.

The control unit 100 thereby allows for enabling the RAN/Network to configure side-link resource pools 102 per slice for V2X sessions. The configuration e.g. may be based on the upper layer and/or the session related requirement, which may comprise at least one of the following:

- the slice-to-resource pool initial mapping ratio (N: l, 1 :N);

- Mobile Network Operator and Vertical - resource pool and/or slice situation/availability;

- UE behavior; as well as

- application-related requirements (group formations, level of automations). In other words, the control unit 100 as shown in Fig. 1 can in particular reside in a RAN node (e.g. a gNB, eNB, CU, MN, or SN) and can be configured to:

A: Receive slice-specific NR configuration parameters (mapping policies, e.g. 1 :N or N: 1 slice to RP mapping, NR-PC5 RRM split, spectrum configurations, slice coverage, etc.) by OAM (e.g. the upper layer requirement 103) and/or slice-to-PC5 session mapping and identification by CN (using NGAP signaling) or by the UE (using RRC signaling) (e.g. the network requirement 104). It is to be noted that this step“A” is an optional step performed by the control unit 100, which is not required for general operation.

B: Select and configure (pre- or re-configure) the resource pools (e.g. the side-link resource pool 102) for the V2X sessions attached to one or more slices.

C: Communicating the resource pool configuration (e.g. the resource pool configuration 105) to the involved nodes:

1.: V-UEs using dedicated RRC signaling or System Information

2.: Affected / Involved RAN nodes using XnAP, FI signaling

In the following, several ways of acquiring slice information at RAN by means of the control unit 100 are going to be described.

Information can e.g. be obtained from a UE, , as part of the session related requirements, as it is now described in view of Fig. 2.

If a UE (as e.g. shown in Fig. 2) is configured by upper layers (OAM, CN) with certain slice- tailored resource pool configurations or has some interest on adapting the dedicated resource pools for a certain slice, Side-linkUEInformation message or UECapabilitylnformation message can be extended with more IEs to support slicing information (NSSAI, NR-PC5 Configuration requirement per slice).

Side-linkUEInformation (as in TS36.331):

“UE capable of side-link communication or V2X side-link communication or side-link discovery that is in RRC CONNECTED may initiate the procedure to indicate it is (interested in) receiving side-link communication or V2X side-link communication or side-link discovery in several cases including upon successful connection establishment, upon change of interest, upon change to a PCell broadcasting SystemInformationBlockTypel8 or SystemInformationBlockTypel9 or SystemInformationBlockType21 including sl-V2X- ConfigCommon.“

In this option, the inventive solution is the addition of Slice information (e.g. NSSAI, S-NSSAI, Slice Configuration Info) as a new IE of the Side-linkUEInformation RRC message.

UECapabilitylnformation (as in TS36.331, TS38.331):

The purpose of this procedure is to transfer UE radio access capability information from the UE to E-UTRAN. At least one of the following IEs can be introduced as follows:

UE Available Slice List: the list of available slices for the UE;

- UE Slice SL Resource Pool list: the list of resource pools that can be used by this UE for each slice.

Information can also be obtained by the control unit 100 from the Core Network (CN) as example of the session and/or upper layer requirements, as described in the following:

NG Signaling includes slice information in PDU-session granularity. For NR-V2X SL, the CN may need to provide additional IEs using NG interface for the PC5 Sessions.

CN requires to know/set the slice to session mapping for PC5, because of the following reasons:

- the 5QI model is re-used for PC5 (5QI is set by CN);

- slicing feature is end-to-end and controlled by CN;

- Licensed operation ofNR-PC5 (which is under study in 3GPP) in FR1/FR2 spectrum bands requires the session resource setup by CN.

In this solution, the PC5 Session information including slicing information can be carried using NG signaling at UE Context Setup/ Modification Request message (from Access and Mobility Function (AMF) to RAN), see TS 38.413 section 9.2.2.

Additional Information Elements (IEs) in UE Context Setup / Modification Request message over NGAP can be at least one of the following parameters:

PC5 Session Resource Setup Request List - [V2X Service ID : the identifier of the V2X service (global identifier as set by the network and/or application)

- Group-UE ID (the identifier for a set of UEs for group communications)

- S-NSSAI / NSSAI (the slice/S ST identifier for the session)

- PC5 Session Resource Setup Request Transfer (the SL resource setup request for the session)

- UE Side-link AMBR (parameters for the authorization of the PC5 session)

- SL QoS levels (5QI, PPPP) per LoA and/or slice

Information can also be obtained by the control unit 100 from the OAM as example of upper layer requirement and as as described in the following and in view of Fig. 3:

OAM (SA5) configures the RAN part of the V2X SL slice, using slice-tailored parameters (RRM policies, protocol /functional configurations) via Service-based Interface (SBI) or Itf-N.

A Slice-NR-PC5 Configuration message can be sent from OAM to RAN (in which the control unit 100 is located) with at least one of the following parameters:

- Slice Profile ID;

- NSSAI;

- RRM Policies for PC5 resources;

- PC5 monitoring configuration policies.

In the following, resource pool configuration for 1 :N or N:1 slice to resource pool mapping (which relates to the side-link resource pools 104) is going to be described, in particular in view of Fig. 4.

The assignment of resource pools to different slices is an RRC/RRM functionality which (see 1. and 2.):

1. Takes as input at least one of the following:

A: The OAM is extended for PC5 RAN slice pre-configuration parameters (as described in view of Fig. 3 and SA5 in TS28.531) and the RAN KPI per slice, e.g.: - XI side-link resource pools for slice 1, X2 for slice 2, . ..

- or side-link capacity proportional split (e.g. 30% slice 1, 70% slice 2)

B: Expected/Actual NR-PC5 radio channel conditions / load monitoring by the UEs C: Slice information from Network and/or UE (see sections above)

2. Performs the selection of side-link resource pools per slice based on the inputs in RRC/RRM, given the target objective:

- In case of distributed selection of resource pools (e.g. iterative optimization), this involves also UE-associated RRC-to-MAC signaling which may impact FI for CU-DU splits.

- In case of Dual Connectivity (DC), for multi-Radio Access Technology (RAT) deployment (opt. 4/7); the selection of pools per UE/session may come after negotiation between MN and SN (in Xn/X2). So, a negotiation phase may be needed before the selection (e.g. hypothetical resource pool selection).

In the following, communicating the Resource Pool Configuration to a UE is going to be described.

One key requirement in mode 2 (where the UE schedules the resource pools for SL) is that a RAN node communicates the resource pool configuration to the UE. In case of slice-specific resource pool configurations (e.g. 1 :N or N: 1 mapping), this information needs to pass also to the UE. This can be done with three ways:

- RRC Configuration using dedicated signaling to the UE,

- Broadcasting of this parameters in System Information (e.g. SIB21),

- Pre-configuration of the resource pools per slice.

The RRC Configuration can e.g. be communicated using dedicated signaling, as example of dedicated per terminal device signaling and in particular as part of an RRC reconfiguration message, as it is now described in view of Fig. 5.

After the Configuration by the RAN node (e.g. gNB), the RRC Re-configuration message can include an additional Information Element (IE) or parameter in SL-V2X-ConfigDedicated IE which comprises slice information. - Dedicated signaling extending current IE, for example aSL-V2X-ConfigDedicated IE and/or a new IE per slice can be also possible

The following parameters can be added in this IE:

- Slice-scheduled parameter which includes, apart from the configuration parameters as in current IE:

a. NSSAI/S-NSSAI;

b. Slice RRM policies (pre-configured policies for the RRM split between slices as initially provided at the slice setup/provisioning to the UE).

- Slice-UE selected parameter which includes the selected pool for the UE and slice, apart from the configuration parameters as in current IE:

a. NSSAI or Slice ID.

The information can e.g. be communicated using system information broadcasting, as example of the broadcast messages, as it is now described in view of Fig. 6.

The configuration can be also broadcasted over SIB21 (or SIBxx):

- new IEs can be introduced in SIBs, i.e. Slice-SL-V2X-ConfigCommon to include NSSAI and other slice-related info;

- Current IE can be also extended to support slice information, i.e. sl-V2X-ConfigCommon.

A new IE Slice-SL-V2X-ConfigCommon includes at least one of the side-link configured parameters used for V2X side-link communication per slice and the configured resource split among slices, to be broadcasted over SIB, as follows:

- nSSAI / Slice ID

- v2x-CommRxPoolList: Indicates a list of reception pools for V2X side-link communication per slice

- v2x-CommTxPoolList: Indicates a list of transmission pools for V2X side-link communication per slice

- v2x-ResourceSelectionConfig: Indicates V2X sidelink communication configurations used for UE autonomous resource selection per slice - v2x-slice RRM policies: Indicates the RRM policies for V2X side-link communication per slice as dictated by OAM.

Pre-configuration of slice to resource pool configuration is now described in view of Fig. 7.

Slice_SL-V2X-Preconfiguration, as example of the pre-configuration message, will be sent to UE either by RAN or by the Application-layer/V2X layer. Pre-configuration is enforced by RAN based on the resource situation and sent to UE over RRC signaling, e.g. using a new IE and parameters for SL: Slice_SL-V2X-Preconfiguration.

A new IE Slice_SL-V2X-Preconfiguration includes at least one of the following side-link pre configured parameters used for V2X side-link communication per slice and the preconfigured resource split among slices:

- nSSAI / Slice ID;

- v2x-CommRxPoolList: Indicates a list of reception pools for V2X side-link communication per slice;

- v2x-CommTxPoolList: Indicates a list of transmission pools for V2X side-link communication per slice;

- v2x-ResourceSelectionConfig: Indicates V2X sidelink communication configu-rations used for UE autonomous resource selection per slice;

- v2x-slice RRM policies: Indicates the RRM policies for V2X side-link communication per slice as dictated by OAM.

In the following, communicating the resource pool configuration 104 to other network nodes is going to be described:

The interaction of the control unit 100 with other network nodes (core network nodes and/or RAN nodes, in particular a gNB, eNB, CU, DU, MN, SN, RSU) is essential for notifying involved entities for the resource pool configuraton. This may allow at least one of the following operations:

Core Network to be informed by RAN for charging, session/mobility management and resource monitoring purposes. Other gNBs/eNBs to be informed for optimizing RRM in a multi-cell environment, e.g. avoiding interfence at the cell edges or for mobility management purposes (e.g. one or more vehicles of the V2X service is in coverage of other gNB/eNB).

In CU/DU split, the DU to be informed by the CU so as to perform MAC scheduling of the side-link resources in real-time.

In Dual Connectivity, in particular MN/SN architecture (Arch. Option 4/7), SN or MN to be aware of the resource pool configuration since the resource pools may be owned by the SN or MN and vehicles of the V2X service may be connected to both of them.

In Fig. 8 and Fig. 9, message charts for interacting with other gNBs and with other CN is shown. As a particular embodiment, Xn and NG signaling are shown. However, this can also be applied to interfaces like FI, X2, SI, given the scenario as described above.

In view of Fig. 8, the exchange of a resource pool configuration message per slice for side-link resources using X2/Xn/Fl signaling is now described.

This applies to scenarios when the UEs belong to different cells (or when UEs need to Handover (HO) to neighboring gNB. This message may include RP configuration and assignment parameters for the V2X SL Slice.

Non-UE associated (for Mode 1 or Mode 2):

This information may be exchanged between gNBs for HO purposes for the assignment of resource pools for a slice in a given geographical area.

Non-UE associated Resource Pool Configuration message includes at least one of the following parameters:

- V2X Service ID;

Resource Pool (RP) Assignment information (e.g. mapping table, list, matrix) ;

- NSSAI/S-NSSAI;

Slice RRM Policies;

Geographical Area;

Thresholds;

Time Validity. In view of Fig. 9, the notification of a CN (e.g. AMF/SMF) of the resource pool configuration/assignment per V2X group/slice is now going to be described.

This is required for allowing CN to either get slice analytics, perform charging, interact with application server via NEF, for mobility and session management purposes.

Non-UE-associated:

Non-UE-associated interaction in a new message or extension (RAN SIDE-LINK CONFIGURATION UPDATE message) allows to provide the resource pool configuration information to Core Network. A Slice-aware Side-link Configuration Update (non-UE specific) reporting is sent by the NG-RAN node to transfer updated information for the side-link interface instance and an acknowledgment is sent back upon reception from Core (e.g. AMF).

At least one of the following parameters can be included in Slice-aware Side-link Configuration Update message (non-UE specific):

- V2X Service ID;

Abstracted Resource Pool (RP) Assignment information (e.g. mapping table, list, matrix);

- NSSAI/S-NSSAI;

Update of Configuration;

Geographical Area;

Thresholds;

Time Validity;

Slice Statistics.

Fig.10 shows a schematic view of a method 1000. The method 1000 is for assisting side-link communication for at least one slice 101 of a communication network, wherein the method 1000 comprises the steps of configuring 1001, by a control unit 100, for the at least one slice 101 , at least one side-link resource pool 102 based on an upper layer requirement 103 and/or a network requirement 104; and providing 1002, by the control unit 100, a side-link resource pool configuration 105 to at least one terminal device.

Fig. 11 shows a schematic view of a mobile device 1100 for performing side-link communication for at least one slice 101 of a communication network. The mobile device 1100 is configured to obtain at least one side-link resource pool configuration 1101, for the at least one slice 101, wherein the at least one side-link resource pool configuration 1101 is based on an upper layer requirement 1102 and/or a network requirement 1103. The upper layer requirement 1102 and/or the network requirement 1103 correspond to the upper layer requirement 103 and/or the network requirement 104. The mobile device 1100 is further configured to select resources for side-link communication 1104 based on the obtained at least one side-link resource pool configuration 1101.

Fig. 12 shows a schematic view of a method 1200. The method is for performing side-link communication for at least one slice 101 of a communication network, wherein the method 1200 comprises the steps of obtaining 1201, by a mobile device 1100, at least one side-link resource pool configuration 1101, for the at least one slice 101, wherein the at least one side- link resource pool configuration 1101 is based on an upper layer requirement 1102 and/or a network requirement 1103. The upper layer requirement 1102 and/or the network requirement 1103 correspond to the upper layer requirement 103 and/or the network requirement 104. The method further comprises selecting 1202, by the mobile device 1100, resources for side-link communication 1104 based on the obtained at least one side-link resource pool configuration 1104.

The present invention has been described in conjunction with various embodiments as examples as well as implementations. However, other variations can be understood and effected by those persons skilled in the art and practicing the claimed invention, from the studies of the drawings, this disclosure and the independent claims. In the claims as well as in the description the word “comprising” does not exclude other elements or steps and the indefinite article“a” or“an” does not exclude a plurality. A single element or other unit may fulfill the functions of several entities or items recited in the claims. The mere fact that certain measures are recited in the mutual different dependent claims does not indicate that a combination of these measures cannot be used in an advantageous implementation.

Claims

1. A control unit (100) for assisting side-link communication for at least one slice (101) of a communication network, wherein the control unit (100) is configured to:

- configure, for the at least one slice (101), at least one side-link resource pool (102) based on an upper layer requirement (103) and/or a network requirement (104), and

- provide a side-link resource pool configuration (105) to at least one terminal device.

2. The control unit (100) according to claim 1, wherein the upper layer requirement (103) includes at least one application or service configuration parameter for a side-link communication.

3. The control unit (100) according to claim 1, wherein the network requirement (104) includes at least one network parameter, in particular a slice configuration information.

4. The control unit (100) according to any one of claims 1 to 3, wherein the at least one side- link resource pool configuration (105) comprises at least one of the following:

- Slice identifier and/or Network Slice Network Slice Selection Assistance Information, NSSAI, and/or S-NSSAI;

- Common Rx Pool List;

- Common Tx Pool List;

- Side-link Resource Pool Configuration information;

- Slice Radio Resource Management, RRM, Policies;

- Resource Selection information;

- Geographical Area;

- Time Validity;

- mode mapping information for mapping a session and/or a service to a first or a second operation mode.

5. The control unit (100) according to claim 1 or 2, wherein the control unit (100) is configured to provide the at least one side-link resource pool configuration (105) to the mobile device using dedicated per terminal device signaling.

6. The control unit (100) according to claim 5, wherein the dedicated per terminal device signaling comprises a radio resource control, RRC, reconfiguration message including the side- link resource pool configuration (105).

7. The control unit (100) according to any of the preceding claims, wherein the control unit (100) is configured to provide the side-link resource pool configuration (105) to the mobile device by means of broadcast communication.

8. The control unit (100) according to claim 7, wherein the broadcast messages include System Information Block, SIB, information.

9. The control unit (100) according to any of the preceding claims, wherein the control unit (100) is configured to provide the side-link resource pool configuration (105) to a mobile device by means of a pre-configuration message comprising the side-link resource pool configuration (105).

10. The control unit (100) according to any one of the preceding claims, wherein the control unit (100) is configured to provide the side-link resource pool configuration (105) to a network node using at least one of X2, XnAP, FI, and NGAP signaling.

11. The control unit (100) according to any one of the preceding claims, wherein the control unit (100) is configured to map a network slice to a corresponding side-link resource pool configuration (105).

12. A method (1000) for assisting side-link communication for at least one slice (101) of a communication network, wherein the method (1000) comprises the steps of:

- configuring (1001), by a control unit (100), for the at least one slice (101), at least one side- link resource pool (102) based on an upper layer requirement (103) and/or a network requirement (104), and

- providing (1002), by the control unit (100), a side-link resource pool configuration (105) to at least one terminal device.

13. A mobile device (1100) for performing side-link communication for at least one slice (101) of a communication network, wherein the mobile device (1100) is configured to: - obtain at least one side-link resource pool configuration (1101), for the at least one slice (101), wherein the at least one side-link resource pool configuration (1101) is based on an upper layer requirement (1102) and/or a network requirement (1103);

- select resources for side-link communication (1104) based on the obtained at least one side- link resource pool configuration (1101).

14. The mobile device (1100) according to claim 13, further configured to provide the side-link resource pool configuration (1101) to another terminal device.

15. A method (1200) for performing side-link communication for at least one slice (101) of a communication network, wherein the method (1200) comprises the steps of:

- obtaining (1201), by a mobile device (1100), at least one side-link resource pool configuration (1101), for the at least one slice (101), wherein the at least one side-link resource pool configuration (1101) is based on an upper layer requirement (1102) and/or a network requirement (1103);

- selecting (1202), by the mobile device (1100), resources for side-link communication (1104) based on the obtained at least one side-link resource pool configuration (1104).