TECHNICAL FIELD

The present disclosure relates to the field of deployment of services in mobile communication networks such as 5G and 6G systems and beyond and edge computing. In particular, the disclosure relates to a method for controlling a service in an operator network and a corresponding communication system. More specifically, the disclosure relates to flow-trap mechanism to support service placement decisions.

BACKGROUND

In current 3GPP networks there is a limited amount of interaction between operators and service providers. They mainly focus on provisioning of connectivity but usually neglect compute. To deploy services closer to end users and for an optimal service placement it is required to have some “location” information of the users consuming the service. 3 ^rd party services are not aware of the connectivity nuances from within the operator networks. Only operators have the capabilities to gather some network-based location information about users consuming a particular service. Operators can identify which users are consuming a service solely based on the service description. Currently, there are no efficient and scalable 3GPP mechanisms for tracing application utilization back to users that can be explored to conciliate the information accessible to the service providers with the actual network topology. Such mechanisms, however, are the basis of any further interaction between service providers and operators.

SUMMARY

This disclosure provides a solution for efficient and scalable 3GPP mechanisms for detecting and reporting application utilization based on the data flow of the traffic from the UE to the application.

In particular, the disclosure provides novel mechanisms based on a flow trap to detect application usage in a communication network. This is achieved by enhancing the messages and network entities involved in the data and control paths. Specifically, in a 3GPP context, this disclosure enhances the Npcf_PolicyAuthorization (Npcf: network policy control function) procedures to support UE-independent subscriptions to provide efficient and scalable UE IE/IP address resolution based solely on a Service Description, application ID or DNAI (data network access identifier).

The foregoing and other objects are achieved by the features of the independent claims. Further implementation forms are apparent from the dependent claims, the description and the figures.

A basic concept of this disclosure is providing the mechanisms and entities that are able to realize efficient and scalable application detection. The solution relies on a flow trap mechanism which can be executed at the UPF (data plane path) that detects the usage of the application from any UE. In addition, a coordinated message sequence and interaction between the critical network function in a mobile system is presented. Those interactions are required in a 3GPP context between the application function (api gateway toward the outside of the mobile network), PCF (policy storage function), SMF (session management function), and finally the UPF (the user plane function that actually handles traffic routing and forwarding).

The solution described in this disclosure can be used in a generalized network where it is beneficial to detect application usage, e.g., as described below with respect to Figure 2. This mainly enables an efficient and optimized deployment of edge computing resources close to the end users. The disclosed solution can be more specifically used in a 3GPP based system, e.g., the 5G or 6G mobile communication system, e.g., as described below with respect to Figures 1 and 3 to 6.

In order to describe the invention in detail, the following terms, abbreviations and notations will be used:

3GPP third generation partnership project

AF application function, application function entity

PCF policy control function, policy control function entity

SMF session management function; session management function entity

UPF user plane function; user plane function entity

ID identifier

DNAI data network access identifier

PFD packet flow descriptor

UDR unified data network In this disclosure, edge computing, edge nodes in mobile communication systems for performing edge computing and deployment of services in 5G and 6G mobile communication systems and 5G network functions are described.

Edge computing, or on demand deployment of services very close to end-users, enables next generation applications especially in beyond 5G and 6G mobile communication systems. The main advantage of edge computing is its ability to offer services with very low latencies and high throughput. Since the edge nodes are deployed close to end users it is possible to realize the best service delivery conditions. In general, 6G systems envision applications with very stringent requirements which will have impact on the upcoming architecture. Generally, the growing scale and advancement of virtualization of network functions (the basic logical mobile network building blocks) have led to more radical changes in the data and control components of mobile communication systems. Indeed, many operators are looking into how to make use of untapped resources (virtualization- enabled data centers and servers), deployed with the RAN, transit, and core networks.

In particular the following 5G network functions of the 5G reference point architecture (see Figures 1 and 3) as specified in 3GPP TS 38.300 and 3GPP TS 23.501 specifications are described in this disclosure: UPF, AF, PCF and SMF.

UPF stands for User plane function. The functions of 5G NR UPF node or UPF entity are: Anchor point for lntra-/lnter-RAT mobility (when applicable); External PDU Session point of interconnect to Data Network; Packet routing & forwarding; Packet inspection; User Plane part of policy rule enforcement, e.g. Gating, Redirection, Traffic steering; Lawful intercept (UP collection); Traffic usage reporting; QoS handling for user plane, e.g. UL/DL rate enforcement, Reflective QoS marking in DL; Uplink Traffic verification (SDF to QoS Flow mapping); Transport level packet marking in the uplink and downlink; Downlink packet buffering and downlink data notification triggering; Sending and forwarding of one or more "end marker" to the source NG-RAN node.

SMF stands for Session Management Function. The functions of 5G NR SMF node or SMF entity are: Session Management; UE IP address allocation and management; Selection and control of UP function; Configures traffic steering at UPF to route traffic to proper destination; Control part of policy enforcement and QoS; Downlink Data Notification.

PCF stands for Policy Control Function. The functions of 5G NR PCF node or PCF entity are: Support of unified policy framework to govern network behavior; Providing policy rules to Control Plane function(s) to enforce them; Accessing subscription information relevant for policy decisions in a Unified Data Repository (UDR).

AF stands for Application Function. The functions of 5G NR AF node or AF entity are: Application influence on traffic routing; Accessing Network Exposure Function; Interacting with the Policy framework for policy control.

According to a first aspect, the disclosure relates to a method for controlling a service in an operator network based on a location of at least one User Equipment, UE, the operator network comprising a data plane entity) for delivering data traffic between the at least one UE and the operator network, wherein the data traffic comprises a plurality of data flows which are associated with respective services, each service being identified by a respective service descriptor; and wherein each data flow comprises an identification of the at least one UE which is associated with a location of the at least one UE; the operator network comprising a control plane entity for controlling the data plane entity, the method comprising: controlling, by the control plane entity based on a specific service descriptor, the data plane entity to monitor the data traffic between the at least one UE and the operator network for detecting a data flow being associated with a service identified by the specific service descriptor; and sending, by the data plane entity, a notification to the control plane entity upon detecting a data flow associated with a service identified by the specific service descriptor, wherein the notification comprises the identification of the at least one UE.

This method provides a solution for an efficient and scalable mechanism to detect and report application utilization based on the data flow of the traffic from the UE to the application. The specific service may be efficiently detected and provided to the service provider for controlling a service in the operator network based on a location of at least one User Equipment.

The service may be a communication service or also a non-communication service. The operator network can be any communication network or network in general operated by an operator, for example a data network or a telephone network, e.g., a 3GPP network.

The purpose of the data plane entity is in first place to deliver data plane traffic. A further capability of the data plane entity is to monitor the data plane traffic. In an exemplary implementation of the method, the data plane entity is controlled by the control plane entity based on the specific service descriptor without indicating an identification of the at least one UE.

This provides the advantage that the control plane entity does not require the specific identification of the UE for controlling the data plane entity to detect a data flow associated with a service of the specific service descriptor.

In an exemplary implementation of the method, the data plane entity is controlled by the control plane entity based on a data structure in which the identification of the at least one UE is an optional data field.

This provides the advantage that the control plane entity does not require the specific identification of the UE for controlling the data plane entity. The mechanism also functions with a data structure in which the identification of the UE is an optional data field.

In an exemplary implementation of the method, the data plane entity is controlled by the control plane entity based on a “AppSessionContextReqData” data structure according to 3GPP TS23.502 in which specification of addressing parameters of the at least one UE is optional.

This provides the advantage that the existing procedures of the 3GPP standard can be reused with some little modification as indicated above.

In an exemplary implementation of the method, the operator network comprises a control function entity for controlling the control plane entity and providing an interface to a service provider entity, the method comprising: receiving, by the control function entity, a request from the service provider entity for initiating the monitoring of the data traffic between the at least one UE and the operator network, wherein the request comprises the specific service descriptor; and controlling, by the control function entity, the control plane entity to enable the data plane entity for monitoring of the data traffic between the at least one UE and the operator network based on the specific service descriptor.

This provides the advantage that an interface is provided to the service provider which can control by this interface the acquisition of the UE identification in order to control the services provided in the operator network. In an exemplary implementation of the method, the method comprises: providing, by the control function entity, a report about the detected data flow associated with the service identified by the specific service descriptor, to the service provider entity, wherein the report comprises the identification of the at least one UE.

This provides the advantage that the service provider receives information about the different UEs such that the service provider can tailor his services depending on the specific UEs and their locations.

The report may contain information about one UE or information about multiple UEs at once.

In an exemplary implementation of the method, the method comprises: determining, by the service provider entity, the location of the at least one UE based on the identification of the at least one UE; and controlling the service, by the service provider entity based on the determined location of the UE.

This provides the advantage that the service provider can control the service based on the location of the at least one UE.

In an exemplary implementation of the method, the operator network comprises a plurality of edge nodes for providing access to the respective services, the method comprising: instantiating the service identified by the specific service descriptor, by the service provider entity, at a first edge node of the plurality of edge nodes based on the location of the at least one UE.

This provides the advantage that the service provider can instantiate its services based on the location of the at least one UE in order to reduce a distance between the UE and the edge nodes providing the service.

In an exemplary implementation of the method, a location of the first edge node is closer to the location of the at least one UE than a location of the other edge nodes.

This provides the advantage that the service provider can choose the edge node having a minimum distance to the UE for providing the service.

In an exemplary implementation of the method, the control function entity comprises an application function, AF, entity according to 3GPP specification, wherein the request from the service provider entity for initiating the monitoring of the data traffic is received by the AF entity, wherein the report about the detected data flow is produced by the AF entity; and wherein the enabling of the data plane entity for monitoring of the data traffic is initiated by the AF entity.

This provides the advantage that the method can be applied in a 3GPP context where the AF can control the data plane entity for monitoring the data traffic.

In an exemplary implementation of the method, the data plane entity comprises a user plane function, UPF, entity according to 3GPP specification, wherein the data traffic between the UE and the operator network is monitored by the UPF entity.

This provides the advantage that the method can be applied in a 3GPP context where the UPF can monitor the data traffic.

In an exemplary implementation of the method, the control plane entity comprises a session management function, SMF, entity according to 3GPP specification, wherein the data plane entity is controlled by the SMF entity.

This provides the advantage that the method can be applied in a 3GPP context where the SMF can control the data plane entity.

In an exemplary implementation of the method, the data plane entity is controlled by the SMF entity based on an application detection request message, the application detection request message comprising an application identifier for indicating the service descriptor and reporting triggers for reporting a start or stop of the data flow detection.

This provides the advantage that the method can be applied in a 3GPP context where the SMF can control the data plane entity based on an application identifier and where the SMF can report a state of the data flow indication.

In an exemplary implementation of the method, the control plane entity comprises a policy control function, PCF, entity according to 3GPP specification, wherein the data plane entity is controlled by the SMF entity which is controlled by the PCF entity.

This provides the advantage that the method can be applied in a 3GPP context where the PCF can control the SMF for controlling the data plane entity. In an exemplary implementation of the method, the SMF entity is controlled by the PCF entity based on an application detection update notify message, the application detection update notify message providing notifications to the SMF entity every time there is new request from the service provider entity for initiating the monitoring of the data traffic between the at least one UE and the operator network, wherein the new request comprises a specific service descriptor that is not tied to any active session.

This provides the advantage that the method can be applied in a 3GPP context where the PCF can control the SMF based on request from the service provider.

According to a second aspect, the disclosure relates to a communication system for controlling a service in an operator network based on a location of at least one User Equipment, UE, the communication system comprising: a data plane entity configured to deliver data traffic between the at least one UE and the operator network, wherein the data traffic comprises a plurality of data flows which are associated with respective services, each service being identified by a respective service descriptor; and wherein each data flow comprises an identification of the at least one UE which is associated with a location of the at least one UE; and a control plane entity configured to control the data plane entity, based on a specific service descriptor, to monitor the data traffic between the at least one UE and the operator network for detecting a data flow being associated with a service identified by the specific service descriptor, wherein the data plane entity is configured to send a notification to the control plane entity upon detecting a data flow associated with a service identified by the specific service descriptor, wherein the notification comprises the identification of the at least one UE.

This communication system provides a solution for an efficient and scalable mechanism to detect and report application utilization based on the data flow of the traffic from the UE to the application. The specific service may be efficiently detected and provided to the service provider for controlling a service in the operator network based on a location of at least one User Equipment.

According to a third aspect, the disclosure relates to a computer program product including computer executable code or computer executable instructions that, when executed, causes at least one computer to execute the method according to the first aspect described above. The computer program product may run on a controller or processor for controlling the above-described service in an operator network, e.g., one of the components of the operator network described in Figure 1 or Figure 2.

According to a fourth aspect, the disclosure relates to a computer-readable medium, storing instructions that, when executed by a computer, cause the computer to execute the method according to the first aspect described above. Such a computer readable medium may be a non-transient readable storage medium. The instructions stored on the computer- readable medium may be executed by a controller or processor for controlling the abovedescribed service in an operator network, e.g., one of the components of the operator network described in Figure 1 or Figure 2.

BRIEF DESCRIPTION OF THE DRAWINGS

Further embodiments of the invention will be described with respect to the following figures, in which:

Figure 1 shows a block diagram illustrating a communication system 100 for controlling a service in an operator network according to the disclosure;

Figure 2 shows a block diagram illustrating a method 200 for controlling a service in an operator network according to the disclosure;

Figure 3 shows a block diagram illustrating a network architecture for the 3GPP mobile communication system 300 usable for controlling a service in an operator network according to the disclosure;

Figure 4 shows a message flow chart 400 illustrating interaction between AF, PCF, SMF and UPF entities of a 3GPP mobile communication system to detect application usage based on provisioning of the UE ID;

Figure 5 shows a message flow chart 500 illustrating a modified interaction between AF, PCF, SMF and UPF entities of a 3GPP mobile communication system to support service control without requiring the UE ID according to the disclosure; Figure 6 shows a message flow chart 600 illustrating a simplified interaction between AF, SMF and UPF entities of a 3GPP mobile communication system to support service control without requiring the UE ID according to the disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

In the following detailed description, reference is made to the accompanying drawings, which form a part thereof, and in which is shown by way of illustration specific aspects in which the disclosure may be practiced. It is understood that other aspects may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present disclosure is defined by the appended claims.

It is understood that comments made in connection with a described method may also hold true for a corresponding device or system configured to perform the method and vice versa. For example, if a specific method step is described, a corresponding device may include a unit to perform the described method step, even if such unit is not explicitly described or illustrated in the figures. Further, it is understood that the features of the various exemplary aspects described herein may be combined with each other, unless specifically noted otherwise.

Figure 1 shows a block diagram illustrating a communication system 100 for controlling a service in an operator network according to the disclosure.

In particular, Figure 1 shows the architecture of an end-to-end data delivery network 100. The service provider 121 offers the applications and usually deploys those compute instances in centralized clouds. The network operators 111 , on the other hand, are responsible for creating and managing the mobile network 110, also referred to as operator network 110 in this disclosure, as well as handling the connectivity between the user devices 131 , 132, 133 and the service providers 121.

In current 3GPP networks, there is a limited amount of interaction between operators 111 and service providers 121. They mainly focus on provisioning of connectivity but usually neglect compute. Going forward, the operator 111 will provide compute resources to the service providers 121 based on the fog and edge computing paradigm. To be able to do this, the operator has to open up its network and reveal APIs and develop interaction paradigms. Moving the compute termination points to within or very close to the operator’s network 110 enables better performance, lower costs for service providers 121 , as well as new business models for operators 111. Finally, the overall efficiency is enhanced since the operator 111 can use the untapped resources in its network 110.

This disclosure provides a solution for efficient and scalable 3GPP mechanisms for detecting and reporting application utilization based on the data flow of the traffic from the UE to the application.

In this disclosure, novel mechanisms based on a flow trap 102 to detect application usage in a communication network such as the operator network 110 shown in Figure 1 are described. This is achieved by enhancing the messages and network entities shown in Figure 1 involved in the data and control paths.

Based on a Service Description and Instantiation Request 101 from the service provider network 120, novel flow trap mechanism 102 are used as described hereinafter. Users utilizing the services are located 103 and services can be instantiated closer to the user 105.

Regarding the Service Description and instantiation request 101 , the service provider 121 explores the API exposed by AF 140 to request the operator 111 the deployment of a service 112, 112a (or service subpart for that matter) instance in its premises. AF 140 as main point of interaction with the core network offers functionality to instantiate services. So far, the AF 140 has been limited to traffic steering and redirection as highlighted in 3GPP TS 23.501.

Regarding the novel flow-trap mechanism 102, the request 122 from the service provider 121 triggers an application detection event in the data plane of the operator's network 110. So that the optimal location for service deployment is described, flow trap mechanisms 102 are used within the core network as described in this disclosure.

Regarding user localization, users utilizing the services are located 103: As a result, the operator 111 gains knowledge on what users are consuming the service 112, 112a. With this knowledge, the network can then obtain information such as user location. Users are located by tracing the application usage and not using the UE identification as in current 3GPP networks.

Regarding service instantiation, services 112, 112a are instantiated closer to the users 131 , 132, 133: Location information can be fed to an optimizer which will provide a recommendation on where the service 112, 112a should be placed in order to efficiently utilize the compute and network resources, e.g. available in the edge nodes 181 , 182, 183. Services 112, 112a are instantiated and deployed close to the users 131 , 132, 133 without wasting resources (e.g. by deploying the service all over the network where it will not be used).

Specifically, in a 3GPP context, this disclosure enhances the Npcf_PolicyAuthorization (Npcf: network policy control function) procedures to support UE-independent subscriptions to provide efficient and scalable UE IE/IP address resolution based solely on a Service Description, application ID or DNAI (data network access identifier).

This solution presented hereinafter provides an efficient interaction between 3rd party service providers and operators that allows to: Increase the flexibility in deploying computing closer to the end user; reduce service latency and provide increased QoS & QoE; and reduce the amount of information exchanged outside the operator’s network.

The end-to-end data delivery network 100 that is referred to as a communication system hereinafter, is able to control a service 112 in an operator network 110 based on a location of at least one User Equipment, UE 131 , 132, 133.

The communication system 100 comprises a data plane entity, e.g., a data plane entity 240 as shown in Figure 2, configured to deliver data traffic between the at least one UE 131 and the operator network 110. The data traffic comprises a plurality of data flows, e.g., data flows 113 as shown in Figure 2, which are associated with respective services 112, 112a. Each service 112, 112a is identified by a respective service descriptor 114. Each data flow 113 comprises an identification of the at least one UE 131 which is associated with a location of the at least one UE 131.

The communication system 100 comprises a control plane entity, e.g., a control plane entity 230 as shown in Figure 2, configured to control the data plane entity 240 based on a specific service descriptor 114, to monitor the data traffic between the at least one UE 131 and the operator network 110 for detecting a data flow 113 being associated with a service 112 identified by the specific service descriptor 114.

The data plane entity 240 is configured to send a notification 241 to the control plane entity 230 upon detecting a data flow 113 associated with a service 112 identified by the specific service descriptor 114. The notification 241 comprises the identification of the at least one UE 131.

The data plane entity and the control plane entity can be entities of the operator network 110 shown in Figure 1 , e.g., AF 140, PCF 150, SMF 160 and UPF 170 as described in more detail below with respect to Figures 3 to 6.

Figure 2 shows a block diagram illustrating a method 200 for controlling a service in an operator network 110 according to the disclosure.

The operator network can be an operator network 110 as described above with respect to Figure 1 . As shown in Figure 2, the operator network 110 comprises a data plane entity 240 for delivering data traffic between the at least one UE 131 and the operator network 110. The data traffic comprises a plurality of data flows 113 which are associated with respective services 112. Each service 112 is identified by a respective service descriptor 114. Each data flow 113 comprises an identification of the at least one UE 131 which is associated with a location of the at least one UE 131. The operator network 110 comprising a control plane entity 230 for controlling the data plane entity 240.

The method 200 comprises: controlling 231 , by the control plane entity 230 based on a specific service descriptor 114, the data plane entity 240 to monitor the data traffic between the at least one UE 131 and the operator network 110 for detecting a data flow 113 being associated with a service 112 identified by the specific service descriptor 114.

The method 200 comprises: sending a notification 241 , by the data plane entity 240, to the control plane entity 230 upon detecting a data flow 113 associated with a service 112 identified by the specific service descriptor 114, wherein the notification 241 comprises the identification of the at least one UE 131.

The data plane entity 240 may comprise, for example, a UPF entity 170 described above with respect to Figure 1 and below with respect to Figures 3 to 6. The control plane entity 230 may comprise, for example, an AF entity 140, a PCF entity 150 and a SMF entity 160 as described above with respect to Figure 1 and below with respect to Figures 3 to 6.

The data plane entity 240 may be controlled by the control plane entity 230 based on the specific service descriptor 114 without indicating an identification of the at least one UE 131 , e.g. as described below with respect to Figures 5 and 6. The data plane entity 240 may be controlled by the control plane entity 230 based on a data structure in which the identification of the at least one UE 131 is an optional data field, e.g. as described below with respect to Figures 5 and 6.

The data plane entity 240 may be controlled by the control plane entity 230 based on a “AppSessionContextReqData” data structure according to 3GPP TS23.502 in which specification of addressing parameters of the at least one UE 131 is optional, e.g. as described below with respect to Figures 5 and 6.

The operator network 110 may comprise a control function entity 220 for controlling the control plane entity 230 and providing an interface 123 to a service provider entity 121 , e.g., as described above with respect to Figure 1 and below with respect to Figures 3 to 6. The method 200 may further comprise: receiving, by the control function entity 220, a request 122 from the service provider entity 121 for initiating the monitoring of the data traffic between the at least one UE 131 and the operator network 110, wherein the request 122 comprises the specific service descriptor 114; and controlling, by the control function entity 220, the control plane entity 230 to enable the data plane entity 240 for monitoring of the data traffic between the at least one UE 131 and the operator network 110 based on the specific service descriptor 114.

The method 200 may further comprise: providing, by the control function entity 220, a report 104 about the detected data flow 113 associated with the service 112 identified by the specific service descriptor 114, to the service provider entity 121 , wherein the report 104 comprises the identification of the at least one UE 131.

The method 200 may further comprise: determining, by the service provider entity 121 , the location of the at least one UE 131 based on the identification of the at least one UE 131 ; and controlling the service 112, by the service provider entity 121 based on the determined location of the UE 131.

The operator network 110 may comprise a plurality of edge nodes 181 , 182, 183 for providing access to the respective services 112. The method 200 may further comprise: instantiating the service 112 identified by the specific service descriptor 114, by the service provider entity 121 , at a first edge node 181 of the plurality of edge nodes 181 , 182, 183 based on the location of the at least one UE 131 , e.g., as shown in Figure 1. A location of the first edge node 181 may be closer to the location of the at least one UE 131 than a location of the other edge nodes 182, 183 as exemplarily shown in Figure 1.

The control function entity 220 may comprise an application function, AF, entity 140 according to 3GPP specification. The request 122 from the service provider entity 121 for initiating the monitoring of the data traffic may be received by the AF entity 140. The report 104 about the detected data flow 113 may be produced by the AF entity 140. The enabling of the data plane entity 240 for monitoring of the data traffic may be initiated by the AF entity 140.

The data plane entity 240 may comprises a user plane function, UPF, entity according to 3GPP specification. The data traffic between the UE 131 and the operator network 110 may be monitored by the UPF entity 170.

The control plane entity 230 may comprise a session management function, SMF, entity 160 according to 3GPP specification. The data plane entity 240 may be controlled by the SMF entity 160.

The data plane entity 240 may be controlled by the SMF entity 160 based on an application detection request message 503, e.g., as described below with respect to Figures 5 and 6. The application detection request message 503 may comprise an application identifier for indicating the service descriptor and reporting triggers for reporting a start or stop of the data flow detection, e.g., as described below with respect to Figures 5 and 6.

The control plane entity 230 may comprise a policy control function, PCF, entity 150 according to 3GPP specification. The data plane entity 240 may be controlled by the SMF entity 160 which is controlled by the PCF entity 150, e.g., as described below with respect to Figure 5.

The SMF entity 160 may be controlled by the PCF entity 150 based on an application detection update notify message 502, e.g., as described below with respect to Figure 5. The application detection update notify message 502 provides notifications to the SMF entity 160 every time there is new request 122 from the service provider entity 121 for initiating the monitoring of the data traffic between the at least one UE 131 and the operator network 110. The new request 122 may comprise a specific service descriptor 114 that is not tied to any active session, e.g., as described below with respect to Figure 5. Besides the method 200 described above, Figure 2 also describes a generic system for generic flow detection in a networking system that can be but does not have to be a 3GPP system.

The same principles described above are applicable in this generic system. A control function 220 receives information 122 about a given service 112 (i.e., the service flow descriptor 114) and is expected to produce a report 104 about the UEs 131 accessing the service 112. In order to do so, the control function 220 sends a service detection subscription message 221 , indicating the service description 114, to the control plane 230, also referred to as network control plane 230. In turn, the control plane 230 enforces the necessary data plane rules 231 and gets notified 241 every time a new user is accessing the service (this notification includes the corresponding UE IP address). Finally, this information is then sent 232 towards the relevant control function 220 so that it can issue the corresponding report 104 (or take a decision).

Figure 3 shows a block diagram illustrating a network architecture for the 3GPP mobile communication system 300 usable for controlling a service in an operator network according to the disclosure.

In particular, Figure 3 depicts an exemplary network architecture for the 3GPP mobile communication system that handles traffic delivery using network functions and hosting of an application either in a central cloud 303 or edge cloud 180. The data path is visualized using the arrow. Here in Figure 3, two possibilities for this data path are highlighted. For the first case 301 , the data path goes over from the UE 131 (user equipment) to the access network towards the UPF 170 (user plane function) towards the default PSA (PDU packet data unit session anchor), going over the N6 interface towards the default DN (data network) finally going to the central cloud 303. This is how things are done nowadays, with overall good performance. For the second case 301 , as envisioned for next generation applications, the data does not have to go all the way to the central cloud 303, rather the traffic is terminated at close-by edge nodes 180. In this case, the latency between the UE 131 and the applications can be reduced since the application termination points are at optimized edge nodes 180 with minimal latency.

Generally, users could be accessing edge applications from any location within the network. So, to realize the benefits of edge computing, edge nodes 180 for a specific application have to be deployed near all possible network locations. Since this could be in the order of hundreds for a certain large city and tens of thousands or more for a certain country, deploying edge applications at all possible locations is not feasible and very costly at best. A more logical approach is to deploy edge nodes 180 specifically at those locations where the service is needed. Therefore, to deploy services closer to end users and for an optimal service placement it is required to have some “location” information of the users consuming the service. A main challenge in this context is that 3rd party services are not aware of the connectivity nuances at the operator networks. Only operators have the capabilities to gather some network-based location information about users consuming a particular service. Operators need to identify which users are consuming a service solely based on the service description. Further, using current technology, it is not possible for the operator to infer the location information of users consuming a service using a scalable and efficient method.

The main innovation presented in this disclosure is to provide a solution to efficiently infer this information.

As described above with respect to Figures 1 and 2, the disclosure provides a solution for efficient and scalable 3GPP mechanisms for detecting and reporting application utilization based on the data flow of the traffic from the UE 131 to the application.

In particular, novel mechanisms based on a flow trap to detect application usage in the communication network 300 are described. This is achieved by enhancing the messages and network entities shown in Figure 3 involved in the data and control paths, in particular messages 601 , 606 between AF 140 and SMF 160, messages 402, 405 between PCF 150 and SMF, messages 406, 506, 401 , 501 between AF 140 and PCF 150 and messages 403, 503, 404 between SMF 160 and UPF 170 as described below with respect to Figures 4 to 6.

Based on a Service Description and Instantiation Request, e.g., via control over AF 123 from the service provider network, novel flow trap mechanisms are used as described in this disclosure. Users utilizing the services can be located and services can be instantiated closer to the user.

Figure 4 shows a message flow chart 400 illustrating interaction between AF, PCF, SMF and UPF entities of a 3GPP mobile communication system to detect application usage based on provisioning of the UE ID.

This interaction, that requires the UE ID can be summarized as follows: A packet Flow Descriptor (PFD) is provided to the data plane. This is usually associated with a PDU (packet data unit) session. After the UE has performed association procedures.

5G Core Network supports application detection per PDU session;

UE Identity needs to be provided to the 5G Core network (application detection will only be reported for the specified UE).

An AF MUST include the UE IP address in the Npcf_PolicyAuthorization_Create message.

A report containing the detected Application ID is provided by the data plane using the user’s active session.

This can be implemented by the message flow 400 shown in Figure 4:

Message Npcf_PolicyAuthorization_Create 401 is transmitted from AF 140 to PCF 150.

Message Npcf_SMPolicyControl_UpdateNotify 402 is transmitted from PCF 150 to SMF 160.

Message PFCP Session Modification Request (App detection) 403 is transmitted from SMF 160 to UPF 170.

Message PFCP Session Report Request 404 is transmitted from UPF 170 to SMF 160. Message Npcf_SMPolicyControl_Update 405 is transmitted from SMF 160 to PCF 150. Message Npcf_PolicyAuthorization_Notify 406 is transmitted from PCF 150 to AF 140.

These messages are standardized according to 3GPP, e.g., as described in 3GPP TS23.501 and TS23.502.

As already mentioned above, the main limitation of this solution is that the UE IP address or identifier is required by most 5G core APIs to subscribe to monitor the data path or PDU session. However, in the envisioned use case, the UE IP is not available for application detection since one cannot find out beforehand where and which users will use a certain application. The PCF, SMF and UPF only support application detection on a per session basis. The PCF only provides the detected Application ID to AFs.

This disclosure solves the problem by providing an efficient and scalable flow trap mechanism to obtain information about which users are consuming a certain service/application. Two different options for message exchange as well as enhance the relevant network functions (AF, PCF, SMF, UPF) to realize the application detection are presented and described below with respect to Figures 5 and 6.

A first option that is based on AF-PCF-SMF-UPF interaction is described below with respect to Figure 5. A second option that is based on AF-SMF-UPF interaction is described below with respect to Figure 6. Then, the enhanced network functions (AF, PCF, SMF, UPF) are presented.

Figure 5 shows a message flow chart 500 illustrating a modified interaction between AF, PCF, SMF and UPF entities of a 3GPP mobile communication system to support service control without requiring the UE ID according to the disclosure.

The message flow chart 500 is associated with the first option described above.

The message flow 500 can be described as follows:

Message Npcf_PolicyAuthorization_Create 501 is transmitted from AF 140 to PCF 150. Message Npcf_AppDetection_UpdateNotify 502 is transmitted from PCF 150 to SMF 160. Message PFCP_ApplicationDetection_Request 503 is transmitted from SMF 160 to UPF 170.

Message PFCP Session Report Request 404 is transmitted from UPF 170 to SMF 160. Message Npcf_SMPolicyControl_Update 405 is transmitted from SMF 160 to PCF 150. Message Npcf_PolicyAuthorization_Notify 506 is transmitted from PCF 150 to AF 140.

Only the messages 404 and 405 correspond to messages 404 and 405 described in Figure 4 while messages 501 , 502, 503 and 506 are modified over messages 401 , 402, 403 and 406 described in Figure 4.

According to the message flow chart 500 of Figure 5, an efficient and scalable application usage detection can be realized through the following modifications of the message flow 400 shown in Figure 4:

1) Modify the PCF 150 so that it accepts a Npcf_PolicyAuthorization_Create message 501 without specifying the UE IP address. 2) PCF 150 sends a notification towards the SMF 160 (Npcf_AppDetection_UpdateNotify 502) with a new application detection subscription.

3) SMF 160 sends a new PFCP Application Detection Request node level message 503 (i.e., not session specific) towards every known PSA UPFs 170 to trigger the session-less application detection procedure.

4) The UPF 170 detects the traffic and maps the UE IP (obtained from the detected flow) to the corresponding PFCP session. Then sends the report 404 to the SMF 160 as standardized.

5) The SMF 160 sends the report 405 to the PCF 150 as standardized.

6) The Npcf_PolicyAuthorization_Notify message 506 is extended to support a flow descriptor.

In Option 1 , as shown in Figure 5, an enhanced interaction between the mentioned network functions is defined and developed. The full interaction is depicted in the message flow 500 of Figure 5. The individual messages of the message flow 500 as already described above can be summarized as follows:

1) Modified Npcf_PolicyAuthorization_Create message 501 : support policies with no UE IP Address.

2) New Npcf_AppDetection_UpdateNotify message 502: enables application detection subscription not tied to an active session or UE.

3) New PFCP node level message PFCP_ApplicationDetection_Request 503: sent towards every known PSA UPFs 170 to trigger the session-less application detection procedure.

4) Modified Npcf_PolicyAuthorization_Notify message 506: support of detailed flow descriptor information.

In the following, these new messages and enhanced interaction with the network nodes 140, 150, 160, 170 are described in more detail.

Enhanced AF > PCF interaction The interaction between the AF 140 and PCF 150 is modified and enhanced in such a way that it is possible to send application detection queries without specifing a specific UE ID or PDU session. This enables more flexibility in the requrest. The modification is focused on the AppSessionContextData structure that lists the required fields for the messages. Table 1 shown below highlights the modifications over 3GPP 29.514, Release 17, Section 5.6.2.3.

3GPP 29.514 (Release 17) AgffSessm

Modify message: Make the UE addressing parameters optional instead of mandatory!

Source: 3GPP 29.514 Release 17, Section 5.6,2.3 (partial content)

Table 1 : modifications for AF>PCF interaction

Enhanced PCF > SMF Interaction

The interaction between the PCF 150 and SMF 160 is modified and enhanced in such a way that it is possible to send queries to trigger application detection without specifing a specific UE ID or PDU session. A new message is introduced in the Npcf interface: Npcf_AppDetection_UpdateNotify 502 which provides notifications to the SMF 160 every time there is a new Application Detection request not tied to any active session. This interaction can use the DNAI as an application identifier in case the rule of single DNAI <> APP is valid.

Table 2 shown below highlights the new message structure.

Table 2: New message “Npcf_AppDetection_UpdateNotify” structure

21

SUBSTITUTE SHEET (RULE 26) Enhanced SMF > UPF Interaction

The interaction between the SMF 160 and UPF 170 is modified and enhanced in such a way that it is possible to send queries to trigger application detection without specifing a specific UE ID or PDU session. Therefore, a new Node Level message is introduced in the PFCP protocol: PFCP_ApplicationDetection_Request 503. Table 3 shown below highlights the new message structure.

Again, for the application identifier DNAI can be used instead of application ID.

Table 3: New message “PFCP_ApplicationDetection_Request” structure

Enhanced PCF > AF Interaction

The interaction between the PCF and AF is modified and enhanced in such a way that it is possible to send responses to the trigger for application detection without specifing a specific UE ID or PDU session. This is achieved by a modified AppDetectionReport data structure. Table 4 shown below highlights the modified message structure.

Table 4: Modified “AppDetectionReport” message structure

In this modified message structure, the sdfDescription (service data flow) field with type Flowinformation (defined in 3GPP 29.512, Release 17, section 5.6.2.14) is added to the AppDetectionReport data structure (3GPP 29.514, Release 17, section 5.6.2.44).

Figure 6 shows a message flow chart 600 illustrating a simplified interaction between AF, SMF and UPF entities of a 3GPP mobile communication system to support service control without requiring the UE ID according to the disclosure.

22

SUBSTITUTE SHEET (RULE 26) The message flow chart 600 is associated with the second option as described above.

The message flow 600 can be described as follows:

Message Nsmf_EventExposure_Subscribe 601 is transmitted from AF 140 to SMF 160.

Message PFCP_ApplicationDetection_Request 503 is transmitted from SMF 160 to UPF 170.

Message PFCP Session Report Request 404 is transmitted from UPF 170 to SMF 160. Message Nsmf_EventExposure_Notify 606 is transmitted from SMF 160 to AF 140.

The messages 503 and 404 correspond to messages 503 and 404 described in Figure 5 while messages 601 and 606 are new messages for this second option.

In Option 2, as shown in Figure 6, an enhanced interaction between the mentioned network functions is defined and developed. In this option, the AF 140 bypasses the PCF 150 and directly interacts with the SMF 160. The full interaction is depicted in the message chart 600 of Figure 6.

In summary, the interaction, which is based on Nsmf_EventExposure API, follows the same logic as in Option 1 and uses the following messages:

1) Modified Nsmf_EventExposure_Subscribe message 601 : By adding a new event type for application detection.

2) New PFCP new node level message PFCP_Application_Detection_Request 503: sent towards every known PSA UPFs 170 to trigger the session-less application detection procedure.

3) Modified Nsmf_EventExposure_Notify message 606: Notify the start or stop of application detection.

The details of those different interactions/modifications are described in the following.

AF > SMF interaction enhancement

To realize this interaction, two new Enum values are introduced in the SmfEvent structure defined in 3GPP 29.508 (Session Management Event Exposure Service) Release 17, Section 5.6.3.3 as shown in Table 5 below:

23

SUBSTITUTE SHEET (RULE 26)

Table 5: new Enum values introduced in the SmfEvent structure

When these events are selected:

The anyllelnd attribute of the NsmfEventExposure structure (defined in 3GPP 29.508, Release 17, section 5.6.2.2) should be set to True;

The eventSubs attribute (Structure Eventsubscription defined in 3GPP 29.508, Release 17, section 5.6.2.4) should contain the Application Identifier in the applds field.

SMF > AF interaction enhancement

To realize this interaction, the Nsmf_EventExposure_Notify should include in the EventNotification data structure (defined in 3GPP 29.508, Release 17, section 5.6.2.5):

The Event Type (APP_STA or APP_STO) using the event attribute;

The SUPI of the UE using the supi attribute;

The UE IP address using the sourceUelpv4Addr attribute;

The Flow Descriptor using the fDescs attribute.

In the following, the enhanced network functions (AF, PCF, SMF, UPF) are presented that can be applied to the 3GPP system shown in Figures 1 and 3 and corresponding message flows shown in Figures 5 and 6 and to the generic scenario shown in Figure 2.

Enhanced AF, PCF, SMF, and UPF entities to realize application detection in a mobile system

In order to realize the above-mentioned interactions, the different involved network functions, e.g., the AF 140, PCF 150, SMF 160 and UPF 170 are enhanced according to this disclosure. This enhancement is required in order to realize this advanced, data path

24

SUBSTITUTE SHEET (RULE 26) monitoring and detection, data tracking at the different locations, envisioned real time notifications, API exposure which are not possible with today’s respective network functions.

Enhanced AF

The AF 140 is enhanced to issue the modified Npcf_PolicyAuthorization_Create message 501 , as well as to handle the modified Npcf_PolicyAuthorization_Notify message 506 as shown in Figure 5 for the 3GPP system (see also Figures 1 , 3, 4 and 6). To this end, new data structures are implemented to store, add, and remove (e.g., based on timeouts) UEs matching a particular Application ID.

In the generic scenario as described above with respect to Figure 2, the application function reacts to the trigger to start flow trap mechanism. AF stores triggered requests, AF validates received notifications, AF provides specific verification of external requests, e.g., am I authenticated with the PCF, do I create a request for the whole network or subset, etc.

Enhanced PCF

The PCF 150 is enhanced to handle a different kind of policy (i.e., resulting from the modified Npcf_PolicyAuthorization_Create message 501) as well as support the modified messages (Npcf_PolicyAuthorization_Create 501 and Npcf_PolicyAuthorization_Notify 506), e.g., as shown in Figure 5 for the 3GPP system (see also Figures 1 , 3, 4 and 6). The Npcf interface is extended with a new message: Npcf_AppDetection_UpdateNotify 502 which provides notifications to the SMF 160 every time there is a new application detection request that it is not tied to any active session. The remaining core mechanisms can be reutilized from the existing application detection supporting mechanisms.

The PCF 150 accepts a new type of message subscription from the SMF 160 targeting the new application detection mechanism and the corresponding report. In supporting this, the PCF 150 incorporates new data structure as required to maintain state information related to this new subscription type.

In the generic scenario as described above with respect to Figure 2, new policies are stored related to application detection, to know which SMFs to contact, to accept notification response and verify, to store AF information, e.g., IP address, access, (those relevant to application detection). Enhanced SMF

In Option 1 , the SMF 160 subscribe in the PCF 150 to events regarding new applications via the new Npcf_AppDetection_Subscribe message on startup, e.g., as shown in Figure 5 for the 3GPP system (see also Figures 1 , 3, 4 and 6). This enables the SMF 160 to be notified when a new application requires information regarding active users. After receiving this notification, the SMF 160 sends a new PFCP_ApplicationDetection_Request message 503 to serving UPFs 170. No UE identification (either the IP Address or the PDU session ID) is exchanged in this part as the objective of this mechanism is to obtain the identification of UEs using the considered application. When the SMF 160 receives the PFCP Session Report Request message 404 with the UE IP address, the SMF 160 is able to map this address to a UE ID (e.g., SUPI) if needed. Finally, the SMF 160 receives the desired information from the UPF 170.

In Option 2, the SMF 160 handles modified messages, namely Nsmf_EventExposure_Subscribe 601 and Nsmf_EventExposure_Notify 606, e.g., as shown in Figure 6 for the 3GPP system (see also Figures 1 , 3, 4 and 5).. The interaction with the UPF 170 is the same as in Option 1 .

The existing mechanisms for application detection can be reutilized for realizing the disclosed solution with the addition of the relevant data structures to keep new state information.

In the generic scenario as described above with respect to Figure 2, SMF knows which UPF has been contacted, its status regarding application detection, it keeps track of the PCF requests (or AF in case of option 2), it may map the application detect request to a certain DNAI or a certain PDU.

Enhanced UPF

The UPF 170 handles the new PFCP_ApplicationDetection_Request message 503 and implements, in an efficient and scalable way, an application detection mechanism which extracts the address of the UE from the detected flows and maps this address to the corresponding PFCP session, e.g., as shown in Figure 5 for the 3GPP system (see also Figures 1 , 3, 4 and 6). The parameters that identify the application (IP address and transport protocol port tuple) are provided to the UPF 170 via the PFD Management procedure standardized in 3GPP 23.502 clause 4.4.3.5, allowing the UPF 170 to be capable of associating the IP and port tuple to an Application ID. The resulting “Flow Information” Information Element carries the UE IP address, as already standardized (see 3GPP 29.244 clause 8.2.61).

In the generic scenario as described above with respect to Figure 2, the UPF monitors the traffic and detects that an application is being used. It receives, controls, and manages and sends application detection requests. The UPF performs application detection in an efficient and scalable way.

While a particular feature or aspect of the disclosure may have been disclosed with respect to only one of several implementations, such feature or aspect may be combined with one or more other features or aspects of the other implementations as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms "include", "have", "with", or other variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term "comprise". Also, the terms "exemplary", "for example" and "e.g." are merely meant as an example, rather than the best or optimal. The terms “coupled” and “connected”, along with derivatives may have been used. It should be understood that these terms may have been used to indicate that two elements cooperate or interact with each other, regardless whether they are in direct physical or electrical contact, or they are not in direct contact with each other.

Although specific aspects have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that a variety of alternate and/or equivalent implementations may be substituted for the specific aspects shown and described without departing from the scope of the present disclosure. This application is intended to cover any adaptations or variations of the specific aspects discussed herein.

Although the elements in the following claims are recited in a particular sequence with corresponding labeling, unless the claim recitations otherwise imply a particular sequence for implementing some or all of those elements, those elements are not necessarily intended to be limited to being implemented in that particular sequence.

Many alternatives, modifications, and variations will be apparent to those skilled in the art in light of the above teachings. Of course, those skilled in the art readily recognize that there are numerous applications of the invention beyond those described herein. While the present invention has been described with reference to one or more particular embodiments, those skilled in the art recognize that many changes may be made thereto without departing from the scope of the present invention. It is therefore to be understood that within the scope of the appended claims and their equivalents, the invention may be practiced otherwise than as specifically described herein.