Method for slice support for vehicle-to-everything services

Abstract

A wireless communication method for use in an access and mobility management function is disclosed. The wireless communication method includes transmitting allowed network slice selection assistance information (NSSAI) associated with a wireless terminal to a policy control function (PCF).

Description

[0001] This document generally relates to wireless communication.

[0002] V2X communication is a communication that fully utilizes Uu and / or PC5 reference points to support Vehicle-to-Everything (V2X) services. V2X services are realized through various types of V2X applications, i.e., Vehicle-to-Vehicle (V2V), Vehicle-to-Pedestrian (V2P), Vehicle-to-Infrastructure (V2I), and Vehicle-to-Network (V2N). The main motivations behind V2X include road safety, traffic efficiency, and energy saving. Proximity Service (ProSe) is one of the keys to enable support for V2X communication. ProSe functionality includes direct discovery and direct communication via a PC5 interface. The PC5 interface is a reference point between ProSe-enabled User Equipment (UE) for control plane and user plane for ProSe direct discovery, ProSe direct communication, and ProSe UE-to-network relay.

[0003] A network slice is a logical network that provides specific network capabilities and network characteristics. A network slice instance is a collection of network function instances and required resources (e.g., compute, storage, and networking resources) that make up a deployed network slice. Multiple network slice instances can be deployed on one shared physical network, and each network slice instance is designed to meet specific service requirements. In addition, each network slice instance is isolated from each other. To access a network slice, a UE should be authenticated by a network operator and authenticated / authorized by the owner of the network slice.

[0004] V2X communication has its own specific service requirements in terms of latency, jitters, and bandwidth. Therefore, it is possible to deploy a dedicated network slice for V2X communication. In fact, 3GPP has defined a special SST (Slice Service Type = 4) for V2X network slice. The slice concept is considered only when V2X communication is via a PDU session, i.e., via Uu interface and network. However, how to use the network slice concept via the PC5 interface is unclear, especially when the UE is not authorized by the owner of the network slice. Therefore, how to restrict the UE to use the network slice resource is also unknown.

[0005] This document relates to methods, systems, and devices for slice support for V2X services.

[0006] The present document relates to a wireless communication method for use in a policy control function, the wireless communication method comprising:

[0007] receiving, from an access and mobility management function, allowed network slice selection assistance information, NSSAI, associated with a wireless terminal.

[0008] Various embodiments can preferably implement the following features:

[0009] Preferably, at least one single NSSAI of the allowed NSSAI is associated with a vehicle-to-anything service.

[0010] Preferably, the wireless communication method further comprises receiving, from the PCF, at least one PC5 quality of service, QoS, parameter associated with at least one allowed S-NSSAI of the NSSAI; and transmitting, to a first radio access network node, the at least one PC5 QoS parameter and the at least one allowed S-NSSAI.

[0011] Preferably, the at least one PC5 QoS parameter comprises an aggregate maximum bit rate per network slice.

[0012] Preferably, the wireless communication method further comprises receiving, from the PCF, a validity area of the at least one PC5 QoS parameter.

[0013] Preferably, the wireless communication method further comprises receiving an indication of a handover of the wireless terminal to a second radio access network node; and determining, based on the validity area and a location of the wireless terminal, whether to transmit the at least one PC5 QoS parameter to the second radio access network node.

[0014] Preferably, the wireless communication method further comprises receiving, from the PCF, a vehicle-to-anything service policy comprising a mapping between at least one service and at least one S-NSSAI associated with PC5 communication; and transmitting, to the wireless terminal, the vehicle-to-anything service policy.

[0015] The present disclosure relates to a wireless communication method for use in a policy control function, the wireless communication method comprising:

[0016] receiving, from an access and mobility management function, allowed network slice selection assistance information, NSSAI, associated with a wireless terminal.

[0017] Various embodiments can preferably implement the following features:

[0018] Preferably, at least one allowed single NSSAI (S-NSSAI) of the NSSAI is associated with a vehicle-to-anything service for PC5 communication.

[0019] Preferably, the wireless communication method further includes transmitting, to the AMF, at least one PC5 quality of service, QoS, parameter associated with at least one allowed single-network slice selection assistance information, S-NSSAI, in the NSSAI.

[0020] Preferably, the at least one PC5 QoS parameter includes an aggregate maximum bit rate per network slice.

[0021] Preferably, the wireless communication method further includes transmitting, to the AMF, a validity area of the at least one PC5 QoS parameter.

[0022] Preferably, the wireless communication method further includes transmitting, to the AMF, a vehicle-to-everything service policy including a mapping between at least one service and at least one S-NSSAI associated with the PC5 communication.

[0023] The present disclosure relates to a wireless communication method for use in a radio access network node. The wireless communication method includes:

[0024] receiving, from a policy control function, PCF, via an access and mobility management function, AMF, at least one PC5 quality of service, QoS, parameter of at least one allowed single-network slice selection assistance information, S-NSSAI.

[0025] Various embodiments can preferably implement the following features:

[0026] Preferably, the at least one allowed S-NSSAI is associated with a vehicle-to-everything service for the PC5 communication.

[0027] Preferably, the wireless communication method further includes receiving, from the wireless terminal, a requested S-NSSAI and a requested QoS profile for the PC5 communication; and

[0028] transmitting, to the wireless terminal, radio bearer information for the PC5 communication when the requested S-NSSAI and the requested QoS profile are determined to be authorized based on the at least one PC5 QoS parameter per allowed S-NSSAI.

[0029] The present disclosure relates to a wireless communication method for use in a wireless terminal. The wireless communication method includes:

[0030] receiving, from a policy control function, PCF, via an access and mobility management function, AMF, a vehicle-to-everything service policy including a mapping between at least one service and at least one allowed single-network slice selection assistance information, S-NSSAI, associated with a PC5 communication.

[0031] Various embodiments can preferably implement the following features:

[0032] Preferably, the wireless communication method further comprises determining the requested S-NSSAI for the PC5 communication based on a vehicle-to-everything service policy; and

[0033] communicating the requested S-NSSAI and the requested QoS profile for the PC5 communication to a radio access network node.

[0034] Preferably, the wireless communication method further comprises receiving radio bearer information for the PC5 communication from the radio access network node; and

[0035] establishing a radio bearer for the PC5 communication with the peer wireless terminal.

[0036] The present disclosure relates to a wireless device comprising an access and mobility management function. The wireless device comprises a communication unit configured to communicate allowed network slice selection assistance information, NSSAI, associated with a wireless terminal to a policy control function, PCF.

[0037] Various embodiments can preferably implement the following features:

[0038] Preferably, the wireless device comprises a processor configured to perform a wireless communication method according to any of the preceding methods.

[0039] The present disclosure relates to a wireless device comprising a policy control function. The wireless device comprises a communication unit configured to receive allowed network slice selection assistance information, NSSAI, associated with a wireless terminal from an access and mobility management function, AMF.

[0040] Various embodiments can preferably implement the following features:

[0041] Preferably, the wireless device comprises a processor configured to perform a wireless communication method according to any of the preceding methods.

[0042] The present disclosure relates to a wireless network node. The wireless network node comprises a communication unit configured to receive at least one PC5 quality of service, QoS, parameter for at least one allowed single network slice selection assistance information, S-NSSAI, from a policy control function, PCF, via an access and mobility management function, AMF.

[0043] Various embodiments can preferably implement the following features:

[0044] Preferably, the wireless network node can comprise a processor configured to perform a wireless communication method according to any of the preceding methods.

[0045] The present disclosure relates to a wireless terminal. The wireless terminal comprises a communication unit configured to receive, from a policy control function, PCF, a vehicle-to-anything service policy via an access and mobility management function, AMF, the service policy comprising a mapping between at least one service and at least one S-NSSAI associated with a PC5 communication.

[0046] The various embodiments can preferably implement the following features:

[0047] Preferably, the wireless terminal comprises a processor configured to perform a wireless communication method according to any of the preceding methods.

[0048] The present disclosure relates to a computer program product comprising computer readable program medium code stored thereupon, which, when executed by a processor, causes the processor to implement a wireless communication method according to any of the preceding methods.

[0049] The exemplary embodiments disclosed herein are intended to provide features that will become apparent in light of the following description when taken in conjunction with the drawings. In accordance with various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. It should be understood, however, that the embodiments are presented by way of example and not limitation, and that modifications can be made by those of ordinary skill in the art to the embodiments as disclosed herein while still remaining within the scope of the present disclosure.

[0050] Accordingly, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Moreover, the specific order or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based on the nature of the

[0051] The above and other aspects and implementations are described in more detail in conjunction with the appended drawings, description and claims.

[0052] Figure 1 An architecture for V2X communication according to embodiments of the disclosure is illustrated.

[0053] Figure 2 Delivery of V2X related policies / parameters to a UE and delivery of PC5 QoS parameters to NG-RAN according to embodiments of the disclosure is illustrated.

[0054] Figure 3 An example of a schematic diagram of a wireless terminal according to embodiments of the disclosure is shown.

[0055] Figure 4 An example of a schematic diagram of a wireless network node is shown in accordance with an embodiment of the disclosure.

[0056] Figure 5 PCF provisioning N2 PC5 QoS parameters for non-roaming case is illustrated in accordance with an embodiment of the disclosure.

[0057] Figure 6 PCF provisioning N2 PC5 QoS parameters for roaming case is illustrated in accordance with an embodiment of the disclosure.

[0058] Figure 7 NG-RAN authorizing PC5 QoS parameters for network scheduled mode UE is illustrated in accordance with an embodiment of the disclosure.

[0059] Figure 8 AMF sending PC5 QoS parameters to NG-RAN based on valid area of PC5 QoS parameters is illustrated in accordance with an embodiment of the disclosure.

[0060] Figure 9 A flowchart of a process is shown in accordance with an embodiment of the disclosure.

[0061] Figure 10 A flowchart of a process is shown in accordance with an embodiment of the disclosure.

[0062] Figure 11 A flowchart of a process is shown in accordance with an embodiment of the disclosure.

[0063] Figure 12 A flowchart of a process is shown in accordance with an embodiment of the disclosure.

[0064] Figure 1 Architecture for V2X communication is illustrated in accordance with an embodiment of the disclosure. In the following, the functions of various elements of Figure 1 are described.

[0065] A UE supporting V2X requirements and associated procedures. A V2X enabled UE supports V2X direct communication over the PC5 interface. In addition, a V2X enabled UE also supports retrieving V2X related policies / parameters from the core network or from an application server.

[0066] These V2X related policies / parameters can also be pre-configured in the UE. The UE can be configured to use a network scheduled mode of operation or a UE autonomous resource selection mode. For the network scheduled mode of operation, the radio resources for V2X services are controlled by the network. For the UE autonomous resource selection mode, the UE selects the radio resources for V2X services based on its local policies / parameters.

[0067] The Next Generation-Radio Access Network (NG-RAN) manages radio resources for V2X direct communication for network scheduled mode UEs. The NG-RAN also provides V2X authorization and V2X PC5 QoS parameters to V2X-enabled UEs.

[0068] The Access and Mobility Management function (AMF) includes the following functionalities: registration management, connection management, reachability management, and mobility management. The AMF also performs access authentication and access authorization. The AMF is the Non-Access Stratum (NAS) security anchor and relays Security Management (SM) NAS messages between the UE and the SMF. Based on subscription, the AMF provides V2X authorization indication to the NG-RAN.

[0069] The Session Management Function (SMF) includes the following functionalities: session establishment, modify and release, UE IP address allocation and management (including optional authorization function), selection and control of UP function, downlink data notification, etc.

[0070] The User Plane Function (UPF) includes the following functionalities: acting as an anchor point for intra- / inter-Radio Access Technology (RAT) mobility, packet routing and forwarding, traffic usage reporting, QoS handling for user plane, downlink packet buffering and downlink data notification triggering, etc.

[0071] The Policy Control Function (PCF) provides policy rules to control plane functions to enforce these rules. Specifically, the PCF provides access and mobility related policies to the AMF and the AMF enforces them during mobility procedures, provides UE access selection and PDU session selection related policies (UE policies) to the AMF and the AMF forwards them to the UE. The PCF also provides V2X related policies / parameters to the UE / NG-RAN via the AMF. The PCF can be deployed in a distributed manner and each PCF can support different functions in the same Public Land Mobile Network (PLMN).

[0072] The Network Slice Specific Authentication and Authorization Function (NSSAAF) leverages an Authentication, Authorization, and Accounting (AAA) server to support Network Slice Specific Authentication and Authorization (NSSAA). The AMF performs NSSAA for S-NSSAIs (Single Network Slice Selection Assistance Information) to which it is subject based on subscription information of the HPLMN. Only S-NSSAIs that successfully authenticate and authorize are included by the AMF in the allowed NSSAI.

[0073] The AAA server performs slice authentication and authorization for each S-NSSAI.

[0074] In the present disclosure, “PC5” can be equal to “PC5 interface” and vice versa.

[0075] V2X related policies / parameters on the PC5 interface in the UE include the following non-exclusive information:

[0076] 1) Authorization policy indicating that the UE is authorized to perform V2X communication over the PC5 reference point in a PLMN when the UE is served by a radio network and indicating whether the UE is authorized to perform V2X communication over the PC5 reference point when the UE is not served by a radio network;

[0077] 2) Policies / parameters when selecting the PC5 interface:

[0078] - mapping of V2X service types (e.g., Provider Service Identifier (PSID) or Intelligent Transportation System Application Identifiers (ITS-AID)) to V2X frequencies with geographical areas;

[0079] - mapping of destination layer-2 ID and V2X service type, e.g., PSID or ITS-AID for V2X applications for broadcast;

[0080] - mapping of destination layer-2 ID and V2X service type, e.g., PSID or ITS-AID for V2X applications for groupcast;

[0081] - Mapping of default destination layer-2 ID and V2X service type for initial signaling to establish unicast connection, e.g. PSID or ITS-AID of V2X application;

[0082] - PC5 Quality-of-Service (QoS) mapping configuration:

[0083] a. Inputs from V2X application layer:

[0084] i. V2X service type (e.g. PSID or ITS-AID);

[0085] ii. (optional) V2X application requirements for V2X service type, e.g. priority requirement, reliability requirement, latency requirement, range requirement.

[0086] b. Outputs:

[0087] i. PC5 QoS parameters, i.e. Presentation Quality Index (PQI) and conditionally other parameters such as Maximum Flow Bit Rate (MFBR), Guaranteed Flow Bit Rate (GFBR), Per-link Aggregate Maximum Bit Rate (AMBR), etc.

[0088] V2X PC5 related parameters sent to NG-RAN include the following non-exclusive information:

[0089] - "V2X service authorized" indication, indicating that the UE is authorized to use V2X communication over PC5 reference point as a vehicle UE, pedestrian UE or both;

[0090] - UE-PC5-AMBR per PC5 RAT and cross-RAT PC5 control authorization, if applicable, used by NG-RAN for resource management of PC5 transmission of the UE for V2X service in network scheduling mode;

[0091] - PC5 QoS parameters, used by NG-RAN for resource management of PC5 transmission of the UE for V2X service in network scheduling mode.

[0092] Figure 2 It is explained how V2X related policies / parameters are delivered to the UE and how PC5 QoS parameters are delivered to the NG-RAN according to embodiments of the disclosure. In the following, the steps illustrated in Figure 2 are described with reference to the step numbers. Figure 2 illustrated steps.

[0093] 1. The UE initiates a registration request to the NG-RAN. The NG-RAN selects an AMF and forwards the registration request to the AMF. This message includes PC5 capabilities for V2X.

[0094] 2. The AMF performs the registration procedure and accepts the UE registration. The AMF sends a Registration Accept message to the UE.

[0095] 3. During the registration procedure, the AMF selects a PCF for the UE policy and sends a Npcf_UEPolicyControl_Create request to the selected PCF, which includes the PC5 capabilities for V2X indicated by the UE in step 1.

[0096] 4. The PCF sends a Npcf_UEPolicyControl_Create response to the AMF. Based on local configuration, the PCF determines the V2X related policies / parameters on PC5 corresponding to the UE and the PC5 QoS parameters used by the NG-RAN corresponding to the UE.

[0097] 5. The PCF sends a Namf_Communication_N1N2MessageTransfer request to the AMF including the V2X related policies / parameters determined in step 4. The AMF stores the PC5 QoS parameters as part of the UE context.

[0098] 6. The AMF forwards the PC5 QoS parameters in a NGAP message to the NG-RAN.

[0099] 7. The AMF forwards the V2X related policies to the UE. Step 7 can be piggybacked in step 6.

[0100] 8. When the UE needs to initiate V2X communication via PC5 and when using the network scheduled mode of operation, the UE determines the requested QoS profile and sends a SidelinkUEInformationNR (requested QoS profile) to the NG-RAN.

[0101] 9. The NG-RAN performs the authorization and sends an RRC reconfiguration towards the UE and provides the authorized QoS profile to the UE. The UE then initiates the direct communication towards the target UE by using the authorized QoS profile.

[0102] Figure 2 The illustrated procedure does not consider the slice concept. In particular, when the UE is not authenticated to use a network slice for V2X, it is unclear how to restrict the UE to use direct communication via PC5 interface deployed with the network slice.

[0103] Figure 3A schematic diagram of a wireless terminal 30 according to an embodiment of the present disclosure. The wireless terminal 30 can be a user equipment (UE), a mobile phone, a laptop, a tablet, an e-book, or a portable computer system, and is not limited herein. The wireless terminal 30 can include a processor 300 such as a microprocessor or an application specific integrated circuit (ASIC), a storage unit 310, and a communication unit 320. The storage unit 310 can be any data storage device that stores program codes 312 accessed and executed by the processor 300. Embodiments of the storage unit 310 include, but are not limited to, a Subscriber Identity Module (SIM), a Read-Only Memory (ROM), a flash memory, a Random-Access Memory (RAM), a hard disk, and an optical data storage device. The communication unit 320 can be a transceiver, and is used to transmit and receive signals (e.g., messages or packets) according to the processing results of the processor 300. In an embodiment, the communication unit 320 transmits and receives signals via at least one antenna 322 shown. Figure 3

[0104] In an embodiment, the storage unit 310 and the program codes 312 can be omitted, and the processor 300 can include a storage unit in which the program codes are stored.

[0105] The processor 300 can implement any of the steps in the exemplary embodiments on the wireless terminal 30, for example, by executing the program codes 312.

[0106] The communication unit 320 can be a transceiver. The communication unit 320 can alternatively or additionally incorporate a transmission unit and a reception unit configured to transmit and receive signals to and from a wireless network node (e.g., a base station), respectively.

[0107] Figure 4 ​This diagram relates to a wireless network node 40 according to an embodiment of the present disclosure. The wireless network node 40 may be a satellite, base station (BS), network entity, mobility management entity (MME), serving gateway (S-GW), packet data network (PDN) gateway (P-GW), radio access network (RAN), next-generation RAN (NG-RAN), data network, core network, or radio network controller (RNC), and is not limited herein. Furthermore, the wireless network node 40 may include (perform) at least one network function, such as access and mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), application function (AF), etc. The wireless network node 40 may include a processor 400 (such as a microprocessor or ASIC), a storage unit 410, and a communication unit 420. The storage unit 410 may be any data storage device storing program code 412 accessed and executed by the processor 400. Examples of storage units 410 include, but are not limited to, SIM, ROM, flash memory, RAM, hard disk, and optical data storage devices. Communication unit 420 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) based on the processing results of processor 400. In this example, communication unit 420 is connected via... Figure 4 At least one antenna 422 shown transmits and receives signals.

[0108] In this embodiment, the storage unit 410 and the program code 412 may be omitted. The processor 400 may include a storage unit storing program code.

[0109] The processor 400 can implement any of the steps described in the exemplary embodiments on the wireless network node 40, for example, by executing program code 412.

[0110] The communication unit 420 may be a transceiver. The communication unit 420 may alternatively or additionally combine a transmitting unit and a receiving unit, which are respectively configured to transmit signals to and receive signals from a wireless terminal (e.g., a user equipment).

[0111] Generally, in embodiments, the AMF performs slice authentication and authorization procedure during the UE registration procedure. When the S-NSSAI of V2X type is successfully authenticated and authorized, the PCF provides the authorized PC5 QoS parameters to the NG-RAN via the AMF and / or the V2X related policy over PC5 to the UE via the AMF. Otherwise, the PCF can not provide the PC5 QoS parameters and / or the V2X related policy over PC5 to the NG-RAN and the UE, respectively.

[0112] In embodiments, when the UE requests radio resource authorization from the NG-RAN, the UE provides the requested S-NSSAI towards the NG-RAN, so that the NG-RAN can perform V2X authorization based on the requested S-NSSAI and the information provided from the AMF.

[0113] In embodiments, the V2X related policy / parameters over PC5 sent to the UE is enhanced to include the mapping of V2X service type (e.g. PSID or ITS-AID) to network slice (e.g. S-NSSAI).

[0114] In embodiments, the V2X PC5 related parameters sent to the NG-RAN is enhanced, so that the PC5 QoS parameters are per S-NSSAI. In addition, the UE-PC5-Slice-AMBR per S-NSSAI can be introduced to the V2X PC5 related parameters sent to the NG-RAN to identify the aggregated MBR over PC5 per slice.

[0115] In embodiments, the PC5 QoS information sent to the AMF is extended to include the tracking area (TA) list for PC5 QoS parameters as well as the area (e.g. validity area) for the validity of PC5 QoS parameters, so that the AMF can determine whether the PC5 QoS parameters provided by the PCF can be used for the NG-RAN based on the current location of the UE.

[0116] Example 1

[0117] Figure 5 A PCF provisioning N2 PC5 QoS parameters for non-roaming case according to embodiments of the disclosure is illustrated.

[0118] As Figure 5 illustrated, after the V2X type NSSAI is successfully authenticated and authorized, the AMF provides the V2X type NSSAI towards the PCF. Then, the PCF provides the PC5 QoS parameters based on the V2X type NSSAI to the NG-RAN.

[0119] Specifically,Figure 5 The steps shown are as follows, where the numbering corresponds to Figure 5 The numbering shown:

[0120] 1. The UE initiates a registration request message towards the NG-RAN. The UE provides the requested NSSAI in the message. The UE also provides the PC5 capability for V2X in this message. The NG-RAN selects an AMF and forwards the registration request to the AMF.

[0121] 2. The AMF performs the registration procedure and accepts the UE registration. The AMF allocates a 5G-GUTI (5G Global Unique Temporary Identifier) to identify the UE. The AMF determines the allowed NSSAI that the UE is allowed to use in the current registration area and sends a registration accept message towards the UE (registration area, allowed NSSAI). The allowed NSSAI does not include S-NSSAI subject to NSSAA (Network Slice Specific Authentication and Authorization).

[0122] 3. When the subscription indicates that S-NSSAI is subject to NSSAA, the AMF sends a Nnssaaf_NSSAA_Authentication request to the NSSAAF (S-NSSAI) to perform slice authentication and authorization for each S-NSSAI.

[0123] 4. The NSSAAF and AAA perform the slice authentication and authorization procedure. There can be several messages exchanged between the UE and the AAA.

[0124] 5. The NSSAAF sends a Nnssaaf_NSSAA_Authentication response to the AMF (result, S-NSSAI) indicating whether the S-NSSAI has been successfully authenticated and authorized. After this step, the AMF then adds the S-NSSAI to the allowed NSSAI and sends the new allowed NSSAI to the UE.

[0125] 6. If there are any new V2X type S-NSSAI within the allowed NSSAI and the UE supports the PC5 capability for V2X, the AMF selects a PCF for V2X related policy and sends a Npcf_UEPolicyControl_Create request to the PCF including the PC5 capability for V2X indicated by the UE in step 1. The AMF can also provide the V2X type S-NSSAI to the PCF.

[0126] 7. The PCF sends a Npcf_UEPolicyControl_Create response to the AMF.

[0127] 8. Based on the local configuration and the V2X-type S-NSSAI, the PCF determines the V2X policy and PC5 QoS parameters on PC5 for the UE. If the PCF determines that the V2X-type S-NSSAI is for PC5 communication, the PCF can include a new parameter UE-PC5-Slice-AMBR in the PC5 QoS parameters that only applies to the V2X-type S-NSSAI.

[0128] The PCF sends a Namf_Communication_N1N2MessageTransfer request to the AMF that includes the V2X-related policy and authorized PC5 QoS parameters for each V2X-type S-NSSAI. If no V2X-type S-NSSAI is received from the AMF, the PCF provides the complete V2X-related policy and PC5 QoS parameters on PC5 for the UE to the AMF.

[0129] The AMF stores the PC5 QoS parameters as part of the UE context.

[0130] 9. The AMF forwards the authorized PC5 QoS parameters for each V2X-type S-NSSAI to the NG-RAN in an NGAP message. The NG-RAN stores the authorized PC5 QoS parameters.

[0131] 10. The AMF forwards the V2X-related policy to the UE. Step 10 can be piggybacked in step 9.

[0132] Example 2

[0133] Figure 6 It is illustrated the PCF provisioning of N2 PC5 QoS parameters for roaming cases according to embodiments of the disclosure. In particular, Figure 6 It is illustrated the provisioning of V2X-related policy and PC5 QoS parameters based on the V2X-type NSSAI received by the PCF from the AMF for roaming cases.

[0134] In particular, Figure 6 The steps illustrated are as follows, where the numbering corresponds to Figure 6 The numbering illustrated is:

[0135] 1. The UE initiates a registration request message towards the NG-RAN. The UE provides the requested NSSAI in the message. The UE also provides the PC5 capability for V2X in the message. The NG-RAN selects an AMF and forwards the registration request to the AMF.

[0136] 2. The AMF performs the registration procedure and accepts the UE registration. The AMF allocates a 5G-GUTI (5G Globally Unique Temporary Identifier) to identify the UE. The AMF determines the allowed NSSAI that the UE is allowed to use in the current registration area and sends a Registration Accept message towards the UE (Registration Area, Allowed NSSAI). The Allowed NSSAI does not include the S-NSSAI subject to NSSAA (Network Slice Specific Authentication and Authorization).

[0137] 3. When the subscription indicates that the S-NSSAI is subject to NSSAA, the AMF sends a Nnssaaf_NSSAA_Authentication request to the NSSAAF (S-NSSAI) to perform slice authentication and authorization for each S-NSSAI.

[0138] 4. The NSSAAF and the AAA perform the slice authentication and authorization procedure. There can be several messages exchanged between the UE and the AAA.

[0139] 5. The NSSAAF sends a Nnssaaf_NSSAA_Authentication response to the AMF (Result, S-NSSAI) indicating whether the S-NSSAI has been successfully authenticated and authorized. After this step, the AMF then adds the S-NSSAI to the Allowed NSSAI and sends the new Allowed NSSAI to the UE.

[0140] 6. If there are any new V2X type S-NSSAI within the Allowed NSSAI and the UE supports PC5 capability for V2X, the AMF selects the H-PCF (PCF in home PLMN) and V-PCF (PCF in visited PLMN) for V2X related policy and sends a Npcf_UEPolicyControl_Create request to the V-PCF including the PC5 capability for V2X indicated by the UE in step 1. The AMF also provides the V2X type of NSSAI and the corresponding mapped HPLMN NSSAI to the V-PCF.

[0141] 7. The V-PCF sends a Npcf_UEPolicyControl_Create request to the H-PCF including the PC5 capability for V2X received in step 3. If received, the V-PCF also includes the corresponding mapped HPLMN V2X type NSSAI to the H-PCF.

[0142] 8. The H-PCF determines V2X related policies and authorized PC5 QoS parameters over PC5 based on the mapped HPLMN V2X type S-NSSAIs for the UE. If the H-PCF determines that V2X type S-NSSAIs are used for PC5 communication, the H-PCF can include in the PC5 QoS parameters a new parameter UE-PC5-slice-AMBR that only applies to the mapped HPLMN V2X type S-NSSAIs. The H-PCF sends a Npcf_UEPolicyControl_Create response to the V-PCF including the determined V2X related policies information and authorized PC5 QoS parameters for each mapped HPLMN V2X type S-NSSAI.

[0143] 9. The V-PCF sends a Npcf_UEPolicyControl_Create response to the AMF.

[0144] 10. Based on local configuration, the V-PCF can modify the authorized PC5 QoS parameters received from the H-PCF. The V-PCF sends a Namf_Communication_N1N2MessageTransfer request to the AMF including the received V2X related policies and authorized PC5 QoS parameters for each V2X type S-NSSAI within the allowed NSSAI. The AMF stores the PC5 QoS parameters as part of the UE context.

[0145] 11. The AMF forwards the authorized PC5 QoS parameters for each V2X type S-NSSAI in an NGAP message to the NG-RAN. The NG-RAN stores the authorized PC5 QoS parameters.

[0146] 12. The AMF forwards the V2X related policies to the UE. Step 12 can be piggybacked in step 11.

[0147] Example 3

[0148] Figure 7 It is illustrated that the NG-RAN authorizes PC5 QoS parameters for network scheduled mode UEs according to embodiments of the disclosure. In particular, Figure 7 It is illustrated the authorization of resource requests from network scheduled mode UEs by the NG-RAN.

[0149] In particular, Figure 7 The illustrated steps are as follows, where the numbering corresponds to Figure 7 The illustrated numbering:

[0150] 1. When an application in UE1 needs to communicate via PC5, UE1 sends a SideLinkUEInformationNR message towards NG-RAN to request authorization for PC5 communication. Based on V2X related policy, UE determines the requested S-NSSAI and the requested PC5 QoS profile for the application and includes them in the message. Each PC5 QoS profile includes a QoS flow identifier.

[0151] 2. Based on the authorized PC5 QoS parameters per S-NSSAI received from AMF, NG-RAN determines whether the requested S-NSSAI is authorized and the requested PC5 QoS profile is authorized. If the request is authorized, NG-RAN sends an RRC reconfiguration to UE1 to establish radio bearers over PC5. The RRC reconfiguration includes radio bearer information identified by radio bearer identity and mapping information between authorized QoS flow identifiers and radio bearer identities.

[0152] 3. UE1 sends an RRC reconfiguration complete to NG-RAN.

[0153] 4. UE1 sends a direct link setup request towards UE2. UE1 determines the target UE2 address and the service information of the application from V2X related policy. In an embodiment, the direct link setup request can include service information, source user information and target user information.

[0154] 5. Based on the target user information, UE2 identifies that it is the target UE. UE2 initiates a direct link authentication request towards UE1 to perform mutual authentication and derive new security keys shared between the two UEs. The message includes a key establishment information container.

[0155] 6. If the target UE determines that the direct link authentication request (DIRECT LINK AUTHENTICATION REQUEST) message can be received, the target UE shall create a direct link authentication response (DIRECT LINK AUTHENTICATION RESPONSE) message. The message includes a key establishment information container.

[0156] 7. After mutual authentication is successful and security keys are generated between the two UEs, UE2 sends a direct link security mode command to establish security between the two UEs. The message includes security algorithms for integrity protection and ciphering protection. UE2 shall not cipher the direct link security mode command (DIRECT LINK SECURITY MODE COMMAND) message but shall integrity protect it with the new security context.

[0157] 8. UE1 establishes a security context and sends a direct link security mode command to UE2 to complete the process. The selected security algorithm and key are used for integrity protection and encryption of all PC5 signaling messages exchanged on this PC5 unicast link between the UEs, and the security context can be used to protect all PC5 user plane data exchanged on this PC5 unicast link between the UEs. This message includes an authorized PC5 QoS profile, which includes QoS flow identifiers and will be encrypted and integrated.

[0158] 9. UE2 determines the requested S-NSSAI that the application can use based on V2X-related policies and sends a SideLinkUEInformationNR message to the NG-RAN for resource authorization. This message includes the requested S-NSSAI received from UE1 and the requested PC5 QoS profile. Each PC5 QoS profile includes a QoS flow identifier.

[0159] 10. Based on the authorized PC5 QoS parameters for each S-NSSAI received from the AMF, the NG-RAN determines whether the requested S-NSSAI is authorized and whether the requested PC5 QoS profile is authorized. If the request is authorized, the NG-RAN sends an RRC reconfiguration to UE2 to establish a radio bearer on PC5. The RRC reconfiguration includes radio bearer information identified by the radio bearer identifier and mapping information between the authorized QoS flow identifier and the radio bearer identifier.

[0160] 11. UE2 sends an RRC reconfiguration message to NG-RAN.

[0161] 12. Based on the radio bearer information, UE2 sends an RRC reconfiguration side link to UE1 to establish a radio bearer on PC5.

[0162] 13. UE1 allocates radio bearer resources and sends an RRC reconfiguration completion sidelink to UE2.

[0163] 14. UE2 sends a direct link establishment acceptance to UE1. In this embodiment, the message includes an accepted QoS profile, which includes a QoS flow identifier.

[0164] 15. Based on the radio bearer information from NG-RAN and the QoS profile received from UE1, UE1 sends an RRC reconfiguration sidelink to UE2 to establish a radio bearer on PC5.

[0165] 16. UE2 allocates radio bearer resources and sends an RRC reconfiguration completion sidelink to UE1.

[0166] After this procedure, a QoS flow and associated radio bearer is established over PC5 between UE1 and UE2. UE1 and UE2 can start PC5 communication over the QoS flow.

[0167] Example 4

[0168] Figure 8 It is illustrated that the AMF sends PC5 QoS parameters to the NG-RAN based on the valid area for the PC5 QoS parameters according to embodiments of the disclosure.

[0169] In particular, Figure 8 The steps shown are as follows, where the numbering corresponds to Figure 8 The numbering shown is:

[0170] 1. The UE initiates a registration request message towards the NG-RAN. The UE provides the requested NSSAI in the message. The UE also provides the PC5 capability for V2X in the message. The NG-RAN selects an AMF and forwards the registration request to the AMF.

[0171] 2. The AMF performs the registration procedure and accepts the UE registration. The AMF allocates a 5G-GUTI (5G Global Unique Temporary Identifier) to identify the UE. The AMF determines the allowed NSSAI that the UE is allowed to use in the current registration area and sends a registration accept message towards the UE (registration area, allowed NSSAI).

[0172] 3. If there is any new V2X type S-NSSAI within the allowed NSSAI and the UE supports the PC5 capability for V2X, the AMF selects a PCF for V2X related policy and sends an Npcf_UEPolicyControl_Create request to the PCF including the PC5 capability for V2X indicated by the UE in step 1. The AMF can also provide the V2X type S-NSSAI to the PCF.

[0173] 4. The PCF sends an Npcf_UEPolicyControl_Create response to the AMF.

[0174] 5. Based on local configuration and the V2X type S-NSSAI, the PCF determines the V2X policy on PC5 and PC5 QoS parameters for the UE along with the valid area for the PC5 QoS parameters. If the PCF determines that the V2X type S-NSSAI is used for PC5 communication, the PCF can include a new parameter UE-PC5-slice-AMBR in the PC5 QoS parameters that only applies to the V2X type S-NSSAI.

[0175] The PCF sends a Namf_Communication_N1N2MessageTransfer request to the AMF including the V2X related policies, authorized PC5 QoS parameters and the corresponding validity area. If no V2X type S-NSSAI is received from the AMF, the PCF provides the complete V2X related policies and PC5 QoS parameters for the UE to the AMF.

[0176] The AMF stores the PC5 QoS parameters and the corresponding validity area as part of the UE context.

[0177] 6. The AMF forwards the authorized PC5 QoS parameters for each V2X type S- NSSAI to the NG-RAN in NGAP messages. The NG-RAN stores the authorized PC5 QoS parameters.

[0178] 7. The AMF forwards the V2X related policies to the UE. Step 7 can be piggybacked in step 6.

[0179] 8. The UE moves (handover) from NG-RAN1 to NG-RAN2 (e.g., via a handover procedure).

[0180] 9. If the validity area for the PC5 QoS parameters is received in step 5, the area is used by the AMF to determine based on the current location of the UE whether the PC5 QoS parameters provided by the PCF are applicable for NG-RAN2. If the location of the UE is outside the area indicated by the "validity area for PC5 QoS parameters", the AMF does not send the PC5 QoS parameters to NG-RAN2.

[0181] Figure 9 A flowchart of a process in accordance with an embodiment of the present disclosure is shown. Figure 9 The illustrated process can be used in a wireless device including (e.g., executing) an AMF and includes the following steps:

[0182] Step 900: Transmit, to a PCF, allowed NSSAI associated with a wireless terminal (e.g., UE).

[0183] In Figure 9 In the illustrated process, the wireless device (e.g., AMF) transmits allowed NSSAI to a PCF, e.g., when it is determined that there is new allowed NSSAI. In embodiments, the allowed NSSAI includes at least one (allowed) S-NSSAI.

[0184] In an embodiment, at least one single NSSAI in the allowed NSSAI is associated with V2X (e.g., service, application, or network slice). For example, when it is determined that at least one S-NSSAI within the allowed NSSAI is associated with a V2X service and the wireless terminal supports PC5 capability for V2X, the wireless device transmits the allowed NSSAI to the PCF.

[0185] In an embodiment, the wireless device receives, from the PCF, at least one PC5 QoS parameter associated with at least one allowed S-NSSAI in the NSSAI, and transmits the at least one PC5 QoS parameter and the at least one allowed S-NSSAI to a first radio access network (RAN) node (e.g., NG-RAN).

[0186] In an embodiment, the at least one PC5 QoS parameter includes an AMBR per network slice.

[0187] In an embodiment, the wireless device receives, from the PCF, a validity area of the at least one PC5 QoS parameter.

[0188] In an embodiment, when receiving an indication of a handover of the wireless terminal to a second RAN node, the wireless device determines whether to transmit the at least one PC5 QoS parameter to the second RAN node based on a validity area and a location of the wireless terminal. For example, when the wireless terminal remains within the validity of the at least one PC5 QoS parameter, the wireless device transmits the at least one PC5 QoS parameter to the second RAN node. Otherwise, the wireless device does not transmit the at least one PC5 QoS parameter to the second RAN node.

[0189] In an embodiment, the wireless device receives, from the PCF, a V2X service policy including a mapping between at least one service and at least one S-NSSAI associated with PC5 communication, and transmits the V2X service policy to the wireless terminal.

[0190] Figure 10 A flowchart of a process in accordance with an embodiment of the present disclosure is shown. Figure 10 The illustrated process can be used in a wireless device including (e.g., executing) a PCF, and includes the following steps:

[0191] Step 1000: receive, from an access and mobility management function, allowed network slice selection assistance information associated with a wireless terminal.

[0192] In Figure 10 In the illustrated process, the wireless device (i.e., PCF) receives, from an AMF, allowed NSSAI associated with a wireless terminal (e.g., UE).

[0193] In an embodiment, at least one S-NSSAI in the allowed NSSAI is associated with a V2X service (e.g., application or network slice) for PC5 communication.

[0194] In an embodiment, the PCF transmits at least one PC5 QoS parameter associated with at least one allowed S-NSSAI in the NSSAI to the AMF. For example, the PCF can determine that at least one allowed S-NSSAI in the allowed NSSAI is associated with a V2X service and transmit at least one PC5 QoS parameter to the AMF.

[0195] In an embodiment, the at least one PC5 QoS parameter includes an AMBR per network slice.

[0196] In an embodiment, the wireless device can transmit a validity area of the at least one PC5 QoS parameter to the AMF.

[0197] In an embodiment, the wireless device can transmit a V2X service policy to the AMF, the V2X service policy including a mapping between at least one service and at least one S-NSSAI associated with PC5 communication.

[0198] Figure 11 A flowchart of a process in accordance with an embodiment of the disclosure is shown. Figure 11 The illustrated process can be used in a wireless network node (e.g., RAN or NG-RAN) and includes the following steps:

[0199] Step 1100: receiving, via an access and mobility management function, at least one PC5 quality of service parameter of at least one allowed single network slice selection assistance information from a policy control function.

[0200] In Figure 11 In the illustrated process, the wireless network node receives, via the AMF, at least one PC5 QoS parameter of at least one allowed S-NSSAI from the PCF.

[0201] In an embodiment, at least one allowed S-NSSAI is associated with a V2X service for PC5 communication.

[0202] In an embodiment, a wireless network node can receive, from a wireless terminal (e.g., UE), a requested S-NSSAI and a requested QoS profile for a PC5 communication, and determine whether to authorize the requested S-NSSAI and the requested QoS profile for the PC5 communication based on at least one PC5 QoS parameter of each allowed S-NSSAI received. When the requested S-NSSAI and the requested QoS profile are determined to be authorized based on the at least one PC5 QoS parameter of each allowed S-NSSAI received, the wireless network node transmits radio bearer information for the PC5 communication to the wireless terminal.

[0203] Figure 12 A flowchart of a process in accordance with an embodiment of the disclosure is shown. Figure 12 The illustrated process can be used in a wireless terminal (e.g., UE), and includes the following steps:

[0204] Step 1200: receiving, from a policy control function via an access and mobility management function, a vehicle-to-everything service policy including a mapping between at least one service and at least one allowed single network slice selection assistance information associated with a PC5 communication.

[0205] In an embodiment, the wireless terminal receives, from the RAN node, radio bearer information for the PC5 communication based on the requested S-NSSAI and the requested QoS profile being authorized. Figure 12 In the illustrated process, the wireless terminal receives, from a PCF via an AMF, a V2X service policy. In this embodiment, the V2X service policy includes a mapping between at least one service and at least one allowed S-NSSAI associated with a PC5 communication.

[0206] In an embodiment, the wireless terminal also determines a requested S-NSSAI for the PC5 communication based on the V2X service policy, and transmits the requested S-NSSAI and a related requested QoS profile to a RAN node for the PC5 communication.

[0207] In an embodiment, the wireless terminal receives, from the RAN node, radio bearer information for the PC5 communication, e.g., when the requested S-NSSAI and the requested QoS profile are authorized. In this case, the wireless terminal establishes a radio bearer for the PC5 communication with the peer wireless terminal.

[0208] In summary, it is apparent from the foregoing description that embodiments include the following general aspects.

[0209] The AMF provides allowed V2X-type S-NSSAIs to the PCF.

[0210] The AMF receives, from the PCF, PC5 QoS parameters for the allowed V2X-type S-NSSAIs.

[0211] The AMF sends PC5 QoS parameters and allowed V2X-type S-NSSAIs to the NG-RAN.

[0212] The PC5 QoS parameters include an aggregate MBR per (network) slice.

[0213] The PCF receives allowed V2X-type S-NSSAIs from the AMF.

[0214] The PCF sends PC5 QoS parameters for the allowed V2X-type S-NSSAIs to the AMF.

[0215] The PCF sends the validity area of the PC5 QoS parameters to the AMF.

[0216] The PCF sends a mapping of applications (e.g., services) to S-NSSAIs for PC5 communication to the UE.

[0217] The NG-RAN receives authorized PC5 QoS parameters for allowed V2X-type S-NSSAIs from the AMF. The NG-RAN receives requested S-NSSAIs and requested QoS profiles from the UE for authorization.

[0218] The NG-RAN sends radio bearer information to the UE after the requested S-NSSAIs and requested QoS profiles are authorized.

[0219] The UE determines requested S-NSSAIs and requested QoS profiles for PC5 communication.

[0220] The UE sends requested S-NSSAIs and requested QoS profiles to the NG-RAN for authorization.

[0221] The UE receives radio bearer information from the NG-RAN.

[0222] The UE establishes a radio bearer towards a peer UE.

[0223] While various embodiments of the present disclosure have been described above, it should be understood that they have been presented by way of example only, and not limitation. Likewise, the various figures can depict example architectures or configurations, which provide illustration of the various features and functionality described herein. It should be understood, however, that the present disclosure is not limited to the illustrated example architectures or configurations, but can be implemented using a variety of alternative architectures and configurations. Additionally, it is contemplated that one or more features of one embodiment can be combined with one or more features of another embodiment. Furthermore, it is contemplated that features of the present disclosure can be implemented using software, hardware or a combination thereof. It is therefore appreciated that specific structural and functional details disclosed herein are not to be interpreted as limiting, but are to be understood as being merely representative examples of the present disclosure.

[0224] It also should be understood that any reference to an element or element in the singular is not intended to mean "one and only one" unless specifically so stated, but instead "one or more." Unless specifically stated otherwise, the term "some" refers to one or more than one. Terms such as "first" and "second" are used to denote a difference between elements, however, such elements should not be limited by these terms. That is, a first element could be termed a second element without departing from the scope of the example or example.

[0225] Further, those of ordinary skill in the art will appreciate that the information and signals described herein can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols that can be referenced throughout the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0226] Those of skill would further appreciate that any of the various illustrative logical blocks, units, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two), firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as "software" or a "software module"), or any combination of these. It should be appreciated that one or more computer programs (which can be stored or executed by a system) can be

[0227] To clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, modules, circuits and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware or software or any combination thereof, depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure. In accordance with various embodiments, a processor, device, component, circuit, structure, machine, unit, etc. can be configured to perform one or more of the functions described herein. As used herein in relation to specific operations or functions, the terms "configured to," "programmed to," "employing," or "employing a" mean physically structured, programmed and / or arranged to perform the specific operations or functions.

[0228] Furthermore, those skilled in the art will appreciate that the various illustrative logical blocks, modules, circuits, and circuits described herein can be implemented or performed with integrated circuits (ICs): general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, or any combination thereof. The logical blocks, units, and circuits can also include antennas and / or transceivers to communicate with various components within the network or within the device. The general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.

[0229] Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program or code from one place to another. Storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0230] In this document, as used herein the term "unit" refers to software, firmware, hardware, and any combination of these elements that is used to perform the associated functions described herein. In addition, various modules can be described as discrete units; however, as will be apparent to those of ordinary skill in the art, two or more of the units can be combined to form a single unit that performs the associated functions according to embodiments of the present solution.

[0231] Furthermore, in embodiments of the present disclosure, memory or other storage devices and communication components can be employed. It will be appreciated that, for clarity- purposes, the foregoing description has described embodiments of the present disclosure with reference to different functional units and processors. It will be apparent, however, that any suitable distribution of functionality between different functional units, processing logic elements or domains can be used without detracting from the present disclosure. For example, functionality illustrated to be performed by separate processing logic elements or controllers can be performed by the same processing logic element or controller. Hence, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

[0232] Various modifications to the implementations described in this disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other implementations without departing from the scope of this disclosure. Thus, the present disclosure is not intended to be limited to the implementations shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein and made apparent to others skilled in the art by the teachings herein with the fullest scope of equivalents encompassed thereby.

Claims

1. A wireless communication method for use in an access and mobility management function, the wireless communication method comprising: transmitting, to a policy control function, PCF, allowed network slice selection assistance information, NSSAI, associated with a wireless terminal, wherein at least one allowed single network slice selection assistance information, S-NSSAI, of the allowed NSSAI is associated with a vehicle-to-anything service; receiving, from the PCF, at least one PC5 quality of service, QoS, parameter associated with at least one allowed S-NSSAI of the NSSAI, and receiving, from the PCF, a validity area of the at least one PC5 QoS parameter.

2. The wireless communication method of claim 1, further comprising: transmitting, to a first radio access network node, the at least one PC5 QoS parameter and the at least one allowed S-NSSAI.

3. The wireless communication method according to claim 2, wherein, The at least one PC5 QoS parameter comprises an aggregate maximum bit rate per network slice.

4. The wireless communication method of claim 1, further comprising: receiving an indication of a handover of the wireless terminal to a second radio access network node, and determining, based on the validity area and a location of the wireless terminal, whether to transmit the at least one PC5 QoS parameter to the second radio access network node.

5. The wireless communication method of claim 1 or 2, further comprising: receiving, from the PCF, a vehicle-to-anything service policy comprising a mapping between at least one service and at least one S-NSSAI associated with PC5 communication, and transmitting, to the wireless terminal, the vehicle-to-anything service policy.

6. A wireless communication method for use in a policy control function, the wireless communication method comprising: receiving, from an access and mobility management function, AMF, allowed network slice selection assistance information, NSSAI, associated with a wireless terminal, wherein at least one allowed single network slice selection assistance information, S-NSSAI, of the allowed NSSAI is associated with a vehicle-to-anything service for PC5 communication; transmitting, to the AMF, at least one PC5 quality of service, QoS, parameter associated with at least one allowed S-NSSAI of the NSSAI, and transmitting, to the AMF, a validity area of the at least one PC5 QoS parameter.

7. The wireless communication method according to claim 6, wherein, The at least one PC5 QoS parameter comprises an aggregate maximum bit rate per network slice.

8. The wireless communication method of claim 6 or 7, further comprising: transmitting, to the AMF, a vehicle-to-anything service policy comprising a mapping between at least one service and at least one S-NSSAI associated with PC5 communication.

9. A wireless device comprising an access and mobility management function, the wireless device comprising: a communication unit configured to transmit, to a policy control function, PCF, allowed network slice selection assistance information, NSSAI, associated with a wireless terminal, wherein at least one allowed single network slice selection assistance information, S-NSSAI, of the allowed NSSAI is associated with a vehicle-to-everything service; receive, from the PCF, at least one PC5 quality of service, QoS, parameter associated with at least one allowed S-NSSAI of the NSSAI, and receive, from the PCF, a validity area of the at least one PC5 QoS parameter.

10. The wireless device of claim 9, further comprising a processor configured to perform the wireless communication method of any of claims 2-5.

11. A wireless device comprising a policy control function, the wireless device comprising: a communication unit configured to receive, from an access and mobility management function, AMF, allowed network slice selection assistance information, NSSAI, associated with a wireless terminal, wherein at least one allowed single network slice selection assistance information, S-NSSAI, of the allowed NSSAI is associated with a vehicle-to-everything service for PC5 communication; transmit, to the AMF, at least one PC5 quality of service, QoS, parameter associated with at least one allowed S-NSSAI of the NSSAI, and transmit, to the AMF, a validity area of the at least one PC5 QoS parameter.

12. The wireless device of claim 11, further comprising a processor configured to perform the wireless communication method of any of claims 7-8.

13. A computer program product comprising a computer readable program medium code stored thereupon, the code, when executed by a processor, causing the processor to implement the wireless communication method of any of claims 1-8.

Images