Methods, systems, and computer-readable media for providing a unified interface configured to support infrequent data communication via network exposure functions

Abstract

Methods, systems, and computer-readable media 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). One method includes receiving, by the NEF from a session management function (SMF), a protocol data unit (PDU) session event change notification message associated with the UE, establishing, by the NEF in response to the PDU session event change notification message, a data delivery path between the UE and an application function (AF) via one of a plurality of data delivery planes that pass through the NEF, and processing, by the NEF, messages communicated between the UE and the AF over any of the plurality of data delivery planes using a single unified interface supported by the NEF.

Description

[0001] Priority Statement

[0002] This application claims priority to U.S. Patent Application Serial No. 17 / 110,255, filed December 2, 2020, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] The topics described herein relate to improving data communications in fifth-generation (5G) telecommunications networks. More specifically, the topics described herein relate to methods, systems, and computer-readable media for providing a unified interface configured to support small and infrequent data communications between user equipment and application functions via network exposed functions. Background Technology

[0004] Currently, 5G telecommunications networks typically require infrequent communication of small amounts of data between Low Power User Equipment (UE) and Application Functions (AF). Specifically, these small, infrequent communications are used for cellular-based communication between Internet of Things (IoT) devices and the AF. This communication approach enables IoT use cases based on Low Power Wide Area (LWPA), where power-constrained UE devices can utilize both the 5G control plane and the 5G data plane for data transmission. Typically, 3GPP provides different methods and / or interfaces to facilitate infrequent communication of small amounts of data, such as using Internet Protocol (IP) data delivery via the N6 interface through the user plane or using Non-IP Data Delivery (NIDD) through the control plane. While several different paths exist in 5G communication networks for delivering small, infrequent data, some technical difficulties can arise when the AF needs to support different AF communication methods. For example, problems may occur when a roaming network is configured to support only IP data delivery and not NIDD. Difficulties may also arise in localized roaming scenarios where the visited network supports NIDD via User Plane Function (UPF) and the UE's home network supports NIDD via Network Exposure Function (NEF). Furthermore, AF issues may also occur when the UE is used across multiple network slices and each slice can support different deployment models (e.g., slices equipped with NEF, slices without NEF, or slices without NEF that only support IP data delivery via UPF).

[0005] Therefore, there is a need for improved methods and systems to provide a unified interface configured to support infrequent communications via network-exposed functions or services. Summary of the Invention

[0006] Methods, systems, and computer-readable media 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). One method includes the NEF receiving a Protocol Data Unit (PDU) session event change notification message associated with the UE from a Session Management Function (SMF); the NEF, in response to the PDU session event change notification message, establishing a data delivery path between the UE and the Application Function (AF) via one of a plurality of data delivery planes traversing the NEF; and the NEF processing messages transmitted between the UE and the AF via any of the plurality of data delivery planes using a single unified interface supported by the NEF.

[0007] According to aspects of the subject matter described herein, a method comprising a non-IP data delivery (NIDD) based data communication path established in the control plane between the UE and AF via the NEF, a NIDD based data communication path established between the UE and AF via the NEF and UPF using N6 point-to-point tunnel communication connections, and an Internet Protocol (IP) based data communication path between the UE and AF via the NEF and UPF communication connections using N6 interfaces.

[0008] According to aspects of the subject matter described herein, one method is provided, wherein the UE includes a low-power Internet of Things (IoT) device.

[0009] According to aspects of the subject matter described herein, one method is provided, wherein the single unified interface includes a T8 interface and / or an N33 interface.

[0010] According to aspects of the subject matter described herein, a method wherein the NEF is configured to switch between the plurality of data delivery planes while maintaining the attachment of the UE.

[0011] According to aspects of the subject matter described herein, one method is provided in which the NEF is configured to: in response to receiving the PDU session event change notification message, establish a listening server to monitor packet traffic from the UPF.

[0012] According to aspects of the subject matter described herein, a method is provided in which the NEF acts as a PDU session anchor during use of each of the plurality of data delivery planes. An example 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) includes a network node comprising at least one processor and a memory, wherein the memory and the at least one processor belong to a unified interface device configured to host the NEF. The network node also includes a unified interface manager stored in the memory of the NEF and, when executed by the at least one processor, configured to: receive a Protocol Data Unit (PDU) session event change notification message associated with the UE from a Session Management Function (SMF); in response to the PDU session event change notification message, establish a data delivery path between the UE and the Application Function (AF) via one of the plurality of data delivery planes traversing the NEF; and process messages transmitted between the UE and the AF via any of the plurality of data delivery planes using a single unified interface supported by the NEF.

[0013] According to aspects of the subject matter described herein, a system wherein the plurality of data delivery planes includes a non-IP data delivery (NIDD) based data communication path established in the control plane between the UE and AF via the NEF, a NIDD based data communication path established between the UE and AF via the NEF and UPF using N6 point-to-point tunnel communication connections, and an Internet Protocol (IP) based data communication path between the UE and AF via the NEF and UPF communication connections using N6 interfaces.

[0014] According to aspects of the subject matter described herein, a system wherein the UE includes a low-power Internet of Things (IoT) device.

[0015] According to aspects of the subject matter described herein, a system wherein the single unified interface includes a T8 interface and / or an N33 interface.

[0016] According to aspects of the subject matter described herein, a system wherein the NEF is configured to switch between the plurality of data delivery planes while maintaining the attachment of the UE.

[0017] According to aspects of the subject matter described herein, a system wherein the NEF is configured to: in response to receiving the PDU session event change notification message, establish a listening server to monitor packet traffic from the UPF.

[0018] According to aspects of the subject matter described herein, a system in which the NEF acts as a PDU session anchor during use in each of the plurality of data delivery planes.

[0019] An example non-transitory computer-readable medium includes computer-executable instructions implemented therein, which, when executed by at least one processor of at least one computer, cause the at least one computer to perform the following steps: receiving a Protocol Data Unit (PDU) session event change notification message associated with a UE from a Session Management Function (SMF) by the NEF; establishing a data delivery path between the UE and an Application Function (AF) via one of a plurality of data delivery planes traversing the NEF in response to the PDU session event change notification message by the NEF; and processing messages transmitted between the UE and the AF via any of the plurality of data delivery planes by the NEF using a single unified interface supported by the NEF.

[0020] The subjects described herein can be implemented using hardware, software, firmware, or any combination thereof. Therefore, as used herein, the terms “function,” “node,” or “module” refer to hardware used to implement the described features, which may also include software and / or firmware components. In one example implementation, the subjects described herein can be implemented using a computer-readable medium having computer-executable instructions stored thereon, which, when executed by a computer’s processor, control the computer to perform steps. Example computer-readable media suitable for implementing the subjects described herein include non-transitory computer-readable media, such as disk storage devices, on-chip memory devices, programmable logic devices, and application-specific integrated circuits (ASICs). Furthermore, computer-readable media implementing the subjects described herein can reside on a single device or computing platform, or can be distributed across multiple devices or computing platforms. Attached Figure Description

[0021] The subject matter described herein will now be explained with reference to the accompanying drawings, in which:

[0022] Figure 1 It is a logical block diagram of the control plane configured to provide a non-IP data delivery (NIDD) path between user equipment (UE) and application functions via NEF;

[0023] Figure 2 It is a logical block diagram of the control plane configured to provide a non-IP data delivery (NIDD) path between the UE and application functions via the User Plane Function (UPF) and N6 Point-to-Point (PTP) tunnels;

[0024] Figure 3It is a logical block diagram of the user plane that provides an IP data delivery path between the UE and application functions via UPF;

[0025] Figure 4 It is a logical block diagram depicting an aggregated data delivery system configured to establish multiple data delivery paths between the UE and AF via NEF and an associated unified interface;

[0026] Figure 5 This is an example configuration table used to map NEF listening servers and ports to the destination AF;

[0027] Figure 6 It is an example database table maintained at NEF for storing context information of communication sessions between UE and AF;

[0028] Figure 7 This is a block diagram illustrating an example network node configured to host NEF and the Unified Interface Manager; and

[0029] Figure 8 This is a flowchart illustrating an example process for providing a unified interface configured to support infrequent communication via network-exposed functions or services. Detailed Implementation

[0030] 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. Where possible, the same reference numerals will be used throughout the drawings to refer to the same or similar parts.

[0031] In 5G networks, small and infrequent data communication between user equipment (UE) and application functions is primarily used for low-power IoT devices or other devices with power constraints or limitations. Notably, for low-power or power-constrained IoT devices operating in 5G networks, three modes or interfaces exist to facilitate small and infrequent data communication between UE and application functions. For example, the first mode of data communication can be achieved via the 5G system control plane through a NEF using an N33 interface and / or a T8 interface for non-IP data delivery (NIDD) based data transmission between UE and application functions. The second mode of data communication can be achieved via the 5G system control plane through a UPF using an N6 point-to-point tunnel interface for NIDD-based data communication between UE and application functions. Furthermore, the third mode of data communication can be achieved via the 5G system user plane through a UPF using an N6 interface for IP data delivery between UE and application functions. These three different data delivery options are illustrated in [the diagram]. Figures 1-3 The details are described below.

[0032] Figure 1The NIDD data path between user equipment and application functions via the NEF through the 5G control plane is depicted. Specifically, Figure 1 A 5G system 100 is shown, which includes user equipment 102, a control plane 104, and application functions 106. Furthermore, Figure 1 The control plane 104 is illustrated as including a Radio Access Network (RAN) 108, Access and Mobility Management Function (AMF) 110, Session Management Function (SMF) 112, Network Exposure Function (NEF) 114, and Unified Data Management Function (UDM) 116, which together are responsible for establishing a data communication path between User Equipment 102 and Application Function 106 on the control plane. Notably, a Protocol Data Unit (PDU) session establishment process occurs between User Equipment 102 and SMF 112. During the session establishment process, SMF 112 acquires the NEF identity (e.g., corresponding to NEF 114) as part of the subscription data received from UDM 116. Once the NEF identity information is received by SMF 112, an SMF-NEF connection establishment process is performed. Specifically, a NIDD (Mobile Originated) message communication path is established between User Equipment 102 and Application Function 106. Similarly, a NIDD mobile terminated (MT) message communication path is established between application function 106 and user equipment 102. To facilitate one or more communication paths, an N33 / T8 interface is established between application function 106 and NEF 114. Once the communication path is established through control plane 104, user equipment 102 and application function 106 can transmit small and infrequent data through 5G system 100. Specifically, NEF-based NIDD data communication provides an API-based interface (i.e., T8 / N33 interface) to application function 106 for both MO message communication and MT message communication between user equipment 102 and application function 106 through control plane 104. Therefore, in this scenario, NEF 114 serves as and acts as the PDU session anchor point for the data delivery path.

[0033] Figure 2 The NIDD data path between user equipment and application functions via the UPF through the 5G control plane is depicted. Specifically, Figure 2 A 5G system 200 is shown, which includes user equipment 202, a control plane 204, and application functions 206. Furthermore, Figure 2The control plane 204 is illustrated as including RAN 208, AMF 210, SMF 212, and UPF 220, which are collectively responsible for establishing data communication paths. Notably, data communication using NIDD via the UPF on the control plane 204 is initiated by a PDU session event procedure (e.g., a PDU session establishment procedure) between User Equipment 202 and SMF 212. During this procedure, SMF 212 selects a UPF (e.g., UPF 220) and performs an N4 session establishment procedure (i.e., between SMF 212 and UPF 220). Subsequently, the UPF establishes an N6 point-to-point tunnel 205 between UPF 220 and Application Function 206 to support unstructured NIDD data communication in the 5G system 200. Specifically, the UPF-based NIDD provides an N6 point-to-point tunnel interface for MO and MT message communication between user equipment 202 and application function 206 via control plane 204 (between UPF 220 and application function 206). Therefore, in this scenario, UPF 220 is used as and acts as the PDU session anchor point for the data delivery path.

[0034] Figure 3 This describes the IP data delivery path between user equipment and application functions via the UPF through the 5G user plane. Specifically, Figure 3 A 5G system 300 is shown, which includes user equipment 302, user plane 304, and application functions 306. Furthermore, Figure 3 The user plane 304 is illustrated as including RAN 308, SMF 312, and UPF 320, which are collectively responsible for establishing data communication paths on the user plane. Notably, data communication on the user plane 304 via IP data delivery through the UPF is initiated by a PDU session event procedure (e.g., a PDU session establishment procedure) between user equipment 302 and SMF 312. During this procedure, SMF 312 selects UPF 230 and performs an N4 session establishment procedure (i.e., between SMF 312 and UPF 320). Data communication on the user plane 304 then proceeds. It is noteworthy that UPF-based IP data delivery provides an N6 interface (i.e., between UPF 320 and application function 306) for MO and MT message communication between user equipment 302 and application function 306 via the 5G data plane (i.e., user plane 304). Therefore, in this scenario, UPF 320 acts as the PDU session anchor point for the data delivery path.

[0035] Typically, there are several scenarios where application functionality will need to support all three of the aforementioned methods for application function communication. Example scenarios include user equipment entering a roaming network that only supports regular IP data delivery and is not configured to support NIDD data delivery, or user equipment leaving a home network that supports NIDD via NEF and entering a visited network that only supports NIDD via UPF in a local routing roaming scenario. Another example is if user equipment is used across multiple network slices, where each slice supports a different deployment model (e.g., the first slice is equipped with NEF, and adjacent slices are not equipped with NEF or only support IP data delivery via UPF without NEF). Therefore, it would be advantageous to configure the application function to support multiple interfaces for multiple different data delivery paths. Therefore, the disclosed subject matter relates to NEF elements equipped with a unified interface configured to internally support: i) an N33 / T8 interface using control plane data transmission (i.e., NIDD via NEF), ii) an N6 point-to-point tunnel interface using control plane data transmission (i.e., NIDD via UPF), and iii) an N6-based interface (i.e., IP data delivery) specific to IoT use cases utilizing user plane data transmission.

[0036] It should be noted that an AF configured to support only the N6 interface (i.e., excluding NEF interface capabilities) is significantly limited and prevents application functions from utilizing many exposed services provided by NEF. Specifically, an AF limited in this way will be unable to utilize valuable services provided by NEF, including but not limited to: i) monitoring IoT device status via the MONTE service, ii) AF traffic impact services for edge routing use cases, iii) charging third-party service providers (i.e., sponsored data connectivity), iv) setting network parameters (e.g., sleep timers, etc.), and v) setting application function sessions with the required Quality of Service (QoS), etc.

[0037] Instead, the disclosed subject is configured to utilize a single unified interface at the application function level via NEF for all three of the aforementioned deployment models. Specifically, NEF is configured to track the current data delivery path (e.g., PDU session path) utilized by the user equipment and to use a single T8 / N33 interface pointing to the application function's destination to accommodate any path switching, thereby enabling small and infrequent data communications between the user equipment and the application function.

[0038] Figure 4A logical block diagram of a 5G communication network 400 is depicted. Notably, network 400 includes an aggregated unified interface system 401 that facilitates communication paths between user equipment 402 and application functions 406. Specifically, system 401 includes three communication planes 411-413, and a unified interface 408 that can be used to provide small data delivery communication paths between user equipment 402 (e.g., low-power IoT devices) and application functions 406. Although Figure 4 Multiple instances of the same network elements existing on different communication planes are shown (e.g., UPF 420 and UPF 430, RAN 414, 424, 434, etc.), but Figure 4 Since it is a logic diagram, the network elements represented here can be implemented as a single network element configured to function on each of the communication planes shown.

[0039] In some embodiments, the communication plane 411 includes a control plane that establishes NIDD data paths between user equipment 402 and application function 406 via NEF 410 (according to 3GPP standards). It is worth noting that NEF 410 can be used to establish a communication connection with unified interface 408 to transmit MO and MT message data communication between user equipment 402 and application function 406.

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

[0041] Specifically, NEF 410 acts as a PDU session anchor point via communication plane 411 and communication planes 412-413 as described below.

[0042] In some embodiments, system 401 further includes a second communication plane 412, which includes a control plane providing a NIDD data path between user equipment 402 and application function 406. Specifically, communication plane 412 provides a NIDD data path including an N6 point-to-point tunnel interface 422 via a UPF 420 (according to the 3GPP standard). Specifically, an N6 point-to-point tunnel interface 422 is established between the UPF 420 and a NEF 410 located in communication plane 411. Therefore, MO and MT messaging communications between user equipment 402 and application function 406 traverse communication plane 412 using the point-to-point tunnel interface 422, the NEF 410, and the unified interface 408.

[0043] Similarly, system 401 includes a third communication plane 413, which includes a user plane (or data plane) providing an IP data delivery path between user equipment 402 and application function 406. Specifically, communication plane 413 enables a UPF-based IP data path (according to the 3GPP standard) via an N6 interface terminating at NEF 410 located in communication plane 411. It is worth noting that, as... Figure 4 As shown, MO and MT messaging communication between user equipment 402 and application function 406 is facilitated via NEF 410 and unified interface 408.

[0044] As described above, the disclosed subject supports a unified interface 408, which enables communication between the NEF 410 and application function 406 in the first communication plane 411. It is worth noting that the NEF 410 is equipped with an AF configuration table 500 (e.g., Figure 5 As shown in the diagram, the AF configuration table 500 maps the AF and its corresponding IP address, Data Network Name (DNN) information, and / or Single Network Slice Selection Auxiliary Information (NSSAI) identifier data to the NEF's N6 listening port. Specifically, Figure 5 Configuration table 500 is depicted, which includes an application function identifier column 502, a DNN column 504, an S-NSSAI column 506, a NEF listening server IP address and port column 508, and a server type column 510. The information stored in configuration table 500 can be used at NEF 410 to start listening servers that monitor 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 via the N6 interface (e.g., IP data delivery) or the N6 point-to-point tunnel interface (e.g., via UPF 420 and NIDD of tunnel interface 422).

[0045] After being pre-configured, the NEF 410 uses the configuration details (not shown) contained in Table 500 to start the listening server to listen for incoming N6 (TCP / IP) data traffic from the UPF 430 and N6 point-to-point tunneled (e.g., Unified Data Protocol (UDP) / IP) data traffic from the UPF 420. The NEF 410 can perform the NIDD configuration procedure for a given user equipment according to one or more 3GPP specifications. For example, the NEF 410 can create an NIDD configuration context for a given user equipment using the application function identifier, T8 Long-Term Transaction Reference Identifier (TLTRI) information (e.g., NIDD context identifier), Subscription Persistent Identifier (SUPI), and General Public Subscription Identifier (GPSI). Notably, the NEF 410 can be pre-configured by storing DNN and S-NSSAI information in configuration Table 500 according to 3GPP specifications mapped to the application function identifier and, optionally, the user equipment identifier.

[0046] In some embodiments, NEF 410 subscribes to SMF 418 by sending an Nsmf_EventExposure_Subscribe service operation request to SMF 418 in order to monitor one or more of a plurality of PDU session events concerning User Equipment 402 (e.g., as indicated in TS 29.528). It is noteworthy that this request may include User Equipment GPSI and / or SUPI data received in the NIDD configuration call stream. Examples of the aforementioned plurality of PDU session events include, but are not limited to: i) User Plane (UP) path 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.

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

[0048] Subsequently, for UE 402, NEF 410 updates the user equipment context information using the PDU session identifier and SMF identifier. In some embodiments, NEF 410 may update, for example... Figure 6 The UE context data structure table is shown below. It is worth noting that... Figure 6 The illustration shows 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 also includes an application function identifier column 604, a PDU session type column 606, a context identifier column 608, DNN and S-NSSAI columns 610, a PDU session state column 612, a NIDD authorized duration column 614, an N6 tunnel point-to-point information column 616, and a UE information column 618 derived from SMF events. Although... Figure 6 Nine columns in UE Context Data Table 600 are described, but additional columns (or fewer columns) may be used without departing from the scope of the disclosed subject matter.

[0049] In some embodiments, NEF 410 (e.g., in column 606 of UE context data table 600) marks the data delivery path as via NEF NIDD for handling MO and MT message communication between UE 402 and application function 406. Therefore, NEF 410 handles MO and MT messages as defined by the 3GPP NIDD service (e.g., as specified in section 4.25 of TS 23.502). More specifically, NEF 410 transmits data with application function 406 via the N33 / T8 interface facilitated by unified interface 408.

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

[0051] At this point, NEF 410 can be configured to process MO and MT messages received from UE 402 and AF 406 respectively via the data delivery path. Specifically, NEF 410 can receive UE-generated MO messages from UPF 420 via N6 point-to-point tunnel interface 422 (established by UPF 420). Then, NEF 410 can be configured to extract application payload information (e.g., Transmission Control Protocol (TCP) / IP payload data) from encapsulated UDP MO payload messages received from UPF 420 via tunnel interface 422. Specifically, NEF 410 can extract and / or retrieve user equipment context information, including source IP address and port identifier, from encapsulated TCP packets. Subsequently, NEF 410 can extract the encapsulated TCP / IP payload, which can be sent as an NIDD MO commit message to application function 406 via unified interface 408 (e.g., T8 / N33 interface) (e.g., using a context identifier retrieved from context data information of user equipment 402 created during the NIDD configuration process).

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

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

[0054] As described above, a data delivery path can be established via the user plane using the third communication plane 413. For example, NEF 410 can be configured to receive PDU session event messages (e.g., PDU session establishment messages) when user equipment 402 establishes an IP-type PDU session. In response, NEF 410 stores the user equipment's IP address in user equipment context information (e.g., UE context data table 600) and processes MO and MT messages transmitted between UE 402 and application function 406. Specifically, NEF 410 receives MO IP data messages from UPF 430 via the N6 interface. NEF 410 then retrieves and / or extracts the application payload from the received TCP / IP packets and encapsulates the MO message in a T8 / N33 message sent to application function 406 using TLTRI (e.g., NIDD configuration context identifier). Furthermore, NEF 410 can receive MT messages from application function 406 via unified interface 408 (e.g., T8 / N33 interface) and can be configured to subsequently extract (e.g., decrypt) and / or retrieve data payloads from the encapsulated messages. Notably, NEF 410 uses the application payload to construct a TCP / IP payload message and then sends the message to UE 402 via UPF 430 using the UE IP address. Specifically, UPF 430 routes the message to UE 402 via the user plane (e.g., communication plane 413) using the RAN-based UE IP address. Additionally, NEF 410 can be configured to remove UE context information from the context information database (e.g., UE context data table 600) after receiving a PDU session release event message from SMF 438 and subsequently cease processing the delivered MO and MT messages.

[0055] Figure 7 This is a block diagram illustrating an example network node 700 configured to provide a unified interface for data delivery communication paths between user equipment and application functions configured to support NEF. Network node 700 can represent any suitable one or more entities for performing various aspects of supporting the unified interface. In some embodiments, node 700 can represent or include one or more 5GC network functions, such as a network exposure service, network exposure function, etc. In some embodiments, network node 700 can represent or include a network gateway, network proxy, edge security device, or any associated computing device configured to host NEF or similar functions.

[0056] In some embodiments, network node 700 or related modules may (e.g., via programming logic) be configured to support a unified interface, which may be implemented as a T8 interface and / or N33 interface supported by the managed NEF. Specifically, the unified interface implemented at network node 700 can deliver and support small, infrequent data communications from UEs and / or IoT devices directed to application functions. It is noteworthy that in this scenario, the terminating application function is agnostic and unaware of the underlying data communication path in the 5G network being utilized by the user equipment and network node 700. The disclosed solution also enables communication based on both non-IP and IP (e.g., NIDD and non-IP data delivery). Therefore, the disclosed subject matter allows for seamless data services for user equipment or IoT devices moving between different data communication paths without any service impact. It should also be noted that no custom interfaces are implemented at other network functions; that is, the disclosed subject matter is based on existing 3GPP-defined interfaces.

[0057] Reference Figure 7 Network node 700 may include one or more communication interfaces 702 for transmitting messages via a communication environment (e.g., a home 5GC network). In some embodiments, the communication interfaces(s) 702 may include a unified interface (e.g., a T8 / N33 interface) for communicating with one or more application functions in the manner described above. Furthermore, the communication interface 702 may also include necessary interfaces (e.g., an N6 interface, an N6 point-to-point tunnel interface, etc.) established by a listener server created by the NEF for establishing a data delivery path with the UPF.

[0058] Network node 700 may include a unified interface manager 704. The unified interface manager 704 may be any suitable entity (e.g., software executing on at least one processor of the network node) for performing one or more aspects of the disclosed data delivery technology via the unified interface. In some embodiments, the unified interface manager 704 may include a configuration database (e.g., for pre-configuring data stored in a local data storage device 706) for pre-configuring data. Figure 5 Configuration table 500), maintaining and updating the UE context database (e.g., Figure 6The unified interface manager 704 includes the UE context data table 600 and the functions to execute necessary algorithms to perform and support the disclosed patterns of small and infrequent data communication between low-power UEs and application functions in a 5G network. For example, in some embodiments, the unified interface manager 704 may be configured to: i) receive a Protocol Data Unit (PDU) session event change notification message associated with the UE from a session management function; ii) in response to the PDU session event change notification message, establish a data delivery path between the UE and the application function via one of a plurality of data delivery planes traversing the NEF; and iii) use a single unified interface supported by the NEF to process messages passed between the UE and the AF via any of the plurality of data delivery planes. In particular, the three delivery planes that the unified interface manager 704 may establish include a non-IP data delivery (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 between the UE and the AF via the NEF and UPF using N6 point-to-point tunnel communication connections, and an Internet Protocol (IP) based data communication path between the UE and the AF via the NEF and UPF communication connections using the N6 interface.

[0059] In some embodiments, network node 700 can access data storage device 706 (e.g., read information from data storage device 706 and / or write information to data storage device 706). Data storage device 706 can be any suitable entity for storing various types of data (e.g., computer-readable media or memory). As described above, data storage device 706 can be configured to store multiple different databases, such as a configuration database (by...). Figure 5 The configuration table 500 shown indicates) or the UE context data structure that enables data communication between the UE and AF (by... Figure 6 The UE context data table 600 shown in the figure represents this.

[0060] Figure 8 This is a diagram illustrating an example process 800 for providing a unified interface configured to support small, infrequent data communication between user equipment and application functions via network exposure capabilities. In some embodiments, the example process 800 or a portion thereof described herein may be executed at or by network node 700, unified interface manager 704 and / or another module or node.

[0061] In step 802, the NEF receives a PDU session event change notification message associated with the UE from the Session Management Function (SMF). It is worth noting that the NEF has previously subscribed to the SMF for PDU session events related to a given UE (e.g., using the Nsmf_EventExposure_Subscribe service operation). When the UE triggers a PDU session event (e.g., UP path change, PDU session release, PLMN change, UE IP address change, communication failure, and PDU session establishment), the SMF will notify the NEF of the session event.

[0062] In step 804, in response to a PDU session event change notification message, the NEF establishes a data delivery path between the UE and the AF via one of a plurality of data delivery planes traversing the NEF. In some embodiments, the NEF determines the data delivery plane in which to serve the communication session between the UE and the AF. In some embodiments, the NEF is configured to establish an appropriate data delivery path based on a 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 UPF through the control plane, the NEF will enable the N6 tunnel listener server to accept MO messages from the UPF via the control plane (e.g., via the NIDD data path through the control plane via the UPF). If the NEF is notified that the UE is attempting to establish a session via the UPF through the user plane, the NEF will enable the N6 listener server to receive MO messages from the UPF via the user plane (e.g., via the non-IP data delivery data path through the user plane via the UPF). Furthermore, the NEF may also be configured to receive the MO messages themselves directly from the UE via the control plane (e.g., via the NIDD data path through the control plane via the NEF).

[0063] In block 806, the NEF uses a single unified interface supported by the NEF to process messages transmitted between the UE and AF via any of the multiple data delivery planes. In some embodiments, the NEF is configured to process MO messages and MT messages transmitted between the UE and AF. Notably, regardless of the data delivery path utilized (e.g., a NIDD data path via the NEF through the control plane, a NIDD data path via the UPF through the control plane, or a non-IP data delivery data path via the UPF through the user plane), 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 / N33 interface.

[0064] It should be understood that processing 800 is for illustrative purposes and different and / or additional actions may be used. It should also be understood that the various actions described herein may occur in different orders or sequences.

[0065] It should be noted that the descriptions in this article (e.g., such as...) Figure 7 The network node 700, unified interface manager 704, and / or functions shown herein can constitute a dedicated computing device. Furthermore, the node 700, unified interface manager 704, and / or functions described herein can improve the technical field of data communication in 5G networks. It is noteworthy that the disclosed subject matter can provide a unified interface that can be used by the NEF to establish any number of data delivery paths that can be used by the UE and AF. It is also noteworthy that the AF is unaware of the underlying data communication paths used by the NEF and its unified interface in the 5G network. Moreover, the unified interface allows for seamless data services that allow the UE to move between data delivery paths without any service disruption.

[0066] The public information disclosed in each of the following references is incorporated herein by reference in its entirety, without contradicting this document, and to the extent that it supplements, explains, provides background or teaching on the methods, techniques and / or systems used herein.

[0067] It should be understood that various details of the currently disclosed subject matter can be changed without departing from the scope of the currently disclosed subject matter. Furthermore, the foregoing description is for illustrative purposes only and not for limiting purposes.

[0068] References

[0069] 1.3GPP TS 23.501-System architecture for the 5G System(5GS)

[0070] 2.3GPP TS 23.502-Procedures for the 5G System(5GS)

[0071] 3.3GPP TS 29.122-T8 reference point for Northbound APIs

[0072] 4.3GPP TS 29.522-N33 reference point for Northbound APIs

[0073] 5.3GPP TS 23.682-Architecture enhancements tofacilitatecommunications with packet data networks and applications

Claims

1. A method for providing a unified interface, the unified interface being configured to support communication between a user equipment (UE) and an application function (AF) via a network exposure function (NEF), the method comprising: The NEF receives session event change notification messages for Protocol Data Units (PDUs) associated with the UE from the Session Management Function (SMF); In response to a PDU session event change notification message, the NEF establishes a data delivery path between the UE and the application function (AF) via one of a plurality of data delivery planes traversing the NEF. These plurality of data delivery planes include a non-IP data delivery (NIDD) based data communication path established in the control plane between the UE and AF via the NEF, an NIDD-based data communication path established between the UE and AF via the NEF and UPF using an N6 point-to-point tunnel communication connection, and an Internet Protocol (IP) based data communication path between the UE and AF via the NEF and UPF communication connection using an N6 interface. The NEF is configured to, in response to receiving the PDU session event change notification message and based on the UPF in the data delivery path of the PDU session event change notification message, initiate a listening server to monitor packet traffic from the UPF. as well as The NEF uses a single unified interface supported by the NEF to process messages passed between the UE and AF through any of the multiple data delivery planes.

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 claim 2, wherein the single unified interface includes a T8 interface and / or an N33 interface.

4. The method of claim 1 or claim 2, wherein the NEF is configured to switch between the plurality of data delivery planes while maintaining the attachment of the UE.

5. The method of claim 1 or claim 2, wherein the NEF acts as a PDU session anchor during use of each of the plurality of data delivery planes.

6. 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: Network nodes, the network nodes including: At least one processor; Memory, wherein the memory and the at least one processor belong to a unified interface device configured to host NEF; and A unified interface manager, stored in the memory of the NEF, and configured when executed by the at least one processor, to: receive a Protocol Data Unit (PDU) session event change notification message associated with the UE from the Session Management Function (SMF); and, in response to the PDU session event change notification message, establish a data delivery path between the UE and the Application Function (AF) via one of a plurality of data delivery planes traversing the NEF, wherein the plurality of data delivery planes includes a non-IP data delivery (NIDD) based data communication path established in the control plane between the UE and the AF via the NEF, via a point-to-point tunnel communication connection using N6. The NEF and UPF establish a NIDD-based data communication path between the UE and AF, and a data communication path between the UE and AF via the NEF and UPF communication connection using the N6 interface, wherein the NEF is configured to, in response to receiving the PDU session event change notification message and based on the UPF in the data delivery path of the PDU session event change notification message, initiate a listening server to monitor packet traffic from the UPF; and use a single unified interface supported by the NEF to process messages transmitted between the UE and AF through any of the plurality of data delivery planes.

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

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

9. The system of claim 6 or claim 7, wherein the NEF is configured to switch between the plurality of data delivery planes while maintaining the attachment of the UE.

10. The system of claim 6 or claim 7, wherein the NEF acts as a PDU session anchor during use of each of the plurality of data delivery planes.

11. A non-transitory computer-readable medium having executable instructions stored thereon, the executable instructions controlling the computer to perform the following steps when executed by a computer's processor: The NEF receives session event change notification messages for Protocol Data Units (PDUs) associated with the UE from the Session Management Function (SMF); In response to a PDU session event change notification message, the NEF establishes a data delivery path between the UE and the application function (AF) via one of a plurality of data delivery planes traversing the NEF. These plurality of data delivery planes include a non-IP data delivery (NIDD) based data communication path established in the control plane between the UE and AF via the NEF, an NIDD-based data communication path established between the UE and AF via the NEF and UPF using an N6 point-to-point tunnel communication connection, and an Internet Protocol (IP) based data communication path between the UE and AF via the NEF and UPF communication connection using an N6 interface. The NEF is configured to, in response to receiving the PDU session event change notification message and based on the UPF in the data delivery path of the PDU session event change notification message, initiate a listening server to monitor packet traffic from the UPF. as well as The NEF uses a single unified interface supported by the NEF to process messages passed between the UE and AF through any of the multiple data delivery planes.

12. The non-transitory computer-readable medium of claim 11, wherein the UE includes a low-power Internet of Things (IoT) device.

13. The non-transitory computer-readable medium of claim 11 or claim 12, wherein the single unified interface comprises a T8 interface and / or an N33 interface.

14. The non-transitory computer-readable medium of claim 11 or claim 12, wherein the NEF is configured to switch between the plurality of data delivery planes while maintaining the attachment of the UE.

15. The non-transitory computer-readable medium of claim 11 or claim 12, wherein the NEF acts as a PDU session anchor during use of each of the plurality of data delivery planes.

Images