Providing intra-network computing services in cellular core network

Abstract

A User Equipment, UE, (1) for a cellular network, a plurality of control plane network functions (2 to 4) of a cellular network, and corresponding methods (5 to 8) of operating the UE and the control plane network functions are disclosed. The UE (1) is configured to discover (12) an edge application service, EAS, of a cellular network, where the EAS comprises an in-network computing service based on a network function entity, cNF (4), in a core network of the cellular network. The UE (1) is further configured to establish (13) a protocol data unit (PDU) session based on the discovered EAS. This enables an application service provider (ASP) to deploy intra-network application logic (IN-AL) for its own application service in the 3GPP core domain.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and more particularly to providing in-network computing (INC) in a core network domain of a cellular network. Background Art

[0002] Traditionally, network equipment for cellular networks is vendor-specific. Functions such as network protocols supported by traditional network equipment are pre-installed and difficult to upgrade after deployment because the onboard hardware chipsets are statically designed and packaged according to predefined specifications.

[0003] With the rapid development of programmable technology, this limitation is being alleviated. Currently, programmable network processing units (NPUs) are widely used, and the performance of programmable network devices is comparable to that of traditional network devices. By using the popular P4 language to write scripts that are then compiled, deployed, and executed on programmable chips, network devices can be programmed according to application logic for packet processing. This provides opportunities for customized network infrastructure.

[0004] The programmability of network infrastructure has inspired the concept of in-network computing (INC). The INC concept refers to the deployment of non-standardized dedicated computing logic directly on network elements in the forwarding path of the 3GPP core network. Using intermediate computing logic, processing tasks can be started earlier before reaching the endpoint where the actual application server is located.

[0005] According to the definition of 3GPP, the computing tasks of the application layer (relative to the network layer) are regarded as application services to be provided in the data network (DN) outside the 3GPP network domain. In addition, the European Telecommunications Standards Institute (ETSI) has defined a network architecture called "multi-access edge computing (MEC)" to realize cloud / edge computing capabilities at the edge of the cellular network.

[0006] That is, the 3GPP network only provides connections from user equipment (UE) to the DN or MEC system. If an application service provider (ASP) wants to deploy in-network application logic (IN-AL) for its application in the 3GPP core network domain, this is not supported by current mobile network systems (such as 5G), especially control plane (CP) operations. Summary of the invention

[0007] The object is to overcome these and other disadvantages. This object is achieved by the subject matter of the independent claims. Further implementations are apparent from the dependent claims, the description and the drawings.

[0008] According to a first aspect, a user equipment (UE) for a cellular network is provided. The UE is configured to discover an edge application service (EAS) of the cellular network, wherein the EAS includes an in-network computing (INC) service based on a network function entity cNF in a core network of the cellular network. The UE is also configured to establish a protocol data unit (PDU) session based on the discovered EAS.

[0009] This enables the UE to discover and request the provision of INC services in the core network, where the INC service offloads the existing EAS hosted outside the cellular network in the data network (DN) domain by pre-processing and / or terminating user plane traffic.

[0010] Edge application service (EAS) as used in this article may refer to computing services associated with edge application servers hosted in the DN domain. Edge computing enables operators and third-party services to be hosted close to the UE's access attachment point, enabling efficient service delivery as end-to-end latency and load on the transport network are reduced.

[0011] The INC used in this article may refer to deploying non-standardized dedicated computing logic directly on the network element of the forwarding path of the 3GPP core network.

[0012] The network function entity or computing network function (cNF) used in this document may particularly refer to the user plane function of the 3GPP core network that implements non-standardized dedicated computing logic. Since the user plane function is deployed in the 3GPP core network, it may also be called in-network application logic (IN-AL).

[0013] In a possible implementation, in order to discover EAS, the UE may also be configured to send a discovery request to an edge application service discovery function (EASDF) of the cellular network. The discovery request may include: an identifier of the EAS; a domain name service (DNS) name of the EAS; a query indication of the support of the in-network computing service for the EAS; an identifier of the required version of the in-network computing service; and a query indication of the configuration of the cNF that terminates the EAS.

[0014] In a possible implementation, in order to discover the EAS, the UE may also be configured to receive a discovery response from the EASDF. The discovery response may include: an identifier of the EAS; a locator address of the EAS including the in-network computing service and / or a locator address of the corresponding EAS not including the in-network computing service; a response indication of the in-network computing service's support for the EAS; an identifier of the version of the in-network computing service; and a response indication of the configuration of the cNF that terminates the EAS.

[0015] In a possible implementation, in order to establish a PDU session, the UE may also be configured to send a PDU session request to a session management function (SMF) of the cellular network. The PDU session request may include: a locator address of an EAS of an in-network computing service.

[0016] In a possible implementation, in order to establish a PDU session, the UE may also be configured to receive a PDU session request acceptance from the SMF. The PDU session request acceptance includes a locator address for the UE to access the EAS including the in-network computing service.

[0017] According to a second aspect, a session management function (SMF) for a cellular network is provided. The SMF is configured to establish a PDU session for an edge application service (EAS) based on the cellular network. The EAS includes an in-network computing service based on a registered network function entity cNF.

[0018] This enables the SMF to provide PDU sessions in the core network that include INC services, where the INC services offload existing EAS hosted outside the cellular network in the DN domain by pre-processing and / or terminating user plane traffic.

[0019] In a possible implementation, in order to establish a PDU session, the SMF may be configured to receive a PDU session request from a user equipment (UE) of a cellular network. The PDU session request may include: a locator address of an EAS including an in-network computing service.

[0020] In one possible implementation, in order to establish a PDU session, the SMF may also be configured to select a cNF from a plurality of registered cNFs of the cellular network; send a configuration request to the selected cNF; and receive a configuration response from the selected cNF. The configuration request may include one or more of an entry point of a subsequent cNF of the selected cNF in the EAS and a termination rule of the EAS. The configuration response may include a locator address for the UE to access the EAS including the in-network computing service.

[0021] In a possible implementation, in order to establish a PDU session, the SMF may also be configured to send a PDU session request acceptance to the UE. The PDU session request acceptance may include a locator address, which is used for the UE to access the EAS including the in-network computing service.

[0022] According to a third aspect, an edge application service discovery function (EASDF) for a cellular network is provided. The EASDF is configured to register a network function entity (cNF) with a core network of the cellular network. The EASDF is also configured to notify an edge application service (EAS) of the cellular network. The EAS includes an in-network computing service based on the network function entity (cNF).

[0023] This enables the EASDF to register in the core network and provide information about INC services, which offload existing EAS hosted outside the cellular network in the DN domain by pre-processing and / or terminating user plane traffic.

[0024] In a possible implementation, in order to register the cNF, the EASDF may also be configured to receive a registration request from the cNF; process the configuration file of the cNF according to the registration request; and send a registration response to the cNF. The registration request may include one of the following: an instruction to create the configuration file of the cNF at the registration entity; an instruction to update the configuration file of the cNF at the registration entity; an instruction to notify the configuration file of the cNF at the registration entity; an instruction to delete the configuration file of the cNF at the registration entity.

[0025] The registration request may also include: an identifier of the EAS; a mapping of the domain name service (DNS) name of the cNF to a locator address of the EAS including in-network computing services; an indication that the cNF terminates the EAS; an identifier of a subsequent cNF of the cNF in the EAS; an indication of support for analysis data collection for the cNF; and an indication of a service area of ​​the cNF.

[0026] In one possible implementation, in order to notify EAS, the EASDF may also be configured to receive a discovery request from a user equipment (UE) of a cellular network; cooperate with a query entity of the cellular network to resolve the discovery request; and send a discovery response to the UE. The discovery request may include: an identifier of the EAS; a DNS name of the EAS; a query indication regarding support for EAS by the in-network computing service; an identifier of the required version of the in-network computing service; and a query indication regarding the configuration of the cNF that terminates the EAS. The discovery response may include: an identifier of the EAS; a locator address of the EAS and / or a locator address of a corresponding EAS that is not supported by the in-network computing service; a response indication regarding support for EAS by the in-network computing service; an identifier of the version of the in-network computing service; and a response indication regarding the configuration of the cNF that terminates the EAS.

[0027] The query entity of the cellular network may include one of the following: a network repository function (NRF) of the cellular network; a unified data management (UDM) entity of the cellular network; an application service provider (ASP) of the EAS.

[0028] According to a fourth aspect, a network function entity cNF for a core network of a cellular network is provided. The cNF is configured to register the cNF with a registration entity of the cellular network. The cNF is also configured to perform local configuration of the cNF for a PDU session of an edge application service (EAS) based on the cellular network. The EAS includes an in-network computing service based on the network function entity cNF.

[0029] This enables the cNF to form part of the INC service in the core network, where the INC service offloads the existing EAS hosted outside the cellular network in the DN domain by pre-processing or terminating user plane traffic.

[0030] In a possible implementation, in order to register the cNF, the cNF may also be configured to send a registration request to a registration entity of the cellular network. The cNF may also be configured to receive a registration response from the registration entity. The registration request may include one of the following: an instruction to create a configuration file of the cNF at the registration entity; an instruction to update the configuration file of the cNF at the registration entity; an instruction to notify the configuration file of the cNF at the registration entity; an instruction to delete the configuration file of the cNF at the registration entity.

[0031] In a possible implementation, the registration request may further include: an identifier of the EAS; a mapping of a domain name service (DNS) name of the cNF to a locator address of the cNF; an indication that the cNF terminates the EAS; an identifier of a subsequent cNF of the cNF in the EAS; an indication of supporting analysis data collection for the cNF; and an indication of a service area of ​​the cNF.

[0032] In a possible implementation, the registration entity may include an edge application service discovery function (EASDF) of the cellular network.

[0033] In one possible implementation, the registration entity may include a network repository function (NRF) of the cellular network.

[0034] In one possible implementation, in order to perform local configuration of the cNF for the PDU session, the cNF may also be configured to receive a configuration request from a session management function (SMF) of the cellular network; and send a configuration response to the SMF. The configuration request may include one or more of an entry point of a subsequent cNF of the cNF in the EAS and a termination rule of the EAS. The configuration response may include a locator address for the UE to access the EAS including the in-network computing service.

[0035] In one possible implementation, the cNF may include a user plane function.

[0036] According to a fifth aspect, a method for operating a user equipment (UE) for a cellular network is provided. The method includes: discovering an edge application service (EAS) of the cellular network; and establishing a protocol data unit (PDU) session based on the discovered EAS. The EAS includes an in-network computing service based on a network function entity cNF in a core network of the cellular network.

[0037] According to a sixth aspect, a method for operating a session management function (SMF) of a cellular network is provided. The method includes establishing a PDU session of an edge application service (EAS) based on the cellular network. The EAS includes an in-network computing service of a network function entity cNF in a core network based on the cellular network.

[0038] According to a seventh aspect, a method for operating an edge application service discovery function (EASDF) of a cellular network is provided. The method includes notifying an edge application service (EAS) of the cellular network. The EAS includes an in-network computing service based on a network function entity cNF in a core network of the cellular network.

[0039] According to an eighth aspect, a method for operating a network function entity cNF of a core network for a cellular network is provided. The method comprises: registering the cNF with a registration entity of the cellular network; and locally configuring the cNF for a PDU session of an edge application service (EAS) based on the cellular network. The EAS comprises an in-network computing service based on the network function entity cNF.

[0040] According to a ninth aspect, a computer program is provided, comprising a program code, and when executed on a computer, is used to perform the method according to any one of the fifth to eighth aspects or any implementation thereof.

[0041] The technical effects and advantages described above in combination with the UE of the first aspect and the control plane network functions of the second to fourth aspects are also applicable to the methods of the fifth to eighth aspects with corresponding characteristics, and also to the computer program of the ninth aspect for implementing the method. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The above-described aspects and implementations will now be explained with reference to the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements.

[0043] The drawings should be considered as schematic representations and the elements shown in the drawings are not necessarily shown to scale. Instead, various elements are shown so that their function and general purpose are apparent to a person skilled in the art.

[0044] Figure 1 An exemplary reference architecture of a 3GPP cellular network is shown;

[0045] Figure 2 The UE, related network functions and corresponding methods of operating the UE and related network functions according to the present disclosure are shown;

[0046] Figure 3 Shown in more detail Figure 2 method. DETAILED DESCRIPTION

[0047] In the following description, reference is made to the accompanying drawings that form part of the present disclosure, which illustrate specific aspects of the embodiments of the present disclosure or specific aspects of the embodiments of the present disclosure that can be used by way of illustration. It should be understood that the embodiments of the present disclosure can be used in other aspects and include structural or logical changes not depicted in the drawings. Therefore, the following detailed description should not be understood in a restrictive sense, and the scope of the present disclosure is defined by the appended claims.

[0048] For example, it should be understood that the disclosure related to the described method may also be equally applicable to the corresponding device or system configured to perform the method, and vice versa. For example, if one or more specific method steps are described, the corresponding device may include one or more units (e.g., functional units) to perform the described one or more method steps (e.g., one unit performs one or more steps, or multiple units perform one or more steps of multiple steps respectively), even if such one or more units are not explicitly described or shown in the drawings. On the other hand, for example, if a specific device is described based on one or more units (e.g., functional units), the corresponding method may include a step to perform the function of one or more units (e.g., one step performs the function of one or more units, or multiple steps perform the function of one or more units of multiple units respectively), even if such one or more steps are not explicitly described or shown in the drawings. In addition, it should be understood that unless otherwise explicitly stated, the features of the various exemplary embodiments and / or aspects described herein may be combined with each other.

[0049] Figure 1 An exemplary reference architecture of a 3GPP cellular network is shown.

[0050] Figure 1 The bottom shows the user plane (UP) elements of the forwarding path of the 3GPP network. Figure 1 The user equipment (UE) on the left and Figure 1 The right side extends between the data network (DN) domain, passing through the 3GPP (radio) access network ((R)AN) domain and the 3GPP core network (CN) domain, which includes one or more (i.e., a series of) user plane functions (UPFs), i.e., network functions (NFs) 4.

[0051] The user plane function used in this article may refer to the interconnection point between the cellular network and the DN, providing functions such as (see 3GPP TS 23.501): packet encapsulation and decapsulation, packet routing and forwarding, flow-based QoS processing, providing mobility as a protocol data unit (PDU) session anchor point, etc.

[0052] A network function as used herein may refer to one of the multiple network elements of the CN domain of a cellular network, used to provide a specific part of the overall functionality of the CN. Network functions can be roughly distinguished according to the UP / CP to which they belong. For example, UPF represents a specific type of UP NF. Most network functions can be implemented as software / computer programs for execution on commercial off-the-shelf cloud computing platforms.

[0053] The (R)AN domain and the core network domain are connected to each other through the N3 reference point.

[0054] Figure 1 The NF standardized for the 3GPP core network is omitted in the example, so that only the UPF with IN-AL is shown, which is denoted as computing network function (cNF) 4 for simplicity. The cNF used in this article may include non-standardized dedicated computing logic (i.e., IN-AL) defined and deployed according to the requirements of ASP / UE. The network function 4 in the chain is denoted by the enumeration number k as cNF k Therefore, one or more cNFs 4 on the forwarding path are implemented as a special type of UPF with IN-AL. One or more cNFs 4 are connected to each other via the N9 reference point.

[0055] cNF 4 is associated with the EAS deployed in the DN domain. The corresponding cNF 4 can act as a pre-processing part or a termination point of the associated EAS. For the first mode, cNF 4 is only responsible for part of the preparation tasks of the EAS. For the second mode, cNF 4 itself can provide a complete service to UE 1, and the UP service can be terminated at a cNF 4 instead of necessarily reaching the terminal server side. The ASP can comprehensively consider the characteristics of the EAS, resource availability, and expected QoS to decide which mode to adopt or combine the two modes to design a specific service. Different UE 1s can also receive different processing of IN-AL according to the UE profile (e.g., the location of UE 1 and / or the processing capability of UE 1). Therefore, for a specific EAS, some UE services can be processed and terminated at cNF1, some UE services can be processed at cNF1 and cNF2 and terminated at cNF2, some UE services can be processed at cNF1 and cNF2 and continue to the DN, and some UE services can be processed and terminated at cNF3, and so on.

[0056] The CN domain and the DN domain are connected to each other through the N6 reference point.

[0057] Figure 1 The top of is shown the relevant CP elements of the 3GPP network. The session management function (SMF) 2 and the edge application service discovery function (EASDF) 3 are particularly relevant to the present disclosure.

[0058] The SMF 2 is the CP element that interacts with the UP. This includes creating, updating, and deleting protocol data unit (PDU) sessions, and managing session contexts with one or more UPFs 4 in the CN domain over the N4 reference point.

[0059] EASDF 3 is a CP element used to facilitate UE's edge application server / service (EAS) discovery. EASDF 3 acts as a domain name system (DNS) resolver for UE 1 and can supplement DNS queries with location-based information based on the UE location. This enables resolution of EAS close to the UE location. EASDF 3 uses N easdf Reference points connect to other CP elements.

[0060] Other CP elements include the network repository function (NRF) and the unified data manager (UDM) function.

[0061] NRFs are CP elements that essentially act as indexes that other NFs can query so they can discover information about other entities that exist in the CN domain. nrf Reference points connect to other CP elements.

[0062] UDM is a CP element used to manage access authorization, user registration, and DN profile data. udm Reference points connect to other CP elements.

[0063] The service provision will be completed by EASDF 3 in coordination with SMF 2 and UE 1. Service provision may also involve the terminal server side located in the DN.

[0064] Figure 2 A UE 1, related network functions 2 to 4 and corresponding methods 5 to 8 of operating the UE and related network functions according to the present disclosure are shown.

[0065] Figure 1 The top of the diagram shows the relevant CP elements of the 3GPP network. From left to right, UE 1, RAN, SMF 2, EASDF 3, exemplary cNF 4 and EAS are shown.

[0066] These CP elements represent network entities in the CP of the cellular network system.

[0067] UE 1, SMF 2, EASDF 3 and cNF 4 may operate according to corresponding methods 5 to 8, respectively, wherein each method plays a role in providing a PDU session based on EAS including an INC service based on cNF 4.

[0068] CP elements 1 to 4 may be implemented in hardware / software (eg, a computer program implementing methods 5 to 8 for CP elements).

[0069] In high-level view, the offer can be based on Figure 2 This is accomplished by signaling executed from top to bottom.

[0070] First, a registration process is needed to disclose the existence and capabilities of the instantiated cNF 4 to the EASDF 3.

[0071] Initially, cNF 4 is configured as a registration entity to the cellular network, e.g. Figure 2In the example of EASDF 3 (direct registration) or NRF (indirect registration, not shown), the register 41 itself.

[0072] Correspondingly, the EASDF 3 is configured to register 31 cNF 4 .

[0073] Secondly, a service discovery request and response procedure is required between UE 1 and EASDF 3 so that information of previously registered cNF 4 can be provided according to a request from UE 1 indicating that a specific type of cNF 4 is to be used for EAS.

[0074] Accordingly, the UE 1 is configured to discover 12 the EAS including the cNF 4 based INC service by approaching the EASDF 4 .

[0075] Correspondingly, the EASDF 4 is also configured to notify 32 the UE 1 of the EAS including the cNF 4-based INC service.

[0076] Third, a session establishment / modification process is required between UE 1 and SMF 2 so that SMF 2 can discover and identify the appropriate cNF 4 so that the PDU session can be correctly established. Depending on the specific application scenario triggered by UE 1, the PDU session may or may not terminate at the selected cNF 4.

[0077] Therefore, the UE 1 is also configured to establish 13 a PDU session based on the discovered EAS by approaching the SMF 2.

[0078] Correspondingly, the SMF 2 is configured to establish 23 an EAS-based PDU session by approaching the cNF 4, the EAS including the cNF 4-based INC service.

[0079] Correspondingly, the cNF 4 is further configured to perform 43 local configuration of the cNF 4 for the PDU session based on the EAS, the EAS including the INC service based on the cNF 4.

[0080] Figure 3 Shown in more detail Figure 2 Methods 5 to 8.

[0081] The signalling starts with the cNF 4 which is configured to register 41 the cNF 4 (ie itself) with a registration entity of the cellular network.

[0082] The registration entity may include the EASDF 3 of the cellular network (e.g. Figure 3 shown) or NRF for cellular networks (see Figure 1 ).

[0083] In order to register 41 the cNF 4, the cNF 4 may be configured to send 411 a registration request to a registration entity of the cellular network.

[0084] The registration request may include one of: an instruction to create a configuration file of cNF 4 at the registration entity; an instruction to update the configuration file of cNF 4 at the registration entity; an instruction to notify the configuration file of cNF 4 at the registration entity; an instruction to delete the configuration file of cNF 4 at the registration entity.

[0085] Unlike normal UPF / NF, cNF 4 is not independent because the cNF is associated to the existing EAS in the DN.

[0086] The registration request may also include: an identifier of the EAS ("EdgeAppId"); a mapping of the DNS name of cNF 4 to the locator address of the EAS including the INC service ("DnsToIp"); an indication that the cNF 4 terminates the EAS ("IsTerminated"); an identifier of the subsequent cNF 4 of the cNF 4 in the EAS ("FuncChainId"); an indication that analysis data collection for cNF 4 is supported ("IsDataCollectionSupported"); and an indication of the serving area of ​​cNF 4 ("ServingArea").

[0087] First, the "EdgeAppID" parameter indicates the ID value of the associated EAS, because the cNF is designed to enhance the experience and performance of the existing EAS. This information can help network operators further optimize the service quality and user experience of this EAS.

[0088] Secondly, the "IsTerminated" parameter indicates whether this cNF 4 can serve as the termination point of the EAS indicated by "EdgeAppId". This determines whether the UP service is terminated in the 3GPP network domain or further transferred to the outside such as DN. This parameter also helps network operators make more precise decisions about EAS. If this attribute is not defined, it can only serve as the termination point for certain services.

[0089] Third, if cNF 4 cannot serve as a termination point, the "FuncChainId" parameter specifies the service function chain identifier. If cNF 4 is not a termination point, cNF 4 forwards the processed UP service to the next station, which can be another cNF 4 or a group of cNF 4s forming a service function chain (SFC). This parameter indicates that the network operator can further identify the SFC through "FuncChainId". Therefore, if "IsTerminated" is FALSE, the "FuncChainId" parameter can represent the ID value of the chained service function of the next processing step.

[0090] Fourth, the "IsDataCollectionSupported" parameter specifies whether this cNF 4 supports data collection through the network, especially through NWDAF. If supported, NWDAF can collect operation data on cNF 4 for analysis to serve other purposes, such as learning for network control, optimization, etc.; otherwise, network operators cannot collect operation data.

[0091] Fifth, the "ServingArea" parameter may represent, for example, a tracking area identifier (TAI) indicating the location of the UE served by the cNF 4.

[0092] The Registration Request may also include all existing profile parameters mentioned in clause 5.2.7.2.2 of 3GPP TS 23.502.

[0093] The profile parameters provide a clear description of the INC services available from the CN, which helps the CP to subsequently identify the appropriate cNF instance.

[0094] The signalling continues to the EASDF 3 which is configured to register 31 the cNF 4 accordingly.

[0095] In order to register 31 the cNF 4 , the EASDF 3 may be configured to receive 311 a registration request from the cNF 4 .

[0096] The EASDF 3 may also be configured to process 312 the profile of the cNF 4 according to the registration request. For example, the EASDF 3 may verify the profile data of the cNF 4 and may also store the profile data of the cNF 4.

[0097] The EASDF 3 may also be configured to send 313 a Registration Response to the cNF 4.

[0098] Can be combined with cellular network NRF (see Figure 1) as a registered entity to perform a similar registration process. If cNF4 is a non-trusted entity deployed by a third party, the cNF must be registered through the NEF of the cellular network.

[0099] The signaling returns to the cNF 4. In order to register 41 the cNF 4, the cNF 4 may accordingly be configured to receive 413 a registration response from the registration entity.

[0100] Signaling continues at the UE 1 which is configured to discover 12 an EAS including a cNF 4 based INC service.

[0101] UE 1 discovers EASDF 3 via SMF 2. This follows a similar procedure defined in steps 1 to 6 of clause 6.2.3.2.2 of 3GPP TS 23.548 ("EAS Discovery Procedure with EASDF").

[0102] It is assumed that the EASDF 3 is registered at the NRF of the cellular network and that the SMF 2 knows which EASDF 3 should be contacted. The information of the EASDF 3 can be configured to the UE 1 or can be retrieved dynamically during the PDU session establishment. The necessary processes and interactions between the AMF and the SMF 2 are also included here, including the creation of the UE context and the exchange of information between the RAN and the AMF to establish this PDU session.

[0103] In order to discover 12 the EAS, the UE 1 may be configured to send 121 a discovery request to the EASDF 3 over an established PDU session.

[0104] The discovery request may include: an identifier of EAS ("EdgeAppId"); a DNS name of EAS ("DNSAddress"); a query indication regarding the INC service's support for EAS ("IsINCSupported"); an identifier of the required version of the INC service ("INCALVersion"); and a query indication regarding the configuration of cNF 4 that terminates EAS ("HasTerminationPoint").

[0105] First, the “EdgeAppId” parameter may represent an ID value of an EAS associated with cNF 4.

[0106] Second, the "IsINCSupported" parameter may indicate checking whether the associated EAS has the INC enhancement option.

[0107] Third, the "INCALVersion" parameter may specify the requested ID of the INC / IN-AL version of the associated EAS.

[0108] Fourth, the "HasTerminationPoint" parameter may indicate a check to see if the INC service (if present) can serve as a termination point for the associated EAS.

[0109] The discovery request enables the UE to indicate an INC application service request associated with a certain EAS. The request will also trigger the EASDF 3 to discover the corresponding cNF instances available in the CN.

[0110] The signaling continues to the EASDF 3 which is accordingly configured to inform 32 the UE 1 of the EAS including the cNF 4 based INC service.

[0111] In order to advertise 32 the EAS, the EASDF 3 may also be configured to receive 321 a discovery request from the UE 1 , to parse 322 the discovery request in cooperation with a query entity of the cellular network, and to send 323 a discovery response to the UE 1 .

[0112] The query entity of the cellular network may include one of an NRF of the cellular network, a UDM entity of the cellular network, and an application service provider (ASP) of the EAS.

[0113] Resolving 322 the discovery request may in particular comprise checking profile data of the requesting UE 1 and / or resolving a DNS name of the requested EAS from the received application identification with the locator address (ie IP address).

[0114] The discovery response may include: an identifier of EAS ("EdgeAppId"); a locator address of EAS and / or a corresponding EAS locator address not supported by the INC service ("DNSResolvedInfo"); a response indication of the INC service's support for EAS ("IsINCSupported"); an identifier of the version of the INC service ("INCALVersion"); and a response indication of the configuration of cNF 4 that terminates EAS ("HasTerminationPoint").

[0115] The signaling returns to the UE 1. In order to discover 12 the EAS, the UE 1 may be configured accordingly to receive 123 a discovery response from the EASDF 3.

[0116] The UE 1 is further configured to establish 13 a PDU session based on the discovered EAS.

[0117] To establish 13 a PDU session, the UE 1 may be configured to send 131 a PDU session request to the SMF 2 of the cellular network via the RAN and AMF of the cellular network.

[0118] The PDU Session Request may include the locator address ("DNSResolvedInfo") of the EAS containing the INC service. That is, a PDU session based on the EAS including the INC service based on the cNF 4 is requested by specifying the locator address (EAS entry point) in the PDU Session Request. If the termination flag is set in the PDU Session Request, the UP service may be terminated at the cNF 4 as the final destination, and if the termination flag is not set in the PDU Session Request, the UP service may be forwarded to, for example, other cNF 4 of the service function chain, a normal UPF, and / or directly to the EAS in the DN domain.

[0119] The signaling continues to the SMF 2 which is accordingly configured to establish 23 a PDU session based on an EAS including an INC service based on cNF 4.

[0120] In order to establish 23 a PDU session, the SMF 2 may be configured to receive 231 a PDU session request from the UE 1 .

[0121] Optionally, SMF 2 may need to request the PCF of the cellular network to check the policy of the requested EAS including the INC service indicated in the PDU session request. This allows SMF 2 to decide whether to allow such requested services based on the profile of UE 1.

[0122] Optionally, SMF 2 may need to request information of cNF 4 deployed in the CN domain from the NRF of the cellular network in order to select one or more cNFs that meet the EAS / INC service requirements indicated in the PDU session request of UE 1. This information may include the location and capabilities of the instantiated cNF 4, and cNF 4 profile data related to EAS with respect to the application identity contained in the PDU session request of UE 1.

[0123] Hence, for establishing 23 the PDU session, the SMF 2 may also be configured to select 232 a cNF 4 from a plurality of registered cNFs 4 of the cellular network.

[0124] In order to establish 23 the PDU session, the SMF 2 may also be configured to send 233 a configuration request to the selected cNF 4. In other words, the SMF 2 may configure the selected cNF 4 for the requested INC-enabled EAS.

[0125] The configuration request may include one or more of the following: an entry point of the INC-enabled EAS, an entry point of a subsequent cNF 4 of the selected cNF 4 in the EAS; and a termination rule of the EAS.

[0126] The signaling continues to one or more selected cNFs 4, which are accordingly configured to perform 43 local configuration of the corresponding cNF 4 for the PDU session based on EAS, which includes the INC service based on cNF 4.

[0127] In order to perform 43 local configuration of the cNF 4 for the PDU session, the corresponding selected cNF 4 may also be configured to receive 433 a configuration request from the SMF 2 and to send 434 a configuration response to the SMF 2.

[0128] The configuration response may include a locator address that facilitates UE 1 (ie, that UE 1 may use) to access the EAS including the cNF 4-based INC service.

[0129] The signaling returns to the SMF 2. To establish 23 the PDU session, the SMF 2 may be configured accordingly to receive 234 a configuration response from the selected cNF 4.

[0130] In order to establish 23 the PDU session, the SMF 2 may also be configured to send 235 a PDU Session Request Accept to the UE 1 via the AMF and the RAN of the cellular network.

[0131] The PDU Session Request Accept may include a locator address to facilitate UE 1 to access the EAS including the INC service based on cNF 4.

[0132] The signaling returns to the UE 1. To establish 13 the PDU session, the UE 1 may be configured accordingly to receive 135 a PDU Session Request Accept from the SMF 2.

[0133] This concludes the provision of PDU sessions based on cNF 4-based INC-enabled EAS.

[0134] UE 1 can then access the INC service of EAS using the provided information. The process is similar to the process defined in clause 4.3.2.2 of 3GPP TS 23.502, including the uplink and downlink data service activation process between cNF 4, AMF and SMF 2.

[0135] The disclosure has been described in conjunction with various embodiments as examples and implementations. However, other variations can be understood and effected by those skilled in the art in practicing the claimed subject matter, from a study of the drawings, the disclosure, and the independent claims.

[0136] For example, when considering other types of network systems (e.g., WLAN, LAN), network operators can also use the present disclosure to deploy INC services in their network domains. In this case, network elements (e.g., switches / routers) should be programmable, and MPs should be able to manage network elements so that components of the INC part are deployed on network elements of the AS. Specifically, a cNF4 with a specific IN-AL can be instantiated on one or more network elements.

[0137] In the claims and the description, the word "comprising" does not exclude other elements or steps, and the indefinite article "a", "an" does not exclude a plurality. A single element or other unit may fulfil the functions of several entities or items described in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used in an advantageous implementation. The computer program may be stored or distributed on a suitable medium, such as an optical storage medium or solid-state medium provided together with or as part of other hardware, and may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunication systems.

Claims

1. A user equipment UE (1) for a cellular network, wherein: The UE (1) is configured to: discovering (12) an edge application service EAS of the cellular network, wherein the EAS comprises an in-network computing service based on a network function entity cNF (4) in a core network of the cellular network; and A protocol data unit (PDU) session based on the discovered EAS is established (13).

2. The UE (1) according to claim 1, wherein: In order to discover (12) the EAS, the UE (1) is further configured to: Sending (121) a discovery request to an edge application service discovery function EASDF (3) of the cellular network, the discovery request comprising: an identification of the EAS; The domain name service DNS name of the EAS; a query indication regarding support of the EAS by the in-network computing service; an identification of a desired version of the in-network computing service; A query indication regarding the configuration of the cNF (4) terminating the EAS.

3. The UE (1) according to claim 1 or 2, wherein: In order to discover (12) the EAS, the UE (1) is further configured to: A discovery response is received (123) from the EASDF (3), the discovery response comprising: the identification of the EAS; the locator address of the EAS including the in-network computing service and / or the locator address of the corresponding EAS excluding the in-network computing service; a response indication regarding the support of the EAS by the in-network computing service; An identifier of a version of the in-network computing service; A response indication regarding the configuration of the cNF (4) terminating the EAS.

4. The UE (1) according to any one of claims 1 to 3, wherein: In order to establish (13) the PDU session, the UE (1) is configured to: A PDU session request is sent (131) to a session management function SMF (2) of the cellular network, the PDU session request comprising: The locator address of the EAS for the in-network computing service is included.

5. The UE (1) according to claim 4, wherein: In order to establish (13) the PDU session, the UE (1) is further configured to: Receiving (135) a PDU session request acceptance from the SMF (2), the PDU session request acceptance comprising: A locator address, wherein the locator address is used for the UE (1) to access the EAS including the in-network computing service.

6. A session management function SMF (2) for a cellular network, wherein: The SMF (2) is configured as: A PDU session of an edge application service EAS based on the cellular network is established (23), wherein the EAS includes an in-network computing service based on the registered network function entity cNF (4).

7. The SMF (2) according to claim 6, wherein: In order to establish (23) the PDU session, the SMF (2) is configured to: A PDU session request is received (231) from a user equipment UE (1) of the cellular network, the PDU session request comprising: A locator address of the EAS for the in-network computing service is included.

8. The SMF (2) according to claim 6 or 7, wherein: In order to establish (23) the PDU session, the SMF (2) is further configured to: selecting (232) the CNF (4) from a plurality of registered CNFs (4) of the cellular network; Sending (233) a configuration request to the selected cNF (4), the configuration request comprising one or more of the following: an entry point of a subsequent cNF (4) of the selected cNF (4) in the EAS; Termination rules of the EAS; as well as Receiving (234) a configuration response from the selected cNF (4) of the selection, the configuration response comprising: A locator address, wherein the locator address is used for the UE (1) to access the EAS including the in-network computing service.

9. The SMF (2) according to any one of claims 6 to 8, wherein: In order to establish (23) the PDU session, the SMF (2) is further configured to: Sending (235) a PDU session request acceptance to the UE (1), the PDU session request acceptance comprising: The locator address is used by the UE (1) to access the EAS including the in-network computing service.

10. An edge application service discovery function EASDF (3) for a cellular network, wherein: The EASDF(3) is configured as: registering (31) a network function entity cNF (4) with a core network of the cellular network; and Notify (32) the edge application service EAS of the cellular network, the EAS comprising an in-network computing service based on the network function entity cNF (4).

11. The EASDF (3) according to claim 10, wherein: In order to register (31) the cNF (4), the EASDF (3) is also configured as follows: A registration request is received (311) from the cNF (4), the registration request comprising one of: an instruction to create a configuration file of said CNF (4) at said registration entity, an indication to update said configuration file of said CNF (4) at said registration entity, an indication of said profile of said CNF (4) being notified at said registration entity, an indication of deleting the configuration file of the cNF (4) at the registration entity; processing (312) the configuration file of the cNF (4) according to the registration request; as well as A registration response is sent (313) to the cNF (4).

12. The EASDF (3) according to claim 11, The registration request also includes: The EAS logo; a mapping of a domain name service DNS name of the cNF (4) to a locator address of the EAS including the in-network computing service; The cNF (4) terminates the indication of the EAS; an identifier of a subsequent cNF (4) of the cNF (4) in the EAS; An instruction for supporting the collection of analytical data for the cNF (4); An indication of the service area of ​​the cNF (4).

13. The EASDF (3) according to any one of claims 10 to 12, wherein: In order to notify (32) the EAS, the EASDF (3) is further configured to: A discovery request is received (321) from a user equipment UE (1) of the cellular network, the discovery request comprising: the identification of the EAS; the DNS name of the EAS; a query indication regarding support of the EAS by the in-network computing service; an identification of a desired version of the in-network computing service; a query indication regarding the configuration of the cNF (4) terminating the EAS; parsing (322) the discovery request in cooperation with a querying entity of the cellular network; and Sending (323) a discovery response to the UE (1), the discovery response comprising: the identification of the EAS; The locator address of the EAS and / or the locator address of the corresponding EAS not supported by the in-network computing service; a response indication regarding the support of the EAS by the in-network computing service; An identifier of a version of the in-network computing service; A response indication regarding the configuration of the cNF (4) terminating the EAS.

14. The EASDF (3) according to claim 13, The query entity of the cellular network comprises one of the following: The network storage function NRF of the cellular network, The unified data management (UDM) entity of the cellular network, The EAS is an application service provider ASP.

15. A network function entity cNF (4) for a core network of a cellular network, wherein: The cNF (4) is configured as: registering (41) the cNF (4) with a registration entity of the cellular network; and The cNF (4) is locally configured (43) for a PDU session of an edge application service EAS based on the cellular network, wherein the EAS includes an in-network computing service based on the network function entity cNF (4).

16. The cNF (4) according to claim 15, wherein In order to register (41) the cNF (4), the cNF (4) is also configured to: A registration request is sent (411) to the registration entity of the cellular network, the registration request comprising one of: an instruction to create a configuration file of said CNF (4) at said registration entity, an indication to update said configuration file of said CNF (4) at said registration entity, an indication of said profile of said CNF (4) being notified at said registration entity, an indication to delete the configuration file of the cNF (4) at the registration entity; and A registration response is received (413) from the registration entity.

17. The cNF (4) according to claim 16, The registration request also includes: an identification of the EAS; a mapping of a domain name service DNS name of the cNF (4) to a locator address of the cNF (4); The cNF (4) terminates the indication of the EAS; an identifier of a subsequent cNF (4) of the cNF (4) in the EAS; An instruction for supporting the collection of analytical data for the cNF (4); An indication of the service area of ​​the cNF (4).

18. The cNF (4) according to any one of claims 15 to 17, wherein the registration entity comprises: The cellular network edge application service discovery function EASDF (3).

19. The cNF (4) according to any one of claims 15 to 17, wherein the registration entity comprises: The cellular network has a network storage function NRF.

20. The cNF (4) according to any one of claims 15 to 19, wherein In order to perform (43) the local configuration of the cNF (4) for the PDU session, the cNF (4) is further configured to: A configuration request is received (433) from a session management function SMF (2) of the cellular network, the configuration request comprising one or more of the following: an entry point of a subsequent cNF (4) of the cNF (4) in the EAS; Termination rules of the EAS; as well as Sending (434) a configuration response to the SMF (2), the configuration response comprising: A locator address, wherein the locator address is used for a UE (1) to access the EAS including the in-network computing service.

21. The cNF (4) according to any one of claims 15 to 20, comprising: User plane function.

22. A method (5) of operating a user equipment UE (1) for a cellular network, the method (5) comprising: Discovering (12) an edge application service EAS of the cellular network, the EAS comprising an in-network computing service based on a network function entity cNF (4) in a core network of the cellular network; as well as A protocol data unit (PDU) session based on the discovered EAS is established (13).

23. A method (6) of operating a session management function (SMF) (2) of a cellular network, the method (6) comprising: A PDU session of an edge application service EAS based on the cellular network is established (23), wherein the EAS includes an in-network computing service of a network function entity cNF (4) in a core network of the cellular network.

24. A method (7) for operating an edge application service discovery function (EASDF) (3) of a cellular network, the method (7) comprising: Notify (32) the edge application service EAS of the cellular network, the EAS comprising an in-network computing service based on a network function entity cNF (4) in a core network of the cellular network.

25. A method (8) for operating a core network network function entity cNF (4) for a cellular network, the method (8) comprising: Registering (41) the cNF (4) with a registration entity of the cellular network; as well as The cNF (4) is locally configured (43) for a PDU session of an edge application service EAS based on the cellular network, wherein the EAS includes an in-network computing service based on the network function entity cNF (4).

26. A computer program comprising a program code for performing the method (5, 6, 7, 8) according to any one of claims 22 to 25 when executed on a computer.

Images