Search

EP-4740492-A1 - SYSTEM AND METHOD FOR MANAGING MOBILE TERMINATED MESSAGE IN A NETWORK

EP4740492A1EP 4740492 A1EP4740492 A1EP 4740492A1EP-4740492-A1

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.

Inventors

  • BHATNAGAR, AAYUSH
  • SINHA, ANURAG
  • Khan, Rijvan
  • BAVISHI, Hardik Navinbhai
  • BISHT, SANDEEP
  • SINGH, Kumar Gaurav
  • Sanas, Nilesh
  • SINGH, AMIT KUMAR
  • Bhushan, Raghvendra
  • Kale, Mangesh Shantaram
  • JAIN, GAURAV

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260513
Application Date
20240603

Claims (16)

  1. 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. 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. 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. 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. 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. 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. 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. 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); and sending, by the MME (310), the MT messages to the UE (302) attached to the second network function.
  9. 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. 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. 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. 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. 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. 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. 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 network exposure 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. 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 the second 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.

Description

SYSTEM AND METHOD FOR MANAGING MOBILE TERMINATED MESSAGE IN A NETWORK RESERVATION 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 [003] 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. [004] 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. [005] 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. [006] 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. [007] 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 [008] 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. [009] 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 selec