WO2020052775A1 - Dispositif et procédé pour la fourniture d'une fonction de qualité de service - Google Patents

Dispositif et procédé pour la fourniture d'une fonction de qualité de service Download PDF

Info

Publication number
WO2020052775A1
WO2020052775A1 PCT/EP2018/074862 EP2018074862W WO2020052775A1 WO 2020052775 A1 WO2020052775 A1 WO 2020052775A1 EP 2018074862 W EP2018074862 W EP 2018074862W WO 2020052775 A1 WO2020052775 A1 WO 2020052775A1
Authority
WO
WIPO (PCT)
Prior art keywords
qos
network
communication
service
function
Prior art date
Application number
PCT/EP2018/074862
Other languages
English (en)
Inventor
Emmanouil Pateromichelakis
Apostolos KOUSARIDAS
Chan Zhou
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to PCT/EP2018/074862 priority Critical patent/WO2020052775A1/fr
Publication of WO2020052775A1 publication Critical patent/WO2020052775A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0247—Traffic management, e.g. flow control or congestion control based on conditions of the access network or the infrastructure network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/46—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for vehicle-to-vehicle communication [V2V]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/36—Modification of an existing route due to handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS

Definitions

  • the present invention generally relates to the field of providing Quality of Service (QoS) in communication networks. More specifically, the present disclosure relates to a device and a method for determining a QoS of a communication service (e.g., a Vehicle-to- Everything (V2X) service) of an application entity (e.g., a vehicle, an application server).
  • QoS function may be provided for application entities in one or more communication networks being operated by one or more Mobile Network operators (MNOs) or Public Land Mobile Networks (PLMNs), for roaming and non-roaming scenarios.
  • MNOs Mobile Network operators
  • PLMNs Public Land Mobile Networks
  • Enhanced Vehicular- to-Everything (eV2X) services are described as a special type of Fifth generation (5G) services, which include both safety and non-safety services, according to the technical specification document with the reference number of “TS 22.186”.
  • KPIs Key Performance Indicators
  • UE dynamic group-User Equipment
  • network changes i.e., network congestion to core network and/or access network entities, mode of transmission or operation change.
  • the dynamicity of environment may eventually lead to fluctuation of performance (the QoS or Quality of Experience (QoE)) in short-time scale (e.g. in milliseconds).
  • QoS Quality of Experience
  • this may be tolerated by averaging performance over a time window, however, in V2X critical communications, dynamic QoS changes need to be captured, otherwise this may lead to failure of meeting the network requirements (from application point of view this may be translated to possibility of car accidents due to the heavy reliance on cellular communication system).
  • Processing complexity and signalling load, for dynamic monitoring and control of the UE (or UEs) QoS, across all segments of the communication system is expected to be high, assuming dense networks of connected cars.
  • Group-based communications with a mixture of diverse KPIs need to be set or adapted. This needs to take into account the KPI/QoS of other cars in proximity to ensure traffic efficiency or safety.
  • PLMN Fast Inter-Public Land Mobile Network
  • a predictive QoS configuration or adaptation is essential, for example, to ensure meeting the mixture of safety or non safety V2X services with the minimum control-plane latency, and real-time signalling.
  • the Radio Access Network (RAN) for each User Equipment (UE) establishes one or more Data Radio Bearers (DRBs) per Protocol Data Unit (PDU) session.
  • the RAN associates the uplink traffic (UL) and downlink traffic (DL) QoS flows with the DRBs.
  • the DRB defines the packet treatment on the radio interface (Uu).
  • a DRB serves packets with the same packet forwarding treatment. Separate DRBs may be established for the QoS flows requiring different packet forwarding treatment, as it is defined in“3GPP- 38804”.
  • the appropriate DRBs are established based on the output of the admission control, in order to make sure that the expected QoS is achieved.
  • the network via the“modify bearer context request” message provides the dynamic QoS modification in an established bearer
  • a detailed description can be found in 3GPP specification documents with the references of 3GPP-36331, and 3GPP-24301.
  • This is a hard decision that does not provide an“early” notification scheme from the network to the UE (or a group of them), for example, about the expected QoS and/or the coverage changes.
  • This function does not allow the application or the UE to be notified early enough about an expected QoS change, and negotiate with the network or adapt the application layer configuration, e.g., before the actual QoS modification.
  • the conventional schemes e.g., Long Term Evolution (LTE), the 5G
  • LTE Long Term Evolution
  • 5G 5th Generation
  • P-QoS QoS changes
  • V2X scenarios may involve interaction among multiple PLMNs (for roaming and non-roaming scenarios). If the prediction of the QoS changes is applied to inter- PLMN scenarios, the interaction between Network Function (NF) of different PFMNs may need to be extended, in order to allow for joint prediction configurations and notifications to deal with ultra-reliable and low latency V2X communications.
  • NF Network Function
  • the functionality for the prediction of the QoS changes may also affect the management plane (MP) and the MP-to-CP interfaces (e.g. SBI).
  • MP management plane
  • MP-to-CP interfaces e.g. SBI
  • the role of the MP to the P-QoS pre-operation i.e., how the management of the NEs needs to be extended to support the P-QOS NF
  • the operation or the maintenance phase needs to be determined.
  • the conventional devices and methods have the disadvantages that, they do not support the prediction of the changes in the QoS and/or the coverage (e.g., based on the mobility information of the UEs (e.g., the vehicles), the application behaviour, the map information, and the network information).
  • the conventional devices and methods do not support, for example, the subscription to the service for the prediction of the QoS Changes, the corresponding monitoring requests to enable the prediction, the QoS negotiation between the application and the network (e.g., V2X application at the vehicle side), the early notification of the involved applications for the changes of the provided QoS and/or the coverage, etc.
  • one objective of the present invention is to improve the conventional solutions for providing the QoS function for the communication services in the communication networks.
  • the present invention proposes a device for providing a QoS function for a communication service of an application entity.
  • the device may determine the QoS and/or a change in the QoS of the communication service of the application entity.
  • the QoS may be provided for one or more communication networks of one or more different Mobile Network Operators (MNOs) or PLMNs that may interact to each other.
  • MNOs Mobile Network Operators
  • PLMNs Packet Control Network Operators
  • the QoS function (also hereinafter referred to as the prediction QoS “P-QoS” function) may be based on a prediction functionality in a communication system that allows to, for example, determine the QoS, predict the QoS, determine a change in the QoS, predict (and/or detect very fast) changes in the QoS, and/or the coverage for a specific communication service of an application entity (e.g., V2X application entity)), identify potential changes of QoS (e.g., based on historic information or statistics).
  • an application entity e.g., V2X application entity
  • the QoS function may be an individual network function, it may be distributed among different network entities, it may be a part of an existing function or network entity (e.g., Point Coordinates Function (PCF), Session Management Function (SMF), Network and Data Analytic Function (NWDAF), V2X control function, Application Function (AF) of the 5G communication system, etc.,) without limiting the present disclosure to a specific function.
  • PCF Point Coordinates Function
  • SMF Session Management Function
  • NWDAF Network and Data Analytic Function
  • V2X control function e.g., V2X control function, Application Function (AF) of the 5G communication system, etc.
  • the QoS function may be or may include determining expected QoS stability or change for a Protocol Data Unit (PDU) session (e.g., determining QoS fluctuations with respect to the traffic distribution), determining the expected coverage changes, group-based QoS expectation, estimated network situation (e.g., abstracted channel conditions, network availability, congestion status, load status, etc.), determining average interference levels in certain areas, determining average single or group-based mobility, determining handover failure rate probabilities, etc.
  • PDU Protocol Data Unit
  • the QoS function may provide notifications for type of communication, e.g., sidelink (PC5) communication, cellular (Uu) communication, combination of both communications, a dual connectivity modes, etc.
  • the QoS function may be adapted on either at the RAN side and/or at the end-to-end communication path that has been formed (e.g., core and RAN side).
  • a first aspect of the present invention provides a device for providing a QoS function, for at least one communication service of at least one application entity, the device being configured to determine a first QoS for the at least one communication service of the at least one application entity, wherein the first QoS is determined based on at least one network parameter of a first communication network, and obtain at least one network parameter of a second communication network, for determining a second QoS for the communication service of the at least one application entity, wherein the second QoS is determined based on the first QoS and/or the obtained at least one network parameter of the second communication network.
  • the device may provide the QoS function, and the QoS function may include determining the first QoS and the second QoS.
  • one or more communication networks of one or more different MNOs or PLMNs may interact to configure the QoS function.
  • the first QoS may be determined based on the at least one network parameter of the first communication network.
  • the first and the second communication networks (and/or their corresponding network entities) may interact to each other.
  • the application entity may be based on a UE that roams from the first MNO to the second MNO).
  • two or more MNOs may exchange notifications and/or configurations for QoS changes, for example, when the UEs participating to the same service are attached to different MNOs.
  • the device further determines the second QoS.
  • the second QoS may be determined based on the first QoS and/or the obtained at least one network parameter of the second communication network.
  • the network parameter may be any parameter that is related to the network (i.e., the first network and/or the second network).
  • the network parameter may be a network characteristics, a network information, a parameter that is related to the different entities in the network (e.g., the characteristics and behavior of the network entities), a structural parameter of the network, a performance parameter of the network, etc.
  • the network parameter may be or may include a parameter that is related to the communication, e.g., the communication of the networks, the Sidelink PC5, the Uu, etc.
  • the network parameter may be the communication parameter that may be (directly or indirectly) related to the network, e.g., a measurement of a Sidelink/D2D communication that is established between two vehicles, etc.
  • the network parameters may be and/or may include the service requirements, the network capabilities, the situation of the network and the radio resources in one or more network domains (RAN, CN), the availability of the network and the radio resources in one or more network domains (RAN, CN), the QoS parameters, the latency, the bit rate, the monitoring parameters such as the network load, the link load, the radio link quality, the coverage information, the analytics or the historic data, etc.
  • the network capabilities, the situation of the network and the radio resources, the availability of the network and the radio resources may be based on the current and/or the actual values, their predicted values, and/or based on historic information and statistics, etc.
  • the network parameters may be the parameters and/or the information related to the network entities, e.g., the NWDAF, the PCF, the SMF, etc.
  • the QoS function may include determining the QoS, determining the changes in the QoS or the coverage level, notifying the QoS, negotiating the QoS, etc.
  • a V2X application entity may be configured to subscribe and may further request the device (and/or the communication network) to provide the QoS function (e.g., enable the prediction service, determine the QoS, determine a change in the QoS, determine the change in the coverage levels, etc.).
  • the device and/or the application entity may be in the first communication network.
  • the plurality of network entities in the first communication network e.g., the RAN, the core network
  • UEs and the application entities may be configured to report information (e.g., application layer, network layer, radio layer, etc.) to the device, and the device may determine the first QoS.
  • the first communication network may interact with the second communication network.
  • the plurality of network entities in the second communication network may be configured to report information (e.g., application layer, network layer, radio layer, etc.) to the device, and the device may determine the second QoS.
  • the device may be located in the first communication network (e.g., as an individual entity or as a part of another core network function), in the second communication network (e.g., as an individual entity or as a part of another core network function), in the application entities, in a server computer, on the cloud, etc., without limiting the present disclosure.
  • the first and the second communication networks may support different types of communication services and different types of communication links (Uu, PC5).
  • the device and/or the first communication network and/or the second communication network may notify the application entity (e.g., the V2X application entity) about, e.g., expected changes in an initially agreed QoS and/or the changes in the coverage level.
  • the notification may include a location information, timing information, and probabilistic information to describe the change in the QoS and/or the coverage provision.
  • the notification for the QoS change may be reported to the application entity and/or to at least one of the network entities (RAN, core network) in the first communication network and/or in the second communication network, to allow a re-configuration for maintenance of the QoS, or for the support of a new QoS, etc.
  • the device is further configured to obtain at least one application parameter (e.g., road conditions, user routes/paths, group formation, etc.) of one or more application entities, for pro-actively setting a third QoS for the at least one communication service of the at least one application entity, wherein the third QoS is pro-actively set based on the first QoS and/or the obtained at least one network parameter of the second communication network and/or the obtained at least one application parameter.
  • application parameter e.g., road conditions, user routes/paths, group formation, etc.
  • the device may obtain the application parameters, and it may pro-actively set (e.g., proactively determine) the third QoS for the communication service of the application entity.
  • the device is further configured to transmit a subscription request of the at least one application entity in the first communication network to a network entity in the second communication network. This is beneficial, since the application entity may request a subscription to the QoS function. Moreover, the subscription of the application entity to the QoS function may be activated.
  • the subscription request comprises a QoS service request message for determining, upon a roaming of the at least one application entity from the first communication network to the second communication network, whether the QoS function for the at least one communication service of the at least one application entity is supported in the second communication network.
  • the application entity may move from the first communication network to the second communication network.
  • it may be determined that the QoS function for the communication service of the application entity is supported in the second communication network or not.
  • an alternative QoS may be provided to the application entity.
  • the QoS service request message includes one or more of:
  • a QoS subscription parameter including one or more of a time information, a location information and a periodicity information. This is beneficial, since the subscription of the application entity to the QoS function may be activated and the QoS function may be provided.
  • the subscription parameter includes one or more of:
  • PDU protocol data unit
  • ID session identification number
  • V2X vehicle-to-everything
  • V2X-UE vehicle-to-everything user equipment
  • the type of the link including the Sidelink (PC5), and/or the Cellular communication (Uu).
  • the subscription request is transmitted based on one or more of:
  • the device and/or the application entity and/or the first communication network and/or the second communication network may transmit information to each other.
  • the device is further configured to receive a QoS service response message from the network entity in the second commination network comprising an alternative QoS function supported for the at least one communication service of the at least one application entity in the second communication network.
  • the QoS service response message is received based on one or more of:
  • the at least one communication service includes a V2X communication service.
  • the communication service may be the V2X communication service.
  • the vehicle may need to communicate with another network entity that may affect the vehicle.
  • the QoS of the V2X service may be determined, etc.
  • the at least one application entity is based on one or more of:
  • UE user equipment
  • the application entity may be a vehicle or a mobile device, etc.
  • the present disclosure is not limited to a specific type of application entity.
  • Different types of the application entities e.g., the V2X application entity, the application server, the AF, etc., may have different types of the communication services, and the QoS function for the communication services of the different types of the application entities may be provided.
  • the device is further configured to provide a vehicle-to-everything control function (V2XCF) for providing a Sidelink (PC5) parameter to the UE.
  • V2XCF vehicle-to-everything control function
  • PC5 Sidelink
  • a direct vehicle to vehicle communication may be provided.
  • the device is further configured to provide, via the vehicle-to-everything control function (V2XCF) one or more of QoS parameters from a UE in the first communication system to a UE in the second communication system.
  • V2XCF vehicle-to-everything control function
  • the application entity may be a UE such as a vehicle in the first communication network, furthermore, the vehicle may further communicate with another vehicle in the second communication network.
  • the one or more of QoS parameters includes one or more of: ⁇ A mapping of proximity services (ProSE) per packet priority (PPPP) to packet delay budget (PDB) and packet error rate (PER), for the first QoS and the second QoS.
  • ProSE proximity services
  • PPPP packet priority
  • PDB packet delay budget
  • PER packet error rate
  • a timer information (Txxxx) indicating the UE in the first communication system changing the radio parameter and/or the PPPP mapping being self-assigned by the first UE for the V2X communication service over the PC5.
  • the device is further configured to provide an alert notification representing a change of the QoS, to the at least one application entity in the first communication system and/or the network entity in the second communication system, wherein the alert notification comprises a minimum exposure of the first and/or the second network’s information with respect to a predefined criterion.
  • the device is further configured to exchange a safety-related instruction between the UE in the first communication system and the UE in the second communication system.
  • a safety-related instruction may be a notification for the change in the QoS, and it may be transmitted over the Sidelink, between the UEs that belong to different communication networks.
  • the first communication system and/or the second communication system are based on one or more of:
  • a multiple PLMN operators wherein the multiple PLMN operators are based on a roaming inter-PLMN operator or a non-roaming inter-PLMN operator.
  • a second aspect of the invention provide a method for providing a QoS function, for at least one communication service of at least one application entity, the method comprising determining a first QoS for the at least one communication service of the at least one application entity, wherein the first QoS is determined based on at least one network parameter of a first communication network, and obtaining at least one network parameter of a second communication network, for determining a second QoS for the communication service of the at least one application entity, wherein the second QoS is determined based on the first QoS and/or the obtained at least one network parameter of the second communication network.
  • the method further comprises obtaining at least one application parameter of one or more application entities, for pro-actively setting a third QoS for the at least one communication service of the at least one application entity, wherein the third QoS is pro-actively set based on the first QoS and/or the obtained at least one network parameter of the second communication network and/or the obtained at least one application parameter.
  • the method further comprises transmitting a subscription request of the at least one application entity in the first communication network to a network entity in the second communication network.
  • the subscription request comprises a QoS service request message for determining, upon a roaming of the at least one application entity from the first communication network to the second communication network, whether the QoS function for the at least one communication service of the at least one application entity is supported in the second communication network.
  • the QoS service request message includes one or more of:
  • a communication service identification number (ID).
  • At least one QoS metrics At least one QoS metrics
  • At least one or more alternative QoS levels that could be used, when it is determined that a primary QoS is not available.
  • the type of the link including the Sidelink (PC5), and/or the cellular communication (Uu).
  • a QoS subscription parameter including one or more of a time information, a location information and a periodicity information.
  • the subscription parameter includes one or more of:
  • PDU protocol data unit
  • ID session identification number
  • V2X vehicle-to-everything
  • V2X-UE vehicle-to-everything user equipment
  • a timing window and/or a frequency of the subscription request to the QoS function A time horizon for the determination of the change in the QoS of the at least one communication service.
  • a predefined geographical area for the determination of the change in the QoS of the at least one communication service is a predefined geographical area for the determination of the change in the QoS of the at least one communication service.
  • a threshold value of the change in the QoS of the at least one communication service is
  • a duration time of the communication service is a duration time of the communication service.
  • a segment-based subscription or an end to end (E2E) subscription to the QoS function A required capability and a monitoring exposure to the at least one application entity.
  • At least one or more alternative QoS levels that could be used, when it is determined that a primary QoS is not available.
  • the type of the link including the Sidelink (PC5), and/or the Cellular communication (Uu).
  • the subscription request is transmitted based on one or more of:
  • the method further comprises receiving a QoS service response message from the network entity in the second commination network comprising an alternative QoS function supported for the at least one communication service of the at least one application entity in the second communication network.
  • the QoS service response message is received based on one or more of:
  • the at least one communication service includes a vehicle-to-everything (V2X) communication service.
  • V2X vehicle-to-everything
  • the at least one application entity is based on one or more of:
  • UE user equipment
  • the method further comprises providing a vehicle-to-everything control function (V2XCF) for providing a Sidelink (PC5) parameter to the UE.
  • V2XCF vehicle-to-everything control function
  • PC5 Sidelink
  • the method further comprises providing, via the vehicle-to-everything control function (V2XCF) one or more of QoS parameters from a UE in the first communication system to a UE in the second communication system.
  • V2XCF vehicle-to-everything control function
  • the one or more of QoS parameters includes one or more of:
  • a timer information (Txxxx) indicating the UE in the first communication system changing the radio parameter and/or the PPPP mapping being self-assigned by the first UE for the V2X communication service over the PC5.
  • the method further comprises providing an alert notification representing a change of the QoS, to the at least one application entity in the first communication system and/or the network entity in the second communication system, wherein the alert notification comprises a minimum exposure of the first and/or the second network’s information with respect to a predefined criterion.
  • the method further comprises exchanging a safety-related instruction between the UE in the first communication system and the UE in the second communication system.
  • the first communication system and/or the second communication system are based on one or more of:
  • a multiple PLMN operators wherein the multiple PLMN operators are based on a roaming inter-PLMN operator or a non-roaming inter-PLMN operator.
  • FIG. 1 shows a schematic view of a device for providing a QoS function, for a communication service of an application entity, according to an embodiment of the invention.
  • FIG. 2 shows a schematic view of a system including the device for activating and providing the QoS function for a communication service of an application entity, according to an embodiment of the invention.
  • FIG. 3 shows a flow diagram of an exemplary procedure, for activation of the QoS function, configuration of the communication network, and providing the QoS function.
  • FIG. 4 shows a flow diagram of an exemplary procedure, for activation of monitoring for the QoS function.
  • FIG. 5 shows a flow diagram of an exemplary procedure, for activation of monitoring for a local prediction of the QoS function.
  • FIG 6a and 6b schematically illustrate examples of message sequence charts (MSCs) for notifying the changes in the QoS to an application function and an application server, respectively.
  • MSCs message sequence charts
  • FIG 7a and 7b schematically illustrate examples of MSC for notifying the changes in the QoS to a V2X application entity of a user equipment (UE).
  • UE user equipment
  • FIG. 8 schematically illustrates a procedure for a configuration of the QoS function by a Slice Management System.
  • FIG. 9 schematically illustrates a procedure for a configuration of the PC5 parameters for the P-QoS function.
  • FIG. 10 schematically illustrates a procedure for transmitting a QoS subscription request based on an inter NEF interaction, in a Multi-MNO environment using a roaming service.
  • FIG. 1 la and 1 lb schematically illustrate a procedure for transmitting a QoS subscription request based on an inter-PFMN control plane, in a Multi-MNO environment using a roaming service.
  • FIG. l2a, l2b, and l2c schematically illustrate exemplary MSCs for providing QoS function in a Multi-MNO environment, where the application entities are attached at different MNOs.
  • FIG. 13 schematically illustrates an embodiment of a system including the device, for performing a network-centric inter-PLMN communication, according to an embodiment of the invention.
  • FIG. 14 schematically illustrates an embodiment of a system including the device, for performing a V2XCF-centric inter-PLMN communication, according to an embodiment of the invention.
  • FIG. 15 schematically illustrates an embodiment of a system including the device, for an application-centric inter-PLMN P-QoS control, according to an embodiment of the invention.
  • FIG. 16 shows a schematic view of a method for providing a QoS function, for a communication service of an application entity, according to an embodiment of the invention.
  • FIG. 1 shows a device 100 for providing a QoS function, for a communication service 111 of an application entity 110, according to an embodiment of the invention.
  • the application entity 110 is located in the first communication network 1.
  • the first communication network 1 is operated by the first mobile network operator MNO 1.
  • the device 100 is further configured to determine the first QoS 103, for the communication service 111 of the application entity 110.
  • the first QoS 103 is determined based on the network parameters 112, 113, 114 of the first communication network 1.
  • Network parameters may include, for example, the service requirements, the network capabilities, the network and radio resources situation/availability in one or more network domain (RAN, CN), the communication parameters, e.g, the Sidelink, the Uu., the parameters and/or information of the network entities, e.g., the NWDAF, the SMF, etc.
  • the network capabilities and network or radio resources situation/availability may be current/actual values, predicted values, or based on historic information and statistics.
  • the device is further configured to obtain the network parameter 115 of the second communication network 2, for determining the second QoS 104 for the communication service 111 of the application entity 110. For example, the device 100 determines the second QoS 104 based on the first QoS 103 and/or the obtained network parameter 115 of the second communication network 2.
  • the second mobile network operator MNO 2 operates the second communication network 2.
  • An application entity 116 having a communication service 117 is located in the second communication network 2.
  • the application entities 110 and 116 may be based on the same application entity, for example, a UE, a vehicle.
  • the communication services 111 and 117 may be based on an identical service, e.g., a V2X service.
  • the device 110 may be based on a mobile device (e.g., a vehicle) and it may further move from the first communication network 1 to the second communication network 2.
  • a mobile device e.g., a vehicle
  • the application entity 110 may include, for example, a QoS function (e.g., the device 100 may be located in the application entity 110). Moreover, the application entity 110 may determine a first QoS for its communication service 111. Besides, the application entity 116 may also be configured to determine a QoS for its commination service 117. Furthermore, the application entity 110 may communicate with the application entity 116 and may, for example, exchange information, exchange QoS, etc. For instance, the application entity 110 may determine a second QoS for its communication service 111 in which its second QoS is determined based on its first QoS and the QoS of the second application entity 116.
  • a QoS function e.g., the device 100 may be located in the application entity 110.
  • the application entity 110 may determine a first QoS for its communication service 111.
  • the application entity 116 may also be configured to determine a QoS for its commination service 117.
  • the application entity 110 may communicate with the application entity 116 and
  • the device 100 and/or the application entity 110 and/or the application entity 116 may be located in one or more PLMNs, etc., without limiting the present disclosure to a specific network configuration, and may further be configured to communicate to each other.
  • the device 100 determines the first QoS for the communication service 111 of the application entity 110. For example, the device 100 transmits a monitoring request 101 to at least one network entity in the communication network 1. For instance, the monitoring request may be transmitted to different network nodes, and/or the application entities, and/or the UEs, etc., and may further be used for collection of information for determining the first QoS 103 of the communication service 111.
  • the device 100 may further obtain a monitoring response 102 from the network entities in the communication network 1, and/or the application entities, and/or the UEs, etc., and it may further determine the first QoS 103, e.g., based on the obtained monitoring response 102.
  • the device 100 may further transmit the first QoS 103 and/or the second QoS 104 to the application entity 110 and/or to the application entity 116 and/or to the network entities in the first communication network 1 and/or to the network entities the second communication network 2.
  • FIG. 2 shows a schematic view of a system 200 including a device 100 for activating and providing a QoS function for a communication service of an application entity 110, according to an embodiment of the invention.
  • the device 100 in the system 200 performs several procedures that may be needed, in order to enable the QoS function.
  • the system 200 includes the application entity 110 which sends a subscription request to the QoS function of the device 100.
  • the device 100 performs activation of prediction for all types of links and/or services, in response to the subscription request of the application entity 110.
  • the device 100 further performs activation of monitoring reports to the appropriate nodes for all types of links and/or services, in order to enable and/or to provide the QoS function.
  • the device 100 transmits the monitoring request to the Radio Access Network (RAN) 201 and several network entities including NWDAF, SMF, PCF, Access and Mobility management Function (AMF) and UPF, in the Core Network (CN) 202 of the communication network 1.
  • the device 100 obtains a monitoring response from the RAN 201, and from one or more of the network entities including NWDAF, SMF, PCF, AMF and UPF in the core network (CN) 202.
  • the device 100 further determines a change in the QoS of the communication service of the application entity 110, based on the obtained monitoring response, and transmits the determined change in the QoS to the application entity 110.
  • the device 100 notifies the application entity, by providing a notification of QoS change and/or coverage using timing, location, probabilistic information, etc.
  • the system 200 is based on a Multi-operators in which two different operators including a first mobile network operator MNOl is interacting with a second mobile network operator MN02. The interactions may be based on roaming and non-roaming cases.
  • the device 100, the network entities in the CN 202, the application entity 110, and the RAN 201 are included in the first MNOl, without limiting the present disclosure to a specific location of the different entities.
  • the device 100 (and/or the system 200) further performs the configuration of the QoS function, for example, by the Management plane.
  • FIG. 3 a flow diagram of an exemplary procedure, for activation of the QoS function, configuration of the communication network and providing a QoS function.
  • Entities shown in FIG. 3 are the UE 300, the AN 301, the AMF 302, the SMF 303, the UPF 304, the NWDAF 305, the device 100 which is configured to provide the QoS function (e.g., the P- QoS functionality), the PCF 306, the Network Exposure function (the NEF) 307, and the application entity in the form of application function 110.
  • the QoS function e.g., the P- QoS functionality
  • the PCF 306 the Network Exposure function
  • the application entity in the form of application function 110 e.g., the P- QoS functionality
  • the V2X application entity subscribes with the 5G communication network to support the predictive QoS (P-QoS) functionality.
  • the application entity sends a P-QoS subscription parameter to the 5G system.
  • the subscription parameter includes one or more of:
  • PDU protocol data unit
  • ID session identification number
  • V2X vehicle-to-everything
  • V2X-UE vehicle-to-everything user equipment
  • a timing window and/or a frequency of the subscription request to the QoS function is provided.
  • a time horizon for the determination of the change in the QoS of the communication service (e.g., a QoS guarantee that the communication network provides for the next x seconds, the QoS downgrade or the QoS upgrade will take place in x seconds, etc.).
  • a predefined geographical area for the determination of the change in the QoS of the communication service e.g., the QoS downgrade/upgrade will take place in x meters or the location with coordinates of x, y, z, etc.).
  • a threshold value of the change in the QoS of the at least one communication service is
  • a duration time of the communication service is a duration time of the communication service.
  • a specific prediction capability (e.g., QoS Change, out of coverage, 5G to LTE transition, etc.).
  • a segment-based subscription or an end to end (E2E) subscription to the QoS function (this information may be required, for example, for identifying the requirement for a local or a global prediction).
  • a required capability and a monitoring exposure to the at least one application entity (this information may be used by the communication network to determine whether the subscription request can be activated or not).
  • At least one or more alternative QoS levels that could be used, when it is determined that a primary QoS is not available.
  • the type of the link including the Sidelink (PC5) and/or the Cellular link
  • the activation of the QoS function (e.g., the P-QoS functionality activation) is described as a feature which can be activated, e.g., in response to a subscription request of an application entity being based on an application function (AF), and for a V2X service considering the 5G system.
  • AF application function
  • the procedure can be applied more generally to all types of the application entities.
  • the application entity may be based on an application server, an application function, a middleware application, etc.
  • the communication system may also be any type of the (e.g., cellular) communication systems.
  • AF 110 sends a service request message which includes:
  • the AF 110 sends a service ID, and a time, area and periodicity information to the NEF 307 and the PCF 306, respectively.
  • the PCF 306 (or any relevant network functionality which may be responsible for the policy control and charging), after receiving the AF’ s 110 request, sends a P-QoS activation request message to the device 100 (e.g., its P-QoS logical unit).
  • the P- QoS activation request message includes:
  • V2X UE IDs • One or more V2X UE IDs. • One or more of the P-QoS subscription parameters (e.g., parameters related to the time, geographic area, and the periodicity or monitoring requirement).
  • P-QoS subscription parameters e.g., parameters related to the time, geographic area, and the periodicity or monitoring requirement.
  • the device 100 (for example, its P-QoS unit) initiates the monitoring activation/subscription procedure (which will be described in detailed in the following in FIG. 4).
  • the monitoring activation/subscription procedure may include on demand the analytics activation messages to the NWDAF 305, as well as, to the RAN via the AMF 302 and the UE 300 (for example, for a real-time UE monitoring).
  • the device 100 e.g., its P-QoS admission control
  • the PCF 306 activates the subscription of the AF 110 to the QoS function, in order to ensure that the communication network can support this features and monitoring response is acknowledged (ACK).
  • ACK acknowledged
  • the P-QoS functionality of the device 100 sends a P-QoS activation response message to the application entity 110, directly, or via the NEF 307.
  • This message may include an ACK (in case of acceptance) or NACK (in case of rejection) or a negotiation of network parameters, for example, in the cases that, not all P-QoS parameters can be fulfilled by the system, etc.).
  • the AF 110 responds by an ACK/NACK, for example, in the case of negotiating the P-QoS subscription parameters.
  • the device 100 may undertake the role of overriding or extending the PCC rules by sending a message to the PCF 306 and/or to the SMF 303.
  • a pre-configured extended PCC rule message may be transmitted from the P-QoS of the device 100 to the SMF 303
  • a dynamic extended PCC rules message may be transmitted from the P-QoS of the device 100 to the PCF 306.
  • both messages may include the P-QoS activation parameters.
  • the P-QoS function of the device 100 may be operated, for example, in a service or a session based manner.
  • the communication network may notify the application entity 110 when the prediction service is not supported any more (e.g., change of the Radio Access Technology (RAT) or the cell), or in the cases when any change in the configuration of the prediction service (i.e. the QoS function) is needed. Therefore, the prediction service may be, e.g., released, modified, and updated either by the application entity and/or by the device and/or by the communication network, etc.
  • the prediction service may be, e.g., released, modified, and updated either by the application entity and/or by the device and/or by the communication network, etc.
  • the subscription request for the activating the prediction service may be sent by an application entity of a UE (or a group of UEs) to the network using control plane signaling (Radio Resource Control (RRC), Non-access stratum (NAS)), or to an application function (e.g., AF of 5GS) using user plane signaling.
  • RRC Radio Resource Control
  • NAS Non-access stratum
  • AF AF of 5GS
  • FIG. 4 shows a flow diagram of an exemplary procedure, for activation of monitoring for the QoS function.
  • the device 100 transmits a monitoring request to a network entity, for example, to AN 301 in the communication network, and/or the application entity 110, and/or the UE 300.
  • a network entity for example, to AN 301 in the communication network, and/or the application entity 110, and/or the UE 300.
  • the P-QoS subscription request e.g., the P-QoS subscription parameters, the type of the V2X service
  • different monitoring subscription or configuration requests may be required, transmitted and collected, e.g., by different network nodes (e.g., gNB, UPF), depending on the type of the V2X service and the agreed P-QoS requirements.
  • These requests may allow collection of different types of information that may be needed, in order to, e.g., activate the subscription request, determine the QoS, determine the change in the QoS and/or enable the prediction of the QoS change, etc.
  • the different types of information may be one or more of:
  • BS General information per node
  • N3 in 5G Network-to-Network Interface
  • NWDAF Network-to-Network Interface
  • BS General information per node
  • N3 in 5G Network-to-Network Interface
  • Specific information per QoS flow that can be retrieved via the corresponding node (RAN, CN, UE)), e.g., packet delay information.
  • Analytics or historic data, e.g., statistics on handover failure rate, rejected PDU sessions, etc.
  • Specific information per UE e.g., RRC measurement reports, radio link quality, UE speed, UE mobility information
  • RRC measurement reports e.g., radio link quality, UE speed, UE mobility information
  • Application layer information provided either by the application entity or a third party (e.g., vehicle planned route/path/trajectory, application behavior and/or configuration, road traffic information, road infrastructure information).
  • a third party e.g., vehicle planned route/path/trajectory, application behavior and/or configuration, road traffic information, road infrastructure information.
  • Events that can be reported by the corresponding node that monitors and detects the events e.g., UE reachability, communication failure.
  • the procedure to identify the key QoS parameters and the prediction events may be affected by, for example, the type of service, the type of the communication link that is used (e.g., cellular (Uu), sidelink (PC5)) and the configuration of the P-QoS subscription request.
  • the type of service e.g., cellular (Uu), sidelink (PC5)
  • the configuration of the P-QoS subscription request e.g., the configuration of the P-QoS subscription request.
  • the device may transmit (e.g., directly or via another CN function) the appropriate monitoring subscription request messages to the appropriate nodes (e.g., UE, RAN node, CN node, V2X application entity).
  • the appropriate nodes e.g., UE, RAN node, CN node, V2X application entity.
  • the transmitted monitoring request may include one or more of:
  • the monitoring parameters a parameter (e.g., latency, data rate, packet error rate, bit rate, reliability, jitter, Signal-to-Interference-Plus-Noise Ratio (SINR), coverage) and/or a measure type (e.g., average, actual value, etc.).
  • a parameter e.g., latency, data rate, packet error rate, bit rate, reliability, jitter, Signal-to-Interference-Plus-Noise Ratio (SINR), coverage
  • SINR Signal-to-Interference-Plus-Noise Ratio
  • the monitoring level the QoS flow, the link, the UE, and the network node.
  • the time granularity of the reporting a one-time report, a periodic (value) report, a condition based report (e.g., having a value above/below a threshold value).
  • the area of reporting includes specific cells, and the geographic location.
  • the node that has received the monitoring request for the prediction service responds by an ACK or NACK.
  • the node may indicate an alternative monitoring configuration, if it is available.
  • a monitoring start message may be sent by the P-QoS function of the device 100 (e.g., directly or via another CN function).
  • the monitoring may be stopped or paused (e.g., with a monitoring reject message), and the monitoring configuration may be modified during the lifetime of the V2X service.
  • the device 100 and/or its P-QoS function may transmit an on-demand analytic activation request message.
  • the P-QoS function 100 may transmit the on- demand analytic activation request message to the NWDAF 305.
  • the NWDAF 305 may provide an analytic activation respond (e.g., ACK or NACK), to the P-QoS function of the device 100.
  • an analytic activation respond e.g., ACK or NACK
  • the device 100 and/or its P-QoS function may transmit a mobility stats subscription, for example, to the AMF 302, and the AMF 302 may further transmit a mobility stats response to the device 100.
  • FIG. 5 shows a flow diagram of an exemplary procedure, for activation of monitoring for a local prediction of the QoS function.
  • the P-QoS function (or any other CN function) may be based on a “local” predictions of, e.g., the changes in the QoS, the events that may be requested by and/or allocated to the individual network entities (e.g., Base Station (BS), UPF) or the UE.
  • BS Base Station
  • UPF User Plane Function
  • the assignment of the prediction of the changes in the QoS for a PC5/sidelink communication may be faster to take place at the RAN side.
  • the node that has received the prediction subscription request message may respond by ACK or NACK.
  • the node may indicate an alternative prediction configuration, if possible.
  • the device 100 and/or its P-QoS function transmits a local prediction message to the application entity AF 110 and/or to a network entity.
  • the AN 301 transmit a prediction notification message (e.g., expected degradation of radio quality, increase of path loss of Uu and/or PC5 radio link) to the P- QoS function of the device 100.
  • a prediction notification message e.g., expected degradation of radio quality, increase of path loss of Uu and/or PC5 radio link
  • the prediction subscription request message may include the type of the parameter that should be predicted by the recipient node (or a local P-QoS functionality), the type of reporting (e.g., per flow, node, session, etc.), the time granularity of the prediction and the reporting, the location of the prediction and the reporting, etc.
  • the actual “local” prediction results may be initiated, for example, a prediction start message is transmitted by the P-QoS function (directly or via another CN function).
  • The“local” prediction may further be stopped or paused, while the“local” prediction configuration being modified during the lifetime of a V2X Service.
  • the local” prediction results (i.e., the prediction notification message) may be sent to one or more of:
  • the determined change in the QoS may be transmitted to the application entity and/or one of the network entities.
  • the device 100 may provide a notification to the application entity 110 and/or one of the network entities, based on a type of the communication service, including at least one of a sidelink (PC5), communication, and a cellular communication (Uu).
  • a type of the communication service including at least one of a sidelink (PC5), communication, and a cellular communication (Uu).
  • the outcome of the QoS function e.g., the P-QoS functionality
  • the V2X application entity e.g., the UE, the application server, etc.
  • the type and the description of the notification may depend on the initial P-QoS subscription.
  • the notification may be:
  • the UE1 will be out of coverage in X seconds.
  • the UE1 will be out of coverage in the location with the coordinates of (x, y, z).
  • the QoS e.g., the latency
  • the UE1 will be downgraded in X seconds.
  • the QoS (e.g., the latency) of the UE1 will be downgraded in the location with the coordinates of (x, y, z), and in X seconds,
  • the QoS of a group communication (group-cast) will be downgraded at cell number x, and
  • the QoS (e.g., the latency) of the UE1 will be downgraded in the location with the coordinates of (x, y, z), and with a probability ofX% (or the confidence interval). Potential change in QoS (e.g., bit rate) with certain probability and/or confidence interval.
  • the QoS function (e.g., the prediction functionality) may provide the notification of the changes in the QoS, based on the P-QoS outcome, and it may further include one or more of:
  • the PDU session ID (per PDU session P-QoS), PDU session type, Flow ID.
  • V2X vehicle-to-everything
  • the type of the link including the sidelink (PC5), and/or the cellular communication (Uu).
  • a QoS parameter e.g., packet delay budget, bit rate
  • 5QI ID that will change and/or event that will be triggered (e.g., out of coverage).
  • a level of the QoS per user equipment e.g., ⁇ current QoS, newl QoS, new2 QoS, etc>.
  • a timing information of the UE e.g., ⁇ startl, endl, start2, end2>.
  • FIGs. 6a, 6b, 7a and 7b illustrate different forms of implementations of providing the notification from the device 100 and/or its P-QoS function 100 to the V2X application entity using either a control plane and/or a user plane messages.
  • the notification may be, for example, the service ID, the V2X-UE ID, the QoS parameter (e.g., an old value of the QoS, a new value for the QoS, an event, a timing information that the changes in the QoS being applied, the geographical area that the changes in QoS being applied, probability of the QoS change, etc.)
  • the QoS parameter e.g., an old value of the QoS, a new value for the QoS, an event, a timing information that the changes in the QoS being applied, the geographical area that the changes in QoS being applied, probability of the QoS change, etc.
  • the notification response may be, for example, ACK, NACK, negotiation of the parameters, etc.
  • FIG. 6a and FIG. 6b schematically illustrate two examples of signaling options via the NEF 601 in the 5G networks.
  • the notified destination node is the V2X application entity located at the AF 110, which can be a PFMN-owned application or a third party application.
  • FIG. 7a and FIG. 7b schematically illustrate two examples of signaling options where the notified destination node is the V2X application entity located at the UE 300.
  • the notification may be sent either via the AF 110 or via the RAN interfaces (e.g., NAS, RRC).
  • the SMF 303 is able to notify the PCF 306, if the QoS targets for a QoS flow cannot be fulfilled (in accordance to the“3GPP-23503”), and may further update it with an early notification information, etc.
  • the P-QoS functionality may notify the SMF 303 entity, and the latter may forward the notification for any change of the QoS or the coverage levels to the PCF 306. Then, the PCF 306 undertakes to transmit the notification message to the NEF 601, the AMF 302, and/or any other function or network entity.
  • the receiving V2X application entity may respond with a notification response message, for example, it may acknowledge the notification and/or accept or reject the new proposed QoS level (i.e. if the new proposed QoS level provided). In the case of the rejection, a negotiation of the QoS values between the network side and the V2X application entity may be initiated, and the later may propose a preferable alternative QoS level.
  • the outcomes of the P-QoS notification about the expected QoS and/or the coverage change may be transmitted to the network entities (e.g., BS, UPF, AMF, SMF, PCF, V2X-CF of the 5G system, etc.).
  • the appropriate re-configuration action may be triggered and decided by the network, for example, based on the type of the notification, and in order to maintain the initial agreed QoS level and/or optimize the network performance, etc.
  • FIG. 8 schematically illustrates a procedure for the configuration of the P-QoS function by the management plane, and particularly for the scenario of a slice-based architecture (i.e., V2X slice).
  • the P-QoS function may be a feature which is required, for example, on demand, or it may be activated by default for a particular service.
  • the network slicing is a key 5G requirement for enabling the verticals to operate on an end-to-end logical sub-network, e.g., after an agreement with the network operator.
  • the automotive sector is a key vertical for the 5G system, and the 5G-V2X is envisioned as a key slicing scenario.
  • the operator may provide the required network features, in order to meet the customized service requirements of the third party or the customer (e.g. OEM).
  • the network features may be required, for meeting the slice KPIs, and the associated functions and resources.
  • the P-QoS function may be one particular feature, which may be provided by default or on demand for a V2X slice.
  • the third party 801 (or customer) transmits some service requirements to the CSMF 802 which is the entity that translates the service requirements to the network requirements, from the management perspective.
  • the Network Slice Management Function (NSMF) 800 creates and/or modifies the network slice instances, and it further maps them to policies (e.g. radio resource management (RRM) policy, Network Function (NF) placement, scale in/out, slice coverage, etc.).
  • RRM radio resource management
  • NF Network Function
  • the Communication Service Management Function (CSMF) 802, the NSMF 800, and the Network Slice Subnet Management Function (NSSMF) 803 are the slice management functionalities which comprise the slice management system as it is defined in technical specification document with the reference number of“3GPP-28530”.
  • the Network Slice Instance (NSI) is created based on the application requirement, having the P-QoS feature.
  • the NSMF 800 initially activates, e.g., on demand, the required analytics from the NWDAF 305 (as an activation msgO).
  • the NWDAF 305 collects the analytics from the related network functions (core and/or RAN control functions that are relevant to monitor the QoS, the resource situation, and the events).
  • the NSMF 800 receives the on demand analytics, and it configures the different segments of the 5GS (e.g., the RAN, the TN, the CN), accordingly.
  • the 5GS e.g., the RAN, the TN, the CN
  • the NSMF 800 sends the per-segment configuration to the NSSMF 803 for enabling the P-QoS, which includes parameters for the P-QoS activation and management.
  • the NSSMF 803 sends this information to the managed Network Element (NE) 804, e.g., the control panel (CP) function.
  • the NE 804 can be the PCF which is responsible (e.g., from the control-plane perspective) for providing policies for different domains (e.g., the CN, the RAN).
  • step 8g the NE 804 or the PCF applies the configuration or the policies to the underlying 5GS.
  • FIG. 9 schematically illustrates a procedure for a configuration of the PC5 parameters for the P-QoS function.
  • a V2X Control Function (V2XCF) 900 is provided.
  • the V2XCF 900 is a network function for provision of the Sidelink (PC5) parameters to the UE 300.
  • the QoS function (e.g., the QoS model) for the PC5 includes the proximity services (ProSE) per packet priorities (PPPP), and the reliability (PPPR) provisioning to the UE 300 for the sidelink operation.
  • ProSE proximity services
  • PPPP packet priorities
  • PPPR reliability
  • the P-QoS function provisions the P-QoS parameters which includes the predicted or expected changes (QoS characteristics/PPPPs/5QIs and the mapping to the QoS attributes) for the PC5 session.
  • a message is transmitted from the device 100 (e.g., its P-QoS function) to the V2XCF 900, and/or the application server 901 and/or the UE 300 (via the V2XCF 900).
  • the message is representative of an enhanced provisioning policies for the P-QoS message, and it includes the PC5 provisioning parameters as it is defined in technical specification documents with the reference numbers of“3GPP-24386” and“3GPP-23786”.
  • the transmitted message includes one or more of:
  • FIG. 10 schematically illustrates a procedure for providing a P-QoS function in a Multi- MNO environment.
  • a UE e.g., a vehicle
  • the P-QoS functionality e.g., the P-QoS functionality
  • a V2X service may enable the P-QoS functionality.
  • its subscription to the QoS function (e.g., the P-QoS functionality) of a V2X service may be activated and/or it may be connected to an MNO with a QoS function.
  • the UE may further move to a second MNO (e.g., a national MNO, a cross-border MNO).
  • a second MNO e.g., a national MNO, a cross-border MNO
  • the second MNO i.e., the target MNO
  • an extension of the subscription may be requested.
  • the interaction between the MNOs may take place, for example:
  • FIG. 10 schematically illustrates a procedure for transmitting a P-QoS subscription request based on an inter NEF interaction, in a Multi-MNO environment, using a roaming service.
  • a subscription request of the application entity in the first communication network may be transmitted to a network entity in the second communication network.
  • the subscription request may include the QoS service request message for determining, upon a roaming of the application entity from the first communication network to the second communication network, whether the QoS function for the communication service of the application entity is supported in the second communication network.
  • the PFMN/MNOl asks via a P-QoS service request message whether the P- QoS subscription parameters for a V2X Service of one or more UEs could be supported, when the UE moves to the second PFMN/MN02.
  • the PFMN 1 includes the PCF Point coordinates function (1000) (or P-QoS 1), and the Network Exposure function (NEF) 1001 (NEF PLMN1).
  • the PLMN 2 includes the PCF 1002 (or P-QoS 2), and the NEF 1003 (NEF PLMN2).
  • the PLMN/MN02 responds with the ACK or the NACK.
  • NACK i.e., P- QoS service response message
  • the interaction between the MNOs may take place via the NEF or the AFs.
  • FIG. l la and FIG l lb schematically illustrate a procedure for transmitting a P-QoS subscription request based on an inter-PFMN control plane, in a Multi-MNO environment, using a roaming service.
  • the interactions between the MNOs for the request of the P-QoS capabilities and/or the configuration that could be supported, i.e., by the second MNO are performed via the inter PFMN interfaces.
  • the N24 and the N32 reference points of the 5G system architecture may be used for, e.g., the P-QoS service request, the response messages, and the subscription of the P-QoS capabilities to another MNO/PFMN.
  • the N27 (between NRFs) may be used for inter-PFMN P-QoS service discovery function (e.g., the query, the response). For example, in the cases that the PFMN/MNOl needs to check if the PFMN/MN02 provides any P-QoS service.
  • the QoS function (e.g., the prediction of the QoS) may be provided, for example, when two or more UEs are attached at different MNOs and they communicate via the cellular (Uu) and/or the Sidelink (PC5) interfaces (i.e. an identical or with different frequency bands).
  • the cellular (Uu) and/or the Sidelink (PC5) interfaces i.e. an identical or with different frequency bands.
  • the vehicle-to-network-to-vehicle (V2N2V) communication may be performed between two or more vehicles attached at different MNOs, e.g., sensor sharing, cooperative maneuver, etc.
  • the prediction of the changes in the QoS may require an exchange of the prediction results (e.g., by a notification of QoS changes) for a session of the V2X service that involves vehicles which are attached at different MNOs.
  • the PLMN1 may detect an expected change of the QoS, based on its individual P-QoS calculations.
  • the PLMN1 may notify, for example, the vehicles that are attached at its own network, the other involved vehicles that are attached at the PLMN2, etc.
  • the messages representing notification of the changes in the QoS may include a proposed supported QoS level.
  • a detailed description of the notification of the QoS changes is described above (e.g., in FIG. 6a, FIG. 6b, FIG. 7a, and FIG. 7b).
  • the other vehicles may accept or reject, and/or negotiate the new QoS that could be supported, e.g., by the triggering the corresponding MNO.
  • FIG. l2a, FIG. l2b, and FIG. l2c schematically illustrate mobile switching center for providing QoS function in a Multi-MNO environment, where the application entities are attached at different MNOs.
  • FIG. l2a, FIG. l2b, and FIG. l2c three alternative implementation forms of the MSC are illustrated for the interaction between different MNOs, and consequently, the transmission of the notification messages to the V2X application entities (e.g., in UEs) that are attached to different MNOs.
  • V2X application entities e.g., in UEs
  • FIG. l2a illustrates an interaction between different MNOs, based on the NEF interfaces or AFs.
  • the communication between the MNOs is performed based on the the NEF interfaces.
  • FIG. l2b illustrates an interaction between different MNOs, based on the control plane interfaces, which may be the N24 and the N32 (i.e. reference points of the 5G system architecture“3GPP-23501”, as it is described in FIG. l la).
  • the control plane interfaces may be used for the notification and the notification response messages to the other MNO/PLMN.
  • the second MNO may undertake to forward the notifications to the appropriate V2X application entities (e.g., of the UEs) that are attached to the first MNO.
  • the PLMN 1 including the P-QoSl 1204, and the PCF 1205 communities with the PLMN 2 which includes the P-QoS2 1206 and the PCF 1207.
  • the communication between the MNOs is performed based on the the control plane interfaces.
  • FIG. l2c illustrates an interaction between different MNOs, based on the sidelink interface (PC5).
  • the vehicles exchange notification messages that have received from their MNOs (i.e. MNO that they are attached to it). Similarly, the corresponding notification responses is transmitted via the sidelink interface using either sidelink control plane (e.g., Sidelink RRC) and/or the user plane messages.
  • sidelink control plane e.g., Sidelink RRC
  • FIG. l2a, FIG. l2b, and FIG. l2c may be used either for the cellular Uu (V2N2V) or the sidelink/PC5 communication between two or more UEs.
  • FIG. 13 schematically illustrates an embodiment of a system 1300 including the device 100, for performing a network-centric inter-PLMN communication, according to an embodiment of the invention.
  • the system 1300 performs a QoS information exchange, based on a network-centric secure inter-PLMN communication by using the Security Edge Protection Proxy (SEPP).
  • SEPP Security Edge Protection Proxy
  • the system 1300 includes two public land mobile networks of PLMN A and PLMN B, having the hSEPP 130 la and the vSEPP 130 lb, respectively.
  • the SEPP (i.e. the hSEPP 130 la and the vSEPP 130 lb) is used to protect control plane traffic that is exchanged between different 5G PLMNs (e.g. the PLMN A and the PLMN B in FIG. 13). For example, the SEPP performs message filtering, policing and topology hiding for all API messages.
  • the 5G system architecture introduces the SEPP as the entity located at the perimeter of the PLMN network which is adapted to: • receive all service layer messages from the network function and protect them before sending them out of the network on the N32 interface, and
  • the SEPP (i.e. the hSEPP l30la and the vSEPP l30lb) implements application layer security for all the service layer information exchanged between two NFs across two different PLMNs (e.g. the PLMN A and the PLMN B in FIG. 13).
  • the N32 1302 provides the security of message exchange between the PLMN A and the PLMN B, by hiding the topology, etc.
  • one or more vehicles belonging to the same PLMN are roaming from PLMN A to PLMN B, for example, the UE A 1303 and the UA B 1304.
  • the UEs including the UE A 1303 and the UA B 1304 initially subscribe to the PLMN B (i.e., to its QoS function). For example, the QoS related parameters may be exchanged, in order to allow the PLMN B to activate the subscription of the UE(s), and further notify them and adapt its network parameters, accordingly.
  • the data packets (e.g., the safety-related messages) may be exchanged between vehicles of different operators, for example, the UE A 1303 and the UE C 1305.
  • alert notifications including the (predictive) changes in the QoS may be sent between the operators, with the minimum exposure of network information.
  • FIG. 14 schematically illustrates an embodiment of a system 1400 including the device 100, for performing a V2XCF-centric inter-PLMN communication, according to an embodiment of the invention.
  • the QoS function may also be applied to the PC5 communication.
  • the parameters for the QoS may be provisioned via the V3 to the UE.
  • the V2XCF 140 la provides the QoS parameters via the V3 l402a to the UE A 1303, and the UE B 1304.
  • the V2XCF l40lb provides the QoS parameters via the V3 l402b to the UE C 1305.
  • the system 1400 includes the V6 1403 which is adapted for communication between the V2XCF 140 la and the V2XCF 140 lb.
  • the V2XCF 140 la may transmit the QoS parameters to the V2XCF 140 lb.
  • the V2XCF 140 lb may transmit the QoS parameters to the V2XCF 140 la. This includes radio parameters for the expected QoS for a session, the mapping of the PPPP to the PDB, the reliability, and a timer for the validity of the QoS function in the PC5 communication.
  • the transmitted QoS parameters include one or more of:
  • V6 1403 may also be used for exchanging the QoS parameters between the operators, for either roaming and/or the non-roaming inter-PLM scenarios
  • FIG. 15 schematically illustrates an embodiment of a system 1500 including the device 100, for an application-centric inter-PLMN P-QoS control, according to an embodiment of the invention.
  • the entities and interfaces within the trust domain may all be within one operator's control, or some may be controlled by a trusted business partner which has a trust relationship with the operator e.g. another operator or a 3rd party”.
  • two options 1501 and 1502 may be used, for inter- PLMN P-QoS control based on the application.
  • the AF 1503 is adapted for providing the P-QoS information among the different operators.
  • the option 1501 is representative of when the two MNOs are operating under the trust domain. Moreover, explicit P-QoS parameters and network related parameters may be exchanged.
  • the option 1502 is representative of when the two MNOs are operating such that they are not in the trust domain. Moreover, the P-QoS parameters may be abstracted (e.g., as alerts), in order to ensure minimum exposure of the network parameters to the un-trusted domain.
  • FIG. 16 shows a method 1600 according to an embodiment of the invention for providing a QoS function, for a communication service of an application entity.
  • the method 1600 may be carried out by the device 100, as it described above.
  • the method 1600 comprises a step 1601 of determining a first QoS for the at least one communication service of the at least one application entity, wherein the first QoS is determined based on at least one network parameter of a first communication network.
  • the method 1600 further comprises a step 1602 of obtaining at least one network parameter of a second communication network, for determining a second QoS for the communication service of the at least one application entity, wherein the second QoS is determined based on the first QoS and/or the obtained at least one network parameter of the second communication network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne la fourniture d'une fonction de qualité de service (QoS) pour les services de communication des réseaux de communication. L'invention concerne en particulier un dispositif apte à pour fournir une fonction de QoS pour au moins un service de communication d'au moins une entité d'application. Le dispositif est configuré pour déterminer une première QoS pour le ou les services de communication de la ou des entités d'application, la première QoS étant déterminée sur la base d'au moins un paramètre réseau d'un premier réseau de communication. Le dispositif est configuré en outre pour obtenir au moins un paramètre réseau d'un second réseau de communication, et déterminer une seconde QoS pour le service de communication de la ou des entités d'application, la seconde QoS étant déterminée sur la base de la première QoS et/ou du ou des paramètres réseau obtenus du second réseau de communication.
PCT/EP2018/074862 2018-09-14 2018-09-14 Dispositif et procédé pour la fourniture d'une fonction de qualité de service WO2020052775A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2018/074862 WO2020052775A1 (fr) 2018-09-14 2018-09-14 Dispositif et procédé pour la fourniture d'une fonction de qualité de service

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2018/074862 WO2020052775A1 (fr) 2018-09-14 2018-09-14 Dispositif et procédé pour la fourniture d'une fonction de qualité de service

Publications (1)

Publication Number Publication Date
WO2020052775A1 true WO2020052775A1 (fr) 2020-03-19

Family

ID=63579364

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2018/074862 WO2020052775A1 (fr) 2018-09-14 2018-09-14 Dispositif et procédé pour la fourniture d'une fonction de qualité de service

Country Status (1)

Country Link
WO (1) WO2020052775A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113038553A (zh) * 2021-02-25 2021-06-25 腾讯科技（深圳）有限公司 基于切换过程的消息发送方法、装置、设备及介质
WO2021253369A1 (fr) * 2020-06-19 2021-12-23 Qualcomm Incorporated Procédés de gestion de communication réseau
CN113938921A (zh) * 2021-09-10 2022-01-14 中国联合网络通信集团有限公司 一种体验质量QoE测量方法及装置
DE102020208996A1 (de) 2020-07-17 2022-01-20 Denso Corporation Verfahren und Apparat für ein Managen einer Konnektivität eines Fahrzeugs

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010001373A1 (fr) * 2008-06-30 2010-01-07 France Telecom Système et procédé de transfert

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010001373A1 (fr) * 2008-06-30 2010-01-07 France Telecom Système et procédé de transfert

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on application layer support for V2X services; (Release 16)", 9 September 2018 (2018-09-09), XP051561429, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/SA/Docs/SP%2D180682%2Ezip> [retrieved on 20180909] *
"5G; System Architecture for the 5G System (3GPP TS 23.501 version 15.2.0 Release 15)", vol. 3GPP SA, no. V15.2.0, 28 June 2018 (2018-06-28), pages 1 - 219, XP014329570, Retrieved from the Internet <URL:http://www.etsi.org/deliver/etsi_ts/123500_123599/123501/15.02.00_60/ts_123501v150200p.pdf> [retrieved on 20180628] *
HUAWEI ET AL: "QoS list to support V2X critical applications", vol. SA WG1, no. West Palm Beach, Florida, USA; 20180820 - 20180824, 29 August 2018 (2018-08-29), XP051535047, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fsa/WG1%5FServ/TSGS1%5F83%5FWPalmBeach/Docs/S1%2D182627%2Ezip> [retrieved on 20180829] *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021253369A1 (fr) * 2020-06-19 2021-12-23 Qualcomm Incorporated Procédés de gestion de communication réseau
DE102020208996A1 (de) 2020-07-17 2022-01-20 Denso Corporation Verfahren und Apparat für ein Managen einer Konnektivität eines Fahrzeugs
CN113038553A (zh) * 2021-02-25 2021-06-25 腾讯科技（深圳）有限公司 基于切换过程的消息发送方法、装置、设备及介质
CN113038553B (zh) * 2021-02-25 2023-10-27 腾讯科技（深圳）有限公司 基于切换过程的消息发送方法、装置、设备及介质
CN113938921A (zh) * 2021-09-10 2022-01-14 中国联合网络通信集团有限公司 一种体验质量QoE测量方法及装置
CN113938921B (zh) * 2021-09-10 2023-12-01 中国联合网络通信集团有限公司 一种体验质量QoE测量方法及装置

Similar Documents

Publication Publication Date Title
US11943663B2 (en) Device and method for providing a quality of service function
US12089137B2 (en) Quality of service information notification to user equipment, users, and application server
US20210219110A1 (en) Device for transmitting and/or receiving a message in a combined assisted and ad-hoc mode
WO2020052775A1 (fr) Dispositif et procédé pour la fourniture d&#39;une fonction de qualité de service
US11729711B2 (en) Techniques for radio access network (RAN) configuration in slice-based networks
EP3741141B1 (fr) Entité, réseau et équipement utilisateur pour un service v2x ainsi que l&#39;application v2x
JP7475426B2 (ja) 予想されるイベントの通知
CN115735371A (zh) 网络切片特定认证和授权
US10122634B1 (en) Proactive response to predicted bearer loss
EP4456630A1 (fr) Prédiction de liaison latérale
US20240365274A1 (en) Sidelink prediction
CN117204012A (zh) 用于在无线通信系统中控制e2节点的设备和方法
WO2020182266A1 (fr) Nœud d&#39;accès au réseau et nœud de réseau pour rapporter un trafic prévisionnel

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18769365

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18769365

Country of ref document: EP

Kind code of ref document: A1