System and method for managing mobile terminated message in a network

Abstract

The present disclosure relates to a system (108) and method for managing mobile terminated message in a network. The system sends a mobile terminated message to a user equipment (UE) (104) capable of supporting fourth generation (4G) and fifth generation (5G) networks. The system (108) provides an exchange of mobile terminated messages between a network exposure function (NEF) (306) and a service capability exposure function (SCEF) (308) over an interface between the network exposure function (NEF) (306) and the service capabilities exposure function (SCEF) (308). The system aids a movable device to transfer data independent of network technology.

Description

SYSTEM AND METHOD FOR MANAGING MOBILE TERMINATED MESSAGE IN A NETWORKRESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, integrated circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited ( JPL) or its affiliates (herein after referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.TECHNICAL FIELD

[0002] The present disclosure generally relates to systems and methods for processing mobile terminated messages in a wireless telecommunications network. More particularly, the present disclosure relates to a system and a method for managing mobile terminated messages in a network.BACKGROUND

[0003] The following description of 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 be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0004] The evolution of 3GPP standards has led to the integration of various features and functionalities in network nodes. However, a significant gap exists in the explicit description of interactions between 4G nodes, such as the Service Capabilities Exposure Function (SCEF) and the Network Exposure Function(NEF). This lack of clarity has resulted in technical challenges in designing efficient flows and interfaces within network systems.

[0005] Furthermore, the interaction of Application Functions (AFs) with NEF and SCEF through a Common Application Programming Interface Framework (CAPIF) is inadequately described in the existing standards. There is a noticeable absence of detailed guidance on how CAPIF selects between NEF or SCEF, leading to uncertainties in the implementation of these interactions.

[0006] Additionally, there is a requirement for AFs to support N33 and T8 APIs, which adds to the complexity of data transfers between network elements. These complexities encompass the management of multiple protocols, data transfer mechanisms, certificates, security -related protocols, endpoint IP connection details, and data connection management.

[0007] There is, therefore, a need in the art to provide a system and a method that can mitigate the problems associated with the prior arts.OBJECTS OF THE PRESENT DISCLOSURE

[0008] It is an object of the present disclosure to provide a system and a method that mitigates the complexity of data transfers (such as managing multiple protocols / data transfer mechanisms / certificates / security related protocols / end point IP connection details and data connection management) between network elements.

[0009] It is an object of the present disclosure to provide a system and a method that provides a single point of contact to an application function (AF) for sending a mobile terminating (MT) message.

[0010] It is an object of the present disclosure to provide a system and a method that delivers a MT delivery Acknowledgement at the AF if a radio data system (RDS) is supported at a user equipment (UE) irrespective of UE network handovers.

[0011] It is an object of the present disclosure to provide a system and a method that uses an interface which handles seamless MT messages and acknowledges a transfer between a network exposure function (NEF) and a service capabilities exposure function (SCEF).

[0012] It is an object of the present disclosure to provide a system and a method enables the NEF to handle delivery of buffered MT messages irrespective of the UE being in a fourth generation (4G) or a fifth generation (5G) network.SUMMARY

[0013] In an exemplary embodiment, a system for managing mobile terminated (MT) messages in a network by a network exposure function (NEF) is described. The NEF comprises a receiving unit configured to receive MT messages directed towards a user equipment (UE) from an application function (AF). A processing unit configured to determine a network type of the UE by checking mapping of a non-IP data delivery (NIDD) configuration and a service message (SM) context. A routing unit configured to route the MT message to a network function based on the network type of the UE. The network type includes a first type of network and a second type of network. The network function includes a first network function and a second network function. For the first type of network, first network function is selected and for the second type of network, the second network function is selected. A delivery facilitation unit is configured to deliver the MT message to the UE through the selected network function. For delivery of the MT messages to the UE attached to the first type of network, the NEF is configured to send the MT message to the first network function. The first network function is configured to send the MT message to the UE connected to the first type of network. For delivery of the MT messages to the second network function, the NEF is configured to send the MT message to the second network function via an interface between the NEF and the second network function. The second network function is configured to identify one of plurality mobility management entities (MMEs) based on mapping of NIDD-configuration and the SM context. The second network function is configured to send the MT message to the identified MME. The MME configured to send the MT message to the UE attached to the second type of network.

[0014] In some embodiments, the first type of network is a fifth generation (5G) network, or a sixth generation (6G) network and the first network function isa session management function (SMF) (304). The second type of network type is a fourth generation (4G) network, and the second network function is a service capabilities exposure function (SCEF). The NEF facilitates the communication between the first type of network and the second type of network via the interface.

[0015] In some embodiment, the NEF further comprises a data buffering unit configured to store the MT messages during transitions between an evolved packet core (EPC) network and a 5G core (5GC) network for the UE.

[0016] In some embodiment, on detecting transition of the UE from an evolved packet core (EPC) network to a 5G core (5GC) network, the NEF configured to receive new SM context from the SMF. The SMF configured to overwrite the new SM context with a previous SM context received from MME or SCEF. The NEF configured to initiate delivery of the stored MT messages to the SMF. The SMF configured to send the received MT messages to the UE. The SMF configured to send a MT delivery acknowledgment received from the UE to the NEF.

[0017] In some embodiment, on detecting transition of the 5GC to the EPC, the SCEF configured to receive a new SM context from the MME. The NEF configured to overwrite the new SM context with a previous SM context received from the SMF. The NEF configured to initiate delivery of the stored MT messages to the SCEF via the interface. The SCEF configured to send the MT messages to the UE via the MME. The SCEF configured to send the delivery response to the NEF via the interface.

[0018] In some embodiment, on detecting a request of a reliable data service (RDS) acknowledgement from the NEF, the SMF configured to forward a MT delivery acknowledgement (ACK) to the NEF on receiving acknowledgement from the UE.

[0019] In some embodiment, on detecting a request of the RDS acknowledgement from the NEF, the MME configured to forward the MT deliveryACK to the SCEF on receiving acknowledgement from the UE and the SCEF configured to forward the MT delivery ACK to the NEF over the interface.

[0020] In another exemplary embodiment, method for managing mobile terminated (MT) messages in a network is described. The method comprises receiving, by a network exposure function (NEF), MT messages directed towards a user equipment (UE) from an application function (AF). The method further comprises determining, by the NEF, a network type of the UE by checking mapping of a non-IP data delivery (NIDD) configuration and a service message (SM) context. The method comprises routing, by the NEF, the MT messages to a network function based on the network type of the UE. The network type includes a first type of network and a second type of network. The network function includes a first network function and a second network function. For the first type of network, first network function is selected and for the second type of network, the second network function is selected. The method comprises delivering, by the NEF, the MT message to the UE through the selected network function. For delivery of the MT messages to attached to the first type of network, sending, by the NEF, the MT messages to the first network function, and sending, by the first network function, the MT messages to the UE attached to the first type of network. For delivery of the MT messages to the UE, sending, by the NEF, the MT message to the second network function via an interface between the NEF and the second network function, identifying, by the second network function, one of plurality mobility management entities (MMEs) based on mapping of NIDD-configuration and the SM context, sending, by the second network function, the MT messages to the identified MME, and sending, by the MME, the MT messages to the UE attached to the second network function. .

[0021] In some embodiments, the first type of network is a fifth generation (5G) network, or a sixth generation (6G) network and the first network function is a session management function (SMF) (304). The second type of network type is a fourth generation (4G) network, and the second network function is a servicecapabilities exposure function (SCEF). The NEF facilitates the communication between the first type of network and the second type of network via the interface.

[0022] In some embodiment, the method comprises storing, by the NEF, the MT messages during transitions of the UE between an evolved packet core (EPC) network and a 5G core (5GC) network for the UE.

[0023] In some embodiment, the method comprises on detecting transition of the UE from an evolved packet core (EPC) network to a 5G core (5GC) network, receiving, by the NEF, a new SM context from the SMF. The SMF configured to overwrite the new SM context with a previous SM context received from MME or SCEF. The method comprises initiating, by the NEF, delivery of the stored MT messages to the SMF. The method further comprises sending, by the SMF, the received MT messages to the UE and sending, by the SMF, a MT delivery acknowledgment received from the UE to the NEF.

[0024] In some embodiment, the method comprises on detecting transition of the 5GC to the EPC, receiving, by the SCEF, a new SM context from the MME. The method comprises overwriting, by the NEF, the new SM context with a previous SM context received from the SMF. The method comprises initiating, by the NEF, delivery of the stored MT messages to the SCEF via the interface. The method comprises sending, by the SCEF, the MT messages to the UE via the MME and sending, by the SCEF, a delivery response to the NEF via the interface.

[0025] In some embodiment, the method comprises on detecting a request of a reliable data service (RDS) acknowledgement from the NEF, forwarding, by the SMF, a MT delivery acknowledgement (ACK) to the NEF on receiving acknowledgement from the UE.

[0026] In some embodiment, the method comprises on detecting a request of the RDS acknowledgement from the NEF, forwarding, by the MME, the MT delivery ACK to the SCEF on receiving acknowledgement from the UE and forwarding, by the SCEF, the MT delivery ACK to the NEF over the interface.

[0027] In another exemplary embodiment, a user equipment is communicatively coupled with a network. The coupling comprises steps of receiving, by the network, a connection request, sending an acknowledgment of the connection request to the UE, and transmitting a plurality of signals in response to the connection request. The network includes a first network function, a network exposure function (NEF), a second network function, a mobility management function (MME), and an application function implementing a method for managing mobile terminated (MT) messages in the network as described above.

[0028] In another exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for managing mobile terminated (MT) messages in a network (106). The method includes receiving, by a network exposure function (NEF), MT messages directed towards a user equipment (UE) from an application function (AF). The method further comprises determining, by the NEF, a network type of the UE by checking mapping of a non-IP data delivery (NIDD) configuration and a service message (SM) context. The method comprises routing, by the NEF, the MT messages to a network function based on the network type of the UE. The network type includes a first type of network and a second type of network. The network function includes a first network function and a second network function. For the first type of network, first network function is selected and for the second type of network, the second network function is selected. The method comprises delivering, by the NEF, the MT message to the UE through the selected network function. For delivery of the MT messages to attached to the first type of network, sending, by the NEF, the MT messages to the first network function, and sending, by the first network function, the MT messages to the UE attached to the first type of network. For delivery of the MT messages to the UE, sending, by the NEF, the MT message to the second network function via an interface between the NEF and the second network function, identifying, by the second network function, one of plurality mobility management entities (MMEs) based on mapping of NIDD-configuration and the SM context, sending, by the second network function, the MT messages to the identified MME, and sending, by the MME, the MT messages to the UE attached to the second network function.BRIEF DESCRIPTION OF THE DRAWINGS

[0029] In the figures, similar components and / or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label with a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.

[0030] The diagrams are for illustration only, which thus is not a limitation of the present disclosure, and wherein:

[0031] FIG. 1 illustrates an example network architecture for implementing a proposed system, in accordance with an embodiment of the present disclosure.

[0032] FIG. 2A illustrates an example block diagram of a proposed system, in accordance with an embodiment of the present disclosure.

[0033] FIG. 2B illustrates an example block diagram of a network exposure function (NEF), in accordance with an embodiment of the present disclosure.

[0034] FIG. 3A illustrates an example flow diagram for a mobile terminating (MT) message delivery, in accordance with embodiments of the present disclosure.

[0035] FIG. 3B illustrates an example flow diagram for a mobile terminating (MT) message delivery, in accordance with embodiments of the present disclosure.

[0036] FIG. 4 illustrates an example computer system in which or with which the embodiments of the present disclosure may be implemented.

[0037] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture1 102-1, 102-2... 102-N - Users104-1, 104-2. . . 104-N - User Equipments (UEs)106 - Network108 - System110 - Entity112 - Centralized Server202: Processor(s)204: Memory206: Interface(s)208: Processing unit / engine(s)210: Database (DB)212: Data parameter engine214: Other engine(s)222: Network exposure function (NEF)224: Processing Unit226: Receiving Unit228: Routing Unit230: Delivery Facilitation Unit232: Data Buffering Unit300A: Flow diagram for mobile terminating (MT) message delivery302: User equipment (UE)304: Session Management Function (SMF)306: Network Exposure Function (NEF)308: Service Capabilities Exposure Function (SCEF)310: Mobility Management Entity (MME)312: Application Function (AF)322: Step324: Step326: Step328: Step330: Step: Step : Step : Step : Step : Step : Step : Step : Step : Step B: Flow Diagram for MT message delivery : Step : Step : Step : Step : Step -1: Step -2: Step : Step -1: Step -2: Step -3: Step -4: Step : Computer System - External Storage Device - Bus - Main Memory - Read Only Memory - Mass Storage Device - Communication PortBRIEF DESCRIPTION OF THE INVENTION

[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 can 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. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

[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, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0041] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe theoperations as a sequential process, many of the operations can 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. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[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 like the term “comprising” as an open transition word without precluding any additional or other elements.

[0043] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0044] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

[0045] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical, and computing device. The user device is capable of receiving and / or transmitting one or parameters, performing fimction / s, communicating with other user devices, and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery, and an input-means such as a hard keypad and / or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.

[0046] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purposeprocessor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a 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 is a hardware processor.

[0047] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data transfer are also expected to evolve and replace the older generations of technologies. In the field of wireless data communications, the dynamic advancement of various generations of cellular technology are also seen. The development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourth generation (4G), and now fifth generation (5G), and more such generations are expected to continue in the forthcoming time.

[0048] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.

[0049] The system and method disclosed relates to an Enhanced Packet Core (EPC) interworking and network exposure in telecommunications, particularly focusing on 4G and 5G networks. Standard-setting bodies like the 3GPP have been evolving standards to integrate and enhance network node features. However, these standards have not explicitly detailed the interaction mechanisms between 4G nodes, such as the Service Capabilities Exposure Function(SCEF) and the Network Exposure Function (NEF). This lack of clarity creates challenges in designing effective communication flows and interfaces within network systems. Known technologies in this field has often discussed Application Function's (AF's) interaction with NEF and SCEF through a Common API Framework (CAPIF), but these descriptions are limited in explaining the selection process between NEF and SCEF, and how AF supports necessary APIs like N33 and T8.

[0050] A system and a method disclosed simplifies network interactions by providing a single point of contact for Application Functions (AF) to manage mobile terminated (MT) messages across 4G and 5G networks. The system and the method ensure reliable delivery acknowledgments and introduces a seamless interface for message transfer between network functions and enable efficient handling of buffered MT messages during network transitions, enhancing network communication efficiency.

[0051] The system and the method disclosed an interface between a network exposure function (NEF) and a service capability exposure function (SCEF). This provides an advantage to the developer that the developer does not need to develop both application programming interfaces (APIs) of N33 and T8 with the NEF and the SCEF respectively. The application function (AF) may integrate with NEF on N33 only and the NEF communicates with the SCEF using the interface between the NEF and the SCEF. Further, the AF do not need to track the UE presence in the network while creating subscriptions. The tracking of UE presence is internally handled by the NEF using the interface between the NEF and the SCEF. So that the AF can get notification reports irrespective of UE's network.

[0052] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1A- FIG. 4.

[0053] FIG. 1 illustrates an exemplary network architecture (100) in which or with which a system (108) for changing a plurality of policy rules in a communication network is implemented, in accordance with embodiments of the present disclosure.

[0054] Referring to FIG. 1, the network architecture (100) includes one or more computing devices or user equipments (104-1, 104-2... 104-N) associated with one or more users (102-1, 102-2... 102-N) in an environment. A person of ordinary skill in the art will understand that one or more users ( 102- 1 , 102-2... 102- N) may be individually referred to as the user (102) and collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more user equipments (104-1, 104-2... 104-N) may be individually referred to as the user equipment (104) and collectively referred to as the user equipment (104). A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeably throughout the disclosure. Although three user equipments (104) are depicted in FIG. 1, however any number of the user equipments (104) may be included without departing from the scope of the ongoing description.

[0055] In an embodiment, the user equipment (104) includes smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the user equipment (104) includes, but is not limited to, smart phones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for monitoring or interacting with or for the users (102) and / or entity (110), or any combination thereof. A person of ordinary skill in the art will appreciate that the user equipment (104) may include, but is not limited to, intelligent, multi-sensing, network- connected devices, that can integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network- connected.

[0056] In an embodiment, the user equipment (104) includes, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device(e.g., a headmounted display computer device, a head-mounted camera device, a wristwatchcomputer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the user equipment (104) includes, but is not limited to, any electrical, electronic, electromechanical, or an equipment, or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, wherein the user equipment (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or the entity (110) such as touch pad, touch enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the user equipment (104) may not be restricted to the mentioned devices and various other devices may be used.

[0057] Referring to FIG. 1, the user equipment (104) is configured to communicate with the system (108), for example, a repetitive logs suppression system (208), through a network (106). In an embodiment, the network (106) includes at least one of a Fifth Generation (5G) network, 6G network, or the like. The network (106) enables the user equipment (104) to communicate with other devices in the network architecture (100) and / orwiththe system (108). The network (106) includes a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.

[0058] In another exemplary embodiment, the centralized server (112) may include or comprise, by way of example but not limitation, one or more of: a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running avirtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof.

[0059] The system (108) is configured to receive a request from a user for performing suppression of the file via an input unit. In an example, the input unit is a touch pad or a keyboard. In an embodiment, the system (108) is configured to receive the request by a command-line interface (CLI) and graphical user interface (GUI).

[0060] In an aspect, the network (106) comprises a plurality of network functions (NFs) (not shown in FIG. 1). Network functions are the logical entities or software -based functionalities that define how the network operates and processes data. The plurality of network functions comprises a session management function (SMF), a network exposure function (NEF), a service capabilities exposure function (SCEF), a mobility management function (MME) and an application function (AF).

[0061] The session management function (SMF) is responsible for managing the sessions between user devices and the network. SMF is one of the key network functions in the 5G Core Network (5GC), responsible for session management and policy control.

[0062] The network exposure function (NEF) enables the external application administrators to customize the network for providing innovative services to their end-users.

[0063] The service capabilities exposure function (SCEF) is specifically deployed in support of loT, whereby devices can use NIDD (Non-IP Data Delivery) in order to exchange data with the MME, which in turn passes that data to the SCEF for onward delivery to loT application servers.

[0064] The mobility management function (MME) manages UE access network and mobility, as well as establishing the bearer path for UE's. The MME is also concerned with the bearer activation / deactivation process.

[0065] The application function (AF) performs traffic routing, accessing network exposure function, interacting with the policy framework for policy control.

[0066] In an aspect, non-IP data delivery (NIDD) may be used to handle mobile originated (MO) and mobile terminated (MT) communication with UEs, where the data used for the communication is considered unstructured from the EPS standpoint (e.g., non-IP).

[0067] In an embodiment, the user equipment (UE) (104) may communicatively couple with a network (106). The network (106) may receive a connection request from the UE. The network (106) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request. The network (106) comprising a session management function (SMF), a network exposure function (NEF), a service capability exposure function (SCEF), a mobility management function (MME), and an application function for managing mobile terminated (MT) messages in the network (106).

[0068] In examples, the NEF receives MT messages directed to the UE (104) from the AF. The NEF determines a network type of the UE (104) by checking mapping of a non-IP data delivery (NIDD) configuration and a service message (SM) context. The NEF routes the MT messages to a network function based on the network type of the UE. The network type includes a first type of network and a second type of network. The first type of network is a fifth generation (5G) network or a sixth generation (6G) network. The second type of network type is a fourth generation (4G) network. The network function includes a first network function and a second network function. The first network function is a session management function (SMF). The second network function is a service capabilities exposure function (SCEF). For the first type of network, first network function is selected and for the second type of network, the second network function is selected. The NEF delivers the MT message to the UE (104) through the selected network function. For delivery of the MT messages to the UE attached to the first type of network (e.g., SMF), the NEF sends the MT messages to the first networkfunction. Further, the first network function (SMF) sends the MT messages to the UE attached to the first type of network (5G or 6G). Also, for delivery of the MT messages to the UE (302), the NEF sends the MT message to the second network function (e.g., SCEF) via an interface between the NEF and the second network function (e.g., SCEF). The second network function (e.g., SCEF) identifies one of plurality mobility management entities (MMEs) based on mapping of NIDD- configuration and the SM context. The second network function (e.g., SCEF) sends the MT messages to the identified MME (310). Further, the MME sends the MT messages to the UE attached to the second network function (e.g., SCEF).

[0069] Although FIG. 1 shows exemplary components of the network architecture (100), in other embodiments, the network architecture (100) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture (100) may perform functions described as being performed by one or more other components of the network architecture (100).

[0070] FIG. 2A illustrates an example block diagram (200) of a system (108), in accordance with an embodiment of the present disclosure.

[0071] Referring to FIG. 2 A, in an embodiment, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be configured to store one or more computer- readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may comprise any non-transitory storage device including, for example, volatile memory such as random-access memory (RAM), or non-volatile memory such as erasable programmable read only memory(EPROM), flash memory, and the like.

[0072] In an embodiment, the system (108) may include an interface(s) (206). The interface(s) (206) may comprise a variety of interfaces, for example, interfaces for data input and output devices (I / O), storage devices, and the like. The interface(s) (206) may facilitate communication through the system (108). The interface(s) (206) may also provide a communication pathway for one or more components of the system (108). Examples of such components include, but are not limited to, processing engine(s) (208) and a database (210). Further, the processing engine(s) (208) may include a data parameter engine (212) and other engine(s) (214). In an embodiment, the other engine(s) (214) may include but not limited to a data ingestion engine, an input / output engine, and a notification engine.

[0073] In an embodiment, the processing engine(s) (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) (208). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) (208) may be processorexecutable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine(s) (208) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) (208). In such examples, the system may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system and the processing resource. In other examples, the processing engine(s) (208) may be implemented by electronic circuitry.

[0074] Although FIG. 2A shows exemplary components of the system (108), in other embodiments, the system (108) may include fewer components, different components, differently arranged components, or additional functionalcomponents than depicted in FIG. 2A. Additionally, or alternatively, one or more components of the system (108) may perform functions described as being performed by one or more other components of the system (108).

[0075] FIG. 2B illustrates an example block diagram (200B) of a network exposure function (NEF) (222), in accordance with an embodiment of the present disclosure.

[0076] The NEF (222) comprises a processing unit (224), a receiving unit (226), a routing unit (228), a delivery facilitation unit (230) and a data buffering unit (232).

[0077] The receiving unit (226) may receive mobile terminated (MT) messages directed towards the UE from an application function (AF). In an aspect, the mobile terminated (MT) messages are messages sent from a server or an application to a user equipment (UE).

[0078] The processing unit (224) may determine a network type of the UE (302) by checking mapping of a non-IP data delivery (NIDD) configuration and a service message (SM) context. The network type comprises fourth generation (4G) and fifth generation (5G). The routing unit (228) may route the MT message to a defined network function based on the UE's network type. A session management function (SMF) is selected for the MT message delivery to UE attached to 5G and a service capabilities exposure function (SCEF) is selected for the MT message delivery to UE attached to 4G. The delivery facilitation unit (230) may deliver the MT message to the UE through the selected network function, for delivery of the MT messages to the UE attached to 5G, the NEF may send the MT message to the SMF. The SMF may send the MT message to the UE attached to 5G.

[0079] For delivery of the MT messages to the UE attached to 4G, the NEF may send the MT message to the SCEF via an interface between the NEF and the SCEF. The SCEF may identify one of plurality mobility management entities (MMEs) based on mapping of NIDD-configuration and the SM-context. The SCEF may send the MT message to the identified MME. The MME may send the MT message to the UE attached to 4G.

[0080] The NEF further comprises a data buffering unit (232) configured tostore the MT messages during transitions of the network type for the UE.

[0081] In an aspect, on detecting transition of the UE from an evolved packet core (EPC) network to a 5G core (5GC) network, the NEF may receive new SM context from the SMF. The SMF may overwrite the new SM context with a previous SM context received from MME or SCEF. The NEF may initiate delivery of the stored MT messages to the SMF. The SMF may send the received MT messages to the UE. The SMF may send a MT delivery acknowledgment received from the UE to the NEF. On detecting a request of a reliable data service (RDS) acknowledgement from the NEF, the SMF may forward a MT delivery acknowledgement (ACK) to the NEF on receiving acknowledgement from the UE.

[0082] In an aspect, on detecting the transition of the 5GC to the EPC, the SCEF may receive a new SM context from the MME. The NEF may overwrite the new SM context with a previous SM context received from the SMF. The NEF may initiate delivery ofthe stored MT messages to the SCEF via the interface. The SCEF may send the MT messages to the UE via the MME. The SCEF may send the delivery response to the NEF via the interface. On detecting a request of the RDS acknowledgement from the NEF, the MME may forward the MT delivery ACK to the SCEF on receiving acknowledgement from the UE. The SCEF may forward the MT delivery ACK to the NEF over the interface.

[0083] In an aspect, the evolved packet core (EPC) is a framework for providing converged voice and data on a 4G Long-Term Evolution (LTE) network.

[0084] In an aspect, 5G Core (5GC) is the heart of a 5G network. It establishes reliable, secure connectivity to the network for end users and provides access to its services. The core domain handles a wide variety of essential functions in the mobile network, such as connectivity and mobility management, authentication and authorization, subscriber data management and policy management.

[0085] FIG. 3 A illustrates an example flow diagram (300A) for a mobile terminating (MT) message, in accordance with embodiments of the present disclosure.

[0086] As illustrated in FIG. 3A, in an embodiment, an AF (312) may sendthe MT message towards aNEF (306). The NEF (306) being single point of contact may handle this MT message.

[0087] In an embodiment, for MT delivery to a fifth-generation core (5GC) UE (302), the NEF (306) may check non-intemet protocol data delivery (NIDD)- configuration, SM-context mapping and based on this information, the NEF (306) may forward the MT delivery to a SMF (304). The SMF (304) may forwards this MT message accordingly. The Network Exposure Function (NEF) is a component within the service-based architecture (SBA) of the 5G core network. It serves as an intermediary between external applications and the 5G core, exposing capabilities and events of the core network securely to third-party service providers or other network functions. In one aspect, SM-context refers to the set of information that describes the state of a network session for a user equipment (UE). The session management context includes details about the IP address allocation, quality of service (QoS) levels, session rules, and any other data that defines how the user's data traffic should be handled by the network. SM-context mapping is the process of associating the relevant session management context with the correct UE and network session. It involves matching the stored session information with incoming data packets so that they are routed and treated according to the policies and rules defined in the SM-context. In another aspect, the SMF (304), in the 5G network, is configured for establishing, maintaining, and terminating the session management context for UEs. The SMF (304) interacts with the UE and other core network functions to handle session management tasks, such as assigning IP addresses, deciding on the QoS treatment of user plane data, and controlling the user plane function (UPF) that routes and forwards user data traffic.

[0088] In an embodiment, for MT delivery to an EPC (UE), the NEF (306) may check service message (SM)-context and forward the MT message to the SCEF (308). EPC, Evolved Packet Core, is the core network architecture used in 4G LTE (Long Term Evolution) networks. It provides converged voice and data on a network that is purely based on packet switching. Further, the SCEF (308) may check mapping of the NIDD-configuration, SM-context for a (MME) identity and forward the MT delivery to the MME for delivery to UE (302) . In one aspect, SCEF,Service Capability Exposure Function, is a component in the 4G LTE network architecture, specifically within the Evolved Packet Core (EPC). The SCEF provides a standardized interface for exposing the services and capabilities of the EPC to third-party applications outside the operator’ s-controlled environment.

[0089] In an embodiment, the MT buffered at NEF (306) and the UE (302) may be moved from an evolved packet core (EPC) to the 5GC. In this case new SM-context may come to the NEF (306) from the SMF (304) which may overwrite the previous SM-context received from the MME / SCEF (308). Further, the NEF (306) may send delete trigger to the SCEF (308) for SM-context deletion received previously from the MME (310). Based on a new context from the SMF (304), the NEF (306) may initiate the buffered MT delivery from the SMF (304) towards the UE (302). If radio data system (RDS) acknowledgement is requested, then the SMF (304) may forward the MT delivery acknowledgement (ACK) to the NEF (306) on receiving acknowledgement from the UE (302). The Radio Data System (RDS) is a communications protocol standard for embedding small amounts of digital information in conventional FM radio broadcasts. RDS standardizes several types of information transmitted, including time, station identification and program information. The MT (Mobile Terminated) delivery acknowledgement (ACK) is a confirmation signal sent from the recipient's device (or an intermediary network entity) back to the message sender's system or network function to indicate that the mobile terminated message has been successfully delivered to the intended recipient's device.

[0090] In an embodiment, the MT buffered at the NEF (306) and the UE (302) may be moved from the 5GC to the EPC. In this case, a new SM-context may come to the SCEF (308) from the MME (310). The NEF (306) may overwrite new SM-context with a previous SM-context received from the SMF (304). The NEF (306) may initiate the buffered MT delivery to the SCEF (308). Further, the SCEF (308) may initiate the MT delivery from the MME (310) towards UE (302). The SCEF (308) may also send the delivery response to the NEF (306). If RDS acknowledgement is requested, then the MME (310) may forward the MT delivery ACK to the SCEF (308) on receiving an acknowledgement from the UE (302).Further, the SCEF (308 may forward this ACK to the NEF (306) over a defined interface between the network exposure function (NEF) and service capabilities exposure function (SCEF).

[0091] In an embodiment, the AF (312) may send the MT message towards a converged NEF (306) (i.e., the NEF being single point of contact handling the MT message delivery). For the MT delivery to 5GC UE, the NEF (306) may check NIDD-config and SM-context mapping. Based on NIDD-config and SM-context mapping, the NEF (306) may forward the MT delivery to the SMF (304). The SMF may forward the MT message to the UE accordingly. For the MT delivery to EPC UE, the NEF (306) may check SM-context and forward the MT message to the SCEF (308). Then, the SCEF (308) may check mapping of NIDD-config and SM- context for an MME identity. The SCEF (308) then forwards the MT delivery to the identified MME for delivery to UE.

[0092] As illustrated in FIG. 3A, for delivery of the MT messages to the UE attached to 5G, the below steps are performed.

[0093] At step 322, the AF (312) may send a NIDD MT data request to the NEF (306).

[0094] At step 324, the NEF may check SM-Context to NIDD configuration mapping.

[0095] At step 326, on detecting that the network type is 5G, the NEF may send a MT delivery request to the SMF (304).

[0096] At step 328, the SMF (304) may send the MT message to the UE (302) attached in 5G.

[0097] At step 330, the SMF (304) may send a MT delivery response to the NEF (306).

[0098] At step 332, the NEF (306) may send a NIDD MT delivery response to AF (312).

[0099] For delivery of the MT messages to the UE attached to 4G, the below steps are performed.

[0100] At step 334, the AF (312) may send a NIDD MT data request to the NEF (306).

[0101] At step 336, the NEF (306) may check SM-context to NIDD configuration mapping.

[0102] At step 338, on detecting that the network type is 4G, the NEF (306) may send the NIDD MT data to the SCEF (308).

[0103] At step 340, the SCEF (308) may send a MT deliver request to the MME (310).

[0104] At step 342, the MME (310) may send the MT message to the UE (302) attached in 4G.

[0105] At step 344, the MME (310) may send a MT delivery response to the SCEF (308).

[0106] At step 346, the SCEF (308) may send the MT delivery response to the NEF (306).

[0107] At step 348, the NEF (306) may send the MT delivery response to the AF (312).

[0108] FIG. 3B illustrates an example flow diagram (300B) for a mobile terminating (MT) message delivery, in accordance with embodiments of the present disclosure.

[0109] As illustrated in FIG. 3B, at step 352, receiving, by a network exposure function (NEF) (306), MT messages directed towards a user equipment (UE) (302) from the AF (312).

[0110] At step 354, determining, by the NEF (306), a network type of the UE (302) by checking mapping of a non-IP data delivery (NIDD) configuration and a service message (SM) context, the network type comprises fourth generation (4G) and fifth generation (5G).

[0111] At step 356, routing, by the NEF (306), the MT messages to a network function based on the network type of the UE (104, 302). The network type includes a first type of network and a second type of network. The first type of network is a 5G network or a 6G network. The second type of network type is a 4G network. The network function includes a first network function and a second network function. The first network function is a SMF (304). The second network function is a SCEF (308). For the first type of network, first network function isselected and for the second type of network, the second network function is selected.

[0112] At step 358, delivering, by the NEF (306), the MT message to the UE (302) through the selected network function.

[0113] At step 360, for delivery of the MT messages to the UE attached to 5G, steps 360-1 and 360-2 are performed.

[0114] At step 360-1, sending, by the NEF (306), the MT messages to the first network function.

[0115] At step 360-2, sending, by the first network function (the SMF (304)), the MT messages to the UE (302) attached to the first type of network.

[0116] At step 362, for delivery of the MT messages to the UE attached to 4G, steps 362-1 and 362-2 are performed.

[0117] At step 362-1, sending, by the NEF (306), the MT message to the second network function (the SCEF (308)) via an interface between the NEF (306) and the second network function.

[0118] At step 362-2, identifying, by the second network function (the SCEF (308)), one of plurality mobility management entities (MMEs) based on mapping of NIDD-configuration and the SM-context.

[0119] At step 362-3, sending, by the second network function (the SCEF (308)), the MT messages to the identified MME (310).

[0120] At step 362-4, sending, by the MME (310), the MT messages to the UE (302) attached to the second network function.

[0121] FIG. 4 illustrates an example computer system (400) in which or with which the embodiments of the present disclosure may be implemented.

[0122] As shown in FIG. 4, the computer system (400) may include an external storage device (410), a bus (420), a main memory (430), a read-only memory (440), a mass storage device (450), a communication port(s) (460), and a processor (470). A person skilled in the art will appreciate that the computer system (400) may include more than one processor and communication ports. The processor (470) may include various modules associated with embodiments of the present disclosure. The communication port(s) (460) may be any of an RS-232 portfor use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) (460) may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (400) connects.

[0123] In an embodiment, the main memory (430) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (440) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information e.g., start-up or basic input / output system (BIOS) instructions for the processor (470). The mass storage device (450) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Lirewire interfaces).

[0124] In an embodiment, the bus (420) may communicatively couple the processor(s) (470) with the other memory, storage, and communication blocks. The bus (420) may be, e.g. a Peripheral Component Interconnect PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (470) to the computer system (400).

[0125] In another embodiment, operator and administrative interfaces, e.g., a display, keyboard, and cursor control device may also be coupled to the bus (420) to support direct operator interaction with the computer system (400). Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (460). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (400) limit the scope of the present disclosure.

[0126] The computer system (400) also incorporates an alternative configuration of the present disclosure. The network system is configured to facilitate the handling of mobile terminated (MT) messages in a seamless and efficient manner across evolving telecommunications network environments. The system employs an integrated approach for managing MT messages, particularly when the user equipment (UE) transitions between different network domains, such as from an Evolved Packet Core (EPC) to a Fifth Generation Core (5GC) and vice versa.

[0127] The network system comprises a Network Exposure Function (NEF) that serves as a centralized gateway for receiving MT messages from Application Functions (AF). The NEF is equipped with a decision-making module that determines the current network domain of the UE, whether EPC or 5GC. Depending on this determination, the NEF utilizes a dynamic routing mechanism to forward the MT message to either the Service Capabilities Exposure Function (SCEF) for EPC UEs or the Session Management Function (SMF) for 5GC UEs.

[0128] A buffering and rerouting module within the NEF is configured for managing MT messages when there is a change in the network domain of the UE. The buffering and rerouting module ensures that MT messages are held securely during the transition and then forwarded to the new network function corresponding to the UE's updated network context.

[0129] The system further includes a sophisticated acknowledgment mechanism to ensure that delivery confirmations for MT messages are accurately relayed back to the AF. Such mechanism is configured to operate effectively even when the UE undergoes network handovers, guaranteeing that acknowledgment of message delivery is consistently provided.

[0130] In the event of a network domain change for the UE, the NEF communicates with both the SCEF and the SMF to update the MT message routing and to manage the context information associated with the UE. The NEF executes context synchronization processes, which involves deleting outdated context information from one network function and establishing new context parameters with another, thereby maintaining the integrity and continuity of the messagedelivery process.

[0131] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.ADVANTAGES OF THE INVENTION

[0132] The present disclosure provides a system and a method that mitigates the complexity of data transfers (such as managing multiple protocols / data transfer mechanisms / certificates / security related protocols / end point IP connection details and data connection management) between network elements.

[0133] The present disclosure provides a system and a method that provides a single point of contact to an application function (AF) for sending a mobile terminating (MT) message.

[0134] The present disclosure provides a system and a method that delivers a MT delivery Acknowledgement at the AF if a radio data system (RDS) is supported at a user equipment (UE) irrespective of UE network handovers.

[0135] The present disclosure provides a system and a method that uses an interface which handles seamless MT messages and acknowledges a transfer between a network exposure function (NEF) and a service capabilities exposure function (SCEF).

[0136] The present disclosure provides a system and a method that enables the NEF to handle delivery of buffered MT messages irrespective of the UE being in a fourth generation (4G) or a fifth generation (5G) network.

Claims

CLAIMSWe Claim:

1. A system for managing mobile terminated (MT) messages in a network (108) by a network exposure function (NEF) (222, 306), the NEF (222, 306) comprising: a receiving unit (226) configured to receive MT messages directed towards a user equipment (UE) (302) from an application function (AF) (312); a processing unit (224) configured to determine a network type of the UE (302) by checking a mapping of a non-IP data delivery (NIDD) configuration and a service message (SM) context; a routing unit (228) configured to route the MT message to a network function based on the network type of the UE, wherein the network type comprises a first type of network and a second type of network, wherein the network function comprising a first network function and a second network function, and wherein for the first type of network, first network function is selected and for the second type of network, the second network function is selected; and a delivery facilitation unit (230) configured to deliver the MT message to the UE through the selected network function, wherein: for delivery of the MT messages to the UE (302) attached to the first type of network, the NEF (306) is configured to send the MT message to the first network function, the first network function is configured to send the MT message to the UE connected to the first type of network, wherein for delivery of the MT messages to the second network function, the NEF (306) is configured to send the MT message to the second network function via an interface between the NEF (306) and the second network function;the second network function configured to identify one of plurality mobility management entities (MMEs) based on mapping ofNIDD-configuration and the SM context; the second network function configured to send the MT message to the identified MME (310); and the MME (310) configured to send the MT message to the UE attached to the second type of network.

2. The system of claim 1, wherein the first type of network is a fifth generation (5G) network or a sixth generation (6G) network and the first network function is a session management function (SMF) (304), wherein the second type of network type is a fourth generation (4G) network, and the second network function is a service capabilities exposure function (SCEF), wherein the NEF (306) facilitates the communication between the first type of network and the second type of network via the interface.

3. The system of claim 2, wherein the NEF (306) further comprises a data buffering unit (232) configured to store the MT messages during transitions between an evolved packet core (EPC) network and a 5G core (5GC) network for the UE.

4. The system of claim 3, further comprises: on detecting the transition of the UE from the EPC network to the 5GC network, the NEF (306) is configured to receive new SM context from the SMF (304), wherein the SMF (304) is configured to overwrite the new SM context with a previous SM context received from MME (310) or SCEF (308); the NEF (306) configured to initiate delivery of the stored MT messages to the SMF (304);the SMF (304) configured to send the received MT messages to the UE (302); and the SMF (304) configured to send a MT delivery acknowledgment received from the UE to the NEF (306).

5. The system of claim 3, further comprises: on detecting transition of the 5GC to the EPC network, the SCEF (308) configured to receive a new SM context from the MME (310); the NEF (306) configured to overwrite the new SM context with a previous SM context received from the SMF (304); the NEF (306) configured to initiate delivery of the stored MT messages to the SCEF (308) via the interface; the SCEF (308) configured to send the MT messages to the UE (302) via the MME (310); and the SCEF (308) configured to send a delivery response to the NEF (306) via the interface.

6. The system of claim 4 further comprises: on detecting a request for a reliable data service (RDS) acknowledgment from the NEF (306), the SMF (304) configured to forward an MT delivery acknowledgment (ACK) to the NEF (306) on receiving acknowledgment from the UE (302).

7. The system of claim 4 further comprises: on detecting a request for an RDS acknowledgement from the NEF (306), the MME (310) configured to forward the MT delivery ACK to the SCEF (308) on receiving acknowledgement from the UE (302); and the SCEF (308) configured to forward the MT delivery ACK to the NEF (306) over the interface.

8. A method for managing mobile terminated (MT) messages in a network (106), the method comprising: receiving, by a network exposure function (NEF) (306), MT messages directed to a user equipment (UE) (104, 302) from an application function (AF) (312); determining, by the NEF (306), a network type of the UE (104, 302) by checking mapping of a non-IP data delivery (NIDD) configuration and a service message (SM) context; routing, by the NEF (306), the MT messages to a network function based on the network type of the UE (104, 302), wherein the network type comprises a first type of network and a second type of network, wherein the network function comprising a first network function and a second network function, and wherein for the first type of network, first network function is selected and for the second type of network, the second network function is selected; and delivering, by the NEF (306), the MT message to the UE (104, 302) through the selected network function, wherein: for delivery of the MT messages to the UE (302) attached to the first type of network, sending, by the NEF (306), the MT messages to the first network function; and sending, by the first network function, the MT messages to the UE (302) attached to the first type of network; for delivery of the MT messages to the UE (302), sending, by the NEF (306), the MT message to the second network function via an interface between the NEF (306) and the second network function; identifying, by the second network function, one of plurality mobility management entities (MMEs) based on mapping of NIDD- configuration and the SM context; sending, by the second network function, the MT messages to the identified MME (310); andsending, by the MME (310), the MT messages to the UE (302) attached to the second network function.

9. The method of claim 8, wherein the first type of network is a fifth generation (5G) network or a sixth generation (6G) network and the first network function is a session management function (SMF) (304), wherein the second type of network type is a fourth generation (4G) network, and the second network function is a service capabilities exposure function (SCEF), wherein the NEF (306) facilitates the communication between the first type of network and the second type of network.

10. The method claimed as in claim 9, further comprising: storing, by the NEF (306), the MT messages during transitions of the UE (302) between transitions between an evolved packet core (EPC) network and a 5G core (5GC) network for the UE.

11. The method claimed as in claim 10, further comprising: on detecting transition of the UE (302) from the EPC network to the 5GC network, receiving, by the NEF (306), a new SM context from the SMF (304), wherein the SMF (304) configured to overwrite the new SM context with a previous SM context received from MME (310) or SCEF (308); initiating, by the NEF (306), delivery of the stored MT messages to the SMF (304); sending, by the SMF (304), the received MT messages to the UE (302); and sending, by the SMF (304), a MT delivery acknowledgment received from the UE (302) to the NEF (306).

12. The method claimed as in claim 10, further comprising:on detecting transition of the 5GC to the EPC network, receiving, by the SCEF (308), a new SM context from the MME (310); overwriting, by the NEF (306), the new SM context with a previous SM context received from the SMF (304); initiating, by the NEF (306), delivery of the stored MT messages to the SCEF (308) via the interface; sending, by the SCEF (308), the MT messages to the UE via the MME (310); and sending, by the SCEF (308), a delivery response to the NEF (306) via the interface.

13. The method claimed as in claim 11, further comprising: on detecting a request of a reliable data service (RDS) acknowledgement from the NEF (306), forwarding, by the SMF (304), a MT delivery acknowledgement (ACK) to the NEF (306) on receiving acknowledgement from the UE (302).

14. The method claimed as in claim 11, further comprising: on detecting a request of a RDS acknowledgement from the NEF (306), forwarding, by the MME (310), the MT delivery ACK to the SCEF (308) on receiving acknowledgement from the UE (302); and forwarding, by the SCEF (308), the MT delivery ACK to the NEF (306) over the interface.

15. A user equipment (UE) (104, 302) communicatively coupled with a network (106), the coupling comprises steps of: receiving, by the network (106), a connection request; sending an acknowledgment of the connection request to the UE (104, 302); and transmitting a plurality of signals in response to the connection request, wherein the network comprising a first network function, a networkexposure function (NEF) (306), a second network function, a mobility management function (MME) (310), and an application function (312) implementing a method for managing mobile terminated (MT) messages in the network (106) as claimed in claim 7.

16. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for managing mobile terminated (MT) messages in a network (106), the method comprising: receiving, by a network exposure function (NEF) (306), MT messages directed to a user equipment (UE) (104, 302) from an application function (AF) (312); determining, by the NEF (306), a network type of the UE (104, 302) by checking mapping of a non-IP data delivery (NIDD) configuration and a service message (SM) context; routing, by the NEF (306), the MT messages to a defined network function based on the network type of the UE, wherein the network type comprises a first type of network and a second type of network, wherein the network function comprising a first network function and a second network function, and wherein for the first type of network, first network function is selected and for the second type of network, the second network function is selected; delivering, by the NEF (306), the MT message to the UE (104, 302) through the selected network function, wherein: for delivery of the MT messages to the UE (302) attached to the first type of network, sending, by the NEF (306), the MT messages to the first network function; and sending, by the to the first network function, the MT messages to the UE (302) attached to the first network function, wherein for delivery of the MT messages to the UE (302) to thesecond network function, sending, by the NEF (306), the MT message to the second network function via an interface between the NEF (306) and the second network function; identifying, by the second network function, one of plurality mobility management entities (MMEs) based on mapping of NIDD- configuration and the SM context; sending, by the second network function, the MT messages to the identified MME (310); and sending, by the MME (310), the MT messages to the UE (302) attached to the second network function.

Images