Method and system for handling non-ip data delivery (NIDD) configuration data

Abstract

The present disclosure relates to method and system for handling Non-IP Data Delivery (NIDD) configuration data The present disclosure encompasses: receiving, at a Network Exposure Function (NEF) node [318], a request for creation of the NIDD configuration data along with an NEF-ID, from Application Function (AF) node [310]; sending, from the NEF node [318], a request to a Unified Data Manager (UDM) node [312] along with the NEF-ID for authorization of a Mobile Station International Subscriber Directory Number of a UE; storing, by the UDM node [312], the NIDD configuration data at Home Subscriber Service (HSS) node [314] after a successful authentication; receiving, at the NEF node [318], an authorisation response from the UDM node [312]; receiving, at the AF node [310], a response to the request for creation, from the NEF node; sharing, from the NEF node [318] the NIDD configuration data with a SCEF node [316].

Description

METHOD AND SYSTEM FOR HANDLING NON-IP DATA DELIVERY (NIDD) CONFIGURATION DATATECHNICAL FIELD

[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to methods and systems for handling Non-IP Data Delivery (NIDD) configuration data.BACKGROUND

[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.

[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.

[0004] Nowadays, telecom operators are working hard to enhance the network capabilities and to efficiently handle the handover scenarios or switching conditions from low generation network (say 4G) to high generation network (say 5G) or vice versa. In particular, the Application Function (AF) needs to communicate with Network Exposure Function (NEF) and Service Capability Exposure Function (SCEF) separately over N33 and T8 interface for provisioning Non-IP DataDelivery (NIDD) devices and also to maintain the status of UE. This leads to additional development of both Application Programming Interfaces (APIs) by the AF. The Network also needs to maintain two NIDD configuration IDs for the same Mobile Station International Subscriber Directory Number (MSISDN). Moreover, it also leads to keeping track of multiple NIDD config IDs for same UE provisioned in both networks i.e., 4G and 5G. However, a failure to do so leads to adverse impact on network performance such as sending mobile terminated messages to an incorrect network.

[0005] Hence, in view of these and other existing limitations, there arises an imperative need to provide an efficient solution to overcome the above-mentioned and other limitations and to provide a method and system for efficiently manage non-IP data delivery in handover conditions such as handover from 4G to 5G or vice versa.SUMMARY

[0006] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0007] An aspect of the present disclosure may relate to a method for handling Non-IP Data Delivery (NIDD) configuration data. The method comprises receiving, by a receiver unit at a Network Exposure Function (NEF) node, a request for creation of the NIDD configuration data along with a Network Exposure Function ID (NEF -ID), from an Application Function (AF) node. The method further comprises sending, by a transmitter unit from the NEF node, a request to a Unified Data Manager (UDM) node along with the NEF-ID for authorization of a Mobile Station International Subscriber Directory Number (MSISDN) of a user equipment (UE). The method further comprises storing, via a facilitator unit by the UDM node, the NIDD configuration data in a repository of a Home Subscriber Service (HSS) node after a successful authentication of the MSISDN. The method further comprises receiving, by the receiver unit at the NEF node, an authorisation response from the UDM node. The method further comprises creating, by a creation unit, at one of the NEF node and a Service Capability Exposure Function (SCEF) node, the NIDD configuration data. The method further comprises receiving, via the receiver unit at the AF node, a response to the request for creation of the NIDD configuration data from the NEF node. The method further comprises sharing, by the transmitter unit from the NEF node over an interface, the NIDD configuration data with a Service Capability Exposure Function (SCEF) node.

[0008] In an exemplary aspect of the present disclosure, the method further comprises sending, by the transmitter unit from the NEF node over the interface, one or more of a Delete request and an Update request related to the NIDD configuration data to the SCEF node.

[0009] In an exemplary aspect of the present disclosure, the interface is a NeSc interface.

[0010] In an exemplary aspect of the present disclosure, the NEF-ID is used as a converged NEF- ID when the HSS node and the UDM node belong to a same cluster.

[0011] In an exemplary aspect of the present disclosure, the converged NEF-ID and the NIDD configuration data are transmitted to the SCEF node by the NEF node over the interface.

[0012] In an exemplary aspect of the present disclosure, the NIDD configuration data comprises at least one of the NEF-ID, a NIDD configuration ID, and one or more NIDD configuration parameters.

[0013] According to another aspect of the present disclosure, a system for handling Non-IP Data Delivery (NIDD) configuration data is provided. The system comprises a receiver unit, a transmitter unit, a facilitator unit, and a creation unit connected to each other. The receiver unit is configured to receive at a Network Exposure Function (NEF) node, a request for creation of the NIDD configuration data along with a Network Exposure Function ID (NEF-ID), from an Application Function (AF) node. The transmitter unit is configured to send from the NEF node, a request to a Unified Data Manager (UDM) node along with the NEF-ID for authorization of a Mobile Station International Subscriber Directory Number (MSISDN) of a user equipment (UE). The facilitator unit is configured to store via the UDM node, the NIDD configuration data in a repository of a Home Subscriber Service (HSS) node after a successful authentication of the MSISDN. The receiver unit is further configured to receive at the NEF node an authorisation response from the UDM node. The creation unit is configured to create, at one of the NEF node and a Service Capability Exposure Function (SCEF) node, the NIDD configuration data. The receiver unit is further configured to receive at the AF node, a response to the request for creation of the NIDD configuration data from the NEF node. The transmitter unit is further configured to share from the NEF node, over an interface, the NIDD configuration data with a Service Capability Exposure Function (SCEF) node.

[0014] According to another aspect of the present disclosure, a method for handling Non-IP Data Delivery (NIDD) configuration data is provided. The method comprises receiving, by a receiver unit at a Network Exposure Function (NEF) node, a request for creation of the NIDD configuration data along with a Network Exposure Function Identity (NEF-ID), from an Application Function (AF) node. The method further comprises transmitting, by a transmitter unit from the NEF node, the request to a Unified Data Manager (UDM) node along with the NEF-ID for authorization of a Mobile Station International Subscriber Directory Number (MSISDN) of a user equipment (UE). The method further encompasses receiving, by the receiver unit at the NEF node, an authorisation response from the UDM node, wherein the authorisation response comprises at least a NIDD Configuration ID. The method further encompasses transmitting, by the transmitter unit from the NEF node over an interface, the request to a Service Capability Exposure Function (SCEF) node along with the NIDD Configuration ID for the creation of the NIDD configuration data. The method further comprises transmitting, by the transmitter unit from the SCEF node to a Home Subscriber Service (HSS) node, a request for a Home Subscriber Service (HSS) authorization. The method further comprises receiving, by the receiver unit at the SCEF node from the HSS node, a response to the request transmitted to the HSS node for the HSS authorization. The method further encompasses receiving, by the receiver unit at the NEF node from the SCEF node, a target response in response to the request transmitted to the SCEF node for the creation of NIDD configuration data. The method further comprises transmitting, by the transmitter unit from the NEF node to the AF node, a response to the request for creation of the NIDD configuration data, based on the target response.

[0015] In an exemplary aspect of the present disclosure, the interface is an NeSc interface.

[0016] In an exemplary aspect of the present disclosure, the method comprises receiving, by the receiver unit at the NEF node, one or more of a delete request related to the NIDD configuration data and an update request related to the NIDD configuration data. The method further comprises establishing, by a facilitator unit, a communication of the NEF node with the SCEF node over the interface based on the one or more of the delete request related to the NIDD configuration data and the update request related to the NIDD configuration data.

[0017] In an exemplary aspect of the present disclosure, the UDM node and the HSS node are configured in a non-cluster configuration.

[0018] In an exemplary aspect of the present disclosure, the NIDD Configuration ID is created at the UDM node.

[0019] In an exemplary aspect of the present disclosure, the target response comprises the NIDD configuration data and the target response is created at the SCEF node based on the NIDD Configuration ID.

[0020] According to another aspect of the present disclosure, a system for handling Non-IP Data Delivery (NIDD) configuration data is disclosed. The system comprising a receiver unit, a transmitter unit, and a facilitator unit connected to each other. The receiver unit is configured to receive, at a Network Exposure Function (NEF) node, a request for creation of the NIDD configuration data along with a Network Exposure Function Identity (NEF-ID), from an Application Function (AF) node. The transmitter unit is configured to transmit from the NEF node, the request to a Unified Data Manager (UDM) node along with the NEF-ID for authorization of a Mobile Station International Subscriber Directory Number (MSISDN) of a user equipment (UE). The receiver unit is further configured to receive at the NEF node from the UDM node, an authorisation response, wherein the authorisation response comprises at least a NIDD Configuration ID. The transmitter unit is further configured to transmit from the NEF node over an interface, the request to a Service Capability Exposure Function (SCEF) node along with the NIDD Configuration ID for the creation of the NIDD configuration data. The transmitter unit is further configured to transmit from the SCEF node to a Home Subscriber Service (HSS) node, a request for a Home Subscriber Service (HSS) authorization. The receiver unit is further configured to receive at the SCEF node from the HSS node, a response to the request transmitted to the HSS node for the HSS authorization. The receiver unit is further configured to receive at the NEF node from the SCEF node, a target response in response to the request transmitted to the SCEF node for the creation of NIDD configuration data. The transmitter unit is further configured to transmit from the NEF node to the AF node, a response to the request for creation of the NIDD configuration data, based on the target response.

[0021] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for handling Non-IP Data Delivery (NIDD) configuration data, the instructions include executable code which, when executed by one or more units of a system, causes a receiver unit of the system to receive at a Network Exposure Function (NEF) node, a request for creation of the NIDD configuration data along with a Network Exposure Function ID (NEF-ID), from an Application Function (AF) node. Further, the instructions includeexecutable code which, when executed causes a transmitter unit of the system to send from the NEF node, a request to a Unified Data Manager (UDM) node along with the NEF-ID for authorization of a Mobile Station International Subscriber Directory Number (MSISDN) of a user equipment (UE). Further, the instructions include executable code which, when executed causes a facilitator unit of the system to store via the UDM node, the NIDD configuration data in a repository of a Home Subscriber Service (HSS) node after a successful authentication of the MSISDN. Further, the instructions include executable code which, when executed causes the receiver unit of the system to receive at the NEF node an authorisation response from the UDM node. Further, the instructions include executable code which, when executed causes a creation unit of the system to create, at one of the NEF node and a Service Capability Exposure Function (SCEF) node, the NIDD configuration data. Further, the instructions include executable code which, when executed causes the receiver unit of the system to receive at the AF node, a response to the request for creation of the NIDD configuration data from the NEF node. Further, the instructions include executable code which, when executed causes the transmitter unit of the system to share from the NEF node, over an interface, the NIDD configuration data with a node.

[0022] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for handling Non-IP Data Delivery (NIDD) configuration data, the instructions include executable code which, when executed by one or more units of a system, causes a receiver unit of the system to receive, at a Network Exposure Function (NEF) node, a request for creation of the NIDD configuration data along with a Network Exposure Function Identity (NEF-ID), from an Application Function (AF) node. Further, the instructions include executable code which, when executed causes a transmitter unit of the system to transmit from the NEF node, the request to a Unified Data Manager (UDM) node along with the NEF-ID for authorization of a Mobile Station International Subscriber Directory Number (MSISDN) of a user equipment (UE). Further, the instructions include executable code which, when executed causes the receiver unit of the system to receive at the NEF node from the UDM node, an authorisation response, wherein the authorisation response comprises at least an NIDD Configuration ID. Further, the instructions include executable code which, when executed causes the transmitter unit of the system to transmit from the NEF node over an interface, the request to a Service Capability Exposure Function (SCEF) node along with the NIDD Configuration ID for the creation of the NIDD configuration data. Further, the instructions include executable code which, when executed causes the transmitter unit of the system to transmit from the SCEF node to a Home Subscriber Service (HSS) node, a request for a Home Subscriber Service (HSS) authorization. Further, the instructions include executable code which, when executed causes thereceiver unit of the system to receive at the SCEF node from the HSS node, a response to the request transmitted to the HSS node for the HSS authorization. Further, the instructions include executable code which, when executed causes the receiver unit of the system to receive at the NEF node from the SCEF node, a target response in response to the request transmitted to the SCEF node for the creation of NIDD configuration data. Further, the instructions include executable code which, when executed causes the transmitter unit of the system to transmit from the NEF node to the AF node, a response to the request for creation of the NIDD configuration data, based on the target response.OBJECTS OF THE DISCLOSURE

[0023] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0024] It is an object of the present disclosure to provide a system and a method for handling NonIP Data Delivery (NIDD) configuration data.

[0025] It is an object of the present disclosure to provide a system and a method for non-IP data delivery in a communication network.

[0026] It is another object of the present disclosure to provide a NeSc interface between NEF and SCEF to exchange message flow between NEF and SCEF for handling NIDD configuration.

[0027] It is yet another object of the present disclosure to provide a single point of contact to AF so that the AF do not needs to maintain APIs of NEF and SCEF.

[0028] It is yet another object of the present disclosure to efficiently handle NIDD configuration creation and maintain NIDD config ID for 5G and 4G networks.DESCRIPTION OF THE DRAWINGS

[0029] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating theprinciples of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.

[0030] FIG. 1 illustrates an exemplary block diagram representation of 5thgeneration core (5GC) network architecture.

[0031] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.

[0032] FIG. 3 illustrates an exemplary block diagram of a system for handling Non-IP Data Delivery (NIDD) configuration data, in accordance with exemplary implementations of the present disclosure.

[0033] FIG. 4 illustrates a method flow diagram for handling Non-IP Data Delivery (NIDD) configuration data in accordance with exemplary implementations of the present disclosure.

[0034] FIG. 5 illustrates an exemplary method flow diagram for handling Non-IP Data Delivery (NIDD) configuration data in accordance with exemplary implementations of the present disclosure.

[0035] FIG. 6 illustrates a method flow diagram for handling Non-IP Data Delivery (NIDD) configuration data in accordance with exemplary implementations of the present disclosure.

[0036] FIG. 7 illustrates an exemplary method flow diagram for handling Non-IP Data Delivery (NIDD) configuration data in accordance with exemplary implementations of the present disclosure.

[0037] The foregoing shall be more apparent from the following more detailed description of the disclosure.DETAILED DESCRIPTION

[0038] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.

[0039] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0040] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.

[0041] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.

[0042] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims,such terms are intended to be inclusive — in a manner similar to the term “comprising” as an open transition word — without precluding any additional or other elements.

[0043] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signal Processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.

[0044] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smartdevice”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and / or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment / device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from unit(s) which are required to implement the features of the present disclosure.

[0045] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.

[0046] As used herein “interface” or “user interface refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or moremodules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.

[0047] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.

[0048] As used herein the receiver unit is configured for receiving data, signals, information or a combination thereof between units / components within the system and / or connected with the system.

[0049] As used herein the transmitter unit is configured for transmitting data, signals, information or a combination thereof between units / components within the system and / or connected with the system.

[0050] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing method and system of handling Non-IP Data Delivery (NIDD) configuration data. More specifically, the present disclosure provides a single interface between the Network Exposure Function (NEF) and the Service Capability Exposure Function (SCEF) and provides a common point of contact for the Application Function (AF), in different configurations where the Home Subscriber Service (HSS) and Unified Data Manager (UDM) are in the same cluster, and where the HSS and the UDM are not in same cluster.

[0051] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0052] FIG. 1 illustrates an exemplary block diagram representation of 5thgeneration core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network architecture

[0100] includes a user equipment (UE)

[0102] , a radio access network (RAN)

[0104] , an access and mobility management function (AMF)

[0106] , a Session Management Function (SMF)

[0108] , a Service Communication Proxy (SCP)

[0110] , anAuthentication Server Function (AUSF)

[0112] , a Network Slice Specific Authentication and Authorization Function (NSSAAF)

[0114] , a Network Slice Selection Function (NSSF)

[0116] , a Network Exposure Function (NEF)

[0118] , a Network Repository Function (NRF)

[0120] , a Policy Control Function (PCF)

[0122] , a Unified Data Management (UDM)

[0124] , an application function (AF)

[0126] , a User Plane Function (UPF)

[0128] , a data network (DN)

[0130] , wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.

[0053] Radio Access Network (RAN)

[0104] is the part of a mobile telecommunications system that connects user equipment (UE)

[0102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.

[0054] Access and Mobility Management Function (AMF)

[0106] is a 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.

[0055] Session Management Function (SMF)

[0108] is a 5G core network function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.

[0056] Service Communication Proxy (SCP)

[0110] is a network function in the 5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.

[0057] Authentication Server Function (AUSF)

[0112] is a network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.

[0058] Network Slice Specific Authentication and Authorization Function (NSSAAF)

[0114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.

[0059] Network Slice Selection Function (NSSF)

[0116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.

[0060] Network Exposure Function (NEF)

[0118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.

[0061] Network Repository Function (NRF)

[0120] is a network function that acts as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.

[0062] Policy Control Function (PCF)

[0122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.

[0063] Unified Data Management (UDM)

[0124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.

[0064] Application Function (AF)

[0126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.

[0065] User Plane Function (UPF)

[0128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.

[0066] Data Network (DN)

[0130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.

[0067] FIG. 2 illustrates an exemplary block diagram of a computing device

[0200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device

[0200] may implement a method for handling Non-IP Data Delivery (NIDD) configuration data by utilising a system

[0300] , In another implementation, the computing device

[0200] itself implements the methodfor handling Non-IP Data Delivery (NIDD) configuration data using one or more units configured within the computing device

[0200] , wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.

[0068] The computing device

[0200] may include a bus

[0202] or other communication mechanism for communicating information, and a hardware processor

[0204] coupled with bus

[0202] for processing information. The hardware processor

[0204] may be, for example, a general-purpose microprocessor. The computing device

[0200] may also include a main memory

[0206] , such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus

[0202] for storing information and instructions to be executed by the processor

[0204] , The main memory

[0206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor

[0204] , Such instructions, when stored in non-transitory storage media accessible to the processor

[0204] , render the computing device

[0200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device

[0200] further includes a read only memory (ROM)

[0208] or other static storage device coupled to the bus

[0202] for storing static information and instructions for the processor

[0204] ,

[0069] A storage device

[0210] , such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus

[0202] for storing information and instructions. The computing device

[0200] may be coupled via the bus

[0202] to a display

[0212] , such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device

[0214] , including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus

[0202] for communicating information and command selections to the processor

[0204] , Another type of user input device may be a cursor controller

[0216] , such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor

[0204] , and for controlling cursor movement on the display

[0212] , The input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.

[0070] The computing device

[0200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and / or program logic which in combination with the computing device

[0200] causes or programs the computing device

[0200] to be a special-purpose machine. According to one implementation, the techniques herein areperformed by the computing device

[0200] in response to the processor

[0204] executing one or more sequences of one or more instructions contained in the main memory

[0206] , Such instructions may be read into the main memory

[0206] from another storage medium, such as the storage device

[0210] , Execution of the sequences of instructions contained in the main memory

[0206] causes the processor

[0204] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.

[0071] The computing device

[0200] also may include a communication interface

[0218] coupled to the bus

[0202] , The communication interface

[0218] provides a two-way data communication coupling to a network link

[0220] that is connected to a local network

[0222] , For example, the communication interface

[0218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface

[0218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface

[0218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

[0072] The computing device

[0200] can send messages and receive data, including program code, through the network(s), the network link

[0220] and the communication interface

[0218] , In the Internet example, a server

[0230] might transmit a requested code for an application program through the Internet

[0228] , the ISP

[0226] , a host

[0224] , the local network

[0222] and the communication interface

[0218] , The received code may be executed by the processor

[0204] as it is received, and / or stored in the storage device

[0210] , or other non-volatile storage for later execution.

[0073] Referring to FIG. 3, an exemplary block diagram of a system

[0300] for handling Non-IP Data Delivery (NIDD) configuration data, is shown, in accordance with the exemplary implementations of the present disclosure. The system

[0300] comprises at least one receiver unit

[0302] , at least one transmitter unit

[0304] , at least one facilitator unit

[0306] , and at least one creation unit

[0308] , Also, all of the components / units of the system

[0300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system

[0300] may comprise multiple such units or the system

[0300] may comprise any such numbers of said units, as required to implement the features of the presentdisclosure. Further, in an implementation, the system

[0300] may reside in a server or a network entity or the system

[0300] may be in communication with the network entity to implement the features as disclosed in the present disclosure.

[0074] For instance, as indicated in the FIG. 3, the system

[0300] is in connection with a Network Exposure Function (NEF) node

[0318] , an Application Function (AF) node

[0310] , a Unified Data Manager (UDM) node

[0312] , a Home Subscriber Server (HSS) node

[0314] , and a Service Capability Exposure Function (SCEF) node

[0316] for implementing the features as disclosed in the present disclosure.

[0075] The system

[0300] is configured for handling Non-IP Data Delivery (NIDD) configuration data, with the help of the interconnection between the components / units of the system

[0300] , The NIDD configuration data may be a configuration data or specific settings that are required to establish communication between a device and a network using the NIDD. In NIDD small amounts of data are transmitted efficiently by passing the traditional IP layer. The NIDD is a data delivery mechanism for delivering non-IP based data over the telecommunication network.

[0076] Particularly, for handling the Non-IP Data Delivery (NIDD) configuration data, initially the receiver unit

[0302] is configured to receive at the Network Exposure Function (NEF) node

[0318] a request for creation of the NIDD configuration data, along with a Network Exposure Function ID (NEF-ID), from the Application Function (AF) node

[0310] , The request for creation may refer to a request from the AF node

[0310] for creating the NIDD configuration data.

[0077] The NEF node

[0318] is a bridge between application(s) and an underlying network infrastructure exposing the capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications. The AF node

[0310] represents a node of the external applications interfacing with the 5G core network to access network capabilities and services.

[0078] The NIDD configuration data comprises at least one of the NEF-ID, a NIDD configuration ID, and one or more NIDD configuration parameters. The NIDD configuration ID may refer to the identifier used for a specific NIDD configuration data. The one or more NIDD configuration parameters may be parameters such as the access point names (APNs), server addresses, security credentials, duration, and / or notification destination address, the NIDD configuration ID, the MSISDN, an external ID, a radio data system (RDS) support, a public data network (PDN)establishment option, a notification destination, a maximum packet size, a NIDD downlink data transfer, a NIDD status, etc. Due to presence of multiple NIDD configurations present in conventional technologies, such multiple NIDD configurations were required to be managed, in order to handle such multiple NIDD configuration data, in an exemplary implementation of the present disclosure, usage of a common NEF-ID is provided.

[0079] The NEF-ID is a unique identifier that is assigned to each NEF within the network. The NED-ID helps to distinguish multiple NEFs and enables applications to interact with the specific NEF. The NEF-ID is the unique identifier used for identifying the details associated with the cluster in which the NEF is located. As would be understood, in the context of the present invention, a cluster may be referred to as a group of NEFs that may support internal communication amongst each other. There may be multiple NEF clusters which may be deployed, and the NEF-ID enables identification of such NEF clusters.

[0080] The NEF-ID is used as a converged NEF-ID when the HSS node

[0314] and the UDM node

[0312] belong to a same cluster. The converged NEF-ID may be a unique identifier used for identifying an SCEF instance, and a NEF instance. The HSS node

[0314] and the UDM node

[0312] being in the same cluster indicates that the HSS node

[0314] and the UDM node

[0312] supports internal communications among each other.

[0081] The present disclosure further discloses that the converged NEF-ID and the NIDD configuration data is transmitted to the SCEF node

[0316] by the NEF node

[0318] over the interface. Also, in an implementation the interface is an NeSc interface and therefore, in such case, the converged NEF-ID and the NIDD configuration data is transmitted to the SCEF node

[0316] by the NEF node

[0318] over the NeSc interface. The transmission of the converged NEF-ID and the NIDD configuration data over the interface supports authorization of the UE

[0102] and the AF node

[0310] and allows the UE

[0102] to latch onto any network and fetch the data related to the UE

[0102] using the same NIDD configuration data.

[0082] Further, after the receipt of the request for creation of the NIDD configuration data, the transmitter unit

[0304] is configured to send from the NEF node

[0318] , a request to a Unified Data Manager (UDM) node

[0312] along with the NEF-ID for authorization of a Mobile Station International Subscriber Directory Number (MSISDN) of the user equipment (UE)

[0102] , The UDM node

[0312] centralizes the management of subscriber data, including authentication, authorization, and subscription information. The MSISDN may be a unique identifier associatedwith mobile numbers assigned to a subscriber identity module (SIM) of the UE

[0102] , The authorisation of the MSISDN is a requirement enabling a control over the requests received via the AF node

[0310] ,

[0083] Further, the facilitator unit

[0306] is configured to store via the UDM node

[0312] , the NIDD configuration data in a repository of a Home Subscriber Service (HSS) node

[0314] after a successful authentication of the MSISDN. The repository is a location for storing, organising and managing data. The HSS node

[0314] is a node for a central database that stores the subscriber information and performs authentication and authorisation functions. The successful authentication of the MSISDN refers to the event where the MSISDN is authenticated successfully by the UDM node

[0312] i.e., the MSISDN exists. The storing of the NIDD configuration data supports the authorisation of the MSISDN until the NIDD configuration data expires or in a case, where the NIDD configuration data is manually deleted.

[0084] Thereafter, the receiver unit

[0302] is further configured to receive at the NEF node

[0318] an authorisation response from the UDM node

[0312] , The authorisation response may refer to the response from the UDM node

[0312] regarding the authentication of the MSISDN. This authorisation response contains the response regarding success or failure of the authorisation of the MSISDN, and the storing at the UDM unit

[0312] ,

[0085] The creation unit

[0308] is configured to create, at one of the NEF node

[0318] and the Service Capability Exposure Function (SCEF) node

[0316] , the NIDD configuration data. The NIDD configuration data may be created by either the NEF node

[0318] or the SCEF node

[0316] , The NEF node

[0318] and the SCEF node

[0316] will share the same NIDD configuration data which may be created by either one of them.

[0086] The receiver unit

[0302] is further configured to receive at the AF node

[0310] , a response to the request for creation of the NIDD configuration data from the NEF node

[0318] , The response to the request for creation of the NIDD configuration data is the response which comprises the NIDD configuration data, if the NIDD configuration data has been created, and contains an information or an indication message indicating failure in case the NIDD configuration data is not created.

[0087] The transmitter unit

[0304] is further configured to share from the NEF node

[0318] , over an interface, the NIDD configuration data with the Service Capability Exposure Function (SCEF) node

[0316] , In an implementation, the interface is an NeSc Interface. The SCEF node

[0316] is agateway between the external application servers and devices on the network. The NeSc Interface is the communication channel between the SCEF node

[0316] and the NEF node

[0318] , Through the communication between the SCEF node

[0316] and the NEF node

[0318] , once either one of them creates the NIDD configuration data, the NIDD configuration data is shared with the other such that the other node will use the created NIDD configuration data and does not recreate another NIDD configuration data. To avoid duplicity of creation of the NIDD configuration data, the SCEF node

[0316] will not create the NIDD configuration data again.

[0088] The transmitter unit

[0304] is further configured to send from the NEF node

[0318] over the interface (e.g., the NeSc Interface), one or more of a Delete request and an Update request related to the NIDD configuration data to the SCEF node

[0316] , The Delete request may refer to a request for deleting the NIDD configuration data, and an update request may refer to a request for updating the contents of the NIDD configuration data.

[0089] In another implementation of the present disclosure, wherein the UDM node

[0312] and the HSS node

[0314] are configured in a non-cluster configuration, the present disclosure further discloses that the receiver unit

[0302] is configured to receive, at the Network Exposure Function (NEF) node

[0318] , the request for creation of the NIDD configuration data along with the Network Exposure Function Identity (NEF-ID), from the Application Function (AF) node

[0310] ,

[0090] Then the transmitter unit

[0304] is configured to transmit from the NEF node

[0318] , the request to the Unified Data Manager (UDM) node

[0312] along with the NEF-ID for authorization of the Mobile Station International Subscriber Directory Number (MSISDN) of the user equipment (UE)

[0102] ,

[0091] Then the receiver unit

[0302] is further configured to receive at the NEF node

[0318] from the UDM node

[0312] , an authorisation response, wherein the authorisation response comprises at least the NIDD Configuration ID. The authorisation response may be a response for authorisation of the MSISDN which may be a successful authorisation response and an unsuccessful authorisation response. The successful authorisation response may be a response indicating success of the authorisation of the MSISDN and the unsuccessful authorisation response may be a response indicating a failure of the authorisation of the MSISDN.

[0092] The transmitter unit

[0304] is further configured to transmit from the NEF node

[0318] over the interface, the request to the Service Capability Exposure Function (SCEF) node

[0316] alongwith the NIDD Configuration ID for the creation of the NIDD configuration data. The present disclosure further discloses that the interface is an NeSc interface.

[0093] The transmitter unit

[0304] is further configured to transmit from the SCEF node

[0316] to the Home Subscriber Service (HSS) node

[0314] , a request for a Home Subscriber Service (HSS) authorization. The request for the HSS authorisation may be a request for validating the authority or legitimacy of the UE

[0102] that is trying to connect to the network. During the initial phases of communication between the UE and the telecommunication network, the HSS node

[0314] authenticates the user and verifies the subscriber's identity by comparing the provided credentials with the stored information.

[0094] The receiver unit

[0302] is further configured to receive at the SCEF node

[0316] from the HSS node

[0314] , a response to the request transmitted to the HSS node

[0314] for the HSS authorization. The response to the request may be a successful authentication response and an unsuccessful authentication response. The successful authentication response may be a response indicating success of the authentication of the UE

[0102] and the unsuccessful authentication response may be a response indicating a failure of the authentication of the UE

[0102] ,

[0095] The receiver unit

[0302] is further configured to receive at the NEF node

[0318] from the SCEF node

[0316] , a target response in response to the request transmitted to the SCEF node

[0316] for the creation of NIDD configuration data. The target response is a response comprising the NIDD configuration data and the target response is created at the SCEF node based on the NIDD Configuration ID.

[0096] The transmitter unit

[0304] is further configured to transmit from the NEF node

[0318] to the AF node

[0310] , a response to the request for creation of the NIDD configuration data, based on the target response.

[0097] The present disclosure further discloses that the receiver unit

[0302] is configured to receive at the NEF node

[0318] , one or more of the delete request related to the NIDD configuration data and the update request related to the NIDD configuration data, and wherein the facilitator unit

[0306] is configured to establish a communication of the NEF node

[0318] with the SCEF node

[0316] over the interface based on the one or more of the delete requests related to the NIDD configuration data and the update requests related to the NIDD configuration data. The communication of theNEF node

[0318] with the SCEF node

[0316] may refer to establishment of a connection between the NEF node

[0318] and the SCEF node

[0316] ,

[0098] The present disclosure further discloses that the UDM node

[0312] and the HSS node

[0314] are configured in the non-cluster configuration. The non-cluster configuration may be the configuration in which the HSS node

[0314] and the UDM node

[0312] are not part of the same cluster.

[0099] The present disclosure further discloses that the NIDD Configuration ID is created at the UDM node

[0312] ,

[0100] Referring to FIG. 4, an exemplary method flow diagram

[0400] for handling Non-IP Data Delivery (NIDD) configuration data, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method

[0400] is performed by the system

[0300] , Further, in an implementation, the system

[0300] may be present in a network entity to implement the features of the present disclosure.

[0101] Also, as shown in FIG. 4, the method

[0400] starts at step

[0402] ,

[0102] At step

[0404] , the method

[0400] comprises receiving, by a receiver unit

[0302] at a Network Exposure Function (NEF) node

[0318] , a request for creation of the NIDD configuration data, along with a Network Exposure Function ID (NEF-ID), from an Application Function (AF) node

[0310] , The NEF node

[0318] is a bridge between application(s) and an underlying network infrastructure exposing the capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications. The request for creation may refer to a request from the AF node

[0310] for creating the NIDD configuration data.

[0103] The NIDD configuration data may be a configuration data or specific settings that are required to establish communication between a device and a network using the NIDD. In NIDD small amounts of data are transmitted efficiently bypassing the traditional IP layer. The NIDD configuration data comprises at least one of the NEF-ID, a NIDD configuration ID, and one or more NIDD configuration parameters. The NIDD configuration ID may refer to the identifier used for a specific NIDD configuration data. The one or more NIDD configuration parameters may be parameters such as the access point names (APNs), server addresses, security credentials, duration, notification destination address, the NIDD configuration ID, the MSISDN, an external ID, a radiodata system (RDS) support, a public data network (PDN) establishment option, a notification destination, a maximum packet size, a NIDD downlink data transfer, a NIDD status, etc.

[0104] The AF node

[0310] represents a node of the external applications interfacing with the 5G core network to access network capabilities and services. The NEF-ID is a unique identifier that is assigned to each NEF within the network, this helps to distinguish multiple NEFs and enables applications to interact with the specific NEF. The NEF-ID is the unique identifier used for identifying the details associated with the cluster in which the NEF is located, there may be multiple NEF clusters which may be deployed, and the NEF-ID enables identification of such NEF clusters. The NEF-ID is used as a converged NEF-ID when the HSS node

[0314] and the UDM node

[0312] belongs to a same cluster. The converged NEF-ID may be a unique identifier used for identifying an SCEF instance, and a NEF instance. The HSS node

[0314] and the UDM node

[0312] being in the same cluster indicates that the HSS node

[0314] and the UDM node

[0312] supports internal communications and exchange different parameters for executing a service operation.

[0105] The present disclosure further discloses that the converged NEF-ID and the NIDD configuration data is transmitted to the SCEF node

[0316] by the NEF node

[0318] over the interface. Also, in an implementation the interface is an NeSc interface and therefore, in such case, the converged NEF-ID and the NIDD configuration data is transmitted to the SCEF node

[0316] by the NEF node

[0318] over the NeSc interface. The transmission of the converged NEF-ID and the NIDD configuration data over the interface supports authorization of the UE

[0102] and the AF node

[0310] and allows the UE

[0102] to latch onto any network and fetch the data related to the UE

[0102] using the same NIDD configuration data.

[0106] At step

[0406] , the method

[0400] comprises sending, by a transmitter unit

[0304] from the NEF node

[0318] , a request to a Unified Data Manager (UDM) node

[0312] along with the NEF-ID for authorization of a Mobile Station International Subscriber Directory Number (MSISDN) of a user equipment (UE)

[0102] , The UDM node

[0312] centralizes the management of subscriber data, including authentication, authorization, and subscription information. The MSISDN may be a unique identifier associated with mobile numbers assigned to a subscriber identity module (SIM) of the UE

[0102] , The authorisation of the MSISDN is a requirement enabling a control over the requests received via the AF node

[0310] ,

[0107] At step

[0408] , the method

[0400] comprises storing, via a facilitator unit

[0306] by the UDM node

[0312] , the NIDD configuration data in a repository of a Home Subscriber Service (HSS) node

[0314] after a successful authentication of the MSISDN. The repository is a location for storing, organising and managing data. The HSS node

[0314] is a node for a central database that stores the subscriber information and performs authentication and authorisation functions. The successful authentication of the MSISDN refers to the event where the MSISDN is authenticated successfully by the UDM node

[0312] i.e., the MSISDN exists. The storing of the NIDD configuration data supports the authorisation of the MSISDN until the NIDD configuration data expires or in a case, where the NIDD configuration data is manually deleted.

[0108] At step

[0410] , the method

[0400] comprises receiving, by the receiver unit

[0302] at the NEF node

[0318] , an authorisation response from the UDM node

[0312] , The authorisation response may refer to the response from the UDM node

[0312] regarding the authentication of the MSISDN. This authorisation response contains the response regarding success or failure of the authorisation of the MSISDN, and the storing at the UDM unit

[0312] ,

[0109] At step

[0412] , the method

[0400] comprises creating, by the creation unit

[0308] , at one of the NEF node

[0318] and the Service Capability Exposure Function (SCEF) node

[0316] , the NIDD configuration data. The NIDD configuration data may be created by either the NEF node

[0318] or the SCEF node

[0316] , The NEF node

[0318] and the SCEF node

[0316] will share the same NIDD configuration data which may be created by either one of them.

[0110] At step

[0414] , the method

[0400] comprises receiving, via the receiver unit

[0302] at the AF node

[0310] , a response to the request for creation of the NIDD configuration data from the NEF node

[0318] , The response to the request for creation of the NIDD configuration data is the response which comprises the NIDD configuration data, if the NIDD configuration data has been created, and contains an information or an indication message indicating failure in case the NIDD configuration data is not created.[OHl] At step

[0416] , the method

[0400] comprises sharing, by the transmitter unit

[0304] from the NEF node

[0318] over an interface, the NIDD configuration data with the Service Capability Exposure Function (SCEF) node

[0316] , In an implementation, the interface may be an NeSc Interface. The SCEF node

[0316] is a gateway between the external application servers and devices on the network. The NeSc Interface is the communication channel between the SCEF node

[0316] and the NEF node

[0318] , Through the communication between the SCEF node

[0316] and the NEF node

[0318] , once either one of them creates the NIDD configuration data, the NIDD configuration data is shared with the other such that the other node will use the created NIDD configuration dataand does not recreate another NIDD configuration data. To avoid duplicity of creation of the NIDD configuration data, the SCEF node

[0316] will not create the NIDD configuration data again.

[0112] The present disclosure further discloses that the method

[0400] further comprises sending, by the transmitter unit

[0304] from the NEF node

[0318] over the interface (e.g., the NeSc Interface), one or more of a Delete request and an Update request related to the NIDD configuration data to the SCEF node

[0316] , The Delete request may refer to a request for deleting the NIDD configuration data, and an update request may refer to a request for updating the contents of the NIDD configuration data.

[0113] Thereafter, at step

[0418] , the method

[0400] is terminated.

[0114] Referring to FIG. 5, an exemplary method flow diagram

[0500] for handling Non-IP Data Delivery (NIDD) configuration data is provided. The method

[0500] starts at step 1 where the AF node

[0310] sends to the NEF node

[0318] , the request for creation of the NIDD configuration data. Then at step 2, the NEF node

[0318] sends to the UDM node

[0312] the request for authorisation of the MSISDN of the UE

[0102] , Thereafter, at step 3, the UDM node

[0312] stores in the repository of the HSS

[0314] the NIDD configuration data after the successful authentication of the MSISDN. Then at step 4, the HSS performs authentication and sends the response to the UDM node

[0312] , The UDM node

[0312] thereafter, at step 5 sends the authorisation response to the NEF node

[0318] , Then at step 6, the AF node

[0310] receives from the NEF node

[0318] , the response to the request for creation of the NIDD configuration data. Thereafter, at step 7, the NIDD configuration data is shared with the SCEF node

[0316] by the NEF node

[0318] and the method

[0500] ends.

[0115] Referring to FIG. 6, an exemplary method flow diagram

[0600] for handling Non-IP Data Delivery (NIDD) configuration data, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method

[0600] is performed by the system

[0300] , Further, in an implementation, the system

[0300] may be present in a network entity to implement the features of the present disclosure.

[0116] Also, as shown in FIG. 6, the method

[0600] starts at step

[0602] ,

[0117] At step

[0604] , the method

[0600] comprises receiving, by a receiver unit

[0302] at the Network Exposure Function (NEF) node

[0318] , a request for creation of the NIDD configurationdata along with a Network Exposure Function Identity (NEF-ID), from the Application Function (AF) node

[0310] ,

[0118] The NEF node

[0318] is a bridge between application(s) and an underlying network infrastructure exposing the capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications. The AF node

[0310] represents a node of the external applications interfacing with the 5G core network to access network capabilities and services.

[0119] The NIDD configuration data comprises at least one of the NEF-ID, a NIDD configuration ID, and one or more NIDD configuration parameters. The NIDD configuration ID may refer to the identifier used for a specific NIDD configuration data. The one or more NIDD configuration parameters may be parameters such as the access point names (APNs), server addresses, security credentials, duration, and / or notification destination address, etc. Due to presence of multiple NIDD configurations present in conventional technologies, such multiple NIDD configurations were required to be managed, in order to handle such multiple NIDD configuration data, in an exemplary implementation of the present disclosure, usage of a common NEF-ID is provided.

[0120] The NEF-ID is a unique identifier that is assigned to each NEF within the network, this helps to distinguish multiple NEFs and enables applications to interact with the specific NEF.

[0121] At step

[0606] , the method

[0600] further comprises transmitting, by a transmitter unit

[0304] from the NEF node

[0318] , the request to the Unified Data Manager (UDM) node

[0312] along with the NEF-ID for authorization of a Mobile Station International Subscriber Directory Number (MSISDN) of a user equipment (UE)

[0102] , The UDM node

[0312] centralizes the management of subscriber data, including authentication, authorization, and subscription information, in other words, the UDM node

[0312] , The MSISDN may be a unique identifier associated with mobile numbers assigned to a subscriber identity module (SIM) of the UE

[0102] ,

[0122] Thereafter, at step

[0608] , the method

[0600] further comprises receiving, by the receiver unit

[0302] at the NEF node

[0318] , an authorisation response from the UDM node

[0312] , wherein the authorisation response comprises at least the NIDD Configuration ID. The authorisation response may be a response for authorisation of the MSISDN which may be a successful authorisation response and an unsuccessful authorisation response. The successful authorisation response maybe a response indicating success of the authorisation of the MSISDN and the unsuccessful authorisation response may be a response indicating a failure of the authorisation of the MSISDN.

[0123] Thereafter, at step

[0610] , the method

[0600] comprises transmitting, by the transmitter unit

[0304] from the NEF node over an interface, the request to a Service Capability Exposure Function (SCEF) node

[0316] along with the NIDD Configuration ID for the creation of the NIDD configuration data. The present disclosure further discloses that the interface is an NeSc interface. The SCEF node

[0316] is a gateway between the external application servers and devices on the network. The NeSc Interface is the communication channel between the SCEF node

[0316] and the NEF node

[0318] , Through the communication between the SCEF node

[0316] and the NEF node

[0318] , once either one of them creates the NIDD configuration data, the NIDD configuration data is shared with the other such that the other node will use the created NIDD configuration data and does not recreate another NIDD configuration data. To avoid duplicity of creation of the NIDD configuration data, the SCEF node

[0316] will not create the NIDD configuration data again.

[0124] Thereafter, at step

[0612] , the method

[0600] comprises transmitting, by the transmitter unit

[0304] from the SCEF node

[0316] to a Home Subscriber Service (HSS) node

[0314] , a request for a Home Subscriber Service (HSS) authorization. The request for the HSS authorisation may be a request for validating the authority or legitimacy of the UE

[0102] that is trying to connect to the network. During the initial phases of communication between the UE and the telecommunication network, the HSS node

[0314] authenticates the user and verifies the subscriber's identity by comparing the provided credentials with the stored information.

[0125] Then, at step

[0614] , the method

[0600] comprises receiving, by the receiver unit

[0302] at the SCEF node

[0316] from the HSS node

[0314] , a response to the request transmitted to the HSS node

[0314] for the HSS authorization. The response to the request may be a successful authentication response and an unsuccessful authentication response. The successful authentication response may be a response indicating success of the authentication of the UE

[0102] and the unsuccessful authentication response may be a response indicating a failure of the authentication of the UE

[0102] ,

[0126] Thereafter, at step

[0616] , the method

[0600] comprises receiving, by the receiver unit

[0302] at the NEF node

[0318] from the SCEF node

[0316] , a target response in response to the request transmitted to the SCEF node

[0316] for the creation of NIDD configuration data. The targetresponse is a response comprising the NIDD configuration data and the target response is created at the SCEF node based on the NIDD Configuration ID.

[0127] At step

[0618] , the method

[0600] comprises transmitting, by the transmitter unit

[0304] from the NEF node

[0318] to the AF node

[0310] , a response to the request for creation of the NIDD configuration data, based on the target response.

[0128] The present disclosure further discloses that the method encompasses receiving, by the receiver unit

[0302] at the NEF node

[0318] , one or more of a delete request related to the NIDD configuration data and an update request related to the NIDD configuration data; and establishing, by a facilitator unit

[0306] , a communication of the NEF node

[0318] with the SCEF node

[0316] over the interface based on the one or more of the delete request related to the NIDD configuration data and the update request related to the NIDD configuration data. The communication of the NEF node

[0318] with the SCEF node

[0316] may refer to establishment of a connection between the NEF node

[0318] and the SCEF node

[0316] ,

[0129] The present disclosure further discloses that the UDM node

[0312] and the HSS node

[0314] are configured in a non-cluster configuration. The non-cluster configuration may be the configuration in which the HSS node

[0314] and the UDM node

[0312] are not part of the same cluster.

[0130] The present disclosure further discloses that the NIDD Configuration ID is created at the UDM node

[0312] ,

[0131] Referring to FIG. 7, an exemplary method flow diagram

[0700] for handling Non-IP Data Delivery (NIDD) configuration data is provided. The method

[0700] starts at step SI where the AF node

[0310] sends to the NEF node

[0318] , the request for creation of the NIDD configuration data. Then at step S2, the NEF node

[0318] sends to the UDM node

[0312] the request for authorisation of the MSISDN of the UE

[0102] , Thereafter, at step S3, the UDM node

[0312] responds to the NEF node

[0318] and sends the authorisation response. Then at step S4, the NEF node

[0318] transmits the request to the SCEF node

[0316] , The SCEF node

[0316] thereafter, at step S5 sends the request for the HSS authorisation to the HSS node

[0314] , Then at step S6, the HSS node

[0314] sends the response to the request for the HSS authorisation to the SCEF node

[0316] , Then, at step S7, the NEF node

[0318] receives from the SCEF node

[0316] , the target response in response to the request for creation of the NIDD configuration data. Thereafter, at step S8, the NEF node

[0318] transmitsto the AF node

[0310] , the response to the request for creation of the NIDD configuration data based on the target response.

[0132] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for handling Non-IP Data Delivery (NIDD) configuration data, the instructions include executable code which, when executed by one or more units of a system

[0300] , causes: a receiver unit

[0302] of the system

[0300] to receive at a Network Exposure Function (NEF) node

[0318] , a request for creation of the NIDD configuration data along with a Network Exposure Function ID (NEF-ID), from an Application Function (AF) node

[0310] ; a transmitter unit

[0304] of the system

[0300] to send from the NEF node

[0318] , a request to a Unified Data Manager (UDM) node

[0312] along with the NEF-ID for authorization of a Mobile Station International Subscriber Directory Number (MSISDN) of a user equipment (UE); the facilitator unit

[0306] of the system

[0300] to store via the UDM node

[0312] , the NIDD configuration data in a repository of a Home Subscriber Service (HSS) node

[0314] after a successful authentication of the MSISDN; the receiver unit

[0302] of the system

[0300] to receive at the NEF node

[0318] an authorisation response from the UDM node

[0312] ; the receiver unit

[0302] of the system

[0300] to receive at the AF node

[0310] , a response to the request for creation of the NIDD configuration data from the NEF node

[0318] ; the transmitter unit

[0304] of the system

[0300] to share from the NEF node

[0318] , over an interface, the NIDD configuration data with a Service Capability Exposure Function (SCEF) node

[0316] ,

[0133] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for handling Non-IP Data Delivery (NIDD) configuration data, the instructions include executable code which, when executed by one or more units of a system

[0300] , causes: a receiver unit

[0302] of the system

[0300] to receive, at a Network Exposure Function (NEF) node

[0318] , a request for creation of the NIDD configuration data along with a Network Exposure Function Identity (NEF-ID), from an Application Function (AF) node

[0310] ; a transmitter unit

[0304] of the system

[0300] to transmit from the NEF node

[0318] , the request to a Unified Data Manager (UDM) node

[0312] along with the NEF-ID for authorization of a Mobile Station International Subscriber Directory Number (MSISDN) of a user equipment (UE); the receiver unit

[0302] of the system

[0300] to receive at the NEF node

[0318] from the UDM node

[0312] , an authorisation response, wherein the authorisation response comprises at least an NIDD Configuration ID; the transmitter unit

[0304] of the system

[0300] to transmit from the NEF node

[0318] over an interface, the request to a Service Capability Exposure Function (SCEF) node

[0316] along with the NIDD Configuration ID for the creation of the NIDD configuration data; the transmitter unit

[0304] of the system

[0300] to transmit from the SCEF node

[0316] to a HomeSubscriber Service (HSS) node

[0314] , a request for a Home Subscriber Service (HSS) authorization; the receiver unit

[0302] of the system

[0300] to receive at the SCEF node

[0316] from the HSS node

[0314] , a response to the request transmitted to the HSS node

[0314] for the HSS authorization; the receiver unit

[0302] of the system

[0300] to receive at the NEF node

[0318] from the SCEF node

[0316] , a target response in response to the request transmitted to the SCEF node

[0316] for the creation of NIDD configuration data; the transmitter unit

[0304] of the system

[0300] to transmit from the NEF node

[0318] to the AF node

[0310] , a response to the request for creation of the NIDD configuration data, based on the target response.

[0134] As is evident from the above, the present disclosure provides a technically advanced solution for handling Non-IP Data Delivery (NIDD) configuration data. The present solution provides a NeSc interface between the NEF node and the SCEF node to efficiently exchange message flow between the NEF and the SCEF for handling NIDD configuration data. Thus, the present disclosure provides a simple architecture by providing a single point of contact to the AF. Hence, the AF only needs to maintain N33 APIs instead of maintaining N33 and T8 both. Further, the present disclosure allows efficient handling of NIDD configuration data creation and thus maintaining NIDD configuration ID for 5G and 4G networks.

[0135] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

[0136] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components / units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

Claims

We Claim:

1. A method for handling Non-IP Data Delivery (NIDD) configuration data, the method comprising: receiving, by a receiver unit [302] at a Network Exposure Function (NEF) node [318], a Network Exposure Function ID (NEF -ID) along with a request for creation of the NIDD configuration data, from an Application Function (AF) node [310]; sending, by a transmitter unit [304] from the NEF node [318], a request to a Unified Data Manager (UDM) node [312] along with the NEF -ID for authorization of a Mobile Station International Subscriber Directory Number (MSISDN) of a user equipment (UE) [102]; storing, via a facilitator unit [306] by the UDM node [312], the NIDD configuration data in a repository of a Home Subscriber Service (HSS) node [314] after a successful authentication of the MSISDN; receiving, by the receiver unit [302] at the NEF node [318], an authorisation response from the UDM node [312]; creating, by a creation unit [308], at one of the NEF node [318] and a Service Capability Exposure Function (SCEF) node [316], the NIDD configuration data; receiving, via the receiver unit [302] at the AF node [310], a response to the request for creation of the NIDD configuration data from the NEF node [318]; and sharing, by the transmitter unit [304] from the NEF node [318] over an interface, the NIDD configuration data with a SCEF node [316],2. The method as claimed in claim 1, further comprising sending, by the transmitter unit [304] from the NEF node [318] over the interface, one or more of a Delete request and an Update request related to the NIDD configuration data to the SCEF node [316],3. The method as claimed in claim 1, wherein the interface is a NeSc interface.

4. The method as claimed in claim 1, wherein the NEF-ID is used as a converged NEF-ID when the HSS node [314] and the UDM node [312] belong to a same cluster.

5. The method as claimed in claim 4, wherein the converged NEF-ID and the NIDD configuration data are transmitted to the SCEF node [316] by the NEF node [318] over the interface.

6. The method as claimed in claim 1, wherein the NIDD configuration data comprises at least one of the NEF-ID, a NIDD configuration ID, and one or more NIDD configuration parameters.

7. A system [300] for handling Non-IP Data Delivery (NIDD) configuration data, the system [300] comprising:a receiver unit [302]; a transmitter unit [304] connected at least to the receiver unit [302]; a facilitator unit [306] connected at least to the transmitter unit [304]; and a creation unit [308] connected at least to the facilitator unit [306], wherein: the receiver unit [302] is configured to receive at a Network Exposure Function (NEF) node [318] a request for creation of the NIDD configuration data along with a Network Exposure Function ID (NEF-ID), from an Application Function (AF) node [310]; the transmitter unit [304] is configured to send from the NEF node [318], a request to a Unified Data Manager (UDM) node [312] along with the NEF-ID for authorization of a Mobile Station International Subscriber Directory Number (MSISDN) of a user equipment (UE) [102]; the facilitator unit [306] is configured to store via the UDM node [312], the NIDD configuration data in a repository of a Home Subscriber Service (HSS) node [314] after a successful authentication of the MSISDN; the receiver unit [302] is further configured to receive at the NEF node [318] an authorisation response from the UDM node [312]; the creation unit [308] is configured to create, at one of the NEF node [318] and a Service Capability Exposure Function (SCEF) node [316], the NIDD configuration data; the receiver unit [302] is further configured to receive at the AF node [310], a response to the request for creation of the NIDD configuration data from the NEF node; and the transmitter unit [304] is further configured to share from the NEF node [318], over an interface, the NIDD configuration data with a Service Capability Exposure Function (SCEF) node [316],8. The system [300] as claimed in claim 7, wherein the transmitter unit [304] is further configured to send from the NEF node [318] over the interface, one or more of a Delete request and an Update request related to the NIDD configuration data to the SCEF node [316],9. The system [300] as claimed in claim 7, wherein the interface is a NeSc interface.

10. The system [300] as claimed in claim 7, wherein the NEF-ID is used as a converged NEF- ID when the HSS node [314] and the UDM node [312] belong to a same cluster.

11. The system [300] as claimed in claim 10, wherein the converged NEF-ID and the NIDD configuration data are transmitted to the SCEF node [316] by the NEF node [318] over the interface.

12. The system [300] as claimed in claim 7, wherein the NIDD configuration data comprises at least one of the NEF-ID, a NIDD configuration ID, and one or more NIDD configuration parameters.

13. A non-transitory computer-readable storage medium storing instructions for handling NonIP Data Delivery (NIDD) configuration data, the instructions comprising executable code which, when executed by one or more units of a system [300], causes: a receiver unit [302] to receive at a Network Exposure Function (NEF) node [318], a Network Exposure Function ID (NEF-ID) along with a request for creation of the NIDD configuration data, from an Application Function (AF) node [310]; a transmitter unit [304] to send from the NEF node [318], a request to a Unified Data Manager (UDM) node [312] along with the NEF-ID for authorization of a Mobile Station International Subscriber Directory Number (MSISDN) of a user equipment (UE) [102]; a facilitator unit [306] to store, via the UDM node [312], the NIDD configuration data in a repository of a Home Subscriber Service (HSS) node [314] after a successful authentication of the MSISDN; the receiver unit [302] to receive at the NEF node [318], an authorisation response from the UDM node [312]; a creation unit [308] to create, at one of the NEF node [318] and a Service Capability Exposure Function (SCEF) node [316], the NIDD configuration data; the receiver unit [302] to receive at the AF node [310], a response to the request for creation of the NIDD configuration data from the NEF node [318]; and the transmitter unit [304] to share from the NEF node [318] over an interface, the NIDD configuration data with a SCEF node [316],

Images