Collaboration between mobile network operators for mobile edge computing applications

Abstract

Various exemplary embodiments relate to routing data traffic for mobile edge computing in a wireless communication network. Configuration data associated with data traffic of at least one user equipment in a geographical area can be obtained in a home public land mobile network. The configuration data can include a mapping of the data traffic to an identifier of at least one co-located public land mobile network that provides access to an edge application server in the geographical area. The home public land mobile network routes the data traffic to the co-located public land mobile network in accordance with the configuration data.

Description

Technical Field

[0001] Various exemplary embodiments generally relate to the field of communication networks. Specifically, some exemplary embodiments relate to routing data traffic for mobile edge computing in wireless communication networks. Background Technology

[0002] Communication networks can utilize multi-access edge computing (MEC), which allows computational tasks to be processed and executed in appropriate edge application servers (EAS) located relatively close to the user equipment (UE). However, mobile network operators (MNOs) may lack the necessary MEC infrastructure and other resources to serve the UE. Summary of the Invention

[0003] The present invention is provided to introduce a selection of concepts in a simplified form, which will be further described in the following detailed description. The purpose of this present invention is to identify key or essential features of the claimed subject matter, and it is not intended to limit the scope of the claimed subject matter.

[0004] The purpose of this disclosure is to enable a UE to access an edge application server of another public land mobile network (PLMN) through the radio access network of its home PLMN. The above and other objectives can be achieved by the features of the independent claims. Other implementations are apparent from the dependent claims, the specification, and the drawings.

[0005] Firstly, a network node for data traffic routing is provided. The network node can be used to: acquire configuration data associated with data traffic of at least one user equipment in a geographical area on a home public terrestrial mobile network (PLMN), wherein the configuration data includes a mapping relationship between the data traffic and identifiers of at least one co-located PLMN used to provide access to an edge application server in the geographical area; and, based on the configuration data, route the data traffic to the co-located PLMN. This technical solution enables access to an edge application server of a co-located PLMN via the home PLMN.

[0006] According to one implementation of the first aspect, the network node can also be used to receive application function requests from application functions, wherein the application function requests include the configuration data. The technical solution implements external configuration of data traffic routing to the edge application server of the co-located PLMN.

[0007] According to one implementation of the first aspect, the network node can also be used to identify the data traffic based on at least one of a data network name, a single network slice selection auxiliary information value, and an application function service identifier. This technical solution can configure routing for specific data traffic to the edge application server of a co-located PLMN.

[0008] According to one implementation of the first aspect, for the co-located public terrestrial mobile network (PTN), the configuration data may further include at least one of the following: at least one supported data network name; at least one supported data network access identifier; at least one traffic routing requirement for the at least one supported data network access identifier; the fully qualified domain name of the edge application server; the Internet Protocol address of the edge application server; and the requirement to route the data traffic to the edge application server via the shortest path through the user plane function of the home public terrestrial mobile network. The technical solution may select a suitable co-located PLMN.

[0009] According to one implementation of the first aspect, the network node may include the network capability opening function of the home public land mobile network.

[0010] According to one implementation of the first aspect, the network node may include the policy control function of the home public land mobile network.

[0011] According to one implementation of the first aspect, the network node can further be used to: determine the policy and charging control rules of the session management function of the home public land mobile network (PLMN) based on the configuration data, for selecting the user plane function of the co-located public land mobile network (PLMN), and routing the data traffic to the edge application server; and provide the policy and charging control rules to the session management function of the home public land mobile network (PLMN). The technical solution can configure the home PLMN and the co-located PLMN through the session management function of the home PLMN, thereby routing the data traffic to the edge application server of the co-located PLMN.

[0012] According to one implementation of the first aspect, the policy and charging control rules may include a mapping relationship between the at least one supported data network access identifier and the identifier of the co-located public terrestrial mobile network for a given service data flow (SDF) that can be identified by a service data flow template, etc. The technical solution enables the session management function of the home PLMN to determine the appropriate user plane function of the co-located PLMN by means of the session management function belonging to the co-located PLMN, the user plane function being used to route the data traffic to the edge application server of the co-located PLMN.

[0013] According to one implementation of the first aspect, the network node can further be used to: determine access and mobility-related policy information of the access and mobility management function of the home public terrestrial mobile network (PLMN) based on the configuration data, for selecting the session management function of the co-located PLMN, wherein the session management function is used to manage at least one packet data unit (Packet Data Unit) session associated with the data traffic; and provide the access and mobility-related policy information to the access and mobility management function of the home public terrestrial mobile network. The technical solution can configure the home PLMN to select a suitable session management function for the co-located PLMN, so as to route the data traffic to the edge application server of the co-located PLMN.

[0014] According to one implementation of the first aspect, the access and mobility-related policy information may include an indication of at least one permitted co-located public land mobile network associated with at least one tracking area identifier of a given user equipment. This technical solution enables the access and mobility management functions of the home PLMN to select a co-located PLMN that can be used to route the data traffic to an edge application server within the tracking area.

[0015] According to one implementation of the first aspect, the access and mobility-related policy information may further include an indication of at least one supported single network slice selection auxiliary information value for each co-located public terrestrial mobile network associated with the at least one tracking area identifier, to route a given traffic type of the user equipment. This technical solution can further improve the selection of the co-located PLMN within the tracking area.

[0016] According to one implementation of the first aspect, the access and mobility-related policy information may further include a mapping relationship between the identifier of the co-located public land mobile network and one of at least one supported data network name and at least one supported data network access identifier. The technical solution may optionally support routing a given type of data traffic from a user equipment to the co-located PLMN of the edge application server.

[0017] According to one implementation of the first aspect, for the co-located public terrestrial mobile network (PTN), the configuration data further includes at least one data network name, and the network node can also be used to: determine user equipment (UE) routing policy information, wherein the UE routing policy information includes a request for external routing of the data traffic through the PTN, the UE routing policy information further includes at least one routing descriptor, the routing descriptor including: at least one single network slice selection auxiliary information value or the at least one data network name of the home PTN; a mapping relationship between the at least one tracking area identifier or at least one registration area identifier and the at least one single network slice selection auxiliary information value or the at least one data network name of the PTN; and transmit the UE routing policy information to the at least one UE. The technical solution can configure UEs to establish communication sessions with the edge application server of the co-located PTN through the home PTN of a specific geographical area.

[0018] Secondly, a network node for data traffic routing is provided. The network node can be used to: receive from at least one user equipment a registration request including at least one of the following: a mapping relationship between at least one single network slice selection information value of a request for network slice selection assistance information of a home public land mobile network and at least one single network slice selection information value of a co-located public land mobile network; a request for local area network (LAN) data network information of the co-located public land mobile network; retrieve from the unified data management function or unified data repository function of the home public land mobile network at least one of the following: a mapping relationship of allowed or configured network slice selection information between the home public land mobile network and the co-located public land mobile network, the LAN data network information of the co-located public land mobile network, and a list of multiple co-located public land mobile networks for each geographic region; and transmit a registration acceptance message to the at least one user equipment, wherein the registration acceptance message includes at least one of the following: a mapping relationship of allowed or configured network slice selection information between the home public land mobile network and the co-located public land mobile network, the LAN data network information of the co-located public land mobile network, and a list of multiple co-located public land mobile networks for each geographic region. The technical solution can register user equipment and configure the user equipment to establish a communication session with an edge application server via one of a plurality of available co-located PLMNs through the radio access network of the home PLMN of the geographical area.

[0019] According to one implementation of the second aspect, the network node may include access and mobility management functions of the home public land mobile network.

[0020] According to one implementation of the second aspect, the network node can further be used to: provide a network function discovery request to the network repository function of the home PLMN, wherein the network function discovery request includes an identifier of the co-located PLMN and at least one single network slice selection auxiliary information value of the co-located PLMN associated with the data traffic; and receive a network function discovery request response, wherein the network function discovery request response includes an identifier of the session management function of the co-located PLMN. This technical solution enables the home PLMN to select a suitable session management function of the co-located PLMN for controlling the routing of the data traffic to the edge application server of the co-located PLMN.

[0021] Thirdly, a network node for data traffic routing is provided. The network node can be used to: receive a Packet Data Unit (PDU) session establishment request from at least one user equipment (User Equipment), wherein the PDU session establishment request includes a single network slice selection auxiliary information value and a data network name for the home PLMN, a single network slice selection auxiliary information value and a data network name for the co-located PLMN, and a request for external routing through the co-located PLMN; and establish the PDU session according to the PDU session establishment request. This technical solution enables a User Equipment to request the establishment of a communication session for routing the data traffic through the home PLMN to the edge application server of the co-located PLMN.

[0022] According to one implementation of the third aspect, the network node may include session management functionality of the home public land mobile network.

[0023] According to one implementation of the third aspect, the network node is further configured to select the user plane function of the home PLMN based on configuration data, wherein the user plane function is used to route the data traffic to the co-located PLMN. This technical solution implements the configuration of the home PLMN to route the data traffic to the edge application server of the co-located PLMN.

[0024] According to one implementation of the third aspect, the network node can further be used to: transmit a Packet Data Unit (PDU) session creation request to the session management function of the co-located public terrestrial mobile network (PTN), wherein the PDU session creation request includes the single network slice selection auxiliary information value of the PTN and the data network name; receive a PDU session creation request response from the session management function of the PTN, wherein the PDU session creation request response includes at least one of the following: the Internet Protocol (IP) address of the edge application server, the fully qualified domain name (FQDN) of the edge application server, the IP address of the Domain Name System (DNS) server, and the FQDN of the DNS server; and transmit a PDU session establishment acceptance message to the at least one user equipment (UE), wherein the PDU session establishment acceptance message includes at least one of the following: the IP address of the edge application server, the FQDN of the edge application server, the IP address of the DNS server, and the FQDN of the DNS server. This technical solution enables the establishment of a communication session for routing data traffic from the UE of the home PLMN to the edge application server of the co-located PLMN.

[0025] Fourthly, a network node is provided for accessing an edge application server of a co-located public terrestrial mobile network (PTN). The network node is configured to: transmit a Packet Data Unit (PDU) session establishment request, wherein the PDU session establishment request includes a single network slice selection auxiliary information value (SMI) and a data network name of the home PTN, the SMI and a data network name of the co-located PTN, and a request for external routing through the co-located PTN; receive a PDU session establishment acceptance message, wherein the PDU session establishment acceptance message includes at least one of the following: the Internet Protocol (IP) address of the edge application server, the fully qualified domain name (FQD) of the edge application server, the IP address of the Domain Name System (DNS) server, and the FQD of the DNS server; and use the established PDU session to conduct data traffic communication with the edge application server maintaining a connection to the co-located PTN through a base station of the home PTN. This technical solution enables the device to request the establishment of a communication session for routing the data traffic of the user equipment to the edge application server of the co-located PTN through the home PTN.

[0026] According to one implementation of the fourth aspect, the network node can also be used to: transmit a registration request, wherein the registration request includes at least one of the following: a mapping relationship between at least one single network slice selection information value of the requested network slice selection auxiliary information of the home PLMN and at least one single network slice selection information value of the co-located PLMN, and a request for the local area network data network information of the co-located PLMN; and receive a registration acceptance message, wherein the registration acceptance message includes at least one of the following: a mapping relationship of allowed or configured network slice selection information between the home PLMN and the co-located PLMN, the local area network data network information of the co-located PLMN, and a list of multiple co-located PLMNs for each geographic region. The technical solution enables the device to register with the home PLMN and is used to request the establishment of the communication session, routing the data traffic of the user equipment through the home PLMN to the edge application server of the co-located PLMN.

[0027] According to one implementation of the fourth aspect, the network node includes a user equipment.

[0028] Fifthly, a network node for enabling data traffic routing is provided. The network node can be used to: receive data traffic routing information from an application function interacting with a co-located public terrestrial mobile network (PTMN), including at least one of the following: routing information for the interface between the user plane function of the home PTMN and the user plane function of the co-located PTMN, for routing data traffic in a geographic area; a list of supported data network access identifiers of the co-located PTMN in the geographic area; a list of supported single network slice selection auxiliary information values ​​and data network names in the geographic area for at least one application function service identifier; mapping information between the non-normalized single network slice selection auxiliary information values ​​of the home PTMN and the co-located PTMN; and provide the data traffic routing information to the application function interacting with the home PTMN. This technical solution realizes the sharing of data traffic routing information between the home PTMN and the co-located PTMN, for routing data traffic to the edge application server of the co-located PTMN through the home PTMN.

[0029] Sixthly, a method for data traffic routing is provided. The method may include: obtaining configuration data associated with data traffic of at least one user equipment in a geographic area on a home public terrestrial mobile network (PLMN), wherein the configuration data includes a mapping relationship between the data traffic and identifiers of at least one co-located public terrestrial mobile network providing access to an edge application server in the geographic area; and routing the data traffic to the co-located public terrestrial mobile network according to the configuration data. This technical solution enables access to an edge application server of a co-located PLMN via a home PLMN.

[0030] A seventh aspect provides a method for data traffic routing. The method may include: receiving from at least one user equipment a registration request including at least one of the following: a mapping relationship between at least one single network slice selection information value of a request for network slice selection assistance information of a home public land mobile network and at least one single network slice selection information value of a co-located public land mobile network; a request for local area network (LAN) data network information of the co-located LAN; retrieving from a unified data management function or unified data repository function of the home public land mobile network at least one of the following: a mapping relationship of allowed or configured network slice selection information between the home public land mobile network and the co-located LAN, the LAN data network information of the co-located LAN, and a list of multiple co-located LANs for each geographic region; and transmitting a registration acceptance message to the at least one user equipment, wherein the registration acceptance message includes at least one of the following: a mapping relationship of allowed or configured network slice selection information between the home public land mobile network and the co-located LAN, the LAN data network information of the co-located LAN, and the list of multiple co-located LANs for each geographic region. The technical solution can register user equipment and configure the user equipment to establish a communication session with an edge application server via one of a plurality of available co-located PLMNs through the radio access network of the home PLMN of the geographical area.

[0031] Eighthly, a method for data traffic routing is provided. The method may include: receiving a Packet Data Unit (PDU) session establishment request from at least one user equipment (User Equipment), wherein the PDU session establishment request includes a single network slice selection auxiliary information value and a data network name for a home PLMN, a single network slice selection auxiliary information value and a data network name for a co-located PLMN, and a request for external routing through the co-located PLMN; and establishing the PDU session according to the PDU session establishment request. This technical solution enables a User Equipment to request the establishment of a communication session for routing the data traffic through the home PLMN to the edge application server of the co-located PLMN.

[0032] A ninth aspect provides a method for accessing an edge application server in a co-located public terrestrial mobile network (PTN). The method may include: transmitting a Packet Data Unit (PDU) session establishment request, wherein the PDU session establishment request includes a single network slice selection auxiliary information (SMI) value and a data network name of the home PTN, the SMI value and a data network name of the co-located PTN, and a request for external routing through the co-located PTN; receiving a PDU session establishment acceptance message, wherein the PDU session establishment acceptance message includes at least one of the following: the Internet Protocol (IP) address of the edge application server, the fully qualified domain name (FQD) of the edge application server, the IP address of the Domain Name System (DNS) server, and the FQD of the DNS server; and using the established PDU session to transmit data traffic with the edge application server. This technical solution can request the establishment of a communication session for routing data traffic of a user equipment (UE) to the edge application server of the co-located PTN through the home PTN.

[0033] A tenth aspect provides a method for enabling data traffic routing. The method may include: receiving data traffic routing information from an application function interacting with a co-located public terrestrial mobile network (PTN), including at least one of the following: routing information for an interface between a user plane function of the home PTN and a user plane function of the co-located PTN, for routing data traffic in a geographic area; a list of supported data network access identifiers of the co-located PTN in the geographic area; a list of supported single network slice selection auxiliary information values ​​and data network names in the geographic area for at least one application function service identifier; mapping information between the home PTN and the non-normalized single network slice selection auxiliary information values ​​of the co-located PTN; and providing the data traffic routing information to the application function interacting with the home PTN. This technical solution enables the sharing of data traffic routing information between the home PTN and the co-located PTN, for routing data traffic to the edge application server of the co-located PTN through the home PTN.

[0034] Eleventhly, a computer program is provided. The computer program may include program code that, when executed on a computer, can perform any implementation of the methods of the sixth, seventh, eighth, ninth, or tenth aspects.

[0035] Therefore, implementations of this disclosure can provide devices, methods, and computer programs for allowing data traffic to be routed to an edge application server of another PLMN. Any implementation can be combined with one or more other implementations. These and other aspects of this disclosure will become apparent from the exemplary embodiments described below. Attached Figure Description

[0036] The accompanying drawings, which provide a further understanding of exemplary embodiments and form part of this specification, illustrate exemplary embodiments and, together with the description, help to explain the exemplary embodiments. In the drawings:

[0037] Figure 1 An example of a communication system with two mobile network operators provided in an embodiment of this disclosure is shown;

[0038] Figure 2 Examples of devices for implementing one or more embodiments of the present disclosure are shown;

[0039] Figure 3 An example of a user equipment registration process provided in an embodiment of this disclosure is shown;

[0040] Figure 4An example of a network function service discovery process across two public terrestrial mobile networks provided by an embodiment of this disclosure is shown;

[0041] Figure 5 Examples of network functions of home public land mobile networks and co-located public land mobile networks provided in embodiments of this disclosure are shown;

[0042] Figure 6 An example of the packet data unit session establishment process provided in this disclosure embodiment is shown;

[0043] Figure 7 Examples of two public terrestrial mobile networks and a federated application function manager provided in embodiments of this disclosure are shown;

[0044] Figure 8 An example of a method for data traffic routing provided in embodiments of this disclosure is shown;

[0045] Figure 9 An example of a method for accessing a co-located public terrestrial mobile network provided in an embodiment of this disclosure is shown;

[0046] Figure 10 An example of a method for enabling routed data traffic provided in embodiments of this disclosure is shown;

[0047] Figure 11 Examples of methods for data traffic routing provided in embodiments of this disclosure are shown; and

[0048] Figure 12 An example of a method for data traffic routing provided in an embodiment of this disclosure is shown.

[0049] In the accompanying drawings, the same reference numerals are used to indicate the same parts. Detailed Implementation

[0050] Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. The detailed description provided below, in conjunction with the accompanying drawings, is intended as a description of this example and not as representing the only form in which this example can be constructed or utilized. The description illustrates the functionality of the example and the sequence of steps for constructing and operating the example. However, the same or equivalent functionality and sequence can be achieved through different examples.

[0051] Multi-access edge computing (MEC) can be viewed as an enabler of fifth-generation (5G) or other future networks, allowing computing tasks to be processed and executed in appropriate edge application servers (EAS) located near user equipment (UE). One principle of this approach is that, given the time-critical nature of most safety-critical applications, such as in vehicle-to-everything (V2X) scenarios, locally generated data may be relevant to specific geographic areas. For example, vehicle or pedestrian movement can be processed locally, and the results can be promptly delivered to the appropriate road users to ensure the validity of any locally collected / processed data, for example, to prevent accidents.

[0052] For example, in the case of emergency trajectory alignment between UEs supporting V2X applications, cooperative operation may require the communication system to support message exchange between the master and remote vehicles with a maximum end-to-end latency of 3ms, while simultaneously supporting a data rate of 30Mbps when vehicles are traveling at absolute speeds up to 130km / h. This allows the application server to process data from one or more remote vehicles quickly enough before delivering the processed data to the appropriate master vehicle. The application server can determine which data from which remote vehicle is relevant to which master vehicle. These requirements demonstrate the advantages of MEC in ensuring high reliability and high availability of MEC-V2X application services. Therefore, in situations where cooperation avoids conflicts, it can be advantageous to locate the application server locally (i.e., rather than remotely) to meet the requirements of high speed and low latency.

[0053] One of the more pressing factors delaying the deployment of mature V2X or Intelligent Transport Systems (ITS) is that not every mobile network operator (MNO) possesses the necessary MEC infrastructure and other resources, such as roadside units (RSUs), in every region of a particular country. For example, secondary operators may not have deployed the necessary resources in all locations due to financial, regulatory, or operational constraints. Another more pressing factor is that, in road traffic situations, vehicles may belong to different original equipment manufacturers (OEMs), which may primarily have agreements with a single MNO. For example, vehicle OEM C1 may use a subscriber identity module (SIM) belonging to a first MNO (MNO 1) in its vehicles. Another vehicle OEM C2 may use a SIM belonging to a second MNO (MNO 2). Similarly, vulnerable road users (VRUs) and RSUs in ITS may connect to different MNOs. Therefore, the lifeline of a V2X scenario can depend on the degree of cooperation between different MNOs, for example, in terms of MEC resource sharing. MEC resource sharing can be useful in various use cases, such as when a home public land mobile network (HPLMN) needs the assistance of a co-located PLMN, referred to here as a CPLMN, to provide service to its own UEs using its own base stations, such as gNBs in a 5G network. It's important to note that such use cases may not involve any roaming. A "co-located" PLMN can include a PLMN different from the HPLMN, but not a visitor PLMN (VPLMN) used for roaming. A CPLMN can co-locate with an HPLMN. For example, the service areas of a CPLMN and an HPLMN can at least partially overlap, allowing the edge application server of the CPLMN to access via the base station of the HPLMN.

[0054] In a 5G system (5GS), during roaming, a VPLMN can use the UE's subscription permanent identifier (SUPI) to determine the identifier of the HPLMN associated with the UE. However, given that in the considered use cases, the HPLMN may seek assistance from another PLMN, a method is provided to inform the HPLMN that, for a given MEC application in a given geographic location, the HPLMN should seek assistance from a CPLMN to serve its own UE, for example, by routing UE traffic to the appropriate edge application server (EAS). Embodiments of this disclosure describe how the identifier of at least one appropriate CPLMN is notified to the HPLMN to quickly enlist network functions (NFs) belonging to the CPLMN to support a given MEC application in a given geographic location. Since the use of a CPLMN may not involve roaming, the possible application locations can be notified to the HPLMN on a per-CPLMN granularity basis. For this purpose, an application function (AF) request for the 5GC (5G core network) associated with the HPLMN may include an indication of which co-located PLMN-ID (PLMN identifier) ​​will be used for a given UE data traffic. For example, the data traffic may be identified by a single network slice selection assistance information value (S-NSSAI) in a given geographic area, an AF service identifier, or an application ID. The corresponding information may consider at least the following:

[0055] i) External parameter allocation that occurs between the AF and the network exposure function (NEF) / policy control function (PCF) / unified data manager (UDM) (e.g., using Nnef_ParameterProvision_Create / Nnef_ParameterProvision_Update operations), which can also be handled by the AF by directing a single UE address to the NEF's Nnef_TrafficInfluenceCreate / Update / Delete request, as is the case throughout the specification;

[0056] ii) Registration requests between the UE and the AMF;

[0057] iii) Packet data unit (PDU) session establishment between the UE and the SMF;

[0058] iv) UE route selection policy (URSP) configuration between the UE and the PCF;

[0059] v) Dynamic policy and charging control (PCC) creation and exchange between PCF and SMF;

[0060] vi) Creation and exchange of access mobility management-related policies between PCF and AMF;

[0061] vii) The interaction between MNOs and AMFs and NRFs to find a suitable C-SMF; and

[0062] viii) Information exchange between two AF instances, with or without the help of the union manager.

[0063] The embodiments of this disclosure can at least solve the following problems:

[0064] - Inform the HPLMN of the possible locations of applications at each (C)PLMN granularity, enabling the HPLMN to assign resources associated with the selected CPLMN so that appropriate data traffic is routed when its own UE invokes a given (MEC) application.

[0065] - The possible application location is indicated by the application function belonging to a specific road traffic authority (RTA).

[0066] - HPLMN's AMF or SMF determines how data traffic is routed locally by selecting the appropriate UPF.

[0067] - Notify the HPLMN's AMF that it needs to use the HPLMN's gNB to assign the CPLMN's SMF to serve the HPLMN's UE.

[0068] - Select the SMF for CPLMN and determine the PLMN-ID to be included in its network repository function (NRF) or network slice selection function (NSSF) query.

[0069] - Data traffic routed by HPLMN's SMF.

[0070] -Which S-NSSAI configurations are allowed in both HPLMN and CPLMN, and the configuration of S-NSSAI mapping between HPLMN and CPLMN?

[0071] - In the case of non-standardized S-NSSAI, S-NSSAI mapping is provided as part of the UE configuration update.

[0072] - Determine the UE route selection policy (URSP) configuration used to route data traffic to the CPLMN.

[0073] -UE indicates the use of S-NSSAI in both HPLMN and CPLMN, and the need to create a localized path when establishing a PDU session, and

[0074] - Information elements to be included during PDU session establishment.

[0075] For the signaling-based embodiments disclosed herein, one or more of the following system features may be applied:

[0076] - The Road Traffic Authority (RTA) can be a government entity that brings together different automotive OEMs and MNOs / PLMNs, while encouraging / enhancing resource sharing to ensure the full deployment of ITS. The terms MNO and PLMN are used interchangeably.

[0077] - Due to financial, regulatory, and economic reasons, not every MNO may need MEC infrastructure in every region of a country, preventing full-scale V2X operations.

[0078] -RTAs, RSU operators, automotive OEMs, and MNOs can develop relevant SLAs.

[0079] -RTA can operate on one or more AF instances to enable traffic redirection affected by AF, thereby ensuring resource sharing between MNOs.

[0080] - Different AF instances belonging to RTA can interact with HPLMNs that do not have the corresponding MEC infrastructure and CPLMNs that have the required MEC infrastructure.

[0081] -AF instances may be located in a central location – therefore, HPLMNs without MEC infrastructure may obtain the required AF inputs in terms of possible application locations at each CPLMN granularity.

[0082] - AFs belonging to RTA can collect information about possible application locations for each CPLMN granularity through any appropriate means.

[0083] - AFs belonging to RTA can interact with MNO-1 (CPLMN) and MNO 2 (HPLMN) to generate policy rules, such as policy rules that can be used to execute forwarding action rules (FAR).

[0084] - While using a localized UPF, an appropriate PDU session can be established to the correct localized data network.

[0085] Given the stringent latency requirements of V2X applications, such as lane merging, and the potential need to process locally generated multimedia traffic due to their local dependencies, using an EAS may be preferable to using any centralized application server (AS). Therefore, it enables the use of localized MEC infrastructure.

[0086] - When high-speed vehicles generate multimedia traffic related to applications such as lane merging, in order to ensure minimal latency, it may be desirable to leverage localized MEC infrastructure for rapid processing, even if different MNO support is required.

[0087] Taking into account the above characteristics, one or more of the following aspects can be considered to solve the above problems:

[0088] - Configure the AF request to indicate which CPLMN-ID to use for each TA of each HPLMN for a given application ID within a given time period.

[0089] - Configure PCC rules to ensure appropriate access, routing, and accounting behavior—for example, instructing PSAUPF to reside in the CPLMN.

[0090] - Configure the UE's URSP to indicate two sets of S-NSSAI / DNN (Data Network Name) pairs, one for HPLMN and the other for CPLMN.

[0091] - Configure UE registration requests, including the S-NSSAI allowed for each CPLMN, requests for local area data network (LADN) information for each CPLMN, and / or coverage requirements for the HPLMN's tracking area relative to the registration area (RA).

[0092] - Configure the PDU session establishment process to use only the AMF belonging to the HPLMN, allowing interaction between the SMFs of the HPLMN and CPLMN, as well as between the UPFs of the HPLMN and CPLMN. These features will be described further below.

[0093] According to one embodiment of this disclosure, configuration data associated with data traffic of at least one UE in a geographic area can be obtained on the HPLMN. The AF can pass the configuration data to the 5GC using operations such as Nnef_ParameterProvision_Create, Nef_ParameterProvision_Update, or Nnef_TrafficInfluenceCreate / Update / Delete requests from a single UE address to the NEF. The configuration data may include a mapping between a given data traffic and the identifiers of at least one co-located PLMN (e.g., CPLMN) used to provide access to EAS in the geographic area. The HPLMN can route data traffic to the co-located PLMN based on the configuration data. This enables the HPLMN to route EAS access to the co-located PLMN.

[0094] Figure 1 An example of a communication system with two mobile network operators provided in this disclosure is illustrated. One or more devices (e.g., UEs 110, 112, 114) can communicate with a radio access network (RAN) comprising one or more base stations, represented in this example by two fifth-generation base stations (gNBs). The first gNB (gNB 1) may belong to a first MNO (CPLMN 140). The second gNB (gNB 2) may belong to a second MNO (HPLMN 130). Base stations may also be referred to as radio access network nodes. UEs 110, 112, 114 can communicate with their respective gNBs via an air interface, for example, as specified in the 5G New Radio (NR) standard.

[0095] A gNB can connect to one or more user plane functions (UPFs) via the N3 interface. gNB 1 can connect to the local UPF (C-UPF) of a CPLMN 140. gNB 2 can connect to the local UPF (H-UPF) of an HPLMN 130. The UPF can be used to process the user data portion of a communication session. For example, the UPF can be used to encapsulate and decapsulate protocol data units (PDUs) of the user plane (UP), such as the GPRS tunneling protocol for the user plane (GTP-U). The UPF can function as a PSA (PDU session anchor) UPF, terminating the N6 interface of a PDU session in the 5G network. Local UPF 1 can communicate with local UPF 2 via a UPF interface (e.g., the N9 interface).

[0096] Access and mobility management function (AMF) Figure 1 (Not depicted in the text) can receive connection and session request related data from the UE or gNB via the N1 and N2 interfaces respectively (see [link]). Figure 5 The AMF can be used to control access and mobility management within the network. However, the AMF can delegate any session management-related responsibilities to the session management function (SMF). For example, whenever the AMF of HPLMN 130 sees a PDU session establishment request containing additional S-NSSAI and DNN mappings for both HPLMN and CPLMN, or an explicit indication involving the CPLMN, it can use the SMF (C-SMF) for managing communication sessions in CPLMN 140. The AMF of HPLMN 130 can use the SMF (H-SMF) for managing communication sessions in HPLMN 130. However, the AMF of HPLMN 130 is used to assign the C-SMF of CPLMN 140 to serve its own UE 110 for use with its own gNB, such as gNB 2. Information about available SMFs can be obtained by querying the network repository function (NRF), which maintains information about services provided by various network functions (NFs).

[0097] A session management function (SMF), such as a C-SMF or H-SMF, can be used to manage one or more communication sessions (e.g., PDU sessions) within one or more UPFs (e.g., C-UPF and / or H-UPF). The SMF can communicate with the AMF, for example, to receive requests to establish, update, or delete communication sessions. The SMF can be used to select a UPF for a PDU session. Information about available UPFs can be stored locally on the SMF, or the SMF can retrieve this information from one or more other network functions (e.g., NRFs).

[0098] HPLMN 130 and CPLMN 140 may also include network capability opening functions (H-NEF or C-NEF), policy control functions (H-PCF or C-PCF), and connect to corresponding application functions (AF 2 or AF 1), which may reside outside the respective PLMN. CPLMN 140 may be coupled to AF 1, which provides an external application interface for interacting with the network functions of CPLMN 140. Similarly, HPLMN 130 may be coupled to AF 2. Application functions may be controlled by a joint AF manager 150, as described further below. PLMNs 130 and 140 may also access corresponding data networks (DNs).

[0099] Network functions can communicate via a service-based interface (SBI) bus, which can be accessed by different network functions. Interfaces between individual network functions can be implemented via the SBI message bus. HPLMN 130 and / or CPLMN 140 may also include other network functions, such as unified data management (UDM) and / or unified data repository (UDR). UDM can be used to manage user data within the network. UDM can be associated with a UDR, which can store user data such as customer profiles, subscription information, or other user-related information.

[0100] In real-world deployments, due to financial, regulatory, and / or economic reasons, not all MNOs (MNO 2 in this example) may have sufficient MEC infrastructure deployed in all locations. Therefore, some MNOs (MNO 1 in this example) could benefit from using another operator's MEC infrastructure. Regardless of this, a challenge might be how to achieve meaningful ITS interactions between different players, such as maintaining connectivity with multi-vehicle OEMs, VRUs, or RSUs across different MNOs.

[0101] For example, embodiments of this disclosure relate to how to enable a UE 110 (vehicle) belonging to MNO 2 (HPLMN 130) which lacks (or has insufficient) MEC infrastructure to utilize the MEC infrastructure of MNO 1 (CPLMN 140), for example, to enable a UE 112 belonging to MNO 1 to benefit from lane-merging video streams transmitted by UE 110 as part of a V2X lane-merging application. In other words, the problem is how to enable HPLMN 130 (MNO 2) to utilize the PSAUPF (e.g., C-UPF) belonging to CPLMN 140 (MNO 1) to provide services for its own UE 110 while using its own base station (e.g., gNB 2).

[0102] As described above, a co-located PLMN utilizing an edge application server can be referred to as a CPLMN to distinguish it from a VPLMN. This is because embodiments of this disclosure may not involve roaming, and terms like VPLMN can be used in the context of roaming. In a roaming scenario, VPLMN and HPLMN can interact to serve the UE. In this case, a UE belonging to the HPLMN can roam to an area served by the VPLMN. In a roaming scenario, a base station belonging to the VPLMN can actually serve the roaming UE. On the other hand, according to embodiments of this disclosure, HPLMN 130 can request assistance from CPLMN 140, which can be used to provide the necessary MEC applications on its deployed MEC infrastructure to serve UE 110 of HPLMN 130. Therefore, UE 110 belonging to HPLMN 130 may not need to connect to a base station belonging to CPLMN 140.

[0103] Base station (gNB 2) can directly serve HPLMN 130 for UE 110. HPLMN 140 can seek assistance from CPLMN 140, which can provide a specific PSA UPF for the data traffic generated by UE 110. Therefore, the scenario under consideration may differ from home-roaming or local breakout (LBO) roaming scenarios. Since roaming via VPLMN is not involved, the base stations of the two PLMNs (gNB 1 and gNB 2) can operate in the same geographical area, i.e., co-located. Furthermore, UEs 110 and 112 can belong to the same automotive OEM or different automotive OEMs.

[0104] One option for configuring systems, etc., is to manually configure the PCF with static PCC rules so that the PCF knows how to execute static routes related to: policy and charging control rules (including PCC rules and PDU session-related attributes) to be provided to the SMF, access and mobility-related controls and / or UE access selection to be provided to the AMF. However, fully static configuration can require excessive manual intervention and is costly to manage the network while providing the required ITS or V2X services in every corner of the service area. Furthermore, fully static configuration may not provide sufficient flexibility to dynamically handle changing business, regulatory, or inter-MNO collaboration environments. For example, when an MNO deploys new MEC infrastructure in a given area, changes to already statically configured settings may be required. This can involve one or more MNOs; for example, challenging deployments may delay the full deployment of ITS. On the other hand, different NFs can interact across MNO boundaries to exchange information through signaling-based or control-plane-based technical solutions involving 5GC control plane NFs. Achieving this functionality may require establishing appropriate service level agreements (SLAs) between collaborating MNOs, automotive OEMs, RSU owners, etc.

[0105] Even though some embodiments are described in the context of a 5G core network, it should be understood that the embodiments of this disclosure are not limited to the specific examples, and therefore these embodiments can be applied to any current or future communication network. Furthermore, even though some embodiments are described using a single CPLMN 140 as an example, it should be understood that these embodiments can be extended to scenarios with multiple available CPLMNs. For example, any signaling information described herein can be provided to multiple CPLMNs, and an HPLMN can be used to select one of the CPLMNs.

[0106] Figure 2An example of an apparatus 200 for implementing one or more embodiments is shown. Apparatus 200 may include a network device or network node implementing one or more network functions, or a UE such as a mobile phone or vehicle, or any device generally used to implement any of the functions described herein. Apparatus 200 may include at least one processor 202. The at least one processor 202 may include one or more of various processing devices, such as a coprocessor, microprocessor, controller, digital signal processor (DSP), processing circuitry with or without a DSP, or various other processing devices including integrated circuits, such as application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), microcontroller units (MCUs), hardware accelerators, dedicated computer chips, etc.

[0107] Device 200 may also include at least one memory 204. For example, memory 204 may be used to store computer program code, such as operating system software and application software. Memory 204 may include one or more volatile memory devices, one or more non-volatile memory devices, and / or combinations thereof. For example, memory may be embodied as a magnetic storage device (such as a hard disk drive, floppy disk, magnetic tape, etc.), an optical-magnetic storage device, or a semiconductor memory (such as a mask ROM, a programmable ROM (PROM), an erasable PROM (EPROM), a flash ROM, random access memory (RAM), etc.).

[0108] Device 200 may also include a communication interface 208 for enabling device 200 to send and / or receive information. Communication interface 208 may include an internal communication interface, such as an interface between different network functions of device 200 (e.g., SBI). Alternatively, communication interface 208 may be a reference point, such as N3 or N6. Alternatively, communication interface 208 may be used to provide an external interface to another device, for example, via SBI. The communication interface may also be used to provide radio connectivity, such as 3GPP mobile broadband connectivity (e.g., 3G, 4G, 5G, or next-generation), wireless local area network (WLAN) connectivity, such as that standardized by the IEEE 802.11 series or the Wi-Fi Alliance, or short-range wireless network connectivity, such as Bluetooth connectivity. Therefore, communication interface 208 may include one or more antennas to enable the transmission and / or reception of radio frequency signals over the air.

[0109] When device 200 is used to implement a certain function, one and / or some components of the device, such as at least one processor 202 and / or memory 204, can be used to implement that function. Furthermore, when at least one processor 202 is used to implement a certain function, that function can be implemented using, for example, program code 206 included in at least one memory 204.

[0110] The functions described herein may be performed at least in part by one or more computer program product components, such as software components. According to one embodiment, device 200 includes a processor or processor circuitry, such as a microprocessor, which, when executing program code 206, performs embodiments of the operations and functions described herein. Alternatively or additionally, the functions described herein may be performed at least in part by one or more hardware logic components. Exemplary types of hardware logic components that may be used, such as but not limited to, include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SOCs), complex programmable logic devices (CPLDs), and graphics processing units (GPUs).

[0111] Device 200 may be used to perform the methods described herein or may include means for performing the methods described herein. In one example, the means includes at least one processor 202 and at least one memory 204 including program code 206 for causing device 200 to perform the methods when executed by at least one processor 202.

[0112] For example, device 200 may include computing devices such as servers, mobile phones, tablets, laptops, Internet of Things devices, vehicles (e.g., automobiles), base stations, etc. Although device 200 is shown as a single device, it should be understood that, where applicable, the functionality of device 200 may be distributed among multiple devices, for example, among components of a transmitter, receiver, or transceiver.

[0113] Back Figure 1 HPLMN 130 can obtain configuration data associated with data traffic of UE 110 in a given geographic area. The configuration data may include a mapping between data traffic types and identifiers of CPLMN 140 (or typically identifiers of multiple CPLMNs), which provides access to appropriate edge application servers (e.g., EAS 1) within the same geographic area. AF can identify or represent target traffic via AF-Service-Identifier, which NEF can map to a combination of DNN and optional S-NSSAI, as well as application identifiers or traffic filtering information, especially in the case of untrusted AFs. For example, configuration data can be received from an application function (AF 2) in an AF request. Application functions can provide representations of applications residing inside or outside the operator network interacting with the 5GC network. Application functions enable applications to interact with the 5GC and can also influence some operations of the 5G core, such as data traffic routing for edge computing applications. For example, an AF can interact with the 5GC using Nnef_ParameterProvision_Create or Nnef_ParameterProvision_Update operations or Nnef_TrafficInfluenceCreate / Update / Delete request operations for a single UE address. A trusted AF can interact directly with the PCF, while an untrusted AF must always interact through the NEF.

[0114] AF requests can be received at HPLMN 130, for example, at H-NEF. The information element (IE) of the AF request can include an indication of the possible location of the application server (AS) at each (C)PLMN granularity. The possible location of the application server can indicate which (E)AS is available at a given location, for example, for handling a specific UE application. For example, the UE application can be identified by the AF-Service-Identifier or one or more S-NSSAIs. The AF request can also indicate whether each (E)AS is directly connected via HPLMN or via CPLMN. For example, this allows HPLMN 130 to determine which PSAUPF to coordinate with in order to route a given data traffic of the UE if none of its own UPFs supports the required data network access identifier (DNAI) in a given geographic area and / or a given time instance. The AF request may also include an indication of a data network name (DNN) supported by CPLMN 140 and / or a fully qualified domain name (represented throughout the public domain by an example of a fully qualified domain name (FQDN)) or an Internet protocol (IP) address of an EAS accessible via CPLMN 140. The FQDN may typically include data identifying the location of a network node within the domain name system (DNS).

[0115] Table 1 provides examples of information included in an AF request. An AF request may include one or more disclosed information elements. The first column indicates the name of the information (information element). The second and third columns indicate the applicability of PCF and / or NEF information. The fourth column may indicate examples of the category (mandatory / conditional / optional) of the information element. However, the use of categories may be optional, or different classifications may be applied. This also applies to other embodiments of this disclosure.

[0116] Table 1

[0117]

[0118] For example, AF requests can be used for traffic redirection (after the PCF has created appropriate PCC rules), 5GC-based event subscriptions (e.g., user plane (UP) path management events), and / or 5GLAN (5G Local Area Network) purposes. However, as shown in the table above, AF requests can include information for ensuring the required traffic redirection behavior between HPLMN 130 and CPLMN 140.

[0119] AF-based traffic redirection can be applied to non-roaming and LBO scenarios, where the entities involved (e.g., AF, PCF, SMF, and / or UPF) can belong to the serving PLMN, or the AF can belong to a third party with an agreement with the serving PLMN. Embodiments of this disclosure can address the involvement of network functions belonging to two or more PLMNs. For example, HPLMN 130 can be informed of the application location for each CPLMN granularity and each geographic location, such as the tracking area (TA). This enables the AMF associated with HPLMN 130 to determine that it needs to involve an SMF belonging to the CPLMN in order to select the appropriate PSA or intermediate (I) UPF belonging to CPLMN 140 and allow user traffic to be routed to local access to a data network (identified by DNAI) accessible via a PSAUPF belonging to CPLMN 140.

[0120] As described in the table above, an AF request may include indications of possible application locations for one or more PLMNs (e.g., CPLMN 140). An AF request may also include the IP address of an FQDN or EAS accessible through a given CPLMN, at least one of the DNNs or DNAIs supported by each CPLMN, and N9 traffic routing requirements for each S-NSSAI or each CPLMN DNAI.

[0121] Therefore, an AF request sent by an application function to HPLMN 130 may include one or more of the following information cells. These information cells can be associated with a given type of data traffic or an AF-Service-Identifier, which can be associated with a given geographic area (e.g., TA):

[0122] - Application location. For example, each CPLMN has at least one supported DNAI and / or DNN. This can be in the form of an AF-Service-Identifier, which NEF can map to the appropriate DNAI when necessary.

[0123] - N9 traffic routing information (e.g., GTP-U N9 channel) between the UPF of HPLMN 130 and at least one CPLMN. This information can be provided for each DNAI. For one or more S-NSSAIs, this information may include the corresponding DNN used in a given CPLMN for a given geographic area.

[0124] - DNNs associated with LADNs and spatial validity using specific LADNs.

[0125] - Application or Service Identifier. The AF-Service-Identifier or DNN to be used in a given geographic area for each CPLMN-ID. The DNN can be associated with the CPLMN's local area network, and it can be provided with spatial validity. For example, the AF-Service-Identifier can be translated by NEF to an S-NSSAI supported by HPLMN, and the DNN, if possible, mapped to the S-NSSAI information associated with the CPLMN to be used in a given geographic area (e.g., TA).

[0126] - The EAS can be accessed via the FQDN or IP address given in the CPLMN.

[0127] - If possible, S-NSSAI mapping between HPLMN and CPLMN.

[0128] - Force localized routing of data traffic (e.g., via the shortest path) to the appropriate EAS, rather than the remote application server.

[0129] Based on the configuration data, HPLMN 130 can route data traffic to the appropriate CPLMN. For example, routing may include generating corresponding PCC rules from the PCF of the HPLMN (H-PCF) and providing the corresponding access and mobility-related policy control data to the AMF of the HPLMN 130 (H-AMF), as will be further explained below.

[0130] In roaming scenarios, the VPLMN can identify the UE's HPLMN using a Subscription Permanent Identifier (SUPI), which may include the HPLMN-ID. In embodiments of this disclosure, for example, the CPLMN-ID can be explicitly provided to the HPLMN via an AF or static configuration, allowing the H-PCF to include this information as part of a PCC rule passed to the SMF of the HPLMN (H-SMF) handling data traffic, such as a specific type of data traffic. The CPLMN-related information requested by the AF allows the H-SMF to identify the local UPF (H-UPF) of the HPLMN 130, which can be selected to connect to the HPLMN for a given service traffic or data traffic associated with a specific value of S-NSSAI. The AF can indicate spatial relevance, for example, by using a list of geographic area identifiers. The associated PCC rules can be created by the H-PCF. IP addresses can be used to assess the proximity of the H-UPF to the UPF of the HPLMN (C-UPF).

[0131] If the AF belonging to the RTA cannot contact HPLMN 130, the necessary PCC rules can be retrieved from the PCF (C-PCF) of CPLMN 140. Therefore, the C-PCF can contact the relevant H-PCF to obtain a given data traffic in a given geographic location. If this is not possible, the C-PCF can contact the 5GC of HPLMN 130 as the AF. AF requests targeting a UE's existing or future PDU sessions can be sent via NEF, and they can target one or more PCFs. The PCF can translate the AF request into a policy applied to the PDU session. Data traffic can be identified in the AF request, for example, by the DNN and optional network slice information (e.g., S-NSSAI) or AF-Service-Identifier. Operators can deploy Inter-PLMN UP Security (IPUPS) functionality at each local boundary of their network to protect their networks from invalid inter-PLMN N9 traffic.

[0132] The CPLMN-related information requested in the AF request, or the CPLMN-related information configured at HPLMN 130, can be reflected in the creation of the corresponding dynamic PCC rule. This can be used to enable the H-SMF to identify and utilize the C-UPF located in HPLMN 140 with the help of the C-SMF. Based on this information, the H-SMF can decide which H-UPF to select to route the identified data traffic to the appropriate I / PSA-UPF located in HPLMN 140. In an exemplary embodiment, the SMF can be used to select the UPF of HPLMN 130 for routing data traffic to HPLMN 140, at least according to the PCC rule, S-NSSAI, and DNN. This can be done based on configuration data received in the AF request or pre-configured at HPLMN 130.

[0133] H-PCF can also determine the PCC rules that H-SMF selects to route data traffic to the C-UPF of the edge application server based on configuration data. The C-UPF can be selected and managed by the appropriate C-SMF. The determined PCC rules can be provided to H-SMF. Examples of PCC rule information are included in Table 2. PCC rule information can include one or more information cells from Table 2. PCC rules can be provided as traffic redirection enforcement control information affected by AF. The first column indicates the name of the information (information cell), the second column provides a description, and the third column indicates whether PCF is allowed to modify the information.

[0134] Table 2

[0135]

[0136] As shown in Table 2, PCC rule information can include DNAI information for each CPLMN granularity. PCC rule information can indicate which DNAIs are available in which (C)PLMNs. Therefore, PCC rules can include a mapping between at least one supported DNAI and an identifier of the CPLMN 140. If the PCC rules also include the requirement to route data traffic identified using local edge resources, the H-SMF can determine which local H-UPF to select to route traffic to the data network (identified by the DNAI) accessible via the CPLMN 140. To enable this functionality, local UPFs can be connected across PLMN boundaries without the need for any centralized remote UPF.

[0137] The HPLMN 130 can also be configured with access and mobility-related policy information to quickly select the C-SMF for data traffic to be routed. This is achieved by indicating which CPLMNs are allowed for a given UE for each tracking area identifier (TAI). The H-PCF begins preparation, and this access and mobility information can be provided to the H-AMF. This allows the H-AMF to determine which CPLMNs are allowed for the UE to access to route a given type of data traffic. For example, the access and mobility-related policy information can indicate a list of CPLMNs allowed for each geographic location, such as those identified by a TAI, for routing a given traffic type for a given UE. Table 3 provides an example of access and mobility-related policy control information. Access and mobility-related policy control information can include one or more cells from Table 3. The first column indicates the name of the cell, and the second column provides a description of the cell. The third and fourth columns can indicate the category and scope of the cell, respectively.

[0138] Table 3

[0139]

[0140] The access and mobility-related policy information also includes additional information that helps the H-AMF select the appropriate C-SMF to handle specific traffic types identified at least by S-NSSAI, DNN, and DNAI. This additional information can be identified by the co-location SMF selection management in Table 3 and its three distinct pieces of information (e.g., the allowed co-location PLMNs for each TAI of a given UE, the list of supported S-NSSAI mappings for each TAI of each CPLMN, and the list of supported DNN / DNAIs for each CPLMN).

[0141] According to one embodiment, user equipment route selection policy (URSP) information may include CPLMN-related information. URSP helps the UE include appropriate S-NSSAI and / or DNN information when a PDU session is established. This information enables the gNB to select an appropriate AMF, which in turn can select an appropriate SMF to handle a given PDU session. This information can be further used for UPF / PCF selection. Therefore, URSP configuration can function in a 5G system (5GS) to route given UE data traffic while assigning appropriate NFs. Unless statically configured, URSP can enable the 5GS to select an appropriate NF to handle a given data traffic type generated by a particular UE. The PCF attached to HPLMN 130 can provide network slice selection policy (NSSP) information to the UE 110 as part of the URSP rules. This allows the UE to indicate the need for external CPLMN traffic redirection or routing.

[0142] Since HPLMN 130 can use CPLMN to route a given data traffic generated by the UE, the control functions associated with HPLMN 130 can determine which CPLMN to select for routing specific UE traffic in a given geographic area (e.g., TA). Accordingly, the URSP can be configured such that the URSP's traffic descriptor includes an indication that external CPLMN routing is required. For example, the traffic descriptor can be provided with an indication that a given type of data traffic will be routed through a CPLMN. For example, HPLMN 130 can determine to select CPLMN 140. Furthermore, the routing descriptor can indicate which S-NSSAI / DNN sets, corresponding to the HPLMN and CPLMN, will be included by the UE 110 at the time of PDU session establishment. Table 4 provides an example of the traffic descriptor portion of the URSP information. The URSP information (or rules) can include one or more cells as shown in Table 4. The first and second columns represent the cell's name and description. Columns three through five represent the cell's category, the PCF's authority to modify the cell, and the cell's scope, respectively.

[0143] Table 4

[0144]

[0145] URSP information can be determined by HPLMN 130, for example by H-PCF. As provided in Table 4, URSP information may include requests for external routing of data traffic through a CPLMN, which may be identified in the URSP by (C)PLMN-ID.

[0146] The URSP's list of route selection descriptors can include one or more route selection descriptors (RDS). The RDS portion of the URSP can include lists of S-NSSAI and / or DNN pairs to be used for HPLMN 130 and CPLMN 140, respectively. This allows the UE to include two sets of S-NSSAI / DNN pairs corresponding to HPLMN 130 and CPLMN 140, respectively, during PDU session establishment. Table 5 provides an example of RSD cells. An RSD can include one or more cells as shown in Table 5. These columns provide information similar to that in Table 4. Although in this example, the RDS is part of the URSP, it should be understood that similar information can be provided in any suitable signaling information.

[0147] Table 5

[0148]

[0149] The list of RDSs can be generated by the H-PCF and provided to UE 110, for example, within the URSP. The RDSs may include the S-NSSAI and / or DNN of HPLMN 130. The RDSs may also include mappings between geographic regions (e.g., TAI or RAI) and supported S-NSSAIs or DNNs of CPLMNs (e.g., CPLMN 140). Therefore, a mapping between S-NSSAI information between HPLMN 130 and CPLMN 140 can be provided. HPLMN 130 can enable the URSP to be transmitted to UE 110, for example, by providing the URSP to gNB 2.

[0150] Figure 3 An example of a user equipment registration process provided in an embodiment of this disclosure is illustrated. The UE registration process may involve UE 110 and core network elements H-AMF 131, H-PCF 132, and H-UDM / UDR 133. UE 110 can access the core network of HPLMN 130 through radio access network 120 (e.g., gNB). Similar processes can be performed for multiple UEs.

[0151] In roaming scenarios, UE 110 may include mappings of S-NSSAIs it uses in the HPLMN for finding the appropriate S-NSSAI to be used in the VPLMN. The AMF can update UE 110 with the configured NSSAIs and / or allowed NSSAIs and / or associated mappings to HPLMN S-NSSAIs for the serving PLMN. However, since CPLMN 140 can be used without roaming, UE 110 can provide a list of S-NSSAI mappings that will be used in CPLMN 140, along with the corresponding DNNs. This may include mappings of requested NSSAIs (if available), which may include the mapping of each requested NSSAI's S-NSSAI to the CPLMN S-NSSAI. For each access type level context in the UE access and UE context mobility context within the AMF, the following may also be included: mappings of NSSAIs allowed for each CPLMN-ID.

[0152] The requested NSSAI can include the S-NSSAI requested by UE 110 for data traffic. The configured NSSAI can be configured for the UE by the relevant PLMN, and it can be applied to the relevant PLMN, such as HPLMN 130 or CPLMN 140. The configured NSSAI can include standard S-NSSAI values ​​or values ​​specific to the relevant PLMN. Allowed NSSAI can include values ​​assigned by the relevant PLMN, which can be allowed within a registration area or a geographic area such as the entire HPLMN. The requested NSSAI can be either a configured NSSAI or an allowed NSSAI.

[0153] In operation 301, UE 110 may transmit a registration request. This registration request may include the mapping relationship of the NSSAI requested by each CPLMN. This may include the mapping relationship between the S-NSSAI of the requested NSSAI of HPLMN 130 and the S-NSSAI of CPLMN 140. UE 110 may also transmit an indicator for each CPLMN requesting LADN information. UE 110 may transmit the registration request to H-AMF 131. This transmission can be performed via radio access network 120. H-AMF 131 may receive the registration request.

[0154] In operations 302 and 303, H-AMF 131 can retrieve the allowed or configured NSSAI mapping between HPLMN 130 and CPLMN from H-UDM / UDR 133. H-AMF 131 can also retrieve LADN information for CPLMN and / or a list of CPLMNs for each geographic region. For example, retrieving this information may include providing a Nudm_SDM_Get request to H-UDM / UDR 133. The Nudm_SDM_Get request may include the requested NSSAI mapping for each CPLMN and / or an indicator of the requested LADN information for each CPLMN. Therefore, the request to H-UDM / UDR 133 may include information received from UE 110 in the registration request. H-UDM / UDR 133 may receive the request from H-AMF 131 and, in response, provide H-AMF 131 with the allowed or configured NSSAI mapping and / or LADN information for each CPLMN. For example, this information can be provided to H-AMF 131 in an Access and Mobility (AM) policy association establishment or modification message. Retrieving data from H-UDM / UDR 133 can be done in response to determining that H-AMF 131 does not have subscription data for UE 110. Typically, the retrieved data may include Access and Mobility subscription data, SMF selected subscription data, UE context in SMF data, and / or LCS (Location Services) mobility initiation. Data retrieval can be performed via H-PCF 132. For example, H-AMF 131 can provide H-PCF 132 with relevant information, such as allowed NSSAIs and, if available, the mapping of allowed NSSAIs.

[0155] In operation 304, H-AMF 131 may send a registration acceptance message to UE 110, for example, by providing the registration acceptance message to Radio Access Network 120 for transmission to UE 110. The registration acceptance message may include a mapping relationship of allowed or configured NSSAIs between HPLMN 130 and CPLMN 140. The registration acceptance message may also include LADN information for CPLMN 140 and / or a list of CPLMNs for each geographic area. UE 110 may receive the registration acceptance message. For example, when establishing a PDU session to establish a connection with the EAS of CPLMN 140 via HPLMN 130, UE 110 may use the information in the registration acceptance message. For example, this information may be included in the PDU session establishment request, as described further below.

[0156] Figure 4An example of a network function (NF) service discovery process across two public terrestrial mobile networks provided by an embodiment of this disclosure is illustrated. The NF / NF service discovery process (Nnrf_NFDiscovery) can be part of the PDU session establishment process. As described above, as part of the PDU session establishment process, UE 110 can send an indication of external CPLMN routing requests, the S-NSSAI / DNN to be used in HPLMN 130, and the S-NSSAI / DNN to be used in CPLMN 140 to the core network of HPLMN 130. This can be based on the URSP configuration as described above or a static configuration on UE 110 and / or H-PCF 132. Including the CPLMN-ID in the PDU session establishment process enables H-AMF 131 to query the correct NRF in order to identify and subsequently use the appropriate C-SMF belonging to CPLMN 140. In other words, including the CPLMN-ID can affect how the NF / NF service discovery process occurs.

[0157] In operation 401, NF service consumer 137, such as H-AMF 131, may transmit an NF discovery request to the NRF (H-NRF 136) of HPLMN 130. This request may include the CPLMN-ID and S-NSSAI to be used in CPLMN 140. H-NRF 136 may receive the NF service discovery request and identify the NRF of the CPLMN (C-NRF 146) based on the CPLMN-ID.

[0158] In operation 402, H-NRF 136 may transmit an NF discovery request to C-NRF 146 to request NF discovery services from CPLMN 140 and obtain the NF profiles of the NF instances deployed in CPLMN 140. H-NRF 136 may receive an NF service discovery response from C-NRF 146, which may include, for example, the identifier of the SMF of CPLMN 140 (C-SMF) used for routing data traffic of UE 110.

[0159] Figure 5 Examples of network functions for home public land mobile networks and co-located public land mobile networks provided in embodiments of this disclosure are shown. Figure 5Network functions that can be involved in routing data traffic for a given UE to CPLMN 140 are illustrated. UE 110 can be served by access node 122 (e.g., gNB) of HPLMN 130 (H-AN). UE 110 can communicate with H-AMF 131 via a communication interface (e.g., N1 interface), which can be physically routed through H-AN 122. H-AN 122 can communicate with H-AMF 131 via a communication interface (e.g., N2 interface). H-AN 122 can also communicate with H-UPF 135 via a communication interface (e.g., N3 interface). H-SMF 134 can communicate with H-UPF 135 via a communication interface (e.g., N4 interface).

[0160] H-AN 122 can be used to select the appropriate H-AMF 131 based on the requested NSSAI, 5G-GUTI (Globally Unique Temporary Identifier), 5G-S-TMSI (Temporary Mobile Subscriber Identity), and / or GUAMI (Globally Unique AFN Identifier). Once H-AMF 131 is selected, the appropriate H-SMF 134 and C-SMF 144 can be selected based on the aforementioned CPLMN-related information (e.g., the CPLMN-ID and S-NSSAI / DNN sets used in HPLMN 130 and CPLMN 140, respectively). For example, this information may be included in non-access stratum (NAS) service requests or PDU session establishment requests. The SMF selection function of HPLMN 130 can select H-SMF 134 based on the S-NSSAI of HPLMN 130 and C-SMF 144 based on the S-NSSAI of CPLMN 140. For example, when using delegated discovery, H-AMF 131 can select H-SMF 134 and / or C-SMF 144 directly or indirectly through a service communication proxy (SCP) or NRF, based on the SMF service area, additional UE indications and / or UE location.

[0161] H-AMF 131 can communicate with H-SFM 134 via a communication interface (e.g., N11 interface). H-SMF 134 can communicate with C-SMF 144 via a communication interface (e.g., N16a interface). When C-SMF 144 inserts a PDU session, for example during PDU session establishment, C-SMF 144 can provide H-SMF 134 with a list of its supported DNAIs or AF-Service-Identifiers. Based on the DNAI list information received from C-SMF 144, H-SMF 134 can provide C-SMF 144 with a list of DNAIs or AF-Service-Identifiers of interest for PDU sessions used for local traffic redirection. C-SMF 144 can be responsible for the insertion, modification, and / or deletion of C-UPF 145 to ensure local traffic redirection. H-SMF 134 may not need access to the local configuration or NRF output associated with C-UPF 145 controlled by C-SMF 144. H-SMF 134 can provide N4 information to C-SMF 144, indicating how data traffic should be configured in C-UPF 145, controlled by C-SMF 144, to be detected, enforced, and / or monitored. For example, H-SMF 134 can issue a request to C-SMF 144 including N4 information to be used for creating / updating / deleting packet detection rules (PDR), forwarding action rules (FAR), quality-of-service (QoS) enforcement rules (QER), and / or usage reporting rules (URR). H-SMF 134 can generate information for local traffic offloading based on available DNAIs indicated by C-SMF 144, the PCC rules associated with those DNAIs, and / or charging requirements. This (N4) information can be provided by H-SMF 134 to C-SMF 144 via the N16a interface. For example, C-SMF 144 can use this information to deduce appropriate rules for C-UPF 145, which is controlled by C-SMF 144, via the N4 interface. For example, C-UPF 145 can route data traffic to edge application server (EAS) 147 via the N6 interface. For example, data traffic can be received from H-UPF 135 via the N9 interface.

[0162] Figure 6An example of a Packet Data Unit (PDU) session establishment process provided in an embodiment of this disclosure is illustrated. The illustrated PDU session establishment process may involve NFs from both HPLMN 130 and CPLMN 140, while taking into account that UE 110 provides additional S-NSSAI and DNN mapping information and / or explicit indications for applying external routes using CPLMN 140. This information allows H-AMF 131 to select the appropriate H-SMF 134 and C-SMF 144 during PDU session establishment. Unlike home route roaming, H-PCF 132 can participate in the session management (SM) policy association establishment process to establish an SM policy association with the PCF and obtain the default PCC rules for the PDU session. C-PCF 148 can be used by C-SMF 144 to select the appropriate C-UPF 145 to route UE data traffic to the data network identified by DNAI. The disclosed PDU session establishment procedure can be used to pass the DNS or EAS FQDN or IP address as part of the PDU session establishment accept message to the UE 110. For example, the protocol configuration option (PCO) can be configured for this purpose. The UPF provides an indication of neighboring UPFs and their respective UPFInfo lists. Furthermore, the NEF can provide a list of DNAIs supported by the UPF through interfaces such as the N27 interface. Even so... Figure 6 An example of this has been shown in the context of PDU session establishment, and it can generally be used to establish any suitable communication session.

[0163] In operation 601, UE 110 may transmit a PDU session establishment request. The PDU session establishment request may include S-NSSAI and / or DNN, which will be used in HPLMN 130, primarily to find the appropriate NF in the HPLMN to handle a given UE service type. The PDU session establishment request may also include S-NSSAI and / or DNN, primarily to find the appropriate NF in CPLMN 140 to handle a given UE service type. The PDU session establishment request may also include an external routing request via CPLMN 140. For example, the PDU session establishment request may be transmitted to H-AMF 131 via the N2 interface through the base station of RAN 120. H-AMF 131 may receive the PDU session establishment request. The additional S-NSSAI and DNN mappings used in HPLMN 130 and CPLMN 140 respectively, and / or the explicit indication of applying external routes via CPLMN 140, can enable the H-AMF to select C-SMF 144 and H-SMF 134 to handle data traffic associated with a given PDU session. A PDU session can be established. The establishment of a PDU session may include one or more of operations 603 to 612.

[0164] In operation 602, H-AMF 131 can select H-SMF 134 and C-SMF 144 based on the PDU session establishment request. For example, in response to receiving an external routing request, H-SMF 134 and C-SMF 144 can be selected based on the S-NSSAI and / or DNN of HPLMN 130 and CPLMN 140 indicated in the PDU session establishment request. For example, H-AMF 131 can select H-SMF 134 associated with the indicated S-NSSAI and / or DNN of HPLMN 130. H-AMF 131 can also select C-SMF 144 associated with the indicated S-NSSAI and / or DNN of CPLMN 140. This can be achieved by mapping the S-NSSAI and / or DNN of HPLMN 130 and CPLMN 140 in the PDU session establishment request.

[0165] In operation 603, H-AMF 603 may provide a PDU session creation session management (SM) context request (e.g., Nsmf_PDUSession_CreateSMContext request) to the selected H-SMF 134. H-AMF 131 may establish a PDU session by sending a PDU session creation request to H-SMF 134.

[0166] In operation 604, H-SMF 134 can perform subscription retrieval / update to obtain the (latest) subscription information of UE 110 from H-UDM 133.

[0167] In operation 605, H-AMF 131 can receive a PDU session creation session management (SM) context response (e.g., Nsmf_PDUSession_CreateSMContext response) from H-SMF 134.

[0168] In operation 606, PDU session authentication or authorization can be performed. This operation can be performed by H-SMF 134 by consulting H-UDM 133 using, for example, information about UE 110 provided in the PDU session establishment request.

[0169] In operation 607, H-SMF 134 can select H-PCF 132. Then, the establishment or modification of session management policy associations can be performed between H-SMF 134, H-PCF 132 and / or H-UDM 133.

[0170] In operation 608, H-SMF 134 can be selected as H-UPF 135. An N4 session can be established or modified between H-SMF 134 and H-UPF 135. This may involve H-SMF 134, H-UPF 135, and / or H-PCF 132.

[0171] In operation 609, H-SMF 134 may transmit a PDU session creation request (e.g., Nsfm_PDUSession_Create_Request) to C-SMF 144. The PDU session creation request may include S-NSSAI and / or DNN of CPLMN 140, which may be received from H-AMF 131.

[0172] In operation 610, C-SMF 144 can select C-UPF 145. N4 sessions between C-SMF 144 and C-UPF 145 can be established or modified.

[0173] In operation 611, C-SMF 144 may transmit a PDU session creation request response (e.g., Nsfm_PDUSession_Create_Response) to H-SMF 134. The PDU session creation request response may include the IP address and / or the FQDN of the EAS. The PDU session creation request response may also include the IP address and / or the FQDN of the DNS server. Therefore, the local EAS / DNS address at CPLMN 140 can be provided to H-SMF 134.

[0174] In operation 612, H-SMF 134 and H-AMF 131 can perform N1N2 message transfer (e.g., Nsfm_Communication_N1N2MessageTransfer). For example, H-SMF 134 can provide H-AMF 131 with a local EAS / DNS address, such as the IP address or FQDN of the EAS and / or the IP address or FQDN of the DNS server.

[0175] In operation 613, for example, H-AMF 131 can transmit a PDU session establishment accept message to UE 110 via the base station of RAN 120. The PDU session establishment accept message may include the IP address or FQDN of the EAS. The PDU session establishment accept message may also include the IP address or FQDN of the DNS server. UE 110 can receive the PDU session establishment accept message. UE 110 can then use the established PDU session to transmit data traffic with the indicated EAS. UE 110 can use RAN 120 of HPLMN 130 to transmit data traffic with the EAS. Therefore, the connection with CPLMN 140 can be maintained via the base station of HPLMN 130.

[0176] Figure 7 Examples of two public terrestrial mobile networks and a federated application function manager provided in embodiments of this disclosure are shown. HPLMN 130 and CPLMN 140 may include reference... Figure 1The various network functions described. CPLMN 140 may include one or more edge application servers (EAS 1 to EAS n). The federated AF manager 150 can obtain CPLMN-specific data traffic routing information from AF 1 and pass it to AF 2, enabling AF2 to interact with HPLMN 130. The data traffic routing information may include N9 routing information, such as routing information for the interface between the HPLMN 130's UPF and the CPLMN. N9 routing information may be associated with geographic areas such as tracking areas. The data traffic routing information may also include a list of supported AF-Service-Identifiers or DNAIs for a given geographic area on the CPLMN 140. The data traffic routing information may also include a list of S-NSSAIs and / or DNNs supported by the CPLMN in the geographic area. The list of supported S-NSSAIs and / or DNNs may be associated with one or more application function service identifiers. The data traffic routing information may also include mapping information between the non-standardized S-NSSAIs of the HPLMN 130 and the CPLMN 140. The Joint AF Manager 150 can be used to provide data traffic routing information received from AF 1 to AF 2. This information can be provided to the HPLMN UE 110 in the form of URSP configuration to establish a PDU session for communication with one of the CPLMN's EAS via HPLMN 130, as described above. If a direct communication channel exists between the AFs, AF 1 can interact directly with AF 2. If not, the centralized Joint AF Manager can communicate with local AF instances (e.g., AF 1 and AF 2) to relay data traffic routing information.

[0177] In other words, each (C)PLMN exposes the following information, which AF1 collects and passes to AF2, so that the HPLMN can use this configuration details to make application traffic routing decisions:

[0178] i) A list of MEC applications or AF service identifiers supported by each (C)PLMN in each geographic location (e.g., per cell, per gNB, or per TA).

[0179] ii) The current running state of each MEC application, such as onboard, instantiated, etc.

[0180] iii) Using active user information (e.g., GPSI) for each PLMN in each geographic location (e.g., per cell, per gNB, or per TA), for a specific MEC application instance.

[0181] iv) For each (C)PLMN, in each geographic location (e.g., per cell, per gNB, or per TA), the current load level, remaining capacity, and QoS KPIs supported by each MEC application instance.

[0182] v) Address information (e.g., FQDN, IP address, port number) leading to a given MEC application instance.

[0183] Various exemplary embodiments disclose devices, methods, and computer programs for routing UE data traffic to an edge application server of another PLMN in non-roaming scenarios, wherein connectivity with the other PLMN is maintained via the RAN of the HPLMN. This enables collaboration between different MNOs, for example, where time-critical applications cannot be delivered in a geographic area due to a lack of MEC infrastructure and resources required by all MNOs.

[0184] Figure 8 An example of a method for data traffic routing provided in embodiments of this disclosure is shown. For example, the method may be implemented using H-PCF 132 or H-NEF.

[0185] In 801, the method may include: acquiring configuration data associated with data traffic of at least one user equipment in a geographic area on a home public land mobile network, wherein the configuration data includes a mapping between the data traffic and identifiers of at least one co-located public land mobile network providing access to an edge application server in the geographic area.

[0186] In 802, the method may include: routing the data traffic to the co-located public land mobile network based on the configuration data.

[0187] Figure 9 An example of a method for accessing a co-located public terrestrial mobile network provided in an embodiment of this disclosure is illustrated. For example, this method can be implemented by UE 110.

[0188] In 901, the method may include: transmitting a packet data unit session establishment request, wherein the packet data unit session establishment request includes a single network slice selection auxiliary information value and a data network name corresponding to the home public land mobile network, a single network slice selection auxiliary information value and a data network name corresponding to the co-located public land mobile network, and a request for external routing through the co-located public land mobile network.

[0189] In 902, the method may include: receiving a Packet Data Unit Session Establishment Acceptance Message, wherein the Packet Data Unit Session Establishment Acceptance Message includes at least one of the following: the Internet Protocol address of the edge application server, the fully qualified domain name of the edge application server, the Internet Protocol address of the Domain Name System server, and the fully qualified domain name of the domain system server.

[0190] In 903, the method may include: transmitting data traffic with the edge application server using an established packet data unit session.

[0191] Figure 10 An example of a method for data traffic routing provided in an embodiment of this disclosure is shown. For example, the method may be implemented by a federated AF manager 150.

[0192] In 1001, the method may include: receiving data traffic routing information from an application function for interacting with a co-located public terrestrial mobile network, including at least one of the following: routing information for an interface between a user plane function of the home public terrestrial mobile network and a user plane function of the co-located public terrestrial mobile network, for routing data traffic in a geographic area; a list of supported AF-Service-Identifiers or data network access identifiers of the co-located public terrestrial mobile network in the geographic area; for at least one application function service identifier, a list of supported single network slice selection auxiliary information values ​​and data network names in the geographic area; and mapping information between the home public terrestrial mobile network and the non-normalized single network slice selection auxiliary information values ​​of the co-located public terrestrial mobile network.

[0193] In 1002, the method may include: providing the data traffic routing information to application functions used for interacting with the home public land mobile network.

[0194] For example, other features of the method are directly derived from the functionality of one or more network functions of HPLMN 130 and / or CPLMN 140, UE 110, application functions (AF 1 or AF 2), and / or the joint AF manager 150, as described throughout the specification and appended claims, and therefore will not be repeated here. Different variations of the method may also be applied, as described in conjunction with various example embodiments.

[0195] Figure 11 An example of a method for data traffic routing provided in embodiments of this disclosure is shown. For example, the method can be implemented by H-AMF 131.

[0196] In 1101, the method may include: receiving a registration request from at least one user equipment, wherein the registration request includes at least one of the following: a mapping relationship between at least one single network slice selection information value of the requested network slice selection assistance information of the home public land mobile network and at least one single network slice selection information value of the co-located public land mobile network, and a request for local area network data network information of the co-located public land mobile network.

[0197] In 1102, the method may include retrieving at least one of the following from the unified data management function or unified data repository function of the home public land mobile network: a mapping relationship of allowed or configured network slice selection information between the home public land mobile network and the co-located public land mobile network, the local area network data network information of the co-located public land mobile network, and a list of multiple co-located public land mobile networks for each geographic region.

[0198] In 1103, the method may include: transmitting the registration acceptance message to the at least one user equipment, wherein the registration acceptance message includes at least one of the following: a mapping relationship of allowed or configured network slice selection information between the home public land mobile network and the co-located public land mobile network, the local area network data network information of the co-located public land mobile network, and a list of the plurality of co-located public land mobile networks for each geographic region.

[0199] Figure 12 An example of a method for data traffic routing provided in an embodiment of this disclosure is shown. For example, the method can be implemented by an H-SMF 134.

[0200] In 1201, the method may include: receiving a Packet Data Unit Session Establishment Request from at least one user equipment, wherein the Packet Data Unit Session Establishment Request includes a Single Network Slice Selection Auxiliary Information Value and a Data Network Name for a home Public Land Mobile Network, a Single Network Slice Selection Auxiliary Information Value and a Data Network Name for a co-located Public Land Mobile Network, and a request for external routing through the co-located Public Land Mobile Network.

[0201] In 1202, the method may include: establishing the packet data unit session according to the packet data unit session establishment request.

[0202] A device or node, such as a network device or network node for implementing one or more network functions, can be used to perform or carry out any aspect of the methods described herein. Furthermore, a computer program or computer program product may include instructions for causing the device to perform any aspect of the methods described herein when executed. Additionally, the device may include means for performing any aspect of the one or more methods described herein. According to an exemplary embodiment, the means includes at least one processor and memory including program code. The at least one processor and the program code are used to cause the device to perform any aspect of the one or more methods when executed by the at least one processor.

[0203] Any ranges or device values ​​given herein may be extended or modified without losing the desired effect. Furthermore, unless expressly prohibited, any embodiment may be combined with another embodiment.

[0204] Although the subject matter has been described in language specific to structural features and / or actions, it should be understood that the subject matter defined in the claims is not necessarily limited to the specific features or actions described above. In fact, the specific features and actions described above are disclosed as examples of implementing the claims, and other equivalent features and actions are intended to fall within the scope of the claims.

[0205] It should be understood that the above benefits and advantages may relate to one embodiment or several embodiments. The embodiments are not limited to those that solve any or all of the stated problems or those that have any or all of the stated benefits and advantages. It is further understood that a reference to "one" entry may refer to one or more of these entries.

[0206] The steps or operations described herein can be performed in any suitable order, or simultaneously where appropriate. Furthermore, individual boxes can be removed from any method without departing from the scope of the subject matter described herein. Without losing the desired effect, aspects of any of the foregoing exemplary embodiments can be combined with aspects of any other described exemplary embodiments to form other embodiments.

[0207] As used herein, the term "comprising" means including the identified method, block, or element, but such blocks or elements are not included in an exclusive list, and the method or apparatus may include other blocks or elements.

[0208] Although a subject may be referred to as the "first" or "second" subject, this does not necessarily indicate any order or importance of these subjects. Rather, these attributes can be used simply to distinguish between subjects.

[0209] It should be understood that the above description is given by way of example only, and various modifications can be made by those skilled in the art. The above description, examples, and data provide a complete description of the structure and use of exemplary embodiments. Although various embodiments have been described above with some degree of specificity or with reference to one or more individual embodiments, those skilled in the art can make various changes to the disclosed embodiments without departing from the scope of this specification.

Claims

1. A network node for data traffic routing, characterized in that, Used for: Acquire configuration data associated with data traffic of at least one user device in a geographic area on the home public terrestrial mobile network, wherein the configuration data includes a mapping between the data traffic and identifiers of at least one co-located public terrestrial mobile network used to provide access to an edge application server in the geographic area, wherein the co-located public terrestrial mobile network includes public terrestrial mobile networks different from the home public terrestrial mobile network, but not guest public terrestrial mobile networks used for roaming. Based on the configuration data, the data traffic is routed to the co-located public land mobile network.

2. The network node according to claim 1, characterized in that, It is also used to receive application function requests from application functions, wherein the application function requests include the configuration data.

3. The network node according to claim 1 or 2, characterized in that, It is also used to identify the data traffic based on at least one of the data network name, single network slice selection auxiliary information value, and application function service identifier.

4. The network node according to claim 1 or 2, characterized in that, For the co-located public land mobile network, the configuration data further includes at least one of the following: At least one supported data network name; At least one supported data network access identifier; At least one traffic routing requirement for at least one supported data network access identifier; The fully qualified domain name of the edge application server; The Internet Protocol address of the edge application server; and The requirement to route data traffic to the edge application server via the shortest path through the user plane function of the home public terrestrial mobile network.

5. The network node according to claim 1 or 2, characterized in that, The network node includes the network capability opening function of the home public land mobile network.

6. The network node according to claim 1 or 2, characterized in that, The network node includes the policy control functions of the home public land mobile network.

7. The network node according to claim 6, characterized in that, Also used for: Based on the configuration data, the policy and charging control rules of the session management function of the home public land mobile network are determined, which are used to select the user plane function of the co-located public land mobile network and route the data traffic to the edge application server. The policy and charging control rules are provided to the session management function of the home public land mobile network.

8. The network node according to claim 6, characterized in that, For the co-located public land mobile network, the configuration data also includes at least one supported data network access identifier, and the policy and charging control rules include a mapping relationship between the at least one supported data network access identifier and the identifier of the co-located public land mobile network for a given service data flow.

9. The network node according to claim 6, characterized in that, Also used for: Based on the configuration data, access and mobility-related policy information for the access and mobility management function of the home public land mobile network is determined, which is used to select the session management function of the co-located public land mobile network, wherein the session management function is used to manage at least one packet data unit session associated with the data traffic; and Provide the access and mobility related policy information to the access and mobility management function of the home public land mobile network.

10. The network node according to claim 9, characterized in that, The access and mobility-related policy information includes an indication of at least one permitted co-located public land mobile network associated with at least one tracking area identifier of a given user equipment.

11. The network node according to claim 10, characterized in that, The access and mobility-related policy information also includes indications of at least one supported single network slice selection auxiliary information value for each co-located public land mobile network associated with the at least one tracking area identifier, to route a given traffic type of the user equipment.

12. The network node according to any one of claims 9 to 11, characterized in that, The access and mobility-related policy information also includes a mapping relationship between the identifier of the co-located public land mobile network and one of at least one supported data network name and at least one supported data network access identifier.

13. The network node according to claim 10 or 11, characterized in that, For the co-located public land mobile network, the configuration data also includes at least one data network name, and the network node is further used for: The user equipment routing policy information is determined, wherein the user equipment routing policy information includes a request to externally route the data traffic through the co-located public land mobile network, and the user equipment routing policy information further includes at least one routing descriptor, the routing descriptor including: At least one single network slice selection auxiliary information value or the at least one data network name of the home public land mobile network; The mapping relationship between the at least one tracking area identifier or at least one registration area identifier and the at least one single network slice selection auxiliary information value or the at least one data network name of the co-located public land mobile network; and The user equipment routing policy information is transmitted to the at least one user equipment.

14. A data traffic routing method, characterized in that, include: Acquire configuration data associated with data traffic of at least one user device in a geographic area on the home public terrestrial mobile network, wherein the configuration data includes a mapping relationship between the data traffic and identifiers of at least one co-located public terrestrial mobile network providing access to an edge application server in the geographic area, wherein the co-located public terrestrial mobile network includes public terrestrial mobile networks different from the home public terrestrial mobile network, but not guest public terrestrial mobile networks used for roaming. Based on the configuration data, the data traffic is routed to the co-located public land mobile network.

15. A computer program product, characterized in that, Includes a computer program for performing the method according to claim 14 when the computer program is executed on a computer.

Images