Title - METHOD IMPLEMENTED BY AN APPLICATION FUNCTION, AF, A NETWORK EXPOSURE FUNCTION, NEF, A USER DATA REPOSITORY, UDR, AND APPLICATION FUNCTION, AF, EXPOSURE FUNCTION NEF, AND USER DATA REPOSITORY, UDR

Abstract

Methods and devices for application service at the edge are disclosed. According to one embodiment, an application function (AF) sends, to a network exposure function (NEF) or a policy control function (PCF), an indicator that signals whether an application associated with the AF requires discovery of the application server at the edge (EAS) supported by the EAS discovery function (EASDF).

Description

METHODS AND APPARATUS FOR BORDER APPLICATION SERVICES Technical Field

[0001] The realizations of disclosure generally refer to communication and, more particularly, to methods and apparatus for the service of applications at the frontier. Background

[0002] This section introduces aspects that may facilitate a better understanding of this disclosure. Accordingly, the statements in this section should be read in this manner and should not be understood as admissions of what is in the prior art or what is not in the prior art.

[0003] Figure 1 illustrates the 5th generation (5G) architecture for non-roaming backup edge computing (with the uplink [UL] / branch point [BP] classifier [CL]). The network function (NF) of the Edge Application Server (EAS) Discovery Function (EASDF) defined for the architecture's backup edge computing has the ability to influence an application's Domain Name System (DNS) query at the edge in such a way that the EAS discovery considers a candidate user equipment (UE) topological location of a Protocol Data Unit (PDU) session anchor (PSA) even further out (more suitable) in the network than the current PSA.

[0004] The EASDF includes, for example, the following functionalities: handling DNS messages according to the Session Management Function (SMF) instruction, which includes receiving DNS message handling rules from SMF, exchanging DNS messages from the UE, forwarding DNS messages to Central DNS (C-DNS) or Local DNS (L-DNS) for DNS querying, adding extension mechanisms for the DNS Client Subnet Option (ECS) (EDNS) in DNS querying for a complete domain name 1909059 of 71 qualified (FQDN), and notify SMF of EASDF-related information; and terminate DNS security, if used.

[0005] The instructions provided by the SMF to the EASDF on how to handle DNS messages depend on how the applications at the edge are used at the different available / applicable edges. In other words, the EAS discovery procedure permitted by the EASDF depends on the availability of EAS implementation information in the 5G core network (5GC).

[0006] In an edge computing implementation, an application service can be delivered by multiple edge application servers, typically deployed at different sites. These multiple edge application servers hosting the application service can use a single Internet Protocol (IP) address (anycast address) or different IP addresses. To initiate an edge application service, the UE must know the IP addresses of the application servers delivering the service at that edge. The UE can perform a discovery process to obtain the IP addresses of a suitable edge application server (e.g., the closest one) so that traffic can be routed locally to the edge application server, service latency, traffic routing path, and user experience can be optimized.

[0007] EAS discovery is the procedure by which a UE discovers the IP addresses of a suitable application server at the border using DNS. EAS rediscovery is the EAS discovery procedure that occurs when the previously discovered application server at the border cannot be used or may have become suboptimal (e.g., in a border relocation) and a new application server at the border must be used.

[0008] The DNS server can be deployed in different locations on the network as a C-DNS resolver / server or as an L2 resolver / server 1909059 of 71 DNS. To provide a translation of an EAS's FQDN to the address of an EAS as topologically close as possible to the UE, the DNS can use the following information: the source IP address of the incoming DNS query; and / or an EDNS client subnet option (ECS) (as defined in the Request for Comments [RFC] 7871). If UE applications want to discover / access the EAS using the mechanisms defined in this 3rd Generation Society Project (3GPP) Technical Memorandum (TS) 23.548 V1.0.0, the DNS queries generated by the UE will be sent to the EASDF as the DNS resolver designated by the SMF. Summary

[0009] This summary is provided to introduce a selection of concepts in a simplified form, which are further described below in the detailed description. This summary is not intended to identify key features or essential characteristics of the claimed object, nor is it intended to be used to limit the scope of the claimed object.

[0010] One of the objectives of this disclosure is to provide an improved solution for serving applications at the edge. In particular, one of the problems to be addressed in this disclosure is that the existing solution for providing EAS deployment information can be problematic in terms of bandwidth requirements and implementation complexity.

[0011] According to a first aspect of the disclosure, a method is provided that performs an application function (AF). The method may comprise sending, a network exposure function (NEF), or a policy control function (PCF), an indicator that signals whether an application associated with the AF requires application server discovery at the border (EAS) supported by the EAS discovery function (EASDF).

[0012] In this way, it is possible to reduce the bandwidth required and implementation complexity to provide EAS implementation information. 1909059 of 71

[0013] In one realization of disclosure, the indicator may be sent to the NEF in a request to influence traffic routing for the application.

[0014] In a disclosure realization, the request may be an Nnef_TrafficInfluence_Create request or an Nnef_TrafficInfluence_Update request.

[0015] In one realization of the disclosure, the indicator may be sent to the PCF in a request to create or update a policy for a protocol data unit (PDU) session associated with the application.

[0016] In a disclosure realization, the request may be an Npcf_PolicyAuthorization_Create request or an Npcf_PolicyAuthorization_Update request.

[0017] According to a second aspect of the disclosure, a method implemented by a NEF is provided. The method may comprise obtaining an indicator that signals whether an application associated with an AF requires the discovery of EAS supported by EASDF.

[0018] In this way, it is possible to reduce the bandwidth required and implementation complexity to provide EAS implementation information.

[0019] In a realization of the disclosure, obtaining the indicator may involve receiving the indicator from the AF.

[0020] In a realization of the disclosure, obtaining the indicator may involve receiving, from the AF, information to derive the indicator. Obtaining the indicator may also involve determining the indicator based on the information received.

[0021] In a realization of the disclosure, the information to derive the indicator may be an identifier that identifies the application.

[0022] In one realization of disclosure, the indicator or information to derive the indicator may be received from the AF in a request to influence traffic routing for the application.

[0023] In a disclosure realization, the request may be an Nnef_TrafficInfluence_Create request or an Nnef_TrafficInfluence_Update request. 1909059 of 71

[0024] In one embodiment of the disclosure, the method may further comprise sending the obtained indicator to a user data repository (UDR) or a policy control function (PCF).

[0025] In a disclosure realization, the obtained indicator may be sent to the PCF in a request to create or update a policy for a PDU session associated with the application.

[0026] In a disclosure realization, the request may be an Npcf_PolicyAuthorization_Create request or an Npcf_PolicyAuthorization_Update request.

[0027] According to a third aspect of the disclosure, a method implemented by a UDR is provided. The method may comprise receiving, from a NEF, an indicator that signals whether an application associated with an AF requires the discovery of EAS supported by EASDF. The method may further comprise maintaining the received indicator.

[0028] In this way, it is possible to reduce the bandwidth required and implementation complexity to provide EAS implementation information.

[0029] In one realization of the disclosure, the method may further comprise, when a PCF has subscribed to a change in traffic influence requested by the AF for application, sending the indicator to the PCF.

[0030] According to a fourth aspect of the disclosure, a method implemented by a PCF is provided. The method may comprise receiving, from a UDR or an AF or a NEF, an indicator that signals whether an application associated with the AF requires EASDF-supported discovery.

[0031] In this way, it is possible to reduce the bandwidth required and implementation complexity to provide EAS implementation information.

[0032] In one realization of the disclosure, the indicator may be received from the AF or NEF in a request to create or update a policy for a PDU session associated with the application. 1909059 of 71

[0033] In a disclosure realization, the request may be an Npcf_PolicyAuthorization_Create request or an Npcf_PolicyAuthorization_Update request.

[0034] In one embodiment of the disclosure, the method may further comprise sending the received indicator to a session management function (SMF).

[0035] In one embodiment of the disclosure, the received indicator may be sent to the SMF in a request to report updated policy information for a PDU session associated with the application.

[0036] In a disclosure realization, the request may be an Npcf_SMPolicyControl_UpdateNotify request.

[0037] According to a fifth aspect of the disclosure, a method implemented by an SMF is provided. The method may comprise receiving, from a PCF, an indicator that signals whether an application associated with an AF requires the discovery of EAS supported by EASDF.

[0038] In this way, it is possible to reduce the bandwidth required and implementation complexity to provide EAS implementation information.

[0039] In a disclosure realization, the indicator may be received from the PCF in a request to notify updated policy information for a PDU session associated with the application.

[0040] In a disclosure realization, the request may be an Npcf_SMPolicyControl_UpdateNotify request.

[0041] In one realization of the disclosure, the method may further comprise, when the indicator indicates that the application associated with the AF requires the discovery of EAS supported by EASDF, obtaining, from a NEF, EAS implementation information for the application.

[0042] In one embodiment of the disclosure, the method may further comprise, when the indicator indicates that the application associated with the AF requires discovery of EAS supported by EASDF, postponing a user plane (UP) implementation track change to a receipt of a notification from the EASDF notifying a usable EAS. 1909059 of 71

[0043] According to a sixth aspect of the disclosure, a method performed by a service consumer is provided. The method may comprise sending a request to a NEF to perform an operation related to EAS implementation information for an application. The method may also comprise receiving a response to the request from the NEF.

[0044] In this way, it is possible to reduce the bandwidth required and implementation complexity to provide EAS implementation information.

[0045] In a realization of the disclosure, the service consumer may be an AF associated with the application.

[0046] In one realization of the disclosure, the request may be to create, update, or delete EAS deployment information for the application.

[0047] In one realization of the disclosure, the request may be an Nnef_EASDeployment_Create / Update / Delete request.

[0048] In a realization of disclosure, the consumer of services may be an SMF.

[0049] In a disclosure, the request may be to subscribe or unsubscribe to a notification of a change to EAS implementation information, or to notify EAS implementation information.

[0050] In a disclosure realization, the request may be an Nnef_EASDeployment_Subscribe / Unsubscribe / Notify request.

[0051] Under a seventh aspect of the disclosure, a method performed by a NEF is provided. The method may comprise receiving, from a service consumer, a request to perform an operation related to EAS implementation information for an application. The method may further comprise sending the service consumer a response to the request. 1909059 of 71

[0052] In this way, it is possible to reduce the bandwidth required and implementation complexity to provide EAS implementation information.

[0053] In a realization of the disclosure, the service consumer may be an AF associated with the application.

[0054] In one realization of the disclosure, the request may be to create, update, or delete EAS deployment information for the application.

[0055] In one realization of the disclosure, the request may be an Nnef_EASDeployment_Create / Update / Delete request.

[0056] In a realization of disclosure, the service consumer may be an SMF.

[0057] In a disclosure realization, the request may be to subscribe or unsubscribe to a notification of a change to EAS implementation information, or to notify EAS implementation information.

[0058] In a disclosure realization, the request may be an Nnef_EASDeployment_Subscribe / Unsubscribe / Notify request.

[0059] Under an eighth aspect of the disclosure, a method performed by a UDR is provided. The method may comprise receiving, from a NEF, a request to perform an operation related to EAS implementation information for an application. The method may further comprise sending, to the NEF, a response to the request.

[0060] In this way, it is possible to reduce the bandwidth required and implementation complexity to provide EAS implementation information.

[0061] In one realization of the disclosure, the request may be to create, update, or delete EAS implementation information for the application.

[0062] In one realization of the disclosure, the request may be a Nudr_DM_Create / Update / Delete request. 1909059 of 71

[0063] According to a ninth aspect of the disclosure, an AF is provided. The AF may comprise at least one processor and at least one memory. At least one memory may contain instructions executable by at least one processor, by which the AF may be operational to send, to a NEF or a PCF, an indicator signaling whether an application associated with the AF requires EAS, the discovery supported by EASDF.

[0064] In one realization of the disclosure, the AF can function to execute the method according to the first aspect above.

[0065] According to a tenth aspect of the disclosure, a NEF is provided. The NEF may comprise at least one processor and at least one memory. At least one memory may contain instructions executable by at least one processor, by which the NEF can be operational to obtain a flag indicating whether an application associated with an AF requires EAS discovery supported by EASDF.

[0066] In one realization of the disclosure, the NEF can function to execute the method according to the second aspect above.

[0067] According to an eleventh aspect of the disclosure, a UDR is provided. The UDR may comprise at least one processor and at least one memory. At least one memory may contain instructions executable by at least one processor, whereby the UDR may be operational to receive, from a NEF, an indicator signaling whether an application associated with AF requires the discovery of EAS supported by EASDF. The UDR may further function to maintain the received indicator.

[0068] In one realization of the disclosure, the UDR can function to execute the method according to the third aspect above.

[0069] According to a twelfth aspect of the disclosure, a PCF is provided. The PCF may comprise at least one processor and at least one memory. At least one memory may contain instructions executable by at least one processor, whereby the PCF can be operative to receive, from a UDR or an AF or a NEF, an indicator signaling whether a 1909059 of 71 application associated with AF requires EAS discovery supported by EASDF.

[0070] In an implementation of the disclosure, the PCF can function to execute the method according to the fourth aspect above.

[0071] According to a thirteenth aspect of the disclosure, an SMF is provided. The SMF may comprise at least one processor and at least one memory. At least one memory may contain instructions executable by at least one processor, whereby the SMF can be operative to receive, from a PCF, a flag indicating whether an application associated with an AF requires the discovery of EAS supported by EASDF.

[0072] In an implementation of the disclosure, the SMF can function to execute the method according to the fifth aspect above.

[0073] According to a fourteenth aspect of the disclosure, a service consumer is provided. The service consumer may comprise at least one processor and at least one memory. At least one memory may contain instructions executable by at least one processor, by which the service consumer can function to send, to a NEF, a request to perform an operation related to EAS implementation information for an application. The service consumer can further function to receive, from the NEF, a response to the request.

[0074] In an implementation of the disclosure, the service consumer can function to execute the method according to the sixth aspect above.

[0075] According to a fifteenth aspect of the disclosure, a NEF is provided. The NEF may comprise at least one processor and at least one memory. At least one memory may contain instructions executable by at least one processor, whereby the NEF can be operational to receive, from a service consumer, a request to perform an operation related to EAS implementation information for an application. The NEF can further function to send a response to the service consumer. 1909059 of 71

[0076] In an implementation of the disclosure, the NEF can function to execute the method according to the seventh aspect above.

[0077] According to a sixteenth aspect of the disclosure, a UDR is provided. The UDR may comprise at least one processor and at least one memory. At least one memory may contain instructions executable by at least one processor, whereby the UDR can be operational to receive, from a NEF, a request to perform an operation related to EAS implementation information for an application. The UDR can further function to send, to the NEF, a response to the request.

[0078] In one realization of the disclosure, the UDR can function to execute the method according to the eighth aspect above.

[0079] According to a seventeenth aspect of the disclosure, a computer program product is provided. The computer program product may contain instructions that, when executed by at least one processor, cause the processor to execute the method according to any of the first through eighth aspects above.

[0080] According to an eighteenth aspect of the disclosure, a computer-readable storage medium is provided. The computer-readable storage medium may store instructions that, when executed by at least one processor, cause the processor to execute the method according to any of the first through eighth aspects above.

[0081] According to a nineteenth aspect of the disclosure, an AF is provided. The AF may comprise a dispatch module for sending, to a NEF or a PCF, a flag indicating whether an application associated with the AF requires EASDF-supported EAS discovery.

[0082] Pursuant to a twentieth aspect of the disclosure, a NEF is provided. The NEF may comprise a fetch module for obtaining an indicator that signals whether an AF-associated application requires EAS-supported discovery by EASDF. 1909059 of 71

[0083] According to a twenty-first aspect of the disclosure, a UDR is provided. The UDR may comprise a receive module to receive, from a NEF, an indicator that signals whether an application associated with an AF requires EAS discovery supported by EASDF. The UDR may further comprise a maintainer module to maintain the received indicator.

[0084] According to a twenty-second aspect of the disclosure, a PCF is provided. The PCF may comprise a receiver module for receiving, from a UDR or an AF or a NEF, an indicator signaling whether an application associated with the AF requires EASDF-supported EAS discovery.

[0085] According to a twenty-third aspect of the disclosure, an SMF is provided. The SMF may comprise a receiver module to receive, from a PCF, an indicator signaling whether an application associated with an AF requires EAS discovery supported by EASDF.

[0086] According to a twenty-fourth aspect of the disclosure, a service consumer is provided. The service consumer may comprise a send module to send, to a NEF, a request to perform an operation related to EAS implementation information for an application. The service consumer may further comprise a receive module to receive, from the NEF, a response to the request.

[0087] According to a twenty-fifth aspect of the disclosure, a NEF is provided. The NEF may comprise a receive module to receive, from a service consumer, a request to perform an operation related to EAS implementation information for an application. The NEF may further comprise a send module to send, to the service consumer, a response to the request.

[0088] Pursuant to a twenty-sixth aspect of the disclosure, a UDR is provided. The UDR may comprise a receiver module to receive, from a NEF, a request to perform an operation related to EAS implementation information for an application. The UDR may 1909059 of 71 also include a submission module to send a response to the request to the NEF.

[0089] According to a twenty-seventh aspect of the disclosure, a method is provided that is implemented in a communication system that includes any two or more of the AF, NEF, UDR, PCF, and SMF as per aspects nine through thirteen above or aspects nineteen through twenty-third. The method may comprise all the steps of the methods carried out by any two or more of the AF, NEF, UDR, PCF, and SMF.

[0090] Pursuant to an eighteenth aspect of the disclosure, a communication system is provided. The communication system may comprise any two or more of the AF, NEF, UDR, PCF, and SMF as per aspects nine through thirteen above or aspects nineteen through twenty-third.

[0091] Pursuant to a twenty-ninth aspect of the disclosure, a method is provided that is implemented in a communication system involving any two or more of the service consumer, the NEF, and the UDR, as described in aspects fourteen through sixteen above or aspects twenty-four through twenty-six. The method may comprise all steps of the methods carried out by any two or more of the service consumer, the NEF, and the UDR.

[0092] Pursuant to a thirtieth aspect of the disclosure, a communication system is provided. The communication system may comprise any two or more of the following: the service consumer, the NEF, and the UDR, as per aspects fourteenth through sixteenth above or aspects twenty-fourth through twenty-sixth. Brief description of the drawings

[0093] These and other objects, features and advantages of disclosure will become evident from the following detailed description of illustrative realizations of these, which should be read in connection with the accompanying drawings. 1909059 of 71

[0094] Figure 1 is a diagram illustrating the 5G architecture for non-roaming backup edge computing;

[0095] Figure 2 is a diagram showing an example communication system in which a disclosure realization can be applied;

[0096] Figure 3 is a flowchart illustrating a method performed in an AF according to an embodiment of the disclosure;

[0097] Figure 4 is a flowchart illustrating a method performed in an NEF according to an embodiment of the disclosure;

[0098] Figure 5 is a flowchart to explain the method in Figure 4;

[0099] Figure 6 is a flowchart illustrating a method performed in an NEF according to an embodiment of the disclosure;

[00100] Figure 7 is a flowchart illustrating a method performed in a UDR according to an embodiment of the disclosure;

[00101] Figure 8 is a flowchart illustrating a method performed in a UDR according to an embodiment of the disclosure;

[00102] Figure 9 is a flowchart illustrating a method performed in a PCF according to an embodiment of the disclosure;

[00103] Figure 10 is a flowchart illustrating a method performed in a PCF according to an embodiment of the disclosure;

[00104] Figure 11 is a flowchart illustrating a method performed on an SMF according to an embodiment of the disclosure;

[00105] Figure 12 is a flowchart illustrating a method performed on an SMF according to one realization of the disclosure;

[00106] Figure 13 is a flowchart illustrating a method performed on a service consumer according to an embodiment of the disclosure;

[00107] Figure 14 is a flowchart illustrating a method performed in an NEF according to an embodiment of the disclosure;

[00108] Figure 15 is a flowchart illustrating a method performed in a UDR according to an embodiment of the disclosure; 1909059 of 71

[00109] Figure 16 is a flowchart illustrating an exemplary process according to one realization of the disclosure.

[00110] Figure 17 is a flowchart illustrating an exemplary process according to one realization of the disclosure.

[00111] Figure 18 is a flowchart illustrating an exemplary process according to one realization of the disclosure.

[00112] Figure 19 is a flowchart illustrating an exemplary process according to one realization of the disclosure.

[00113] Figure 20 is a flowchart illustrating an exemplary process according to one realization of the disclosure.

[00114] Figure 21 is a block diagram showing equipment suitable for practicing some disclosure achievements.

[00115] Figure 22 is a block diagram showing an AF according to one realization of the disclosure;

[00116] Figure 23 is a block diagram showing an NEF according to one realization of the disclosure;

[00117] Figure 24 is a block diagram showing a UDR according to one realization of the disclosure;

[00118] Figure 25 is a block diagram showing a PCF according to one realization of the disclosure;

[00119] Figure 26 is a block diagram showing an SMF according to one realization of the disclosure;

[00120] Figure 27 is a block diagram showing a service consumer according to one realization of the disclosure;

[00121] Figure 28 is a block diagram showing an NEF according to one realization of the disclosure and

[00122] Figure 29 is a block diagram showing a UDR according to one realization of the disclosure. Detailed description 1909059 of 71

[00123] For the purposes of explanation, the following description stipulates details to provide a comprehensive understanding of the disclosed embodiments. However, it is evident to those skilled in the art that the embodiments can be implemented without these specific details or with an equivalent arrangement.

[00124] The current solution specifies that the AF provides EAS implementation information (the list of FQDNs supported by application servers for each data network access identifier [DNAI], the ranges of IP addresses that correspond to each application server for each DNAI, and the DNS server identifier [consisting of the IP address and port] for each DNAI) in the UDR as additional information to the information specified for AF's influence on traffic routing, as specified in 3GPP TS 23.501 V17.1.1, section 5.6.7.

[00125] 3GPP defines a Policy Control and Load (PCC) architecture that enables policy and load control management across the network. This architecture is defined in 3GPP TS 23.503 (5G) or TS 23.203 (EPS). For simplicity, the description in this document is based on the 5GC architecture. Similar technology also exists in EPC. The PCF is a functional element that comprises policy control decision-making and flow-based load control functionalities. The PCF provides network control with respect to the discovery, selection, quality of service (QoS), and flow-based load (excluding credit management) of service data flow to the SMF. The PCF receives session and media-related information from the AF and reports traffic plane events to the AF.

[00126] The PCF will provide PCC standards to the SMF through reference point N7. The PCF will inform the SMF, using the PCC standards, of the treatment of each service data flow that was under PCC control, in accordance with PCF policy decisions. This treatment includes specific treatment for computing applications in the 1909059 of 71 border. The SMF / UPF includes the detection of service data flow according to the filter definitions included in the PCC standard and the implementation of policies.

[00127] The currently specified procedure requires that EAS implementation information be provided in the PCC standard for each application service. Although a viable option, it presents the following problems.

[00128] First, the purpose of a PCC rule (providing policy decisions that need to be implemented by the SMF) is completely distorted, as it would be to provide general EAS implementation information of the purpose required by the SMF for the actual implementation instruction indicated by the PCC rule. From the inventors' point of view, based on the information in the PCC rule, what should be sufficient is an indication that, for a given application, the EAS discovery supported by EASDF must be implemented "now." This is because the EAS implementation information must be available to the SMF, for any PDU session that may require it, independently.

[00129] Second, providing EAS deployment information within the PCC standard increases the bandwidth required for PCC standard provisioning. When multiple UEs access the same application servers, this increased bandwidth proportionally increases the number of PDU sessions that are triggered. Third, effectively storing EAS deployment information in the SMF also increases in complexity.

[00130] This disclosure proposes an improved solution for the application service at the border. The basic idea is to decouple the provision of EAS deployment information from the provision of the PCC standard. Specifically, a new service (which may be called Nnef_EASDeployment) can be defined to allow an AF to 1909059 of 71 Create / update / delete EAS implementation information in the 5GC when interacting with the NEF, and allow the SMF to subscribe (and extract the currently provided EAS implementation information), to subscribe and be notified about EAS implementation changes. Accordingly, the request data for border computing (AF traffic influence data) can be defined in the UDR, to allow the storage of the provided EAS implementation information. With the new service, an SMF can be enabled to quickly and efficiently extract the EAS implementation information required to appropriately influence the DNS query so that the appropriate L-DNS and local border can be determined for the requested UE traffic.Furthermore, it protects the 5GC network from the creation of duplicate resources by means of the NEF which implements conflict detection and provides accurate information to AF so that they can resolve the conflict according to needs / requirements, thus making AF information and 5GC network information consistent after an AF failure.

[00131] An indication of whether the specified application requires procedures related to EAS discovery from the boundary computing (and therefore interaction with the EASDF) can also be introduced into the AF's influence on traffic routing data. For example, this indication can be derived from the NEF based on the AF's received service identifier and then provided in the UDR or N5 interface, as appropriate. The PCF can then include it in the related PCC rule. Since only the indication is included in the PCC rule, it can avoid additional bandwidth usage in the PCC rule request / provisioning procedure and additional storage capacity in the SMF.

[00132] From here on, the solution will be described in detail with reference to Figures 2-29. Figure 2 is a diagram showing an example communication system in which an implementation of the 1909059 of 71 disclosure. As shown, the communication system comprises a user equipment (UE), a radio access network (RAN), a user plane function (UPF), a data network (DN), an authentication server function (AUSF), an access and mobility management function (AMF), a session management function (SMF), a user data repository (UDR), a network segment selection function (NSSF), a network exposure function (NEF), a network repository function (NRF), a policy control function (PCF), a unified data management (UDM), and an application function (AF). The functional description of the above entities is specified in clause 6 of 3GPP 23.501 V17.1.1 TS, which is incorporated herein in full by reference.

[00133] It should be noted that, within the context of this disclosure, the term UE or terminal device used herein may also be referred to as, for example, device, access terminal, mobile station, mobile unit, subscriber station, or similar terms. It may refer to any end device that can access and receive services from a wireless communication network. By way of example, and not as a limitation, the UE or terminal device may include a laptop computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback device, a mobile phone, a cell phone, a smartphone, a tablet, a wearable device, a personal digital assistant (PDA), or similar devices.

[00134] In an Internet of Things (IoT) scenario, a UE or end device can represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE or end device and / or to network equipment. In this case, the UE or end device can be a machine-to-machine (M2M) device, which, in a 3GPP context, may be referred to as a machine-type communication (MTC) device. Some specific examples of such machines or devices may include sensors, measuring devices, etc. 1909059 of 71 such as power meters, industrial machinery, bicycles, vehicles or personal or household appliances, e.g. refrigerators, televisions, personal portable devices such as watches, etc.

[00135] As used herein, the term “communication system” refers to a system that complies with any suitable communication standard, such as first-generation (1G), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G communication protocols and / or any other protocol now known or that may be developed in the future. Furthermore, communication between a terminal device and a network node in the communication system may be performed according to any suitable generation communication protocol, including, but not limited to, 1G, 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G communication protocols and / or any other protocol now known or that may be developed in the future.Furthermore, the specific terms used in this document do not limit this disclosure only to the communication system related to the specific terms, which may nevertheless be applied more generally to other communication systems.

[00136] Figure 3 is a flowchart illustrating a method implemented in an AF according to one embodiment of the disclosure. Note that the network function (or network entity) mentioned herein can be implemented either as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on a suitable platform, e.g., in a cloud infrastructure. In block 302, the AF sends a flag to a NEF or PCF indicating whether an application associated with the AF requires EAS discovery supported by EASDF. For example, the flag can be configured by an entity associated with the application (e.g., an operator that owns or deploys the application). There can be two cases. In the first case, the AF can request to influence traffic routing for a session not identified by a UE address.In the first case, the indicator can. 1909059 of 71 can be sent to the NEF in a request to influence traffic routing for the application. For example, the request could be an Nnef_TrafficInfluence_Create request or an Nnef_TrafficInfluence_Update request. In the second case, the AF's request to influence traffic routing can be directed to an individual UE address. In this second case, the flag can be sent to the PCF in a request to create or update a policy for a PDU session associated with the application. For example, the request could be an Npcf_PolicyAuthorization_Create request or an Npcf_PolicyAuthorization_Update request. Note that, in the second case, the flag can also be sent to the NEF in a request to influence traffic routing for the application.With the method in Figure 3, since the indicator is provided, it is possible to include this indicator (instead of the EAS implementation information for the application) in the PCC standards provided to SMF, thereby reducing the bandwidth required and implementation complexity to provide EAS implementation information.

[00137] Figure 4 is a flowchart illustrating a method implemented in a NEF according to one implementation of the disclosure. In block 402, the NEF obtains a flag indicating whether an application associated with an AF requires EAS discovery supported by EASDF. For example, as shown in Figure 5, there can be two options for implementing block 402. As the first option, in block 402-1, the NEF receives the flag from the AF. As the second option, blocks 402-2 and 402-3 can be implemented. In block 402-2, the NEF receives information from the AF to derive the flag. For example, the information to derive the flag can be an identifier that identifies the application (e.g., an AF service that identifies an AF service that may be a subservice of the application). The flag or the information to derive the flag can be received from the AF in a request to influence traffic routing for the application.In block 402-3, the NEF determines the indicator based on the information received. For example, this may be. 1909059 of 71 is performed by using a preconfigured table that indicates, for each of a plurality of specified applications, whether the application requires EAS discovery supported by EASDF. With the method in Figure 4, since the indicator is obtained, it is possible to include this indicator (instead of the EAS implementation information for the application) in the PCC rules provided to SMF, thus reducing the bandwidth required and implementation complexity for providing EAS implementation information.

[00138] Figure 6 is a flowchart illustrating a method implemented in a NEF according to an embodiment of the disclosure. As shown, the method comprises block 402 described above and block 604. In block 604, the NEF sends the obtained flag to either a UDR or a PCF. For example, in the first case above, where the AF might request to influence traffic routing for a session not identified by a UE address, the flag might be sent to the UDR. In the second case above, where the AF's request to influence traffic routing might be directed to an individual UE address, the flag might be received from the AF or sent to the PCF. For example, the obtained flag might be sent to the PCF in a request to create or update a policy for a PDU session associated with the application.As an example, the request might be an Npcf_PolicyAuthorization_Create request or an Npcf_PolicyAuthorization_Update request.

[00139] Figure 7 is a flowchart illustrating a method implemented in a UDR according to one implementation of the disclosure. In block 702, the UDR receives, from a NEF, an indicator that signals whether an application associated with an AF requires EAS discovery supported by EASDF. Block 702 corresponds to the first instance of block 604. In block 704, the UDR holds the received indicator. With the method in Figure 7, since the indicator is held, it is possible to include this indicator (instead of the EAS implementation information for the application) in the PCC rules provided to SMF, thereby reducing the required bandwidth. 1909059 of 71 implementation complexity to provide EAS implementation information.

[00140] Figure 8 is a flowchart illustrating a method implemented in a UDR according to an embodiment of the disclosure. As shown, the method comprises blocks 702-704 described above and block 806. In block 806, when a PCF has subscribed to a traffic influence change requested by the AF for the application, the UDR sends the indicator to the PCF. In this way, the indicator can be provided to SMF through the PCF.

[00141] Figure 9 is a flowchart illustrating a method implemented in a PCF according to an embodiment of the disclosure. In block 902, the PCF receives, from a UDR, an AF, or a NEF, a flag indicating whether an application associated with the AF requires EAS discovery supported by EASDF. In the first case above, where the AF may request to influence traffic routing for a session not identified by a UE address, the flag may be received from the UDR. In the second case above, where the AF's request to influence traffic routing may be directed to an individual UE address, the flag may be received from either the AF or the NEF. In this case, the flag may be received in a request to create or update a policy for a PDU session associated with the application. For example, the request may be an Npcf_PolicyAuthorization_Create request or an Npcf_PolicyAuthorization_Update request.With the method in Figure 9, since the indicator is received, it is possible to include this indicator (instead of the EAS implementation information for the application) in the PCC standards provided to SMF, thus reducing the bandwidth required and implementation complexity to provide EAS implementation information.

[00142] Figure 10 is a flowchart illustrating a method implemented in a PCF according to one embodiment of the disclosure. As shown, the method comprises block 902 described above and block 1004. In block 1909059 of 71 1004, the PCF sends the received indicator to an SMF. In the first and second cases above, the received indicator can be sent to the SMF in a request to notify updated policy information for a PDU session associated with the application. For example, the request could be an Npcf_SMPolicyControl_UpdateNotify request.

[00143] Figure 11 is a flowchart illustrating a method implemented in an SMF according to one embodiment of the disclosure. In block 1102, the SMF receives, from a PCF, a flag indicating whether an application associated with an AF requires EAS discovery supported by EASDF. Block 1102 corresponds to block 1004. With the method in Figure 11, since the flag is received by the SMF, it is possible to reduce the bandwidth required and implementation complexity for providing EAS implementation information.

[00144] Figure 12 is a flowchart illustrating a method implemented in an SMF according to an embodiment of the disclosure. As shown, the method comprises block 1102 described above and blocks 1204-1206. In block 1204, when the indicator shows that the application associated with the AF requires the discovery of EAS supported by EASDF, the SMF obtains EAS implementation information for the application from a NEF. This can be accomplished using a new service introduced between the SMF and the NEF, which will be described later. In block 1206, when the indicator shows that the application associated with the AF requires the discovery of EAS supported by EASDF, the SMF postpones the implementation of the UP track switch until it receives a notification from the EASDF notifying a usable EAS. In this way, the implementation of the UP track switch can be performed at a suitable time.

[00145] Figure 13 is a flowchart illustrating a method performed on a service consumer according to an embodiment of the disclosure. In block 1302, the service consumer sends a request to a NEF to perform an operation related to EAS implementation information. Block 1909059 of 71 is used for an application. As a first option, the service consumer can be an AF (Application Function) associated with the application. For this option, the request can be to create, update, or delete EAS deployment information for the application. For example, the request might be a request named Nnef_EASDeployment_Create / Update / Delete. As a second option, the service consumer can be an SMF (Service Function). For this option, the request can be to subscribe to or unsubscribe from notification of a change to the EAS deployment information, or to notify the EAS deployment information. For example, the request might be a request named Nnef_EASDeployment_Subscribe / Unsubscribe / Notify. In block 1304, the service consumer receives a response to the request from the NEF (Network Entity Facility).Using the method in Figure 13, it is possible to reduce the bandwidth required and implementation complexity to provide EAS implementation information.

[00146] Figure 14 is a flowchart illustrating a method implemented in a NEF according to an embodiment of the disclosure. In block 1402, the NEF receives a request from a service consumer to perform an operation related to EAS deployment information for an application. As a first option, the service consumer can be an AF associated with the application. For this option, the request can be to create, update, or delete EAS deployment information for the application. For example, the request might be a request named Nnef_EASDeployment_Create / Update / Delete. As a second option, the service consumer can be an SMF. For this option, the request can be to subscribe to or unsubscribe from notification of a change to the EAS deployment information, or to notify the EAS deployment information.As an example, the request might be an Nnef_EASDeployment_Subscribe / Unsubscribe / Notify request. In block 1402, the NEF sends a response to the service consumer. Using the method in Figure 14, it is possible to reduce the required bandwidth. 1909059 of 71 implementation complexity to provide EAS implementation information.

[00147] Figure 15 is a flowchart illustrating a method implemented in a UDR according to an embodiment of the disclosure. In block 1502, the UDR receives a request from a NEF to perform an operation related to EAS deployment information for an application. For example, the request might be to create, update, or delete EAS deployment information for the application. As an example, the request might be a Nudr_DM_Create / Update / Delete request. In block 1504, the UDR sends a response to the request back to the NEF. The method in Figure 15 can reduce the bandwidth required and the implementation complexity for providing EAS deployment information.

[00148] Based on the above description, the following changes are suggested to 3GPP TS 23.501 17.1.1, where the added content is highlighted with underlines and the content within “[[...]]” refers to the content proposed for removal. The main change is to include a new indication in the AF influence traffic data that the application service refers to an EAS permitted by the EASDF. 5.6. 7.1 General Table 5.6.7-1: Information element contained in the AF application 1909059 of 71 Information Name Applicable to PCF or NEF (NOTE 1) Applicable to NEF only Category Traffic Description Defines the target traffic to be influenced, represented by the combination of DNN and optionally S-NSSAI, and the application identifier or the traffic that filters the information. The target traffic can be represented by AFService-Identifier, instead of the combination of DNN and optionally S-NSSAI. Required Possible Application Locations Indicates the possible application locations, represented by a list of DNAIs. The possible application locations can be represented by AF-Service-Identifier. Conditional (NOTE 2) 1909059 of 71 Target UE Identifiers Indicates the UEs to which the request is directed, i.e., an individual UE, a group of UEs represented by the internal group identifier (NOTE 3), or any UE accessing the combination of DNN, S-NSSAI, and DNAI. GPSI can be used to identify the individual UE, or the external group identifier can be used to identify a group of UEs. Required Spatial Validity Condition Indicates that the request applies only to traffic from UEs located in the specified location, represented by validity areas. The specified location can be represented by a list of geographic area identifiers. Optional AF Transaction Identifier The AF transaction identifier refers to the AF request. N / A Required 1909059 of 71 N6 Traffic Routing Requirements: Routing of the Profile ID and / or N6 traffic routing information corresponding to each DNAI and an optional indication of traffic correlation. N / A Optional (NOTE 2) Application Relocation Possibility: Indicates whether an application can be relocated once an application location is selected by the 5GC. N / A Optional UE IP Address Retention Indication: Indicates that the UE IP address can be retained. N / A Optional Time Validity Condition: Time intervals or durations. N / A Optional 1909059 of 71 Information about AF subscription to relevant SMF events Indicates whether the AF subscribes to a PDU session UP path change and the parameters of this subscription. N / A Optional Information for EAS IP replacement in 5GC Indicates the source EAS identifier and the target EAS identifier (i.e., IP addresses and port numbers of the source and target EAS). N / A Optional User plane latency requirement Indicates the user plane latency requirements. N / A Optional AF change information N / A Indicates the AF instance relocation and relocation information. Optional Indication for EAS relocation Indicates the EAS relocation of the applications. N / A Optional 1909059 of 71 Indication of the EC application permitted by EASDF. This information may be represented by AFService-Identifier. Optional information applied for EC application traffic with EASDF interaction for DNS message handling in 5GC. NOTE 1: When the AF request is directed to existing or future PDU sessions of multiple UEs or any UE and is sent through the NEF, as described in clause 6.3.7.2, the information is stored in the UDR by the NEF and reported to the PCF by the UDR. NOTE 2: The possible application locations and N6 traffic routing requirements may be absent only if the request is for subscription to notifications about UP path management events only. NOTE 3: The internal group ID may be used only by an operator-controlled AF and only towards the PCF. NOTE 3: AF relocation information is applicable for NEF interaction only and is not stored in UDR nor transferred to a PCF, even for case AF that directly interacts with PCF. 4) Indication for the relocation of the EAS. This indicates the applications that will be relocated. 3) Indication of the EC application permitted by EASDF. This indicates that the application traffic is applicable for the activation of the EC service and 5GC takes control of DNS message management through EASDF intervention. When PCC rules are activated, the SMF may take into account, according to local policies, the information in the PCC rules and, optionally, the 1909059 of 71 service experience analytics and / or DN performance analytics by UP path (which includes UPF instance and / or DNAI and / or AS) as defined in clause 6.4.3 and clause 6.14.3, respectively, where TS 23.288

[86] for the following: - (Re)select UP paths (including DNAI) for PDU sessions. The SMF is responsible for managing the mapping between the UE location (TAI / Cell-Id) and DNAI associated with UPFs and applications, and for selecting the UPFs that serve a PDU session. This is described in clause 6.3.3. If the PDU session is of the IP type and if the PCC rules specify the preservation of the UE IP address, the SMF must preserve the UE IP address by not reselecting the related PSA UPF once the PSA UPF is selected, for the traffic identified in the PCC rules. If the user plane latency requirement is included in the PCC rules, the SMF chooses the PSA UPF that satisfies the user plane latency requirement.If the PCC rules are related to a 5G VN group served by the SMF and if the N6 traffic routing requirements information includes an indication of traffic correlation, the SMF must select a frequent DNAI for the 5G VN group PDU sessions. - Configure traffic directed to the UPF, including activation mechanisms for multi-directed traffic or implementation of a UL classifier (UL CL). These mechanisms are defined in clause 5.6.4. This may include the SMF providing the UPF with packet handling instructions (i.e., PDR and FAR) to direct traffic for local access to the DN. The packet handling instructions are generated by the SMF using the traffic routing policy ID and / or the N6 traffic routing information in the PCC rules that corresponds to the applied DNAI. In the case of UP path reselection, the SMF may configure the source UPF to forward traffic to the UL CL / BP so that the traffic is directed to the target UPF. 1909059 of 71 - If information regarding AF's subscription to the relevant SMF events has been provided in the relevant PCC standard, inform AF about the (re)selection of the UP pathway (UP pathway change). If the information includes an indication of "AF acknowledgment is required," the SMF may decide to wait for a response from AF before activating the new UP pathway, as described in clause 5.6.7.2. - if the indication of activation of the EC application has been provided in the PCC standard, the SMF will postpone implementation of the UP pathway change until receipt of notification from the EASDF as described in TS 23.548

[130] . 6.2.5.0 NEF Functionality - Support for UAS NF functionality: Details are defined in TS 23.256

[136] . - Support for the functionality of the EAS implementation: Details are defined in TS 23.548

[130] . 7.2.8 NEF Services The following NF services are specified for NEF: Table 7.2.8-1: NF services provided by NEF Service Name Description Reference in TS 23.502 [3] or other TS Nnef_EventExposure Provides support for event exposure. 5.2.6.2 Nnef_AKMA AKMA application key derivation service TS 33.535

[124] Nnef EASDeployment EAS deployment service. TS 23.548

[130] 1909059 of 71

[00149] It is suggested that the following changes be made to 3GPP TS 23.503 17.1.0, where added content is highlighted with underlines and content within “[[...]]” refers to content proposed for removal. Specifically, the NEF stores the above information in the UDR or forwards it to the PCF using the N5 interface. The PCF uses this information to construct the PCC standard, which will later include this indication. The indication of EC application permitted by EASDF indicates whether it applies the activation of EC application traffic with the interaction of the EASDF for handling DNS messages in 5GC. 6.3.1 General Table 6.3.1: PCC standard information in 5GC 1909059 of 71 Information Name Description Category PCF allowed to modify a dynamic PCC rule in the SMF Differences compared to Table 6.3 in TS 23.203 [4] Rule Identifier Uniquely identifies the PCC rule within a PDU session. Used between the PCF and SMF for reference PCC rules. Mandatory No None ... Implementation control of AF-influenced traffic routing (NOTE 18) This part describes the information required for AF-influenced traffic routing. 1909059 of 71 Information Name Description Category PCF allowed to modify a dynamic PCC rule in the SMF Differences compared to Table 6.3 in TS 23.203 [4] Data Network Access Identifier Target Data Network Access Identifiers (DNAIs). Defined in clause 5.6.7 of TS 23.501 [2]. Yes Added According to DNAI: Traffic directed to the policy identifier Reference to a preconfigured traffic routing policy in the SMF (NOTE 19). Yes Added 1909059 of 71 Information Name Description Category PCF allowed to modify a dynamic PCC rule in the SMF Differences compared to Table 6.3 in TS 23.203 [4] According to DNAI: N6 Traffic Routing Information Describes the information required for traffic routing in the DNAI. Described in clause 5.6.7 of TS 23.501 [2] (NOTE 19). Yes Added 1909059 of 71 Information Name Description Category PCF allowed to modify a dynamic PCC rule in the SMF Differences compared with table 6.3 in TS 23.203 [4] Information on AF subscription to UP change events Indicates whether notifications in the case of a UP path change are requested and optionally indicates whether acknowledgment of notifications should be awaited (as defined in clause 5.6.7 of TS 23.501 [2]). Yes Added 1909059 of 71 Information Name Description Category PCF allowed to modify a dynamic PCC rule in the SMF Differences compared to Table 6.3 in TS 23.203 [4] EU IP address retention indication Indicates that the EU IP address may be retained. Defined in clause 5.6.7 of TS 23.501 [2]. Yes Added 1909059 of 71 Information Name Description Category PCF allowed to modify a dynamic PCC rule in the SMF Differences compared to Table 6.3 in TS 23.203 [4] Traffic Correlation Indication Indicates that target PDU sessions are to be correlated via a frequent DNAI in the user plane. Described in clause 5.6.7 of TS 23.501 [2]. Yes Added User Plane Latency Requirements Information Indicates user plane latency requirements. (See TS 23.548

[33] ). Yes Added 1909059 of 71 Information Name Description Category PCF allowed to modify a dynamic PCC rule in the SMF Differences compared to Table 6.3 in TS 23.203 [4] Information for EAS IP replacement in 5GC Indicates the source EAS identifier and the target EAS identifier (i.e., IP addresses and port numbers of the source and target EAS). (See clause 5.6.7 of TS 23.501 [2]). Yes Added 1909059 of 71 Information Name Description Category PCF allowed to modify a dynamic PCC rule in the SMF Differences compared to Table 6.3 in TS 23.203 [4] Indication of EC application allowed_____by EASDF Indicates whether EC application activation applies to the target traffic with the EASDF for DNS message handling in 5GC. Yes Added NBIFOM related control information This part describes the PCC rule information related to NBIFOM. 1909059 of 71 Information Name Description Category PCF allowed to modify a dynamic PCC rule in the SMF Differences compared to Table 6.3 in TS 23.203 [4] Access type allowed The access to be used for traffic identified by the PCC rule. Deleted The AF-influenced traffic routing implementation control contains: - a set of DNAIs (i.e., a reference to the DNAIs that the SMF must consider for UPF selection / reselection), an optional indication of traffic correlation and, depending on the DNAI, a traffic-directed policy identifier (i.e., a reference to a traffic-directed policy preconfigured in the SMF), and / or corresponding N6 traffic routing information (where N6 traffic routing information is explicitly provided as part of the AF's influence request, as described in clause 5.6.7 of TS 23.501 [2]), or; 1909059 of 71 - an AF subscription parameter to UP change events containing the subscription information defined in clause 5.2.8.3 of TS 23.502 [3] for the UP pathway change event ID, i.e., an indication of early and / or late notification and information on where to provide the relevant notifications (target notification address + notification correlation ID as specified in clause 4.15.1 of TS 23.502 [3]) and optionally an indication of “AF acknowledgment to be expected” to the relevant modifications as described in clause 5.6.7 of TS 23.501 [2]. - a user plane latency requirements parameter containing the AF requested information on the requirements for user plane latency defined in TS 23.548

[33] . - an indication of the EC application allowed by EASDF indicating whether it applies to activating EC application traffic with EASDF interaction for handling DNS messages in 5GC.

[00150] It is suggested that the following changes be made to 3GPP TS 23.502 17.1.0, where added content is highlighted with underlines and content within “[[...]]” refers to content proposed for removal. Specifically, EAS implementation information should be provided by NEF to SMF via UDR, not via PCF. It is proposed to remove EAS implementation information from the PCF policy authorization service and the NEF traffic influence service. Note that Figure 16 illustrates the process for section 4.3.6.2. Figure 17 illustrates the process for section 4.3.6.4. Figure 18 illustrates the process for section 4.16.5.2. 4.3.6.1 General If the AF interacts with PCF through the NEF, the NEF will perform the following mappings where necessary: - Map the AF-Service-Identifier to the DNN and S-NSSAI combination, as determined by the local configuration. 1909059 of 71 - Map the AF-Service-Identifier to a list of DNAI and routing profile IDs determined by the local configuration. The NEF can only provide this mapping when the DNAIs used by the applications are statistically defined. When the DNAIs where the applications are installed can change dynamically, the AF must provide the target DNAIs in its request along with the routing profile IDs or N6 traffic routing information. - Map the GPSI to the target UE identifier in the SUPI, according to the information received from UDM. - Map the external group identifier to the target UE identifier to the internal group identifier, based on the information received from UDM. - Map the identifiers of the geographical areas in the condition of spatial validity in areas of validity, determined by the local configuration. - Map the AF-Service-Identifier to the EC application indication allowed by EASDF, determined by the local configuration. 4.3.6.2 Processing AF requests to influence traffic routing for sessions not identified by a UE address 1. To create a new request, the AF invokes an operation of the Nnef_TrafficInfluence_Create service. The content of this service operation (AF request) is defined in clause 5.2.6.7. The request also contains a transaction ID from the AF. If the AF subscribes to events related to PDU sessions, it also indicates that it wishes to receive the corresponding notifications (AF notification reporting information). To update or delete an existing request, the AF invokes the Nnef_TrafficInfluence_Update or Nnef_TrafficInfluence_Delete service operation provided by the corresponding AF transaction ID. The Nnef_TrafficInfluence_Create service operation (initiated by the target AF) or the Nnef_TrafficInfluence_Update service operation (initiated by either the source or target AF) can be used in the case of an AF instance change. If the 1909059 of 71 The Nnef_TrafficInfluence_Update service operation requires the NEF to update the subscription resource. The Nnef_TrafficInfluence_Update service operation can include an updated notification target address. The updated subscription resource is used for the target AF. NOTE 3: If the source AF transfers the application context to the target AF, then the target AF can create a new subscription through the Nnef_TrafficInfluence_Create operation or update the existing subscription through Nnef_TrafficInfluence_Update. However, whether and how the application context transfer takes place is beyond the scope of this document. 2. The AF sends its request to the NEF. If the request is sent directly from the AF to the PCF, the AF reaches the PCF selected for the existing PDU session through configuration or by invoking the Nbsf_management_Discovery service. The NEF ensures the necessary authorization control which includes exhausting AF requests and, as described in clause 4.3.6.1, mapping from the information provided by the AF to the information required by the 5GC. (NEW) The NEF determines, based on the AF service identifier, whether the requested service is for an EAS permitted by EASDF. If so, it includes this indication in the N5 request to the PCF or in the UDR request to create / store the received information. 3. (in the case of Nnef_TrafficInfluence_Create or Update): The NEF stores the AF request information in the UDR (data set = application data; data subset = traffic influence request information by AF, data key = AF internal transaction ID, S-NSSAI and DNN and / or internal group identifier or SUPI). 1909059 of 71 NOTE 4: Both the AF internal transaction ID and S-NSSAI and DNN and / or the internal group identifier or SUPI are considered data keys when AF request information is stored in the UDR, see Table 5.2.12.2.1-1. (NEW) The NEF stores the derived indication on the EAS permitted by the EASDF in the UDR. (in the case of Nnef_TrafficInfluence_delete): The NEF removes the AF requirements in the UDR (data set = application data; data subset = information from the traffic influence request by AF, data key = internal ID of the AF transaction). NEF responds to AF. 4. PCFs that have subscribed to AF request modifications (data set = application data; data subset = AF traffic influence request information, data key = S-NSSAI and DNN and / or internal group identifier or SUPI) receive a Nudr_DM_Notify data change notification from the UDR. (NEW) The UDR notification regarding the data change includes the indication regarding the EAS permitted by the EASDF 5. The PCF determines whether existing PDU sessions are potentially impacted by the AF request. For each of these PDU sessions, the PCF updates the SMF with the corresponding new policy information about the PDU session by invoking the Npcf_SMPolicyControl_UpdateNotify service operation as described in steps 5 and 6 in clause 4.16.5. If the AF request includes a notification reporting request for the UP track change, the PCF includes in the PCC standard the information required for event reporting, which includes the notification target address pointing to the NEF or AF and the notification correlation ID containing the AF's internal transaction ID. 1909059 of 71 (NEW) The PCF provides, along with existing DNAI information, whether the application is an EASDF-permitted EAS. The PCF may, optionally, use service experience analytics via the UP pathway, as defined in clause 6.4.3, TS 23.288

[50] , to provide an updated DNAI list to the SMF. 6. When updated policy information regarding the PDU session is received from the PCF, the SMF may take appropriate steps to reconfigure the user plane of the PDU session. The SMF may consider service experience analytics and / or DN performance analytics along the UP path (i.e., including UPF instance and / or DNAI and / or AS) as defined in clauses 6.4.3 and 6.14.3, respectively, of TS 23.288

[50] before taking such steps. Examples of actions are as follows: - Determine a target DNAI and add, replace or remove a UPF in the data pathway, e.g. to function as a UL CL or branch point, e.g. as described in clause 4.3.5. - Assign a new prefix to the UE (when multi-directed IPv6 is applied). - Update the UPF in the target DNAI with new traffic routing rules. - Subscribe to notifications from the AMF for an area of ​​interest through the operation of the Namf_EventExposure_Subscribe service. - Determine whether to relocate the PSA UPF considering the user plane latency requirements provided by the AF (see clause 6.3.6 of TS 23.548

[74] ). When updated policy information regarding the (NEW) EC application enabled by EASDF[[PDU session related to EAS implementation]] is received from the PCF, the SMF can take appropriate steps to assist EAS discovery and rediscovery for the PDU session using the session analytics connectivity model, such as: 1909059 of 71 - Extract the EAS implementation information as defined in clause 6.2.3.4.1 of TS 23.548

[74] . - Provide the DNS message handling standard to forward UE DNS messages and / or report when DNS messages are detected as defined in clause 6.2.3.2.2 of TS 23.548

[74] . 7. The SMF may decide whether it is required to send the target DNAI to the AMF to trigger the SMF / I-SMF (re)selection and then report the target DNAI information for the current PDU session or for the next PDU session to the AMF through the operation of the Nsmf_PDUSession_SMContextStatusNotify service. 5.2.5.3.2 Operation of the Npcf_PolicyAuthorization_Create service Optional entries: UE identity if available, DNN if available, S-NSSAI if available, media type, media format, bandwidth requirements, sponsored data connectivity if applicable, flow description, application identifier, AF communication service identifier, AF record identifier, flow status, priority indicator, emergency indicator, application service provider, resource allocation result, AF application event identifier, a list of the corresponding DNAI and routing profile IDs or N6 traffic routing information, AF transaction ID, early and / or late notifications regarding UP path management events, temporal validity condition, spatial validity condition,Information for EAS IP replacement in 5GC and EC application permitted by EASDF indication [[and EAS implementation information]] as described in clause 5.6.7 in 23.501 [2], Background data transfer reference ID, priority sharing indicator as described in clause 6.1.3.15 in TS 23.503

[20] , lookahead control information as described in clause 6.1.3.15 in TS 23.503

[20] , port management information container and related port number, TSN AF parameters provided by the TSN AF to the, 1909059 of 71 PCF as described in clause 6.1.3.23 of TS 23.503

[20] , sets of alternative QoS-related parameters, QoS parameters to be measured, reporting frequency, reporting objective as described in clause 6.1.3.21 of TS 23.503

[20] , individual QoS parameters as described in clause 6.1.3.22 of TS 23.503

[20] , alternative service requirements (containing one or more QoS reference parameters in a prioritized order), MPS for the data transport service indicator as described in clause 6.1.3.11 of TS 23.503

[20] . 5.2.5.3.3 Operation of the Npcf_PolicyAuthorization_Update service Optional entries: media type, media format, bandwidth requirements, sponsored data connectivity if applicable, flow description, application identifier, AF communication service identifier, AF record identifier, flow status, priority indicator, application service provider, resource allocation result, AF application event identifier, a list of the relevant DNAI and routing profile IDs or N6 traffic routing information, AF transaction ID, early and / or late notifications on UP path management events, temporal validity condition, spatial validity condition, information for EAS IP replacement in 5GC and EC application permitted by EASDF indication [[and EAS implementation information]] as described in clause 5.6.7 of TS 23.501 [2], Background data transfer reference ID, priority sharing indicator as described in clause 6.1.3.15 of TS 23.503

[20] , lookahead control information as described in clause 6.1.3.15 of TS 23.503

[20] , port management information container and related port number, TSN AF parameters provided by TSN AF to PCF as described in clause 6.1.3.23 of TS 23.503

[20] , individual QoS parameters as described in clause 6.1.3.22 of TS 23.503

[20] , alternative QoS related parameter sets,. 1909059 of 71 QoS parameters to be measured, reporting frequency, reporting objective as described in clause 6.1.3.21 of TS 23.503

[20] , MPS for the data transport service indicator as described in clause 6.1.3.11 of TS 23.503

[20] . 5.2.6.7.2 Operation Nnef_TrafficInfluence_CreateOptional Inputs: UE address (IP or Ethernet) if available, GPSI if available, DNN if available, S-NSSAI if available, external group identifier if available, external application identifier or traffic filtering information, AF-Service-Identifier, a list of the DNAI and IDs of the corresponding routing profile or N6 traffic routing information, traffic correlation indication, application relocation possibility indication, UE IP address retention indication, early and / or late notifications on UP path management events, notification target address, temporal validity condition, spatial validity condition, user plane latency requirements, information for EAS IP replacement in 5GC and EC application permitted by EASDF indication [[and EAS implementation information]] as described in clause 5.6.7 of TS 23.501 [2]. 5.2.6.7.3 Operation Nnef_TrafficInfluence_Update Optional entries: Same optional information as in the Nnef_TrafficInfluence_Create entry, AF ID [[notification target address]]. 4.3.6.4 Transfer of an AF request addressed to an individual EU address to the relevant PCF Figure 4.3.6.4-1: Handling an AF request directed to an individual UE address to the relevant PCF According to the AF implementation (see clause 6.2.10 of TS 23.501 [2]), the AF can send the AF request to PCF directly, in which case step 1 is omitted, or via the NEF. 1. [Conditional] If the AF sends the AF request via NEF, the AF sends an Nnef_TrafficInfluenceCreate / Update / Delete request that is directed to a 1909059 from 71 individual UE address to the NEF. This request corresponds to an AF request to influence the routing of traffic that is directed to an individual UE address. When NEF receives a request from AF, NEF ensures the necessary authorization control and, as described in clause 4.3.6.1, maps the information provided by AF to the information required by 5GC. NEF responds to AF. (NEW) The NEF may receive an indication on the EAS allowed by the EASDF from the AF. 2. [Conditional] AF / NEF consumes the Nbsf_Management_Discovery service operation (which provides at least the UE address) to discover the relevant PCF address if the PCF address is not available in the NEF according to local configuration; otherwise, step 1 is skipped. NOTE: The AF / NEF finds the BSF according to the local configuration or using the NRF. 3. BSF provides the PCF address in the response from Nbsf_Management_Discovery to AF / NEF. 4. If step 1 was performed, NEF invokes the Npcf_PolicyAuthorization service to the PCF to transfer the AF request. If an AF sends the AF request directly to the PCF, the AF invokes the Npcf_PolicyAuthorization service and the PCF responds to the AF. (NEW) The AF / NEF may include the indication regarding the EAS permitted by the EASDF. 5. The PCF authorizes the AF's request. If the PCF determines that both requirements cannot be authorized, it rejects the AF's request. Once the PCF authorizes the AF's request, the PCF updates the SMF with the new PCC rules corresponding to the SM policy association modification procedure initiated by the PCF as described in clause 4.16.5.2. 1909059 of 71 The PCF may, optionally, use service experience analytics via the UP pathway, as defined in clause 6.4.3, TS 23.288

[50] , to provide an updated DNAI list to the SMF. When a PCC rule is received from the PCF, the SMF may take appropriate action to reconfigure the PDU session user plane, where applicable. The SMF may consider service experience analytics and / or DN performance analytics along the UP path (i.e., including UPF instance and / or DNAI and / or AS) as defined in clauses 6.4.3 and 6.14.3, respectively, of TS 23.288

[50] before taking such action. Examples of actions are as follows: - Determine a target DNAI and add, replace or remove UPF in the data path, e.g. to function as a UL CL, branch point, and / or PDU session anchor, e.g. as described in clause 4.3.5. - Assign a new prefix to the UE (when multi-directed IPv6 is applied). - Update the UPF with respect to the target DNAI with new traffic routing standards. - Subscribe to notifications from the AMF for an area of ​​interest through the operation of the Namf_EventExposure_Subscribe service. - Determine whether to relocate the PSA UPF considering the user plane latency requirements provided by the AF (see clause 6.3.6 of TS 23.548

[74] ). 4. 16.5.2 Modification of SM policy association initiated by the PCF The PCF can initiate the SM policy association modification procedure based on an internal PCF event or one triggered by other PCF peers (AF, NWDAF, CHF, UDR). Figure 4.16.5.2-1: Modification of SM policy association initiated by the PCF This procedure can be triggered by a local PCF decision or as triggered from other PCF peers (AF, NWDAF, CHF, UDR): 1909059 of 71 An SM policy association is established with the PCF as described in clause 4.16.4 before this procedure is triggered. For local analysis roaming, interaction with HPLMN is not used (e.g., steps 1b and 2). In local analysis roaming, the V-PCF interacts with the VPLMN UDR. 1a. Alternatively and optionally, the AF or NEF provides / revokes service information to the PCF, e.g., due to AF session signaling, when invoking the Npcf_PolicyAuthorization_Create request or the Npcf_PolicyAuthorization_Update service operation. The PCF responds to the AF or NEF. 1b. Alternatively and optionally, the CHF provides an expenditure limit report to the PCF as described in clause 4.16.8 and responds to the CHF. 1c. Alternatively and optionally, the UDR notifies the PCF about a policy subscription change by invoking Nudr_DM_Notify (Notification correlation id, policy data, SUPI, updated data, “PDU session policy control data” | “Other permitted usage data”); the PCF responds to the UDR. 1d. Alternatively and optionally, some internal events (e.g., timer, or local decision based on analytics information requested from and received from NWDAF) occur in the PCF. The analytics (i.e., Analytics ID) that can be requested from NWDAF are described in clause 6.1.1.3 of TS 23.503

[20] . 2. If the PCF determines that a change to the reporting of policy count status is required, it may alter the subscribed list of policy counts that use the initial, interim, or final expense limit report extraction procedures as defined in clause 4.16.8. NOTE: The PCF guarantees that the information received in steps 1 and 2 can be used for future policy decisions. 1909059 of 71 3. The PCF makes a policy decision. The PCF may determine that updated or new policy information should be sent to the SMF. In the case of non-roaming, the PCF may also decide to subscribe to a new analytics ID from NWDAF as described in clause 6.1.1.3 of TS 23.503

[20] . If the AF provided a fund data transfer reference ID in step 1a, the PCF can extract it from the UDR by invoking the Nudr_DM_Query (BDT reference ID, policy data, fund data transfer) service. 4. If the PCF has determined that the SMF needs updated policy information in step 3 or if the PCF has received a port management information container for the PDU session and related port number from the AF or NEF in step 1a, the PCF issues an Npcf_SMPolicyControl_UpdateNotify request with possibly updated policy information about the PDU session. (NEW) The PCF provides, along with existing DNAI information, whether the application is an EASDF-permitted EAS. 5. The SMF acknowledges the PCF request with a response of Npcf_SMPolicyControl_UpdateNotify. If the Npcf_SMPolicyControl_UpdateNotify request is received from a new PCF instance in the PCF set, the SMF stores the SM policy association to the new PCF instance.

[00151] It is suggested that the following changes be made to 3GPP TS 23.548 1.0.0, where added content is highlighted with underlines and content within “[[...]]” refers to content proposed for removal. Specifically, a new service, Nnef_EASDeployment, is defined in NEF to allow an AF to provide EAS deployment information at different network boundaries. Figure 19 illustrates the process corresponding to section 6.2.3.4.x. Figure 20 illustrates the process corresponding to section 6.2.3.4.1. 1909059 of 71 Provision of EAS implementation information The provision of node-level information on the EAS implementation from AF is not yet specified. This information can be provided through a new NEF service and stored in the UDR. For SMF to receive EAS deployment information from UDR, this can be done using a push-only approach for simplicity. At the node level, once a subscription is established (via NEF), any data changes in UDR will be reported to SMF. The "immediate report indication" can be used to extract the initial state of the EAS deployment information. Sub-notification procedures allow SMF to receive EAS deployment information for an application identifier from NEF when a PCC standard with that application identifier (subject to EC activation with DNS control) is provided / activated and the EAS deployment information is not available in SMF. In addition, “permitted delay” provides the AF with flexibility to provide EAS implementation information in advance (similar to the provision of PFD). 6.2.3.2.2 EAS discovery procedure with EASDF In the event that the UE DNS query must be handled by the EASDF, the following applies. - The AF can provide EAS deployment information to the UDR via NEF, which includes the list of FQDNs supported by the applications [[for each DNAI]], the IP address ranges corresponding to each DNAI, and the DNS server identifier (consisting of the IP address and port) for each DNAI, as defined in clause [[5.6.7 of TS 23.501 [2]. The AF can update the information as described in clause 4.3.6.2 of TS 23.502 [3]]] 6.2.3.4. SMF can extract the EAS deployment information from NEF as described in 6.2.3.4 or has preconfigured local information. 1909059 of 71 - During the PDU session establishment procedure, the SMF obtains [[the EAS implementation information via]] the PDU session [[related to]] policy information from PCF [[or the SMF is preconfigured with the EAS implementation information]] and the SMF selects an EASDF and provides its address to the UE as the DNS server to be used for the PDU session. NOTE 6: To avoid overloading the SMF caused by mass reporting, the overload control mechanisms defined in clause 6.4 of TS 29.500 [9] may be used. The information for constructing the EDNS client subnet option or the local DNS server address provided by the SMF to the EASDF is part of the DNS message handling rules for handling DNS queries originating from the UE. This information is related to the DNAIs for the FQDNs for the UE's location. The SMF can provide the DNS message handling rules for handling DNS queries from the UE to the EASDF when the SMF establishes the association with the EASDF for the UE and can update the rules at any time while the association exists. For the selection of the candidate DNAI for an FQDN for the UE, the SMF may consider the UE's location, the EAS deployment information of the network topology, and the policy information for the PDU session related to the information provided, modified, or deleted by the PCF as defined in TS 23.503[4] clause 6.4 [[or be preconfigured in the SMF]]. The EAS implementation information is provided by the AF through the procedure described in clause 6.2.3.4.xo preconfigured in the SMF. [[of the influence of AF on the second traffic routing defined in clause 5.6.7.1 of TS 23.501 [2] and in clause 4.3.6.2 of TS 23.502 [3].]]After UE mobility, if the information provided by the EDNS client subnet option or the local DNS server address needs to be updated, the SMF may. 1909059 of 71 send an update to DNS messages that forward the rules to the EASDF. NOTE 7: To protect the SMF (e.g., the DOS block from the EASDF), the EASDF IP address for the DNS query request is only accessible from the UE IP address via UPF. [[Editor's note: The procedure for providing the AF with EAS implementation information is FFS.]] 16. The SMF can perform UL CL / BP and local PSA selection and insert UL CL / BP and local PSA. Based on EAS information received from the EASDF, other UPF selection criteria as specified in clause 6.3.3 of TS 23.501 [2], and DN service experience or performance analysis for a border application as described in TS 23.288

[10] , the SMF can determine the DNAI and the associated N6 traffic routing information for the DNAI. The SMF can perform UL CL / BP and local PSA selection and insertion as described in TS 23.502 [3]. In the case of UL CL, the traffic discovery rules and traffic routing rules are determined by the SMF based on the IP address ranges according to the DNAI included in the EAS implementation information. [[PCC rules as defined in clause 5.6.7 of TS 23.501 [2].Or the SMF determines traffic detection rules and traffic routing rules based on IP address ranges according to the DNAI included in the preconfigured EAS implementation information.]]. 6.2 .3.3 EAS rediscovery procedure in a boundary relocation 2. This step can be carried out as part of step 1a / 1b. The SMF performs the procedure for modifying the requested network PDU session in step 3b-11b as defined in clause 4.3.3.2 TS 23.502 [3]. If the UE has indicated that it supports refreshing locally stored EAS information that corresponds to the impact field as indicated by the 1909059 of 71 EAS rediscovery from the network, the SMF can send the impact field with the EAS rediscovery indication. The SMF determines the affected EAS that must be rediscovered as follows: - If an L-PSA is inserted / relocated / deleted, the SMF determines the impact field, which is associated with the L-DN being inserted, relocated, or deleted and is identified by FQDN or the IP address ranges of the old EAS, according to the association between FQDN / IP address ranges and DNAI [[received from]] provided by AF [[through AF-influenced traffic routing implementation control information in PCC rules]] or in the SMF's local configuration on the L-DN. - For EAS rediscovery triggered by AF, AF can indicate that EAS rediscovery for impacted applications, which are identified by the application identifier[[FQDN]], is to be sent to the SMF through the AF influence procedure on traffic routing. 6.2.3.4 Management of node-level EAS implementation information The procedures for managing node-level EAS implementation information are described in this clause. These procedures are independent of any PDU session and include: - the procedure for information on the implementation of EAS management in the SMF[[, and]]; - the procedure for the information on the implementation of EAS management in the EASDF[[.]];_y - the procedure for the implementation information of EAS management in the NEF. 6.2.3.4.1 Information on the implementation of EAS management in the SMF The SMF can receive EAS implementation information from the NEF via [[UDR via NEF via pull mode or]] push mode as shown in the figure below. The NEF extracts EAS implementation information from UDR unless it is already available in the NEF. 1909059 of 71 [[Editor's note: It is FFS if the interaction between SMF and UDR must go through NEF. Editor's note: If both pull and push modes are needed, it's FFS.]] [[For Pull mode: 1. SMF can invoke Nnef_EASDeployment_Fetch (DNN and / or DNAI) and / or applications to the NEF. SMF can fetch all EAS deployment information for the DNN or for DNAI. 2. The NEF invokes Nudr_DM_Query (DNN and / or DNAI and / or applications) to extract EAS implementation information from UDR. 3. The UDR provides a Nudr_DM_Query response with EAS implementation information for the DNN and / or DNAI and / or applications to the NEF. 4. The NEF responds to the SMF with an Nnef_EASDeployment_Fetch response containing the EAS deployment information. For Push mode:]] 1-2. As a prerequisite for receiving push notifications, the SMF subscribes to EAS deployment information change notifications from the NEF by sending the Nnef EASDeployment Subscribe message. The SMF indicates that the current status of the EAS deployment information will be notified immediately (if available). 3-4. The NEF invokes Nnef_EASDeployment_Notify (DNN and / or DNAIs and / or applications, EAS deployment information) to the SMF to which the EAS deployment information will be provided. If EAS deployment information is available and an immediate report is required, the NEF notifies the SMF with that information. The NEF may decide to delay the distribution of the EAS deployment information to the SMF for a certain period to optimize signaling load. If the NEF received an allowable delay for EAS deployment information, the NEF will distribute this EAS deployment information within the specified time interval. The procedures allow the SMF to receive EAS deployment information from the NEF for an application identifier. 1909059 of 71 when a PCC standard with this application identifier (subject to EC activation with DNS control) is provided / activated and EAS implementation information is not available in the SMF. [[For DNNs and / or DNAIs and / or applications, when a PDU session is established for the DNN and / or DNAIs and the EAS implementation information provided by the NEF is not available in the SMF. In addition, the procedures also allow the SMF to extract the EAS implementation information from the NEF when the caching timer for the EAS implementation information elapses and there are one or more PDU sessions for this DNN and / or DNAIs and / or applications.]]It can be managed either in the full list or a subset of the EAS implementation information for one or more applications [[DNNs and / or DNAI(s), or a subset of the EAS implementation information for the individual DNN and / or DNAIs and / or applications]]. [[Editor's note: It is FFS whether it is necessary and how it supports the feature related to "caching timer" and "allowed delay".]] 6.2.3.4. x Implementation information for EAS management through the NEF Figure 6.2.3.4.x-1: Implementation information for EAS management in the AF procedure 1. The AF invokes the Nnef EASDeployment Create / Update / Delete service. The AF's service identifier or the combination of DNN and SNSSAI will be provided in the Create operation. The allowable delay is an optional parameter that indicates that EAS deployment information must be provided within the time interval specified by the allowable delay to SMFs that have subscribed to the EAS deployment management service used by the Nnef EASDeployment Subscribe service operation. 2. The NEF checks whether the AF is authorized to make this request. The NEF invokes Nudr DM Create / Update / Delete on the UDR if it is authorized. The NEF derives DNN and S-NSSAI from the AF's service identifier if it is not. 1909059 of 71 explicitly received and translates the received external application identifier to a known application identifier within the MNO domain. 3. The UDR stores / updates / deletes the corresponding information (application identifier, DNN, S-NSSAI, DNAI(s), list of FQDNs supported by the application and the EAS IP address varies according to DNAI, allowed delay) and responds to the Nudr DM Create / Update / Delete response to the NEF. 4. The NEF responds to the answer Nnef EASDeployment Create / Update / Delete to AF. 7.x NEF Services 7.x.1 General The following table illustrates NEF services and service operations. Table 7.x.1-1: NF services provided by the NEF 1909059 of 71 Service Name Operations_________of the service Semantics_____of operation Example Consumers Nnef EASDeployment Create AF Request / Response Update AF Request / Response Delete AF Request / Response Subscribe Subscribe / Notify SMF Unsubscribe SMF Notify SMF 7.x.2 Nnef EASDeployment Service 7.X.2.1 General Service description: This service allows the consumer to create, update, or delete EAS deployment information. 7.X.2.2 Operation of the Nnef EASDeployment Create service Service operation name: Nnef EASDeployment Create. Description: Create EAS deployment information in NEF. Input, required: External application identifier, AF service identifier or a combination of DNN and S-NSSAI, list of FQDNs, list of DNAIs, L-DNS IP address and port according to DNAI IP address and EAS varies by DNAI. Admission, optional: Delay allowed. Output, required: Result, transaction reference ID. Optional output: None. 7.X.2.3 Operation of the Nnef EASDeployment Update service Service operation name: Nnef EASDeployment Update. 1909059 of 71 Description: Update EAS implementation information in NEF. Input, required: Transaction reference ID, external application identifier, list of FQDNs, list of DNAIs, L-DNS IP address and port based on DNAI IP address and EAS varies by DNAI. Admission, optional: Delay allowed. Output, required: Result. Optional output: None. 7.x.2.4 Operation of the Nnef EASDeployment Delete service Service operation name: Nnef EASDeployment Delete. Description: Delete EAS deployment information in NEF. Entry, required: Transaction reference ID. Optional entry: None. Output, required: Result. Optional output: None. 7.x.2.5 Operation of the Nnef EASDeployment Subscribe service Service operation name: Nnef EASDeployment Subscribe. Description: Provided by the NEF for NF consumers to explicitly subscribe to notification of changes to EAS implementation information. Input, required: Application identifier, immediate report indication, notification target address. Entry, optional: list of DNAI, DNN and S-NSSAI. Output, required: Result, subscription correlation ID (if the result is positive). Optional output: None. 7.x.2.6 Operation of the Nnef EASDeployment Unsubscribe service Service operation name: Nnef EASDeployment Unsubscribe. Description: Provided by the NEF for NF consumers to explicitly unsubscribe from notification of changes to EAS implementation information. 1909059 of 71 Entry, required: Subscription correlation ID. Optional entry: None. Output, required: Result. Optional output: None. 7.X.2.7 Operation of the Nnef EASDeployment Notify service Service operation name: Nnef EASDeployment Notify. Description: Provided by the NEF to notify the NF consumer with EAS implementation information. Input, required: Notification correlation information, EAS implementation information. Optional entry: None. Output, required: Result. Optional output: None. The EAS implementation information consists of the application identifier, list of FQDNs, list of DNAIs, LDNS IP address and port according to the DNAI; the EAS IP address varies according to DNAI, DNN, and SNSSAI.

[00152] Figure 21 is a block diagram showing equipment suitable for practical use in some of the disclosure's implementations. For example, any of the service consumer, service provider, NRF, and NSSF implementations described above can be implemented using Apparatus 2100. As shown, Apparatus 2100 can include a processor 2110, a memory 2120 that stores a program, and optionally a communication interface 2130 for communicating data with other external devices via wired and / or wireless communication.

[00153] The program includes program instructions that, when executed by the 2110 processor, enable the 2100 computer to function in accordance with the realizations described in this disclosure, as discussed above. That is, the realizations described in this disclosure can be carried out by 1909059 of 71 less in part, by means of software that the 2110 processor can run, or by means of hardware, or by means of a combination of software and hardware.

[00154] The 2120 memory may be of any type suitable for the local technical environment and may be implemented using any appropriate data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory systems and devices, fixed memories, and removable memories. The 2110 processor may be of any type suitable for the local technical environment and may include, but is not limited to, one or more general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures.

[00155] Figure 22 is a block diagram showing an AF according to an embodiment of the disclosure. As shown, AF 2200 comprises a dispatch module 2202 configured to send, to a NEF or a PCF, an indicator signaling whether an application associated with the AF requires EASDF-supported EAS discovery.

[00156] Figure 23 is a block diagram showing a NEF according to one embodiment of the disclosure. As shown, NEF 2300 comprises a fetch module 2302 configured to fetch an indicator that signals whether an AF-associated application requires EAS-supported discovery by EASDF.

[00157] Figure 24 is a block diagram showing a UDR according to one embodiment of the disclosure. As shown, the UDR 2400 comprises a receive module 2402 and a maintain module 2404. The receive module 2402 can be configured to receive, from a NEF, an indicator that signals whether an application associated with an AF requires EAS discovery supported by EASDF. The maintain module 2404 can be configured to maintain the received indicator. 1909059 of 71

[00158] Figure 25 is a block diagram showing a PCF according to one embodiment of the disclosure. As shown, the PCF 2500 comprises a receiver module 2502 configured to receive, from a UDR or an AF or a NEF, an indicator signaling whether an application associated with the AF requires EASDF-supported EAS discovery.

[00159] Figure 26 is a block diagram showing an SMF according to one embodiment of the disclosure. As shown, the SMF 2600 comprises a receive module 2602 configured to receive, from a PCF, an indicator signaling whether an application associated with an AF requires EAS discovery supported by EASDF.

[00160] Figure 27 is a block diagram showing a service consumer according to one embodiment of the disclosure. As shown, the service consumer 2700 comprises a send module 2702 and a receive module 2704. The send module 2702 can be configured to send a request to a NEF to perform an operation related to EAS implementation information for an application. The receive module 2704 can be configured to receive a response to the request from the NEF.

[00161] Figure 28 is a block diagram showing a NEF according to one embodiment of the disclosure. As shown, the NEF 2800 comprises a receive module 2802 and a send module 2804. The receive module 2802 can be configured to receive, from a service consumer, a request to perform an operation related to EAS implementation information for an application. The send module 2804 can be configured to send a response to the request to the service consumer.

[00162] Figure 29 is a block diagram showing a UDR according to one embodiment of the disclosure. As shown, the UDR 2900 comprises a receive module 2902 and a send module 2904. The receive module 2902 can be configured to receive, from a NEF, a 1909059 of 71 request to carry out an operation related to EAS implementation information for an application. The 2904 submission module can be configured to send a response to the request to the NEF. The modules described above can be implemented by hardware, software, or a combination of both.

[00163] In general, the various exemplary embodiments can be implemented in hardware or special-purpose circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while others may be implemented in firmware or software, executed by a controller, a microprocessor, or another computing device, although disclosure is not limited to these.While several aspects of the exemplary realizations in this disclosure may be illustrated and described as block diagrams, flowcharts, or by the use of some other pictorial representation, it is well understood that these blocks, devices, systems, techniques, or methods described herein may be implemented in, as non-limiting examples, special-purpose hardware, software, firmware, circuits or logic, general-purpose hardware or controller, or other computing devices, or some combination thereof.

[00164] As such, it should be appreciated that at least some aspects of the exemplary embodiments of the disclosure can be practiced in different components, such as integrated circuit chips and modules. Thus, it should be appreciated that the exemplary embodiments of this disclosure can be realized in equipment that is incorporated as an integrated circuit, where the integrated circuit may comprise the circuitry (as well as possibly firmware) to incorporate at least one or more of a data processor, digital signal processor, baseband circuitry, and radio frequency circuitry that can be configured to operate in accordance with the exemplary embodiments of this disclosure. 1909059 of 71

[00165] It should be appreciated that at least some aspects of the exemplary embodiments of the disclosure can be incorporated into computer-executable instructions, such as in one or more program modules executed by one or more computers or devices. Generally, program modules include routines, object programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other device. Computer-executable instructions can be stored on a computer-readable medium, such as a hard disk, an optical disk, a removable storage medium, solid-state memory, RAM, etc. As will be appreciated by someone skilled in the art, the function of program modules can be combined or distributed as desired in various embodiments.Furthermore, the function may be incorporated in whole or in part into the firmware or hardware equivalents, such as integrated circuits, field-programmable gate arrays (FPGAs), and the like.

[00166] References in this disclosure to “an embodiment,” “the embodiment,” and so forth, indicate that the embodiment described may include a particular function, structure, or feature, but it is not necessary that every embodiment includes the particular function, structure, or feature. Furthermore, such phrases do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or function is described in connection with an embodiment, it is asserted that a person skilled in the art has the knowledge to implement that feature, structure, or function in connection with other embodiments, whether explicitly described or not.

[00167] It should be understood that, although the terms “first,” “second,” etc., may be used herein to describe different elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element could 1909059 of 71 may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of disclosure. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed terms.

[00168] The terminology used herein is intended to describe particular realizations and is not intended to limit the present disclosure. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It is further understood that the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including,” when used herein, specify the presence of indicated 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. The terms “connect,” “connects,” “connecting,” and / or “connected” used herein cover the direct and / or indirect connection between two elements.It should be noted that two blocks shown in succession in the figures above can, in fact, be executed substantially concurrently, or the blocks can sometimes be executed in reverse order, depending on the functionality involved.

[00169] This disclosure includes any novel features or combinations of features disclosed herein, whether explicitly stated or by generalization. Several modifications and adaptations to the foregoing exemplary embodiments of this disclosure may be apparent to those skilled in the art when the foregoing description is read in conjunction with the accompanying drawings. However, all such modifications shall remain within the scope of the non-limiting, exemplary embodiments of this disclosure. 1909059 of 71 CLARKE MODET & CO. (ARGENTINA) SA - 30540437455 Digitally signed by PORTALTRAM ITES - INPI Date: 2022.08.04 12:41:01 -03:00 Reason: Digitally Signed by the INPI Location: Buenos Aires, Argentina 1909059

Claims

1. A method implemented by an application function, AF, characterized in that it comprises: sending (1302) to a network exposure function, NEF, a request to perform an operation related to the application server border deployment information, EAS, for an application, wherein the request is to create, update, or delete EAS deployment information; and receiving (1304) from the NEF a response to the request. Thirteen claims follow.