[go: up one dir, main page]

WO2025017730A1 - Procédé et système de gestion de données de configuration de distribution de données non ip (nidd) - Google Patents

Procédé et système de gestion de données de configuration de distribution de données non ip (nidd) Download PDF

Info

Publication number
WO2025017730A1
WO2025017730A1 PCT/IN2024/051307 IN2024051307W WO2025017730A1 WO 2025017730 A1 WO2025017730 A1 WO 2025017730A1 IN 2024051307 W IN2024051307 W IN 2024051307W WO 2025017730 A1 WO2025017730 A1 WO 2025017730A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
nef
configuration data
nidd
nidd configuration
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/IN2024/051307
Other languages
English (en)
Inventor
Sandeep Bisht
Nilesh Sanas
Raghvendra Bhushan
Ashish Kumar
Aayush Bhatnagar
Mohd Rijvan Khan MOGIA
Nitesh GOUR
Kumar Gaurav SINGH
Amit Kumar Singh
Anurag Sinha
Hardik Navinbhai BAVISHI
Gaurav Jain
Mangesh Shantaram Kale
Supriya UPADHYE
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jio Platforms Ltd
Original Assignee
Jio Platforms Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jio Platforms Ltd filed Critical Jio Platforms Ltd
Publication of WO2025017730A1 publication Critical patent/WO2025017730A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0892—Network architectures or network communication protocols for network security for authentication of entities by using authentication-authorization-accounting [AAA] servers or protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring

Definitions

  • 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.
  • NIDD Non-IP Data Delivery
  • 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.
  • 2G second generation
  • 3G third generation
  • 4G fourth generation
  • the fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security.
  • 5G fifth generation
  • wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
  • AF Application Function
  • NEF Network Exposure Function
  • SCEF Service Capability Exposure Function
  • MSISDN Mobile Station International Subscriber Directory Number
  • 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).
  • NEF Network Exposure Function
  • AF Application Function
  • 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.
  • SCEF Service Capability Exposure Function
  • 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.
  • SCEF Service Capability Exposure Function
  • 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.
  • the interface is a NeSc interface.
  • the NEF-ID is used as a converged NEF- ID when the HSS node and the UDM node belong to a same cluster.
  • the converged NEF-ID and the NIDD configuration data are transmitted to the SCEF node by the NEF node over the interface.
  • the NIDD configuration data comprises at least one of the NEF-ID, a NIDD configuration ID, and one or more NIDD configuration parameters.
  • a system for handling Non-IP Data Delivery (NIDD) configuration data 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).
  • NEF Network Exposure Function
  • UDM Unified Data Manager
  • 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.
  • SCEF Service Capability Exposure Function
  • 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.
  • SCEF Service Capability Exposure Function
  • a method for handling Non-IP Data Delivery (NIDD) configuration data 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).
  • NEF Network Exposure Function
  • AF Application Function
  • 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.
  • SCEF Service Capability Exposure Function
  • 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.
  • HSS Home Subscriber Service
  • HSS Home Subscriber Service
  • 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.
  • the interface is an NeSc interface.
  • 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.
  • the UDM node and the HSS node are configured in a non-cluster configuration.
  • the NIDD Configuration ID is created at the UDM node.
  • the target response comprises the NIDD configuration data and the target response is created at the SCEF node based on the NIDD Configuration ID.
  • a system for handling Non-IP Data Delivery (NIDD) configuration data 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).
  • NEF Network Exposure Function
  • UDM Unified Data Manager
  • 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.
  • SCEF Service Capability Exposure Function
  • 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.
  • 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.
  • NEF Network Exposure Function
  • AF Application Function
  • the instructions include executable 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).
  • UDM Unified Data Manager
  • MSISDN Mobile Station International Subscriber Directory Number
  • 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.
  • 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.
  • 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.
  • SCEF Service Capability Exposure Function
  • 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.
  • NEF Network Exposure Function
  • NEF-ID Network Exposure Function Identity
  • 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.
  • UDM Unified Data Manager
  • MSISDN Mobile Station International Subscriber Directory Number
  • 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.
  • SCEF Service Capability Exposure Function
  • 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.
  • the instructions include executable code which, when executed causes the receiver 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.
  • 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.
  • NIDD NonIP Data Delivery
  • FIG. 1 illustrates an exemplary block diagram representation of 5 th generation core (5GC) network architecture.
  • 5GC 5 th generation core
  • 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.
  • 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.
  • NIDD Non-IP Data Delivery
  • 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.
  • NIDD Non-IP Data Delivery
  • 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.
  • NIDD Non-IP Data Delivery
  • 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.
  • NIDD Non-IP Data Delivery
  • 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.
  • NIDD Non-IP Data Delivery
  • 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.
  • 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.
  • 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.
  • DSP Digital Signal Processing
  • 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.
  • a user equipment 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.
  • 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.
  • 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.
  • 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.
  • 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 more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
  • 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.
  • DSP digital signal processor
  • ASIC Application Specific Integrated Circuits
  • FPGA Field Programmable Gate Array circuits
  • 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.
  • 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.
  • 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.
  • NEF Network Exposure Function
  • SCEF Service Capability Exposure Function
  • AF Application Function
  • HSS Home Subscriber Service
  • UDM Unified Data Manager
  • FIG. 1 illustrates an exemplary block diagram representation of 5 th generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure.
  • the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management (UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data network (DN) [130], wherein all the components are assumed to be
  • UE user equipment
  • Radio Access Network (RAN) is the part of a mobile telecommunications system that connects user equipment (UE) [102] 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.
  • Access and Mobility Management Function (AMF) 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.
  • Session Management Function (SMF) [108] 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.
  • UPF User Plane Function
  • Service Communication Proxy (SCP) [110] 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.
  • AUSF Authentication Server Function
  • 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
  • Network Slice Specific Authentication and Authorization Function [114] 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.
  • Network Slice Selection Function (NSSF) [116] 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.
  • Network Exposure Function [118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
  • Network Repository Function (NRF) [120] 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.
  • PCF Policy Control Function
  • Unified Data Management [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
  • Application Function (AF) is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.
  • UPF User Plane Function
  • Data Network (DN) 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.
  • FIG. 2 illustrates an exemplary block diagram of a computing device [200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
  • the computing device [200] may implement a method for handling Non-IP Data Delivery (NIDD) configuration data by utilising a system [300],
  • the computing device [200] itself implements the method for handling Non-IP Data Delivery (NIDD) configuration data using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
  • NIDD Non-IP Data Delivery
  • the computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a hardware processor [204] coupled with bus [202] for processing information.
  • the hardware processor [204] may be, for example, a general-purpose microprocessor.
  • the computing device [200] may also include a main memory [206], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204],
  • the main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [204], Such instructions, when stored in non-transitory storage media accessible to the processor [204], render the computing device [200] into a special-purpose machine that is customized to perform the operations specified in the instructions.
  • the computing device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204],
  • ROM read only memory
  • a storage device [210] such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and instructions.
  • the computing device [200] may be coupled via the bus [202] to a display [212], 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 [214] including alphanumeric and other keys, touch screen input means, etc.
  • a cursor controller [216] such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling cursor movement on the display [212].
  • 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.
  • the computing device [200] 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 [200] causes or programs the computing device [200] to be a special-purpose machine.
  • the techniques herein are performed by the computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206], Such instructions may be read into the main memory [206] from another storage medium, such as the storage device [210], Execution of the sequences of instructions contained in the main memory [206] causes the processor [204] to perform the process steps described herein.
  • hard-wired circuitry may be used in place of or in combination with software instructions.
  • the computing device [200] also may include a communication interface [218] coupled to the bus [202], The communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a local network [222],
  • the communication interface [218] 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.
  • the communication interface [218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN.
  • LAN local area network
  • Wireless links may also be implemented.
  • the communication interface [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
  • the computing device [200] can send messages and receive data, including program code, through the network(s), the network link [220] and the communication interface [218],
  • a server [230] might transmit a requested code for an application program through the Internet [228], the ISP [226], a host [224], the local network [222] and the communication interface [218],
  • the received code may be executed by the processor [204] as it is received, and/or stored in the storage device [210], or other non-volatile storage for later execution.
  • FIG. 3 an exemplary block diagram of a system [300] for handling Non-IP Data Delivery (NIDD) configuration data, is shown, in accordance with the exemplary implementations of the present disclosure.
  • the system [300] comprises at least one receiver unit [302], at least one transmitter unit [304], at least one facilitator unit [306], and at least one creation unit [308], Also, all of the components/ units of the system [300] 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.
  • system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [300] may reside in a server or a network entity or the system [300] may be in communication with the network entity to implement the features as disclosed in the present disclosure.
  • the system [300] is in connection with a Network Exposure Function (NEF) node [318], an Application Function (AF) node [310], a Unified Data Manager (UDM) node [312], a Home Subscriber Server (HSS) node [314], and a Service Capability Exposure Function (SCEF) node [316] for implementing the features as disclosed in the present disclosure.
  • NEF Network Exposure Function
  • AF Application Function
  • UDM Unified Data Manager
  • HSS Home Subscriber Server
  • SCEF Service Capability Exposure Function
  • the system [300] is configured for handling Non-IP Data Delivery (NIDD) configuration data, with the help of the interconnection between the components/units of the system [300],
  • 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.
  • 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.
  • the receiver unit [302] is configured to receive at the 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 the Application Function (AF) node [310],
  • the request for creation may refer to a request from the AF node [310] for creating the NIDD configuration data.
  • the NEF node [318] 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 [310] represents a node of the external applications interfacing with the 5G core network to access network capabilities and services.
  • 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.
  • 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.
  • 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.
  • 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.
  • the converged NEF-ID may be a unique identifier used for identifying an SCEF instance, and a NEF instance.
  • the HSS node [314] and the UDM node [312] being in the same cluster indicates that the HSS node [314] and the UDM node [312] supports internal communications among each other.
  • the present disclosure further discloses that the converged NEF-ID and the NIDD configuration data is transmitted to the SCEF node [316] by the NEF node [318] over the interface.
  • 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 [316] by the NEF node [318] over the NeSc interface.
  • the transmission of the converged NEF-ID and the NIDD configuration data over the interface supports authorization of the UE [102] and the AF node [310] and allows the UE [102] to latch onto any network and fetch the data related to the UE [102] using the same NIDD configuration data.
  • 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 the user equipment (UE) [102],
  • the UDM node [312] 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 [102],
  • SIM subscriber identity module
  • the authorisation of the MSISDN is a requirement enabling a control over the requests received via the AF node [310],
  • 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 repository is a location for storing, organising and managing data.
  • the HSS node [314] 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 [312] 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.
  • the receiver unit [302] is further configured to receive at the NEF node [318] an authorisation response from the UDM node [312],
  • the authorisation response may refer to the response from the UDM node [312] 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 [312],
  • the creation unit [308] is configured to create, at one of the NEF node [318] and the Service Capability Exposure Function (SCEF) node [316], the NIDD configuration data.
  • the NIDD configuration data may be created by either the NEF node [318] or the SCEF node [316], The NEF node [318] and the SCEF node [316] will share the same NIDD configuration data which may be created by either one of them.
  • 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 [318],
  • 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.
  • the transmitter unit [304] is further configured to share from the NEF node [318], over an interface, the NIDD configuration data with the Service Capability Exposure Function (SCEF) node [316],
  • the interface is an NeSc Interface.
  • the SCEF node [316] is a gateway between the external application servers and devices on the network.
  • the NeSc Interface is the communication channel between the SCEF node [316] and the NEF node [318], Through the communication between the SCEF node [316] and the NEF node [318], 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 [316] will not create the NIDD configuration data again.
  • the transmitter unit [304] is further configured to send from the NEF node [318] 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 [316],
  • the Delete request may refer to a request for deleting the NIDD configuration data
  • an update request may refer to a request for updating the contents of the NIDD configuration data.
  • the present disclosure further discloses that the receiver unit [302] is configured to receive, at the Network Exposure Function (NEF) node [318], the request for creation of the NIDD configuration data along with the Network Exposure Function Identity (NEF-ID), from the Application Function (AF) node [310],
  • NEF Network Exposure Function
  • AF Application Function
  • the transmitter unit [304] is configured to transmit from the NEF node [318], the request to the Unified Data Manager (UDM) node [312] along with the NEF-ID for authorization of the Mobile Station International Subscriber Directory Number (MSISDN) of the user equipment (UE) [102],
  • MSISDN Mobile Station International Subscriber Directory Number
  • the receiver unit [302] is further configured to receive at the NEF node [318] from the UDM node [312], 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.
  • the transmitter unit [304] is further configured to transmit from the NEF node [318] over the interface, the request to the Service Capability Exposure Function (SCEF) node [316] along with the NIDD Configuration ID for the creation of the NIDD configuration data.
  • SCEF Service Capability Exposure Function
  • the present disclosure further discloses that the interface is an NeSc interface.
  • the transmitter unit [304] is further configured to transmit from the SCEF node [316] to the Home Subscriber Service (HSS) node [314], 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 [102] that is trying to connect to the network.
  • the HSS node [314] authenticates the user and verifies the subscriber's identity by comparing the provided credentials with the stored information.
  • the receiver unit [302] is further configured to receive at the SCEF node [316] from the HSS node [314], a response to the request transmitted to the HSS node [314] 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 [102] and the unsuccessful authentication response may be a response indicating a failure of the authentication of the UE [102],
  • the receiver unit [302] is further configured to receive at the NEF node [318] from the SCEF node [316], a target response in response to the request transmitted to the SCEF node [316] 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.
  • the transmitter unit [304] is further configured to transmit from the NEF node [318] to the AF node [310], a response to the request for creation of the NIDD configuration data, based on the target response.
  • the receiver unit [302] is configured to receive at the NEF node [318], 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 [306] is configured to establish a communication of the NEF node [318] with the SCEF node [316] 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 the NEF node [318] with the SCEF node [316] may refer to establishment of a connection between the NEF node [318] and the SCEF node [316],
  • the present disclosure further discloses that the UDM node [312] and the HSS node [314] are configured in the non-cluster configuration.
  • the non-cluster configuration may be the configuration in which the HSS node [314] and the UDM node [312] are not part of the same cluster.
  • the present disclosure further discloses that the NIDD Configuration ID is created at the UDM node [312],
  • FIG. 4 an exemplary method flow diagram [400] for handling Non-IP Data Delivery (NIDD) configuration data, in accordance with exemplary implementations of the present disclosure is shown.
  • the method [400] is performed by the system [300], Further, in an implementation, the system [300] may be present in a network entity to implement the features of the present disclosure.
  • NIDD Non-IP Data Delivery
  • the method [400] comprises receiving, by a receiver unit [302] 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],
  • NEF Network Exposure Function
  • the NEF node [318] 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 [310] for creating the NIDD configuration data.
  • 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 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.
  • APIs access point names
  • server addresses security credentials
  • duration duration
  • notification destination address the NIDD configuration ID
  • MSISDN an external ID
  • RDS radio data system
  • PDN public data network
  • the AF node [310] 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 [314] and the UDM node [312] 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 [314] and the UDM node [312] being in the same cluster indicates that the HSS node [314] and the UDM node [312] supports internal communications and exchange different parameters for executing a service operation.
  • the present disclosure further discloses that the converged NEF-ID and the NIDD configuration data is transmitted to the SCEF node [316] by the NEF node [318] over the interface.
  • 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 [316] by the NEF node [318] over the NeSc interface.
  • the transmission of the converged NEF-ID and the NIDD configuration data over the interface supports authorization of the UE [102] and the AF node [310] and allows the UE [102] to latch onto any network and fetch the data related to the UE [102] using the same NIDD configuration data.
  • the method [400] comprises 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],
  • the UDM node [312] 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 [102],
  • SIM subscriber identity module
  • the authorisation of the MSISDN is a requirement enabling a control over the requests received via the AF node [310],
  • the method [400] comprises 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.
  • the repository is a location for storing, organising and managing data.
  • the HSS node [314] 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 [312] 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.
  • the method [400] comprises receiving, by the receiver unit [302] at the NEF node [318], an authorisation response from the UDM node [312],
  • the authorisation response may refer to the response from the UDM node [312] 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 [312],
  • the method [400] comprises creating, by the creation unit [308], at one of the NEF node [318] and the Service Capability Exposure Function (SCEF) node [316], the NIDD configuration data.
  • the NIDD configuration data may be created by either the NEF node [318] or the SCEF node [316],
  • the NEF node [318] and the SCEF node [316] will share the same NIDD configuration data which may be created by either one of them.
  • the method [400] comprises 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],
  • 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.
  • the method [400] comprises sharing, by the transmitter unit [304] from the NEF node [318] over an interface, the NIDD configuration data with the Service Capability Exposure Function (SCEF) node [316],
  • the interface may be an NeSc Interface.
  • the SCEF node [316] is a gateway between the external application servers and devices on the network.
  • the NeSc Interface is the communication channel between the SCEF node [316] and the NEF node [318], Through the communication between the SCEF node [316] and the NEF node [318], 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 [316] will not create the NIDD configuration data again.
  • the present disclosure further discloses that the method [400] further comprises sending, by the transmitter unit [304] from the NEF node [318] 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 [316],
  • the Delete request may refer to a request for deleting the NIDD configuration data
  • an update request may refer to a request for updating the contents of the NIDD configuration data.
  • step [418] the method [400] is terminated.
  • an exemplary method flow diagram [500] for handling Non-IP Data Delivery (NIDD) configuration data is provided.
  • the method [500] starts at step 1 where the AF node [310] sends to the NEF node [318], the request for creation of the NIDD configuration data.
  • the NEF node [318] sends to the UDM node [312] the request for authorisation of the MSISDN of the UE [102],
  • the UDM node [312] stores in the repository of the HSS [314] the NIDD configuration data after the successful authentication of the MSISDN.
  • the HSS performs authentication and sends the response to the UDM node [312],
  • the UDM node [312] thereafter, at step 5 sends the authorisation response to the NEF node [318],
  • the AF node [310] receives from the NEF node [318], the response to the request for creation of the NIDD configuration data.
  • the NIDD configuration data is shared with the SCEF node [316] by the NEF node [318] and the method [500] ends.
  • FIG. 6 an exemplary method flow diagram [600] for handling Non-IP Data Delivery (NIDD) configuration data, in accordance with exemplary implementations of the present disclosure is shown.
  • the method [600] is performed by the system [300], Further, in an implementation, the system [300] may be present in a network entity to implement the features of the present disclosure.
  • NIDD Non-IP Data Delivery
  • the method [600] comprises receiving, by a receiver unit [302] at the Network Exposure Function (NEF) node [318], a request for creation of the NIDD configuration data along with a Network Exposure Function Identity (NEF-ID), from the Application Function (AF) node [310],
  • NEF Network Exposure Function
  • NEF-ID Network Exposure Function Identity
  • the NEF node [318] 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 [310] represents a node of the external applications interfacing with the 5G core network to access network capabilities and services.
  • 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.
  • 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 method [600] further comprises transmitting, by a transmitter unit [304] from the NEF node [318], the request to the 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 UDM node [312] centralizes the management of subscriber data, including authentication, authorization, and subscription information, in other words, the UDM node [312],
  • the MSISDN may be a unique identifier associated with mobile numbers assigned to a subscriber identity module (SIM) of the UE [102],
  • SIM subscriber identity module
  • the method [600] further comprises receiving, by the receiver unit [302] at the NEF node [318], an authorisation response from the UDM node [312], 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.
  • the method [600] comprises transmitting, by the transmitter unit [304] from the NEF node over an interface, the request to a Service Capability Exposure Function (SCEF) node [316] along with the NIDD Configuration ID for the creation of the NIDD configuration data.
  • SCEF Service Capability Exposure Function
  • the present disclosure further discloses that the interface is an NeSc interface.
  • the SCEF node [316] is a gateway between the external application servers and devices on the network.
  • the NeSc Interface is the communication channel between the SCEF node [316] and the NEF node [318], Through the communication between the SCEF node [316] and the NEF node [318], 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 [316] will not create the NIDD configuration data again.
  • the method [600] comprises transmitting, by the transmitter unit [304] from the SCEF node [316] to a Home Subscriber Service (HSS) node [314], 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 [102] that is trying to connect to the network.
  • the HSS node [314] authenticates the user and verifies the subscriber's identity by comparing the provided credentials with the stored information.
  • the method [600] comprises receiving, by the receiver unit [302] at the SCEF node [316] from the HSS node [314], a response to the request transmitted to the HSS node [314] 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 [102] and the unsuccessful authentication response may be a response indicating a failure of the authentication of the UE [102],
  • the method [600] comprises receiving, by the receiver unit [302] at the NEF node [318] from the SCEF node [316], a target response in response to the request transmitted to the SCEF node [316] 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.
  • the method [600] comprises transmitting, by the transmitter unit [304] from the NEF node [318] to the AF node [310], a response to the request for creation of the NIDD configuration data, based on the target response.
  • the present disclosure further discloses that the method encompasses receiving, by the receiver unit [302] at the NEF node [318], 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 [306], a communication of the NEF node [318] with the SCEF node [316] 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 [318] with the SCEF node [316] may refer to establishment of a connection between the NEF node [318] and the SCEF node [316],
  • the present disclosure further discloses that the UDM node [312] and the HSS node [314] are configured in a non-cluster configuration.
  • the non-cluster configuration may be the configuration in which the HSS node [314] and the UDM node [312] are not part of the same cluster.
  • the present disclosure further discloses that the NIDD Configuration ID is created at the UDM node [312],
  • an exemplary method flow diagram [700] for handling Non-IP Data Delivery (NIDD) configuration data is provided.
  • the method [700] starts at step SI where the AF node [310] sends to the NEF node [318], the request for creation of the NIDD configuration data.
  • the NEF node [318] sends to the UDM node [312] the request for authorisation of the MSISDN of the UE [102],
  • the UDM node [312] responds to the NEF node [318] and sends the authorisation response.
  • the NEF node [318] transmits the request to the SCEF node [316],
  • the SCEF node [316] thereafter, at step S5 sends the request for the HSS authorisation to the HSS node [314], Then at step S6, the HSS node [314] sends the response to the request for the HSS authorisation to the SCEF node [316], Then, at step S7, the NEF node [318] receives from the SCEF node [316], the target response in response to the request for creation of the NIDD configuration data. Thereafter, at step S8, the NEF node [318] transmits to the AF node [310], the response to the request for creation of the NIDD configuration data based on the target response.
  • 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 [300], causes: a receiver unit [302] of the system [300] 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]; a transmitter unit [304] of the system [300] 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); the facilitator unit [306] of the system [300] to store via the UDM node [312], the NIDD configuration data in a repository of a Home Subscriber Service
  • 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 [300], causes: a receiver unit [302] of the system [300] 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 Identity (NEF-ID), from an Application Function (AF) node [310]; a transmitter unit [304] of the system [300] to transmit from the NEF node [318], the 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); the receiver unit [302] of the system [300] to receive at the NEF node [318] from the UDM node [312], an authorisation response, wherein
  • 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.
  • 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.
  • the present disclosure allows efficient handling of NIDD configuration data creation and thus maintaining NIDD configuration ID for 5G and 4G networks.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente divulgation concerne un procédé et un système de gestion de données de configuration de distribution de données non IP (NIDD). La présente divulgation consiste : à recevoir, au niveau d'un nœud de fonction d'exposition de réseau (NEF) [318], une demande de création des données de configuration NIDD conjointement avec un NEF-ID, en provenance d'un nœud de fonction d'application (AF) [310] ; envoyer, à partir du nœud NEF [318], une demande à un nœud de gestionnaire de données unifié (UDM) [312] conjointement avec le NEF-ID pour une autorisation d'un numéro d'annuaire d'abonnés international de station mobile d'un UE ; stocker, par le nœud UDM [312], les données de configuration NIDD au niveau du nœud de service d'abonné domestique (HSS) [314] après la réussite d'une authentification ; recevoir, au niveau du nœud NEF [318], une réponse d'autorisation en provenance du nœud UDM [312] ; recevoir, au niveau du nœud AF [310], une réponse à la demande de création, en provenance du nœud NEF ; partager, à partir du nœud NEF [318], les données de configuration NIDD avec un nœud SCEF [316].
PCT/IN2024/051307 2023-07-19 2024-07-18 Procédé et système de gestion de données de configuration de distribution de données non ip (nidd) Pending WO2025017730A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202321048586 2023-07-19
IN202321048586 2023-07-19

Publications (1)

Publication Number Publication Date
WO2025017730A1 true WO2025017730A1 (fr) 2025-01-23

Family

ID=94281256

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IN2024/051307 Pending WO2025017730A1 (fr) 2023-07-19 2024-07-18 Procédé et système de gestion de données de configuration de distribution de données non ip (nidd)

Country Status (1)

Country Link
WO (1) WO2025017730A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200322881A1 (en) * 2019-04-02 2020-10-08 Electronics And Telecommunications Research Institute Non-ip data delivery authorization update method and connection release method for non-ip data delivery, and device for performing the method
US20210120377A1 (en) * 2019-10-17 2021-04-22 Oracle International Corporation METHODS, SYSTEMS, AND COMPUTER READABLE MEDIA FOR NON-INTERNET PROTOCOL (NON-IP) DATA DELIVERY BETWEEN USER EQUIPMENT (UEs) AND MULTIPLE APPLICATION SERVERS (ASs)

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200322881A1 (en) * 2019-04-02 2020-10-08 Electronics And Telecommunications Research Institute Non-ip data delivery authorization update method and connection release method for non-ip data delivery, and device for performing the method
US20210120377A1 (en) * 2019-10-17 2021-04-22 Oracle International Corporation METHODS, SYSTEMS, AND COMPUTER READABLE MEDIA FOR NON-INTERNET PROTOCOL (NON-IP) DATA DELIVERY BETWEEN USER EQUIPMENT (UEs) AND MULTIPLE APPLICATION SERVERS (ASs)

Similar Documents

Publication Publication Date Title
US20250350938A1 (en) Key management method and apparatus, device, and storage medium
WO2025017730A1 (fr) Procédé et système de gestion de données de configuration de distribution de données non ip (nidd)
WO2025069097A1 (fr) Procédé et système de gestion d'une ou plusieurs politiques de session dans un réseau
WO2025012979A1 (fr) Procédé et système aux fins d'une gestion basée sur la configuration d'une demande de procédure
WO2025052474A1 (fr) Procédé et système permettant de gérer un abonnement de fonctions de réseau
WO2025008915A1 (fr) Procédé et système de fourniture d'informations d'instance de tranche de réseau
WO2025017686A1 (fr) Procédé et système de fourniture d'informations de tranche dans un réseau de communication
WO2025012943A1 (fr) Procédé et système de création d'un contexte de gestion de session (sm) dans un premier et un second réseau
WO2025052460A1 (fr) Procédé et système de gestion d'accès pour un équipement d'utilisateur dans un réseau
WO2025052420A1 (fr) Procédé et système d'établissement d'une session de réseau au niveau d'une fonction de support de liaison (bsf)
WO2025012980A1 (fr) Procédé et système pour la réalisation d'une procédure d'interdiction dans une zone de rapport de présence prédéfinie (pra)
WO2025012972A1 (fr) Procédé et système de fourniture d'informations de tranche dans un réseau de communication
WO2025008876A1 (fr) Procédé et système de mise sur liste d'autorisation de dispositifs compatibles avec vowifi
WO2025012964A1 (fr) Procédé et système de gestion de routage de messages
WO2025069062A1 (fr) Procédé et système de continuité de service dans un réseau de communication
WO2025057183A1 (fr) Procédé et système pour établir une connexion entre un équipement utilisateur et un réseau
WO2025052436A1 (fr) Procédé et système de découverte d'une ou de plusieurs fonctions de réseau homologues
WO2025057184A1 (fr) Procédé et système de gestion de sessions de protocole de configuration dynamique d'hôte (dhcp) dans un réseau sans fil
WO2025008888A1 (fr) Procédé mis en œuvre par un nœud de réseau pour gérer un transfert dans un réseau de communication
WO2025008869A1 (fr) Procédé et système pour effectuer un enregistrement de réseau dans un réseau de communication sans fil
WO2025069076A1 (fr) Procédé et système d'authentification d'une passerelle domestique (hgw) dans un réseau à large bande
WO2025052404A1 (fr) Procédé et système permettant de faciliter le routage dans un réseau
WO2025008991A1 (fr) Serveur de réseau pour authentifier un dispositif utilisateur et procédé associé
WO2025008867A1 (fr) Procédé et système de gestion de sélection de tranche de réseau dans un réseau de télécommunications
WO2025013048A1 (fr) Procédé et système de mise à jour de paramètres pour un ou plusieurs nœuds réseau

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24842721

Country of ref document: EP

Kind code of ref document: A1