Providing endpoint information for latency measurement

Abstract

A method (600) performed by a first network node (202, 204, or 206) belonging to a first network, the method comprises the first network nod receives from or transmitting to (s602), a second network node (204, 202 / 206, or 204) belonging to a second network, a message including measurement endpoint information, wherein the measurement endpoint information comprises information about one or more endpoints at an edge of one of the first and second networks towards one or more entities belonging to a third network, wherein the said one of the first and second networks and the third network are different.

Description

PROVIDING ENDPOINT INFORMATION FOR LATENCY MEASUREMENTTECHNICAL FIELD

[0001] This disclosure relates to providing endpoint information for latency measurement.BACKGROUND

[0002] Generally, an edge application can be served by different edge application servers (EASs) deployed in different sites, and it is important to choose, from the different EASs, suitable EAS(s) to handle the edge application. In choosing the suitable EAS(s), various factors are considered. Examples of such factors include but are not limited to network metrics such as bandwidth and latency of networks connected to the EASs and computing metrics such as processing and / or storage capabilities of the EASs.

[0003] One of the key issues discussed in the Third Generation Partnership Project (3GPP) Technical Report (TR) 23.700-49 V0.2.0 is enhancement of EAS and local user plane function (UPF) (re)selection. The purpose of this issue is to investigate whether and how to enhance EAS and local UPF selection / reselection considering dynamic information related to EAS such as, for example, EAS load and a delay at the N6 interface (“N6 delay”) between a UPF, e.g., a local packet data unit (PDU) session anchor (PSA), and the EAS.SUMMARY

[0004] As mentioned above, when multiple EASs are available for an edge application, it is important to choose a suitable EAS to handle the edge application. Because a delay at the interface (“interface delay”) between an UPF (e.g., a PSA) belonging to a mobile network and an EAS belonging to a service network may affect whether the EAS is best suitable for handling an edge application, it may be beneficial for a 5G core (5GC) and / or a service provider (e.g., an application function (AF)) to consider the interface delay when selecting a suitable EAS for the edge application. However, in the existing art, the 5GC and / or the AF do not have endpoint information that is needed for performing a measurement of the interface delay. In order to solve this problem, in the embodiments of this disclosure, there is provided a way to provide the endpoint information to the 5GC and / or the AF.

[0005] More specifically, in one aspect of some embodiments of this disclosure, there isprovided a method performed by a first network node belonging to a first network. The method comprises receiving from or transmitting to, a second network node belonging to a second network, a message including measurement endpoint information. The measurement endpoint information comprises information about one or more endpoints at an edge of one of the first and second networks towards one or more entities belonging to a third network. Said one of the first and second networks and the third network are different.

[0006] In another aspect, there is provided a computer program comprising instructions which when executed by processing circuitry cause the processing circuitry to perform the method of any one of the above embodiments.

[0007] In a different aspect, there is provided a carrier containing the computer program of the above embodiment. The carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium.

[0008] In a different aspect, there is provided a first network node belonging to a first network. The first network node is configured to: receive from or transmitting to, a second network node belonging to a second network, a message including measurement endpoint information. The measurement endpoint information comprises information about one or more endpoints at an edge of one of the first and second networks (e.g., MNO network) towards one or more entities belonging to a third network (e.g., service network). Said one of the first and second networks and the third network are different.

[0009] In a different aspect, there is provided an apparatus comprising: processing circuitry; and a memory, said memory containing instructions executable by said processing circuitry, whereby the apparatus is operative to perform the method of any one of the above embodiments.

[0010] The embodiments of this disclosure allow providing the endpoint information to the 5GC and / or the AF, thereby allowing the 5GC and / or the AF to perform a measurement of the interface delay, and to select the most suitable local UPF and EAS considering an end-to- end delay which includes the interface delay.BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate various embodiments.

[0012] FIG. 1 shows an exemplary scenario where embodiments of this disclosure can beapplied.

[0013] FIG. 2A shows a process according to some embodiments.

[0014] FIG. 2B shows a process according to some embodiments.

[0015] FIG. 3 shows a process according to some embodiments.

[0016] FIG. 4 shows a process according to some embodiments.

[0017] FIG. 5 shows a process according to some embodiments.

[0018] FIG. 6 shows a process according to some embodiments.

[0019] FIG. 7 shows an apparatus according to some embodiments.DETAILED DESCRIPTION

[0020] FIG. 1 shows an exemplary scenario 100 where some embodiments of this disclosure can be applied. In the scenario 100, an AF 102 (e.g., a third party trusted and / or nontrusted AF) in a service network 150 determines that it needs to use edge computing to provide a service for an edge application to a user equipment (UE) in a mobile network 120. Thus the AF 102 needs to select, from EASs 108 and 118 which are currently available in the service network, the best suitable EAS to use for the edge computing. The EASs 108 and 118 are connected to UPFs 104 and 114 via endpoints in a mobile network. The endpoints are associated with DN access identifiers (DNAIs) 162 and 164. Note that the number of each of the entities (e.g., the UPFs, the EASs, etc.) shown in FIG. 1 is provided for simple explanation purpose only, and thus it does not limit the embodiments of this disclosure in any way. Also note that even though more than one UPFs and / or EASs can be selected for the particular edge application, for simple explanation purpose, it will be assumed that only one UPF and / or only one EAS is selected.

[0021] In choosing the most suitable local UPF (e.g., from the UPFs 104 and 114) and / or EAS (e.g., from the EASs 108 and 118), the AF 102 may consider various factors. Examples of such factors include but are not limited to network metrics such as the bandwidths and latencies of networks connected to the EASs and computing metrics such as the processing and / or storage capabilities of the EASs.

[0022] One of the network metrics to consider in choosing the most suitable local UPFand / or EAS is an end-to-end delay which includes a delay at a candidate interface of the network 120 (e.g., 5G network) and a candidate EAS. For example, in the scenario 100 shown in FIG. 1, one of the metrics to consider in choosing the most suitable local UPF and / or EAS from the candidate UPFs 104 and 114 and / or the candidate EASs 108 and 118 is a delay at the N6 interface 122 (“N6 delay”) between the first UPF 104 and the EAS 108 and a delay at the N6 interface 124 between the second UPF 114 and the EAS 118.

[0023] Determining the N6 delays requires that either the 5GC or the service network performs latency measurements over the N6 interfaces 122 and 124. However, certain challenges presently exist in performing the latency measurements over the N6 interfaces.

[0024] For example, in performing the latency measurements over the N6 interfaces, internet control message protocol (ICMP)-based PING (echo request) packets may be used but these packets may be blocked by an intermediate firewall for security reasons, and thus the packets may not reach to the given target endpoint. Therefore, in order to ensure that PING works across multiple administrative domains, the target domain should convey information on which IP address is enabled to get the ICMP packets though the firewalls. Then this IP address can be kept alive all the time in the target network, unlike a generic cloud IP address that may or may not be allocated to some worker at a given time.

[0025] However, PING is not very accurate as it is handled as low priority by most of the IP routers and hosts, and it may only measure round-trip delays, which makes it impossible to differentiate between network latency in the different directions. If more evolved active measurement protocols are to be used, such as, for example, One-way Active Measurement Protocol (OWAMP, RFC 4656), Two-Way Active Measurement Protocol (TWAMP, RFC 5357) or Simple Two-way Active Measurement Protocol (STAMP, RFC 8762), then the source domain should know which hosts in the target domain support which measurement protocol. Thus, the information on the given host IP address, UDP destination port and public security credentials used by the test element (a.k.a., Session-Reflector), as well as the IP address and public security credentials of the control element (in case of OWAMP / TWAMP) (which can be collectively called “measurement endpoint information”) should be conveyed to the source domain.

[0026] Accordingly, in some embodiments of this disclosure, there is provided a process 200 shown in FIG. 2A for sharing measurement endpoint information. More specifically, the process 200 is a process of a first network node 202 (e.g., the AF 102) in a first network (e.g., theservice network 150) obtaining, from a second network node 204 (e.g., the NEF 122) and / or a third network node 206 (e.g., the UDR 132) in a second network (e.g., the mobile network 120), information about endpoints at the edge of the second network towards entities in the first network.

[0027] In one example, the first network node 202 is a third party trusted or a non-trusted AF belonging to a service network, the second network node 204 is an NEF belong to a mobile network (a.k.a., a cellular network), and the third network node 206 is an UPF (e.g., UDR) belonging to the mobile network. The process 200 may begin with step s202.

[0028] The step s202 comprises the first network node 202 (e.g., the AF 102) transmitting a first message to the second network node 204 (e.g., the NEF 122). The first message may correspond to a request for measurement endpoint information. The first message may include EAS address information and / or DN access identifier(s) (DNAI(s)).

[0029] The EAS address information may comprise one or more IP addresses of one or more EASs, one or more IP address ranges of one or more EASs, and / or one or more fully qualified domain names of one and / or more EASs. For example, in the scenario 100 shown in FIG. 1, the EAS address information included in the first message may include (1) the IP address of the EAS 108, the IP address range of the EAS 108, and / or the FQDN of the E AS 108 and (2) the IP address of the EAS 118, the IP address range of the EAS 118, and / or the FQDN of the EAS 118.

[0030] The DNAI identifies a user plane access to a local part of the first network where applications are deployed. In other words, the DANI identifies a certain entry / exit point between the 5GC and an IP network. In the scenario 100 shown in FIG. 1, the DNAIs 162 and 164 included in the first message may identify a user plane access to the local part 150-1 of the service network 150 associated with the EAS 108 and a user plane access to the local part 150- 2 of the service network 150 associated with the EAS 118. After transmitting the first message to the second network node 204, the process 200 may proceed to step s208.

[0031] The step s208 comprises the second network node 204 (e.g., the NEF 122) retrieving, based on the EAS address information and / or the DNAI(s) included in the received first message, the measurement endpoint information.

[0032] The measurement endpoint information comprises information about measurement test endpoint(s) in local part(s) (e.g., 150-1 and 150-2) of the first network and / or information about measurement control endpoint(s) in the local part(s) (e.g., 150-1 and 150-2) of the first network.

[0033] The information about measurement test endpoint(s) indicates one or more of: IP address(es) of the measurement test endpoint(s) for DNAI(s), port(s) of the measurement test endpoint(s) for the DNAI(s), and / or security credential(s) of the measurement test endpoint(s) for the DNAI(s).

[0034] The information about measurement control endpoint(s) indicates one or more of: IP address(es) of the measurement control endpoint(s) for the DNAI(s), port(s) of the measurement control endpoint(s) for the DNAI(s), and / or security credential(s) of the measurement control endpoint(s) for the DNAI(s).

[0035] For example, in the scenario 100, the information about the measurement test endpoints may indicate one or more of: IP addresses of the measurement test endpoints for the DNAIs 162 and 164, ports of the measurement test endpoints for the DNAIs 162 and 164, and / or security credentials of the measurement test endpoints for the DNAIs 162 and 164. Similarly, the information about measurement control endpoints may indicate one or more of: IP addresses of the measurement control endpoints for the DNAIs 162 and 164, ports of the measurement control endpoints for the DNAIs 162 and 164, and / or security credentials of the measurement control endpoints for the DNAIs 162 and 164.

[0036] Referring back to the step s208, to retrieve the measurement endpoint information based on the EAS address information and / or the DNAI(s), the second network node 204 (e.g., the NEF 122) must have mapping information mapping the EAS address information and / or the DNAI(s) to the measurement endpoint information.

[0037] Using the mapping information, the second network node 204 (e.g., the NEF 122) can retrieve the measurement endpoint information for given EAS address information and / or a given DNAI. After retrieving the measurement endpoint information, the process 200 may proceed to step s210 in which the second network node 204 (e.g., the NEF 122) transmits to the first network node 202 (e.g., the AF 102) a second message containing the measurement endpoint information,

[0038] In some cases, the mapping information for retrieving the measurement endpoint information may not be available at the second network node 104. In those cases, the second network node 204 may obtain the mapping information from a third network node 206 (e.g., UDR 132). Alternatively, the second network node 204 may directly request the third network node 206 to provide the end point information.

[0039] More specifically, after the first network node 202 transmits the first message to the second network node 204, the process 200 may proceed to step s204 instead of the step s208.

[0040] The step s204 comprises the second network node 204 (e.g., the NEF 122) transmitting a third message to the third network node 206 (e.g., the UDR 132). The third message may correspond to a request for the mapping information or a request for the measurement endpoint information. After the second network node 204 transmits the third message to the third network node 206, the process 200 may proceed to step s206. The step s206 comprises, in response to receiving the third message, the third network node 206 transmitting to the second network node 204 a fourth message containing the mapping information or the measurement endpoint information.

[0041] In case the fourth message contains the mapping information, the process 200 may proceed to the step s208 described above. On the other hand, in case the fourth message contains the measurement endpoint information, the process 200 may skip the process s208 and may proceed to the step s210 described above.

[0042] FIG. 3 shows a process 300 which is a first implementation example of the process 200. The process may correspond to the AF request-based DNAI procedure described in 3 GPP TS 23.548 V18.5.0., Section 6.8.2, which is hereby incorporated by reference. The procedure may be used by an AF to request and obtain EAS address and DNAI mapping information with the measurement endpoint information.

[0043] The process 300 is performed by an AF, an NEF, and an UPF (e.g., UDR). In the process 300, the AF, the NEF, and the UPF correspond to the first, second, and third network nodes 202, 204, and 206 in the process 200, respectively. The process 300 comprises steps 1-5 among which the steps 2 and 3 are optional in some cases.

[0044] In step 1, the AF invokes Nnef_DNAIMapping_Subscribe service to request DNAI information. The request that the AF sends to the NEF includes EAS address information and optionally: DNN, S-NSSAI, and AF Identifier. This request may correspond to the first message transmitted in the step s202 of the process 200. If mapping information for retrieving DNAI information based on the EAS address information, the DNN, the S-NSSAI, and / or the AF identifier is stored in the NEF, the steps 2 and 3 are skipped. Otherwise the step 2 is performed next. The following table shows content of the mapping information. The EAS address and DNAI Mapping Information is enhanced to include the measurement endpoint information.

[0045] In the step 2, if the mapping information is stored in the UDR, the NEF determines the DNN and / or the S-NSSAI if not received from the AF, potentially using the AF identifier. If the NEF has not yet received the DNAI mapping information for this DNN and / or S-NSSAI, NEF invokes the Nudr DM Subscribe service to subscribe to DNAI mapping information for this DNN and / or S-NSSAI. Here, the subscription request that the NEF transmits to the UDR corresponds to the third message transmitted in the step s204 in the process 200.

[0046] In the step 3, the UDR notifies the NEF with all the DNAI mapping information for the requested DNN / S-NSSAI. Here, the notification message that the UDR transmits to the NEF corresponds to the fourth message transmitted in the step s206 in the process 200.

[0047] In the step 4, the NEF determines the suitable DNAI(s) using the DNAI mapping information. The NEF may also retrieve the corresponding measurement endpoint information - i.e., the N6 measurement test endpoint reachability information and the N6 measurement control endpoint reachability information. This step may correspond to the step s208 in the process 200.

[0048] In the step 5, NEF notifies the DNAI(s) or the updated DNAI information to theAF corresponding to the request in step 1. Here, the notification that the NEF transmits to the AF correspond to the second message transmitted in the step s210 in the process 200. Thenotification may include the retrieved measurement end point information which is shown below.

[0049] FIG. 4 shows a process 400 which is a second implementation example of the process 200. The process 400 is performed by an AF, an NEF, and an UPF (e.g., UDR). In the process 400, the AF, the NEF, and the UPF correspond to the first, second, and third network nodes 202, 204, and 206 in the process 200, respectively. The process 400 comprises steps 1-4.

[0050] In the step 1, the AF requests the NEF to provide measurement endpoint information associated with certain EAS(s). The request that the AF sends to the NEF in the step 1 includes a list of DNAI(s) for which the AF needs the measurement endpoint information. This request corresponds to the first message transmitted in the step 202 in the process 200.

[0051] After receiving the request from the AF in the step 1 , in the step 2, the NEF requests the UPF to provide to the NEF the measurement endpoint information for the given list of DNAI(s). Like the request received from the AF in the step 1, this request includes the list of DNAI(s). Note that the UPF for a given DNAI may be discovered via a network repository function (NRF) where the UPF may register its supported DNAI(s). The request sent to the UPF in the step 2 corresponds to the third message transmitted in the step s204 in the process 200.

[0052] Based on receiving the request from the NEF in the step 2, in the step 3, the UPF provides the requested measurement endpoint information to the NEF. More specifically, the UPF sends to the NEF a message containing the requested measurement endpoint information.

[0053] The measurement endpoint information may include the information provided in the following table.

[0054] In some embodiments, the message may contain any of the additional information shown below.

[0055] The message containing the measurement endpoint information may correspond to the fourth message transmitted in the step s206 in the process 200.

[0056] Note that in case the NEF already had the measurement endpoint information at the time of receiving the request in the step 1, the steps 2-3 may be skipped.

[0057] In the step 4, the NEF conveys the requested measurement endpoint information to the AF. More specifically, the NEF transmits to the AF a message containing the requested measurement endpoint information. The message containing the measurement endpoint information may correspond to the second message transmitted in the step s210 of the process 200.

[0058] The process 200 shown in FIG. 2A is a process of the first network node 202 obtaining the measurement endpoint information from the second and / or third network nodes 204 and 206. This means that, at some point in time, the second and / or third network nodes 204 and 206 must obtain the measurement endpoint information from somewhere.

[0059] FIG. 2B shows a process 250 of the second and / or third network nodes 204 and 206 obtaining measurement endpoint information associated with certain EAS(s). More specifically, in the process 250, the first network node 202 registers the measurement endpoint information associated with certain EAS(s) at the second and / or third network nodes 204 and 206.

[0060] The process 250 may begin with step s252. The step s252 comprises the first network node 202 transmitting to the second network node 204 a message including measurement endpoint information associated with certain EAS(s).

[0061] After receiving the message including the measurement endpoint information, instep s254, the second network node 204 transmits to the third network node 206 a message including the same measurement endpoint information - i.e., the measurement endpoint information that the second network node 204 received from the first network node in the step s252.

[0062] After the third network node 206 receiving the message in the step s254, in step s256, the third network node 206 stores the received measurement endpoint information. For example, in case there is no profile associated with the EAS(s), the third network node 206 may create a new profile for the EAS(s) and add the received measurement endpoint information to the new profile. In another example, in case there is already a profile associated with the EAS(s), the third network node 206 may update the profile to include the received measurement endpoint information.

[0063] After the third network node 206 storing the received measurement endpoint information, the process 250 may proceed to steps s258 and s260. In the step s258, the third network node 206 transmits to the second network node 204 a message indicating whether the measurement endpoint information is successfully stored at the third network node 206, and in the step s260, the second network node 204 transmits to the first network node 202 a message indicating whether the measurement endpoint information is successfully stored at the third network node 206.

[0064] FIG. 5 shows a process 500 which is an implementation example of the process 250. The process 500 may correspond to the EAS Deployment Information Provision procedure described in 3GPP TS 23.548 V18.5.0., Section 6.2.3.4.2, which is hereby incorporated by reference. The procedure may be used by an AF to provide non-PDU session specific EAS deployment information to 5GC. The provided EAS deployment information may be used for local UPF and EAS selection / reselection.

[0065] The process 500 is performed by an AF, an NEF, and an UPF (e.g., UDR). In the process 500, the AF, the NEF, and the UPF correspond to the first, second, and third network nodes 202, 204, and 206 in the process 200, respectively. The process 500 comprises steps 1-5.

[0066] In the step 1, the AF invokes the Nnef_EASDeployment_Create / Update service operation. This request that the AF transmits to the NEF is a request for creating or updating EAS deployment information. This request may correspond to the message transmitted in the step s252 of the process 250. The EAS deployment information may comprise one or more ofthe following parameters:

[0067] After receiving the request, in the step 2, the NEF checks whether the AF is authorized to perform the request and authorized to provision the EAS Deployment Information based on the operator policies. If the NEF determines that the AF has the authorization, then the process 500 proceeds to step 3.

[0068] In the step 3, the NEF invokes the Nudr DM Create / Update to the UDR. Like the request in the step 1, the request that the NEF transmits to the UDR in the step 3 may contain the EAS deployment information. This request may correspond to the message transmitted in the step s254 of the process 250.

[0069] In step 4, the UDR stores / updates the corresponding information received from the AF, and transmits a Nudr DM Create / Update Response to the NEF. The storing / updating step may correspond to the step s256 of the process 250 and the Response transmitted to the NEF in this step may correspond to the message transmitted in the step s258 of the process 250.

[0070] In the step 5, the NEF sends Nnef_EASDeployment_Create / Update Response to the AF. This Response may correspond to the message transmitted in the step s260 of the process 250.

[0071] In the embodiments shown in FIGS. 2A and 5, the existing EAS deployment information is enhanced to include the measurement endpoint information in the service network and the 5GC (session management function (SMF), UPF) is enhanced to use this new information in the EAS deployment information to perform the performance measurements towards the EAS(s) and enhance the EAS discovery and selection using the new information.

[0072] FIG. 6 shows a process 600 performed by a first network node (e.g., 202, 204, or 206) belonging to a first network according to some embodiments. The process 600 comprisesstep s602. The step s602 comprises receiving from or transmitting to, a second network node (e.g., 204, 202 / 206, or 204) belonging to a second network, a message including measurement endpoint information. This step corresponds to any of the step s210 in FIG. 2A, the step s252 in FIG. 2B, or the step s254 in FIG. 2B. The measurement endpoint information comprises information about one or more endpoints at an edge of one of the first and second networks (e.g., a cellular network) towards one or more entities (e.g., EASs) belonging to a third network (e.g., a service network). Said one of the first and second networks and the third network are different.

[0073] In some embodiments, the first network node is an application function, AF, the first network is a service network, the second network node is a network exposure function, NEF, the second network is a cellular network, and the first and third networks are the same.

[0074] In some embodiments, the first network node is an NEF, the first network is a cellular network, the second network node is an AF, the second network is a service network, and the second and third networks are the same.

[0075] In some embodiments, the first network node is an NEF, the first network is a cellular network, the second network node is a unified data repository, UDR, the first and second networks are the same, and the third network is a service network.

[0076] In some embodiments, the first network node is an UDR, the first network is a cellular network, the second network node is an NEF, the first and second networks are the same, and the third network is a service network.

[0077] In some embodiments, said one or more entities in the third network are one or more edge application servers, EASs.

[0078] In some embodiments, said one or more endpoints at the edge are associated with N6 interface used for communications between user plane functions, UPFs, belonging to said one of the first and second networks and the EASs belonging to the third network.

[0079] In some embodiments, the information about said one or more endpoints at the edge comprises: information about one or more measurement test endpoints in one or more local parts of the third network associated with N6 interface; and / or information about one or more measurement control endpoints in one or more local parts of the third network associated with N6 interface.

[0080] In some embodiments, the information about said one or more measurement test endpoints indicates one or more of: one or more internet protocol, IP, addresses of said one ormore measurement test endpoints for a particular DN access identifier (DNAI); one or more ports of said one or more measurement test endpoints for the DNAI; and / or one or more security credentials of said one or more measurement test endpoints for the DNAI.

[0081] In some embodiments, the information about said one or more measurement control endpoints indicates one or more of: one or more IP addresses of said one or more measurement control endpoints for the DNAI; one or more ports of said one or more measurement control endpoints for the DNAI; and / or one or more security credentials of said one or more measurement control endpoints for the DNAI.

[0082] In some embodiments, the process 600 comprises: transmitting to the second network node a subscription request for DNAI information; and based at least on transmitting the subscription request, receiving from the second network node the message including the measurement endpoint information, and the subscription request comprises one or more of: one or more IP addresses of one or more EASs; one or more IP address ranges of one or more EASs; and one or more fully qualified domain names of one and / or more EASs.

[0083] In some embodiments, the process 600 comprises: receiving, from the second network node, a subscription request for DNAI information; and based at least on receiving the subscription request, transmitting, to the second network node, the message including the measurement endpoint information, and the subscription request comprises one or more of: one or more IP addresses of one or more EASs; one or more IP address ranges of one or more EASs; and one or more fully qualified domain names of one and / or more EASs.

[0084] In some embodiments, the subscription request further comprises one or more of: a data network name, DNN, single network slice selection assistance information, S-NSSAI, and / or an AF identifier identifying the first network node.

[0085] In some embodiments, the message is a subscription response to the subscription request, and the message further comprises the requested DNAI information identifying one or more DNAIs.

[0086] In some embodiments, the process 600 comprises: transmitting to the second network node a request for the measurement endpoint information; and based at least on transmitting the request for the measurement endpoint information, receiving from the second network node the message including the measurement endpoint information, and the request for the measurement endpoint information includes a list of one or more DNAIs for which themeasurement endpoint information is needed.

[0087] In some embodiments, the process 600 comprises: receiving, from the second network node a request for the measurement endpoint information; and based at least on receiving the request for the measurement endpoint information, transmitting to the second network node the message including the measurement endpoint information. The request for the measurement endpoint information includes a list of one or more DNAIs for which the measurement endpoint information is needed.

[0088] In some embodiments, the message is a request for provisioning EAS deployment information, and the request for provisioning EAS deployment information further comprises one or more of: an AF identifier, a data network name, DNN, single network slice selection assistance information, S-NSSAI, and / or an application identifier identifying an application for which the EAS deployment information is, a FQDN for the EAS deployment information, a DNAI for the EAS deployment information, DNS server information indicating a list of DNS server identifiers, EAS IP address range information, and / or N6 traffic routing information.

[0089] FIG. 7 is a block diagram of a network node 700, according to some embodiments. The network node 700 may be used to implement any one or more of the first network node 202, the second network node 204, and the third network node 206 shown in FIGS. 2 A and 2B. As shown in FIG. 7, the network node 700 may comprise: processing circuitry (PC) 702, which comprises one or more processors (P) 755 (e.g., one or more general purpose microprocessors and / or one or more other processors, such as an application specific integrated circuit (ASIC), field-programmable gate arrays (FPGAs), and the like), which processors may be co-located in a single housing or in a single data center or may be geographically distributed (e.g., the network node 700 may be a distributed computing apparatus comprising two or more computers or a monolithic computing apparatus consisting of a single computer); at least one network interface 748 (e.g., a physical interface or air interface) comprising a transmitter (Tx) 745 and a receiver (Rx) 747 for enabling the network node 700 to transmit data to and receive data from other nodes connected to network 110 (e.g., an Internet Protocol (IP) network) to which network interface 748 is connected (physically or wirelessly) (e.g., network interface 748 may be coupled to an antenna arrangement comprising one or more antennas for enabling the network node 700 to wirelessly transmit / receive data); and a storage unit (a.k.a., “data storage system”) 708, which may include one or more non-volatile storage devices and / or one or more volatile storagedevices. In embodiments where PC 702 includes a programmable processor, a computer readable storage medium (CRSM) 742 may be provided. CRSM 742 may store a computer program (CP) 743 comprising computer readable instructions (CRI) 744. CRSM 742 may be a non-transitory computer readable medium, such as, magnetic media (e.g., a hard disk), optical media, memory devices (e.g., random access memory, flash memory), and the like. In some embodiments, the CRI 744 of computer program 743 is configured such that when executed by PC 702, the CRI causes the network node 700 to perform steps described herein (e.g., steps described herein with reference to the flow charts). In other embodiments, the network node 700 may be configured to perform steps described herein without the need for code. That is, for example, PC 702 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and / or software.

[0090] Summary of EmbodimentsAl. A method (600) performed by a first network node (202, 204, or 206) belonging to a first network, the method comprising: receiving from or transmitting to (s602), a second network node (204, 202 / 206, or 204) belonging to a second network, a message including measurement endpoint information, wherein the measurement endpoint information comprises information about one or more endpoints at an edge of one of the first and second networks (e.g., MNO network) towards one or more entities belonging to a third network (e.g., service network), wherein said one of the first and second networks and the third network are different.A2. The method of embodiment Al, wherein the first network node is an application function, AF, the first network is a service network, the second network node is a network exposure function, NEF, the second network is a cellular network, and the first and third networks are the same.A3. The method of embodiment Al, wherein the first network node is an NEF,the first network is a cellular network, the second network node is an AF, the second network is a service network, and the second and third networks are the same.A3 a. The method of embodiment Al, wherein the first network node is an NEF, the first network is a cellular network, the second network node is a unified data repository, UDR, the first and second networks are the same, and the third network is a service network.A3b. The method of embodiment Al, wherein the first network node is an UDR, the first network is a cellular network, the second network node is an NEF, the first and second networks are the same, and the third network is a service network.A4. The method of any one of embodiments Al-A3b, wherein said one or more entities in the third network are one or more edge application servers, EASs.A5. The method of embodiment A4, wherein said one or more endpoints at the edge are associated with N6 interface used for communications between user plane functions, UPFs, belonging to said one of the first and second networks and the EASs belonging to the third network.A6. The method of embodiment A5, wherein the information about said one or more endpoints at the edge comprises: information about one or more measurement test endpoints in one or more local parts of the third network associated with N6 interface; and / orinformation about one or more measurement control endpoints in one or more local parts of the third network associated with N6 interface.A7. The method of embodiment A6, wherein the information about said one or more measurement test endpoints indicates one or more of: one or more internet protocol, IP, addresses of said one or more measurement test endpoints for a particular DN access identifier (DNAI); one or more ports of said one or more measurement test endpoints for the DNAI; and / or one or more security credentials of said one or more measurement test endpoints for the DNAI.A8. The method of embodiment A7, wherein the information about said one or more measurement control endpoints indicates one or more of: one or more IP addresses of said one or more measurement control endpoints for the DNAI; one or more ports of said one or more measurement control endpoints for the DNAI; and / or one or more security credentials of said one or more measurement control endpoints for the DNAI.The “Nnef DNAIMapping Subscribe” embodiment - AF (Interaction with NEF)A9. The method of any one of embodiments A2 and A4-A8, wherein the method comprises: transmitting to the second network node a subscription request for DNAI information; and based at least on transmitting the subscription request, receiving from the second network node the message including the measurement endpoint information, and the subscription request comprises one or more of: one or more IP addresses of one or more EASs; one or more IP address ranges of one or more EASs; andone or more fully qualified domain names of one and / or more EASs.The “Nnef DNAIMapping Subscribe” embodiment - NET (Interaction with AF)A9a. The method of any one of embodiments A3 and A4-A8, wherein the method comprises: receiving, from the second network node, a subscription request for DNAI information; and based at least on receiving the subscription request, transmitting, to the second network node, the message including the measurement endpoint information, and the subscription request comprises one or more of: one or more IP addresses of one or more EASs; one or more IP address ranges of one or more EASs; and one or more fully qualified domain names of one and / or more EASs.A10. The method of embodiment A9 or A9a, wherein the subscription request further comprises one or more of: a data network name, DNN, single network slice selection assistance information, S-NSSAI, and / or an AF identifier identifying the first network node.Al l. The method of any one of embodiments A9-A10, wherein the message is a subscription response to the subscription request, and the message further comprises the requested DNAI information identifying one or more DNAIs.The embodiment of using a new service operation - AF (Interaction with NEF) or NEF (Interaction with UDR)A12. The method of any one of embodiments A2, A3a, and A4-A8, wherein the method comprises:transmitting to the second network node a request for the measurement endpoint information; and based at least on transmitting the request for the measurement endpoint information, receiving from the second network node the message including the measurement endpoint information, and the request for the measurement endpoint information includes a list of one or more DNAIs for which the measurement endpoint information is needed.The embodiment of using a new service operation - NET (Interaction with AF) or UDR (Interaction with NEF)A12. The method of any one of embodiments A2, A3a, and A4-A8, wherein the method comprises: receiving, from the second network node a request for the measurement endpoint information; and based at least on receiving the request for the measurement endpoint information, transmitting to the second network node the message including the measurement endpoint information, and the request for the measurement endpoint information includes a list of one or more DNAIs for which the measurement endpoint information is needed.The embodiment of EAS Deployment InfoA13. The method of any one of embodiments A3-A8, wherein the message is a request for provisioning EAS deployment information, and the request for provisioning EAS deployment information further comprises one or more of: an AF identifier, a data network name, DNN, single network slice selection assistance information, S-NSSAI, and / or an application identifier identifying an application for which the EAS deployment information is, a FQDN for the EAS deployment information,a DNAI for the EAS deployment information,DNS server information indicating a list of DNS server identifiers, EAS IP address range information, and / orN6 traffic routing information.Bl. A computer program (700) comprising instructions (744) which when executed by processing circuitry (702) cause the processing circuitry to perform the method of any one of embodiments Al -Al 3.B2. A carrier containing the computer program of embodiment Bl, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium.Cl. A first network node (202, 204, or 206) belonging to a first network, the first network node being configured to: receiving from or transmitting to (s602), a second network node (204, 202 / 206, or 204) belonging to a second network, a message including measurement endpoint information, wherein the measurement endpoint information comprises information about one or more endpoints at an edge of one of the first and second networks (e.g., MNO network) towards one or more entities belonging to a third network (e.g., service network), wherein said one of the first and second networks and the third network are different.C2. The first network node of embodiment Cl, wherein the first network node is configured to perform the method of any one of embodiments A2-A13.DI. An apparatus (700) comprising: processing circuitry (702); and a memory (741), said memory containing instructions executable by said processing circuitry, whereby the apparatus is operative to perform the method of any one of embodiments A1-A13.

[0091] While various embodiments are described herein, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of this disclosure should not be limited by any of the above-described exemplary embodiments. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the disclosure unless otherwise indicated herein or otherwise clearly contradicted by context.

[0092] As used herein transmitting a message “to” or “toward” an intended recipient encompasses transmitting the message directly to the intended recipient or transmitting the message indirectly to the intended recipient (i.e., one or more other nodes are used to relay the message from the source node to the intended recipient). Likewise, as used herein receiving a message “from” a sender encompasses receiving the message directly from the sender or indirectly from the sender (i.e., one or more nodes are used to relay the message from the sender to the receiving node). Further, as used herein “a” means “at least one” or “one or more.”

[0093] Additionally, while the processes described above and illustrated in the drawings are shown as a sequence of steps, this was done solely for the sake of illustration. Accordingly, it is contemplated that some steps may be added, some steps may be omitted, the order of the steps may be re-arranged, and some steps may be performed in parallel.

[0094] Appendices

[0095] Appendix #1 begins here.

[0096] Appendix #1 ends here.

[0097] Appendix #2 begins here.

[0098] Appendix #2 ends here.

Claims

Claims1. A method (600) performed by a first network node (202, 204, or 206) belonging to a first network, the method comprising: receiving from or transmitting to (s602), a second network node (204, 202 / 206, or 204) belonging to a second network, a message including measurement endpoint information, wherein the measurement endpoint information comprises information about one or more endpoints at an edge of one of the first and second networks towards one or more entities belonging to a third network, wherein said one of the first and second networks and the third network are different.

2. The method of claim 1, wherein the first network node is an application function, AF, the first network is a service network, the second network node is a network exposure function, NEF, the second network is a cellular network, and the first and third networks are the same.

3. The method of claim 1, wherein the first network node is an NEF, the first network is a cellular network, the second network node is an AF, the second network is a service network, and the second and third networks are the same.

4. The method of claim 1, wherein the first network node is an NEF, the first network is a cellular network, the second network node is a unified data repository, UDR, the first and second networks are the same, and the third network is a service network.

5. The method of claim 1, wherein the first network node is an UDR, the first network is a cellular network, the second network node is an NEF, the first and second networks are the same, and the third network is a service network.

6. The method of any one of claims 1-4, wherein said one or more entities in the third network are one or more edge application servers, EASs.

7. The method of claim 6, wherein said one or more endpoints at the edge are associated with N6 interface used for communications between user plane functions, UPFs, belonging to said one of the first and second networks and the EASs belonging to the third network.

8. The method of claim 7, wherein the information about said one or more endpoints at the edge comprises: information about one or more measurement test endpoints in one or more local parts of the third network associated with N6 interface; and / or information about one or more measurement control endpoints in one or more local parts of the third network associated with N6 interface.

9. The method of claim 8, wherein the information about said one or more measurement test endpoints indicates one or more of: one or more internet protocol, IP, addresses of said one or more measurement test endpoints for a particular DN access identifier (DNAI); one or more ports of said one or more measurement test endpoints for the DNAI; and / or one or more security credentials of said one or more measurement test endpoints for the DNAI.

10. The method of claim 9, wherein the information about said one or more measurement control endpoints indicates one or more of:one or more IP addresses of said one or more measurement control endpoints for theDNAI; one or more ports of said one or more measurement control endpoints for the DNAI; and / or one or more security credentials of said one or more measurement control endpoints for the DNAI.

11. The method of any one of claims 2 and 6-10, wherein the method comprises: transmitting to the second network node a subscription request for DNAI information; and based at least on transmitting the subscription request, receiving from the second network node the message including the measurement endpoint information, and the subscription request comprises one or more of: one or more IP addresses of one or more EASs; one or more IP address ranges of one or more EASs; and one or more fully qualified domain names of one and / or more EASs.

12. The method of any one of claim 3 and 6-10, wherein the method comprises: receiving, from the second network node, a subscription request for DNAI information; and based at least on receiving the subscription request, transmitting, to the second network node, the message including the measurement endpoint information, and the subscription request comprises one or more of: one or more IP addresses of one or more EASs; one or more IP address ranges of one or more EASs; and one or more fully qualified domain names of one and / or more EASs.

13. The method of claim 11 or 12, wherein the subscription request further comprises one or more of: a data network name, DNN,single network slice selection assistance information, S-NSSAI, and / or an AF identifier identifying the first network node.

14. The method of any one of claim 11-13, wherein the message is a subscription response to the subscription request, and the message further comprises the requested DNAI information identifying one or more DNAIs.

15. The method of any one of claims 2, 4 and 6-10, wherein the method comprises: transmitting to the second network node a request for the measurement endpoint information; and based at least on transmitting the request for the measurement endpoint information, receiving from the second network node the message including the measurement endpoint information, and the request for the measurement endpoint information includes a list of one or more DNAIs for which the measurement endpoint information is needed.

16. The method of any one of claims 2, 4 and 6-10, wherein the method comprises: receiving, from the second network node a request for the measurement endpoint information; and based at least on receiving the request for the measurement endpoint information, transmitting to the second network node the message including the measurement endpoint information, and the request for the measurement endpoint information includes a list of one or more DNAIs for which the measurement endpoint information is needed.

17. The method of any one of claims 3-10, wherein the message is a request for provisioning EAS deployment information, andthe request for provisioning EAS deployment information further comprises one or more of: an AF identifier, a data network name, DNN, single network slice selection assistance information, S-NSSAI, and / or an application identifier identifying an application for which the EAS deployment information is, a FQDN for the EAS deployment information, a DNAI for the EAS deployment information,DNS server information indicating a list of DNS server identifiers,EAS IP address range information, and / orN6 traffic routing information.

18. A computer program (700) comprising instructions (744) which when executed by processing circuitry (702) cause the processing circuitry to perform the method of any one of claims 1- 16.

19. A carrier containing the computer program of claim 17, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium.

20. A first network node (202, 204, or 206) belonging to a first network, the first network node being configured to: receiving from or transmitting to (s602), a second network node (204, 202 / 206, or 204) belonging to a second network, a message including measurement endpoint information, wherein the measurement endpoint information comprises information about one or more endpoints at an edge of one of the first and second networks (e.g., MNO network) towards one or more entities belonging to a third network (e.g., service network), wherein said one of the first and second networks and the third network are different.

21. The first network node of claim 19, wherein the first network node is configured to perform the method of any one of claim 2-16.

22. An apparatus (700) comprising: processing circuitry (702); and a memory (741), said memory containing instructions executable by said processing circuitry, whereby the apparatus is operative to perform the method of any one of claims 1-16.

Images