JP2023098989A - Monitoring and reporting service performance - Google Patents

Abstract

To provide monitoring and reporting service performance.SOLUTION: A user plane function receives from a session management function, a first message requesting at least one quality of service (QoS) report for a data flow of a wireless device. The first message including a first information element indicating a QoS event and a second information element indicates a latency value for the QoS event. The user plane function sends to the wireless device, monitoring packets for monitoring a packet transmission latency of the data flow. The user plane function determines an occurrence of the QoS event based on the packet transmission latency of the data flow and the latency value. The user plane function sends to the session management function, a second message including a third information element indicating the occurrence of the QoS event for the data flow.SELECTED DRAWING: Figure 10

Description

CROSS-REFERENCE TO RELATED APPLICATIONS This application is a benefit of U.S. Provisional Patent Application No. 62/616,389, filed January 11, 2018, and U.S. Provisional Patent Application No. 62, filed January 15, 2018. 617,498, which are hereby incorporated by reference in their entireties.

Exemplary embodiments of the present invention enable enhanced features and functionality to be implemented in 5G systems. More specifically, embodiments of the technology disclosed herein may relate to service performance and/or QoS monitoring and reporting, and embodiments of the technology disclosed herein may relate to service performance and/or QoS monitoring and reporting. It may be for roaming scenarios for performance and/or QoS monitoring and reporting. Throughout this disclosure, UE, wireless device, and mobile device are used interchangeably. Throughout this disclosure, Base Stations, (Radio) Access Networks ((R)AN), Next Generation Radio Access Networks (NG-RAN), New Radio NodeBs (gNB), Next Generation eNodeBs (ng-eNB) are interchangeable used for

Some examples of various embodiments of the disclosure are described herein with reference to the drawings.

1 is a diagram of an exemplary 5G system architecture, according to an aspect of an embodiment of the present disclosure; FIG. FIG. 2 is a diagram of an exemplary 5G system architecture, according to an aspect of an embodiment of the present disclosure; FIG. 3 is a system diagram of exemplary wireless devices and network nodes in a 5G system, according to an aspect of an embodiment of the present disclosure; FIG. 4 is a system diagram of an exemplary wireless device, according to an aspect of an embodiment of the present disclosure; 5A and 5B depict two registration management state models for UE 100 and AMF 155, according to an aspect of an embodiment of the present disclosure. 6A and 6B depict two connection management state models for UE 100 and AMF 155, according to an aspect of an embodiment of the present disclosure. FIG. 7 is a diagram of classification and marking traffic, according to an aspect of an embodiment of the present disclosure. FIG. 8 is an example call flow for a UE registration procedure, according to an aspect of an embodiment of the present disclosure; Ditto. FIG. 10 is an exemplary call flow diagram, according to an aspect of an embodiment of the present disclosure. FIG. 11 is an exemplary call flow diagram, according to an aspect of an embodiment of the present disclosure; FIG. 12 is an exemplary call flow diagram, according to an aspect of an embodiment of the present disclosure; FIG. 13 is an exemplary call flow diagram, according to an aspect of an embodiment of the present disclosure; FIG. 14 is an exemplary table depicting performance requirements for low latency and high reliability services, according to an aspect of an embodiment of the present disclosure; FIG. 15 is an exemplary call flow diagram, according to an aspect of an embodiment of the present disclosure; FIG. 16 is a diagram illustrating an exemplary protocol stack for the Rx reference point, in accordance with an aspect of an embodiment of the present invention; FIG. 17 is an exemplary call flow diagram, according to an aspect of an embodiment of the present disclosure; FIG. 18 is an exemplary call flow diagram, according to an aspect of an embodiment of the present disclosure; FIG. 19 is an exemplary flow diagram, according to an aspect of an embodiment of the present disclosure; FIG. 20 is an exemplary flow diagram, according to an aspect of an embodiment of the present disclosure; FIG. 21 is an exemplary flow diagram, according to an aspect of an embodiment of the present disclosure; FIG. 22 is an exemplary flow diagram, according to an aspect of an embodiment of the present disclosure; FIG. 23 is an exemplary flow diagram, according to an aspect of an embodiment of the present disclosure;

The following abbreviations are used throughout this disclosure.
5G: 5th generation mobile networks
5GC: 5G Core Network
5GS: 5G System
5G-AN: 5G Access Network
5QI: 5G QoS Indicator (5G QoS Indicator)
AF: Application Function
AMBR: Aggregate Maximum Bit Rate
AMF: Access and Mobility Management Function
AN: Access Network
APN: Access Point Name
ARP: Allocation and Retention Priority
CCNF: Common Control Network Functions
CN: Core Network
CP: Control Plane
DPI: Deep Packet Inspection
DL: Downlink
DN: Data Network
DN-AAA: Data Network Authentication Authorization and Accounting
DNN: Data Network Name
gNB: NR NodeB
GW: Gateway
HSS: Home Subscriber Server
IETF: Internet Engineering Task Force
IP: Internet Protocol
IP-CAN: IP Connectivity Access Network
L2: Layer 2 (data link layer)
L3: Layer 3 (network layer)
LADN: Local Area Data Network
MICO: Mobile Initiated Connection Only
N3IWF: Non-3GPP (registered trademark, same below) InterWorking Function (non-3GPP interworking function)
NAI: Network Access Identifier
NAS: Non Access Stratum
NEF: Network Exposure Function
NF: Network Function
NR: New Radio
NG-RAN: NR Radio Access Network
NRF: Network Repository Function
NSI: Network Slice Instance
NSSAI: Network Slice Selection Assistance Information
NSSF: Network Slice Selection Function
PCC: Policy and Charging Control
PCF: Policy Control Function
PDCP: Packet Data Convergence Protocol
PDN: Packet Data Network
PDU: Packet Data Unit
PEI: Permanent Equipment Identifier
RAN: Radio Access Network
RB: Radio Bearer
RFC: Request For Comments
RLC: Radio Link Control
RRC: Radio Resource Control
RM: Registration Management
SBA: Service Based Architecture
SDU: Service Data Unit
SMF: Session Management Function
SMSF: SMS Function
SN: Sequence Number
S-NSSAI: Single Network Slice Selection Assistance information
SRB: Signaling Radio Bearer carrying control plane data
SUPI: Subscriber Permanent Identifier
TDF: Traffic Detection Function
TA: Tracking Area
TAI: Tracking Area Identity
TCP: Transmission Control Protocol
UDM: Unified Data Management
UDP: User Datagram Protocol
UE: User Equipment
UL: Uplink
UL CL: Uplink Classifier
UPF: User Plane Function

Exemplary FIGS. 1 and 2 depict a 5G system consisting of an access network and a 5G core network. An exemplary 5G access network may include an access network that connects to a 5G core network. The access network may include NG-RAN 105 and/or non-3GPP AN 165. An exemplary 5G core network may connect to one or more 5G access networks' 5G-AN and/or NG-RAN. A 5G core network may comprise functional elements or network functions as in exemplary FIG. 1 and exemplary FIG. 2, where interfaces are used for communication between functional elements and/or network elements.

A network function can be a processing function in a network with functional behavior and interfaces. Network functions may be implemented as network elements on dedicated hardware and/or network nodes as depicted in FIGS. 3 and 4, or as software instances running on dedicated and/or shared hardware, or as appropriate platforms. It may be implemented either as a virtual function instantiated above.

The Access and Mobility Management Function AMF 155 provides the following functionality (some of the AMF functionality may be supported in a single instance of AMF 155), RAN CP interface termination (N2), NAS termination (N1 ), NAS ciphering and integrity protection, registration management, connection management, reachability management, mobility management, lawful interception (for AMF 155 events and interfaces to the LI system), session management, providing transport, UE 100 and SM messages to/from SMF 160, transparent proxy for routing SM messages, access authentication, access authorization, providing transport for SMS messages between UE 100 and SMSF, security anchor functions, SEA, AUSF 150 and UE 100 Interaction, reception of intermediate keys established as a result of the authentication process of the UE 100, security context management, the SCM receiving keys used to derive access network specific keys from the SEA may be included.

AMF 100 is connected via a non-3GPP access network via N2 interface by N3IWF 170, NAS signaling with UE 100 on N3IWF 170, authentication, mobility management, authentication of UEs connected on N3IWF 170, and non-3GPP access 165; or separate security context states for UE 100 connected via 3GPP and non-3GPP accesses 105, 165 at the same time, support for coordinated valid RM contexts on 3GPP and non-3GPP accesses 105, 165, connection on non-3GPP accesses CM management context support for UE 100 for compatibility. Some of the functionality described above may be supported by instances of network slices.

In one example, the AMF 155 region may consist of one or more AMF 100 sets. A set of AMFs 155 may consist of some AMFs 155 serving a given area and/or network slice. In one example, a set of multiple AMFs 155 may be for each AMF 155 region and/or network slice. An application identifier may be an identifier that can be mapped to a specific application traffic detection rule. The configured NSSAI may be the NSSAI provisioned in the UE 100 . A DN 115 access identifier (DNAI) for a DNN may be an identifier for user plane access to the DN 115 . A new registration may involve the registration of the UE 100 being in the RM-Deregistration 500, 520 state. N2AP UE 100 association may be logical per UE 100 association with 5G AN node and AMF 155 . An N2AP UE-TNLA binding may be a binding between an N2AP UE 100 association and a specific transport network layer (TNL) association for a given UE 100 .

Session management function SMF 160 provides the following functionality (one or more of the SMF 160 functionalities may be supported in a single instance of SMF 160), session management (e.g., between UPF 110 and nodes of AN 105 session establishment, modification, and teardown, including tunnel maintenance); UE 100 IP address assignment and management (including optional authorization); UP function selection and control; Configure traffic steering, terminate interface to policy control functions, control policy enforcement and QoS. Lawful intercept (for SM events and interfaces to LI systems), termination of SM part of NAS messages, downlink data notification, AN-specific SM sent over N2 to (R)AN 105 via AMF 155 Starting Information, Determining the SSC Mode of a Session, Roaming Functionality, Local Enforcement Processing (VPLMN), Charging Data Collection and Charging Interface (VPLMN), Lawful Intercept (at VPLMN, SM events and interfaces to the LI system), support for interaction with external DNs 115 to transport signaling for authorization/authentication of PDU sessions with external DNs 115. One or more of the functionality described above may need to be supported by an instance of a network slice.

The user plane function UPF 110 provides the following functionality (some of which functionality of the UPF 110 may be supported by a single instance of the UPF 110), an anchor point for intra-RAT and/or inter-RAT mobility (applicable possible), external PDU session points of interconnection to DN 115, packet routing and forwarding, user plane part of packet inspection and policy rule enforcement, lawful interception (UP collection), traffic usage reporting, traffic flow to data network Uplink classifier to support routing, bifurcation to support multihomed PDU sessions, QoS support for user plane, uplink traffic validation (SDF to QoS flow mapping), transport level in uplink and downlink packet marking, downlink packet buffering, and downlink data notification triggering. One or more of the functionality described above may be supported by an instance of a network slice.

IP address management for the UE 100 may include assigning and releasing IP addresses for the UE 100, and updating assigned IP addresses if applicable. The UE 100 sets the requested PDU type based on its IP stack capabilities and configuration during the PDU session establishment procedure. In one example, SMF 160 may select a PDU type for a PDU session as follows. When SMF 160 receives a request with a PDU type set to IP, SMF 160 may select either IPv4 or IPv6 for PDU type based on DNN configuration and carrier policy. A cause value may be provided by the SMF 160 to the UE 100 to indicate if the other IP version is supported by the DNN. If the other IP version is supported, the UE 100 may request another PDU session to the same DNN for the other IP version. If the SMF 160 receives a request for PDU type IPv4 or IPv6 and the requested IP version is supported by the DNN, it selects the PDU type requested by the SMF.

In an exemplary embodiment, the 5GC elements and the UE 100 support a mechanism that the IP address may be sent to the UE 100 in SM NAS signaling by the SMF 160 during the following PDU session establishment procedure. Once a PDU session is established, IPv4 address assignment and/or IPv4 parameter configuration via DHCPv4 may be used. IPv6 prefix assignment may be supported by IPv6 stateless autoconfiguration if IPv6 is supported. IPv6 parameter configuration with stateless DHCPv6 may be supported.

5GC may support static IPv4 address and/or static IPv6 prefix allocation based on UDM 140 subscription information or based on per-subscriber, per-DNN configuration.

A user plane function (UPF 110) may correspond to the user plane path of a PDU session. The PDU session anchor functionality is supported by the UPF 110 that provides the interface to the data network.

The Policy Control Function PCF 135 supports an integrated policy framework that governs network behavior, provides them to control plane functions to enforce policy rules, and provides policy decisions in a user data repository (UDR). A front end may be implemented to access relevant subscription information for the .

Network Publishing Function NEF 125 securely publishes services and capabilities provided by 3GPP network functions, translates between information exchanged with AF 145 and information exchanged with internal network functions, and receives information from other network functions. can provide a means to

The NF repository function NRF 130 supports the service discovery function, which receives NF discovery requests from NF instances, provides information of discovered NF instances (to be discovered) to the NF instances, identifies available NF instances and their It may maintain information about the services it supports.

Integrated Data Management UDM 140 includes application front-ends (FEs), including UDM-FEs responsible for authentication information processing, location management, subscription management, and PCF 135 responsible for policy management, and functionality provided by the UDM-FEs. may consist of a user data repository UDR that stores the data required by the PCF 135, plus policy profiles required by the PCF 135.

Configuration by the NSSF selecting the set of network slice instances serving the UE 100, determining the Allowed NSSAI, determining the set of AMFs 155 used to serve the UE 100, and/or possibly querying the NRF 130 may support determining a list of candidate AMFs 155 based on

The data stored in the UDR includes at least user subscription data including at least subscription identifiers, security credentials, access and mobility related subscription data and/or session related subscription data and/or policy data. .

The AUSF 150 provides an authentication server function (AUSF).
server function) may be supported. The functionality of the N3IWF 170 in the case of untrusted non-3GPP access 165 includes the following: support for establishing an IPsec tunnel with the UE; may relay the information necessary to authenticate the UE 100 and authorize access to the 5G core network via the termination of the N2 and N3 interfaces to the 5G core network for the control plane and user plane respectively; Relay of uplink and downlink control plane NAS (N1) signaling between UE 100 and AMF 155, support of N2 signaling from SMF 160 (relayed by AMF 155) related to PDU session and QoS, support PDU session traffic establish IPsec security associations (IPsec SAs), relay uplink and downlink user plane packets between UE 100 and UPF 110, QoS corresponding to N3 packet marking, received over N2 such Enforcement considering QoS requirements related to marking, N3 user plane packet marking in the uplink and/or selection of local mobility anchor, AMF 155, in untrusted non-3GPP access network 165 using MOBIKE. At least one or more of supports may be included.

Application functions AF 145 may interact with the 3GPP core network to provide services. Based on the carrier's deployment, the application functions may be trusted by the carrier and interact directly with the relevant network functions. Application functions that are not allowed to access network functions directly may use external exposed frameworks (via NEF 125) to interact with relevant network functions.

The control plane interface between the (R)AN 105 and the 5G core supports the connection of multiple different types of ANs (e.g. 3GPP RAN 105, N3IWF 170 for untrusted access 165) to the 5GC with a unique control plane protocol. may A single N2 AP protocol requires both 3GPP access 105 and non-3GPP access 165 as well as AMF 155 and control of services supported by the AN (e.g. control of UP resources in AN 105 for PDU sessions) It can be used to decouple other functions, such as the SMF 160, which can be

5GC may be able to provide policy information from PCF 135 to UE 100 . Such policy information may include, but is not limited to, the following: access network discovery and selection policy, UE route selection policy (URSP) or rather SSC mode selection policy (SSCMSP) for grouping UEs 100 : SSC mode selection policy), network slice selection policy (NSSP), DNN selection policy, and non-seamless offload policy.

A 5G core network may support connectivity for UE 100 via non-3GPP access networks 165 . As shown in exemplary Figures 5A and 5B, the registration management RM may be used to register or de-register a UE/user 100 with the network and establish a user context in the network. Connection management may be used to establish and release signaling connections between UE 100 and AMF 155 .

UE 100 may need to register with the network in order to receive services that require registration. Once registered, the UE 100 periodically (periodic registration update) to remain reachable, or for mobility (mobility registration update), or update capabilities or renegotiate protocol parameters, if applicable. may renew their registration with the network.

A new registration procedure, such as depicted in exemplary FIGS. 8 and 9, may involve performing network access control functions (eg, user authentication and access authorization based on subscription profiles in UDM 140). As a result of the registration procedure, the identity of serving AMF 155 may be registered with UDM 140 .

Registration management RM procedures may be applicable across both 3GPP accesses 105 and non-3GPP accesses 165 .

Exemplary FIGS. 5A and 5B depict the RM state of UE 100 as observed by UE 100 and AMF 155. FIG. In one exemplary embodiment, two RM states, namely RM-Deregister 500 and RM-Register 510, may be used for UE 100 and AMF 155 that reflect the registration status of UE 100 with the selected PLMN. In the RM Deregistration state 500, the UE 100 may not be registered with the network. UE 100 is not reachable by AMF 155 because the context of UE 100 in AMF 155 may not hold valid location or routing information for UE 100 . Some UE 100 context may still be stored in UE 100 and AMF 155 . In the RM Registered state 510, the UE 100 may be registered with the network. In the RM-Registration 510 state, the UE 100 may receive services that require registration with the network.

In an exemplary embodiment, two RM states, namely RM-Deregister 520 and RM-Register 530, may be used in AMF 155 for UE 100 to reflect the registration status of UE 100 to the selected PLMN.

As shown in exemplary FIGS. 6A and 6B, connection management (CM) may comprise functionality to establish and release signaling connections between UE 100 and AMF 155 on N1. This signaling connection may be used to enable NAS signaling exchanges between the UE 100 and the core network. Signaling connections include both the AN signaling connection between UE 100 and (R)AN 105 (eg RRC connection with 3GPP access) and the N2 connection between AN and AMF 155 for this UE 100 .

Two CM states, CM-idle 600, 620 and CM-connected 610, 630, may be used for NAS signaling connectivity of the UE 100 with the AMF 155, as depicted in exemplary FIGS. 6A and 6B. A UE 100 in CM-Idle 600 state is in RM-Registration 510 state and has no NAS signaling connection established by AMF 155 on N1. The UE 100 may perform cell selection, cell reselection, and PLMN selection. UE 100 in CM-Connected 610 state has a NAS signaling connection established by AMF 155 on N1.

In one exemplary embodiment, two CM states may be used for UE 100 in AMF 155: CM-Idle 620 and CM-Connected 630 .

The RRC inactive state may apply to NG-RAN (eg, applies to NR and E-UTRA connecting to 5G CN). AMF 155 may provide assistance information to NG RAN 105 to assist NG RAN 105 in deciding whether to send UE 100 to RRC inactive state based on network configuration. When the UE 100 is in the RRC inactive state and the CM-connected state 610, the UE 100 leaves the RAN 105 notification area in response to the RAN 105 paging by the terminal-initiated signaling procedure due to the suspension of uplink data. The RRC connection may be restarted by notifying the network that

NAS signaling connection management may include functions to establish and release NAS signaling connections. A NAS signaling connection establishment function may be provided by UE 100 and AMF 155 to establish a NAS signaling connection to UE 100 in CM-Idle 600 state. The NAS signaling connection release procedure may be initiated by the 5G(R)AN 105 node or the AMF 155 .

Reachability management of the UE 100 may detect if the UE 100 is reachable and the network provides the location of the UE 100 (eg, access node) to reach the UE 100 . This may be done by paging the UE 100 and location tracking of the UE 100 . UE 100 location tracking may include both UE 100 registration area tracking and UE 100 reachability tracking. Such functionality may be located either in the 5GC (for CM-Idle 620 state) or NG-RAN 105 (for CM-Connected 630 state). The UE 100 and AMF 155 may negotiate the reachability characteristics of the UE 100 in the CM-Idle 600, 620 state during registration and registration update procedures.

Two UE 100 reachability categories may be negotiated between the UE 100 and the AMF 155 for CM-Idle 600, 620 states. 1) Reachability of the UE 100 to provide termination data to the mobile device while the UE 100 is in CM-Idle 600 mode. 2) Terminal initiated connection only (MICO) mode. 5GC may support PDU connectivity services that provide PDU exchange between the UE 100 and the data network identified by the DNN. PDU connectivity services may be supported by PDU sessions, which are established upon request from UE 100 .

A PDU session may support one or more PDU session types. A PDU session is established (e.g., when requested by UE 100), modified (e.g., when requested by UE 100 and 5GC), and released ( at the request of the UE 100 and 5GC). Upon request from an application server, 5GC may trigger a specific application in UE 100 . Upon receiving the trigger message, the UE 100 may pass it to the identified application within the UE 100 . An identified application in UE 100 may establish a PDU session to a particular DNN.

A 5G QoS model may support a QoS flow-based framework as shown in exemplary FIG. A 5G QoS model may support both QoS flows that require a guaranteed flow bitrate and QoS flows that may not require a guaranteed flow bitrate. A 5G QoS model may support reflective QoS. The QoS model may include flow mapping or packet marking at the UPF (CN_UP) 110, AN 105, and/or UE 100. Packets may arrive from and/or go to the application/service layer 730 of the UE 100, the UPF (CN_UP) 110, and/or the AF 145.

A QoS flow may be the granularity of QoS differentiation in a PDU session. The QoS flow ID QFI (QoS Flow ID) may be used to identify QoS flows in 5G systems. User plane traffic with the same QFI within a PDU session may undergo the same traffic forwarding treatment. The QFI can be carried in an encapsulating header over N3 (and N9), for example, without any end-to-end packet header modification. QFI may be applied to PDUs with different types of payloads. A QFI may be unique within a PDU session.

The QoS parameters of a QoS flow may be provided to the (R)AN as a QoS profile over N2 in the PDU session or at QoS flow establishment, and the user plane is activated every time NG-RAN is used. be. Default QoS rules may be required for all PDU sessions. SMF 160 may assign QFIs to QoS flows and may derive its QoS parameters from information provided by the PCF. If applicable, the QFI may be provided by the SMF 160 to the (R)AN 105 along with the QoS profile containing the QoS parameters of the QoS flow.

A 5G QoS flow may be the granularity for QoS forwarding processing in a 5G system. Traffic mapped to the same 5G QoS flow may undergo the same forwarding treatment (eg, scheduling policy, queue management policy, rate shaping policy, RLC configuration, and/or the like). Providing different QoS forwarding treatments may require separate 5G QoS flows.

A 5G QoS indicator can be a scalar used as a reference to a particular QoS forwarding behavior (eg, packet loss rate, packet delay budget) provided to a 5G QoS flow. This depends on the specific parameters of the 5QI reference node (e.g. scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration, and/or the like) that control the QoS forwarding process of the access network. may be implemented in

5GC may support edge computing and may allow carrier and third party services to be hosted in close proximity to the access point to which the UE adheres. The 5G core network may select a UPF 110 that is close to the UE 100 and perform traffic steering from the UPF 110 over the N6 interface to the local data network. This may be based on UE 100 subscription data, UE 100 location, information from application function AF 145, policies, or other relevant traffic rules. The 5G core network may expose network information and capabilities to edge computing application functions. Functional support for edge computing includes: 5G core network selects UPF 110 to route user traffic to local data network; Traffic steering, enabling UE 100 and application mobility, session and service continuity, e.g., user plane selection and reselection based on input from application functions, 5G core network and application functions are routed by the NEF to Network capability exposures that can provide information to each other, QoS and charging rules that can provide QoS control and charging rules for traffic routed to local data networks by PCF, 5G core network deploy applications An area may include support for a local area data network, which may provide support to connect to the LADN.

An exemplary 5G system may be a 3GPP system consisting of a 5G access network 105, a 5G core network and UE 100, and/or the like. The unauthorized NSSAI may be, for example, the NSSAI provided by the serving PLMN during the registration procedure, indicating the network-allowed NSSAI for the UE 100 in the serving PLMN for the current registration area.

A PDU connectivity service may provide for the exchange of PDUs between the UE 100 and a data network. A PDU session may be an association between a UE 100 and a data network DN that provides PDU connectivity services. The type of association may be IP, or Ethernet or unstructured.

Establishing user plane connectivity to the data network by a network slice instance consists of at least two steps. Performing an RM procedure to select an AMF 155 that supports the required network slice and establishing one or more PDU sessions to the required data network by the network slice instance.

The set of network slices for a UE 100 may change at any time while the UE 100 is registered with the network, and may be initiated by the network or the UE 100.

A periodic registration update may be re-registration of the UE 100 upon expiration of a periodic registration timer. The requested NSSAI is the NSSAI that the UE 100 can provide to the network. A service-based interface may represent how a set of services is provided/exposed by a given NF.

Service continuity may be that users experience uninterrupted service, including when IP addresses and/or anchor points change. Session continuity may refer to continuity of a PDU session. For IP type PDU sessions, session continuity may mean that the IP address is preserved during the lifecycle of the PDU session. The uplink classifier may be a UPF functionality intended to divert uplink traffic towards the data network based on filter rules provided by SMF.

5G system architectures may support data connectivity and services that enable deployment using techniques such as, for example, network function virtualization and/or software-defined networking. The 5G system architecture may leverage service-based interactions between identified Control Plane (CP) network functions. In 5G system architecture, separation of user plane (UP) functions from control plane functions may be considered. 5G systems may allow network functions to interact directly with other NFs, if required.

A 5G system may reduce the dependency between the access network (AN) and the core network (CN). The architecture may comprise a centralized access independent core network with a common AN-CN interface that integrates different 3GPP and non-3GPP access types.

5G systems may also support a unified authentication framework, stateless NF where computational resources are decoupled from storage resources, capability exposure, and concurrent access to local and centralized services. To support low-latency services and access to local data networks, UP functions may be deployed in close proximity to access networks.

A 5G system may support roaming for both home-routed traffic and local breakout traffic at the visited PLMN. Exemplary 5G architectures may be service-based, and interactions between network functions can be represented in two ways. (1) FIG. 1 is an exemplary service-based representation, where network functions in the control plane may enable other authorized network functions to access services. The display may optionally include point-to-point reference points. (2) FIG. 2 is an exemplary reference point representation, where interaction between NF services within a network function is described by a point-to-point reference point (eg, N11) between any two network functions. show action.

As an example, a control plane of a communication system (eg, 5G) may use a service-based architecture. The interface/reference point (eg, Rx interface or Rx reference point) between AF and PCF may use HTTP protocol. Representational State Transfer (REST) may be used as an architectural style if desired. FIG. 16 is an exemplary diagram showing the protocol stack of the REST-Rx reference point. TCP may provide communication services at the transport layer. An application delivery layer may provide transport of specific application communication data using HTTP. Certain application communication layers may include transport of JSON content types.

The HTTP request message may have methods/processes that indicate to the server what actions the server may take. The client and/or server may use one of the following HTTP methods/processes. POST: HTTP POST can be used to create resource states. A request URI may define the address responsible for creating the resource. PUT: HTTP PUT may be used to replace the resource state. The full state of the resource may be provided in the body of the message. A request URI may define a resource that will be replaced. PATCH: The HTTP PATCH method may apply to partial modifications to resources. A request URI may define the resource that will be modified. GET: An HTTP GET may be used to retrieve the resource state. A request URI may define the resource to query. DELETE: HTTP DELETE may be used to delete resource state. A request URI may define a resource that will be deleted.

Implementing existing technologies can pose problems in supporting specific services/applications. Existing services/applications may have specific requirements for latency and reliability, and those services/applications may be public safety related. As shown in FIG. 14, scenarios requiring low latency and high availability of communication services may be separate automation-motion control, separate automation and process automation-remote control, and so on. FIG. 14 provides exemplary performance requirements for these scenarios. The overall service latency may depend on delays in air interface, transmission within the 5G system, transmission to application servers, which may be external to the 5G system, and/or data processing. Existing technologies may not be able to guarantee the QoS of services in some cases. The application server may measure/detect end-to-end delay between the application server and the wireless device. This may have the problem that the application server may be required to support measurement/detection functionality, which is the end-to-end delay between the application server and the wireless device. It can have a problem of comprehension. The application server determines which part of the delay (e.g., wireless device to access network, access network to core network, or core network to application server) is responsible for the end-to-end delay between the application server and wireless device. You don't have to have the ability to know what to get. Exemplary embodiments provide enhanced mechanisms to improve application server service performance and/or service QoS between the wireless device and the access network, between the access network and the core network, and/or from the core network. monitor and report on In one exemplary embodiment, a network entity in the 5G core network may notify an application server to adjust service behavior.

Implementing existing technologies can cause problems in supporting certain services/applications in roaming scenarios. Existing services/applications may have specific requirements for latency and reliability, and those services/applications may be public safety related. As shown in FIG. 14, scenarios requiring low latency and high availability of communication services may be separate automation-motion control, separate automation and process automation-remote control, and so on. FIG. 14 provides exemplary performance requirements for these scenarios. Overall service latency may depend on air interface, transmission within the 5G system of the visited and home PLMN, transmission to the application server, which may be external to the 5G system, and/or delay in data processing. . Existing technologies may not be able to guarantee the QoS of services in some cases. An application server (eg, HAF in a roaming scenario) may measure/detect end-to-end delay between the application server and wireless devices. This may have the problem that the application server may be required to support measurement/detection functionality, which is the end-to-end delay between the application server and the wireless device. It can have a problem of comprehension. The application server is responsible for any portion of the delay (e.g., wireless device to access network, access network to core network, or core network to the application server) may not have the ability to know what might be the cause of the end-to-end delay between the application server and the wireless device. Exemplary embodiments provide enhanced mechanisms to improve application server service performance and/or service QoS between the wireless device and the access network, between the access network and the core network, and/or from the core network. , and in a roaming scenario (eg, home routing roaming case), the application server may be in the home PLMN and the wireless device may be in the visited PLMN. In one exemplary embodiment, a network entity in the 5G core network of the visited PLMN may notify the application server in the home PLMN to adjust the service behavior.

Example 1
In one example, the AF may send the first message to a network node (eg, PCF or NEF). The first message may indicate a request to subscribe to at least one service performance/QoS event for a service data flow, service/application, PDU session and/or wireless device. The PCF may also subscribe to events to the SMF. FIG. 10 shows an exemplary call flow that may include one or more actions.

An AF (application server) sends messages (e.g., subscribing to service performance/QoS events, or provisioning application/service information) to network functions (e.g., PCF or NEF) to facilitate service data flow, service/ Applications, PDU sessions, and/or wireless devices may subscribe to at least one service performance/QoS event. As an example, the AF may send an HTTP POST message to the PCF to subscribe to at least one service performance/QoS event. A message sent from an AF to a PCF may contain one or more information elements. In one example, the message sent to the PCF includes a first information element indicating the service performance/QoS event trigger. If the service performance/QoS value has changed and/or the value is below a threshold (e.g., required service performance/QoS), the AF will notify the network function (e.g., PCF) that receives the event trigger that the service It may be requested to report the current value of performance/QoS. As an example, if the value of service performance/QoS has changed and/or the value is below a threshold (e.g., required service performance/QoS), the current value of service performance/QoS is replaced by the value of service performance/QoS. may be In one example, the message sent to the PCF includes a second information element indicating the requested service performance/QoS value, and may include one or more parameters using the second information element by the AF It may indicate the required service performance/QoS. In one example, the second information element includes end-to-end latency parameters. End-to-end latency may be the time it takes to convey a given piece of information from a source to a destination. As an example, the end-to-end latency between the wireless device and the separate automation-motion control application server/controller may be 1 millisecond. In one example, the second information element includes jitter parameters. Jitter may be the variation in the delay of received packets. As an example, the separate automation-motion control jitter may be 1 microsecond. In one example, the second information element includes a time-to-live parameter. Time to live may be the amount of time an application that consumes communication services can continue without an expected message. As an example, the separate automation-motor control lifetime can be 0 milliseconds. In one example, the second information element includes communication service availability parameters. Communication service availability may be dependable or reliable in service interfaces. As an example, the availability of separate automation-motion control communication services may be 99.9999%. In one example, the second information element includes a reliability parameter. The reliability of a given network node may be dependable or trustworthy. As an example, the separate automation-motor control reliability may be 99.9999%. In one example, the second information element includes a user experience data rate parameter. A user experience data rate may be the minimum data rate required to achieve a sufficient quality experience. As an example, separate automation-motion control user experience data rates may range from 1 Mbps up to 10 Mbps. In one example, the message sent to the PCF contains a third information element indicating the service data flow template. Service data flow templates may be used to detect service data flows for service performance/QoS events. In one example, the message sent to the PCF includes a fourth information element indicating the service/application identifier. Service/application identifiers may be used to detect services/applications for service performance/QoS events. In one example, the message sent to the PCF includes a fifth information element indicating the PDU session identifier. A PDU session identifier may be an identifier for a PDU session that applies to service performance/QoS events. In one example, the message sent to the PCF includes a sixth information element indicating the user identification of the wireless device. A user identity of a wireless device may be an identity of a wireless device that applies to service performance/QoS events. When the AF sends a message above to the NEF (eg, subscribing to service performance/QoS events or provisioning application/service information), as an example, the NEF forwards the message to the PCF.

One or more actions may be taken by the PCF in response to messages received from AF or NEF. In an exemplary action, the PCF makes policy decisions based on information (eg, desired service performance/QoS values) received from the AF or NEF. In an exemplary action, the PCF sends a message to the SMF (e.g., subscribe to service performance/QoS events or Nsmf_EventExposure_Subscribe) to subscribe to event triggers and/or to apply policies (e.g., QoS policies). Provision. The message may contain information received from the AF or NEF. As an example, the message sent to the SMF may include information (eg, requested service performance/QoS values) and/or policies (eg, QoS policy) received from the AF or NEF. As an example, a message sent to the SMF may include a policy (eg, QoS policy), and the policy may include information received from the AF or NEF (eg, requested service performance/QoS values).

In response to messages received from the PCF, the SMF may send messages to the UPF (e.g., subscribe to service performance/QoS events, or requests for N4 session establishment/modification) to subscribe to event triggers. and/or policies (eg, QoS policies) may be provisioned. A message may contain one or more information elements received from the PCF. As an example, the message sent to the UPF may include information (eg, requested service performance/QoS value) and/or policy (eg, QoS policy) received from the PCF. As an example, a message sent to the UPF may include a policy (eg, QoS policy), and the policy may include information received from the PCF (eg, requested service performance/QoS value). In response to messages received from the SMF, the UPF may send response messages to the SMF (eg, subscribe for service performance/QoS event responses, or N4 session establishment/modification responses).

In response to the message received from the UPF, the SMF may send a response message to the PCF (eg, subscribe to service performance/QoS event response, or Nsmf_EventExposure_Subscribe response). In response to messages received from the SMF, the PCF may send response messages to the AF (eg, subscribe service performance/QoS event response or application/service information provisioning response). As an example, PCF allows HTTP
An HTTP 201 CREATED message may be sent to the AF in response to the POST message.

One or more actions may be taken by the UPF in response to messages received from the SMF. An exemplary action is monitoring service performance/QoS for service data flows, services/applications, PDU sessions, and/or wireless devices by the UPF to measure/detect at least one service performance/QoS event. One or more methods may be taken to measure/detect service performance/QoS by UPF. In one exemplary method, the UPF monitors service performance/QoS between the UPF and the wireless device based on the echo function of internet control message protocol (ICMP). As an example, UPF may send a ping packet to the wireless device after receiving a response from the wireless device and calculate service performance/QoS values (eg, end-to-end latency, jitter). In one exemplary method, the UPF monitors service performance/QoS between the UPF and the (R)AN based on the ICMP echo function. As an example, the UPF may send a ping packet to the (R)AN after receiving a response from the (R)AN and calculate service performance/QoS values (e.g., end-to-end latency, jitter). . FIG. 15 is an exemplary call flow in which the UPF measures service performance/QoS with the ICMP echo function. In one exemplary method, the UPF queries service performance/QoS between the (R)AN and the wireless device. As an example, the UPF may send a signaling message to the (R)AN to inquire about service performance/QoS values between the (R)AN and the wireless device, the (R)AN and the wireless device, and send a response message containing the service performance/QoS values to the UPF. As an example, a user plane data packet containing an indication to query the service performance/QoS value between the (R)AN and the wireless device and/or the service performance/QoS value between the wireless device and the application server by the UPF (eg, in the header of the data packet) may be sent to the (R)AN. The (R)AN may measure/detect performance/QoS values between the (R)AN and the wireless device and/or the (R)AN may instruct the wireless device to may be requested to measure service performance/QoS values between The (R)AN may send user plane data packets (eg, in the header of the data packet) containing the measured service performance/QoS values to the UPF. In one exemplary method, the UPF monitors service performance/QoS between the UPF and the application server based on the Internet Control Message Protocol (ICMP) echo function. As an example, UPF may send a ping packet to an application server after receiving a response from the wireless device and calculate service performance/QoS values (eg, end-to-end latency, jitter). In an exemplary action, at least one service performance/QoS event is triggered for at least one of a service data flow, service/application, PDU session, and wireless device (e.g., service performance/QoS When detected by the UPF that the value has changed and/or is below a threshold (e.g., required service performance/QoS), the UPF sends a message (e.g., service performance/QoS measurement report) to the SMF. do. A message sent from the UPF to the SMF may contain one or more information elements. In one example, the message includes a first information element indicating a service performance/QoS event trigger. In one example, the message sent from the UPF to the SMF includes a second information element indicating the measured service performance/QoS value, and using the measured service performance/QoS value, one or more parameters may indicate service performance/QoS measured by a network function (eg, UPF), which may include: In one example, the second information element may include a parameter indicating service performance/QoS value type, which may be used to indicate the type or range of service performance/QoS. As an example, this parameter may include one or more types. An exemplary type may be a service performance/QoS value (eg, end-to-end latency) between UPF and wireless device. An exemplary type may be a service performance/QoS value (eg, end-to-end latency) between UPF and (R)AN. An exemplary type may be a service performance/QoS value (eg, end-to-end latency) between the (R)AN and the wireless device. An exemplary type may be service performance/QoS values (eg, end-to-end latency) between UPF and application servers. An exemplary type may be a service performance/QoS value (eg, end-to-end latency) between UE and application server. In one example, the second information element may include a parameter indicative of measured end-to-end latency. In one example, the second information element may include a parameter indicative of the measured jitter. In one example, the second information element may include a parameter indicative of measured survival time. In one example, the second information element may include a parameter indicative of the measured communication service availability. In one example, the second information element may include parameters indicative of the measured reliability. In one example, the second information element may include a parameter indicative of the measured user experience data rate. In one example, a message sent from UPF to SMF includes a third information element indicating a service data flow template. In one example, a message sent from UPF to SMF includes a fourth information element indicating a service/application identifier. In one example, a message sent from UPF to SMF includes a fifth information element indicating a PDU session identifier. In one example, the message sent from UPF to SMF includes a sixth information element indicating the user identity of the wireless device.

In response to the message received from the UPF, the SMF may send a message (eg, service performance/QoS measurement report) to the PCF that includes the information received from the UPF. In response to the message received from the SMF, the PCF may send a message (eg, service performance/QoS measurement report) containing the information received from the SMF to the AF or NEF. When the NEF receives a message (eg, service performance/QoS measurement report) from the PCF, the NEF may forward the message to the AF.

In response to a message received from the PCF or NEF, in response, based on information received from the PCF or NEF (e.g., event triggers of service performance/QoS values and/or measured service performance/QoS values) , AF can adjust the service behavior in time. As an example, the AF may change the codec rate of the video based on the measured service performance/QoS value (e.g., if the current service performance of the communication system is 8K Ultra High Definition (UHD) ) May not be able to support video, may change video codec rate to 4K UHD). Messages for application information changes (eg, provisioning of application/service information) may be sent by the AF to the PCF. As an example, with AF, any part of the delay (e.g., wireless device to access network, access network to core network, or core network to application server) causes long end-to-end delay between application server and wireless device. You may analyze whether it may be the cause. For example, the AF may determine that the end-to-end delay may be caused by the delay between the core network and the application server, and the AF determines the route between the core network (eg, UPF) and the application server. A message indicating a policy change (e.g., HTTP
PUT) may be sent to the PCF. A policy that selects a better route with a lower delay between the UPF and the application server compared to the current end-to-end delay may be sent by the PCF to the SMF and sent by the SMF to the UPF for enforcement. policy.

Example 2

In one example, the AF may send a first message to a network node (eg, PCF or NEF). The first message may indicate a request for at least one service performance/QoS report for a service data flow, service/application, PDU session, and/or wireless device. The PCF may also request reports from the SMF. FIG. 11 shows an exemplary call flow that may include one or more of the following actions.

A network function (e.g., PCF or NEF ) (eg requesting service performance/QoS reports or provisioning application/service information). A message sent to a network function (eg, PCF or NEF) may contain one or more information elements. In one example, the message includes a service performance/QoS report indication information element. The indication is to query the current value of one or more of the following parameters for service performance/QoS: end-to-end latency, jitter, time to live, communication service availability, reliability, and user experience data rate. , AF. As an example, a network function (eg, UPF) may measure current values of service performance/QoS parameters upon receiving a service performance/QoS report indication. In one example, the message includes an information element that indicates a service dataflow template. In one example, the message includes an information element that indicates a service/application identifier. In one example, the message includes an information element indicating a PDU session identifier. In one example, the message includes an information element that indicates the user identification of the wireless device. When the AF sends a message above to the NEF (eg request for service performance/QoS reports or provisioning of application/service information), the message may be forwarded by the NEF to the PCF, as an example.

One or more actions may be taken by the PCF in response to messages received from AF or NEF. In an exemplary action, the PCF makes policy decisions based on information received from AFs or NEFs. In an exemplary action, the PCF sends a message (eg, Request Service Performance/QoS Report) to the SMF to request at least one current Service Performance/QoS Report. The message may contain information received from the AF or NEF. As an example, messages sent to the SMF may include information (eg, service performance/QoS report indications) and/or policies (eg, QoS policies) received from AFs or NEFs. As an example, a message sent to the SMF may include a policy (eg, QoS policy), and the policy may include information received from the AF or NEF (eg, service performance/QoS report indication). In response to the message received from the PCF, send a message (e.g., Request for Service Performance/QoS Report or Request for N4 Session Establishment/Modification) to the UPF to request the current Service Performance/QoS Report by the SMF. and/or a policy (eg, QoS policy) may be provisioned. The message may contain information received from the PCF. As an example, messages sent to the UPF may include information received from the PCF (eg, service performance/QoS report indications) and/or policies (eg, QoS policies). As an example, a message sent to the UPF may include a policy (eg, QoS policy), and the policy may include information received from the PCF (eg, service performance/QoS report indication).

One or more actions may be taken by the UPF in response to messages received from the SMF. In an exemplary action, the UPF monitors service data flows, services/applications, PDU sessions, and/or service performance/QoS of the wireless device to measure/detect at least one service performance/QoS event. One or more methods may be taken to measure/detect service performance/QoS by UPF. In one exemplary method, the UPF monitors service performance/QoS between the UPF and the wireless device based on the Internet Control Message Protocol (ICMP) echo function. As an example, UPF may send a ping packet to the wireless device after receiving a response from the wireless device and calculate service performance/QoS values (eg, end-to-end latency, jitter). In one exemplary method, the UPF monitors service performance/QoS between the UPF and the (R)AN based on the ICMP echo function. As an example, the UPF may send a ping packet to the (R)AN after receiving a response from the (R)AN and calculate service performance/QoS values (e.g., end-to-end latency, jitter). . In one exemplary method, the UPF queries service performance/QoS between the (R)AN and the wireless device. As an example, the UPF may send a signaling message to the (R)AN to inquire about service performance/QoS values between the (R)AN and the wireless device, the (R)AN and the wireless device, and send a response message containing the service performance/QoS values to the UPF. As an example, send user plane data packets containing indications (e.g., in the header of the data packet) to the (R)AN over the UPF to provide service performance/performance between the (R)AN and the wireless device. QoS values may be queried, and the (R)AN measures/detects performance/QoS values between the (R)AN and the wireless device and sends user plane data packets ( for example, in the header of the data packet) may be sent. In an exemplary action, the UPF may send a report message (e.g., service performance/QoS measurement report, or N4 session establishment/modification response) to the SMF, where the report message contains one or more information elements. may contain. In one example, the report message includes a first information element indicating the measured service performance/QoS value. A first information element may be used to indicate a measured service performance/QoS, which may include one or more parameters. In one example, the first information element includes a parameter indicating service performance/QoS value type, which may be used to indicate the type or range of service performance/QoS. As an example, this parameter can be of the following types: service performance/QoS value between UPF and wireless device (e.g., end-to-end latency); service performance/QoS value between UPF and (R)AN ( end-to-end latency), service performance/QoS value between (R)AN and wireless device (e.g., end-to-end latency), service performance/QoS value between UPF and application server (e.g., , end-to-end latency), and service performance/QoS values (eg, end-to-end latency) between the UE and the application server. In one example, the first information element includes a parameter indicative of measured end-to-end latency. In one example, the first information element includes a parameter indicative of measured jitter. In one example, the first information element includes a parameter indicative of measured survival time. In one example, the first information element includes a parameter indicative of the measured communication service availability. In one example, the first information element includes a parameter indicative of measured reliability. In one example, the first information element includes a parameter indicative of the measured user experience data rate. In one example, the report message includes a second information element indicating a service data flow template. In one example, the report message includes a third information element indicating the service/application identifier. In one example, the report message includes a fourth information element indicating a PDU session identifier. In one example, the report message includes a fifth information element indicating the user identification of the wireless device.

In response to the message received from the UPF, the SMF may send a message (eg, service performance/QoS measurement report) to the PCF that includes the information received from the UPF. In response to the message received from the SMF, the PCF may send a message (eg, service performance/QoS measurement report) containing the information received from the SMF to the AF or NEF. When the NEF receives a message (eg, service performance/QoS measurement report) from the PCF, the NEF may forward the message to the AF. In response to messages received from the PCF or NEF, service behavior may be timely adjusted by the AF accordingly based on information (eg, measured service performance/QoS values) received from the PCF or NEF. As an example, the AF may change the video codec rate based on the measured service performance/QoS value (e.g., the current service performance of the communication system supports 8K Ultra High Definition (UHD) video). may not be possible, you may change the video codec rate to 4K UHD). Messages for application information changes (eg, provisioning of application/service information) may be sent by the AF to the PCF.

Example 3
In one example, compared to Example 2, the (R)AN may perform the service performance/QoS measurements rather than the UPF doing the measurements. FIG. 12 shows an exemplary call flow that may include one or more actions.

A network function (e.g., PCF or NEF ) (eg requesting service performance/QoS reports or provisioning application/service information). A message may contain one or more information elements. In one example, the message includes a service performance/QoS report indication information element. AF uses an indication to present one or more of the following parameters for service performance/QoS: end-to-end latency, jitter, time to live, communication service availability, reliability, and user experience data rate You can query the value of In one example, the message includes an information element that indicates a service dataflow template. In one example, the message includes an information element that indicates a service/application identifier. In one example, the message includes an information element indicating a PDU session identifier. In one example, the message includes an information element that indicates the user identification of the wireless device. When the AF sends a message above to the NEF (eg request for service performance/QoS reports or provisioning of application/service information), as an example, the message may be forwarded by the NEF to the PCF.

One or more actions may be taken by the PCF in response to messages received from AF or NEF. In an exemplary action, the PCF makes policy decisions based on information received from the AF or NEF. In an exemplary action, the PCF sends a message (eg, request for service performance/QoS report) to the SMF indicating at least one current service performance/QoS report. The message may contain information received from the AF or NEF. As an example, messages sent to the SMF may include information (eg, service performance/QoS report indications) and/or policies (eg, QoS policies) received from AFs or NEFs. As an example, a message sent to the SMF may include a policy (eg, QoS policy), and the policy may include information received from the AF or NEF (eg, service performance/QoS report indication).

In response to the message received from the PCF, the SMF may send a message (e.g., request for service performance/QoS report) to the AMF to request the current service performance/QoS report and/or the policy ( For example, QoS policies) may be provisioned. The message may contain information received from the PCF. As an example, messages sent to the AMF may include information received from the PCF (eg, service performance/QoS report indications) and/or policies (eg, QoS policies). As an example, messages sent to the AMF may include policies (eg, QoS policies), and policies may include information received from the PCF (eg, service performance/QoS report indications). In response to the message received from the SMF, the AMF may send a message (e.g., Request Service Performance/QoS Report) to the (R)AN to request the current Service Performance/QoS Report and/or Or policies (eg, QoS policies) may be provisioned. The message may contain information received from the SMF. As an example, the message sent to the (R)AN may include information received from the SMF (eg service performance/QoS report indication) and/or policy (eg QoS policy). As an example, a message sent to the (R)AN may include a policy (eg, QoS policy), and the policy may include information received from the SMF (eg, service performance/QoS report indication).

In response to messages received from the AM, the (R)AN may take one or more actions. In an exemplary action, the (R)AN monitors service data flows, services/applications, PDU sessions, and/or wireless device service performance/QoS to measure/detect at least one service performance/QoS event. do. The (R)AN may take one or more methods to measure/detect service performance/QoS. In one exemplary method, the (R)AN monitors service performance/QoS between the (R)AN and the UPF based on the ICMP echo function; After receiving the response, it may send a ping packet to the UPF and calculate service performance/QoS values (eg, end-to-end latency, jitter). In one exemplary method, the (R)AN queries service performance/QoS between the (R)AN and the wireless device. As an example, after receiving a response from the wireless device, the (R)AN sends a data packet (e.g., PDCP packet) to the wireless device and provides service performance/QoS values (e.g., end-to-end latency, jitter). can be calculated. In an exemplary action, the (R)AN may send a message (eg, service performance/QoS measurement report) to the AMF, and the report message may contain one or more information elements. In one example, the report message includes a first information element indicating a measured service performance/QoS value, and using the first information element, the measured service performance/QoS value may include one or more parameters. QoS may be indicated. In one example, the first information element includes a parameter indicating service performance/QoS value type, which may be used to indicate the type or range of service performance/QoS. As an example, this parameter can be of the following types: service performance/QoS value between UPF and wireless device (e.g., end-to-end latency); service performance/QoS value between UPF and (R)AN ( end-to-end latency), service performance/QoS value between (R)AN and wireless device (e.g., end-to-end latency), service performance/QoS value between UPF and application server (e.g., , end-to-end latency), and service performance/QoS values (eg, end-to-end latency) between the UE and the application server. In one example, the first information element includes a parameter indicative of measured end-to-end latency. In one example, the first information element includes a parameter indicative of measured jitter. In one example, the first information element includes a parameter indicative of measured survival time. In one example, the first information element includes a parameter indicative of the measured communication service availability. In one example, the first information element includes a parameter indicative of measured reliability. In one example, the first information element includes a parameter indicative of the measured user experience data rate. In one example, the report message includes a second information element indicating a service data flow template. In one example, the report message includes a third information element indicating the service/application identifier. In one example, the report message includes a fourth information element indicating a PDU session identifier. In one example, the report message includes a fifth information element indicating the user identification of the wireless device.

In response to the message received from the (R)AN, the AMF may send a message (eg, service performance/QoS measurement report) to the SMF that includes the information received from the (R)AN. In response to messages received from AMF, messages (eg, service performance/QoS measurement reports) containing information received from AMF may be sent by SMF to PCF. In response to the message received from the SMF, the PCF may send a message (eg, service performance/QoS measurement report) containing the information received from the SMF to the AF or NEF. When the NEF receives a message (eg, service performance/QoS measurement report) from the PCF, the NEF may forward the message to the AF. In response to messages received from the PCF or NEF, service behavior may be timely adjusted by the AF accordingly based on information (eg, measured service performance/QoS values) received from the PCF or NEF. As an example, the AF may change the video codec rate based on the measured service performance/QoS value (e.g., the current service performance of the communication system supports 8K Ultra High Definition (UHD) video). may not be possible, you may change the video codec rate to 4K UHD). Messages for application information changes (eg, provisioning of application/service information) may be sent by the AF to the PCF.

Example 4
In one example, the (R)AN may receive service performance/QoS event subscriptions from the AMF, and the (R)AN may report to the AMF when events are triggered. FIG. 13 shows an exemplary call flow that may include one or more actions.

The AF sends messages (e.g., subscribing to service performance/QoS events, or provisioning of application/service information) to network functions (e.g., PCF or NEF) to facilitate service data flow, service/application, PDU session , and/or to at least one service performance/QoS event for the wireless device. A message may contain one or more information elements. In one example, the message includes information elements that indicate service performance/QoS event triggers. Using event triggers, the current value of service performance/QoS is requested when the value of service performance/QoS has changed and/or the value is below a threshold (e.g., requested service performance/QoS). , may indicate that it is reported. In one example, the message contains an information element indicating the service performance/QoS value requested and uses this information element (IE) to specify the following parameters: end-to-end latency, jitter, time to live, A requested service performance/QoS, which may include one or more of communication service availability, reliability, user experience data rate, may be indicated by the AF. In one example, the message includes an information element that indicates a service dataflow template. In one example, the message includes an information element that indicates a service/application identifier. In one example, the message includes an information element indicating a PDU session identifier. In one example, the message includes an information element that indicates the user identification of the wireless device. When the AF sends a message above to the NEF (eg, subscribing to service performance/QoS events or provisioning application/service information), the message may be forwarded by the NEF to the PCF, as an example.

One or more actions may be taken by the PCF in response to messages received from AF or NEF. In an exemplary action, the PCF makes policy decisions based on information (eg, desired service performance/QoS values) received from the AF or NEF. In an exemplary action, the PCF sends a message to the SMF (e.g., subscribe to service performance/QoS events or Nsmf_EventExposure_Subscribe) to subscribe to event triggers and/or to apply policies (e.g., QoS policies). Provision. The message may contain information received from the AF or NEF. As an example, the message sent to the SMF may include information (eg, requested service performance/QoS values) and/or policies (eg, QoS policy) received from the AF or NEF. As an example, a message sent to the SMF may include a policy (eg, QoS policy), and the policy may include information received from the AF or NEF (eg, requested service performance/QoS values).

In response to messages received from the PCF, the SMF may send messages to the AMF (e.g., subscribe to service performance/QoS events), subscribe to event triggers, and/or subscribe to policies (e.g., QoS policy) may be provisioned. The message may contain information received from the PCF. As an example, the message sent to the AMF may include information (eg, requested service performance/QoS value) and/or policy (eg, QoS policy) received from the PCF. As an example, a message sent to the AMF may include a policy (eg, QoS policy), and the policy may include information received from the PCF (eg, requested service performance/QoS value). In response to messages received from the SMF, the AMF may send messages (e.g., subscribe to service performance/QoS events) to the (R)AN to subscribe to event triggers and/or policy (eg, QoS policy) may be provisioned. The message may contain information received from the SMF. As an example, the message sent to the (R)AN may include information received from the SMF (eg requested service performance/QoS value) and/or policy (eg QoS policy). As an example, a message sent to the (R)AN may include a policy (e.g. QoS policy), and the policy may include information received from the SMF (e.g. requested service performance/QoS values) . In response to messages received from the AMF, the (R)AN may send response messages to the AMF (eg, subscribe to service performance/QoS event responses). In response to the message received from the (R)AN, the AMF may send a response message (eg, subscribe to service performance/QoS event response) to the SMF. In response to messages received from AMF, response messages (eg, subscribe to service performance/QoS event response or Nsmf_EventExposure_Subscribe response) may be sent by SMF to PCF. In response to messages received from the SMF, the PCF may send response messages to the AF (eg, subscribe service performance/QoS event response or application/service information provisioning response).

In response to messages received from AMF, (R)AN may take one or more actions. In an exemplary action, the (R)AN monitors service data flows, services/applications, PDU sessions, and/or wireless device service performance/QoS to measure/detect at least one service performance/QoS event. do. The (R)AN may take one or more methods to measure/detect service performance/QoS. In one exemplary method, the (R)AN monitors service performance/QoS between the (R)AN and the UPF based on the ICMP echo function. As an example, after receiving a response from the UPF, the (R)AN may send a ping packet to the UPF and calculate service performance/QoS values (eg, end-to-end latency, jitter). In one exemplary method, the (R)AN queries service performance/QoS between the (R)AN and the wireless device. As an example, the UPF may send a signaling message to the (R)AN to inquire about service performance/QoS values between the (R)AN and the wireless device, the (R)AN and the wireless device, and send a response message containing the service performance/QoS values to the UPF. As an example, after receiving a response from the wireless device, the (R)AN sends a data packet (e.g., PDCP packet) to the wireless device and provides service performance/QoS values (e.g., end-to-end latency, jitter). can be calculated. In an exemplary action, at least one service performance/QoS event is triggered for at least one of a service data flow, service/application, PDU session, and wireless device (e.g., service performance/QoS If the (R)AN detects that the value has changed and/or is below a threshold (e.g., required service performance/QoS), the (R)AN sends a message to the AMF (e.g., service performance /QoS measurement report) may be sent. A measurement report message may contain one or more information elements. In one example, the measurement report message includes information elements that indicate service performance/QoS event triggers. In one example, the measurement report message includes a first information element indicating the measured service performance/QoS value, and may include one or more parameters using a first information element (IE). It may also indicate service performance/QoS. In one example, the first information element includes a parameter indicating service performance/QoS value type, which may be used to indicate the type or range of service performance/QoS. As an example, this parameter can be of the following types: service performance/QoS value (e.g., end-to-end latency) between UPF and (R)AN; service performance/QoS value between (R)AN and wireless device; It may include one or more of QoS values (eg, end-to-end latency), service performance/QoS values (eg, end-to-end latency) between the UE and the application server. In one example, the first information element includes a parameter indicative of measured end-to-end latency. In one example, the first information element includes a parameter indicative of measured jitter. In one example, the first information element includes a parameter indicative of measured survival time. In one example, the first information element includes a parameter indicative of the measured communication service availability. In one example, the first information element includes a parameter indicative of measured reliability. In one example, the first information element includes a parameter indicative of the measured user experience data rate. In one example, the measurement report message includes a second information element indicating a service data flow template. In one example, the measurement report message includes a third information element indicating a service/application identifier. In one example, the measurement report message includes a fourth information element indicating a PDU session identifier. In one example, the measurement report message includes a fifth information element indicating user identification of the wireless device.

In response to the message received from the (R)AN, the AMF may send a message (eg, service performance/QoS measurement report) to the SMF that includes the information received from the (R)AN. In response to messages received from AMF, messages (eg, service performance/QoS measurement reports) containing information received from AMF may be sent by SMF to PCF. In response to the message received from the SMF, the PCF may send a message (eg, service performance/QoS measurement report) containing the information received from the SMF to the AF or NEF. When the NEF receives a message (eg, service performance/QoS measurement report) from the PCF, the NEF may forward the message to the AF.

In response to a message received from the PCF or NEF, in response, based on information received from the PCF or NEF (e.g., event triggers of service performance/QoS values and/or measured service performance/QoS values) , AF can adjust the service behavior in time. As an example, the AF may change the video codec rate based on the measured service performance/QoS value (e.g., the current service performance of the communication system supports 8K Ultra High Definition (UHD) video). may not be possible, you may change the video codec rate to 4K UHD). Messages for application information changes (eg, provisioning of application/service information) may be sent by the AF to the PCF.

As an example, the SMF sends a first message from the PCF indicating a request to subscribe to at least one service performance/QoS event for a service data flow, service/application, PDU session, and/or wireless device. may be received, the first message is indicative of at least one service performance/QoS event, including at least one first information element (IE), a first end-to-end latency, a first jitter, a first At least one second IE indicative of a service performance/QoS value including at least one of a time to live of one, availability of the first communication service, a first confidence value, or a first user experience data rate. , at least one third IE indicating a template of a service data flow, at least one fourth IE indicating a first identifier of a service/application, at least one fourth IE indicating a second identifier of a PDU session. 5 IEs, or at least one of six IEs indicating a user identity of the wireless device, and in response to the first message, by SMF to the UPF, at least one service performance/QoS Send a second message indicating a request to subscribe to the event.

As an example, a response message to the second message may be received from the UPF, the response message indicating that at least one service performance/QoS event is a service data flow, service/application, PDU session, and wireless device and the response message may indicate the following: a second end-to-end latency, a second jitter, a second time-to-live, a second communication service At least one service performance/QoS value may be included including at least one of availability, a second reliability, or a second user experience data rate.

As an example, a third message containing at least one service performance/QoS value may be sent by the SMF to the PCF.

In one example, the UPF may monitor service data flows, services/applications, PDU sessions, and/or wireless device service performance/QoS to detect at least one service performance/QoS event.

In one example, the service performance/QoS monitoring includes a first service performance/QoS monitoring between the UPF and the wireless device based on the Internet Control Message Protocol (ICMP) echo function, the ICMP echo function based UPF and (R)AN monitoring a second service performance/QoS between the (R)AN and the wireless device; A request message may be sent to the (R)AN indicating the request to monitor QoS.

In one example, the AF sends a first message to the PCF indicating a request to subscribe to at least one service performance/QoS event for a service data flow, service/application, PDU session, and/or wireless device. and wherein the first message is indicative of at least one service performance/QoS event, including at least one first information element (IE), a first end-to-end latency, a first jitter, a first At least one second IE indicating a service performance/QoS value including at least one of a time to live of one, availability of the first communication service, a first confidence value, or a first user experience data rate. , at least one third IE indicating a template of a service data flow, at least one fourth IE indicating a first identifier of a service/application, at least one fourth IE indicating a second identifier of a PDU session. 5 IEs, or at least one of at least one of six IEs that indicate the user identity of the wireless device.

In one example, the AF may receive a response message to the first message from the PCF.

In one example, a measurement indicating that at least one service performance/QoS event is triggered by the AF from the PCF to at least one of a service data flow, a service/application, a PDU session, and a wireless device A report message may be received, the measurement report message comprising: a second end-to-end latency, a second jitter, a second time-to-live, a second communication service availability, a second reliability , or at least one service performance/QoS value comprising at least one of the second user-experienced data rate.

In one example, the AF may timely adjust service behavior and/or determine application parameters accordingly based on at least one service performance/QoS value. A message for changing application parameters may be sent by the AF to the PCF.

In one example, the SMF may receive a first message from the PCF indicating a request for at least one service performance/QoS report for a service data flow, service/application, PDU session, and/or wireless device; The first message includes at least one first information element (IE) indicating at least one service performance/QoS report, a first end-to-end latency, a first jitter, a first time to live, a first at least one second IE indicating a service performance/QoS type to report including at least one of one communication service availability, a first confidence value, or a first user experience data rate; service data; At least one third IE indicating a template of a flow; at least one fourth IE indicating a first identifier of a service/application; at least one fifth IE indicating a second identifier of a PDU session. , or at least one of the six IEs that indicate the user identity of the wireless device.

In one example, in response to the first message, the SMF may send a second message to the UPF indicating a request for at least one service performance/QoS report.

In one example, a response message to the second message may be received by the SMF from the UPF, the response message indicating at least one service for the service data flow, service/application, PDU session, and/or wireless device. a second end-to-end latency, a second jitter, a second time-to-live, a second communication service availability, a second Indicate at least one of reliability or a second user experience data rate.

In one example, a third message containing at least one service performance/QoS measurement may be sent by the SMF to the PCF.

In one example, the AF may send a first message to the PCF indicating a request for at least one service performance/QoS report for the service data flow, service/application, PDU session, and/or wireless device; The first message includes at least one first information element (IE) indicating at least one service performance/QoS report, a first end-to-end latency, a first jitter, a first time to live, a first at least one second IE indicative of a service performance/QoS type including at least one of one communication service availability, a first confidence value, or a first user experience data rate; a service data flow template; at least one third IE indicating a first identifier of a service/application; at least one fifth IE indicating a second identifier of a PDU session; or wireless Include at least one of at least one of six IEs that indicate the user identity of the device.

In one example, a response message including at least one service performance/QoS measurement for a service data flow, service/application, PDU session, and/or wireless device from the PCF by the AF in response to the first message and the at least one service performance/QoS measure is a second end-to-end latency, a second jitter, a second time to live, a second communication service availability, a second reliability or a second user experience data rate, the AF determining to adjust the application parameters based on the at least one service performance/QoS measurement.

In one example, the SMF may receive a first message from the PCF indicating a request for at least one service performance/QoS report for a service data flow, service/application, PDU session, and/or wireless device; The first message includes at least one first information element (IE) indicating at least one service performance/QoS report, a first end-to-end latency, a first jitter, a first time to live, a first at least one second IE indicating a service performance/QoS type to be reported including at least one of one communication service availability, a first confidence value, or a first user experience data rate, service data; At least one third IE indicating a template of a flow; at least one fourth IE indicating a first identifier of a service/application; at least one fifth IE indicating a second identifier of a PDU session. , or at least one of the six IEs that indicate the user identity of the wireless device.

In one example, in response to the first message, SMF may send a second message to AMF indicating a request for at least one service performance/QoS report.

In one example, in response to the second message, the AMF may send a third message to the (R)AN indicating a request for at least one service performance/QoS report.

In one example, a first response message to the third message may be received by the AMF from the (R)AN, the first response message being the service data flow, service/application, PDU session, and/or or for the wireless device, including at least one service performance/QoS measurement, wherein the at least one service performance/QoS measurement is a second end-to-end latency, a second jitter, a second time to live, a second communication service availability, a second reliability, or a second user experience data rate.

In one example, the SMF may receive from the AMF a second response message to the second message, the second response message including at least one service performance/QoS measurement.

In one example, a fourth message containing at least one service performance/QoS measurement may be sent by the SMF to the PCF.

In one example, the (R)AN is an Internet Control Message Protocol (ICMP) echo function between the (R)AN and the UPF, or an ICMP echo function and/or a PDCP function between the (R)AN and the wireless device. Based on at least one of the service data flow, service/application, PDU session, and/or wireless device service performance/QoS may be measured.

Example 5
In one example, the wireless device may be in a visited network and an application server (eg, Home AF (HAF)) may be in a home network. In a home routing roaming scenario, a wireless device may send user data from a visited network to an application server located in the home network. A first message may be sent by the HAF to a network node (eg, HPCF or HNEF). The first message may indicate a request to subscribe to at least one service performance/QoS event for a service data flow, service/application, PDU session and/or wireless device. The HPCF may also subscribe to events to the VPCF, which may be in the visited network. FIG. 17 shows an exemplary call flow that may include one or more actions.

HAF (application server) sends messages (e.g. subscribe to service performance/QoS events or provision application/service information) to network functions (e.g. home PCF or home NEF) to facilitate service data flow, service subscribe to at least one service performance/QoS event for /application, PDU session, and/or wireless device; As an example, the HAF may send an HTTP POST message to the HPCF to subscribe to at least one service performance/QoS event. A message may contain one or more information elements. In one example, the message includes a first information element indicating a service performance/QoS event trigger. If the service performance/QoS value has changed and/or the value is below a threshold (e.g. the requested service performance/QoS value), the network function (e.g. HPCF) that receives the event trigger by the HAF to: It may be requested to report the current value of service performance/QoS. As an example, the current value of the service performance/QoS is changed and/or the value is below a threshold (e.g., the requested service performance/QoS) value). It can be a QoS value. In one example, the message includes a second information element indicating the service performance/QoS value requested, and using this information element (IE), may include one or more of the following parameters by the HAF: It may indicate the required service performance/QoS. In one example, the second information element includes a parameter indicative of end-to-end latency. End-to-end latency may be the time it takes to convey a given piece of information from a source to a destination. As an example, the end-to-end latency between the wireless device and the separate automation-motion control application server/controller may be 1 millisecond. In one example, the second information element includes a parameter indicative of jitter. Jitter may be the variation in the delay of received packets. As an example, the separate automation-motion control jitter may be 1 microsecond. In one example, the second information element includes a parameter indicating time to live. Time to live may be the amount of time an application that consumes communication services can continue without an expected message. As an example, the separate automation-motor control lifetime may be 0 milliseconds. In one example, the second information element includes a parameter indicative of communication service availability. The availability of communication services of service interfaces may be dependable or reliable. As an example, the availability of the separate automation-motion control communication service may be 99.9999%. In one example, the second information element includes a parameter indicative of reliability. The reliability of a given network node may be dependable or trustworthy. As an example, the separate automation-motor control reliability may be 99.9999%. In one example, the second information element includes a parameter indicating user experience data rate. A user experience data rate may be the minimum data rate required to achieve a sufficient quality experience. As an example, separate automation-motion control user experience data rates may range from 1 Mbps up to 10 Mbps. In one example, the message includes a third information element indicating a service data flow template. Service data flow templates may be used to detect service data flows for service performance/QoS events. In one example, the message includes a fourth information element indicating a service/application identifier. Service/application identifiers may be used to detect services/applications for service performance/QoS events. In one example, the message includes a fifth information element indicating a PDU session identifier. A PDU session identifier may be an identifier for a PDU session that applies to service performance/QoS events. In one example, the message includes a sixth information element indicating the user identification of the wireless device. A user identity of a wireless device may be an identity of a wireless device that applies to service performance/QoS events. When the HAF sends a message above to the HNEF (eg, subscribing to service performance/QoS events or provisioning application/service information), the message may be forwarded by the HNEF to the HPCF, as an example.

One or more actions may be taken by the HPCF in response to messages received from the HAF or HNEF. In an exemplary action, the HPCF makes policy decisions based on information (eg, desired service performance/QoS values) received from the HAF or HNEF. In an exemplary action, the HPCF sends a message (e.g., subscribe to service performance/QoS events, or Nsmf_EventExposure_Subscribe) to a visited PCF (VPCF) to subscribe to event triggers, and/or or provision policies (eg, QoS policies). The message may contain information received from the HAF or HNEF. As an example, messages sent to the VPCF may include information received from the HAF or HNEF (e.g., requested service performance/QoS values) and/or policies made by the HPCF (e.g., QoS policies). . As an example, a message sent to the VPCF may contain a policy (e.g. QoS policy) made by the HPCF, which is the information received from the HAF or HNEF (e.g. requested service performance/QoS values) may include

One or more actions may be taken by the VPCF in response to messages received from the HPCF. In one example, the VPCF makes policy decisions based on information received from the HPCF (e.g., desired service performance/QoS values), and in one example, the policy created from the VPCF is the same as the policy received from the HPCF. and as an example, the policy created from the VPCF may differ from the policy received from the HPCF. In one example, the VPCF sends messages to the SMF (eg, subscribe to service performance/QoS events or Nsmf_EventExposure_Subscribe) to subscribe to event triggers and/or provision policies (eg, QoS policies). The SMF may be in the visited network. The message may contain information received from the HPCF. As an example, the message sent to the SMF may include information (eg, requested service performance/QoS value) and/or policy (eg, QoS policy) received from the HPCF. As an example, a message sent to the SMF may include a policy (eg, QoS policy), and the policy may include information received from the HPCF (eg, requested service performance/QoS values).

In response to messages received from VPCF, SMF may send messages to UPF (e.g., subscribe to service performance/QoS events, or requests for N4 session establishment/modification) to subscribe to event triggers. and/or policies (eg, QoS policies) may be provisioned. The UPF may be in the visited network. The message may contain information received from the VPCF. As an example, the message sent to the UPF may include information (eg, requested service performance/QoS value) and/or policy (eg, QoS policy) received from the VPCF. As an example, a message sent to the UPF may include a policy (eg, QoS policy), and the policy may include information received from the VPCF (eg, requested service performance/QoS value). In response to messages received from the SMF, the UPF may send response messages to the SMF (eg, subscribe for service performance/QoS event responses, or N4 session establishment/modification responses). In response to the message received from the UPF, the SMF may send a response message to the VPCF (eg, subscribe to service performance/QoS event response, or Nsmf_EventExposure_Subscribe response). In response to the message received from the SMF, the VPCF may send a response message to the HPCF (eg, subscribe for service performance/QoS event response, or Nsmf_EventExposure_Subscribe response). In response to the message received from the VPCF, the HPCF may send a response message to the HAF (eg, subscribe service performance/QoS event response or application/service information provisioning response). As an example, the HPCF may send an HTTP 201 CREATED message to the HAF in response to an HTTP POST message.

One or more actions may be taken by the UPF in response to messages received from the SMF. An exemplary action is monitoring service performance/QoS for service data flows, services/applications, PDU sessions, and/or wireless devices by the UPF to measure/detect at least one service performance/QoS event. One or more methods may be taken to measure/detect service performance/QoS by UPF. In one exemplary method, the UPF monitors service performance/QoS between the UPF and the wireless device based on the Internet Control Message Protocol (ICMP) echo function. As an example, UPF may send a ping packet to the wireless device after receiving a response from the wireless device and calculate service performance/QoS values (eg, end-to-end latency, jitter). In one exemplary method, the UPF monitors service performance/QoS between the UPF and the (R)AN based on the ICMP echo function. As an example, the UPF may send a ping packet to the (R)AN after receiving a response from the (R)AN and calculate service performance/QoS values (e.g., end-to-end latency, jitter). . FIG. 15 is an exemplary call flow in which the UPF measures service performance/QoS with the ICMP echo function. In one exemplary method, the UPF queries service performance/QoS between the (R)AN and the wireless device. As an example, the UPF may send a signaling message to the (R)AN to inquire about service performance/QoS values between the (R)AN and the wireless device, the (R)AN and the wireless device, and send a response message containing the service performance/QoS values to the UPF. As an example, a user plane data packet containing an indication to query the service performance/QoS value between the (R)AN and the wireless device and/or the service performance/QoS value between the wireless device and the application server by the UPF (eg, in the header of the data packet) may be sent to the (R)AN. The (R)AN may measure/detect performance/QoS values between the (R)AN and the wireless device and/or the (R)AN may instruct the wireless device to may be requested to measure service performance/QoS values between The (R)AN may send user plane data packets (eg, in the header of the data packet) containing the measured service performance/QoS values to the UPF. In one exemplary method, the UPF monitors service performance/QoS between the UPF and the application server based on the Internet Control Message Protocol (ICMP) echo function. As an example, UPF may send a ping packet to an application server after receiving a response from the wireless device and calculate service performance/QoS values (eg, end-to-end latency, jitter). In an exemplary action, at least one service performance/QoS event is triggered for at least one of a service data flow, service/application, PDU session, and wireless device (e.g., service performance/QoS When detected by the UPF that the value has changed and/or is below a threshold (e.g., required service performance/QoS), the UPF sends a message (e.g., service performance/QoS measurement report) to the SMF. do. A message sent from the UPF to the SMF may contain one or more information elements. In one example, the message includes a first information element indicating a service performance/QoS event trigger. In one example, the message sent from the UPF to the SMF includes a second information element indicating the measured service performance/QoS value, and using the measured service performance/QoS value, one or more parameters may indicate service performance/QoS measured by a network function (eg, UPF), which may include: In one example, the second information element may include a parameter indicating service performance/QoS value type, which may be used to indicate the type or range of service performance/QoS. As an example, this parameter can be of the following types: service performance/QoS value between UPF and wireless device (e.g., end-to-end latency); service performance/QoS value between UPF and (R)AN ( end-to-end latency), service performance/QoS value between (R)AN and wireless device (e.g., end-to-end latency), service performance/QoS value between UPF and application server (e.g., , end-to-end latency), service performance/QoS values (eg, end-to-end latency) between the UE and the application server. In one example, the second information element may include a parameter indicative of measured end-to-end latency. In one example, the second information element may include a parameter indicative of the measured jitter. In one example, the second information element may include a parameter indicative of measured survival time. In one example, the second information element may include a parameter indicative of the measured communication service availability. In one example, the second information element may include a parameter indicative of measured reliability. In one example, the second information element may include a parameter indicative of the measured user experience data rate. In one example, a message sent from UPF to SMF includes a third information element indicating a service data flow template. In one example, a message sent from UPF to SMF includes a fourth information element indicating a service/application identifier. In one example, a message sent from UPF to SMF includes a fifth information element indicating a PDU session identifier. In one example, the message sent from UPF to SMF includes a sixth information element indicating the user identity of the wireless device.

In response to the message received from the UPF, the SMF may send a message (eg, Service Performance/QoS Measurement Report) containing the information received from the UPF to the VPCF. In response to messages received from SMF, the VPCF may send messages (eg, service performance/QoS measurement reports) to HPCF that include information received from SMF. In response to the message received from the VPCF, the HPCF may send a message (eg, service performance/QoS measurement report) to the HAF or HNEF including the information received from the VPCF. When the HNEF receives messages from HPCF (eg service performance/QoS measurement reports), the HNEF may forward the messages to the HAF.

In response to a message received from HPCF or HNEF, and in response based on information received from HPCF or HNEF (e.g., event triggers of service performance/QoS values and/or measured service performance/QoS values) , HAF can adjust the service behavior timely. As an example, the HAF may change the video codec rate based on the measured service performance/QoS value (e.g., the current service performance of the communication system supports 8K Ultra High Definition (UHD) video). may not be possible, video codec rate may be changed to 4K UHD). Messages for application information changes (eg, provisioning of application/service information) may be sent by the HAF to the HPCF. As an example, with HAF, any part of the delay (e.g., wireless device to access network, access network to core network, or core network to application server) causes long end-to-end delay between application server and wireless device. You may analyze whether it may be the cause. As an example, the HAF may determine that the end-to-end delay may be caused by the delay between the core network and the application server, and the HAF determines that the delay between the core network (e.g., UPF) and the application server A message (eg, HTTP PUT) indicating the change in route policy may be sent to the HPCF. The HPCF may send a policy to the VPCF that selects a better route with a shorter delay between the UPF and the application server compared to the current end-to-end delay, and the VPCF sends the received policy to the SMF. It may be forwarded and sent by the SMF to the policy to the UPF for enforcement.

Example 6
In one example, the application server (e.g., HAF), HPCF, and/or HNEF may reside in the home network, and the VPCF, SMF, UPF, (R)AN, and/or wireless devices may reside in the visited network. may be in A first message may be sent by the HAF to a network node (eg, HPCF or HNEF). The first message may indicate a request for at least one service performance/QoS report for a service data flow, service/application, PDU session, and/or wireless device. FIG. 18 shows an exemplary call flow that may include one or more actions.

A network function (e.g., HPCF or HNEF ) (eg requesting service performance/QoS reports or provisioning application/service information). A message may contain one or more information elements. In one example, the message includes a first information element including a service performance/QoS report indication, which indicates the following parameters for service performance/QoS: end-to-end latency, jitter, time to live, communication service availability , reliability, and user experience data rate. As an example, a network function (eg, UPF) may measure the current values of service performance/QoS parameters upon receiving a service performance/QoS report indication. In one example, the message includes a second information element indicating a service data flow template. In one example, the message includes a third information element indicating a service/application identifier. In one example, the message includes a fourth information element indicating a PDU session identifier. In one example, the message includes a fifth information element indicating the user identification of the wireless device. When the HAF sends a message above to the HNEF (eg requesting service performance/QoS reports or provisioning application/service information), the message may be forwarded by the HNEF to the HPCF, as an example.

One or more actions may be taken by the HPCF in response to messages received from the HAF or HNEF. In an exemplary action, HPCF makes policy decisions based on information received from HAF or HNEF. In an exemplary action, the HPCF sends a message (eg, Request Service Performance/QoS Report) to the VPCF to request at least one current Service Performance/QoS Report. The message may contain information received from the HAF or HNEF. As an example, messages sent to the VPCF may include information (eg, service performance/QoS report indications) and/or policies (eg, QoS policies) received from the HAF or HNEF. As an example, messages sent to the VPCF may include policies (eg, QoS policies), and policies may include information received from HAF or HNEF (eg, service performance/QoS report indications).

One or more of the actions may be taken by the VPCF in response to messages received from the HPCF. In an exemplary action, the VPCF makes policy decisions based on information received from the HPCF; , VPCF may differ from the policy received from HPCF. In an exemplary action, the VPCF sends a message (eg, Request Service Performance/QoS Report) to the SMF to request at least one current Service Performance/QoS Report. The message may contain information received from the HPCF. As an example, messages sent to the SMF may include information received from the HPCF (eg, service performance/QoS report indications) and/or policies (eg, QoS policies). As an example, a message sent to SMF may include a policy (eg, QoS policy), and the policy may include information received from HPCF (eg, service performance/QoS report indication).

Send a message (e.g., Request for Service Performance/QoS Report or Request for N4 Session Establishment/Modification) to UPF by SMF in response to the message received from VPCF to request the current Service Performance/QoS Report. and/or a policy (eg, QoS policy) may be provisioned. The message may contain information received from the VPCF. As an example, messages sent to the UPF may include information received from the VPCF (eg, service performance/QoS report indications) and/or policies (eg, QoS policies). As an example, a message sent to the UPF may include a policy (eg, QoS policy), and the policy may include information received from the VPCF (eg, service performance/QoS report indication).

One or more actions may be taken by the UPF in response to messages received from the SMF. In an exemplary action, the UPF monitors service data flows, services/applications, PDU sessions, and/or service performance/QoS of the wireless device to measure/detect at least one service performance/QoS event. One or more methods may be taken to measure/detect service performance/QoS by UPF. In one exemplary method, the UPF monitors service performance/QoS between the UPF and the wireless device based on the Internet Control Message Protocol (ICMP) echo function. As an example, UPF may send a ping packet to the wireless device after receiving a response from the wireless device and calculate service performance/QoS values (eg, end-to-end latency, jitter). In one exemplary method, the UPF monitors service performance/QoS between the UPF and the (R)AN based on the ICMP echo function. As an example, the UPF may send a ping packet to the (R)AN after receiving a response from the (R)AN and calculate service performance/QoS values (e.g., end-to-end latency, jitter). . In one exemplary method, the UPF queries service performance/QoS between the (R)AN and the wireless device. As an example, the UPF may send a signaling message to the (R)AN to inquire about service performance/QoS values between the (R)AN and the wireless device, the (R)AN and the wireless device, and send a response message containing the service performance/QoS values to the UPF. As an example, send user plane data packets containing indications (e.g., in the header of the data packet) to the (R)AN over the UPF to provide service performance/performance between the (R)AN and the wireless device. QoS values may be queried, and the (R)AN measures/detects performance/QoS values between the (R)AN and the wireless device and sends user plane data packets ( for example, in the header of the data packet) may be sent. In an exemplary action, the UPF may send a report message (e.g., service performance/QoS measurement report, or N4 session establishment/modification response) to the SMF, where the report message contains one or more information elements. may contain. In one example, the report message includes a first information element indicating the measured service performance/QoS value. A first information element may be used to indicate a measured service performance/QoS, which may include one or more parameters. In one example, the first information element includes a parameter indicating service performance/QoS value type, which may be used to indicate the type or range of service performance/QoS. As an example, this parameter can be of the following types: service performance/QoS value between UPF and wireless device (e.g., end-to-end latency); service performance/QoS value between UPF and (R)AN ( end-to-end latency), service performance/QoS value between (R)AN and wireless device (e.g., end-to-end latency), service performance/QoS value between UPF and application server (e.g., , end-to-end latency), and service performance/QoS values (eg, end-to-end latency) between the UE and the application server. In one example, the first information element includes a parameter indicative of measured end-to-end latency. In one example, the first information element includes a parameter indicative of measured jitter. In one example, the first information element includes a parameter indicative of measured survival time. In one example, the first information element includes a parameter indicative of the measured communication service availability. In one example, the first information element includes a parameter indicative of measured reliability. In one example, the first information element includes a parameter indicative of the measured user experience data rate. In one example, the report message includes a second information element indicating a service data flow template. In one example, the report message includes a third information element indicating the service/application identifier. In one example, the report message includes a fourth information element indicating a PDU session identifier. In one example, the report message includes a fifth information element indicating the user identification of the wireless device.

In response to the message received from the UPF, the SMF may send a message (eg, Service Performance/QoS Measurement Report) containing the information received from the UPF to the VPCF. In response to messages received from SMF, the VPCF may send messages (eg, service performance/QoS measurement reports) to HPCF that include information received from SMF. In response to the message received from the VPCF, the HPCF may send a message (eg, service performance/QoS measurement report) to the HAF or HNEF including the information received from the VPCF. When the HNEF receives messages from HPCF (eg service performance/QoS measurement reports), the HNEF may forward the messages to the HAF.

In response to messages received from HPCF or HNEF, service behavior may be adjusted by the HAF in a timely manner based on information (eg, measured service performance/QoS values) received from HPCF or HNEF accordingly. As an example, the AF may change the codec rate of the video based on the measured service performance/QoS value (e.g., the current service performance of the communication system supports 8K Ultra High Definition (UHD) video). may not be possible, you may change the video codec rate to 4K UHD). Messages for application information changes (eg, provisioning of application/service information) may be sent by the AF to the PCF. As an example, HAF allows any portion of the delay (e.g., wireless device to access network, access network to core network, or core network to application server) to introduce a long end-to-end delay between the application server and wireless device. It may be analyzed to see if it could be the cause. As an example, the HAF may determine that the end-to-end delay may be caused by the delay between the core network and the application server, and the HAF determines that the delay between the core network (e.g., UPF) and the application server A message (eg, HTTP PUT) indicating the change in route policy may be sent to the HPCF. The HPCF may send a policy to the VPCF that selects a better route with a shorter delay between the UPF and the application server compared to the current end-to-end delay, and the VPCF sends the received policy to the SMF. It may be forwarded and sent by the SMF to the policy to the UPF for enforcement.

In one example, the Home PCF (HPCF) sends a first message indicating a request to subscribe to at least one service performance/QoS event for service data flows, services/applications, PDU sessions, and/or wireless devices. may be received from the home AF (HAF), the first message including at least one first information element (IE) indicating at least one service performance/QoS event, a first end-to-end a service performance/QoS value including at least one of latency, a first jitter, a first time to live, a first communication service availability, a first confidence value, or a first user experience data rate; at least one second IE indicating a service data flow template; at least one third IE indicating a service/application first identifier; at least one fourth IE indicating a service/application first identifier; At least one fifth IE indicating an identifier or at least one of at least one of the six IEs indicating a user identity of the wireless device.

In one example, in response to the first message, the HPCF may send a second message to the visited PCF (VPCF) indicating a request to subscribe to at least one service performance/QoS event. . In one example, the HPCF may receive a response message to the second message from the VPCF. In one example, the HPCF may send a response message to the first message to the HAF.

In one example, when at least one service performance/QoS event is triggered by the HPCF for one of a service data flow, a service/application, a PDU session, and a wireless device, the service performance/QoS report message is a second end-to-end latency, a second jitter, a second time-to-live, a second communication service availability, a second At least one service performance/QoS value including at least one of reliability or a second user experience data rate.

In one example, the HPCF may send a third message to the HAF that includes at least one service performance/QoS value. In one example, in response to the third message, the HPCF may receive a fourth message from the HAF containing updated application parameters.

According to various embodiments, one or more devices such as, for example, wireless devices, off-network wireless devices, base stations, core network devices, and/or the like may be employed in the system. One or more of the devices may be defined by software, firmware, hardware, or combinations thereof installed on one or more of the devices and causing one or more of the devices to perform actions in operation. may be configured to perform the operations or actions of One or more computer programs, when executed by a data processing device, can be configured to perform certain operations or actions by including instructions that cause the device to perform an action. Exemplary action embodiments are illustrated in the accompanying drawings and specification. Features from various embodiments can be combined to create further embodiments.

Figure 19 is a flow diagram of one aspect of an embodiment of the present disclosure. At 1910, a first message may be received from a session management function by a user plane function. The first message may request at least one quality of service (QoS) report for the wireless device's data flow. The first message may include a first information element indicating a QoS event. The first message may contain a second information element indicating a latency value for the QoS event. At 1920, a user plane function may send a monitoring packet to the wireless device to monitor packet transmission latency of the data flow. At 1930, occurrence of a QoS event may be determined by user plane functions based on packet transmission latencies and latency values for data flows. At 1940, a second message may be sent by the user plane function to the session management function and may include a third information element indicating the occurrence of a QoS event for the data flow.

According to an exemplary embodiment, the session management function may receive the third message from the policy control function. A third message may request to subscribe to QoS events for the data flow. The third message may contain a third information element indicating the QoS event. The third message may include a fourth information element indicating that the QoS value may include end-to-end latency. According to an exemplary embodiment, the fourth information element may contain jitter. According to one exemplary embodiment, the fourth information element may include time to live. According to one exemplary embodiment, the fourth information element may include communication service availability. According to one exemplary embodiment, the fourth information element may contain a confidence value. According to one exemplary embodiment, the fourth information element may include user experience data rate.

According to an exemplary embodiment, the third message may include a fifth information element indicating a service data flow template. According to an exemplary embodiment, the third message may include a sixth information element indicating the identifier of the service/application. According to an exemplary embodiment, the third message may include a seventh information element indicating the identifier of the PDU session. According to one exemplary embodiment, the third message may include an eighth information element indicating the user identification of the wireless device. According to an exemplary embodiment, the third message may include sending, by the session management function, a fourth message in response to the third message to the policy control function.

According to an exemplary embodiment, a policy control function may receive a fifth message from an application function. A fifth message may request to subscribe to QoS events for the data flow. A fifth message may include a fifth information element indicating a QoS event. The fifth message may include a sixth information element indicating QoS values including end-to-end latency.

According to an exemplary embodiment, the sixth information element may contain jitter. According to one exemplary embodiment, the sixth information element may include time to live. According to an exemplary embodiment, the sixth information element may include communication service availability. According to an exemplary embodiment, the sixth information element may contain a confidence value. According to an exemplary embodiment, the sixth information element may include user experience data rate. According to an exemplary embodiment, the fifth message may contain a seventh information element indicating a service data flow template. According to an exemplary embodiment, the fifth message may include an eighth information element indicating the identifier of the service/application. According to an exemplary embodiment, the fifth message may include a ninth information element indicating the identifier of the PDU session. According to one exemplary embodiment, the fifth message may include a tenth information element indicating the user identification of the wireless device. According to an exemplary embodiment, a sixth message in response to the fifth message may be sent to the application function by the policy control function.

According to an exemplary embodiment, the second information element may further include the first value of jitter. According to an exemplary embodiment, a user plane function may monitor and measure the second value of jitter. According to an exemplary embodiment, a user plane function may determine the occurrence of a QoS event based on the first value and the second value. According to an exemplary embodiment, the second information element may further comprise a first value of time to live. According to an exemplary embodiment, a user plane function may monitor and measure the second value of time to live. According to an exemplary embodiment, a user plane function may determine the occurrence of a QoS event based on the first value and the second value. According to an exemplary embodiment, the second information element may include a first value of communication service availability.

According to an exemplary embodiment, a user plane function may monitor and measure a second value of communication service availability. According to an exemplary embodiment, a user plane function may determine the occurrence of a QoS event based on the first value and the second value.

According to one exemplary embodiment, the second information element may further include the first value of the confidence value. According to an exemplary embodiment, the user plane functionality may monitor and measure the second value of the confidence value. According to an exemplary embodiment, a user plane function may determine the occurrence of a QoS event based on the first value and the second value.

According to an exemplary embodiment, the second information element may further include a first value of user experience data rate. According to an exemplary embodiment, a user plane function may monitor and measure a second value of the user experience data rate. According to an exemplary embodiment, a user plane function may determine the occurrence of a QoS event based on the first value and the second value.

According to an exemplary embodiment, the second message may contain a fourth information element indicating a latency value for the QoS event. According to an exemplary embodiment, the fourth information element may contain the jitter value for the QoS event. According to an exemplary embodiment, the fourth information element may contain a time-to-live value for the QoS event. According to an exemplary embodiment, the fourth information element may include a communication service availability value for the QoS event. According to an exemplary embodiment, the fourth information element may contain a confidence value for the QoS event. According to one exemplary embodiment, a fourth information element may include a user experience data rate value for the QoS event. According to an exemplary embodiment, the session management function may send a third message including a third information element and a fourth information element to the policy control function. According to an exemplary embodiment, the policy control function may send a fourth message including a third information element and a fourth information element to the application function. According to an exemplary embodiment, an application function may adjust service behavior based on the fourth message. According to an exemplary embodiment, packet transmission latency for data flows may be between user plane functions and wireless devices. According to an exemplary embodiment, a user plane function may monitor packet transmission latency between the user plane function and the base station by sending monitoring packets to the base station.

According to an exemplary embodiment, a user plane function may query packet transmission latency between a base station and a wireless device by sending a monitor packet to the base station. According to an exemplary embodiment, a user plane function may monitor packet transmission latency between the user plane function and the application server by sending monitoring packets to the application server.

According to an exemplary embodiment, the user plane function may receive the third message from the session management function. The third message may subscribe to at least one quality of service (QoS) event for the data flow. The third message may contain an information element indicating the QoS event. The third message includes an information element indicating that the QoS value may include at least one of end-to-end latency, jitter, time to live, communication service availability, reliability value, or user experience data rate. may contain. According to an exemplary embodiment, the information element indicates a service data flow template. According to an exemplary embodiment, the information element indicates a service/application identifier. According to an exemplary embodiment, the information element indicates a PDU session identifier. According to one exemplary embodiment, the information element indicates a user identity of the wireless device.

According to an exemplary embodiment, the session management function may send a third message subscribing to at least one quality of service (QoS) event for the data flow to the access and mobility management function. The third message may contain a fourth information element indicating a QoS event. The third message may include a fifth information element indicating that the QoS value may include end-to-end latency. According to an exemplary embodiment, a fourth message may be sent to the base station by the access and mobility management function. The fourth message may contain at least one information element of the third message. According to an exemplary embodiment, the fifth information element may contain jitter. According to one exemplary embodiment, the fifth information element may include time to live. According to an exemplary embodiment, the fifth information element may include communication service availability. According to one exemplary embodiment, the fifth information element may contain a confidence value. According to an exemplary embodiment, the fifth information element may include user experience data rate. According to an exemplary embodiment, the third message may include a sixth information element indicating a service data flow template. According to an exemplary embodiment, the third message may include a seventh information element indicating the identifier of the service/application. According to an exemplary embodiment, the third message may include an eighth information element indicating the identifier of the PDU session. According to one exemplary embodiment, the third message may include a ninth information element indicating the user identification of the wireless device. According to an exemplary embodiment, a base station may transmit monitoring packets to monitor packet transmission latencies of data flows to wireless devices. According to one exemplary embodiment, the base station determines the occurrence of a QoS event based on packet transmission latency and end-to-end latency of the data flow. According to one exemplary embodiment, the base station may send a fifth message to the access and mobility management function in response to the determination. The fifth message may contain an information element indicating the occurrence of a QoS event and the packet transmission latency of the data flow. According to an exemplary embodiment, a sixth message may be sent by the access and mobility management function to the session management function. The sixth message may contain an information element indicating the occurrence of a QoS event and the packet transmission latency of the data flow. According to an exemplary embodiment, a user plane function may monitor packet transmission latency between the user plane function and the base station by sending monitoring packets to the base station. According to an exemplary embodiment, a user plane function may monitor packet transmission latency between a base station and a wireless device by sending monitoring packets to the wireless device.

Figure 20 is a flow diagram of one aspect of an embodiment of the present disclosure. At 2010, a first message may be received from a session management function by a user plane function. The first message may request at least one quality of service (QoS) report for the data flow. The first message may include a first information element indicating a QoS event. The first message may include a second information element indicating a first QoS value for the QoS event. At 2020, a user plane function may transmit a monitoring packet to monitor a second QoS value of the data flow to the wireless device. At 2030, occurrence of a QoS event may be determined by a user plane function based on the second QoS value and the first QoS value of the data flow. At 2040, a second message may be sent to the session management function by the user plane function in response to the determination. The second message may contain a third information element indicating the occurrence of a QoS event. According to an exemplary embodiment, the first QoS value and the second QoS value may include end-to-end latency. According to one exemplary embodiment, the first QoS value and the second QoS value may include jitter. According to one exemplary embodiment, the first QoS value and the second QoS value may include time to live. According to one exemplary embodiment, the first QoS value and the second QoS value may include communication service availability. According to one exemplary embodiment, the first QoS value and the second QoS value may include confidence values. According to an exemplary embodiment, the first QoS value and the second QoS value may include user experience data rates.

Figure 21 is a flow diagram of one aspect of an embodiment of the present disclosure; At 2110, a first message may be received from a session management function by a user plane function. The first message may request at least one quality of service (QoS) report for the data flow of the packet data unit session. The first message may include a first information element indicating a QoS event. The first message may contain a second information element indicating a latency value for the QoS event. At 2120, the user plane function may transmit the supervisory packet to the wireless device. The monitor packet may be for monitoring packet transmission latency of the data flow. At 2130, occurrence of a QoS event may be determined by a user plane function based on the data flow's packet transmission latency and the latency value. At 2140, a second message may be sent to the session management function by the user plane function in response to the determination. The second message may contain a third information element indicating the occurrence of a QoS event.

Figure 22 is a flow diagram of one aspect of an embodiment of the present disclosure; At 2210, a first message may be received from an application function by a home policy control function (HPCF). The first message may request to subscribe to quality of service (QoS) events for the wireless device's data flow. The first message may include a first information element indicating a first QoS event. The first message may include a second information element indicating a first QoS value for the first QoS event. At 2220, the HPCF may determine a QoS reporting policy for the data flow based on the first QoS event and the first QoS value. The QoS reporting policy may include a second QoS event and a second QoS value. At 2230, a second message may be sent by the HPCF to the visited policy control function (VPCF). The second message may contain the QoS reporting policy. At 2240, the HPCF may receive the measurement results from the VPCF. The measurement result may include a third information element indicating the occurrence of a second QoS event. The measurement result may include a fourth information element indicating the measured QoS value. At 2250, the HPCF may send the measurement results to the application function.

According to one exemplary embodiment, occurrence of a second QoS event may be determined based on the measured QoS value and the second QoS value. According to one exemplary embodiment, the first QoS value may include end-to-end latency. According to one exemplary embodiment, the first QoS value may include jitter. According to an exemplary embodiment, the first QoS value may include time to live. According to one exemplary embodiment, the first QoS value may include the availability of communication services. According to one exemplary embodiment, the first QoS value may include a confidence value. According to one exemplary embodiment, the first QoS value may include a user experience data rate. According to one exemplary embodiment, the second QoS value may include end-to-end latency. According to one exemplary embodiment, the second QoS value may include jitter. According to one exemplary embodiment, the second QoS value may include time to live. According to one exemplary embodiment, the second QoS value may include the availability of communication services. According to one exemplary embodiment, the second QoS value may include a confidence value. According to one exemplary embodiment, the second QoS value may include the user experience data rate. According to one exemplary embodiment, the measured QoS values may include end-to-end latency. According to an exemplary embodiment, the measured QoS values may include jitter. According to one exemplary embodiment, the measured QoS values may include time to live. According to an exemplary embodiment, the measured QoS values may include communication service availability. According to an exemplary embodiment, the measured QoS values may include confidence values. According to an exemplary embodiment, the measured QoS values may include user experience data rates.

According to an exemplary embodiment, a visited session management function may receive a third message from a visited policy control function. A third message may request to subscribe to QoS events for the data flow. The third message may contain an information element indicating the second QoS event. The third message may contain an information element indicating the second QoS value. The second QoS value may include end-to-end latency. The second QoS value may include jitter. The second QoS value may include time to live. The second QoS value may include the availability of communication services. The second QoS value may include a confidence value. A second QoS value may include a user-experienced data rate. The third message may contain an information element indicating a service data flow template. The third message may contain an information element indicating the identifier of the service/application. The third message may contain an information element indicating the identifier of the PDU session. The third message may include an information element indicating user identification of the wireless device. A fourth message may be sent to the visited policy control function by the visited session management function in response to the third message.

According to an exemplary embodiment, the visited user plane function may receive the fifth message from the visited session management function. A fifth message may request to subscribe to QoS events for the data flow. A fifth message may include a first information element indicating a second QoS event. The fifth message may include a second information element indicating a second QoS value. A visited user plane function may transmit to the wireless device a monitoring packet for monitoring the second QoS value of the data flow. A visiting user plane function may determine the occurrence of a QoS event based on the second QoS value of the data flow and the measured QoS value. A sixth message may be sent by the visited user plane function to the visited session management function. A sixth message may include a third information element indicating the occurrence of a QoS event. A sixth message may include a fourth information element indicating the measured QoS value. According to an exemplary embodiment, a seventh message may be sent by the visited session management function to the visited policy control function. The seventh message may contain the third information element and the fourth information element.

According to an exemplary embodiment, the first message may contain an information element indicating a service data flow template. According to an exemplary embodiment, the first message may contain an information element indicating the identifier of the service/application. According to an exemplary embodiment, the first message may include an information element indicating the identifier of the PDU session. According to one exemplary embodiment, the first message may include an information element indicating the user identity of the wireless device.

According to an exemplary embodiment, QoS reporting policies and measurements may include information elements that indicate service data flow templates. According to an exemplary embodiment, QoS reporting policies and measurements may include information elements that indicate service/application identifiers. According to an exemplary embodiment, QoS reporting policies and measurements may include information elements that indicate identifiers of PDU sessions. According to one exemplary embodiment, QoS reporting policies and measurements may include information elements that indicate user identities of wireless devices.

According to an exemplary embodiment, application functions may adjust service behavior based on measurements. According to an exemplary embodiment, a home policy control function (HPCF) may receive a third message from an application function querying a QoS event for the data flow. The third message may contain an information element indicating the first QoS event. The third message may include an information element indicating a first QoS value for the first QoS event. The first QoS value may include end-to-end latency. The first QoS value may include jitter. The first QoS value may include time to live. The first QoS value may include communication service availability. The first QoS value may include a confidence value. The first QoS value may include a user-experienced data rate. The third message may contain an information element indicating a service data flow template. The third message may contain an information element indicating the identifier of the service/application. The third message may contain an information element indicating the identifier of the PDU session. The third message may include an information element indicating user identification of the wireless device. According to an exemplary embodiment, the home policy control function may send a fourth message to the visited policy control function querying QoS events for the data flow. The fourth message may contain at least one of the information elements of the third message. According to an exemplary embodiment, the visited policy control function may send a fifth message to the visited session management function querying QoS events for the data flow. The fifth message may contain at least one of the information elements of the fourth message. According to an exemplary embodiment, a sixth message may be sent by the visited session management function to the visited user plane function querying QoS events for the data flow, the sixth message message information elements. According to an exemplary embodiment, a third QoS value may be measured by a visiting user plane function. A third QoS value may include end-to-end latency. The third QoS value may include jitter. A third QoS value may include time to live. A third QoS value may include the availability of communication services. A third QoS value may include a confidence value. A third QoS value may include a user-experienced data rate. A seventh message reporting a third QoS value may be sent by the visited user plane function to the visited session management function. According to an exemplary embodiment, an eighth message reporting a third QoS value may be sent by the visited session management function to the visited policy control function. According to an exemplary embodiment, a ninth message reporting a third QoS value may be sent by the visited policy control function to the home policy control function. According to an exemplary embodiment, a tenth message reporting a third QoS value may be sent by the home policy control function to the application function. According to an exemplary embodiment, an application function may adjust service behavior based on the third QoS value.

According to an exemplary embodiment, the visited QoS reporting policy may be determined by the visited policy control function based on the QoS reporting policy received from the home policy control function. A visited QoS reporting policy may include visited QoS events. A visited QoS reporting policy may include visited QoS values for visited QoS events. According to an exemplary embodiment, the third message, which may be sent by the visited policy control function to the visited session management function, may include the visited QoS reporting policy.

Figure 23 is a flow diagram of one aspect of an embodiment of the present disclosure. At 2310, a first message may be received by the visited policy control function from the home policy control function, subscribing to at least one quality of service (QoS) event for the data flow. The first message may include a first information element indicating a QoS event. The first message may include a second information element indicating a first QoS value for the QoS event. At 2320, a second message may be sent by the visited policy control function to the session management function. The second message may contain the first information element and the second information element. At 2330, a third message may be received from the session management function by the visited policy control function. The third message may contain a third information element indicating the QoS event. The third message may include a fourth information element indicating a second QoS value for the QoS event. At 2340, a fourth message may be sent by the visited policy control function to the home policy control function. A fourth message may include a third information element and a fourth information element.

In this disclosure, the terms "a" and "one" ("a" and "an") and similar phrases should be interpreted as "at least one" or "one or more." Similarly, any term ending in "" (suffix "(s)") should be interpreted as "at least one" or "one or more." In this disclosure, "may" and "may" (the term "may") should be interpreted as "may, for example." In other words, "may", "may" (the term "may") the preceding phrase may be used in one or more of the various embodiments, or It is alluded to as an example of one of many preferred possibilities that may not be used. A is called a subset of B if A and B are sets and each element of A is also an element of B. Only non-empty sets and subsets are considered here. For example, the possible subsets of B={cell 1, cell 2} are {cell 1}, {cell 2}, and {cell 1, cell 2}. The phrase "based on" is a multiple preference that the preceding phrase may or may not be used in one or more of the various embodiments. This implies that it is an example of one of the possibilities. The phrase "in response to" is used to indicate that the preceding phrase may or may not be used in one or more of the various embodiments. is one example of the preferred possibilities of The terms "including" and "comprising" are to be interpreted as meaning "including but not limited to."

In the present disclosure and claims, distinguishing terms such as "first," "second," and "third" do not imply order of elements or functionality of elements, but rather identify separate elements. Distinguishing terms may be replaced by other distinguishing terms when describing embodiments.

Various embodiments are disclosed in this disclosure. Limitations, features, and/or elements from the disclosed exemplary embodiments can be combined to create additional embodiments within the scope of the present disclosure.

In this disclosure, a parameter (information element: IE) may contain one or more objects, each of which may contain one or more other objects. For example, if parameter (IE)N includes parameter (IE)M, parameter (IE)M includes parameter (IE)K, and parameter (IE)K includes parameter (information element) J, for example, N is contains K and N contains J. In an exemplary embodiment, when the one or more messages include multiple parameters, a parameter in the multiple parameters is in at least one of the one or more messages, but one or more means that it does not have to be in each of the messages.

In addition, many of the features presented above are described as optional by the use of "may" or the use of parentheses. For the sake of brevity and readability, this disclosure does not explicitly list every possible permutation combination that can be obtained by selecting from a set of optional features. However, the present disclosure should be construed as explicitly disclosing all such permutations. For example, a system described as having three optional features can be described in seven different ways: only one of the three possible features, any two of the three possible features, or It can be implemented with all three of the three possible features.

Many of the elements described in the disclosed embodiments may be implemented as modules. Modules are defined herein as separable elements that perform defined functions and have defined interfaces to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (i.e., hardware with a biological component), or combinations thereof, all of which Behaviorally equivalent. For example, a module may be a software routine written in a computer language (such as C, C++, Fortran, Java, Basic, Matlab, or the like) configured to be executed by a hardware machine; Or it can be implemented as a modeling/simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript. Additionally, it may be possible to implement the modules using physical hardware that incorporates discrete or programmable analog, digital, and/or quantum hardware. Examples of programmable hardware include computers, microcontrollers, microprocessors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages such as assembly, C, C++, or the like. FPGAs, ASICs, and CPLDs use Hardware Description Languages (HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog, to make connections between internal hardware modules with less functionality on programmable devices. often programmed with Finally, it should be emphasized that the above techniques are often used in combination to achieve functional module results.

The disclosure of this patent document incorporates material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, for limited purposes required by law. , otherwise all rights reserved.

While various embodiments have been described above, it should be understood that they have been presented by way of example, not limitation. It will be apparent to those skilled in the art that various changes in form and detail may be made without departing from the scope. Indeed, after reading the above description, it will become apparent to a person skilled in the art how to implement alternative embodiments. Accordingly, the present embodiments should not be limited by any of the exemplary embodiments described above.

Further, it should be understood that any diagrams highlighting functionality and advantages are presented for illustrative purposes only. The disclosed architecture is sufficiently flexible and configurable so that it can be utilized in ways other than those shown. For example, in some embodiments, actions listed in any flowchart may be reordered or simply optionally used.

Furthermore, the purpose of the Abstract of the Disclosure is to provide an at-a-glance view of the application to the United States Patent and Trademark Office and to the general public, particularly scientists, engineers, and practitioners in the field who are unfamiliar with patents or legal terms or phrases. to enable a quick determination of the nature and essence of the technical disclosure of The Abstract of the Disclosure is not intended to be limiting in scope in any way.

Finally, it is Applicants' intent that only those claims containing the explicit words "means for" or "step for" be interpreted under 35 USC §112. . Any claim that does not explicitly contain the words "means for" or "step for" should not be construed under 35 USC §112.

Description of symbols 100 UE
105 NG-RAN, 3GPP Access, (R)AN
110 User plane functions UPF, UPF (CN_UP)
115 DNs
125 Network Publishing Facility NEF
130 NF Repository Function, NRF
135 Policy Control Function PCF
140 Integrated Data Management UDM
145 Application Function AF
150 AUSF
155 Access and Mobility Management Function AMF
160 session management function SMF
165 Non-3GPP AN, Non-3GPP Access 170 N3IWF
500 RM-Deregister 510 RM-Register 520 RM-Deregister 530 RM-Register 600 CM-Idle 610 CM-Connect 620 CM-Idle 630 CM-Connect 730 Application/Service Layer 1910 Step 1920 Step 1930 Step 1940 Step 2010 Step 2020 Step 2030 Step 2040 Step 2110 Step 2120 Step 2130 Step 2140 Step 2210 Step 2220 Step 2230 Step 2240 Step 2250 Step 2310 Step 2320 Step 2330 Step 2340 Step

Claims (80)

receiving, by a user plane function, from a session management function a first message requesting at least one quality of service (QoS) report for a data flow of a wireless device, the first message comprising:
a first information element indicating a QoS event;
a second information element indicating a latency value for said QoS event;
including
sending, by a user plane function, to the wireless device a monitoring packet for monitoring packet transmission latency of the data flow;
determining by the user plane function the occurrence of the QoS event based on the packet transmission latency and the latency value of the data flow;
sending by the user plane function to the session management function a second message comprising a third information element indicating the occurrence of the QoS event for the data flow;
method including. further comprising receiving, by said session management function, a third message from a policy control function requesting subscription to said QoS event for said data flow, said third message:
a third information element indicating the QoS event;
a fourth information element indicating a QoS value including end-to-end latency;
2. The method of claim 1, comprising: 3. The method of claim 2, wherein said fourth information element further comprises jitter. A method according to any of claims 2-3, wherein said fourth information element further comprises time to live. A method according to any of claims 2 to 4, wherein said fourth information element further comprises communication service availability. A method according to any of claims 2-5, wherein said fourth information element further comprises a confidence value. A method according to any of claims 2-6, wherein said fourth information element further comprises a user experience data rate. the third message further comprising:
a fifth information element indicating a service data flow template;
a sixth information element indicating a service/application identifier;
A method according to any of claims 2-7, comprising at least one of: a seventh information element indicating a PDU session identifier; or an eighth information element indicating a user identity of the wireless device. The method of any of claims 2-8, further comprising sending, by said session management function, to said policy control function a fourth message in response to said third message. further comprising receiving, by the policy control function, a fifth message from an application function requesting subscription to the QoS event for the data flow, the fifth message comprising:
a fifth information element indicating the QoS event;
a sixth information element indicating a QoS value including the end-to-end latency;
The method according to any one of claims 2 to 9, comprising 11. The method of claim 10, wherein said sixth information element further comprises jitter. A method according to any of claims 10-11, wherein said sixth information element further comprises time to live. A method according to any of claims 10-12, wherein said sixth information element further comprises communication service availability. A method according to any of claims 10-13, wherein said sixth information element further comprises a confidence value. A method according to any of claims 10-14, wherein said sixth information element further comprises a user experience data rate. The fifth message further comprising:
a seventh information element indicating a service data flow template;
an eighth information element indicating a service/application identifier;
A method according to any of claims 10-15, comprising at least one of: a ninth information element indicating a PDU session identifier; or a tenth information element indicating a user identity of the wireless device. A method according to any of claims 10-16, further comprising sending, by said policy control function, to said application function a sixth message in response to said fifth message. A method according to any preceding claim, wherein said second information element further comprises a first value of jitter. 19. The method of claim 18, further comprising monitoring and measuring the second value of jitter by a user plane function. 20. The method of claim 19, further comprising determining occurrence of the QoS event by the user plane function based on the first value and the second value. A method according to any preceding claim, wherein said second information element further comprises a first value of time to live. 22. The method of claim 21, further comprising monitoring and measuring the time-to-live second value by a user plane function. 23. The method of claim 22, further comprising determining occurrence of the QoS event by the user plane function based on the first value and the second value. A method according to any preceding claim, wherein said second information element further comprises a first value of communication service availability. 25. The method of claim 24, further comprising monitoring and measuring, by a user plane function, a second value of availability of said communication service. 26. The method of claim 25, further comprising determining occurrence of the QoS event by the user plane function based on the first value and the second value. A method according to any preceding claim, wherein said second information element further comprises a first value of confidence value. 28. The method of claim 27, further comprising monitoring and measuring a second value of said confidence value by a user plane function. 29. The method of claim 28, further comprising determining occurrence of the QoS event by the user plane function based on the first value and the second value. A method according to any preceding claim, wherein said second information element further comprises a first value of user experience data rate. 31. The method of claim 30, further comprising monitoring and measuring a second value of the user experience data rate by a user plane function. 32. The method of claim 31, further comprising determining occurrence of the QoS event by the user plane function based on the first value and the second value. A method according to any preceding claim, wherein said second message further comprises a fourth information element indicating said latency value for said QoS event. 34. The method of claim 33, wherein said fourth information element further comprises a jitter value for said QoS event. A method according to any of claims 33-34, wherein said fourth information element further comprises the time to live of said QoS event. A method according to any of claims 33 to 35, wherein said fourth information element further comprises communication service availability of said QoS event. A method according to any of claims 33-36, wherein said fourth information element further comprises a confidence value of said QoS event. A method according to any of claims 33-37, wherein said fourth information element further comprises a user experience data rate value for said QoS event. 39. The method according to any one of claims 33 to 38, further comprising sending, by said session management function, a third message comprising said third information element and said fourth information element to a policy control function. Method. 40. The method of claim 39, further comprising sending, by said policy control function, to an application function a fourth message comprising said third information element and said fourth information element. 41. The method of claim 40, further comprising adjusting service behavior by said application function based on said fourth message. A method according to any of claims 33-34, wherein said packet transmission latency of said data flow is between said user plane function and said wireless device. 43. The method according to any one of claims 1 to 42, further comprising monitoring, by said user plane function, packet transmission latency between said user plane function and a base station by sending a monitor packet to said base station. the method of. 44. The method of any preceding claim, further comprising querying, by the user plane function, packet transmission latency between a base station and the wireless device by sending a monitor packet to the base station. . 45. The method according to any one of claims 1 to 44, further comprising monitoring, by said user plane function, packet transmission latency between said user plane function and an application server by sending a monitoring packet to said application server. the method of. further comprising receiving, by said user plane function, from said session management function a third message subscribing to at least one quality of service (QoS) event for a data flow, said third message comprising:
an information element indicating the QoS event;
end-to-end latency,
jitter,
survival time,
the availability of telecommunications services;
an information element indicating a QoS value, including at least one of a confidence value or a user experience data rate;
an information element, indicating a template for the service data flow,
an information element indicating the identifier of the service/application;
46. The method of any preceding claim, comprising at least one of: an information element indicative of a PDU session identifier; or an information element indicative of a wireless device user identity. receiving, by said session management function, a third message subscribing to at least one quality of service (QoS) event for a data flow to an access and mobility management function, said third message comprising:
a fourth information element indicating said QoS event;
a fifth information element indicating a QoS value including end-to-end latency;
comprising at least one of
sending, by the access and mobility management function, to a base station a fourth message comprising at least one information element of the third message;
47. The method of any of claims 1-46, further comprising: 48. The method of claim 47, wherein said fifth information element further comprises jitter. 49. The method of any of claims 47-48, wherein said fifth information element further comprises time to live. 50. A method according to any of claims 47-49, wherein said fifth information element further comprises communication service availability. A method according to any of claims 47-50, wherein said fifth information element further comprises a confidence value. A method according to any of claims 47-51, wherein said fifth information element further comprises a user experience data rate. the third message further comprising:
a sixth information element indicating a service data flow template;
a seventh information element indicating a service/application identifier;
53. The method of any of claims 47-52, comprising at least one of: an eighth information element indicating a PDU session identifier; or a ninth information element indicating a wireless device user identity. transmitting by the base station to the wireless device a monitoring packet for monitoring packet transmission latency of the data flow;
determining, by the base station, occurrence of the QoS event based on the packet transmission latency and the end-to-end latency of the data flow;
Sending, by said base station, to said access and mobility management function, in response to said determination, a fifth message comprising an information element indicating said occurrence of said QoS event and said packet transmission latency of said data flow. and,
54. The method of any of claims 47-53, further comprising Further comprising sending, by the access and mobility management function, to the session management function a sixth message, the sixth message indicating the occurrence of the QoS event and the packet transmission latency of the data flow. , information elements. monitoring, by the user plane function, packet transmission latency between the user plane function and a base station by sending a monitor packet to the base station; or, by the user plane function, the base station and the wireless device by sending a monitor packet to the wireless device. receiving, by a user plane function, from a session management function a first message requesting at least one quality of service (QoS) report for a data flow, said first message comprising:
a first information element indicating a QoS event;
a second information element indicating a first QoS value for said QoS event;
including
sending, by a user plane function, to a wireless device a monitoring packet for monitoring a second QoS value of said data flow;
determining, by the user plane function, the occurrence of the QoS event based on the second QoS value and the first QoS value of the data flow;
sending, by the user plane function, to the session management function, in response to the determination, a second message including a third information element indicating the occurrence of the QoS event;
A method, including wherein the first QoS value and the second QoS value are
end-to-end latency,
jitter,
survival time,
the availability of telecommunications services;
58. The method of claim 57, comprising at least one of: a confidence value; or a user experience data rate. receiving, by a user plane function, from a session management function a first message requesting at least one quality of service (QoS) report for a data flow of a packet data unit session, said first message ,
a first information element indicating a QoS event;
a second information element indicating a latency value for said QoS event;
including
sending, by a user plane function, to a wireless device a monitoring packet for monitoring packet transmission latency of said data flow;
determining by the user plane function the occurrence of the QoS event based on the packet transmission latency and the latency value of the data flow;
sending, by the user plane function, to the session management function, in response to the determination, a second message including a third information element indicating the occurrence of the QoS event;
A method, including Receiving, by a home policy control function (HPCF), from an application function, a first message requesting subscription to quality of service (QoS) events for wireless device data flows, said first message teeth,
a first information element indicating a first QoS event;
a second information element indicating a first QoS value for the first QoS event;
including
determining, by the HPCF, a QoS reporting policy for the data flow based on the first QoS event and the first QoS value, the QoS reporting policy comprising a second QoS event and a second including the QoS value of
sending, by the HPCF, a second message to a visited policy control function (VPCF) including the QoS reporting policy;
a third information element indicating occurrence of the second QoS event;
a fourth information element indicating the measured QoS value;
receiving, by the HPCF, from the VPCF measurements comprising
sending the measurement results by the HPCF to the application function;
A method, including 61. The method of claim 60, wherein said occurrence of said second QoS event is determined based on said measured QoS value and said second QoS value. The first QoS value, the second QoS value, and the measured QoS value are
end-to-end latency,
jitter,
survival time,
the availability of telecommunications services;
62. The method of any of claims 60-61, comprising at least one of confidence value or user experience data rate. receiving, by a visited session management function, a third message from said visited policy control function requesting subscription to said QoS event for said data flow, said third message comprising:
an information element indicating said second QoS event;
an information element indicating the second QoS value, the second QoS value comprising:
end-to-end latency,
jitter,
survival time,
the availability of telecommunications services;
an information element containing at least one of a confidence value or a user experience data rate;
an information element, indicating a template for the service data flow,
an information element indicating the identifier of the service/application;
including at least one of: an information element indicating a PDU session identifier; or an information element indicating a user identity of the wireless device;
sending, by the visited session management function, to the visited policy control function a fourth message in response to the third message;
63. The method of any of claims 60-62, further comprising receiving, by a visited user plane function, a fifth message from said visited session management function requesting subscription to said QoS event for said data flow, said fifth message comprising:
a first information element indicating said second QoS event;
a second information element indicating the second QoS value;
sending, by a visited user plane function, to the wireless device a monitoring packet for monitoring a second QoS value of the data flow;
determining, by the visited user plane function, the occurrence of the QoS event based on the second QoS value and the measured QoS value of the data flow;
said third information element indicating said occurrence of said QoS event;
the fourth information element indicating the measured QoS value;
sending by the visited user plane function to the visited session management function a sixth message comprising:
64. The method of any of claims 60-63, further comprising 65. The claim of claim 64, further comprising sending, by said visited session management function, to said visited policy control function a seventh message comprising said third information element and said fourth information element. Method. The first message further comprising:
an information element, indicating a template for the service data flow,
an information element indicating the identifier of the service/application;
66. The method of any of claims 60-65, comprising at least one of: an information element indicating a PDU session identifier; or an information element indicating a user identity of the wireless device. The QoS reporting policy and the measurement result further:
an information element, indicating a template for the service data flow,
an information element indicating the identifier of the service/application;
67. The method of any of claims 60-66, comprising at least one of: an information element indicating a PDU session identifier; or an information element indicating a user identity of the wireless device. 68. The method of any of claims 60-67, further comprising adjusting, by said application function, service behavior based on said measurement results. further comprising receiving, by the home policy control function (HPCF), a third message from the application function inquiring about a QoS event for the data flow, the third message comprising:
an information element indicative of said first QoS event; and an information element indicative of said first QoS value for said first QoS event, said first QoS value comprising:
end-to-end latency,
jitter,
survival time,
the availability of telecommunications services;
an information element containing at least one of a confidence value or a user experience data rate;
an information element, indicating a template for the service data flow,
an information element indicating the identifier of the service/application;
62. The method of any of claims 60-61, comprising at least one of: an information element indicating a PDU session identifier; or an information element indicating a user identity of the wireless device. Sending, by the home policy control function, to the visited policy control function a fourth message querying the QoS event for the data flow, wherein the fourth message is the third message. 70. The method of claim 69, comprising at least one of information elements. further comprising, by the visited policy control function, sending to a visited session management function a fifth message querying the QoS event for the data flow, the fifth message being the result of the fourth message; 71. The method of claim 70, comprising at least one of information elements. further comprising sending, by the visited session management function, to a visited user plane function a sixth message querying the QoS event for the data flow, the sixth message being equal to the number of the fifth message; 72. The method of claim 71, comprising at least one of information elements. measuring, by the visited user plane function, a third QoS value, the third QoS value comprising:
end-to-end latency,
jitter,
survival time,
the availability of telecommunications services;
including at least one of a confidence value or a user experience data rate;
sending, by the visited user plane function, to the visited session management function a seventh message reporting the third QoS value;
73. The method of claim 72, further comprising: 74. The method of claim 73, further comprising sending, by the visited session management function, to the visited policy control function an eighth message reporting the third QoS value. 75. The method of claim 74, further comprising sending, by the visited policy control function, to the home policy control function a ninth message reporting the third QoS value. 76. The method of claim 75, further comprising sending, by the home policy control function, to the application function a tenth message reporting the third QoS value. 77. The method of claim 76, further comprising adjusting service behavior by the application function based on the third QoS value. determining, by the visited policy control function, a visited QoS reporting policy based on the QoS reporting policy received from the home policy control function, the visited QoS reporting policy comprising:
a visited QoS event;
a visited QoS value for the visited QoS event;
78. The method of any of claims 60-77, comprising 79. The method of claim 78, further comprising sending by the visited policy control function to a visited session management function a third message including the visited QoS reporting policy. receiving, by a visited policy control function, a first message subscribing to at least one quality of service (QoS) event for a data flow from a home policy control function, said first message comprising:
a first information element indicating a QoS event;
a second information element indicating a first QoS value for said QoS event;
including
sending by the visited policy control function to a session management function a second message comprising the first information element and the second information element;
a third information element indicating a QoS event;
a fourth information element indicating a second QoS value for said QoS event;
receiving, by the visited policy control function, from the session management function a third message comprising:
sending by the visited policy control function to the home policy control function a fourth message comprising the third information element and the fourth information element;
A method, including

Images