Quality of service measurement

Abstract

Embodiments of the present disclosure relate to quality of service (QoS) measurements. In an aspect, a first network device triggers at least one QoS measurement through at least one data network user plane interface of a communication network and at least one network node of a data network. The first network device also sends, to at least one second network device, a configuration comprising one or more measurement parameters for the at least one QoS measurement through the at least one data network user plane interface. In this way, a solution for triggering and measuring QoS metrics through at least N6 interface can be provided, and thus QoS metrics can be better monitored and used for controlled or assisted (edge) application server (AS or EAS) discovery or re-discovery.

Description

Technical Field

[0001] Various example embodiments generally relate to the field of communications, and more particularly to first network devices, second network devices, third network devices, fourth network devices, methods, apparatuses, and computer-readable storage media for quality of service (QoS) measurement. Background Technology

[0002] A communication network can be viewed as a facility that enables communication between two or more communication devices, or provides communication devices with access to a data network. Mobile or wireless communication networks are an example of communication networks. Such communication networks operate according to standards provided by organizations such as 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). An example of such a standard is the so-called 5G (fifth generation) standard provided by 3GPP.

[0003] Edge computing (EC) refers to technologies that process and analyze data at the edge of a network. Unlike cloud computing, edge computing places some or all computing tasks on devices closer to the data source, thereby reducing data transmission latency and enhancing the speed and efficiency of data processing. For a given Edge Data Network (EDN), during the Edge Application Server (EAS) deployment phase, the location and number of EAS instances deployed can be determined based on requirements from the Application Service Provider (ASP). The connection between the newly deployed EAS and the User Plane Function (UPF) used for a given EDN can be pre-configured via the management plane. Summary of the Invention

[0004] Typically, the exemplary embodiments of this disclosure provide a solution for QoS measurement, such as QoS measurement via the N6 interface. For example, the solution provided by the exemplary embodiments of this disclosure can trigger and measure QoS metrics via the N6 interface. Therefore, QoS metrics can be better monitored and used for the discovery or rediscovery of controlled or auxiliary (edge) application servers (AS or EAS).

[0005] In a first aspect, a first network device is provided. The first network device includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the first network device to at least: trigger at least one QoS measurement via at least one data network user plane interface of a communication network and at least one network node of the data network; and send a configuration including one or more measurement parameters to at least one second network device for at least one QoS measurement via the at least one data network user plane interface.

[0006] In a second aspect, a second network device is provided. The second network device includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the second network device to at least: receive from a first network device a configuration including one or more measurement parameters for at least one QoS measurement via at least one interface between the second network device and at least one network node of a data network; and perform at least one QoS measurement based on the configuration including the one or more measurement parameters.

[0007] In a third aspect, a third network device is provided. The third network device includes at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the third network device to at least: receive from a fourth network device information for triggering at least one QoS measurement via at least one data network user plane interface and at least one network node of the data network through a communication network, wherein the information for triggering the at least one QoS measurement includes at least one of one or more measurement requirements or one or more measurement auxiliary information; and send one or more measurement requirements or one or more measurement auxiliary information to at least one of a policy control function (PCF) or a first network device; or store one or more measurement requirements or one or more measurement auxiliary information in a unified data repository (UDR).

[0008] In a fourth aspect, a fourth network device is provided. The fourth network device includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the fourth network device to at least: send information to a third network device for triggering at least one QoS measurement via at least one data network user plane interface of a communication network and at least one network node of the data network, wherein the information for triggering the at least one QoS measurement includes at least one of one or more measurement requirements or one or more measurement auxiliary information.

[0009] In a fifth aspect, a method is provided. The method includes: triggering at a first network device at at least one QoS measurement via at least one data network user plane interface of a communication network and at least one network node of the data network; and sending to at least one second network device a configuration including one or more measurement parameters for at least one QoS measurement via at least one data network user plane interface.

[0010] In a sixth aspect, a method is provided. The method includes: receiving at a second network device a configuration from a first network device including one or more measurement parameters for at least one QoS measurement via at least one interface between the second network device and at least one network node of a data network; and performing at least one QoS measurement based on the configuration including the one or more measurement parameters.

[0011] In a seventh aspect, a method is provided. The method includes: receiving, at a third network device, information from a fourth network device for triggering at least one QoS measurement via at least one data network user plane interface and at least one network node of the data network through a communication network, wherein the information for triggering the at least one QoS measurement includes at least one of one or more measurement requirements or one or more measurement auxiliary information; and sending one or more measurement requirements or one or more measurement auxiliary information to at least one of the PCF or a first network device; or storing one or more measurement requirements or one or more measurement auxiliary information in a unified data repository (UDR).

[0012] In an eighth aspect, a method is provided. The method includes: sending information from a fourth network device to a third network device for triggering at least one QoS measurement via at least one data network user plane interface of a communication network and at least one network node of the data network, wherein the information for triggering the at least one QoS measurement includes at least one of one or more measurement requirements or one or more measurement auxiliary information.

[0013] In a ninth aspect, an apparatus is provided. The apparatus includes: components for triggering at least one QoS measurement via at least one data network user plane interface of a communication network and at least one network node of the data network; and components for transmitting a configuration including one or more measurement parameters to at least one second network device for at least one QoS measurement via the at least one data network user plane interface.

[0014] In a tenth aspect, an apparatus is provided. The apparatus includes: components for receiving from a first network device a configuration including one or more measurement parameters, wherein the one or more measurement parameters are used for at least one QoS measurement via at least one interface between a second network device and at least one network node of a data network; and components for performing at least one QoS measurement based on the configuration including the one or more measurement parameters.

[0015] In an eleventh aspect, an apparatus is provided. The apparatus includes: components for receiving from a fourth network device information for triggering at least one QoS measurement via at least one data network user plane interface and at least one network node of the data network through a communication network, wherein the information for triggering the at least one QoS measurement includes at least one of one or more measurement requirements or one or more measurement auxiliary information; components for sending the one or more measurement requirements or one or more measurement auxiliary information to at least one of the PCF or a first network device; and components for storing the one or more measurement requirements or one or more measurement auxiliary information in a UDR.

[0016] In a twelfth aspect, an apparatus is provided. The apparatus includes: components for transmitting information to a third network device for triggering at least one QoS measurement via at least one data network user plane interface of a communication network and at least one network node of the data network, wherein the information for triggering the at least one QoS measurement includes at least one of one or more measurement requirements or one or more measurement auxiliary information.

[0017] In a thirteenth aspect, a non-transitory computer-readable medium is provided, the non-transitory computer-readable medium comprising program instructions for causing an apparatus to perform a method according to at least any one of the fifth to eighth aspects.

[0018] In a fourteenth aspect, a computer program is provided, the computer program including instructions that, when executed by a device, cause the device to at least: trigger at least one QoS measurement via at least one data network user plane interface of a communication network and at least one network node of the data network; and send a configuration including one or more measurement parameters to at least one second network device for at least one QoS measurement via at least one data network user plane interface.

[0019] In a fifteenth aspect, a computer program is provided, the computer program including instructions that, when executed by an apparatus, cause the apparatus to at least: receive from a first network device a configuration including one or more measurement parameters for at least one QoS measurement via at least one interface between a second network device and at least one network node of a data network; and perform at least one QoS measurement based on the configuration including the one or more measurement parameters.

[0020] In a sixteenth aspect, a computer program is provided, the computer program including instructions that, when executed by an apparatus, cause the apparatus to at least: receive from a fourth network device information for triggering at least one QoS measurement through at least one data network user plane interface and at least one network node of the data network, wherein the information for triggering the at least one QoS measurement includes at least one of one or more measurement requirements or one or more measurement auxiliary information; send one or more measurement requirements or one or more measurement auxiliary information to at least one of the PCF or a first network device; or store one or more measurement requirements or one or more measurement auxiliary information in a UDR.

[0021] In a seventeenth aspect, a computer program is provided, the computer program including instructions that, when executed by an apparatus, cause the apparatus to at least: send information to a third network device for triggering at least one QoS measurement through at least one data network user plane interface of a communication network and at least one network node of the data network, wherein the information for triggering the at least one QoS measurement includes at least one of one or more measurement requirements or one or more measurement auxiliary information.

[0022] In an eighteenth aspect, a first network device is provided. The first network device includes a triggering circuit system configured to trigger at least one QoS measurement via at least one data network user plane interface of a communication network and at least one network node of the data network; and a transmitting circuit system configured to transmit a configuration including one or more measurement parameters to at least one second network device for at least one QoS measurement via at least one data network user plane interface.

[0023] In a nineteenth aspect, a second network device is provided. The second network device includes a receiving circuitry configured to receive from a first network device a configuration including one or more measurement parameters for at least one QoS measurement via at least one interface between the second network device and at least one network node of a data network; and an execution circuitry configured to perform at least one QoS measurement based on the configuration including the one or more measurement parameters.

[0024] In a twentieth aspect, a third network device is provided. The third network device includes a receiving circuit system configured to receive from a fourth network device information for triggering at least one QoS measurement via at least one data network user plane interface and at least one network node of the data network, wherein the information for triggering the at least one QoS measurement includes at least one of one or more measurement requirements or one or more measurement auxiliary information; a transmitting circuit system configured to transmit one or more measurement requirements or one or more measurement auxiliary information to at least one of the PCF or a first network device; or a storage circuit system configured to store one or more measurement requirements or one or more measurement auxiliary information in a UDR.

[0025] In a twenty-first aspect, a fourth network device is provided. The fourth network device includes a transmission circuit system configured to send information to a third network device for triggering at least one QoS measurement via at least one data network user plane interface of a communication network and at least one network node of the data network, wherein the information for triggering the at least one QoS measurement includes at least one of one or more measurement requirements or one or more measurement auxiliary information.

[0026] It should be understood that the summary section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to be used to limit the scope of this disclosure. Other features of this disclosure will become apparent from the following description. Attached Figure Description

[0027] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which:

[0028] Figure 1A The illustration shows an example network environment in which exemplary embodiments of this disclosure may be implemented;

[0029] Figure 1B The illustrations illustrate exemplary conceptual principles according to some exemplary embodiments of the present disclosure;

[0030] Figure 1C The illustrations depict example measurement scenarios according to some exemplary embodiments of the present disclosure;

[0031] Figure 1D The illustration shows another example measurement scenario according to some example embodiments of the present disclosure;

[0032] Figure 2A The illustration shows an example signaling process for QoS measurement according to some example embodiments of the present disclosure;

[0033] Figure 2B The illustration shows another example signaling process for QoS measurement according to some example embodiments of this disclosure;

[0034] Figure 3 The illustration shows an example signaling process for a measurement triggered from an application function (AF) according to some example embodiments of the present disclosure;

[0035] Figure 4 The illustration shows an example flowchart of a QoS measurement process at a first network device according to some example embodiments of the present disclosure;

[0036] Figure 5 The illustration shows an example flowchart of a QoS measurement process at a second network device according to some example embodiments of the present disclosure;

[0037] Figure 6 The illustration shows an example flowchart of a QoS measurement process at a third network device according to some example embodiments of the present disclosure;

[0038] Figure 7 The illustration shows an example flowchart of a QoS measurement process at a fourth network device according to some example embodiments of the present disclosure;

[0039] Figure 8 The illustration shows an example simplified block diagram of a device suitable for implementing embodiments of the present disclosure; and

[0040] Figure 9 An example block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is illustrated.

[0041] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0042] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. This disclosure described herein can be implemented in various ways other than those described below.

[0043] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0044] The embodiments described in this disclosure with references to "an embodiment," "an embodiment," "an example embodiment," and similar designations may include specific features, structures, or characteristics, but not every embodiment necessarily includes that specific feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when a specific feature, structure, or characteristic is described in connection with an embodiment, it should be understood that, whether explicitly described or not, in conjunction with other embodiments, it is within the knowledge of those skilled in the art to affect such a feature, structure, or characteristic.

[0045] It should be understood that although terms such as “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may also be referred to as a second element, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0046] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that, when used herein, the terms “comprising,” “including,” “having,” “containing,” and / or “comprising” specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements is connected by “and” or “or”, means at least any one element, or at least any two or more elements, or at least all elements.

[0047] As used in this application, the term "circuit system" may refer to one or more, or all of the following: (a) Pure hardware circuit implementation (such as implementation only in analog and / or digital circuit systems) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions, and (c) (Multiple) hardware circuits and / or (multiple) processors (such as (multiple) microprocessors or a portion of (multiple) microprocessors) that require software (e.g., firmware) to operate, but may be absent when operation does not require software.

[0048] This definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used in this application, the term "circuit system" also covers only the implementation of hardware circuitry or a processor (or processors) or portions thereof and their accompanying software and / or firmware. For example, if applicable to a particular claim element, the term "circuit system" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network nodes, or other computing or network nodes.

[0049] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network nodes in a communication network can be performed according to any suitable intergenerational communication protocol, including, but not limited to, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols and / or more advanced communication protocols. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, there will certainly be future types of communication technologies and systems that this disclosure can utilize. This should not be construed as limiting the scope of this disclosure to the systems described above.

[0050] As used herein, the term "network device" refers to a node in a communication network through which terminal devices access the network and receive services. Depending on the terminology and technology used, a network node can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Headend (RH), a Remote Radio Headend (RRH), a relay, a low-power node (such as a femtonode, piconode), and so on.

[0051] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), USB dongles, smart devices, wireless client devices (CPEs), Internet of Things (IoT) devices, watches or other wearables, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, commercially operating equipment, relays, integrated access and backhaul (IAB) and / or industrial wireless networks, etc. In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" may be used interchangeably.

[0052] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink (UL) resource,” or “downlink (DL) resource” can refer to any resource used to perform communication, such as communication between a terminal device and a network device, including resources in the time domain, frequency domain, spatial domain, code domain, a combination of more than one domain, or any other resource enabling communication. In the following, resources in the time domain (such as subframes) will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. It should be noted that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0053] As mentioned above, since Release (Rel)-15, 3GPP has been working on support for fifth-generation (5G) systems (5GS) for EC. EC enables new applications or enhanced user experiences by reducing latency. In EC, EAS (re)discovery is one of the key issues addressed in 3GPP SA2. EAS (re)discovery can take into account user plane latency requirements provided by AF via AF service impact requests. However, the Session Management Function (SMF) only considers user plane latency requirements as the latency between the UE and the Protocol Data Unit (PDU) Session Anchor (PSA) UPF, while N6 latency (such as from the PSA UPF to the EAS, or any node in the EDN or Data Network (DN)) is not considered.

[0054] In one design, the (re)discovery of EAS by the EAS Discovery Function (EASDF) is based on EAS deployment information, which includes only static deployment information but does not consider EAS load status and computing power, as this information is not applicable to EASDF. To (re)discover more suitable EAS, some dynamic information (e.g., EAS load, N6 latency between the local PSA and the EAS) and the relationships between different EAS need to be made available to EASDF. This information should be investigated together.

[0055] In recent years, a new paradigm called "Compute and Network Convergence (CNC)" has emerged. Server instance selection can be based on a combination of network and compute metrics associated with each EAS instance, such as available compute capacity, compute load, processing latency, and / or scaling strategies. This means that in some cases, for example, the EAS instance that is not closest to the UE (or does not generally have the best network metrics) may be preferred because its compute load is lower than that of the nearest instance. Therefore, enabling multi-domain-based server instance selection is one of the problems that needs to be addressed.

[0056] In 5GS, a QoS monitoring mechanism can be implemented to determine, measure, and / or monitor 5GS-internal latency. This mechanism allows the AF to subscribe to DL, UL, or round-trip packet latency measurements between the UE and the anchor UPF. The PCF translates the AF's request into Policy and Charging Control (PCC) rules and instructs the SMF to control the actual measurement. The SMF configures the Radio Access Network (RAN) and UPF accordingly. The UPF calculates the UL / DL packet latency between the UE and the PSA UPF based on the received RAN portion packet latency and the calculated packet latency between the NG-RAN and the PSA UPF. The UPF reports the calculated packet latency between the NG-RAN and the PSA UPF to the AF via the control plane or user plane. However, the QoS monitoring mechanism used for latency measurement is not applicable to measurements or monitoring of any 5GS-external latency, such as the N6 latency between the UPF and the EAS, or any other node in the EDN or DN.

[0057] A method is provided for 5GS to provide the AF with the expected latency between the UPF and / or Data Network Access Identifier (DNAI) and the EAS via EAS address and DNAI mapping information. However, the entire EAS address and DNAI mapping information maintained in the Unified Data Repository (UDR) and / or Network Open Function (NEF) is configured by the Operation, Administration and Maintenance (OAM) function, and the 5G Core Network (5GC) (e.g., SMF) cannot obtain latency values ​​through real-time measurement.

[0058] Assume that the N6 latency between the PSA UPF and any other node in the EAS, AS, or EDN or DN must be known by the 5GS. In order for this information to facilitate EAS (re)discovery controlled or assisted by the 5GS, the 5GC needs this information to guide traffic or provide auxiliary information to the EASDF or AF based on it. The process for the 5GS to obtain N6 latency information is at least one problem that will be addressed in this disclosure. Similar to N6 latency, other QoS parameters (e.g., packet delay variation, packet loss, data rate, etc.) may also be related to 5GS-controlled or assisted EAS (re)discovery.

[0059] Therefore, the exemplary embodiments of this disclosure provide a general solution, for example, to address the problem of how to trigger and measure QoS metrics through at least N6 interfaces, as well as other potential problems. According to some embodiments of this disclosure, a first network device triggers at least one QoS measurement through at least one data network user plane interface of a communication network and at least one network node of the data network. The first network device also sends a configuration including one or more measurement parameters to at least one second network device for at least one QoS measurement through at least one data network user plane interface. Through the exemplary embodiments of this disclosure, a solution for triggering and measuring QoS metrics through at least N6 interfaces can be provided, and thus QoS metrics can be better monitored and used for controlled or assisted AS or EAS discovery or rediscovery.

[0060] For illustrative purposes, the principles and exemplary embodiments of this disclosure for enabling announcement areas will be referenced below. Figures 1A to 9 The following are descriptions. However, it should be noted that these embodiments are provided to enable those skilled in the art to understand the inventive concept of this disclosure and implement the solutions presented herein, and are not intended to limit the scope of this application in any way. It should also be noted that although this description uses a RAN radio access network as an example of an access network that allows a UE to access a 3GPP core network (e.g., a 5G core network), it must be understood that this is not limiting, and other types of access networks can be used, such as untrusted non-3GPP access networks and wired access networks to the 3GPP core network. Similarly, the RAN can correspond to a terrestrial access network or a non-terrestrial access network, and is not limited to terrestrial base stations.

[0061] refer to Figure 1A The illustration shows an example network environment 100A in which exemplary embodiments of the present disclosure may be implemented. The network environment 100A, which may be part of a communication network, includes a first network device 102, a second network device 104, a third network device 106, and a fourth network device 108.

[0062] like Figure 1A As shown, network environment 100A includes a first network device 102 (a network node such as SMF). Network environment 100A includes a second network device 104 (a network node such as UPF). Network environment 100A includes a third network device 106 (a network node such as NEF). Network environment 100A includes a fourth network device 108 (a network node such as AF).

[0063] In some example embodiments, the AF may include at least one of a central AF or a local AF (L-AF). The NEF may include at least one of a central NEF or a local NEF (L-NEF). The network node of the data network may include at least one of an EAS, a gateway associated with the EAS, or an ingress node associated with the EAS.

[0064] The first network device 102 and the second network device 104 can communicate directly with each other. The first network device 102 and the third network device 106 can communicate with each other via PCF 112 or directly with each other. The second network device 104 can communicate directly with PCF 112. The second network device 104 can also communicate with network nodes of data network 110 (e.g., DN endpoint (DN-EP)) via interface 116. The second network device 104 can also communicate with terminal device 114 (hereinafter referred to as UE 114) via interface 118. The interface 116 between the second network device 104 and the network node of data network 110 (also referred to as DN-EP 110) can also be referred to as the N6 interface.

[0065] It should be understood that the number of network devices and / or terminal devices is for illustrative purposes only and does not imply any limitation. Environment 100A may include any number of network devices and / or terminal devices to suit the implementation of embodiments of this disclosure. Although not shown, it should be understood that one or more devices may be located in environment 100A.

[0066] refer to Figure 1B This illustration depicts an example conceptual principle 100B according to some exemplary embodiments of the present disclosure. Conceptual principle 100B introduces a method to enable 5GC 120 to measure network metrics between UPF 126 and DN-EP 124 (such as the AS or EAS itself, or another node in the DN or EDN on the path and close to the AS or EAS, such as a router, gateway, ingress node, or load balancer) via at least an N6 interface. It should be understood that, for simplicity, the EAS in the DN is merely an example used to illustrate the solution of this disclosure. Any node in the DN may also include any node in the EDN and may be applicable to all options or embodiments. The process of how QoS measurement and monitoring is triggered, configured, and controlled is provided. The following description will use packet delay via N6 as an example. It should be understood that conceptual principle 100B is also applicable to other metric measurements via the N6 interface, the interface between the UE and the PSA UPF, and / or the N3 interface, which may be, but is not limited to, packet loss, packet delay variation, or data rate (such as throughput and / or capacity).

[0067] Typically, the process for QoS monitoring via at least the N6 interface can be triggered by: 1) SMF local policy; 2) OAM, in which case the information that may be reported could be QoS parameters via the N6 interface; or 3) AF, in which case the information that may be reported is QoS parameters for the link between the UE or UE group and the EAS collection. The following six aspects of conceptual principle 100B will be described for an overall and brief overview.

[0068] First, QoS monitoring via at least the N6 interface can be triggered by information received from or configured by local policies of the AF, OAM, or (SMF), including measurement requirements or measurement assistance information. Different triggers may include different parameters. For example, measurement requirements may involve 5GS information, DN-EP information, information associated with EAS, application information, or any combination of the above information included in the measurement requirements or measurement assistance information.

[0069] In some example implementations, measurement requirements or measurement assistance information can be applied to different use cases. As an example, measurement assistance information can be part of the measurement requirement, excluding the application ID received by the NEF and from the AF. As another example, measurement assistance information can be information derived by the NEF based on the measurement requirement received from the AF, and may need to be sent to other network functions. As yet another example, measurement assistance information can be an information element that can be provided, configured, or deployed by the AF to the 5GS.

[0070] In some example embodiments, measurement requirements or measurement assistance information may be provided to the 5GS via different processes. As an example, measurement requirements may be provided to the 5GS by the AF via a process for QoS monitoring (e.g., an AF session with QoS requirements), a process for service provisioning, a process for AF impact on service routing, or a process for new services. As another example, measurement requirements may be provided to the 5GS by the OAM via a management plane process. As yet another example, measurement assistance information may be provided, configured, or deployed to the 5GS by the AF via EAS Deployment Information (EDI). The above examples are provided only for a better understanding of this disclosure and are not intended to be limiting. That is, other examples are not excluded.

[0071] In some example implementations, 5GS information may correspond to a list of Data Network Names (DNNs), Single Network Slice Selection Aid Information (S-NSSAI), UE addresses, UE group addresses or identifiers, or UE location identifiers. UE identifiers may be, but are not limited to, IP addresses or prefixes. UE location identifiers may correspond to, but are not limited to, dedicated RAN nodes.

[0072] In some example embodiments, DN-EP information may correspond to at least one of the following: DNAI, endpoint ID, list of IP addresses, range of IP addresses, fully qualified domain name (FQDN), or Uniform Resource Locator (URL) of a remote peer in the DN (e.g., EAS or any other node in the DN).

[0073] In some example embodiments, if the DN-EP is not the EAS itself, the EAS information may correspond to a list of EASIDs, IP addresses, IP address ranges, and FQDNs. In some example embodiments, if EAS information is included, the AF may also provide EAS instantiation information per EASID (e.g., instantiated, instantiable but not yet instantiated). This information can indicate which DN-EP is for the EAS and that the measurement performed between the UPF and that DN-EP is relevant.

[0074] In some example implementations, application information, such as application ID, service descriptor, or service filtering information, may be provided.

[0075] Second, measurement protocol-related information can also be provided as measurement requirements or measurement aids to indicate the supported measurement protocols in preferred order. For example, STAMP [RFC8792] or TWAMP [RFC5357], ICMP, or HTTP can be applied. Some protocol-specific configuration parameters can also be included. For example, if STAMP is indicated, the measurement role, operating mode, security-related parameters (such as authentication mode), and / or port number can be provided.

[0076] In some example embodiments, parameters related to the reporting can be provided as measurement requirements, including reporting frequency, reporting objectives, and threshold(s).

[0077] Third, upon receiving a measurement request or measurement assistance information, the 5GC (e.g., NEF or SMF) can determine the measurement target (such as any other node in (multiple) EAS or DN) and prepare measurement parameters that include the determined measurement target. The measurement parameters can be sent to another NF (e.g., SMF) in the 5GC, or determined locally in the SMF.

[0078] Fourth, the 5GC (e.g., SMF) can initiate and configure measurement parameters for QoS monitoring of UPFs via at least the N6 interface. The SMF can determine and configure affected UPFs for QoS monitoring via the N6 interface based on measurement requirements received from the AF or OAM, or based on measurement requirements configured or determined by the AF, OAM, or local policies. The SMF can determine and configure affected UPFs for QoS monitoring via the N6 interface based on measurement assistance information received from the AF, OAM, NEF, or NEF, or based on measurement parameters received from the NEF. The SMF can determine and configure affected UPFs for QoS monitoring via the N6 interface based on the UPF's measurement capabilities.

[0079] Fifth, the UPF can receive configured measurement parameters for QoS monitoring via at least the N6 interface and can perform packet delay measurements between itself and the DN-EP (which may correspond to (multiple) EAS) or a defined measurement target. The UPF can report the measured packet delay directly to the SMF or AF and / or NEF via the N6 interface, based on the configuration from the SMF. Before receiving the QoS monitoring configuration via the N6 interface, the UPF can also report its measurement capabilities (…). Figure 1B (Not shown in the diagram). SMF can utilize UPF measurement capabilities while identifying and configuring affected UPFs for QoS monitoring via at least the N6 interface.

[0080] In some example embodiments, the results of QoS monitoring via at least the N6 interface can be used as follows: 1) The AF can use the results of QoS monitoring via at least the N6 interface to provide more accurate 5GS user plane latency requirements (e.g., for radio level scheduling) by taking into account the reported latency via the N6 interface in E2E latency requirements for EAS (re)discovery; 2) The 5GC (e.g., SMF or PCF) can directly expose the results of QoS monitoring via at least the N6 interface to the AF based on received requests for QoS monitoring via at least the N6 interface; and / or 3) The 5GC can calculate the sum of the latency measured locally via the N6 interface, the latency measured between the UE and the PSA UPF, and / or the latency measured via the N3 interface. This sum can be referred to below as the combined measurement latency. The combined measurement latency can be used in different use cases. As an example, the SMF can use the combined measurement latency when considering edge relocation. For example, the joint EAS and UPF determined for 5GS can be (re)selected to meet E2E user plane latency requirements requested by AF, or to determine the 5GS-centric EAS (rediscovery) in the case of INC. Additionally, it should be understood that the procedures used to trigger QoS monitoring can also be used for other metrics such as packet loss, packet delay variation, or data rate.

[0081] Finally, based on the configuration received from the SMF, QoS measurement reports can be sent directly from the UPF to the NEF, AF, local NEF, or local AF. QoS measurement reports can also be sent from the UPF to the AF via the SMF and / or PCF. Furthermore, QoS measurement reports can be sent from the UPF to the SMF (since the SMF is the consumer of QoS measurement results).

[0082] refer to Figure 1C The illustration depicts an example measurement scenario 100C according to some example embodiments of the present disclosure. Figure 1C In this configuration, EAS 134 and 136 are configured as the measured components. Therefore, EAS 134 and 136 are DN-EP. SMF 130 can be configured with UPF 132 to perform QoS measurements via the N6 interface.

[0083] refer to Figure 1D The illustration depicts another example measurement scenario 100D according to some example embodiments of the present disclosure. Figure 1D In this context, only the gateway or ingress node 148 is visible to 5GS, and the gateway or ingress node 148 is used to access the EAS behind the gateway / ingress node.

[0084] In measurement scenario 100D, the gateway and / or ingress node 148 can be a DN-EP as defined in this disclosure. The gateway and / or ingress node 148 can be an IP router, a tunnel gateway (where the tunnel can be any type of IP or L2 tunneling protocol, such as GTP-U, L2TP, IPSec in tunnel mode, or HTTP / QUIC), or a load balancer. The gateway and / or ingress node can be located on a path to one or more EAS 144 and 146. The measurement results between UPF 142 and the DN-EP can sufficiently accurately reflect the measurement between UPF 142 and those EAS such as EAS 144 and 146. Both DN-EP information and EAS address information can be provided by the AF to trigger QoS monitoring via at least the N6 interface. DN-EP information can be used by 5GS to determine measurement points; however, EAS information can be used to determine which DN-EP corresponds to which EAS(s) for the purpose of generating EAS instance-specific measurement results. These measurement results are needed to select between EAS instances or to determine whether a particular EAS instance meets the end-to-end UE-to-EAS latency requirements.

[0085] In some example embodiments, the DN-EP to EAS mapping information may include an additional delay component that is added to the delay measurement between the UPF and the DN-EP. This delay component may represent the delay between the DN-EP and the EAS.

[0086] refer to Figure 2A The illustration shows an example signaling process 200A for QoS measurement according to some example embodiments of the present disclosure. Figure 2A This illustrates a scenario where SMF triggers QoS measurements. Figure 2A Reference Figure 1A It was discussed.

[0087] The first network device 102 triggers (202) at least one QoS measurement through at least one data network user plane interface of the communication network and at least one network node of the data network. For example, the first network device 102 (hereinafter referred to as SMF) may activate QoS measurement through the N6 interface based on measurement requirements received, configured or determined from AF, OAM or through local policies; measurement auxiliary information received, configured or determined from AF, OAM, NEF or through local policies; or measurement parameters received from NEF.

[0088] The information used to trigger QoS measurements via the N6 interface is shown in Table 1. The received measurement requirements or measurement assistance information may include any part of Table 1. Table 1: Information used to trigger QoS measurements via the N6 interface

[0089] In some example embodiments, the SMF may receive measurement parameters (also referred to as the first set of measurement parameters) from another NF in the 5GC, including one or more of DN-EP information, 5GS information, EAS and DN-EP to EAS mapping information, measurement protocol-related information, and reporting-related parameters. In this case, other NFs in the 5GC (e.g., NEFs) may derive the measurement parameters based on measurement requirements received from the AF or OAM for at least one QoS measurement via at least the N6 interface, as shown in Table 1.

[0090] In some example embodiments, if the SMF decides to trigger QoS monitoring via at least the N6 interface based on a local policy, it can derive measurement parameters locally. In some example embodiments, the SMF may use 5GS information including one or more of the following: DNN, S-NSSAI, UE address, UE identifier or UE location identifier, UE group address, UE group identifier or UE group location identifier, to determine the UPF to be used for QoS monitoring via at least the N6 interface. In some example embodiments, the SMF may also determine the preferred protocol to be used by the UPF and configure protocol-specific configuration parameters based on, for example, a local policy and / or the received measurement parameters.

[0091] In some example implementations, if the SMF determines to use STAMP as the measurement protocol, it can configure the UPF to have at least one of the following: measurement role (session sender), operating mode, security-related information (such as authentication mode), port number, etc. Similar principles can be applied to other protocols.

[0092] First network device 102 sends a configuration 208 to at least one second network device 104 (hereinafter sometimes referred to as UPF) including one or more measurement parameters for at least one QoS measurement via at least one data network user plane interface. At least one second network device 104 receives (206) the configuration 208 from first network device 102. In this way, the SMF can configure the determined UPF using measurement parameters for QoS monitoring via at least N6 interfaces.

[0093] The second network device 104 performs (210) at least one QoS measurement based on a configuration including one or more measurement parameters. For example, the UPF can perform configured QoS monitoring via at least the N6 interface by using a protocol configured by the SMF, or by implementation if the protocol is not configured by the SMF. The UPF can report the measured QoS parameters to the SMF.

[0094] In some example embodiments, the SMF may open the received measurement QoS parameters for further use by other NFs or entities, or the received measurement QoS parameters may be used locally. In some example embodiments, the SMF may open the received measurement reports to the AF via the PCF, or to the AF via the NEF, or to any other 5GC NF (e.g., Network Data Analysis Function NWDAF).

[0095] In some example embodiments, the SMF or PCF may also construct a combined measurement delay by calculating the sum of the measurement delay via the N6 interface and the delay between the UE and the PSA UPF, and / or the measurement delay via the N3 interface. The SMF or PCF can then disclose the combined measurement delay to the AF or to any other 5GC NF (e.g., NWDAF). In some example embodiments, as part of early notification, the SMF / PCF may report the combined measurement delay of the list of candidate DNAIs to the AF. In some example embodiments, the SMF / PCF may report the combined measurement delay associated with the list of candidate DNAIs to the NEF as part of the public DNAI selection for the UE set.

[0096] In some example embodiments, the SMF can consume measurement results locally (N6 delay or combined measurement delay). In some example embodiments, the SMF can use combined measurement delays to compile a list of candidate DNAIs.

[0097] In some example embodiments, the UPF may send a combination set of the following: directly to AF; via NEF to AF; via L-NEF to AF; directly to L-AF; via NEF to L-AF; via L-NEF to L-AF; OAM; or any combination thereof.

[0098] Figure 2B Another example signaling process 200B for QoS measurement according to some example embodiments of this disclosure is illustrated. Figure 2B This illustrates a scenario where AF triggers QoS measurements. Figure 2B Reference Figure 1A It was discussed.

[0099] A fourth network device (hereinafter referred to as AF) 108 sends (222) information 226 to a third network device 106 (hereinafter referred to as NEF) for triggering at least one QoS measurement through at least one data network user plane interface and at least one network node of the data network. The third network device 106 receives (224) information 226 from the fourth network device 108. The information for triggering at least one QoS measurement may include at least one of one or more measurement requirements or one or more measurement auxiliary information.

[0100] Then, the third network device 106 can determine the measurement target based on at least one of one or more measurement requirements or one or more measurement auxiliary information. The third network device 106 can determine one or more measurement parameters based on the measurement target and at least one of one or more measurement requirements or one or more measurement auxiliary information.

[0101] In some example embodiments, the information used to trigger at least one QoS measurement may include a trigger (such as a request for a provided request or a request to trigger at least one of one or more measurement requirements or one or more measurement aids).

[0102] In some example embodiments, one or more measurement parameters may include at least one of the following: a measurement target, a parameter to be measured, a measurement protocol-specific parameter, a parameter related to reporting, or information associated with a communication system.

[0103] Then, the third network device 106 sends (228) one or more measurement requests or one or more measurement assistance information to at least one of the PCF or the first network device. Alternatively, instead of 228, the third network device 106 stores (230) one or more measurement requests or one or more measurement assistance information in a unified data repository (UDR).

[0104] A complete description of the process for QoS measurements triggered by AF will be provided below. Figure 3 . Figure 3 The illustration shows an example signaling procedure 300 for a measurement triggered from an AF according to some example embodiments of this disclosure. Figure 3 In the meantime, AF 308 can request 5GS to perform QoS monitoring through at least the N6 interface.

[0105] At step 320, SMF 302 may provide protocol-specific parameters and information for UPF 304 along with early notification (e.g., TWAMP / STAMP / ICMP / HTTP, indicating the address of UPF 304). In this case, QoS monitoring via at least the N6 interface is triggered by AF 308. Step 320 may be optional and may be applicable when AF 308 receives early notification due to UE mobility.

[0106] At point 322, AF 308 can send a request to NEF 306 for QoS measurements via at least the N6 interface. Details or parameters included in this request for QoS measurements via at least the N6 interface can be found in Table 1 as described above.

[0107] In some example implementations, if the requested target is specific to a particular UE(s), the QoS monitoring process can be reused. For example, the Nnef_AFSessionWithQoS_Create / Modify service can be reused and extended. In this case, the Nnef_AFSessionWithQoS_Create / Modify service may need to be updated to support measurement requirements, which may include the information listed in Table 1.

[0108] In some example embodiments, if the requested target is for a specific application(s), the procedures for supplying service-specific parameters (e.g., 3GPP TS 23.502 V18.4.0 (2023-12), Clause 4.15.6.7.2) can be reused. In this case, the AF 308 request for QoS measurements may include either application information or DN-EP information. In this case, the Nnef_ServiceParameter_Create / Update / Delete service can be reused and extended. Furthermore, a new Nnef service may need to be defined to support measurement requirements, which may include the information listed in Table 1.

[0109] In some example implementations, the procedures for AF impact regarding traffic guidance (e.g., 3GPP TS 23.502V18.4.0 (2023-12), Clause 4.3.6.4) can be reused. In this case, the Nnef_TrafficInfluence_Create / Update / Delete request can be reused and extended to allow AF 308 to provide measurement requirements, including the information listed in Table 1. AF 308's requests for QoS measurements can be directed to a list of UEs, a group of UEs, or an application.

[0110] In some example embodiments, the process for providing EAS deployment information (EDI) from AF 308 via NEF 306 (e.g., 3GPP TS 23.548 V18.4.0 (2023-12), Clause 6.2.3.4.2) can be reused. In this case, the Nnef_EASDeployment_Create / Update / Delete service can be used. The Nnef_EASDeployment_Create / Update request of AF 308 can be extended to allow AF 308 to provide measurement assistance information, including the information listed in Table 1. In this case, NEF 306 can directly send one or more received measurement assistance information (which is in...) to SMF 302. Figure 3 (Not shown in the text).

[0111] In one or more of the example embodiments described above, measurement requirements may include measurement protocol-related information (as shown in Table 1) and reporting-related information. Protocol information may include supported protocols (e.g., supported protocols for measurement in a preferred order: STAMP, TWAMP, ICMP, HTTP, etc.) and / or protocol-specific configuration information (e.g., measurement role (session sender), operating mode, security-related information (such as authentication mode), and / or port number). Reporting-related information may reuse conventional QoS monitoring mechanisms, which may include at least one of the following: reporting frequency, reporting target, and threshold(s).

[0112] At 324, after NEF 306 receives a request from AF 308 for QoS measurements via at least the N6 interface, NEF 306 can translate the request and determine (multiple) measurement targets. NEF 306 can also prepare measurement parameters (also referred to as a second set of measurement parameters) for QoS monitoring via at least the N6 interface based on the measurement requirements and the determined measurement targets. In some example embodiments, if application information is provided, but DN-EP information is not included in the QoS measurement request from AF 308, all (multiple) EAS(s) associated with a DNAI can be selected as measurement targets based on the EAS address and DNAI mapping information maintained in NEF 306 and / or UDR 314. Using the EAS address and DNAI mapping information, NEF 306 can determine which EAS(s) are associated with the corresponding DNAI.

[0113] In some example embodiments, if QoS monitoring via at least the N6 interface is for (multiple) UEs, UE-based measurement parameters for QoS monitoring via at least the N6 interface can be communicated to the PCF 312 associated with the UE's PDU session. Then, at 326, the PCF 312 can provide the measurement parameters in a PCC rule. The PCC rule may need to be updated / extended to carry these measurement parameters. Then, at 332, the PCF 312 can notify the SMF 302 of the notification containing the measurement parameters for QoS monitoring via at least the N6 interface in the updated / extended PCC rule.

[0114] In some example embodiments, if QoS monitoring via at least the N6 interface is for (multiple) applications, then at 328, service-based measurement parameters for QoS monitoring via at least the N6 interface can be sent from NEF 306 to PCF 312 via UDR 314, and can be further stored, updated, and / or removed in UDR 314. At 330, PCF 312 can register data changes from UDR 314, and PCF 312 can receive measurement parameters for QoS monitoring via at least the N6 interface from UDR 314. At 332, PCF 312 can notify SMF 302 of the measurement parameters for QoS monitoring via at least the N6 interface in the updated / extended PCC rules. Alternatively, in roaming cases, SMF 302 can subscribe directly from NEF 306 / UDR 314.

[0115] At 334, SMF 302 can identify the affected UPF(s) 304 to perform QoS measurements. At 336, SMF 302 can notify the affected UPF(s) 304 to perform QoS measurements based on measurement parameters used for QoS monitoring via at least the N6 interface. At 338, the affected UPF(s) 304 can perform QoS measurements between themselves / themselves and the affected DN-EP(s) 310 based on measurement configuration.

[0116] At 342, (multiple) affected UPFs 304 can send a measurement report to SMF 302. At 344, SMF 302 can use the information contained in the measurement report for controlled or auxiliary AS or EAS detection or rediscovery. Details of steps 334 to 344 may refer to Figure 2A The description is omitted here for simplicity. At point 346, SMF302 can send a measurement report to PCF 312. At point 348, PCF 312 can send a measurement report to NEF 306. At point 350, NEF 306 can send a measurement report to AF 308.

[0117] Examples of use cases where AF 308 can request 5GS to perform QoS monitoring at least N6 can be the following use cases (1) through (4). Use case 1: AF 308 can request monitoring of the latency of a combination of (end-to-end) delays about the UE or UE location by requesting notification when the latency exceeds a threshold. For example, the monitoring can be continuous and can be used to detect when the AF should (re)find a more suitable EAS.

[0118] Use Case 2: After receiving an early UE mobility notification from SMF 302, AF 308 may request an N6 delay between the collection of the UE's PSA UPF and EAS, so as to select the appropriate EAS after the UE's PSA UPF or target DNAI has changed.

[0119] Use Case 3: After the UE attempts to reach an application via the application load balancer (LB), the LB, acting as AF 308, can request immediate monitoring of the (end-to-end) latency (or N6 latency) between the UE (identified by its IP address) and a set of candidate EAS(s), or between the UE and a candidate data center hosting the EAS supporting the target application. Each candidate EAS(s) or data center can be identified by the IP address and port number to which their respective latency monitoring terminates. Supported protocols can be in a preferred order (e.g., STAMP, TWAMP, ICMP, and / or HTTP). Once the LB has obtained the QoS measurements, it can select the most suitable EAS or data center.

[0120] Use Case 4: The AF 308 is not required to select the EAS with the lowest latency, and the AF 308 can take into account other information such as the load of the EAS to select the most suitable EAS.

[0121] In some example embodiments, the OAM function may request the SMF 302 to measure metrics via at least the N6 interface. For a given EDN, the connections between (multiple) instantiated EASs and one or more UPFs 304s may be pre-configured by the management plane. The OAM function may request the SMF 302 to measure metrics for these connections via at least the N6 interface. In this case, the measurement request may include both 5GS information and DN-EP information and / or EAS information. All one or more UPFs 304s and DN-EPs 310s (and / or those with EASs) can be notified to the SMF 302 by the OAM function. Measurement reports can be sent to the OAM function. The OAM function may store the report contents in the EAS address and DNAI mapping information in the UDR 314 and / or NEF 306.

[0122] In some example embodiments, the UPF 304 may register its measurement capabilities and supported protocols. For example, when establishing or updating its association with the SMF 302 (before it receives any configuration of signaling associated with an N4 session or any configuration of combined QoS monitoring or QoS monitoring via at least the N6 interface), the UPF 304 may also report its measurement capabilities to the SMF 302.

[0123] In some example embodiments, measurement capabilities may include supported measurement protocols(s), measurement profile(s), measurement orientation (such as DL, UL, or round trip), supported measurement parameters (such as packet delay, packet delay variants, packet loss, data rate, etc.), and measurement role (session sender), supported operating modes, security-related information (such as authentication modes), and / or port numbers of supported measurement protocols. This capability may also be provided as part of UPF 304 registration to NRF 306.

[0124] By reference Figures 1A to 3 Implementing example embodiments of this disclosure, a solution for triggering and measuring QoS metrics via at least the N6 interface can be provided, and thus the QoS metrics can be better monitored and used for controlled or assisted AS or EAS discovery or rediscovery.

[0125] refer to Figure 4 The illustration shows an example flowchart of a QoS measurement process 400 at a first network device according to some example embodiments of the present disclosure. Figure 4 Reference Figure 1A Described.

[0126] At 402, the first network device 102 triggers at least one QoS measurement via at least one data network user plane interface of the communication network and at least one network node of the data network. At 404, the first network device 102 sends a configuration including one or more measurement parameters to at least one second network device 104 for at least one QoS measurement via at least one data network user plane interface. In some embodiments, the data network user plane interface refers to the interface between the communication network and at least one network node of the data network. For example, the data network user plane interface may be the N6 interface between the (PSA) UPF and (at least one network node) of the data network.

[0127] In some example embodiments, triggering at least one QoS measurement via at least one data network user plane interface may be in response to receiving one or more measurement requests, or one or more measurement assistance information, or at least one of the policies configured at the first network device.

[0128] In some example embodiments, at least one of one or more measurement requirements or one or more measurement assistance information can be received from the OAM function or AF.

[0129] In some example embodiments, one or more measurement requirements or one or more measurement assistance information may be received from the AF via a policy control rule that supports one or more measurement requirements or one or more measurement assistance information sent by the PCF.

[0130] In some example embodiments, one or more measurement requirements or one or more measurement assistance information can be received from the NEF.

[0131] In some example embodiments, one or more measurement requirements or one or more measurement support information may be received from the AF via at least one of the following: a process for QoS monitoring; a process for the impact of AF on service guidance; a process for EDI provision; or a process for new services.

[0132] In some example embodiments, at least one of one or more measurement requirements or one or more auxiliary information may include at least one of the following: information associated with a communication system; information associated with a network node of a data network; information associated with an EAS; information associated with at least one application; information associated with a mapping between a network node of a data network and an EAS; information associated with a measurement protocol for at least one QoS measurement; information associated with a list indicating a preferred order of supported measurement protocols; or information associated with configuration parameters dedicated to a measurement protocol.

[0133] In some example embodiments, at least one of one or more measurement requirements or one or more measurement auxiliary information may also include at least one of the following: at least one parameter to be measured; or information associated with reporting at least one QoS measurement.

[0134] In some example embodiments, the first network device 102 may determine at least one second network device 104 based on at least one of information associated with a communication system or information associated with one or more network nodes of a data network configured at the first network device 102.

[0135] In some example embodiments, the information associated with the communication system may include at least one of the following: at least one DNN; at least one single S-NSSAI; the address of the terminal device; the ID of the terminal device; the location ID corresponding to the terminal device; the address of the terminal device group; the ID of the terminal device group; or the location ID corresponding to the terminal device group.

[0136] In some example embodiments, the first network device 102 may receive the measurement capabilities of at least one second network device 104.

[0137] In some example embodiments, the first network device 102 may send one or more configuration parameters of a measurement protocol for at least one QoS measurement. The measurement protocol may be determined based on at least one of the following: a policy configured at the first network device, the measurement capabilities of at least one second network device, one or more measurement requirements, one or more measurement support information, or a second set of measurement parameters.

[0138] In some example embodiments, one or more configuration parameters of the measurement protocol may include at least one of the following: measurement profile; measurement direction; operating mode; security-related information; or port number information.

[0139] In some example embodiments, the first network device 102 may receive at least one measurement report associated with at least one QoS measurement from at least one second network device 104.

[0140] In some example embodiments, the first network device 102 may send at least one measurement report to at least one of the following: directly to AF; via NEF to AF; via L-NEF to AF; directly to L-AF; via NEF to L-AF; via L-NEF to L-AF; or OAM.

[0141] In some example embodiments, at least one QoS measurement may be at least one first QoS measurement, and the set of measured parameters included in the measurement report may be a first set, and the first network device 102 may trigger at least one second QoS measurement via at least one terminal device and at least one second network device. The first network device 102 may determine a combination set of the first set and the second set of measured parameters of the at least one second QoS measurement.

[0142] In some example embodiments, the first network device 102 may send a combination set to at least one of the following: directly to AF; or via NEF to AF; via L-NEF to AF; directly to L-AF; via NEF to L-AF; via L-NEF to L-AF; or OAM.

[0143] In some example embodiments, the first network device 102 may determine a list of candidate DNAIs based on a combined set.

[0144] In some example embodiments, the one or more measurement parameters may be a first set of measurement parameters, and the first set of measurement parameters may be determined based on at least one of the following: one or more measurement requirements, one or more measurement assistance information, a second set of measurement parameters, or a policy configured at the first network device.

[0145] In some example embodiments, the first network device 102 may send a configuration including a first set of measurement parameters to at least one second network device 104, wherein the first set of measurement parameters includes at least one of the following: a measurement target, a parameter to be measured, a measurement protocol-specific parameter, a parameter related to a report, or information associated with a communication system.

[0146] In some example embodiments, at least one of the following may be applicable: a first network device includes an SMF; at least one second network device includes at least one UPF; or a network node of the data network may include at least one of the following: an EAS, a gateway associated with an EAS, or an ingress node associated with an EAS.

[0147] In some example embodiments, the first network device 102 may perform as described in the reference. Figure 2A The other steps described above.

[0148] refer to Figure 5 The illustration shows an example flowchart of a QoS measurement process 500 at a second network device according to some example embodiments of the present disclosure. Figure 5 Reference Figure 1A Described.

[0149] At point 502, the second network device 104 receives from the first network device 102 a configuration including one or more measurement parameters for at least one QoS measurement via at least one interface between the second network device 104 and at least one network node of the data network. At point 504, the second network device 104 performs at least one QoS measurement based on the configuration including the one or more measurement parameters.

[0150] In some example embodiments, the second network device 104 may send the measurement capabilities of the second network device 104 to the first network device 102.

[0151] In some example embodiments, the measurement capability may include at least one of the following: at least one supported measurement protocol; at least one measurement profile; at least one measurement direction; at least one supported measurement parameter; at least one supported measurement role; at least one supported operating mode; at least one security-related information; or at least one port number information of at least one supported measurement protocol.

[0152] In some example embodiments, the second network device 104 may send a measurement report associated with at least one QoS measurement to at least one of the following: the first network device; the OAM function; AF; via the first network device to AF; via PCF to AF; via L-NEF to AF; L-AF; via the first network device to L-AF; or via L-NEF to L-AF.

[0153] In some example embodiments, at least one QoS measurement may be at least one first QoS measurement, and the set of measured parameters included in the measurement report may be a first set, and the second network device 104 may perform a second QoS measurement through at least one terminal device and the second network device; and determine a combination set of the second set of measured parameters of the first set and the second QoS measurement.

[0154] In some example embodiments, the second network device 104 may send a combination set to at least one of the following: direct to AF; via NEF to AF; via L-NEF to AF; direct to L-AF; via NEF to L-AF; via L-NEF to L-AF; or OAM.

[0155] In some example embodiments, at least one of the following may be applicable: the first network device includes an SMF; the second network device includes a UPF; or the network node of the data network includes at least one of the following: an EAS, a gateway associated with an EAS, or an ingress node associated with an EAS.

[0156] In some example embodiments, the second network device 104 may perform as described in the reference. Figure 2A The other steps described above.

[0157] refer to Figure 6 The illustration shows an example flowchart of a QoS measurement process 600 at a third network device according to some example embodiments of the present disclosure. Figure 6 Reference Figure 1A Described.

[0158] At point 602, the third network device 106 receives from the fourth network device 108 information for triggering at least one QoS measurement via at least one data network user plane interface and at least one network node of the data network through the communication network. The information for triggering the at least one QoS measurement may include at least one of one or more measurement requirements or one or more measurement auxiliary information.

[0159] At 604, the third network device 106 sends one or more measurement requests or one or more measurement assistance information to at least one of the PCF or the first network device 102. Alternatively, instead of 604, at 606, the third network device 106 stores one or more measurement requests or one or more measurement assistance information in the UDR.

[0160] In some example embodiments, the third network device 106 may determine the measurement target based on at least one of one or more measurement requirements or one or more measurement auxiliary information included in the information used to trigger at least one QoS measurement. The third network device 106 may also send one or more measurement parameters to at least one of the PCF or the first network device 102. Alternatively, instead of sending the one or more measurement parameters, the third network device 106 may store the one or more measurement parameters in the UDR.

[0161] In some example embodiments, the one or more measurement parameters may be a second set of measurement parameters, and the second set of measurement parameters may include at least one of the following: a measurement target, a parameter to be measured, a measurement protocol-specific parameter, a parameter related to reporting, or information associated with a communication system.

[0162] In some example embodiments, based on the determination that at least one QoS measurement via at least one data network user plane interface and at least one network node of the data network is for one or more terminal devices, the third network device 106 may determine one or more network nodes of the data network corresponding to the one or more terminal devices as measurement targets based on information used to trigger the at least one QoS measurement. The third network device 106 may determine a second set of measurement parameters for the at least one QoS measurement performed by at least one second network device based on the determined measurement target and at least one of one or more measurement requirements or one or more measurement auxiliary information. The third network device 106 may send information including the second set of measurement parameters to the PCF.

[0163] In some example embodiments, based on the determination that at least one QoS measurement via at least one data network user plane interface and at least one network node of the data network is for one or more applications, the third network device 106 may determine one or more network nodes corresponding to the one or more applications as measurement targets based on information used to trigger the at least one QoS measurement. The third network device 106 may determine a second set of measurement parameters for the at least one QoS measurement performed by at least one second network device based on at least one of the determined measurement targets, one or more measurement requirements, or one or more measurement auxiliary information. The third network device 106 may store the second set of measurement parameters in a UDR, or the third network device 106 may send information including the second set of measurement parameters to at least one of the PCF or the first network device.

[0164] In some example embodiments, if information about at least one network node of the data network is not included in the information used to trigger at least one QoS measurement, the third network device 106 may determine the measurement target based on the EAS address and DNAI mapping information.

[0165] In some example embodiments, one or more measurement requirements or one or more measurement auxiliary information may include at least one of the following: information associated with a communication system including a third network device and a fourth network device; information associated with at least one network node of a data network; information associated with an EAS; information associated with at least one application; information associated with a mapping between at least one network node of the data network and the EAS; information associated with a measurement protocol for at least one QoS measurement; or information associated with configuration parameters dedicated to the measurement protocol.

[0166] In some example embodiments, one or more measurement requirements or one or more measurement aids may also include at least one of the following: at least one parameter to be measured; or information associated with reporting at least one QoS measurement.

[0167] In some example embodiments, a request to trigger at least one QoS measurement may be received via a process supporting at least one of one or more measurement requirements or one or more measurement support information. In some example embodiments, the process may include at least one of the following: a process for QoS monitoring; a process for AF impact regarding service guidance; a process for EAS EDI provisioning; or a process for a new service.

[0168] In some example embodiments, the third network device 106 may receive a measurement report associated with at least one QoS measurement from the PCF. In some example embodiments, the third network device 106 may receive a measurement report associated with at least one QoS measurement from at least one second network device.

[0169] In some example embodiments, at least one of the following may be applicable: at least one second network device includes at least one second network device; a third network device includes a NEF, which includes at least one of a central NEF or an L-NEF; a fourth network device includes an AF, which includes at least one of a central AF or an L-AF; or a network node of the data network includes at least one of the following: an EAS, a gateway associated with an EAS, or an ingress node associated with an EAS.

[0170] In some example embodiments, the third network device 104 may perform as described in the reference. Figure 2B The other steps described above.

[0171] refer to Figure 7 The figure illustrates an example flowchart of a QoS measurement process 700 at a fourth network device according to some example embodiments of the present disclosure. Figure 7 Reference Figure 1A Described.

[0172] At point 702, the fourth network device 108 sends information to the third network device 106 for triggering at least one QoS measurement via at least one data network user plane interface and at least one network node of the data network through the communication network. The information for triggering the at least one QoS measurement may include at least one of one or more measurement requirements or one or more measurement auxiliary information.

[0173] In some example embodiments, the fourth network device 108 may receive a measurement report of at least one QoS measurement from the third network device 106.

[0174] In some example embodiments, the one or more measurement requirements or one or more measurement auxiliary information may include at least one of the following: information associated with a communication system including a third network device and a fourth network device; information associated with at least one network node of a data network; information associated with an EAS; information associated with at least one application; information associated with a mapping between at least one network node of the data network and the EAS; information associated with a measurement protocol for at least one QoS measurement; or information associated with configuration parameters dedicated to the measurement protocol.

[0175] In some example embodiments, the one or more measurement requirements or one or more measurement aids may include at least one of the following: at least one parameter to be measured; or information associated with reporting at least one QoS measurement.

[0176] In some example embodiments, the fourth network device 108 may request at least one of the following: detection of one or more metrics relating to the terminal device or the location of the terminal device; monitoring of one or more metrics between the terminal device’s PSA UPF and the collection of EAS; or monitoring of one or more metrics between the terminal device and the candidate EAS collection or the candidate data center hosting the EAS supporting the target application.

[0177] In some example embodiments, the fourth network device 108 may request monitoring of one or more metrics between the terminal device and network nodes of the data network.

[0178] In some example embodiments, at least one of the following may be applicable: at least one second network device includes at least one second network device; a third network device includes a NEF, which includes at least one of a central NEF or an L-NEF; or a fourth network device includes an AF, which includes at least one of a central AF or an L-AF; or a network node of the data network includes at least one of the following: an EAS, a gateway associated with an EAS, or an ingress node associated with an EAS.

[0179] In some example embodiments, the fourth network device 108 may perform as described in the reference. Figure 2B The other steps described above.

[0180] By implementing any of methods (processes) 400 to 700, a solution for triggering and measuring QoS metrics via at least the N6 interface can be provided, and thus QoS metrics can be better monitored and used for controlled or auxiliary (edge) application server (AS or EAS) discovery or rediscovery.

[0181] In some example embodiments, the apparatus capable of performing method 400 (e.g., the first network device 102) may include components for performing the corresponding steps of method 400. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0182] In some example embodiments, the apparatus includes components for triggering at least one QoS measurement via at least one data network user plane interface of a communication network and at least one network node of the data network; and components for sending a configuration including one or more measurement parameters to at least one second network device for at least one QoS measurement via at least one data network user plane interface.

[0183] In some exemplary embodiments, the apparatus may further include a component for determining at least one second network device based on at least one of information associated with a communication system or information associated with one or more network nodes of a data network configured at the first network device.

[0184] In some example embodiments, the apparatus may also include components for receiving measurement capabilities of at least one second network device from at least one second network device.

[0185] In some example embodiments, the apparatus may further include components for transmitting one or more configuration parameters of a measurement protocol for at least one QoS measurement. In some example embodiments, the measurement protocol may be determined based on at least one of the following: a policy configured at a first network device, the measurement capabilities of at least one second network device, one or more measurement requirements, one or more measurement assistance information, or a second set of measurement parameters.

[0186] In some example embodiments, the apparatus may also include a component for receiving at least one measurement report associated with at least one QoS measurement from at least one second network device.

[0187] In some example embodiments, the device may also include components for sending at least one measurement report to at least one of the following: directly to AF; via NEF to AF; via L-NEF to AF; directly to L-AF; via NEF to L-AF; via L-NEF to L-AF; or OAM.

[0188] In some example embodiments, the at least one QoS measurement may be at least one first QoS measurement, and the set of measured parameters included in the measurement report may be a first set. The apparatus may also include components for triggering at least one second QoS measurement via at least one terminal device and at least one second network device; and components for determining a combination set of the first set and the second set of measured parameters of the at least one second QoS measurement.

[0189] In some example embodiments, the apparatus may also include components for sending a combined set to at least one of the following: directly to AF; or via NEF to AF; via L-NEF to AF; directly to L-AF; via NEF to L-AF; via L-NEF to L-AF; or OAM.

[0190] In some example embodiments, the apparatus may also include components for determining a list of candidate Data Network Access Identifiers (DNAIs) based on a combination set.

[0191] In some example embodiments, one or more measurement parameters may be a first set of measurement parameters, and the first set of measurement parameters may be determined based on at least one of the following: one or more measurement requirements, one or more measurement assistance information, or a policy configured at the first network device.

[0192] In some example embodiments, the apparatus may further include components for transmitting a configuration including a first set of measurement parameters to at least one second network device. The first set of measurement parameters may include at least one of the following: a measurement target, a parameter to be measured, measurement protocol-specific parameters, parameters related to reporting, or information associated with a communication system.

[0193] In some example embodiments, the apparatus may also include components for performing other steps in some example embodiments of method 400. In some example embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to cause execution of the apparatus together with the at least one processor.

[0194] In some example embodiments, the apparatus capable of performing method 500 (e.g., the second network device 104) may include components for performing the corresponding steps of method 500. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0195] In some example embodiments, the apparatus may include components for receiving a configuration including one or more measurement parameters from a first network device for at least one QoS measurement via at least one interface between a second network device and at least one network node of a data network; and components for performing at least one QoS measurement based on the configuration including one or more measurement parameters.

[0196] In some example embodiments, the apparatus may also include components for transmitting the measurement capabilities of the second network device to the first network device.

[0197] In some example embodiments, the apparatus may further include components for sending a measurement report associated with at least one QoS measurement to at least one of the following: a first network device; an OAM function; an AF; via the first network device to the AF; via the PCF to the AF; via the L-NEF to the AF; L-AF; via the first network device to the L-AF; or via the L-NEF to the L-AF.

[0198] In some example embodiments, at least one QoS measurement may be at least one first QoS measurement, and the set of measured parameters included in the measurement report may be a first set. The apparatus may also include components for performing a second QoS measurement through at least one terminal device and a second network device; and a combination set component for determining a second set of measured parameters for the first set and the second QoS measurement.

[0199] In some example embodiments, the apparatus may also include components for sending a combined set to at least one of the following: directly to AF; via NEF to AF; via L-NEF to AF; directly to L-AF; via NEF to L-AF; via L-NEF to L-AF; or OAM.

[0200] In some example embodiments, the apparatus may further include components for performing other steps in some example embodiments of method 500. In some example embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to cause execution of the apparatus together with the at least one processor.

[0201] In some example embodiments, the apparatus capable of performing method 600 (e.g., the third network device 106) may include components for performing the corresponding steps of method 600. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0202] In some example embodiments, the apparatus may include: components for receiving from a fourth network device information for triggering at least one QoS measurement via at least one data network user plane interface and at least one network node of the data network through the communication network, wherein the information for triggering at least one QoS measurement includes at least one of one or more measurement requirements or one or more measurement assistance information; components for sending one or more measurement requirements or one or more measurement assistance information to at least one of the PCF or the first network device; and components for storing one or more measurement requirements or one or more measurement assistance information in a UDR.

[0203] In some example embodiments, the apparatus may further include: a component for determining a measurement target based on at least one of one or more measurement requirements or one or more measurement auxiliary information included in the information that triggers at least one QoS measurement; a component for sending one or more measurement parameters to at least one of the PCF or the first network device; and / or a component for storing one or more measurement parameters in the UDR.

[0204] In some example embodiments, the apparatus may further include: components for determining one or more network nodes of the data network corresponding to one or more terminal devices as measurement targets based on information for triggering the at least one QoS measurement, based on at least one QoS measurement determined for one or more terminal devices via at least one data network user plane interface of the communication network and at least one network node of the data network; components for determining a second set of measurement parameters for at least one QoS measurement performed by at least one second network device based on the determined measurement target and at least one of one or more measurement requirements or one or more measurement auxiliary information; and components for sending information including the second set of measurement parameters to a policy control function (PCF).

[0205] In some example embodiments, the apparatus may further include: components for determining one or more network nodes corresponding to one or more applications as measurement targets based on information for triggering the at least one QoS measurement, based on determining that at least one QoS measurement via at least one data network user plane interface of a communication network and at least one network node of the data network is for one or more applications; components for a user to determine a second set of measurement parameters for at least one QoS measurement performed by at least one second network device based on at least one of the determined measurement targets, one or more measurement requirements, or one or more measurement auxiliary information; components for storing the second set of measurement parameters in a UDR; components for storing the second set of measurement parameters in a UDR; and / or components for sending information including the second set of measurement parameters to at least one of the PCF or the first network device.

[0206] In some exemplary embodiments, the apparatus may further include a component for determining a measurement target based on EAS address and DNAI mapping information if information of at least one network node of the data network is not included in the information used to trigger at least one QoS measurement.

[0207] In some example embodiments, the apparatus may further include components for receiving a measurement report associated with at least one QoS measurement from the PCF; or components for receiving a measurement report associated with at least one QoS measurement from at least one second network device.

[0208] In some example embodiments, the apparatus may further include components for performing other steps in some example embodiments of method 600. In some example embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to cause execution of the apparatus together with the at least one processor.

[0209] In some example embodiments, the apparatus capable of performing method 700 (e.g., the fourth network device 108) may include components for performing the corresponding steps of method 700. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0210] In some example embodiments, the apparatus includes components for sending information to a third network device for triggering at least one QoS measurement via at least one data network user plane interface of a communication network and at least one network node of the data network, wherein the information for triggering at least one QoS measurement includes at least one of one or more measurement requirements or one or more measurement auxiliary information.

[0211] In some example embodiments, the apparatus may also include a component for receiving a measurement report of at least one QoS measurement from a third network device.

[0212] In some example embodiments, the apparatus may also include components for requesting at least one of the following: monitoring of one or more metrics relating to a terminal device or the location of the terminal device; monitoring of one or more metrics between the terminal device’s PSA UPF and the collection of EAS; or monitoring of one or more metrics between the terminal device and a candidate collection of EAS or a candidate data center hosting EAS that supports the target application.

[0213] In some example embodiments, the apparatus may also include components for requesting monitoring of one or more metrics between the terminal device and network nodes of the data network.

[0214] In some example embodiments, the apparatus may further include components for performing other steps in some example embodiments of method 700. In some example embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to cause execution of the apparatus together with the at least one processor.

[0215] refer to Figure 8 The illustration shows an example simplified block diagram of a device suitable for implementing embodiments of the present disclosure. Device 800 may be provided to implement a network device, such as... Figure 1AAny of the network devices 102 to 108 shown. As shown, device 800 includes one or more processors 810, one or more memories 820 that can be coupled to processor 810, and one or more communication modules 840 that can be coupled to processor 810.

[0216] Communication module 840 is for bidirectional communication. Communication module 840 has at least one antenna to facilitate communication. The communication interface can represent any interface necessary for communication with other network elements; for example, the communication interface can be wireless or wired to other network elements, or a software-based interface for communication.

[0217] Processor 810 can be of any type suitable for a local technology network, and by way of non-limiting example, can include one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 800 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock synchronized with the main processor.

[0218] Memory 820 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 824, electrically programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 822 and other volatile memories that do not persist during power outages.

[0219] Computer program 830 includes computer-executable instructions that are executed by the associated processor 810. Program 830 may be stored in ROM 824. Processor 810 may perform any suitable actions and processes by loading program 830 into RAM 822.

[0220] The embodiments of this disclosure can be implemented by a program, such that device 800 can perform as described in the reference. Figures 2A to 7 Any process discussed in this disclosure. Embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.

[0221] In some embodiments, program 830 may be tangibly contained in a computer-readable medium, which may be included in device 800 (e.g., in memory 820) or in other storage devices accessible to device 800. Device 800 may load program 830 from the computer-readable medium into RAM 822 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 9 An example of a computer-readable medium 900 in the form of a CD or DVD is shown. A program 830 is stored on the computer-readable medium.

[0222] In some embodiments, device 800 may (be configured to perform / include) at least one network function (e.g., AF, NEF, UDR, UDM, PCF, UPF, SMF). In one embodiment, device 800 being / including a network function means a device / apparatus configured to perform at least a portion of the functionality of a network function.

[0223] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software, which can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0224] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions (such as those included in program modules) that are executed in a device on a target real or virtual processor to perform the functions described above. Figure 4 or Figure 7 The methods described are 400 to 700. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. The functionality of a program module can be combined or split among program modules as needed in various embodiments. The machine-executable instructions used for a program module can be executed on a local or distributed device. In a distributed device, the program module can reside on both local and remote storage media.

[0225] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0226] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0227] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having one or more lines, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. As used herein, the term “non-transient” refers to limitations inherent in the medium itself (i.e., tangible rather than signaling), rather than limitations on the persistence of data storage (e.g., RAM and ROM).

[0228] Furthermore, although the operations are described in a specific order, this should not be construed as requiring that these operations must be performed in the specific order or sequence shown, or that all of the operations shown must be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these implementation details should not be considered as a limitation on the scope of this disclosure, but rather as a description of features that may be specific to particular embodiments. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0229] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that this disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as examples of implementing the claims.

Claims

1. A first network device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the first network device to at least: Trigger at least one Quality of Service (QoS) measurement through at least one data network user plane interface and at least one network node of the data network in the communication network; as well as Send a configuration including one or more measurement parameters to at least one second network device, the one or more measurement parameters being used for the at least one QoS measurement via the at least one data network user plane interface.

2. The first network device of claim 1, wherein triggering the at least one QoS measurement via the at least one data network user plane interface is in response to receiving one or more measurement requests, or one or more measurement assistance information, or at least one of a policy configured at the first network device.

3. The first network device according to claim 2, wherein at least one of the one or more measurement requirements or the one or more measurement assistance information is received from an Operation, Administration and Maintenance (OAM) function or an Application Function (AF).

4. The first network device of claim 3, wherein the one or more measurement requirements or the one or more measurement assistance information are received from the AF via a policy control rule, the policy control rule supporting the one or more measurement requirements or the one or more measurement assistance information sent by the policy control function (PCF).

5. The first network device according to claim 3, wherein the one or more measurement requirements or the one or more measurement assistance information are received from the Network Open Function (NEF).

6. The first network device according to claim 2 or 3, wherein the one or more measurement requirements or the one or more measurement assistance information are received from the AF via at least one of the following: The process of QoS monitoring; The process of addressing the impact of AF on business guidance; The process of providing deployment information (EDI) for Edge Application Server (EAS); or The process for the new service.

7. The first network device according to any one of claims 2 to 6, wherein at least one of the one or more measurement requirements or the one or more measurement auxiliary information includes at least one of the following: Information associated with the communication system; Information associated with the network node of the data network; Information associated with EAS; Information associated with at least one application; Information associated with the mapping between the network nodes of the data network and the EAS; Information associated with the measurement protocol of the at least one QoS measurement; Information associated with a list indicating the preferred order of supported measurement protocols; or Information associated with configuration parameters specific to the measurement protocol.

8. The first network device of claim 7, wherein the at least one of the one or more measurement requirements or the one or more measurement assistance information further comprises at least one of the following: At least one parameter to be measured; or Information associated with at least one QoS measurement described in the report.

9. The first network device according to claim 7 or 8, wherein the first network device is further configured to: determine the at least one second network device based on at least one of the information associated with the communication system or information associated with one or more network nodes of the data network configured at the first network device.

10. The first network device according to any one of claims 7 to 10, wherein the information associated with the communication system includes at least one of the following: At least one data network name (DNN); At least one single network slice selection auxiliary information (S-NSSAI); The address of the terminal device; The identifier (ID) of the terminal device; The location ID corresponding to the terminal device; The address of the terminal device group; The ID of the terminal device group; or The location ID corresponding to the terminal device group.

11. The first network device according to any one of claims 1 to 10, wherein the first network device is further configured to: Receive the measurement capabilities of the at least one second network device from the at least one second network device.

12. The first network device according to any one of claims 2 to 11, wherein the first network device is further configured to: Send one or more configuration parameters of a measurement protocol for the at least one QoS measurement, wherein the measurement protocol is determined based on at least one of the following: the policy configured at the first network device, the measurement capabilities of the at least one second network device, the one or more measurement requirements, the one or more measurement assistance information, or a second set of measurement parameters.

13. The first network device of claim 12, wherein the one or more configuration parameters of the measurement protocol include at least one of the following: Measurement configuration file; Measurement direction; Operating modes; Information related to security; or Port number information.

14. The first network device according to any one of claims 1 to 13, wherein the first network device is further configured to: Receive at least one measurement report associated with the at least one QoS measurement from the at least one second network device.

15. The first network device according to claim 14, wherein the first network device is further configured to: Send at least one of the following measurement reports: Go directly to AF; Via Network Open Function (NEF) to the AF; via the local NEF (L-NEF) to the AF; Directly to the local AF (L-AF); via NEF to the L-AF; via L-NEF to the L-AF; or OAM.

16. The first network device of claim 15, wherein the at least one QoS measurement is at least one first QoS measurement, and the set of measured parameters included in the measurement report is a first set, and wherein the first network device is further configured to: Triggering at least one second QoS measurement via at least one terminal device and the at least one second network device; and A combined set of the first set and the second set of parameters of the at least one second QoS measurement is determined.

17. The first network device of claim 16, wherein the first network device is further configured to send the combined set to at least one of: Go directly to AF; or Via Network Open Function (NEF) to the AF; via the local NEF (L-NEF) to the AF; Directly to the local AF (L-AF); via NEF to the L-AF; via L-NEF to the L-AF; or OAM.

18. The first network device according to claim 16 or 17, wherein the first network device is further configured to: Based on the combined set, a list of candidate Data Network Access Identifiers (DNAIs) is determined.

19. The first network device according to any one of claims 1 to 18, wherein the one or more measurement parameters are a first set of measurement parameters, and the first set of measurement parameters is determined based on at least one of: one or more measurement requirements, one or more measurement assistance information, a second set of measurement parameters, or a policy configured at the first network device.

20. The first network device according to claim 19, wherein the first network device is further configured to: Send a configuration including the first set of measurement parameters to the at least one second network device, wherein the first set of measurement parameters includes at least one of the following: a measurement target, a parameter to be measured, a measurement protocol-specific parameter, a parameter related to a report, or the information associated with the communication system.

21. The first network device according to any one of claims 1 to 20, wherein at least one of the following is applicable: The first network device includes a session management function (SMF); The at least one second network device includes at least one user plane function (UPF); or The network nodes of the data network include at least one of the following: EAS, a gateway associated with the EAS, or an ingress node associated with the EAS.

22. A second network device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the second network device to at least: Receive configuration from a first network device including one or more measurement parameters, the one or more measurement parameters being used for at least one (QoS) measurement via at least one interface between the second network device and at least one network node of the data network; as well as The at least one QoS measurement is performed based on the configuration including the one or more measurement parameters.

23. The second network device according to claim 22, wherein the second network device is further configured to: Send the measurement capabilities of the second network device to the first network device.

24. The second network device of claim 23, wherein the measurement capability includes at least one of the following: At least one supported measurement protocol; At least one measurement profile; At least one measurement direction; At least one supported measurement parameter; At least one supporting measurement role; At least one supported operating mode; At least one piece of security-related information; or At least one port number information for the at least one supported measurement protocol.

25. The second network device according to any one of claims 22 to 24, wherein the second network device is further configured to send a measurement report associated with at least one of the following: The first network device; Operation, administration, and maintenance (OAM) functions; Application Functionality (AF); Via the first network device to the AF; Via Policy Control Function (PCF) to the AF; To the AF via Local Network Open Function (L-NEF); Local AF (L-AF); via the first network device to the L-AF; or From L-NEF to L-AF.

26. The second network device of claim 25, wherein the at least one QoS measurement is at least one first QoS measurement, and the set of measured parameters included in the measurement report is a first set, and wherein the second network device is further configured to: Perform a second QoS measurement via at least one terminal device and the second network device; and A combined set of the first set and the second set of parameters of the second QoS measurement is determined.

27. The second network device of claim 26, wherein the second network device is further configured to send the combined set to at least one of: Go directly to AF; via NEF to the AF; via L-NEF to the AF; Go directly to L-AF; via NEF to the L-AF; via L-NEF to the L-AF; or OAM.

28. The second network device according to any one of claims 22 to 27, wherein at least one of the following is applicable: The first network device includes a session management function (SMF); The second network device includes User Plane Function (UPF); or The network nodes of the data network include at least one of the following: an edge application server (EAS), a gateway associated with the EAS, or an entry node associated with the EAS.

29. A third network device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the third network device to at least: The fourth network device receives information for triggering at least one quality of service (QoS) measurement through at least one data network user plane interface and at least one network node of the data network via the communication network, wherein the information for triggering the at least one QoS measurement includes at least one of one or more measurement requirements or one or more measurement auxiliary information. as well as Send the one or more measurement requests or the one or more measurement assistance information to at least one of the Policy Control Function (PCF) or the first network device; or The one or more measurement requirements or the one or more measurement auxiliary information are stored in a unified data repository (UDR).

30. The third network device of claim 29, wherein the third network device is further configured to: The measurement target is determined based on at least one of the one or more measurement requirements or the one or more measurement auxiliary information included in the information used to trigger the at least one QoS measurement; as well as Send one or more measurement parameters to the PCF or the first network device; or The one or more measurement parameters are stored in the UDR.

31. The third network device of claim 30, wherein the one or more measurement parameters are a second set of measurement parameters, and wherein the second set of measurement parameters includes at least one of the following: a measurement target, a parameter to be measured, a measurement protocol-specific parameter, a parameter related to a report, or information associated with a communication system.

32. The third network device according to claim 31, wherein the third network device is further configured to: Based on the determination that the at least one QoS measurement via the at least one data network user plane interface of the communication network and the at least one network node of the data network is for one or more terminal devices, based on the information used to trigger the at least one QoS measurement, one or more network nodes of the data network corresponding to the one or more terminal devices are determined as the measurement target. Based on the determined measurement target and at least one of the one or more measurement requirements or the one or more measurement auxiliary information, a second set of measurement parameters is determined for the at least one QoS measurement performed by the at least one second network device; as well as Send information including the second set of measurement parameters to the Policy Control Function (PCF).

33. The third network device according to claim 31 or 32, wherein the third network device is further configured to: Based on the determination that the at least one QoS measurement via the at least one data network user plane interface of the communication network and the at least one network node of the data network is for one or more applications, based on the information used to trigger the at least one QoS measurement, one or more network nodes corresponding to the one or more applications are determined as the measurement targets. Based on at least one of the determined measurement target, the one or more measurement requirements, or the one or more measurement auxiliary information, a second set of measurement parameters is determined for the at least one QoS measurement performed by the at least one second network device; as well as The second set of measurement parameters is stored in the UDR; or Send information including the second set of measurement parameters to at least one of the PCF or the first network device.

34. The third network device according to claim 33, wherein the third network device is further configured to: If the information of the at least one network node of the data network is not included in the information used to trigger the at least one QoS measurement, the measurement target is determined based on the Edge Application Server (EAS) address and Data Network Access Identifier (DNAI) mapping information.

35. The third network device according to any one of claims 29 to 34, wherein the one or more measurement requirements or the one or more measurement auxiliary information comprises at least one of the following: Information associated with the communication system; Information associated with at least one network node of the data network; Information associated with the EAS; Information associated with at least one application; Information associated with the mapping between the at least one network node of the data network and the EAS; Information associated with the measurement protocol of the at least one QoS measurement; or Information associated with configuration parameters specific to the measurement protocol.

36. The third network device of claim 35, wherein the one or more measurement requirements or the one or more measurement assistance information further comprises at least one of the following: At least one parameter to be measured; or Information associated with at least one QoS measurement described in the report.

37. The third network device according to any one of claims 29 to 36, wherein the information for triggering the at least one QoS measurement is received via a process supporting at least one of the one or more measurement requirements or the one or more measurement assistance information, and wherein the process includes at least one of the following: The process used for QoS monitoring; The process used to assess the impact of business guidance (AF); The process used for providing EAS deployment information (EDI); or The process used for new services.

38. The third network device according to any one of claims 29 to 37, wherein the third network device is further configured to: Receive a measurement report associated with the at least one QoS measurement from the PCF; or Receive measurement reports associated with the at least one QoS measurement from the at least one second network device.

39. The third network device according to any one of claims 29 to 38, wherein at least one of the following is applicable: The at least one second network device includes at least one user plane function (UPF). The third network device includes a Network Open Function (NEF), which includes at least one of a Central NEF or a Local NEF (L-NEF); The fourth network device includes an application function (AF), which includes at least one of a central AF or a local AF (L-AF); or The network nodes of the data network include at least one of the following: EAS, a gateway associated with the EAS, or an ingress node associated with the EAS.

40. A fourth network device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the fourth network device to at least: Sending information to a third network device to trigger at least one quality of service (QoS) measurement through at least one data network user plane interface and at least one network node of the data network via a communication network, wherein the information for triggering the at least one QoS measurement includes at least one of one or more measurement requirements or one or more measurement auxiliary information.

41. The fourth network device of claim 40, wherein the fourth network device is further configured to: Receive a measurement report of the at least one QoS measurement from the third network device.

42. The fourth network device according to claim 40 or 41, wherein the one or more measurement requirements or the one or more measurement auxiliary information include at least one of the following: Information associated with the communication system including the third network device and the fourth network device; Information associated with at least one network node of the data network; Information associated with the Edge Application Server (EAS); Information associated with at least one application; Information associated with the mapping between the at least one network node of the data network and the EAS; Information associated with the measurement protocol of the at least one QoS measurement; or Information associated with configuration parameters specific to the measurement protocol.

43. The fourth network device of claim 42, wherein the one or more measurement requirements or the one or more measurement assistance information includes at least one of the following: At least one parameter to be measured; or Information associated with at least one QoS measurement described in the report.

44. The fourth network device according to any one of claims 40 to 43, wherein the fourth network device requests at least one of the following: Monitoring of one or more metrics relating to a terminal device or the location of the terminal device; Monitoring of one or more metrics between the collection of Protocol Data Units (PDUs), Session Anchor Points (PSA), UPFs, and EASs of terminal devices; or Monitoring one or more metrics between the terminal device and the candidate EAS set or the candidate data center hosting the EAS that supports the target application.

45. The fourth network device of claim 44, wherein the fourth network device further requests monitoring of one or more metrics between the terminal device and a network node of the data network.

46. ​​The fourth network device according to any one of claims 40 or 45, wherein at least one of the following is applicable: The at least one second network device includes at least one user plane function (UPF). The third network device includes a Network Open Function (NEF), which includes at least one of a Central NEF or a Local NEF (L-NEF); The fourth network device includes an application function (AF), which includes at least one of a central AF or a local AF (L-AF); or The network nodes of the data network include at least one of the following: EAS, a gateway associated with the EAS, or an ingress node associated with the EAS.

47. A method comprising: Trigger at least one Quality of Service (QoS) measurement at a first network device, through at least one data network user plane interface of the communication network and at least one network node of the data network; as well as Send a configuration including one or more measurement parameters to at least one second network device, the one or more measurement parameters being used for the at least one QoS measurement via the at least one data network user plane interface.

48. A method comprising: At the second network device, a configuration including one or more measurement parameters is received from the first network device, the one or more measurement parameters being used for at least one (QoS) measurement via at least one interface between the second network device and at least one network node of the data network; as well as The at least one QoS measurement is performed based on the configuration including the one or more measurement parameters.

49. A method comprising: At the third network device, information for triggering at least one quality of service (QoS) measurement via at least one data network user plane interface and at least one network node of the data network through the communication network is received from the fourth network device, wherein the information for triggering the at least one QoS measurement includes at least one of one or more measurement requirements or one or more measurement auxiliary information. as well as Send the one or more measurement requests or the one or more measurement assistance information to at least one of the Policy Control Function (PCF) or the first network device; or The one or more measurement requirements or the one or more measurement auxiliary information are stored in a unified data repository (UDR).

50. A method comprising: At the fourth network device, information is sent to the third network device to trigger at least one quality of service (QoS) measurement through at least one data network user plane interface and at least one network node of the data network via the communication network, wherein the information for triggering the at least one QoS measurement includes at least one of one or more measurement requirements or one or more measurement auxiliary information.

51. An apparatus comprising: A component for triggering at least one quality of service (QoS) measurement of at least one data network user plane interface and at least one network node of the data network through a communication network; as well as A component for sending a configuration including one or more measurement parameters to at least one second network device, the one or more measurement parameters being used for at least one QoS measurement via the at least one data network user plane interface.

52. An apparatus comprising: A component for receiving a configuration including one or more measurement parameters from a first network device, the one or more measurement parameters being used for at least one quality of service (QoS) measurement via at least one interface between the second network device and at least one network node of the data network; as well as A component for performing the at least one QoS measurement based on the configuration including the one or more measurement parameters.

53. An apparatus comprising: Components for determining a measurement target based on at least one of the one or more measurement requirements or the one or more measurement auxiliary information included in the information used to trigger the at least one QoS measurement; as well as Components for transmitting one or more measurement parameters to the PCF or the first network device; or A component that stores one or more measurement parameters in the UDR.

54. An apparatus comprising: A component for sending information to a third network device for triggering at least one quality of service (QoS) measurement of at least one data network user plane interface and at least one network node of the data network through a communication network, wherein the information for triggering the at least one QoS measurement includes at least one of one or more measurement requirements or one or more measurement auxiliary information.

55. A non-transitory computer-readable medium comprising program instructions for causing a device to perform the method according to any one of claims 47 to 50.

Images