Traffic routing towards the local data network based on application function requests

Abstract

The present disclosure relates to traffic routing towards a local area data network based on an application function request. The present invention discloses a cellular network, the cellular network comprising a first network component, the first network component being configured to: i) identify a first session between a first data network and a user equipment (UE), wherein the first session corresponds to a first session management function (SMF); ii) receive data network access information (DNAI) from a network function, the DNAI corresponding to a second data network; and iii) select a second SMF to be used for a second session between the second data network and the UE. The cellular network also comprises a second network component, the second network component being configured to: i) store a mapping between the DNAI and the second SMF, and ii) transmit an indication of the second SMF to the first network component, wherein the first network component selects the second SMF based on the indication.

Description

Background Art

[0001] Edge computing refers to performing computation and data processing at the network where the data is generated. This allows performance to be optimized and latency to be minimized. Edge computing is a distributed approach where data processing is localized.

[0002] 5G New Radio (NR) networks can be equipped with edge computing capabilities. One aspect of edge computing within the context of 5G NR is local access to data networks. Local access typically involves routing traffic to a data network near the end user's location, such as a local area data network. This improves latency by shortening the distance that data must travel within the 5G NR network.

[0003] In order to route the traffic towards the local area data network, the relevant network function may be configured with data network access information (DNAI) for the requested data network. However, in conventional situations, the network function may not be configured with a DNAI for the requested data network. Summary of the invention

[0004] Some exemplary embodiments relate to a method performed by an access and mobility management function (AMF) of a cellular network. The method includes: identifying a first session between a first data network and a user equipment (UE), wherein the first session corresponds to a first session management function (SMF); receiving data network access information (DNAI) from a network function, wherein the DNAI corresponds to a second data network; and selecting a second SMF to be used for a second session between the second data network and the UE.

[0005] Other exemplary embodiments relate to a cellular network including a plurality of network components. A first network component is configured to: i) identify a first session between a first data network and a user equipment (UE), wherein the first session corresponds to a first session management function (SMF); ii) receive data network access information (DNAI) from the network function, the DNAI corresponding to a second data network; and iii) select a second SMF to be used for a second session between the second data network and the UE. A second network component is configured to: i) store a mapping between the DNAI and the second SMF, and ii) transmit an indication of the second SMF to the first network component, wherein the first network component selects the second SMF based on the indication. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 Exemplary network arrangements are shown according to various exemplary embodiments.

[0007] Figure 2AA first exemplary architectural arrangement of an edge computing architecture according to various exemplary embodiments described herein is shown, the first exemplary architectural arrangement including accessing an edge application server (EAS) via an uplink (UL) classifier (CL) and a branching point (BP).

[0008] Figure 2B A second exemplary architectural arrangement of an edge computing architecture according to various exemplary embodiments described herein is shown, which second exemplary architectural arrangement does not include accessing the EAS via the UL CL / BP.

[0009] Figure 3 An exemplary signaling diagram for providing a DNAI to a network storage function (NRF) according to various exemplary embodiments is shown.

[0010] Figure 4 Exemplary architectural arrangements are shown according to various exemplary embodiments.

[0011] Figure 5 A signaling diagram of a data network change including an SMF change initiated by an SMF according to various exemplary embodiments is shown.

[0012] Figure 6 A signaling diagram of a data network change including an SMF change initiated by an SMF according to various exemplary embodiments is shown.

[0013] Figure 7 A signaling diagram of a data network change including an SMF change initiated by a PCF is shown according to various exemplary embodiments.

[0014] Figure 8 Exemplary architectural arrangements are shown according to various exemplary embodiments.

[0015] Fig. 9 A signaling diagram of a data network change including an Intermediate-SMF (I-SMF) change initiated by an SMF is shown according to various exemplary embodiments.

[0016] Fig.10 A signaling diagram of a data network change including an I-SMF change initiated by a PCF is shown according to various exemplary embodiments.

[0017] Fig.11 An exemplary user equipment (UE) is shown in accordance with various exemplary embodiments. DETAILED DESCRIPTION

[0018] The exemplary embodiments may be further understood with reference to the following description and associated drawings, wherein similar elements have the same reference numerals.Exemplary embodiments relate to routing traffic toward a local area data network.

[0019] The exemplary embodiments are described with respect to UE. However, reference to UE is provided for illustration purposes only. The exemplary embodiments may be used with any electronic component that can establish a connection with a network and is configured with hardware, software and / or firmware for exchanging information and data with the network. Therefore, the UE described herein is used to represent any electronic component.

[0020] In addition, the exemplary embodiments are described with reference to a 5G New Radio (NR) cellular network. However, reference to a 5G NR network is provided for illustration purposes only. The exemplary embodiments may be used with any network that implements the functionality described herein for edge computing. Thus, a 5G NR network as described herein may represent any network that includes functionality associated with edge computing.

[0021] Exemplary embodiments relate to edge computing within a 5G NR network. One aspect of edge computing within the context of 5G NR is local access to data networks. The term "local access" generally refers to routing traffic to a data network at or near the edge of a 5G NR network. This improves latency by shortening the distance that data must travel within the 5G NR network. However, reference to local access is provided for illustrative purposes only. Different entities may refer to similar concepts by different names.

[0022] The exemplary embodiments are described with reference to configuring a packet data unit (PDU) session for a UE. Those skilled in the art will appreciate that a PDU session generally refers to a logical connection between a UE and a data network. Throughout the specification, the term "local area data network" refers to a data network located near the UE within the context of 5G NR. The exemplary embodiments will include a mechanism implemented on the network side for configuring a PDU session for a UE to a local area data network. This may include establishing a new PDU session or modifying an existing PDU session.

[0023] As noted above, one problem with conventional edge computing in 5G NR is that the network function may not be configured with data network access information (DNAI) for a particular data network. Without the DNAI, traffic may not be routed to the corresponding data network, and therefore, a PDU session may not be established. An exemplary embodiment involves providing a DNAI for a requested data network to one or more relevant network components to enable routing of traffic to the requested data network.

[0024] Figure 1A network arrangement 100 according to various exemplary embodiments is shown. The network arrangement 100 includes a UE 110. Those skilled in the art will appreciate that the UE 110 may be any type of electronic component configured to communicate via a network, such as a mobile phone, a tablet, a smart phone, a phablet, an embedded device, a wearable device, a Cat-M device, a Cat-M1 device, an MTC device, an eMTC device, other types of Internet of Things (IoT) devices, etc. A practical network arrangement may include any number of UEs used by any number of users. Therefore, the example of a single UE 110 is provided for illustration purposes only.

[0025] UE 110 may communicate with one or more networks. In the example of network configuration 100, the networks with which UE 110 may wirelessly communicate are 5G New Radio (NR) radio access network (5G NR-RAN) 120, LTE radio access network (LTE-RAN) 122, and wireless local area network (WLAN) 124. However, UE 110 may also communicate with other types of networks, and UE 110 may also communicate with a network via a wired connection. Thus, UE 110 may include a 5G NR chipset that communicates with 5G NR-RAN 120, an LTE chipset that communicates with LTE-RAN 122, and an ISM chipset that communicates with WLAN 124.

[0026] 5G NR-RAN 120 and LTE-RAN 122 may be parts of cellular networks that may be deployed by cellular providers (e.g., Verizon, AT&T, Sprint, T-Mobile, etc.). These networks 120, 122 may include, for example, base stations (NodeB, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive traffic from UEs equipped with appropriate cellular chipsets. WLAN 124 may include any type of wireless local area network (WiFi, hotspot, IEEE 802.11x network, etc.). More details of 5G NR-RAN 120 will be provided below.

[0027] The base station (e.g., gNB 120A, eNB 122A) may include one or more communication interfaces to exchange data and / or information with the camped UE, the corresponding RAN, the cellular core network 130, the Internet 140, etc. It will be appreciated by those skilled in the art that any association process may be performed for the UE 110 to connect to the 5G NR-RAN 120. For example, as described above, the 5G NR-RAN 120 may be associated with a specific cellular service provider, where the UE 110 and / or its user has agreement and credential information (e.g., stored on a SIM card). Upon detecting the presence of the 5G NR-RAN 120, the UE 110 may transmit corresponding credential information in order to associate with the 5G NR-RAN 120. More specifically, the UE 110 may be associated with a specific cell (e.g., the gNB 120A of the 5G NR-RAN 120). As described above, the use of the 5G NR-RAN 120 is for illustration purposes, and any type of network may be used.

[0028] In addition to the networks 120, 122, and 124, the network arrangement 100 includes a cellular core network 130, the Internet 140, an IP multimedia subsystem (IMS) 150, and a network service backbone 160. The cellular core network 130 can be viewed as an interconnected collection of components that manage the operation and traffic of the cellular network. The cellular core network 130 also manages the traffic flowing between the cellular network and the Internet 140. The IMS 150 can be generally described as an architecture for delivering multimedia services to the UE 110 using the IP protocol. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network service backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network service backbone 160 can be generally described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 to communicate with various networks.

[0029] Figure 2A A first exemplary architectural arrangement 200 of an edge computing architecture according to various exemplary embodiments described herein is shown, the first exemplary architectural arrangement including access to an edge application server (EAS) via an uplink (UL) classifier (CL) and a branching point (BP). A general overview of the various components of the exemplary architectural arrangement 200 will be provided below. However, when describing the exemplary embodiments, specific operations performed by the components with respect to the exemplary embodiments will be described in more detail below. It should also be understood that the components of the exemplary architectural arrangement 200 may reside in the above-described Figure 1 The various physical and / or virtual locations described herein may include within an access network (e.g., within 5G NR-RAN 120), within a core network 130, as well as within a cellular network. Figure 1 Individual components outside of the described positions, etc.

[0030] In addition, Figure 2A In the exemplary architecture arrangement 200, various components are shown as being connected via connections labeled Nx (e.g., N1, N2, N3, N6, N9, etc.). Those skilled in the art will appreciate that each of these connections (or interfaces) is defined in the 3GPP specifications. The exemplary architecture arrangement 200 uses these connections in the manner in which they are defined in the 3GPP specifications. In addition, although these interfaces are referred to as connections throughout the specification, it should be understood that these interfaces do not need to be direct wired connections or wireless connections, that is, these interfaces can communicate via intermediate hardware and / or software components. To provide an example, the UE 110 exchanges communications with the gNB 120A. However, in the architecture arrangement 200, the UE 110 is shown as having a connection to an access and mobility management function (AMF) 230 within the core network 130. The connection or interface is not a direct communication link between the UE 110 and the AMF 230, but rather a connection facilitated by intermediate hardware and software components. Therefore, throughout the specification, the terms "connection" and "interface" may be used interchangeably to describe the Nx interface between various components.

[0031] The architecture arrangement 200 includes a UE 110 and an access network (AN) 120 (e.g., a 5G NR-RAN 120). The AN 120 is connected to a first user plane function (UPF) 205. The UPF 205 performs various functions within the core network 130, including packet routing and forwarding. In this example, the UPF 205 includes a UL CL / BP function. Generally speaking, the UL CL function may refer to providing destination-based multi-homing to achieve load balancing, and the BP may refer to forwarding UL traffic to different PDU session anchors (PSAs). The first UPF 205 is also connected to a second UPF 210 and a third UPF 215. The second UPF 210 and the third UPF 215 include PSA functions. The third UPF 215 is connected to a data network (DN) 220.

[0032] In this exemplary embodiment, the second UPF 210 is connected to a local EAS 225. Those skilled in the art will appreciate that the EAS 225 may include one or more EASs, as will be described in more detail below. In addition, those skilled in the art will appreciate that the network may include one or more additional UPFs (not shown) each connected to one or more additional EASs (not shown).

[0033] In addition to the above connections, the UE 110 and the AN 120 may also be connected to the AMF 230. The AMF 230 is generally responsible for mobility management in the 5G NR-RAN 120. For example, the AMF 230 may be responsible for managing handovers between gNBs. In another example, the AMF 230 may be able to store information related to ongoing sessions. In another example, the AMF 230 may be configured to modify and create a session from a first SMF to a second SMF. The UPF 205-215 may also include a connection to a session management function (SMF) 235. The SMF 235 may generally be responsible for creating, updating, and removing protocol data unit (PDU) sessions for the UE. In this example, the SMF 235 is configured to store information related to paths to other SMFs (or intermediate SMFs (I-SMFs)).

[0034] The exemplary architecture arrangement 200 also includes a network exposure function (NEF) 240. The NEF 240 is generally responsible for securely exposing services and capabilities provided by the 5G NR-RAN 120 network functions. The exemplary architecture arrangement 200 also includes a positioning calculation function (PCF) 245. The PCF 245 is generally responsible for determining the location of the UE 110. The exemplary architecture arrangement 200 also includes an application function (AF) 250. The AF 250 can be considered as a logical element that provides session related information.

[0035] Figure 2B A second exemplary architecture arrangement 260 of an edge computing architecture according to various exemplary embodiments described herein is shown, which does not include accessing the EAS via the UL CL / BP. Thus, in this exemplary architecture arrangement 260, there is no UPF (e.g., Figure 2A 205). In the exemplary architecture arrangement 260, the AN 120 is connected to a UPF 270 including a PSA function. The UPF 270 is connected to a DN 275 including an EAS 280. Similar to the architecture arrangement 200, those skilled in the art will appreciate that the DN 275 may include one or more EASs 280, and the network may include one or more additional UPFs (not shown), each of which is connected to one or more additional DNs having one or more EASs (not shown). The remaining components are the same as described with respect to the architecture arrangement 200 and will not be described again.

[0036] References Figure 2A and Figure 2B The arrangements 200 and 260 shown and described are intended to provide two exemplary arrangements of edge computing architectures in which the exemplary embodiments may be implemented. However, it should be understood that there may be other edge computing architectures that may be implemented with the exemplary embodiments. In addition, as described above, Figure 2A and Figure 2B The related description is intended only to provide a general overview of the components in various arrangements. Exemplary operations performed by the components in implementing the exemplary embodiments will be provided below.

[0037] The exemplary embodiments are described with reference to the following exemplary scenarios. Initially, UE 110 is configured with a PDU session to a first data network. During operation, a serving AF may initiate a request for a data network change. In order to provide UE 110 with local access to the requested data network, it may be necessary to provide a DNAI for the requested data network to a serving network function (e.g., SMF, I-SMF, etc.). As will be described in more detail below, the exemplary embodiments include various mechanisms for providing the requested DNAI to the relevant network functions to enable local access to the requested data network.

[0038] Figure 3 An exemplary signaling diagram 300 for providing a DNAI to a network storage function (NRF) 305 according to various exemplary embodiments is shown. Those skilled in the art will appreciate that the NRF 305 may perform operations related to network service discovery functions, which allow network functions to determine where and how to access other network functions. As will be described following the description of the signaling diagram 300, the NRF 305 may provide the DNAI and other information to the AMF during SMF selection, which may occur when configuring local access to a requested data network.

[0039] Signaling diagram 300 includes NRF 305, UPF 310, and SMF 315. In 320, UPF 310 transmits DNAI information to NRF 305. For example, UPF 310 may register with NRF 305 using Nnrf_NFManagement_NFRegister message. The message may be configured to include a list of DNAIs supported by UPF 310 and SMF region IDs that may be served by UPF 310. In some embodiments, the message may be transmitted directly to NRF 305. In other embodiments, the message may be transmitted indirectly to NRF 305 via a connected SMF (e.g., SMF 310).

[0040] In 325, NRF 305 may transmit a response to the DNAI information. For example, NRF 305 may transmit a create session response to UPF 310 in response to the Nnrf_NFManagement_NFRegister message. This signaling exchange may occur according to a currently existing UPF management procedure or a future specific implementation of the UPF management procedure.

[0041] In 330, SMF 310 transmits DNAI information to NRF 305. For example, SMF 315 may register with NRF 305 using Nnrf_NFManagement_NFRegister message. The message may be configured to include PSA information, SMF region ID, and a list of DNAIs to which SMF 310 can provide services. In 325, NRF 305 may transmit a response to the DNAI information. For example, NRF 305 may transmit Nnrf_NFmanagement_NFregister response.

[0042] Various UPFs and SMFs may provide DNAI information to NRF 305 using signaling exchanges similar to the above-mentioned signaling diagram 300. In some embodiments, NRF 305 may periodically synchronize with the network according to a schedule or timer to collect DNAI information from any newly added UPF and SMF. In other embodiments, NRF may synchronize with the network in response to predetermined conditions (e.g., user input, a signal received from another network component, an indication of a newly added network function, etc.) to collect DNAI information from any newly added UPF and SMF. Therefore, NRF 305 may have context information related to DNAI information. This context information may include mapping of UPF to SMF area ID and mapping of SMF to corresponding DNAI. NRF 305 may have this context information for one or more public land mobile networks (PLMN). As will be described below, when configuring access to the requested local area data network, NRF 305 may then provide this information to other network functions (e.g., AMF) for SMF selection.

[0043] The following signaling diagrams 500 to 700 will be described with reference to the above-described exemplary scenario in which the AF requests a data network change. Figure 4 The illustrated architectural arrangement 400 shows a reference Figure 2B For example, consider that UE 110 is initially configured with Figure 2B 260. Subsequently, AF 250 requests a data network change from DN 275 to a new data network (nDN 405). nDN 405 is served by UPF 410 and SMF 415. Those skilled in the art will appreciate that nDN 405, UPF 410, and SMF 415 may be used to interface to each other and other network components of architectural arrangement 260.

[0044] Figure 5 A signaling diagram 500 of a data network change including an SMF change initiated by an SMF is shown according to various exemplary embodiments. Figure 4The signaling diagram 500 is described with reference to the architectural arrangement 400 of FIG.

[0045] The signaling diagram 500 includes AF 250 , NEF 240 , unified data store (UDR) 502 , PCF 245 , SMF 235 , NRF 305 , AMF 230 , SMF 415 , and UPF 410 .

[0046] In 510, there is an ongoing PDU session. From the perspective of AF 250, a PDU session may be conducted between UE 110 and DN 275. The control plane of the PDU session may be served by various network components including SMF 235 and AMF 230.

[0047] In 515, AF 250 initiates a request for a data network change associated with the ongoing PDU session of 510. In this example, the data network change is requested for nDN 405, and therefore, the request may include a DNAI associated with nDN 405. However, an actual request may be for multiple data networks and therefore include a list of DNAIs. The basis for initiating the data network change request is beyond the scope of the exemplary embodiment. The exemplary embodiment is applicable to initiating the request for any appropriate reason.

[0048] In 520, AF 250 may transmit a request to NEF 240. For example, AF 250 may transmit to NEF 240 an Nnef_trafficinfluence_create request including information such as, but not limited to, one or more DNAIs (e.g., DNAIs associated with nDN 405), AF service IDs, application identifiers, and an indication of relocation possibility.

[0049] In 525, the request received from the AF 250 is stored locally at the NEF 240 and / or the UDR 502. In 530, the UDR 502 sends a notification message to the PCF 245. For example, the UDR 502 may send a Nudr_DM_Notify message including the requested one or more DNAIs, the AF service ID, and the application identifier. Those skilled in the art will appreciate that the UDR 502, PCF 245, AMF 230, and SMF 235 may be subscribed to exchange information prior to the signaling described in the signaling diagram 500.

[0050] In 535, the PCF 245 transmits a policy control notification to the SMF 235. The policy control notification may include the requested one or more DNAIs, AF session IDs, and application identifiers.

[0051] SMF 235 can use this information to determine whether SMF 235 can route the session to the requested DNAI. In this example, it is assumed that SMF 235 is not currently configured with the requested DNAI. Therefore, when SMF 235 receives the policy control notification, it can recognize that it is not configured with the DNAI requested by AF 250.

[0052] In 540, the SMF 235 indicates to the AMF 230 that the SMF 235 is not configured with the requested DNAI. For example, the SMF 235 may send an Nsfm_event_exposure_notify message to the AMF 230 indicating that an ongoing PDU session needs to be modified or a new PDU session is to be created to facilitate the user plane path change to the nDN 405. The message may include the PDU session ID and the requested DNAI.

[0053] In 545, AMF 230 initiates network function discovery with NRF 305. The request may include the requested DNAI. NRF 305 may then determine an SMF that can handle the current context along with the requested DNAI. For example, as described above with reference to Figure 3 As described, NRF 305 may have a mapping between AMF, SMF, and DNAI. Therefore, NRF 305 may check the mapping table and provide a response to AMF 230 in 550, which identifies the SMF that can handle the current context together with the requested DNAI. In this example, AMF 230 identifies SMF 415.

[0054] In 555, AMF 230 selects a new SMF (e.g., SMF 415) based on the information requested from NRF 305. In 560, AMF 230 may transmit session information to the selected SMF 415. For example, AMF 230 may transmit an Nsmf_eventexposure subscription message. The message may include information related to the previous session from SMF 325, a session establishment indication, and a data network name (DNN) ID. This transfers the active PDU session from SMF 235 to SMF 415. This may include modifying an ongoing PDU session or creating a new PDU session.

[0055] In 565, the SMF 415 and the UPF 410 perform a signaling exchange to establish the N4 session. In 570, the SMF 415 transmits the application relocation information to the AF 250. For example, the SMF 415 may transmit a Nsmf_eventexposure_apprelocationinfo message to the AF 250, which includes the PDU session ID and the DNAI associated with the nDN 405. If a new PDU session is established, additional signaling may be performed to update the AF 250 and other network functions with the new session information and the release of the old PDU session.

[0056] Figure 6 A signaling diagram 600 of a data network change including an SMF change initiated by an SMF is shown according to various exemplary embodiments. Figure 4 The architecture layout of 400 and Figure 5 The signaling diagram 600 is described with reference to the architectural arrangement 500 of FIG.

[0057] Signaling diagram 600 relates to a scenario substantially similar to that shown in signaling diagram 500. However, in this example, SMF 235 is connected to SMF 415. As will be described below, SMF 235 may select SMF 415 based on this information and therefore may not query NRF 305.

[0058] The signaling diagram 600 starts at 535 of the signaling diagram 500 and does not include the discovery and response of the NRF 305. Therefore, only the AF 250, PCF 245, SMF 235, AMF 230, SMF 415 and UPF 410 are shown in the signaling diagram 600.

[0059] In 605, the PCF 245 transmits a policy control notification to the SMF 235. This is substantially similar to 535 of the signaling diagram 500.

[0060] In 610, SMF 235 identifies a new SMF (e.g., SMF 415) that can be used for the requested DNAI. For example, as described above, SMF 235 and SMF 415 can be connected. Therefore, SMF 235 can know that SMF 415 can handle the current context together with the requested DNAI.

[0061] In 615, the SMF 235 indicates to the AMF 230 that the SMF 235 is not configured with the requested DNAI. For example, as in 540 of the signaling diagram 500, the SMF 235 may send an Nsfm_event_exposure_notify message to the AMF 230 indicating that an ongoing PDU session needs to be modified or a new PDU session is to be created to facilitate the user plane path change to the nDN 405. In contrast to 540, the message in 615 may include information corresponding to the selected SMF (e.g., SMF 415).

[0062] In 620, AMF 230 selects a new SMF (e.g., SMF 415) based on the information received from SMF 235. In some embodiments, SMF 235 may automatically release the session and transfer the context to the new SMF 415 via AMF 230. In other embodiments, SMF 415 may request SMF 235 to release the session and provide context information.

[0063] In 625, the AMF 230 may transmit session information to the selected SMF 415. This is substantially similar to 560 of the signaling diagram 500. In 630, the SMF 415 and the UPF 410 perform a signaling exchange to establish an N4 session. This is substantially similar to 565 of the signaling diagram 500. In 635, the SMF 415 transmits application relocation information to the AF 250. This is substantially similar to 570 of the signaling diagram 500. As described above, if a new PDU session is established, additional signaling may be performed to update the AF 250 and other network functions with the new session information and the release of the old PDU session.

[0064] Figure 7 A signaling diagram 700 of a data network change including an SMF change initiated by a PCF is shown according to various exemplary embodiments. Figure 4 The architecture layout of 400 and Figure 5 The signaling diagram 700 is described with reference to the architectural arrangement 500 of FIG.

[0065] The signaling diagram 700 relates to a scenario that is substantially similar to the scenarios shown in the signaling diagrams 500 to 600. However, in this example, the PCF 245 initiates the SMF change.

[0066] The signaling diagram 700 occurs after 505-530 of the signaling diagram 500. Therefore, only the AF 250, the PCF 245, the SMF 235, the NRF 305, the AMF 230, the SMF 415, and the UPF 410 are shown in the signaling diagram 700.

[0067] As described above, in 530, UDR 502 sends a notification message to PCF 245. For example, UDR 502 may send a Nudr_DM_Notify message that includes the requested one or more DNAIs, AF service ID, and application identifier.

[0068] In 705, the PCF 245 transmits a policy control notification to the SMF 235. The policy control notification may include the requested DNAI. In 710, the SMF 235 sends a response indicating that the SMF 235 is not configured to support sessions with the requested DNAI.

[0069] In 715, the PCF 245 transmits a policy control update to the AMF 230. The message may include the requested DNAI and a request to relocate the session to a new SMF.

[0070] In 720, AMF 230 initiates network function discovery with NRF 305. For example, based on the message received from PCF 245, AMF 230 may assume that SMF 235 cannot handle the session on the requested DNAI. This may trigger AMF 230 to initiate SMF discovery. The discovery request may include the requested DNAI. NRF 305 may then determine an SMF that can handle the current context together with the requested DNAI. For example, as described above with reference to Figure 3 As described above, NRF 305 may have a mapping between AMF, SMF and DNAI. Therefore, NRF 305 may check the mapping table.

[0071] In 725, NRF 305 transmits a response to AMF 230, which identifies the SMF that can handle the current context together with the requested DNAI. In this example, AMF 230 identifies SMF 415.

[0072] In 730, the AMF 230 selects a new SMF (e.g., SMF 415) based on the information received from the NRF 305. In 735, the AMF 230 may transmit session information to the selected SMF 415. This is substantially similar to 560 of the signaling diagram 500. In 740, the SMF 415 and the UPF 410 perform a signaling exchange to establish an N4 session. This is substantially similar to 565 of the signaling diagram 500. In 745, the SMF 415 transmits application relocation information to the AF 250. This is substantially similar to 570 of the signaling diagram 500. As described above, if a new PDU session is established, additional signaling may be performed to update the AF 250 and other network functions with the new session information and the release of the old PDU session.

[0073] The following exemplary embodiments will be described with reference to Enhanced SMF and UPF Topology in 5G Networks (ETSUN). ETSUN is a use case that includes an intermediate SMF (I-SMF). The I-SMF can be used for PDU session continuity. For example, the I-SMF can be inserted between the AMF and the SMF to maintain the PDU session. The I-SMF can also perform operations related to selecting and controlling the UPF.

[0074] The following signaling diagrams 900 to 1000 will be described with reference to the above-described exemplary scenario in which the AF requests a data network change. In contrast to the signaling diagrams 500 to 700, an I-SMF is included in the architecture. Figure 8 The illustrated architectural arrangement 800 shows a reference Figure 2A For example, consider that UE 110 is initially configured with Figure 2A 810. The embodiment of the present invention illustrates a scenario of a PDU session of the architecture arrangement 200 and the I-SMF 805. Subsequently, the AF 250 requests a data network change from the DN 220 to the new data network (nDN 810). The nDN 405 is served by the UPF 815 and the I-SMF 820. Those skilled in the art will appreciate that the I-SMF 805, the nDN 810, the UPF 415, and the I-SMF 820 may be used to interface to each other and other network components of the architecture arrangement 200.

[0075] Fig. 9 A signaling diagram 900 of a data network change including an I-SMF change initiated by an SMF is shown according to various exemplary embodiments. Figure 8 The signaling diagram 900 is described with reference to the architectural arrangement 800 .

[0076] The signaling diagram 900 includes the AF 250, the NEF 240, the UDR 902, the PCF 245, the SMF 235, the I-SMF 805, the AMF 230, the I-SMF 820 and the UPF 815. Thus, in contrast to the signaling diagrams 500 to 700, the NRF 305 is not used.

[0077] In 910, a PDU session is ongoing. From the perspective of AF 250, a PDU session may be conducted between UE 110 and DN 220. The control plane of the PDU session may be served by various network components including SMF 235, I-SMF 805, and AMF 230.

[0078] At 915, AF 250 initiates a request for a data network change associated with the ongoing PDU session of 910. In this example, the data network change is requested for nDN 810, and therefore, the request may include a DNAI associated with nDN 810. However, an actual request may be for multiple data networks and therefore include a list of DNAIs. The basis for initiating the data network change request is beyond the scope of the exemplary embodiment. The exemplary embodiment is applicable to initiating the request for any appropriate reason.

[0079] In 920, AF 250 may transmit a request to NEF 240. For example, AF 250 may transmit to NEF 240 an Nnef_trafficinfluence_create request including information such as, but not limited to, one or more DNAIs (e.g., DNAIs associated with nDN 810), AF service IDs, application identifiers, and an indication of relocation possibility.

[0080] In 925, the request received from the AF 250 is stored locally at the NEF 240 and / or the UDR 902. In 930, the UDR 902 sends a notification message to the PCF 245. For example, the UDR 902 may send a Nudr_DM_Notify message including the requested one or more DNAIs, the AF service ID, and the application identifier. Those skilled in the art will appreciate that the UDR 902, PCF 245, AMF 230, SMF 235, and I-SMF 805 may be subscribed to exchange information prior to the signaling described in the signaling diagram 900.

[0081] In 935, the PCF 245 transmits a policy control notification to the SMF 235. The policy control notification may include the requested one or more DNAIs, AF service IDs, and application identifiers.

[0082] SMF 235 may use this information to determine whether SMF 235 and I-SMF 805 are able to route the session to the requested DNAI. In this example, it is assumed that SMF 235 and I-SMF 805 are not currently configured with the requested DNAI. Therefore, when SMF 235 receives the policy control notification, it may identify that SMF 235 and I-SMF 805 are not configured with the DNAI requested by AF 250.

[0083] In 940, SMF 235 transmits a request to AMF 230. The request may be for releasing the I-SMF 805 PDU session with the user plane path change. The request may also include a new I-SMF ID. That is, since SMF 235 is connected to I-SMF 820, SMF 235 knows that I-SMF 820 can handle the requested DNAI. In some embodiments, the request may be a Nsfm_event_exposure message.

[0084] In 945, the AMF 230 selects a new I-SMF (e.g., I-SMF 820) based on the information received from the SMF 235. In 950, the I-SMF 820 performs a signaling exchange with the SMF 235. This may include a session management context creation request and a response to transfer context from the I-SMF 805 to the new I-SMF 820. In some embodiments, the signaling exchange may occur between the old I-SMF 805 and the new I-SMF 820.

[0085] In 955, the I-SMF 820 and the UPF 815 perform a signaling exchange to establish the N4 session. In 960, the I-SMF 820 transmits application relocation information to the AF 250. For example, the I-SMF 820 may transmit a Nsmf_eventexposure_apprelocationinfo message to the AF 250, which includes the PDU session ID and the DNAI associated with the nDN 810. If a new PDU session is established, additional signaling may be performed to update the AF 250 and other network functions with the new session information and the release of the old PDU session.

[0086] Fig.10 A signaling diagram 1000 of a data network change including an I-SMF change initiated by a PCF is shown according to various exemplary embodiments. Figure 8 The architecture layout of 800 and Fig. 9 The signaling diagram 1000 is described with reference to the architectural arrangement 900 .

[0087] The signaling diagram 1000 relates to a scenario that is substantially similar to the scenario shown in the signaling diagram 900. However, in this example, the PCF 245 initiates the I-SMF change and the NRF 305 is used.

[0088] The signaling diagram 1000 occurs after 910-930 of the signaling diagram 900. Therefore, only the AF 250, the PCF 245, the SMF 235, the I-SMF 805, the AMF 230, the NRF 305, the I-SMF 820 and the UPF 810 are shown in the signaling diagram 1000.

[0089] As described above, in 930, the UDR 902 sends a notification message to the PCF 245. For example, the UDR 902 may send a Nudr_DM_Notify message including the requested one or more DNAIs, the AF service ID, and the application identifier.

[0090] In 1005, PCF 245 performs a policy control signaling exchange with SMF 235. This may include PCF 245 transmitting a policy control notification to SMF 235. The policy control notification may include the requested DNAI. SMF 235 may then send a response indicating that SMF 235 and I-SMF 805 are not configured to support sessions with the requested DNAI.

[0091] In 1010, the PCF 245 transmits a policy control update to the AMF 230. The message may include the requested DNAI and a request to relocate the session to a new SMF.

[0092] In 1015, AMF 230 initiates network function discovery with NRF 305. For example, based on the message received from PCF 245, AMF 230 may assume that SMF 235 and / or I-SMF 805 cannot handle the session on the requested DNAI. This may trigger AMF 230 to initiate SMF discovery. The discovery request may include the requested DNAI. NRF 305 may then determine an I-SMF that can handle the current context together with the requested DNAI. For example, as described above with reference to Figure 3 As described above, NRF 305 may have a mapping between AMF, SMF and DNAI. Therefore, NRF 305 may check the mapping table.

[0093] In 1020, NRF 305 transmits a response to AMF 230, which identifies the I-SMF that can handle the current context together with the requested DNAI. In this example, AMF 230 identifies I-SMF420.

[0094] In 1025, the AMF 230 selects a new I-SMF (e.g., I-SMF 820) based on the information received from the NRF 305. In 1030, the I-SMF 820 performs a signaling exchange with the SMF 235. This may include a session management context creation request and a response to transfer context from the I-SMF 805 to the new I-SMF 820. In some embodiments, the signaling exchange may occur between the old I-SMF 805 and the new I-SMF 820.

[0095] In 1035, the I-SMF 820 and the UPF 815 perform a signaling exchange to establish the N4 session. In 1040, the I-SMF 820 transmits application relocation information to the AF 250. For example, the I-SMF 820 may transmit a Nsmf_eventexposure_apprelocationinfo message to the AF 250, the message including the PDU session ID and the DNAI associated with the nDN 810. If a new PDU session is established, additional signaling may be performed to update the AF 250 and other network functions with the new session information and the release of the old PDU session.

[0096] Fig.11 An exemplary user equipment (UE) 110 is shown in accordance with various exemplary embodiments. Figure 1 100 is used to describe the UE 110. The UE 110 may represent any electronic device and may include a processor 1105, a memory arrangement 1110, a display device 1115, an input / output (I / O) device 1120, a transceiver 1125, and other components 1130. The other components 1130 may include, for example, a SIM card, an audio input device, an audio output device, a battery providing a limited power source, a data acquisition device, a port for electrically connecting the UE 110 to other electronic devices, and the like.

[0097] The processor 1105 may be configured to execute a number of engines of the UE 110. For example, the engines may include a control plane engine 1135. The control plane engine 1135 may perform various operations related to establishing and maintaining a connection to a local area data network.

[0098] The above-described engine as an application (e.g., program) executed by processor 1105 is merely exemplary. Functions associated with the engine may also be represented as independent combined components of UE 110, or may be modular components coupled to UE 110, such as integrated circuits with or without firmware. For example, an integrated circuit may include input circuits for receiving signals and processing circuits for processing signals and other information. The engine may also be embodied as one application or multiple separate applications. In addition, in some UEs, the functionality described for processor 1105 is shared between two or more processors (such as a baseband processor and an application processor). The exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0099] The memory arrangement 1110 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 1115 may be a hardware component configured to display data to a user, and the I / O device 1120 may be a hardware component that enables user input. The display device 1115 and the I / O device 1120 may be separate components or may be integrated together (such as a touch screen). The transceiver 1125 may be a hardware component configured to establish a connection with the 5G NR-RAN 120, the WLAN 122, etc. Thus, the transceiver 1125 may operate on multiple different frequencies or channels (e.g., a set of continuous frequencies).

[0100] Those skilled in the art will appreciate that the exemplary embodiments described above may be implemented with any suitable software configuration or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, etc. The exemplary embodiments of the above methods may be embodied as a program comprising lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, may be executed on a processor or microprocessor.

[0101] Although this patent application describes various combinations of various embodiments each having different features, those skilled in the art will understand that any feature of an embodiment may be combined with features of other embodiments in any manner not publicly denied or with features that are not functionally or logically inconsistent with the operation or function of the device of the embodiments disclosed in the present invention.

[0102] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0103] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is intended to cover modifications and variations of the present disclosure, provided that these modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. A method comprising: At the access and mobility management function AMF of the cellular network: identifying a first session between a first data network and a user equipment UE, wherein the first session corresponds to a first session management function SMF; receiving data network access information DNAI from a network function, the DNAI corresponding to a second data network different from the first data network; In response to receiving the DNAI, transmitting a request to another network function, wherein the other network function stores a mapping between a set of DNAIs and one or more SMFs; receiving an indication to a second SMF from the further network function; as well as Selecting the second SMF to be used for a second session between the second data network and the UE, wherein the second SMF is selected based on the indication.

2. The method of claim 1, wherein the network function is the first SMF. The method of claim 1 , wherein the second SMF is an intermediate SMF (I-SMF).

4. The method according to claim 1, further comprising: An indication of the second SMF is received from the first SMF, wherein the second SMF is selected based on the indication. The method of claim 4 , wherein the second SMF is an intermediate SMF (I-SMF). The method of claim 1 , wherein the network function is a policy and control function (PCF).

7. The method according to claim 6, further comprising: transmitting the request to another network function, wherein the other network function stores a mapping between a set of DNAIs and one or more SMFs; as well as An indication of the second SMF is received from the further network function, wherein the second SMF is selected based on the indication. The method of claim 7 , wherein the second SMF is an intermediate SMF (I-SMF).

9. A cellular network comprising: A first network component, the first network component being configured to: i) identify a first session between a first data network and a user equipment UE, wherein the first session corresponds to a first session management function SMF; ii) receive data network access information DNAI from a network function, the DNAI corresponding to a second data network different from the first data network; and iii) selecting a second SMF to be used for a second session between the second data network and the UE; and a second network component configured to: i) store a mapping between the DNAI and the second SMF, and ii) transmit an indication of the second SMF to the first network component, wherein the first network component selects the second SMF based on the indication, Wherein the first network component is further configured to transmit a discovery request to the second network component, and wherein the first network component is triggered to transmit the request based on the DNAI received from the network function.

10. The cellular network of claim 9, wherein the network function is the first SMF.

11. The cellular network of claim 9, wherein the network function is a policy and control function (PCF).

12. The cellular network of claim 9, wherein the second SMF is an intermediate SMF (I-SMF).

13. The cellular network of claim 9, wherein the second network component periodically receives mapping information corresponding to the additional DNAI and the additional SMF.

14. The cellular network of claim 9, wherein the second network component is further configured to receive a list of supported DNAIs from a user plane function (UPF).

15. The cellular network of claim 14, wherein the second network component is further configured to receive an SMF area ID corresponding to the UPF from the UPF.

16. The cellular network of claim 14, wherein the second network component is further configured to receive, from another SMF, DNAI information that the another SMF is configured to provide a service.

17. The cellular network of claim 9, wherein the first session and the second session are associated with the same packet data unit (PDU) session.

18. The cellular network of claim 9, wherein the first session is associated with a first packet data unit (PDU) session and the second session is associated with a second, different PDU session.

19. An access and mobility management function (AMF) of a cellular network, comprising: one or more processors; and A memory storing computer instructions which, when executed by the one or more processors, cause the one or more processors to perform a method according to any one of claims 1-8.

Images