Search

EP-4740511-A1 - METHOD AND SYSTEM FOR OPTIMIZATION OF DEVICE TRIGGERING PROCEDURE FOR IOT DEVICES

EP4740511A1EP 4740511 A1EP4740511 A1EP 4740511A1EP-4740511-A1

Abstract

The present disclosure relates to a method and a system for optimization of device triggering procedure for Internet of Things (IoT) device(s) [300id] in exposure function [300ef] The disclosure encompasses configuring a Data-Coding-Scheme (DCS); receiving device triggering requests over a standard interface; extracting one of: the DCS from the device triggering requests based on a custom header, and a pre- maintained default DCS; and optimizing the device triggering procedure for the IoT devices [300id] based on the DCS fetched from the device triggering requests.

Inventors

  • BHATNAGAR, AAYUSH
  • SINGH, Kumar Gaurav
  • SINGH, AMIT KUMAR

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260513
Application Date
20240611

Claims (19)

  1. We Claim 1. A method [400] for optimization of a device triggering procedure for one or more Internet of Things (IoT) devices [300id] in an exposure function [300ef], the method [400] comprises: configuring, by a configuration unit [301] for each service consumer [300sc] among one or more service consumers [300sc], a Data-Coding-Scheme (DCS), wherein each DCS is associated with a one or more device triggering requests for the one or more Internet of Things (IoT) devices [300id]; receiving, by a transceiver unit [302] at the exposure function [300ef] from each service consumer [300sc] among the one or more service consumers [300sc], the one or more device triggering requests over a standard interface; extracting, by the an extraction unit [303], via the exposure function [300ef], one of: the DCS from the one or more device triggering requests based on a custom header of said each of the one or more device triggering requests in an event of presence of the custom header in the one or more device triggering requests, and a pre-maintained default DCS in an event of absence of the custom header in the one or more device triggering requests; and optimizing, by an optimization unit [304] the device triggering procedure for the one or more Internet of Things (IoT) devices [300id] based on the DCS fetched from said each of the one or more device triggering requests.
  2. 2. The method [400] as claimed in claim 1, wherein the exposure function [300ef] is one of a Service Capability Exposure Function (SCEF) and a Network Exposure Function (NEF).
  3. 3. The method [400] as claimed in claim 1, wherein the service consumer [300sc] is one of a Services Capability Server (SCS), an Application Server (AS) and an Application Function (AF).
  4. 4. The method [400] as claimed in claim 1, wherein the standard interface is a standard T8/N33 interface.
  5. 5. The method [400] as claimed in claim 1, wherein the custom header is a “devicePayloadFormat” custom header.
  6. 6. The method [400] as claimed in claim 1, wherein to optimize the device triggering procedure for the one or more Internet of Things (IoT) devices [300id], the method [400] comprises configuring by the optimization unit [304] for the exposure function [300ef], the at least one DCS fetched from said each of the one or more device triggering requests.
  7. 7. The method [400] as claimed in claim 1, wherein the pre-maintained default DCS is maintained by the exposure function [300ef] for each of the one or more device triggering requests of each service consumer [300sc], at a time of onboarding of each service consumer [300sc].
  8. 8. The method [400] as claimed in claim 1, the method [400] comprises enabling by a balancing unit [305], one or more load balancers (LBs) to load balance the one or more device triggering requests.
  9. 9. A system [300] for optimization of a device triggering procedure for one or more Internet of Things (IoT) devices [300id] in an exposure function [300ef], the system [300] comprises: - a configuration unit [301] to configure, for each service consumer [300sc] among one or more service consumers [300sc], a Data-Coding-Scheme (DCS) from one or more DCSs, wherein each DCS is associated with one or more device triggering requests for the one or more Internet of Things (IoT) devices [300id], - a transceiver unit [302] connected to at least the configuration unit [301], the transceiver unit [302] configured to receive, at the exposure function [300ef] from each service consumer [300sc] among the one or more service consumers [300sc], the one or more device triggering request over a standard interface; - an extraction unit [303] connected to at least the transceiver unit [302], the extraction unit [303] configured to extract, via the exposure function [300ef], one of: the DCS from the one or more device triggering requests based on a custom header of said each of the one or more device triggering requests in an event of presence of the custom header in the one or more device triggering requests, and a pre-maintained default DCS in an event of absence of the custom header in the one or more device triggering requests, and - an optimization unit [304] connected to at least the extraction unit [303], the optimization unit [304] configured to optimize, the device triggering procedure for the one or more Internet of Things (IoT) devices [300id] based on the DCS extracted from said each of the one or more device triggering requests.
  10. 10. The system [300] as claimed in claim 9, wherein the exposure function [300ef] is one of a Service Capability Exposure Function (SCEF) and a Network Exposure Function (NEF).
  11. 11. The system [300] as claimed in claim 9, wherein the service consumer [300sc]is one of a Services Capability Server (SCS), an Application Server (AS) and an Application Function (AF).
  12. 12. The system [300] as claimed in claim 9, wherein the standard interface is a standard T8/N33 interface.
  13. 13. The system [300] as claimed in claim 9, wherein the custom header is a “devicePayloadFormat” custom header.
  14. 14. The system [300] as claimed in claim 9, wherein to optimize the device triggering procedure for the one or more Internet of Things (IoT) devices [300id], the at least one optimization unit [304] is further configured to configure for the exposure function [300ef], the at least one DCS fetched from said each of the device triggering requests.
  15. 15. The system [300] as claimed in claim 9, wherein the pre-maintained default DCS is maintained by the exposure function [300ef] for each of the one or more device triggering requests of each service consumer [300sc], at a time of onboarding of each service consumer [300sc].
  16. 16. The system [300] as claimed in claim 9, wherein a balancing unit [305] is configured to enable one or more load balancers to load balance the one or more device triggering requests.
  17. 17. A User Equipment (UE) device receiving, the UE device comprising: a transceiver unit configured to: receive, a device triggering, from a system [300], via a Short Message Service Center (SMSC), wherein the system [300] performs optimization of a device triggering procedure for the UE device before the device triggering is sent to the UE device, wherein the system [300] comprises: a configuration unit [301], wherein the configuration unit [301] is configured to configure, for each service consumer [300sc] among one or more service consumers [300sc], a Data-Coding-Scheme (DCS) from one or more DCSs, wherein each DCS is associated with one or more device triggering requests for the UE device; a transceiver unit [302] configured to receive, at an exposure function [300ef] from each service consumer [300sc] among the one or more service consumers [300sc], the one or more device triggering requests over a standard interface; an extraction unit [303] configured to extract, via the exposure function [300ef], one of: the DCS from the one or more device triggering requests based on a custom header of said each of the one or more device triggering requests in an event of presence of the custom header in the one or more device triggering requests, and a pre-maintained default DCS in an event of absence of the custom header in the one or more device triggering requests; and an optimization unit [304] configured to optimize, the device triggering procedure for the UE device based on the DCS extracted from said each of the one or more device triggering requests.
  18. 18. The UE device as claimed in claim 17, wherein the UE device belongs to a group consisting of one or more Internet of Things (IoT) devices.
  19. 19. A non-transitory computer-readable storage medium storing instructions for optimization of a device triggering procedure for one or more Internet of Things (IoT) devices [300id] in an exposure function [300ef], the storage medium comprising executable code which, when executed by one or more units of a system, causes: - a configuration unit [301] to configure, for each service consumer [300sc] among one or more service consumers [300sc], a Data-Coding-Scheme (DCS) from one or more DCSs, wherein each DCS is associated with a one or more device triggering requests for the one or more IoT devices [300id]; - a transceiver unit [302] connected to at least the configuration unit [301], the transceiver unit [302] to receive, at the exposure function [300ef], from each service consumer [300sc] among the one or more service consumers [300sc], the one or more device triggering requests over a standard interface; - an extraction unit [303] connected to at least the transceiver unit [302], the extraction unit [303] to extract, via the exposure function [300ef], one of: the DCS from the one or more device triggering requests based on a custom header of said each of the one or more device triggering requests in an event of presence of the custom header in the one or more device triggering requests, and a pre-maintained default DCS in an event of absence of the custom header in the one or more device triggering requests; and - an optimization unit [304] connected to at least the extraction unit [303], the optimization unit [303] to optimize, the device triggering procedure for the one or more Internet of Things (IoT) devices [300id] based on the DCS extracted from said each of the one or more device triggering requests.

Description

METHOD AND SYSTEM FOR OPTIMIZATION OF DEVICE TRIGGERING PROCEDURE FOR IoT DEVICES FIELD OF INVENTION [0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to a method and a system for optimization of device triggering procedure for the Internet of Things (IoT) device(s) in exposure function. BACKGROUND [0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art. [0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analogue technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third- generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users. [0004] IoT (Internet of Things) devices are physical objects embedded with sensors, software, and connectivity features that enable them to collect, exchange, and act upon data with minimal human intervention. The IoT devices are interconnected through the internet or other communication networks to enable remote monitoring, control, and automation of various tasks. Further, the Internet of Things (IoT) devices such as wearable technologies, smart locks, smoke detectors, home automation devices, motion Detectors etc., are connected to Communication servers in order to send alerts, notifications, and/or information about various events such as trespass, accidental falls, burglary etc. In a communication network (preferably a 5G communication network), all the IoT devices perform various task such but not limited to handling loads, introduction of new 5G use cases, etc. In a 5G communication network, the IoT devices communicate with each other via Network Exposure Functions (NEF) through a process facilitated by the NEF's capabilities to expose network resources and services. The Network exposure (sometimes exposure function), or service exposure refers to the functionality of the communication network that helps in making network capabilities, such as data and network services, easily available for communication service providers and third parties. The exposure function is responsible for securely exposing the network capabilities to application function. The NEF acts as an intermediary that enables IoT devices to access and utilize network functions, data, and resources provided by the underlying network infrastructure. This is done with the help of standardized Application Programming Interfaces (APIs) exposed by the NEF. The IoT devices can interact with each other, exchange data, and collaborate on various applications and services with the help of exposure function. For e.g., a communication done between Application Programming Interfaces (APIs) by sharing data via a Service Capability Exposure Function (SCEF)/ NEF from the Capability Server (CS)/ Application Server (AS)/ Application Function (AF). The APIs provided by the Exposure Functions may include but not limited to Subscriber Data API, QoS (Quality of Service) Management API, Session Management API etc. These APIs are generally configured on predefined rules and conditions such as standardized protocols and are exposed by the Exposure Function to authorized third-party applications through secure authentication and authorization mechanisms. The SCEF is responsible for exposing network capabilities and services to authorize third-party applications. The SCEF provides standardized APIs for accessing network functions, data, and resources, enabling developers to create innovative services and applications. While the NEF serves as an interface between the network infrastructure and external applications in the 5G environment. It exposes network resources and services through standardized APIs, allowing authorized third-party applications to access and util