CN117545040A - A method of routing data from an application client to an application server via the core network of a cellular network - Google Patents

Abstract

A method for routing data through a cellular network from an application client at a user equipment, UE, to an application server via a core network. The network operator platform receives an initial request from the UE to establish a communication session between the application client and the application server. The network operator platform then generates configuration information for configuring the application client to establish the communication session. The network operator platform further generates configuration information for configuring the core network to establish the communication session. Next, the application client is configured according to the application client configuration information and the core network is configured according to the core network configuration information such that the core network sends the generated urs to the UE for storage in a urs repository at the UE.

Description

Routes data from application clients to application services via the cellular network's core network server method

Technical field

A method for routing data over a cellular network from an application client at a user equipment UE to an application server via the core network. The approach takes advantage of enhanced routing options in 5G, the fifth-generation technology standard for broadband cellular networks. This method allows the network operator to identify the origin (including specific applications and UEs) and type of data traffic received at the core network via network slicing as part of a communication session.

Background technique

Different applications and services running at user devices may benefit from different network characteristics (eg, service-level requirements such as bandwidth and/or latency) to provide a better customer experience or for the application to function properly. For example, a video streaming service might benefit from high bandwidth but be less sensitive to latency, while an online gaming application might prioritize lower latency. Under 3G or 4G, the third and fourth generation technology standards for broadband cellular networks respectively, different applications often utilize the same data bearer in order to provide services, which data bearer provides a common set of network characteristics. However, options to optimize data routing are available in 5G, the fifth generation technology standard for broadband cellular networks.

5G provides a network architecture that allows network slicing. Network slicing describes the provision of distinct channels (or "slices") between user equipment and the core network, or outside the data network where application servers reside. The use of network slicing provides a mechanism to multiplex virtual and independent channels on the same physical network infrastructure. Each network slice provides an end-to-end channel that may or may not be isolated from other slices. Each network slice can have different network characteristics that can be customized to meet the requirements of a specific application. Therefore, in principle, specific network slices can be allocated by the network to provide network characteristics best suited to the type of data traffic generated by a specific application or for a specific service.

Network slices are allocated according to the type of data services to be carried on the network slice. For example, Application A may generate data traffic in a first specialized service category with a preference for low latency. Application B may generate data traffic in a second specialized service category with a preference for high bandwidth. Under 5G, Application A can be routed through a first network slice (optimized for traffic from applications requiring variable bandwidth rates but low or ultra-low latency), while Application B can be routed through a second network slice (optimized for traffic from applications requiring variable bandwidth rates but low or ultra-low latency). Optimized for applications with high bandwidth requirements). Routes from the UE via network slices are allocated at the UE by consulting the stored UE routing policy (URSP) according to the 3rd Generation Partnership Project (3GPP) standards. Each URSP associates a specific type of data (or a specific specialized service class) to a specific network slice and data network name (DNN).

While proper selection of network slices for routing data traffic can improve user experience by tailoring network characteristics for a given application, further improvements can be achieved by network operator customization of routing at the edge of the core network to the data network where the application servers reside. It is possible. However, such network operator-tailored routing is only beneficial if there is some understanding of the content of the data traffic and its origin. Many applications may generate data traffic of the same type and the same specialized service class (and therefore be routed via the same network slice). Therefore, network operators need more information about data traffic in order to more precisely distinguish the processing or routing of data.

Although it is specified within the 5G standards to provide the core network with information about the origin and content of the data traffic, in practice this information is not available from the core network due to privacy regulations imposed by the operating system at the user equipment (or UE). The tendency is to be vague. In particular, applications running at the UE may identify themselves to the UE's operating system, but the operating system typically does not convey to the cellular network identification of specific types of network traffic, or identification of the specific application from which the data originated. Loss of this information at the core network prevents network operators from providing optimal paths for data associated with specific applications through the cellular network. Furthermore, since the operating system at the user equipment has no way of knowing the current network conditions, the operating system at the UE itself cannot instruct specific processing of data passing through the cellular network. As a result, some of the benefits offered by 5G may be lost.

One option to overcome this problem is for the network to inspect data packets from specific users to identify the specific type of network traffic and its origin. However, this is only possible if the data traffic itself is not encrypted. Additionally, such checks can increase the latency of data transmission over cellular networks.

Therefore, there is a need for a method for routing data over a cellular network from an application client at a user equipment (UE) to an application server via the core network, which overcomes these shortcomings in order to provide applications via the application client provide the best possible experience to our users.

Contents of the invention

In this context, a method for routing data over a cellular network from an application client at a user equipment (UE) to an application server via the core network is provided according to claims 1 to 11 . Also described is a computer program according to claim 12, a UE according to claim 13, a network entity (or system of network entities) according to claim 14 and a network operator platform according to claim 15.

Most generally, a method for routing data over a cellular network from an application client at a user equipment (UE) to an application server via a core network is described. The network leverages 5G capabilities, including network slicing. The approach involves using a network operator platform to configure application clients and the core network. The application client is configured to address requests for communication sessions between the application client and the application server to a token data network name (DNN) in order to identify the application client and the UE to an operator of the core network. The core network is configured to route data addressed to the token DNN to the designated DNN (by the core network changing the token DNN of the designated DNN upon receipt of a request addressed to the token DNN to establish a communication session. accomplish). By providing the network operator with information about the source and type of data traffic received from the UE (by signaling using the token DNN, which can be specific to a given application session), the network operator can Realize specific, customized processing and disposal of data services.

In a first aspect, there is a method for routing data over a cellular network from an application client at a user equipment (UE) to an application server via a core network, the method comprising:

An initial request is received from the UE at the network operator platform to establish a communication session between the application client and the application server, the communication session being routed via a network slice for routing belongings sent from the application client to the application Data of the category of the server’s data service;

Configuration information generated by the network operator platform for configuring the application client to establish a communication session. The application client configuration information includes:

Instructions causing the application client to address subsequent requests to establish a communication session with the application server to the token data network name DNN;

Configuration information generated by the network operator platform for configuring the core network to establish communication sessions. The core network configuration information includes:

Instructions causing the core network to change the token DNN of the specified DNN upon receipt of a request to establish a communication session addressed to said token DNN;

Cause the core network to generate instructions for the UE routing policy URSP to be sent to the UE, and the generated URSP rules associate the categories of data services sent from the application client to the application server with the token DNN and network slices;

Configure the application client according to the application client configuration information;

Configure the core network according to the core network configuration information, thereby causing the core network to send the generated URSP to the UE for storage in a URSP repository at the UE;

wherein, after configuring the application client and the core network, a subsequent request for establishing a communication session between the application client and the application server is sent from the application client via a network slice, which indicates the category of the data traffic and is addressed to the token DNN, Core Network identifies information about the data in the communication session and the application client from which that data is routed by receiving the token DNN, in order to facilitate specific processing or disposition of the communication session by the network operator.

In other words, before establishing a communication session with the application server, a communication session is first established with the network operator platform. The network operator platform generates configuration information used to reconfigure the application client and the core network for data routing in subsequent communication sessions between a specific application client and the application server. One piece of configuration information generated by the network operator platform is the token DNN, which is generated taking into account the identity of the application client and UE. During configuration, the token DNN is sent from the network operator platform to the application client for use in subsequent requests to establish a communication session with the application server. The token DNN is also sent to the core network to allow the core network to identify the origin of data transmitted in subsequent data sessions. The core network is further configured by the network platform such that upon receipt of a request to establish a subsequent communication session, the core network replaces the token DNN with the designated or predetermined "real" DNN of the data network where the application server resides.

Receipt of a request with a specific data type and addressed to the token DNN at the core network signals the network operator information about the application client and UE, as well as the type of data to be routed through the communication session. By gaining knowledge of the origin and nature of data sent in subsequent communication sessions, network operators can tailor the handling of data passing through the cellular network. In particular, the processing can be optimized for a given application. This in turn improves the overall experience for end users utilizing that particular application.

Preferably, the cellular network has 5G (fifth generation technology standard for broadband cellular networks) capabilities. An application client will be understood as a software element at a UE, which is a user equipment such as a mobile device or a computer. The application client transmits, processes and receives data from the application server in order to provide the application functionality to the end user of the UE.

A network operator platform is an entity of a cellular network that provides functionality to expose core network capabilities that can be used by the network operator itself or by third parties. A network operator platform is an entity that allows network operators, as well as third-party developers and engineers, to monitor, adapt, and program aspects of the network and data routing.

A communication session may describe any connection that routes data between two entities (here, between an application client and an application server) over a cellular network. In 5G, the communication session may be a PDU session, which provides end-to-end connectivity between elements or applications at the UE and a specific data network, such as the Internet or a private network, via the User Plane Function (UPF) of the core network. The data network to be accessed is identified or addressed by a data network name (DNN). In 5G, a given PDU session occurs on a single network slice and is connected to the DNN. Communication session requests are sent by the UE and are addressed to a given DNN, directed via a specific network slice according to the UE routing policy (URSP). URSP are routing rules stored in the repository at the UE. The URSP may be pre-configured in the UE and may be sent or updated from the core network (e.g., although not exclusively, when the UE registers or connects to the operator's network).

The method may further include the following steps:

At the core network, receive subsequent requests to establish a communication session from the application client via the network slice and addressed to the token DNN based on the generated URSP;

Change the token DNN of the specified DNN at the core network;

Establishes a communication session between the application client and the application server via the specified DNN and network slice, and has network-assigned properties.

In particular, at the UE, a request to establish a communication session utilizes the generated URSP together with the token DNN together with the application data type. In turn, and based on the previous configuration of the network operator platform, the core network then exchanges the token DNN for the real, designated DNN. Therefore, the network slice extends from the UE to the edge of the core network (which may be a multi-access edge computing (MEC) server or a peer-to-peer connection to an application server), and data traffic may undergo specific processing during routing through the network or Disposal.

The configuration information used to configure the core network may further include one or more of the following:

instructions for the core network to associate subsequent requests to establish communication sessions with UE subscriptions using network slicing;

Instructions to alert the network operator platform of changes in the geographical location of the UE;

Instructions to alert the network operator platform if the application has been started or stopped;

Instructions to alert the network operator platform of network conditions that may affect the quality of service associated with application clients; and

Information related to the Domain Name System DNS server at the core network for use in resolving the application server's IP address during communication session establishment.

In other words, additional configuration information may be used to allow more precise charging of users when the UE moves or when taking into account application server conditions and/or network conditions, or when starting or stopping applications related to application clients , change the routing of data traffic in the communication session. The configuration information may further be used to change further characteristics of routing through the core network to more generally improve quality of service metrics or quality of experience.

The configuration information used to configure the application client may further include:

Instructions to address DNS servers using DNS over Hypertext Transfer Protocol Secure HTTPS; and/or

Information related to the Domain Name System DNS server at the core network for use in resolving the application server's Internet Protocol IP address during communication session establishment.

DNS over HTTPS can be used to provide greater privacy for communication sessions. The information related to the DNS server may include the identification of the DNS server at the core network.

In view of the common identifier derived from the identifier of the UE and the identifier associated with the application client requesting access to the network slice, the core network configuration information and/or the application client configuration information can be processed with the core network through the network operator platform. Generated by the interaction of network repository and configuration node. In this way, the configuration information (including the token DNN) is customized to the application client and the application at the UE, and may be time-limited or application-specific.

After the step of receiving the initial request to establish a communication session between the application client and the application server, the method may further include:

Obtain authorization from the application client's end-users by the network operator platform to share information to identify the origin of data originating from the application client to the core network;

Authorization for application clients to use network slicing is obtained by the network operator platform from the core network.

Obtain authorization from the end user to mitigate privacy concerns associated with passing information about the origin and type of data traffic from the application client to the core network. In particular, end users are required to voluntarily choose application traffic at the user's device to be processed in a specific manner.

Obtaining authorization from an end user of the application client to share information to identify the origin of data originating from the application client to the core network may further include receiving from the application client an application identifier associated with the application client requesting access to the network slice as authorize; and

Obtaining authorization for the application client to use the network slice may further comprise receiving as the authorization a UE identifier corresponding to the UE's subscription to use the network slice;

Wherein, given the identifier of the UE and the identifier associated with the application client requesting access to the network slice, core network configuration information and/or are generated through interaction of the network operator platform with the network repository and configuration node at the core network. Or the application client configuration information can further include:

Construct a universal identifier from the UE identifier and the application identifier;

Wherein the configuration information for configuring the application client and for configuring the core network is generated through interaction of the network operator platform with the network repository and configuration nodes at the core network using universal identifiers.

In other words, the configuration information is generated using knowledge of the application associated with the application client and knowledge of the UE. This allows customization of configuration information so that the routing of data traffic between application clients and application servers provides an optimal user experience. Configuration information (and therefore data routing) can be further customized to ensure regulatory requirements are met (such as retaining data within the EU to comply with GDPR regulations).

Once the universal identifier has been constructed, the core network configuration information generated by the network operator platform may further include instructions for the core network to store the universal identifier together with subscriber data associated with the network slice and the specified DNN. In other words, the core network associates a universal identifier with the subscriber, the network slices that the subscriber is allowed to use, and with both the token DNN and the designated DNN. This allows the network operator (via the core network) to understand the origin and nature of the data traffic in subsequent communication sessions.

The initial request to establish a communication session between the application client and the application server may be routed between the application client and the network operator platform via a network slice and addressed to the network operator platform DNN. In a specific example, an initial request to establish a communication session between an application client and an application server may be routed from the UE based on an initial URSP stored in a URSP repository in the UE, which initial URSP will be retrieved from the application client in the specific UE. The categories of data services sent by the end are associated with the network operator platform DNN and network slicing. For example, an application client generates data of a specific data type, which is routed to the network operator platform (addressed with the network operator platform DNN) via the network slice associated with the specific data type according to the initial URSP.

The initial URSP may be updated in or added to the URSP repository at the UE upon the UE's initial registration with the core network, or may be stored in the URSP at the UE by the network operator prior to the UE's initial registration with the core network. Pre-configured in the library. The generated URSP and the initial URSP can have relative rule priority values that force the generated URSP to be evaluated before the initial URSP.

In a second aspect, a computer program is described, comprising when operated by a processor of a UE of the cellular network, a network operator platform or an entity or entity system of the core network, for transferring data passing through the cellular network from the core network via the core network. The application client at the user equipment UE routes instructions to the application server, which instructions cause the processor to perform the method described above.

In a third aspect, there is a user equipment UE, which is in a cellular network and includes an application client configured to operate according to the method described above.

In a fourth aspect, there is an entity or entity system of a core network of a cellular network configured to operate according to the method described above.

In a fifth aspect, there is a network operator platform configured to operate according to the method described above.

In a fifth aspect, there is a cellular network including a UE, a network operator platform and a core network entity, each configured to operate according to the method described above.

Description of drawings

The present disclosure may be put into practice in various ways and the preferred embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which:

Figure 1 shows a flowchart illustrating steps in an example of a method for routing data over a cellular network from an application client at a user equipment (UE) to an application server via a core network;

Figure 2 shows the elements of the system to be configured during the configuration phase; and

Figure 3 shows elements of the same system during establishment of a communication session between an application client and an application server via the core network of a cellular network.

In the drawings, identical components are designated with the same reference numerals. The drawings are not to scale.

Detailed ways

Users can subscribe to specialized services provided by network operators. For example, users can subscribe to network packs to allow an improved user experience for streaming applications or gaming applications.

A method of routing data over a cellular network from an application client at a user equipment (UE) to an application server via a core network is provided. This approach aims to provide the best possible user experience, particularly taking advantage of the more adaptive network routing available in 5G. This approach allows the core network to identify the origin and nature of data routed through it without relying on the UE's operating system to provide specific information about the content or origin of the data packets.

In the described approach, the routing of data from the UE to the edge of the core network occurs through network slices assigned to the specialized service classes required by the application. Each network slice provides network characteristics optimized for the described service class. However, distinguishing data traffic by specialized service categories is not particularly precise because many different applications may generate data that fits the same service category. Therefore, the method of the present disclosure allows the core network to receive additional information (both UE and information of the application from which the data originates) about the origin and nature of data traffic routed through the cellular network. This allows network operators with visibility into network conditions to route data in a specialized or customized manner (especially through the core network) in order to provide improved conditions for the operation of specific applications and therefore provide a better user experience.

The method utilizes the network operator platform in order to configure the entities involved in the establishment of the communication session in the cellular network and at the UE. In particular, during the initial configuration phase, the network operator platform reconfigures the application client and the core network in view of the UE's identifier and the identifier associated with the application client. More specifically, when establishing a communication session with an application server, the network platform generates a token Data Network Name (DNN) to be addressed in the application client's requests. When received by the core network, the token DNN is treated as an identifier of the originating application and UE. The core network exchanges the token DNN for a real DNN, while knowledge of the origin of the data traffic can be used by the network operator to assign more accurate or customized routing of data through the cellular network.

In some examples, knowledge of the origin or nature of the data traffic in a communication session allows data to be directed to specific peers or servers that may have been established by means of an agreement between the network operator and the application provider. Additionally or alternatively, data traffic may be rerouted under the control of the network operator (eg, in view of user mobility or network congestion). In yet other examples, knowledge of the source or nature of the data traffic allows the data traffic to be provided with special treatment, such as using different radio types, or to separate the traffic into fixed and mobile access, or to be given a way to interact with the user or application that may already be in use. The guaranteed bitrate agreed upon in the provider's contract. Finally, this knowledge could allow operators to monetize specific data services with greater precision or granularity.

Configuration and configuration information generated as part of the disclosed methods may be application session specific, time-limited, or permanent. Configuration according to this method can persist across more than one application session.

As outlined here, the method is described in more detail in four stages as follows:

A. Subscriber registration;

B. Establish a communication session with the network operator platform;

C. Configuration; and

D. Execute.

The steps of each phase are described in more detail below, although not all steps are essential to the practice of the invention. A flow chart of the steps of the method is shown in FIG. 1 .

It will be understood that Phase A (user registration) may form part of the initial registration of the UE to the core network. Phases B and C (Establishment of a communication session and configuration with the network operator platform) relate to the configuration of the system according to the method, and phase D relates to the establishment of a communication session within the configured system.

Phase A: Subscriber Registration

This stage registers the user equipment (UE) with the network operator in order to identify the user as a subscriber to a specific service(s) provided by the network operator.

The steps in Phase A are:

Step 1: A registration request is sent from UE 5 to core network 50. The request may be sent from the modem 30 or the UE higher layer software, depending on the particular implementation. Typically, the registration request is sent from the modem layer, but the content of the registration request can be generated by other layers in the UE 5.

Step 2: Check the subscriber details (with UDM (Unified Data Management) in the core network 50) to verify whether the user is subscribed to use one or more network slices, each network slice used to route data traffic in a specific specialized service category.

Step 3: The core network 50 sends a registration acceptance message to the UE 5. The registration acceptance message includes a list of network slices that the UE 5 is allowed to use. The list of network slices includes one or more specific network slices 100 that are to be used by the corresponding one or more specialized service classes. Each of one or more specialized service classes may have a different set of network characteristics (such as different bandwidth, latency, etc.). Each network slice can be identified by S-NSSAI (Single Network Slice Selection Assistance Information), which can be associated with a specific specialized service class. For example, a first specific network slice designated S-NSSAI-a 110 is for use by a first specialized service class.

Step 4: Optionally, the core network 50 returns one or more new URSPs (UE routing policies) to the UE 5. One or more new URSPs are stored in the URSP repository 20 at the UE 5. Typically, each URSP associates data traffic classified within a given one of one or more specialized service classes with a specific network slice and a Data Network Name (DNN). Within the disclosed method, the one or more new URSPs include a first URSP that associates data traffic in a first specialized service category with the network slice S-NSSAI-a and with the network operator platform DNN op_platform_DNN.

Phase B: Establishing a communication session with the network operator platform

At this stage, an initial communication session (PDU session) is established between the application client and the network operator platform. A network operator platform is an entity that allows developers to interact with an operator's network and ultimately design applications or products that can select and define network requirements for their use.

The steps in Phase B are:

Step 5: The application client 10 requests to establish a communication session with the application server 70 for a specific application, the data service from which application belongs to the first specialized service category (first data type).

Step 6: UE 5 (more specifically, modem 30) consults URSP repository 20 to determine how to route the application client request. Modem 30 identifies the URSP as suitable for a particular specialized service class. In this example, the first URSP (updated in URSP repository 20 in phase A) is identified as being suitable for the first specialized service category. The first URSP associates the application client request, which includes an indicator of the first specialized service class as a traffic descriptor, with the network operator platform DNN (op_platform_DNN) and the network slice S-NSSAI-a.

An example of a first URSP is:

Step 7: According to the first URSP, a request to establish a communication session is sent from the UE 5 to the network operator platform 40 via the network slice S-NSSAI-a 110 and addressed op_platform_DNN.

Step 8: The initial communication session is established between the application client 10 at the UE 5 and the network operator platform 40.

Phase C: Configuration

Within the initial communication session established in Phase B, in Phase C the network operator platform is used to authorize special handling of data traffic from the application and configure the application client, UE and core network to allow access through the preferred network slice Establish subsequent communication sessions and notify the network of the origin and nature of the data service (including identification of the originating UE and application). The entities during configuration phase C are depicted in Figure 2.

The steps in Phase C are:

Step 9: The network operator platform 40 requests and receives authorization from the core network 50 for the application client 10 to use the specific network slice. For example, in this example, the network operator platform 40 requests authorization to use the network slice S-NSSAI-a 110 assigned to the first specialized service class.

Step 10: The network operator platform 40 requests from the end user of the UE 5 via the application client 10 authorization for special routing of data generated during the requested communication session and/or authorization for sharing of information that allows access from the application client The source of end 10's data traffic is identified by the network operator.

Step 11: The application client 10 returns the identifier of the application client 10 (here denoted client_ID) to the network operator platform 40 as an authorization, which includes the identification of the specialized service class it intends to use.

Step 12: The network operator platform 10 constructs a universal identifier for applications and users (here designated as generic_ID) for use during the life cycle of the requested communication session. The universal identifier (generic_ID) is generated based on both the application client identifier (client_ID) and the UE identifier (UE_ID). The UE identifier can take various forms, including the Subscription Permanent Identifier SUPI (the equivalent in 5G to the International Mobile Subscriber Identity IMSI in 4G), or the Mobile Station International Subscriber Directory Number MSISDN (which is the subscriber's telephone number). In one example, the core network records the SUPI from the user's first connection with the network operator in its repository, but this identifier can be passed directly by the application client or UE during the authorization phase at step 10 Network operators.

Step 13: The network operator platform 10 constructs a betokened DNN (here marked as token_DNN). This can be considered a pseudo-DNN or virtual DNN, which is not a real network address. The Predictive DNN is used to configure and alert (or signal) the core network 50 that the application is using a specialized service class, and also to identify to the network operator when a request addressed to the Predictive DNN is received at the Core Network 50 Application client 10 and UE 5.

Step 14: Using the universal identifier (generic_ID), the network operator platform 40 interacts with one or more network repositories 90 and/or network configuration nodes 80 to configure and prepare the core network 50 for use by the application client at the UE 5 Communication session initiated by end 10. The network repository 90 and network configuration node 80 may include UDM (Unified Data Management), UDR (Unified Data Repository), NEF (Network Exposure Function) and PCF (Policy Control Function)). Information related to the UE subscription is retrieved and further configuration information for applying the configuration of the client 10 and the core network 50 is generated.

Configuration information generated by the network operator platform 40 for the configuration of the core network 50 includes:

i. Instructions for the core network 50 to associate a universal identifier (generic_ID) with a UE subscription to a network slice (eg, S-NSSAI-a110) that is to be used for application-generated data to be classified therein specialized service categories.

ii Instructions for the core network 50 to associate the prediction DNN with the UE subscription to the network slice (e.g., S-NSSAI-a110) that is to be used for the specialized service class in which the generated data is classified. .

iii. Instructions for causing the core network 50 to generate another new URSP (herein designated as the second URSP) to be sent to the UE. The second URSP associates the traffic descriptor (TD) of the specialized service class in which the data generated by the application is classified with the network slice of the specialized service class and the prediction DNN (token_DNN). The routing descriptor in the second URSP does not include any DNN. The rule priority value of the second URSP is given relative to the value of the first URSP (generated as part of the Registration Accept message in step 4) in order to force the second URSP to be evaluated at the UE before the first URSP is evaluated.

An example of a second URSP is:

iv. When a communication session request addressed to said token_DNN is received at the core network, for causing the core network 50 (specifically, the repository containing subscriber policies) to allow the token_DNN for A specific subscriber and an instruction to exchange the heralded DNN for another specified or predefined DNN. Specifies that the DNN is the real or real address used to access the data network where the application server resides. In some cases, a designated DNN may be selected by the core network due to transient network conditions or due to data network conditions as warned by the network operator platform.

v. Optionally, instructions to alert the network operator platform 40 when the geographical location of the UE 5 changes. This can trigger a reconfiguration of the network operator's platform, for example by repeating some steps of the described method.

vi. Optionally, an instruction to alert the network operator platform 40 whether the application is started or stopped. This may trigger timed actions related to (re)configuration of application clients and core network.

vii. Optionally, charging information and quality of service (QoS) information related to specific applications in UE 5.

viii. In some cases, a specific DNS server 60 in the core network 50 may be identified to be used in subsequent communication sessions.

The information retrieved by the network operator platform 40 from the UDR (Unified Data Repository) through the UDM at the core network 50 includes subscription information related to the usage of the Multi-Access Edge Computing (MEC) service by the UE 5 . This can be used to configure the application client 10 with information related to the use of edge computing features.

The configuration information compiled or generated by the network operator platform 40 for configuring the application client 10 includes:

a) Token DNN (token_DNN) used in subsequent requests of the communication session between the application client 10 and the application server 70 .

b) Optionally, in the case where the subscriber has subscribed to an edge computing service provided by the network operator itself or agreed with the application provider, use the network operator's domain name server via Hypertext Transfer Protocol Secure (HTTPS) (DNS)(DoHH) to resolve the application server address via the DNS server 60 at the core network 50. A specific DNS server 60 in the core network 50 can be identified to be used.

Step 15: The network operator platform 40 provides core network configuration information to the core network 50, and the core network configuration information is used to configure the core network 50.

Step 16: Core Network Reconfiguration A configuration update message is triggered to the UE 5 using non-access layer signaling according to the standard procedure described in 3GPP TS 23.502. The configuration update message includes the second URSP generated by the network operator platform 40 at step 14 (configuration information iii of step 14).

Step 17: After receiving the configuration update message, update the URSP repository 20 at the UE 5 with the second URSP.

Step 18: The network operator platform 40 provides application client configuration information to the application client 10, and the application client configuration information is used to configure the application client 10.

Phase D: Execution

In this phase, the application client initiates a new communication session between the application client and the application server via the core network. A communication session is established based on the configuration imposed in Phase C. The entities during execution phase D are depicted in Figure 3 .

Phase D steps include:

Step 19: The application client 10 sends a request for a new communication session between the application client 10 and the application server 70 . The request from the application client 10 to the UE 5 modem layer 30 includes a token_DNN and an identification of the specialized service class (here the first specialized service class) used by the application as a traffic descriptor (TD). The request from the application client 10 may include a request to obtain a DNS server address for further resolution of the application server address via the DNS server 60 at the core network 50 . This may be done if the application client has not been configured with DNS settings during the configuration phase.

Step 20: The UE 5 (specifically, the modem layer 30) consults the URSP repository 20 and identifies a second URSP (as previously provided at step 14) that will predict the DNN (token_DNN) and the first specialized service class with the first network Slice (S-NSSAI-a 110) associated.

Step 21: A request to establish a new communication session is sent by the UE 5 to the core network 50 (in particular, to the Access and Mobility Management Function (AMF) in the control plane of the core network 50). The request is addressed via the network slice token DNN (token_DNN) for the first specialized service class (S-NSSAI-a 110).

Step 22: The core network 50 (eg, at the control plane level) changes the token DNN (token_DNN) of the designated DNN (as specified in the configuration information iv of step 14). Requests for communication sessions are sent to the specified DNN.

Step 23: If configured to use a network DNS server, a DNS query is signaled from the application client 10 towards the DNS server 60 located in the operator network, using DoH, if configured in the application client, to obtain the application client The address of the application server with which peer 10 intends to communicate.

Step 24: Connect the communication session between the application client 10 and the application server 70 through the network slice S-NSSAI-a 110 allocated by the network and according to specific processing or handling by the network operator.

Network operator specific processing or handling can be assigned by the network operator because the network operator knows the source and nature of the data traffic within the communication session (including the identity of the specific application and UE). Network operator assigned attributes for data processing may allow data traffic in a communication session to be directed to specific peers or servers that have been established by means of an agreement between the network operator and the application provider. Additionally or alternatively, data traffic may be rerouted under the control of the network operator (eg, due to UE mobility, network congestion, or other transient network conditions). In still further examples, knowledge of the origin of the data traffic permits special treatment to be provided to the data traffic, such as using different radio types or frequency bands, or splitting the traffic into fixed and mobile access, or being given a way to deal with the problem that may already exist with users or applications. The guaranteed bitrate agreed upon in the provider's contract. Finally, the network operator's knowledge of the origin of the data traffic may allow the operator to monetize specific data traffic with greater precision or granularity.

It will be understood that the features disclosed herein may be combined in any way and are not limited to the specific implementations described above. Each feature disclosed in this specification may be replaced by alternative features serving the same, equivalent or similar purpose, unless stated otherwise. Therefore, unless expressly stated otherwise, each feature disclosed is one example only of a series of generally equivalent or similar features.

As used herein, including in the claims, the singular form of a term herein shall be construed to include the plural form and vice versa unless the context indicates otherwise. For example, singular references such as "a" or "an" included in the claims mean "one or more" unless the context dictates otherwise. Throughout the specification and claims of this disclosure, the words "includes," "includes," "has," and "contains," as well as variations of the words such as "comprising" and "comprises" or the like means "including but not limited to" and is not intended to (and does not) exclude other components.

The use of any and all examples, or exemplary language ("such as," "such as," "such as," and similar language) provided herein is intended merely to better illuminate the invention and does not pose a limitation on the scope of the invention unless otherwise specified. There is a statement. No language in the specification should be construed as indicating any non-claimed element as essential to the practice of the invention.

Any steps described in this specification may be performed in any order or concurrently, unless otherwise indicated or the context requires otherwise. All aspects and/or features disclosed in this specification may be combined in any combination, except combinations in which at least some such features and/or steps are mutually exclusive. In particular, the preferred features of the invention apply to all aspects of the invention and can be used in any combination. Likewise, features described in unnecessary combinations may be used individually (not in combination).

Claims (16)

1. A method for routing data over a cellular network from an application client at a user equipment UE to an application server via a core network, the method comprising: Receive, at the network operator platform, an initial request from the UE to establish a communication session between the application client and the application server, the communication session to be routed via the network slice for routing belonging to the application client. Data of the category of data services to the application server; Configuration information generated by the network operator platform for configuring the application client to establish a communication session. The application client configuration information includes: Instructions causing the application client to address subsequent requests to establish a communication session with the application server to the token data network name DNN; Configuration information generated by the network operator platform for configuring the core network to establish communication sessions. The core network configuration information includes: Instructions for causing the core network to change the token DNN of a specified DNN upon receipt of a request to establish a communication session addressed to said token DNN; Instructions for causing the core network to generate a UE routing policy URSP to be sent to the UE, the generated URSP rules being associated with categories of data traffic sent from the application client to the application server with token DNNs and network slices; Configure the application client according to the application client configuration information; Configure the core network according to the core network configuration information, thereby causing the core network to send the generated URSP to the UE for storage in a URSP repository at the UE; wherein, after configuring the application client and the core network, a subsequent request for establishing a communication session between the application client and the application server is sent from the application client via a network slice, which indicates the category of the data traffic and is addressed to the token DNN, Core Network identifies information about the data in the communication session and the application client from which said data is routed by receiving the token DNN, in order to facilitate specific processing or disposition of the communication session by the network operator. 2. The method of claim 1, wherein the token DNN is a virtual DNN, the virtual DNN is not a real network address, and wherein the token DNN signals to a network operator platform about application clients and Information about the UE and the type of data to be routed through the communication session. 3. The method of claim 1 or claim 2, further comprising: At the core network, receive subsequent requests to establish a communication session from the application client via the network slice and addressed to the token DNN based on the generated URSP; At the core network, change the token DNN of the specified DNN; Establishes a communication session between an application client and an application server via a specified DNN and network slice, and has network-assigned properties. 4. The method according to any one of claims 1 to 3, wherein the configuration information for configuring the core network further includes one or more of the following: instructions for the core network to associate subsequent requests to establish communication sessions with UE subscriptions using network slicing; Instructions to alert the network operator platform of changes in the geographical location of the UE; Instructions to alert the network operator platform if the application has been started or stopped; Instructions to alert the network operator platform of network conditions that may affect the quality of service associated with application clients; and Information related to the Domain Name System DNS server at the core network for use in resolving the application server's IP address during communication session establishment. 5. The method of any preceding claim, wherein the configuration information for configuring the application client further comprises: Instructions to address DNS servers using DNS over Hypertext Transfer Protocol Secure HTTPS; and/or Information related to the Domain Name System DNS server at the core network for use in resolving the application server's Internet Protocol IP address during communication session establishment. 6. A method according to any preceding claim, wherein the core network configuration information and/or the application client configuration information are passed in view of an identifier of the UE and an identifier associated with the application client requesting access to the network slice. Generated by the interaction of the network operator platform with the network repository and configuration nodes at the core network. 7. The method of claim 6, further comprising, after the step of receiving an initial request to establish a communication session between the application client and the application server: Obtain authorization from the application client's end user by the network operator platform to share information identifying to the core network the origin of data originating from the application client; and/or Authorization for application clients to use network slicing is obtained by the network operator platform from the core network. 8. The method of claim 7, wherein obtaining authorization from an end user of an application client to share information to identify the origin of data originating from the application client to the core network further comprises receiving and requesting access to the network slice from the application client The application identifier associated with the application client as the authorization; and/or Obtaining authorization for the application client to use the network slice further includes receiving as the authorization a UE identifier corresponding to the UE's subscription to use the network slice; Wherein, given the identifier of the UE and the identifier associated with the application client requesting access to the network slice, core network configuration information and/or are generated through interaction of the network operator platform with the network repository and configuration node at the core network. Or the application client configuration information includes: Construct a universal identifier from the UE identifier and the application identifier; Wherein the configuration information for configuring the application client and for configuring the core network is generated through interaction of the network operator platform with the network repository and configuration nodes at the core network using universal identifiers. 9. The method of claim 8, wherein the core network configuration information further includes: Instructions to cause the core network to store the universal identifier along with subscriber data associated with the network slice and both the token DNN and the designated DNN. 10. A method according to any preceding claim, wherein an initial request to establish a communication session between an application client and an application server is routed between the application client and the network operator platform via a network slice and is Addressed to network operator platform DNN. 11. The method of claim 10, wherein an initial request to establish a communication session between an application client and an application server is routed from the UE according to an initial URSP stored in a URSP repository in the UE, the initial URSP The categories of data traffic sent from the application client are associated with the network operator platform DNN and network slicing. 12. The method of claim 11, wherein the initial URSP is updated in or added to a URSP repository at the UE when the UE initially registers with the core network, or when the UE initially registers with the core network. Previously pre-configured by the network operator in the URSP repository at the UE. 13. A method according to claim 11 or claim 12, wherein the generated URSP and the initial URSP have relative rule priority values that force the generated URSP to be evaluated before the initial URSP. 14. User equipment UE, being in a cellular network and comprising an application client configured to operate according to the method of any one of claims 1 to 13. 15. An entity or entity system of a core network of a cellular network configured to operate according to the method of any one of claims 1 to 13. 16. A network operator platform configured to operate according to the method of any one of claims 1 to 13.