Method, system and computer-readable medium for providing a unified interface configured to support infrequent data communications over a network publishing facility

Abstract

A method, system, and computer-readable medium are disclosed for providing a unified interface configured to support communication between a user equipment (UE) and an application function (AF) via a network exposure function (NEF). The method includes: the NEF receiving, from a session management function (SMF), a protocol data unit (PDU) session event change notification message associated with the UE; the NEF establishing a data distribution path between the UE and the application function (AF) via one of multiple data distribution planes traversing the NEF in response to the PDU session event change notification message; and the NEF processing messages communicated between the UE and the AF via any of the multiple data distribution planes using the single unified interface supported by the NEF.

Description

[Technical Field]

[0001] Priority claim This application claims the benefit of U.S. Patent Application No. 17 / 110,255, filed December 2, 2020, the entire disclosure of which is incorporated herein by reference.

[0002] Technical Field The subject matter described herein relates to improvements in data communications occurring in fifth-generation (5G) telecommunications networks. More particularly, the subject matter described herein relates to methods, systems, and computer-readable media for providing a unified interface configured to support small-scale, infrequent data communications between user equipment and application functions via network publishing capabilities. [Background technology]

[0003] background Currently, 5G telecommunications networks often require infrequent small-scale data communications between low-power user equipment (UE) and application functions (AFs). In particular, such small-scale and infrequent communications are used for cellular-based communications between Internet of Things (IoT) devices and AFs. This communication method enables low-powered wide area (LWPA)-based IoT use cases in which power-constrained UE devices can utilize both the 5G control plane and the 5G data plane for data transmission. Generally, 3GPP provides different methods and / or interfaces to facilitate infrequent small-scale data communications, such as using internet protocol (IP) data delivery over the N6 interface via the user plane or non-Internet protocol data delivery (NIDD) over the control plane. Although there are several different paths available for small-scale and infrequent data communications in 5G communications networks, technical challenges may arise when AFs need to support different AF communication methods. For example, problems can arise if the roaming network is configured to support only Internet Protocol (IP) data delivery and cannot support Non-Internet Protocol Data Delivery (NIDD). Problems can also arise in local breakout roaming scenarios where the visited network supports NIDD via a user plane function (UPF) and the UE's home network supports NIDD via a network exposure function (NEF).Furthermore, issues with AF may arise when a UE is used across multiple network slices, where each slice may support a different deployment model (e.g., a slice provisioned using NEF, a slice provisioned without NEF, or a slice that supports only IP data delivery via UPF without NEF).

[0004] Therefore, a need exists for improved methods and systems for providing a unified interface configured to support infrequent communication over network exposed features or services. Summary of the Invention [Problem to be solved by the invention]

[0005] overview A method, system, and computer-readable medium are disclosed for providing a unified interface configured to support communication between a user equipment (UE) and an application function (AF) via a network publishing function (NEF). The method includes: the NEF receiving, from a session management function (SMF), a protocol data unit (PDU) session event change notification message associated with the UE; the NEF establishing a data distribution path between the UE and the application function (AF) via one of multiple data distribution planes traversing the NEF in response to the PDU session event change notification message; and the NEF processing messages communicated between the UE and the AF via any of the multiple data distribution planes using the single unified interface supported by the NEF.

[0006] In a method according to an aspect of the subject matter described herein, the multiple data distribution planes include a non-IP data distribution (NIDD)-based data communication path established in the control plane between the UE and the AF via the NEF, a NIDD-based data communication path established between the UE and the AF via the NEF and the UPF communicatively connected using an N6 point-to-point tunnel, and an Internet Protocol (IP) data distribution-based data communication path between the UE and the AF communicatively connected via the NEF and the UPF using an N6 interface.

[0007] In a method according to an aspect of the subject matter described herein, the UE includes a low-power Internet of things (IoT) device.

[0008] In a method according to certain aspects of the subject matter described herein, the single unified interface includes a T8 interface and / or an N33 interface.

[0009] In a method according to an aspect of the subject matter described herein, the NEF is configured to switch between multiple data delivery planes while maintaining connectivity for the UE.

[0010] In a method according to one aspect of the subject matter described in this specification, the NEF is configured to establish a listening server that monitors packet traffic from the UPF in response to receiving a PDU session event change notification message.

[0011] In a method according to an aspect of the subject matter described herein, the NEF functions as a PDU session anchor during use of each of multiple data distribution planes. An example of a system for providing a unified interface configured to support communication between a user equipment (UE) and an application function (AF) via a network publishing function (NEF) includes a network node, the network node including at least one processor and a memory, the memory and the at least one processor belonging to a unified interface device configured to host the NEF. The network node further includes a unified interface manager, the unified interface manager being configured, when stored in the memory of the NEF and executed by the at least one processor, to receive a protocol data unit (PDU) session event change notification message associated with the UE from a session management function (SMF), to establish a data distribution path between the UE and the application function (AF) via one of multiple data distribution planes across the NEF in response to the PDU session event change notification message, and to process messages communicated between the UE and the AF via any of the multiple data distribution planes using the single unified interface supported by the NEF.

[0012] In a system according to an aspect of the subject matter described herein, the multiple data distribution planes include a non-IP data distribution (NIDD)-based data communication path established in the control plane between the UE and the AF via the NEF, a NIDD-based data communication path established between the UE and the AF via the NEF and the UPF communicatively connected using an N6 point-to-point tunnel, and an Internet Protocol (IP) data distribution-based data communication path between the UE and the AF communicatively connected via the NEF and the UPF using an N6 interface.

[0013] In a system according to an aspect of the subject matter described herein, the UE includes a low-power Internet of things (IoT) device.

[0014] In a system according to an embodiment of the subject matter described herein, the single unified interface includes a T8 interface and / or an N33 interface.

[0015] In a system according to an aspect of the subject matter described herein, the NEF is configured to switch between multiple data distribution planes while maintaining connectivity for the UE.

[0016] In a system according to one aspect of the subject matter described in this specification, the NEF is configured to establish a listening server that monitors packet traffic from the UPF in response to receiving a PDU session event change notification message.

[0017] In a system according to an aspect of the subject matter described herein, the NEF functions as a PDU session anchor during the use of each of multiple data distribution planes.

[0018] An example of a non-transitory computer-readable medium having executable instructions embodied thereon that, when executed by at least one processor of at least one computer, cause the at least one computer to perform steps including: a NEF receiving, from a session management function (SMF), a protocol data unit (PDU) session event change notification message associated with a UE; the NEF establishing, in response to the PDU session event change notification message, a data distribution path between the UE and an application function (AF) via one of multiple data distribution planes traversing the NEF; and the NEF processing messages communicated between the UE and the AF via any of the multiple data distribution planes using a single unified interface supported by the NEF.

[0019] The subject matter described herein can be implemented in hardware, software, firmware, or any combination thereof. Therefore, the terms "function," "node," or "module" as used herein refer to hardware that may include software and / or firmware components for implementing the described functionality. In some implementations, the subject matter described herein can be implemented using a computer-readable medium having stored thereon computer-executable instructions that, when executed by a computer processor, control a computer to perform steps. Examples of computer-readable media suitable for implementing the subject matter described herein include non-transitory computer-readable media such as disk memory devices, chip memory devices, programmable logic devices, and application-specific integrated circuits. Furthermore, computer-readable media implementing the subject matter described herein can be located on a single device or computing platform or distributed across multiple devices or computing platforms.

[0020] The subject matter described herein will now be described with reference to the accompanying drawings. [Brief explanation of the drawings]

[0021] [Figure 1] FIG. 1 is a logical block diagram illustrating a control plane configured to provide a non-IP data delivery (NIDD) path between a user equipment (UE) and an application function via an NEF. [Figure 2] FIG. 1 is a logical block diagram illustrating a control plane configured to provide a non-IP data delivery (NIDD) path between a UE and an application function via a user plane function (UPF) and an N6 point-to-point (PTP) tunnel. [Figure 3] FIG. 1 is a logical block diagram illustrating a user plane that provides an IP data delivery path between the UE and application functions via the UPF. [Figure 4]1 is a logical block diagram illustrating an aggregated data distribution system configured to establish multiple data distribution paths between a UE and an AF via a NEF and an associated unified interface. [Figure 5] 10 is an exemplary configuration table for mapping NEF listening servers and ports to destination AFs. [Figure 6] 1 is an exemplary database table maintained in a NEF for storing context information of a communication session between a UE and an AF. [Figure 7] FIG. 2 is a block diagram illustrating an example of a network node configured to host a NEF and a uniform interface manager. [Figure 8] 1 is a flowchart illustrating an example of a process for providing a uniform interface configured to support infrequent communication over a network-exposed feature or service. DETAILED DESCRIPTION OF THE INVENTION

[0022] Detailed Description Reference will now be made in detail to various embodiments of the subject matter described herein, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

[0023] Communication of small and infrequent data between user equipment and application functions in 5G networks is primarily used for low-power IoT devices or other devices with power constraints or limitations. It is noteworthy that there are three modes or interfaces that can be used to facilitate small and infrequent data communication between user equipment and application functions for low-power or power-constrained IoT devices operating in 5G networks. For example, a first mode of data communication can be implemented as non-IP data distribution (NIDD)-based data transmission between user equipment and application functions via the NEF using the N33 interface and / or the T8 interface via the 5G system control plane. A second mode of data communication can be implemented as NIDD-based data communication between user equipment and application functions via the UPF using the N6 point-to-point tunnel interface via the 5G system control plane. Furthermore, a third mode of data communication can be implemented as IP data distribution between user equipment and application functions via the UPF using the N6 interface via the 5G system user plane. These three different data distribution options are illustrated in Figures 1-3 and described in detail below.

[0024] Figure 1 illustrates the NIDD data path that exists between user equipment and application functions via the 5G control plane via the NEF. In particular, Figure 1 illustrates a 5G system 100 including a user equipment 102, a control plane 104, and an application function 106. Furthermore, Figure 1 illustrates the control plane 104 as including a radio access network (RAN) 108, an access and mobility management function (AMF) 110, a session management function (SMF) 112, a network exposure function (NEF) 114, and a unified data management function (UDM) 116, which are collectively responsible for establishing a data communication path between the user equipment 102 and the application function 106 via the control plane. In particular, a protocol data unit (PDU) session establishment procedure occurs between the user equipment 102 and the SMF 112. During the session establishment procedure, an NEF identity (e.g., corresponding to the NEF 114) is obtained by the SMF 112 as part of the subscription data received from the UDM 116. Once the NEF identity information is received by the SMF 112, an SMF-NEF connection establishment procedure is performed. In particular, an NIDD mobile originated (MO) message communication path is established between the user equipment 102 and the application function 106. Similarly, an NIDD mobile terminated (MT) message communication path is established between the application function 106 and the user equipment 102. To facilitate the communication path(s), an N33 interface / T8 interface between the application function 106 and the NEF 114 is established by the NEF. Once the communication path via the control plane 104 is established, the user equipment 102 and the application function 106 can communicate small and infrequent data over the 5G system 100.Specifically, the NEF-based NIDD data communication provides an API-based interface (i.e., T8 interface / N33 interface) towards the application functions 106 for both MO and MT message communication between the user equipment 102 and the application functions 106 via the control plane 104. In this manner, the NEF 114 acts as the PDU session anchor for the data delivery path in this scenario.

[0025] Figure 2 illustrates an NIDD data path that exists between user equipment and application functions via a 5G control plane via a UPF. In particular, Figure 2 illustrates a 5G system 200 including a user equipment 202, a control plane 204, and an application function 206. Figure 2 further illustrates the control plane 204 as including a RAN 208, an AMF 210, an SMF 212, and a UPF 220, which are collectively responsible for establishing the data communication path. In particular, data communication using the NIDD over the UPF via the control plane 204 is initiated by a PDU session event procedure (e.g., a PDU session establishment procedure) that occurs between the user equipment 202 and the SMF 212. During this procedure, the SMF 212 selects a UPF (e.g., the UPF 220) and performs an N4 session establishment procedure (i.e., between the SMF 212 and the UPF 220). An N6 point-to-point tunnel 205 is then established by the UPF between the UPF 220 and the application functions 206 to support unstructured NIDD data communication in the 5G system 200. In particular, the UPF-based NIDD provides an N6 point-to-point tunnel interface (between the UPF 220 and the application functions 206) for MO and MT message communication between the user equipment 202 and the application functions 206 via the control plane 204. In this manner, the UPF 220 serves as a PDU session anchor for the data delivery path in this scenario.

[0026] Figure 3 illustrates an IP data delivery path that exists between user equipment and application functions over the 5G user plane via the UPF. In particular, Figure 3 illustrates a 5G system 300 including a user equipment 302, a user plane 304, and an application function 306. Figure 3 further illustrates the user plane 304 as including a RAN 308, an SMF 312, and a UPF 320, which are collectively responsible for establishing a data communication path on the user plane. In particular, data communication using IP data delivery over the UPF via the user plane 304 is initiated by a PDU session event procedure (e.g., a PDU session establishment procedure) between the user equipment 302 and the SMF 312. During this procedure, the SMF 312 selects a UPF 230 and performs an N4 session establishment procedure (i.e., between the SMF 312 and the UPF 320). Data communication on the user plane 304 then occurs. In particular, the UPF-based IP data delivery provides an N6 interface (i.e., between the UPF 320 and the application functions 306) for MO and MT message communication between the user equipment 302 and the application functions 306 via the 5G data plane (i.e., the user plane 304). As such, the UPF 320 serves as the PDU session anchor for the data delivery path in this scenario.

[0027] In general, there are situations in which an application function must support all three of the aforementioned application function communication methods. Example scenarios include a scenario in which a user equipment enters a roaming network that supports only traditional IP data delivery and is not configured to support NIDD data delivery, or a local breakout roaming scenario in which a user equipment leaves a home network that supports NIDD via NEF and enters a visited network that supports only NIDD via UPF. Another example is a scenario in which a user equipment is used across multiple network slices, with each slice supporting a different deployment model (e.g., a first slice with NEF and an adjacent slice without NEF or without NEF and supporting only IP data delivery via UPF). Therefore, it is advantageous for an application function to be configured to support multiple interfaces for multiple different data delivery paths. Thus, the disclosed subject matter relates to an NEF element provisioned with a unified interface configured internally to support i) an N33 interface / T8 interface using control plane data forwarding (i.e., NIDD via NEF), ii) an N6 point-to-point tunnel interface using control plane data forwarding (i.e., NIDD via UPF), and iii) an N6 interface (i.e., IP data delivery) based interface specialized for IoT use cases utilizing user plane data forwarding.

[0028] It should be noted that an AF configured to support only the N6 interface (i.e., without the NEF interface functionality) is severely limited and prevents application functions from leveraging many of the exposed services offered by the NEF. In particular, such a limited AF cannot utilize valuable services offered by the NEF, including, but not limited to: i) monitoring the health of IoT devices via the MONTE service, ii) AF traffic impact services for edge routing use cases, iii) billing third-party service providers (i.e., sponsored data connectivity), iv) configuring network parameters (e.g., sleep timers, etc.), and v) configuring application function sessions, such as the required quality of service (QoS).

[0029] In contrast, the disclosed subject matter is configured to utilize a single unified interface with application functions via the NEF for all three of the aforementioned deployment models. In particular, the NEF is configured to track the current data delivery path (e.g., PDU session path) utilized by the user equipment and accommodate optional path switching using a single T8 / N33 interface directed toward the application function destination to enable small-scale, infrequent data communications between the user equipment and the application function.

[0030] Figure 4 is a logical block diagram illustrating a 5G communications network 400. In particular, network 400 includes an aggregated unified interface system 401 that facilitates a communications path between user equipment 402 and application functions 406. In particular, system 401 includes three communications planes 411-413 and an integrated interface 408 that can be used to provide a small-scale data delivery communications path between user equipment 402 (e.g., a low-power IoT device) and application functions 406. While Figure 4 depicts multiple instances of the same network elements (e.g., UPF 420 and UPF 430, RANs 414, 424, 434, etc.) residing on different communications planes, Figure 4 is a logical diagram, and as such, these depicted network elements may be embodied as a single network element configured to function via each of the depicted communications planes.

[0031] In some embodiments, communication plane 411 comprises a control plane that establishes an NIDD data path between user equipment 402 and application functions 406 via NEF 410 (compliant with 3GPP standards). In particular, NEF 410 can be used to establish a communication connection with unified interface 408 for MO and MT message data communication between user equipment 402 and application functions 406.

[0032] In some embodiments, the unified interface 408 may be embodied as a separate element or may be incorporated within the NEF 410. For example, the NEF 410 may be configured to operate or function as an interworking function (IWF) and may offload any multiple interface requirements (e.g., N6 point-to-point interface and N6 interface) from the AF.

[0033] In particular, the NEF 410 functions as a PDU session anchor for a small-scale data distribution path via the communication plane 411, similar to communication planes 412 to 413 described later.

[0034] In some embodiments, system 401 further includes a second communication plane 412 consisting of a control plane that provides an NIDD data path between user equipment 402 and application functions 406. In particular, communication plane 412 provides the NIDD data path via UPF 420 (compliant with 3GPP standards), which includes N6 point-to-point tunnel interface 422. Specifically, N6 point-to-point tunnel interface 422 is established between UPF 420 and NEF 410, which is located in communication plane 411. Thus, MO and MT messaging communications between user equipment 402 and application functions 406 traverse communication plane 412 using point-to-point tunnel interface 422, NEF 410, and unified interface 408.

[0035] Similarly, system 401 includes a third communication plane 413 consisting of a user plane (or data plane) that provides an IP data delivery path between user equipment 402 and application functions 406. In particular, communication plane 413 enables a UPF-based IP data path (compliant with 3GPP standards) via an N6 interface that terminates at NEF 410 located in communication plane 411. In particular, MO and MT messaging communications between user equipment 402 and application functions 406 are facilitated via NEF 410 and unified interface 408, as shown in FIG.

[0036] As described above, the disclosed subject matter supports a unified interface 408 that enables communication between the NEF 410 and the application functions 406 in the first communication plane 411. Notably, the NEF 410 is provisioned with an AF configuration table 500 (as shown in FIG. 5 ), which maps AFs and corresponding IP addresses, data network name (DNN) information, and / or Network Slice Selection Assistance Information (NSSAI) identification data to the NEF's N6 listening port. In particular, FIG. 5 shows the configuration table 500, which includes an application function identifier column 502, a DNN column 504, an S-NSSAI column 506, an NEF listening server IP address and port column 508, and a server type column 510. The information stored in the configuration table 500 can be used by the NEF 410 to activate a listening server that monitors incoming packets received on the N6 interface or the N6 point-to-point tunnel interface, as described below. Specifically, these listening servers are configured to enable data delivery between user equipment 402 and application function 406 via UPF 430 over the N6 interface (e.g., IP data delivery) or the N6 point-to-point tunnel interface (e.g., NIDD via UPF 420 and tunnel interface 422).

[0037] After pre-configuration, the NEF 410 uses the configuration details (not shown) contained in table 500 to start a listening server that listens for incoming N6 (TCP / IP) data traffic from the UPF 430 and N6 point-to-point tunnel (e.g., Unified Data Protocol (UDP) / IP) data traffic from the UPF 420. The NEF 410 can perform NIDD configuration procedures for a given user equipment in accordance with 3GPP specifications. For example, the NEF 410 can create an NIDD configuration context for a given user equipment using an application capability identifier, T8 Long Term Transaction Reference Identifier (TLTRI) information (e.g., an NIDD context identifier), a subscription permanent identifier (SUPI), and a generic public subscription identifier (GPSI). In particular, the NEF 410 can be pre-configured by storing 3GPP specification-compliant DNN·S-NSSAI information in the configuration table 500 that is mapped to an application capability identifier and, optionally, a user equipment identifier.

[0038] In some embodiments, the NEF 410 subscribes with the SMF 418 to monitor one or more of a plurality of PDU session events (e.g., as indicated in TS 29.528) for a user equipment 402 that sends an Nsmf_EventExposure_Subscribe service operation request to the SMF 418. In particular, the request may include user equipment GPSI and / or SUPI data received in an NIDD-configured call flow. Examples of the aforementioned plurality of PDU session events include, but are not limited to, i) user plane (UP) route change, ii) PDU session release procedure, iii) public land mobile network (PLMN) change, iv) UE IP address change, v) communication failure, and vi) PDU session establishment procedure.

[0039] After the NEF 410 subscribes with the SMF, the user equipment 402 establishes a PDU session with the NEF 410, UPF 420 (or UPF 430) using one of three modes: If the user equipment attempts to establish a session via the NIDD via the NEF 410 through the control plane, the communication plane 411 is utilized. In embodiments where the session is established via the NIDD via the NEF, the NEF 410 is notified during the PDU session establishment procedure through an Nnef_SMContext_Create Request message from the SMF (e.g., SMF 418 or 428). Alternatively, in embodiments where the session is established via the UPF (e.g., NIDD via UPF or IP data delivery via UPF), the NEF subscribes to the SMF to be notified of PDU session events.

[0040] The NEF 410 then updates the user equipment context information with the PDU session identifier and SMF identifier of the UE 402. In some embodiments, the NEF 410 may update a UE context data structure table as shown in FIG. 6. Notably, FIG. 6 illustrates an example UE context data table 600 that may include multiple entries, each corresponding to a user equipment identifier (see column 602). The UE context data table 600 further includes an application function identifier column 604, a PDU session type column 606, a context identifier column 608, a DNN·S-NSSAI column 610, a PDU session status column 612, an NIDD grant period column 614, an N6 tunnel point-to-point information column 616, and UE information 618 derived from the SMF event column. While FIG. 6 illustrates nine columns of the UE context data table 600, additional columns (or fewer columns) may be utilized without departing from the scope of the disclosed subject matter.

[0041] In some embodiments, the NEF 410 marks the data delivery path as NEF-via-NIDD (e.g., in column 606 of the UE context data table 600) to handle communication of MO and MT messages between the user equipment 402 and the application functions 406. In this manner, the NEF 410 processes MO and MT messages as defined in the 3GPP NIDD service (e.g., in accordance with TS 23.502 section 4.25). More specifically, the NEF 410 communicates data with the application functions 406 via an N33 interface / T8 interface facilitated by the unified interface 408.

[0042] In some embodiments, the NEF 410 receives a PDU session event change notification (e.g., PDU session establishment event / UP path change notification) from an SMF (e.g., SMF 428 of communication plane 412) indicating PDU session establishment for the NIDD via a UPF (e.g., UPF 420). In this scenario, the NEF 410 enables an N6 tunnel listener server (not shown) to accept MO messages from the UPF 420. Furthermore, the N6 tunnel listener server in the NEF 410 is enabled to transmit MT messages received from the AF 406 via the unified interface 408 and the UPF 420 to the user equipment 402. The NEF 410 then updates the user equipment's context information in its local context information database (e.g., updates the UE 402's entry in the UE context data table 600). For example, the NEF 410 may store PDU session information and user equipment information (e.g., the IPv6 prefix of the user equipment to be later used in MT messages from the application function 406) corresponding to the UE 402 in the UE context data table 600.

[0043] At this point, the NEF 410 may be configured to process the MO and MT messages received from the UE 402 and the AF 406, respectively, via the data delivery path. Specifically, the NEF 410 may receive the UE-generated MO message from the UPF 420 via the N6 point-to-point tunnel interface 422 (established by the UPF 420). The NEF 410 may then be configured to extract application payload information (e.g., transmission control protocol (TCP) / IP payload data) from the encapsulated UDP MO payload message received from the UPF 420 via the tunnel interface 422. Specifically, the NEF 410 may extract and / or obtain user equipment context information, including the source IP address and port identifier, from the encapsulated TCP packet. The NEF 410 may then extract the encapsulated TCP / IP payload created during the NIDD configuration procedure (e.g., using a context identifier obtained from the user equipment 402's context data information) that can be sent as an NIDD MO submit message to the application function 406 via a unified interface 408, e.g., a T8 interface / N33 interface.

[0044] In some embodiments, the NEF 410 is configured to receive an NIDD MT message from the application function 406 via the unified interface 408. The NEF 410 then constructs an N6-compliant message (e.g., a UDP packet) containing the TCP / IP payload of the MT message received from the application function 406. In particular, the new message is directed by the NEF 410 to the user equipment 402 using the user equipment IP address previously obtained and then encapsulated in the UDP packet. In particular, the NEF 410 sends the UDP packet to the UPF 420 via the N6 point-to-point tunnel interface 422. Upon receiving the UDP packet, the UPF 420 ultimately transmits the encapsulated MT message toward the user equipment 402 using the PDU session established via the control plane (e.g., the communication plane 412).

[0045] When the communication session is completed, the NEF 410 receives a PDU session release event from the SMF 428 and stops processing MT messages received from the application function 406 via the unified interface 408. In some embodiments, the NEF 410 may be configured to buffer MT messages until the PDU session is re-established.

[0046] As indicated above, the third communication plane 413 may be utilized to establish a data delivery path via the user plane. For example, the NEF 410 may be configured to receive a PDU session event message (e.g., a PDU session establishment message) when the user equipment 402 establishes an IP-type PDU session. In response, the NEF 410 stores the user equipment's IP address in user equipment context information (e.g., the UE context data table 600) and processes MO and MT messages communicated between the UE 402 and the application function 406. In particular, the NEF 410 receives MO IP data messages from the UPF 430 via the N6 interface. Subsequently, the NEF 410 obtains and / or extracts the application payload from the received TCP / IP packet and encapsulates the MO message in a T8 / N33 message that is sent to the application function 406 using the TLTRI (e.g., the NIDD configuration context identifier). Furthermore, the NEF 410 may receive MT messages from the application functions 406 via the unified interface 408 (e.g., T8 interface / N33 interface) and may then be configured to extract (e.g., decrypt) and / or retrieve the data payload from the encapsulated message. Notably, the NEF 410 constructs a TCP / IP payload message using the application payload and then transmits the message to the UE 402 via the UPF 430 using the user equipment IP address. Specifically, the UPF 430 routes the message towards the user equipment 402 via the user plane (e.g., communication plane 413) via the RAN-based user equipment IP address. Furthermore, upon receiving a PDU session release event message from the SMF 438, the NEF 410 may be configured to delete user equipment context information from a context information database (e.g., UE context data table 600) and then stop processing the communicated MO and MT messages.

[0047] 7 is a block diagram illustrating an example of a network node 700 configured to provide a unified interface configured to support a data delivery communication path between user equipment and application functions via a NEF. Network node 700 may represent any suitable entity or entities for performing aspects of supporting a unified interface. In some embodiments, node 700 may represent or include one or more 5GC network functions, e.g., a network publishing service, a network publishing function, etc. In some embodiments, network node 700 may represent or include a network gateway, a network proxy, an edge security device, or any associated computing device configured to host a NEF or similar function.

[0048] In some embodiments, the network node 700 or associated modules may be configured (e.g., via programming logic) to support a unified interface, which may be embodied as a T8 interface and / or an N33 interface supported by a hosted NEF. In particular, the unified interface implemented in the network node 700 is capable of conveying and supporting small, infrequent data communications directed from the UE and / or IoT device to the application function. Notably, in this scenario, the terminating application function is independent of and unaware of the underlying data communication path within the 5G network utilized by the user equipment and the network node 700. The disclosed solution further enables both non-IP-based and IP-based communications (e.g., NIDD data delivery and non-IP data delivery). As a result, the disclosed subject matter thereby enables seamless data services for user equipment or IoT devices moving between different data communication paths without impacting service. Furthermore, it should be noted that no customized interfaces are implemented with other network functions; i.e., the disclosed subject matter is based on existing 3GPP-defined interfaces.

[0049] 7, network node 700 may include one or more communication interfaces 702 for communicating messages over a communication environment, e.g., a home 5GC network. In some embodiments, communication interface(s) 702 may include a unified interface (e.g., a T8 interface / N33 interface) for communicating with one or more application functions in the manner described above. Communication interface 702 may further include any necessary interfaces (e.g., an N6 interface, an N6 point-to-point tunnel interface, etc.) utilized by a listener server established by the NEF to establish a data delivery path with the UPF.

[0050] The network node 700 may include a uniform interface manager 704. The uniform interface manager 704 may be any suitable entity (e.g., software executing via at least one processor of the network node) for performing one or more aspects of the disclosed data distribution techniques over a uniform interface. In some embodiments, the uniform interface manager 704 may include functionality for pre-configuring a configuration database (e.g., configuration table 500 of FIG. 5 ) stored in local data storage 706, for maintaining and updating a UE context database (e.g., UE context data table 600 of FIG. 6 ), and for executing algorithms necessary to implement and support the disclosed low-power and low-frequency modes of data communication between low-power UEs and AFs in 5G networks. For example, in some embodiments, the unified interface manager 704 may be configured to: i) receive a protocol data unit session event change notification message associated with the UE from a session management function; ii) establish a data distribution path between the UE and an application function via one of multiple data distribution planes across the NEF in response to the PDU session event change notification message; and iii) process messages communicated between the UE and the AF via any of multiple data distribution planes using a single unified interface supported by the NEF. In particular, the three distribution planes that the unified interface manager 704 can establish include a non-IP data distribution (NIDD)-based data communication path established in the control plane between the UE and the AF via the NEF, an NIDD-based data communication path established between the UE and the AF via the NEF and UPF communicatively connected using an N6 point-to-point tunnel, and an Internet Protocol (IP) data distribution-based data communication path between the UE and the AF communicatively connected via the NEF and UPF using the N6 interface.

[0051] In some embodiments, the network node 700 may access (e.g., read and write information to) the data storage 706. The data storage 706 may be any suitable entity (e.g., a computer-readable medium or memory) for storing various data. As indicated above, the data storage 706 may be configured to store multiple different databases, such as a configuration database (represented by the configuration table 500 shown in FIG. 5) or a UE context data structure (represented by the UE context data table 600 shown in FIG. 6) that enables data communication between the UE and the AF.

[0052] 8 illustrates an example process 800 for providing a unified interface configured to support small and infrequent data communications between user equipment and application functions via network publishing functionality. In some embodiments, the example process 800 described herein, or portions thereof, may be performed in or by network node 700, unified interface manager 704, and / or another module or node.

[0053] In step 802, a PDU session event change notification message associated with the UE is received by the NEF from a session management function (SMF). Notably, the NEF has previously subscribed to the SMF for PDU session events for a given UE (e.g., using the Nsmf_EventExposure_Subscribe service operation). When the UE triggers a PDU session event (such as a UP path change, a PDU session release, a PLMN change, a UE IP address change, a communication failure, or a PDU session establishment), the SMF notifies the NEF of the session event.

[0054] In step 804, in response to the PDU session event change notification message, the NEF establishes a data distribution path between the UE and the AF via one of multiple data distribution planes traversing the NEF. In some embodiments, the NEF determines which data distribution plane will serve the communication session between the UE and the AF. In some embodiments, the NEF is configured to establish an appropriate data distribution path based on the notification included in the PDU session event change notification message. For example, if the NEF is notified that the UE is attempting to establish a session via the control plane via the UPF, the NEF enables the N6 tunnel listener server to accept MO messages via the control plane from the UPF (e.g., NIDD data path via the control plane via the UPF). If the NEF is notified that the UE is attempting to establish a session via the user plane via the UPF, the NEF enables the N6 listener server to receive MO messages via the user plane from the UPF (e.g., non-NIDD data path via the user plane via the UPF). Additionally, the NEF may be configured to directly receive MO messages from the UE via the control plane (e.g., NIDD data path via the control plane via the NEF).

[0055] In block 806, messages communicated between the UE and the AF via any of multiple data distribution planes are processed by the NEF using a single unified interface supported by the NEF. In some embodiments, the NEF is configured to process MO and MT messages communicated between the UE and the AF. In particular, regardless of the data distribution path utilized (e.g., NIDD data path via the control plane via the NEF, NIDD data path via the control plane via the UPF, or non-IP data distribution data path over the user plane via the UPF), the NEF is configured to utilize a single unified interface to provide MO messages to the AF and receive MT messages from the AF. In some embodiments, the unified interface may be a T8 interface / N33 interface.

[0056] It will be understood that process 800 is for illustrative purposes and that different and / or additional operations may be used. It will also be understood that the various operations described herein may occur in a different order or sequence.

[0057] It should be noted that the network node 700, the unified interface manager 704, and / or the functionality described herein (e.g., as shown in FIG. 7) may constitute special-purpose computing devices. Furthermore, the node 700, the unified interface manager 704, and / or the functionality described herein may improve the technical field of data communications in 5G networks. Notably, the disclosed subject matter may provide a unified interface available by the NEF to establish any number of data distribution paths that may be used by the UE and the AF. Notably, the AF is independent of the underlying data communication path used by the NEF and its unified interface in the 5G network. Furthermore, the unified interface enables seamless data services, permitting UE movement between data distribution paths without impacting service.

[0058] The disclosure of each of the following references is incorporated herein by reference in its entirety to the extent not inconsistent with this specification and to the extent that it supplements, explains, provides background for, or teaches the methods, techniques, and / or systems employed herein.

[0059] It will be understood that various details of the presently disclosed subject matter can be changed without departing from the scope of the presently disclosed subject matter. Further, the foregoing description is for purposes of illustration only, and not for purposes of limitation.

[0060] References 1. 3GPP TS23.501-System architecture for the 5G System(5GS) 2. 3GPP TS23.502-Procedures for the 5G System(5GS) 3. 3GPP TS29.122-T8 reference point for Northbound APIs 4. 3GPP TS29.522-N33 reference point for Northbound APIs 5. 3GPP TS23.682-Architecture enhancements to facilitate communications with packet data networks and applications

Claims

1. 1. A method for providing a unified interface configured to support communication between a user equipment (UE) and an application function (AF) via a network exposure function (NEF), comprising: The NEF receives, from a session management function (SMF), a protocol data unit (PDU) session event change notification message associated with the UE; The NEF establishes a data delivery path between the UE and an application function (AF) via one of a plurality of data delivery planes across the NEF in response to the PDU session event change notification message; The NEF processes messages communicated between the UE and the AF via any of the plurality of data distribution planes using a single unified interface supported by the NEF; The plurality of data distribution planes include a non-IP data distribution (NIDD)-based data communication path established in a control plane between the UE and the AF via the NEF, a NIDD-based data communication path established between the UE and the AF via the NEF and a UPF communicatively connected using an N6 point-to-point tunnel, and an Internet Protocol (IP) data distribution-based data communication path between the UE and the AF communicatively connected via the NEF and the UPF using an N6 interface; The method, wherein the NEF is configured to start a listening server that monitors packet traffic from a UPF based on a UPF in a data delivery path of the PDU session event change notification message in response to receiving the PDU session event change notification message.

2. The method of claim 1 , wherein the UE comprises a low-power Internet of Things (IoT) device.

3. The method according to claim 1 or 2, wherein the single unified interface includes a T8 interface and / or an N33 interface.

4. The method of any one of claims 1 to 3, wherein the NEF is configured to switch between the multiple data distribution planes while maintaining connectivity for the UE.

5. The method of any one of claims 1 to 4, wherein the NEF functions as a PDU session anchor during use of each of the multiple data distribution planes.

6. 1. A system for providing a unified interface configured to support communication between a user equipment (UE) and an application function (AF) via a network exposure function (NEF), the system comprising: a network node, the network node comprising: at least one processor; a memory, wherein the memory and the at least one processor belong to a uniform interface device configured to host a NEF, and the network node further comprises: a unified interface manager, the unified interface manager being stored in the memory of the NEF and being configured, when executed by the at least one processor, to receive from a session management function (SMF) a protocol data unit (PDU) session event change notification message associated with a UE; and in response to the PDU session event change notification message, to establish a data delivery path between the UE and an application function (AF) via one of a plurality of data delivery planes traversing the NEF, the plurality of data delivery planes being a non-IP data delivery path established in a control plane between the UE and the AF via the NEF. a NIDD-based data communication path established between the UE and the AF via the NEF and the UPF communicatively connected using an N6 point-to-point tunnel; and an Internet Protocol (IP) data delivery-based data communication path between the UE and the AF communicatively connected via the NEF and the UPF using an N6 interface, wherein the NEF is configured to activate a listening server that monitors packet traffic from the UPF based on the UPF in the data delivery path of the PDU session event change notification message in response to receiving the PDU session event change notification message; The system, wherein the unified interface manager, when executed by the at least one processor, is further configured to process messages communicated between the UE and the AF via any of the multiple data delivery planes using a single unified interface supported by the NEF.

7. The system of claim 6 , wherein the UE comprises a low-power Internet of Things (IoT) device.

8. The system according to claim 6 or 7, wherein the single unified interface comprises a T8 interface and / or an N33 interface.

9. The system according to any one of claims 6 to 8, wherein the NEF is configured to switch between the multiple data distribution planes while maintaining connectivity for the UE.

10. The system of any one of claims 6 to 9, wherein the NEF functions as a PDU session anchor during use of each of the plurality of data distribution planes.

11. A program for causing a computer to execute the method according to any one of claims 1 to 5.

Images