WO2025008879A1 - Procédé et système d'optimisation de procédure de déclenchement de dispositif pour dispositifs iot - Google Patents

Procédé et système d'optimisation de procédure de déclenchement de dispositif pour dispositifs iot Download PDF

Info

Publication number
WO2025008879A1
WO2025008879A1 PCT/IN2024/050749 IN2024050749W WO2025008879A1 WO 2025008879 A1 WO2025008879 A1 WO 2025008879A1 IN 2024050749 W IN2024050749 W IN 2024050749W WO 2025008879 A1 WO2025008879 A1 WO 2025008879A1
Authority
WO
WIPO (PCT)
Prior art keywords
device triggering
dcs
requests
exposure function
unit
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/IN2024/050749
Other languages
English (en)
Inventor
Aayush Bhatnagar
Kumar Gaurav SINGH
Amit Kumar Singh
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jio Platforms Ltd
Original Assignee
Jio Platforms Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jio Platforms Ltd filed Critical Jio Platforms Ltd
Publication of WO2025008879A1 publication Critical patent/WO2025008879A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • 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.
  • IoT Internet of Things
  • 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.
  • 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.
  • 2G second-generation
  • 3G third-generation
  • 4G fourth-generation
  • the fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security.
  • 5G fifth-generation
  • wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
  • IoT Internet of Things
  • the IoT 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.
  • 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.
  • 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.
  • 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.
  • APIs Application Programming Interfaces
  • 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.
  • a device triggering request refers to a signal/ prompt sent from one device (preferably an IoT device) to another IoT device to perform a specific task or action.
  • the device triggering request is governed as per a predefined protocol that is required in implementation of the receipt of the device triggering request thus ensuring seamless interaction and optimal performance of the communication network.
  • the data shared by the APIs via the SCEF/NEF is to be encoded with Data-Coding-Scheme (DCS) for device trigger payload.
  • DCS Data-Coding-Scheme
  • the DCS here refers to a parameter that specifies the encoding and formatting scheme used for representing data.
  • the DCS defines how the data is structured, encoded, and interpreted by the network elements. It may include information such as data format, compression method, character set, and error detection/correction mechanisms, allowing efficient and reliable transmission of trigger-related information between the IoT devices and network components.
  • the device trigger payload refers to the data/ information included in a message sent from a service consumer such as but not limited to Services Capability Server/ Application Server and an Application Function.
  • the device trigger payload helps in initiating a specific action or event in one or more Internet of Things (IoT) devices.
  • the device trigger payload typically contains instructions, parameters, or identifiers necessary in the predefined protocols of the device triggering request, for the targeted IoT devices to perform the desired action.
  • the payload may include various types of data, such as configuration settings, commands, or status updates, depending on the specific requirements of the triggering operation.
  • 3GPP 3rd Generation Partnership Project
  • the SCEF/NEF does not get the information from the SCS/AS/AF to allow the data to be conveyed via SCEF/ NEF about the intended DCS for the data to be shared using the APIs.
  • the SCEF/NEF are configured to share data of a pre-defined DCS format only because of limitation of the existing 3GPP standard specification. Any data shared which is not of the pre- defined DCS format does not reach the intended target which, in turn, leads to failure of data transmittal.
  • a device trigger procedure for the IoT device in the 5G communication network refers to the sequence of actions and signalling processes involved in initiating a specific action or event.
  • the device trigger procedure typically includes the transmission of trigger commands or messages from a service consumer to the targeted IoT devices, thereby triggering the execution of predefined tasks or operations, such as data collection, device activation, or event reporting.
  • various solutions have been developed to improve the performance of communication devices for enhancement in device triggering procedure for IoT device(s) to specify/configure intended Data-Coding-Scheme (DCS) for each Services Capability Server (SCS)/ Application Server (AS)/ Application Function (AF) to allow the data to be conveyed via Service Capability Exposure Function (SCEF) or Network Exposure Function (NEF) to one or more intended IoT Devices.
  • DCS Data-Coding-Scheme
  • SCEF Service Capability Exposure Function
  • NEF Network Exposure Function
  • An aspect of the present disclosure may relate to a method for optimization of a device triggering procedure for one or more Internet of Things (IoT) devices in an exposure function.
  • the method comprises configuring, by a configuration unit for each service consumer among one or more service consumers, a Data-Coding-Scheme (DCS).
  • DCS Data-Coding-Scheme
  • each DCS is associated with a one or more device triggering requests for the one or more Internet of Things (IoT) devices.
  • the method further comprises receiving by a transceiver unit at the exposure function from each service consumer among the one or more service consumers, the one or more device triggering requests over a standard interface.
  • the method further comprises extracting, by an extraction unit, via the exposure function, 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.
  • the method further comprises optimizing, by an optimization unit the device triggering procedure for the one or more Internet of Things (IoT) devices based on the DCS fetched from said each of the one or more device triggering requests.
  • the exposure function is one of a Service Capability Exposure Function (SCEF) and a Network Exposure Function (NEF).
  • SCEF Service Capability Exposure Function
  • NEF Network Exposure Function
  • the service consumer is one of a Services Capability Server (SCS), an Application Server (AS) and an Application Function (AF).
  • the standard interface is a standard T8/N33 interface.
  • the custom header is a “devicePayloadFormat” custom header.
  • the method further comprises configuring by the optimization unit, for the exposure function, the at least one DCS fetched from said each of the one or more device triggering requests.
  • the pre- maintained default DCS is maintained by the exposure function for each of the one or more device triggering requests of each service consumer, at a time of onboarding each of the service consumer.
  • the method further comprises enabling by a balancing unit, one or more load balancers (LBs) to load balance the one or more device triggering requests.
  • LBs load balancers
  • Another aspect of the present disclosure may relate to a system [300] for optimization of a device triggering procedure for one or more Internet of Things (IoT) devices in an exposure function.
  • the system comprises a configuration unit to configure, for each service consumer among one or more service consumers, a Data-Coding-Scheme (DCS) from one or more DCSs. It is to be noted that each DCS is associated with a one or more device triggering requests for the one or more IoT devices.
  • the system further comprises a transceiver unit connected to at least the configuration unit.
  • the transceiver unit is configured to receive, at the exposure function, from each service consumer among the one or more service consumers, the one or more device triggering requests over a standard interface.
  • the system further comprises an extraction unit connected to at least the transceiver unit.
  • the extraction unit is configured to extract, via the exposure function, 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.
  • the system further comprises an optimization unit connected to at least the extraction unit.
  • the optimization unit is configured to optimize, the device triggering procedure for the one or more Internet of Things (IoT) devices based on the DCS extracted from said each of the one or more device triggering requests.
  • IoT Internet of Things
  • the instructions include executable code which, when executed by one or more units of a system, causes: a configuration unit to configure, for each service consumer among one or more service consumers, a Data- Coding-Scheme (DCS) from one or more DCSs.
  • DCS Data- Coding-Scheme
  • each DCS is associated with a one or more device triggering requests for the one or more IoT devices; a transceiver unit to receive, at the exposure function, from each service consumer among the one or more service consumers, the one or more device triggering requests over a standard interface; an extraction unit to extract, via the exposure function, 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 to optimize, the device triggering procedure for the one or more Internet of Things (IoT) devices based on the DCS extracted from said each of the one or more device triggering requests.
  • IoT Internet of Things
  • the UE device comprises a transceiver unit configured to receive, a device triggering, from a system, via a Short Message Service Center (SMSC), wherein the system performs optimization of a device triggering procedure for the UE device before the device triggering request is sent to the UE device.
  • the system further comprises a configuration unit configured to configure, for each service consumer among one or more service consumers, a Data-Coding-Scheme (DCS) from one or more DCSs, wherein each DCS is associated with the one or more device triggering requests for the UE device.
  • DCS Data-Coding-Scheme
  • the system further comprises a transceiver unit configured to receive, at an exposure function from each service consumer among the one or more service consumers, the one or more device triggering requests over a standard interface.
  • the system further comprises an extraction unit configured to extract, via the exposure function, 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.
  • the system further comprises an optimization unit 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.
  • OBJECTS OF THE INVENTION Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below. [00022] It is an object of the present disclosure to provide a system and a method for enhancement in device triggering procedure for Internet of Things (IoT). [00023] It is another object of the present disclosure to specify/configure intended Data- Coding-Scheme (DCS) for each of the Services Capability Server (SCS)/ Application Server (AS)/ Application Function (AF). [00024] It is an object of the present disclosure to allow the data to be conveyed via Service Capability Exposure Function (SCEF) or Network Exposure Function (NEF) to one or more intended IoT Devices.
  • SCEF Service Capability Exposure Function
  • NEF Network Exposure Function
  • FIG.1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.
  • FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
  • FIG. 31 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
  • FIG. 3 illustrates an exemplary block diagram of a system [300] for optimization of a device triggering procedure for one or more Internet of Things (IoT) devices in an exposure function, in accordance with exemplary implementations of the present disclosure.
  • FIG. 4 illustrates a method [400] flow diagram for optimizing a device triggering procedure for one or more Internet of Things (IoT) devices in an exposure function, in accordance with exemplary implementations of the present disclosure.
  • FIG. 4 illustrates a method [400] flow diagram for optimizing a device triggering procedure for one or more Internet of Things (IoT) devices in an exposure function, in accordance with exemplary implementations of the present disclosure.
  • FIG. 4 illustrates a method [400] flow diagram for optimizing a device triggering procedure for one or more Internet of Things (IoT) devices in an exposure function, in accordance with exemplary implementations of the present disclosure.
  • FIG. 4 illustrates a method [400] flow diagram for optimizing a device triggering procedure for one or more Internet of Things (
  • FIG. 5 illustrates an exemplary block diagram of a system [500] for enhancement in device triggering procedure for Internet of Things (IoT) to allow the data to be conveyed from the SCS/AS/AF via Service Capability Exposure Function (SCEF) or Network Exposure Function (NEF) to one or more intended IoT Devices, in accordance with exemplary embodiments of the present disclosure.
  • FIG. 6 illustrates an exemplary method [600] flow diagram indicating the process for enhancement in device triggering procedure for Internet of Things (IoT) to allow the data to be conveyed from the SCS/AS/AF via Service Capability Exposure Function (SCEF) or Network Exposure Function (NEF) to one or more intended IoT Devices, in accordance with exemplary embodiments of the present disclosure.
  • SCEF Service Capability Exposure Function
  • NEF Network Exposure Function
  • 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.
  • the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
  • a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions.
  • a processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc.
  • the processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
  • a user equipment may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure.
  • the user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure.
  • the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
  • “storage unit” or “memory unit” refers to a machine or computer- readable medium including any mechanism for storing information in a form readable by a computer or similar machine.
  • a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media.
  • the storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
  • interface refers to a shared boundary across which two or more separate components of a system exchange information or data.
  • the interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
  • All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
  • the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
  • FIG.1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in FIG.
  • the 5GC network architecture includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management (UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data network (DN) [130], wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.
  • UE user equipment
  • RAN radio access network
  • AMF Access and mobility management
  • Radio Access Network [104] is the part of a mobile telecommunications system that connects user equipment (UE) [102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
  • Access and Mobility Management Function AMF
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • SMF Session Management Function
  • Service Communication Proxy (SCP) [110] is a network function in the 5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.
  • AUSF Authentication Server Function
  • NSSAAF Network Slice Specific Authentication and Authorization Function
  • Network Slice Selection Function [116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
  • Network Exposure Function (NEF) [118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
  • Network Repository Function (NRF) [120] is a network function that acts as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.
  • PCF Policy Control Function
  • UDM Unified Data Management
  • AF Application Function
  • UPF User Plane Function
  • UPF User Plane Function
  • Data Network (DN) [130] refers to a network that provides data services to user equipment (UE) in a telecommunications system.
  • the data services may include but are not limited to Internet services, private data network related services.
  • FIG.2 illustrates an exemplary block diagram of a computing device [1000] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
  • the computing device [1000] may also implement a method for optimization of a device triggering procedure for one or more Internet of Things (IoT) devices in an exposure function, utilising the system.
  • IoT Internet of Things
  • the computing device [1000] itself implements the method for optimization of a device triggering procedure for one or more Internet of Things (IoT) devices in an exposure function, using one or more units configured within the computing device [1000], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
  • the computing device [1000] may include a bus [1002] or other communication mechanism for communicating information, and a hardware processor [1004] coupled with bus [1002] for processing information.
  • the hardware processor [1004] may be, for example, a general- purpose microprocessor.
  • the computing device [1000] may also include a main memory [1006], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [1002] for storing information and instructions to be executed by the processor [1004].
  • the main memory [1006] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [1004].
  • Such instructions when stored in non-transitory storage media accessible to the processor [1004], render the computing device [1000] into a special-purpose machine that is customized to perform the operations specified in the instructions.
  • the computing device [1000] further includes a read only memory (ROM) [1008] or other static storage device coupled to the bus [1002] for storing static information and instructions for the processor [1004].
  • ROM read only memory
  • a storage device [1010], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [1002] for storing information and instructions.
  • the computing device [1000] may be coupled via the bus [1002] to a display [1012], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user.
  • An input device [1014], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [1002] for communicating information and command selections to the processor [1004].
  • cursor control such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [1004], and for controlling cursor movement on the display [1012].
  • This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
  • the computing device [1000] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [1000] causes or programs the computing device [1000] to be a special-purpose machine.
  • the techniques herein are performed by the computing device [1000] in response to the processor [1004] executing one or more sequences of one or more instructions contained in the main memory [1006]. Such instructions may be read into the main memory [1006] from another storage medium, such as the storage device [1010]. Execution of the sequences of instructions contained in the main memory [1006] causes the processor [1004] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions. [00067]
  • the computing device [1000] also may include a communication interface [1018] coupled to the bus [1002].
  • the communication interface [1018] provides a two-way data communication coupling to a network link [1020] that is connected to a local network [1022].
  • the communication interface [1018] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line.
  • the communication interface [1018] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN.
  • LAN local area network
  • Wireless links may also be implemented.
  • the communication interface [1018] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
  • the computing device [1000] can send messages and receive data, including program code, through the network(s), the network link [1020] and the communication interface [1018].
  • a server [1030] might transmit a requested code for an application program through the Internet [1028], the ISP [1026], the local network [1022] and the communication interface [1018].
  • the received code may be executed by the processor [1004] as it is received, and/or stored in the storage device [1010], or other non-volatile storage for later execution.
  • FIG.3 an exemplary block diagram of 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], is shown, in accordance with the exemplary implementations of the present disclosure.
  • the exposure function [300ef] may include but not limited to one of a Service Capability Exposure Function (SCEF) and a Network Exposure Function (NEF).
  • SCEF Service Capability Exposure Function
  • NEF Network Exposure Function
  • the system [300] comprises at least one configuration unit [301], at least one transceiver unit [302], at least one extraction unit [303], at least one optimization unit [304] and at least one balancing unit [305].
  • system [300] all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the system [300], all units within the system [300] should also be assumed to be connected to each other. Also, in Fig.3 only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [300] may be a part of the user device / or may be independent of but in communication with the user device (may also referred herein as a UE). In another implementation, the system [300] may reside in a server or a network entity.
  • the system [300] may reside partly in the server/ network entity and partly in the user device.
  • the system [300] is configured for optimization of the device triggering procedure for one or more Internet of Things (IoT) devices [300id] in an exposure function [300ef], with the help of the interconnection between the components/units of the system [300].
  • the configuration unit [301] configures, for each service consumer [300sc] among one or more service consumers [300sc], a Data-Coding-Scheme (DCS) from one or more DCSs. It is to be noted that each DCS is associated with one or more device triggering requests for the one or more IoT devices [300id].
  • DCS Data-Coding-Scheme
  • the service consumer [300sc] is one of a Services Capability Server (SCS), an Application Server (AS) and an Application Function (AF).
  • the one or more device triggering requests refers to a signal/ prompt sent from one IoT device [300id] to another IoT device [300id2] to perform a specific task or action.
  • the one or more device triggering request may be governed as per a predefined protocol that are required in implementation of the receipt of the device triggering request for information exchange, thus ensuring seamless interaction and optimal performance of the communication network.
  • the transceiver unit [302] is 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 requests over a standard interface.
  • the standard interface is a standard T8/N33 interface.
  • the extraction unit [303] is 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.
  • the custom header is a “devicePayloadFormat” custom header.
  • 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].
  • the optimization unit [304] is 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.
  • IoT Internet of Things
  • the optimization unit [304] is further configured to configure, for the exposure function [300ef], the DCS fetched from said each of the device triggering requests.
  • the balancing unit [305] is configured to enable one or more load balancers (LBs) to load balance the one or more device triggering requests.
  • the one or more load balancers (LBs) may include but are not limited to edge load balancers.
  • an exemplary method flow diagram [400] for optimization of a device triggering procedure for one or more Internet of Things (IoT) devices [300id] in an exposure function [300ef], in accordance with exemplary implementations of the present disclosure is shown.
  • the method [400] is performed by the system [300].
  • the system [300] may be present in a server device to implement the features of the present disclosure.
  • the method [400] starts at step [402].
  • the exposure function [300ef] is one of a Service Capability Exposure Function (SCEF) and a Network Exposure Function (NEF).
  • SCEF Service Capability Exposure Function
  • NEF Network Exposure Function
  • 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).
  • DCS Data- Coding-Scheme
  • each DCS is associated with a one or more device triggering requests for the one or more Internet of Things (IoT) devices [300id].
  • IoT Internet of Things
  • the one or more device triggering requests refers to a signal/ prompt sent from one IoT device [300id] to another IoT device [300id2] to perform a specific task or action.
  • the one or more device triggering request may be governed as per a predefined protocol that are required in implementation of the receipt of the device triggering request for information exchange, thus ensuring seamless interaction and optimal performance of the communication network.
  • the service consumer [300sc] is one of a Services Capability Server (SCS), an Application Server (AS) and an Application Function (AF).
  • the method [400] comprises 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.
  • the standard interface is a standard T8/N33 interface.
  • the method [400] comprises extracting, by 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.
  • the custom header is a “devicePayloadFormat” custom header.
  • 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 the each service consumer [300sc].
  • the method [400] comprises 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.
  • IoT Internet of Things
  • the method [400] further 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.
  • the method [400] further comprises enabling by a balancing unit [305], one or more load balancers (LBs) to load balance the one or more device triggering requests.
  • FIG. 30 shows a balancing unit [305]
  • LBs load balancers
  • FIG. 5 illustrates an exemplary block diagram of a system [500] for enhancement in device triggering procedure for Internet of Things (IoT) to allow the data to be conveyed from the SCS/AS/AF [506] via Service Capability Exposure Function (SCEF) or Network Exposure Function (NEF) [512] to one or more intended IoT Devices [508], in accordance with exemplary embodiments of the present disclosure.
  • the system [500] comprises at least one processing unit [502] and at least one storage unit [504]. Also, all of the components/ units of the system [500] are assumed to be connected to each other unless otherwise indicated below. Also, in Fig.
  • system [500] may comprise multiple such units or the system [500] may comprise any such numbers of said units, as required to implement the features of the present disclosure.
  • the system [500] may be a part of the user device / or may be independent of but in communication with the user device (may also referred herein as a UE).
  • the system [500] may reside in a server or a network entity.
  • the system [500] may reside partly in the server/ network entity and partly in the user device.
  • the system [500] is configured for enhancement in device triggering procedure for Internet of Things (IoT) to allow the data to be conveyed from the SCS/AS/AF [506] via Service Capability Exposure Function (SCEF) or Network Exposure Function (NEF) [512] to one or more intended IoT Device [508], with the help of the interconnection between the components/units of the system [500].
  • IoT Internet of Things
  • the processing unit [502] of the system [500] is configured to provide SCEF [512] with DCS required to allow the communication from the first API to the second API.
  • the processing unit [502] commands the SCEF [512] to fetch DCS associated with each device trigger request on standard T8/N33 interface.
  • the processing unit [502] commands SCS/AS/AF [506] to adapt this requirement and specify intended DCS while initiating device trigger request over T8/N33 interface.
  • the data shall transmit from the first API to the Second API using the fetched DBS.
  • the SCEF [512] will be configured to store the DCS information in cache/Database (DB) for each SCS/AS/AF [506] based on parameters required by various services (for e.g., a device trigger, Monitoring Events (MontE) Non-IP data delivery (NIDD) Background data transfer (BDT) MSISDN-Less MO) specified at the time of its on- boarding which will later be used in each device trigger request initiated from a respective SCS/AS/AF [506].
  • DB cache/Database
  • DB Database
  • a Provisioning Gateway (G/W) UI [516] is used to provide the SCS/AS/AF [506] along with all the configurations that must be required by SCEF [512] with respect to that SCS/AS/AF [506].
  • An Edge Load Balancer (ELB) [514] will load balance the provisioning request towards SCEF [512] instances.
  • the SCS/AS/AF [506] will initiate device trigger create/replace request, which is to be delivered to an IoT device.
  • the SCEF [512] will check whether device payload format is provided in the request. If not, the SCEF [512] will fetch that information from the configurations provided while provisioning an SCS/AS/AF [506].
  • FIG.6 illustrates an exemplary method [600] flow diagram indicating the process for enhancement of device triggering procedure for Internet of Things (IoT) to allow the data to be conveyed from the SCS/AS/AF via Service Capability Exposure Function (SCEF) or Network Exposure Function (NEF) to one or more intended IoT Devices, in accordance with exemplary embodiments of the present disclosure.
  • IoT Internet of Things
  • the method [600] is performed by the system [500]. As shown in FIG.6, the method [600] involves following steps: Step [601] of receiving Device Trigger Request from SCS/AS/AF Step [602] of checking if the Trigger Payload Format is Specified. If the answer to the previous step is positive, then the method [600] proceeds to next step [603]. If the answer to the previous step in negative, then the method [600] executes step [6021] of using the payload format configured at the time of SCS/AS/AF provisioning and then proceeds to step [6022] of fetching the payload format for specific SCS/AS/AF. Step [603] of submitting the device trigger along with payload format to the SMSC and proceed for communication.
  • the present disclosure further discloses 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 instructions include 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.
  • IoT Internet of Things
  • DCS Data-Coding-Scheme
  • each DCS is associated with a one or more device triggering requests for the one or more IoT devices [300id]; a 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] 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] 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.
  • IoT Internet of Things
  • the present disclosure further discloses a User Equipment (UE) device receiving a device trigger.
  • the UE device comprises 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 request is sent to the UE device.
  • the system [300] further comprises a configuration unit [301] 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 the one or more device triggering requests for the UE device.
  • DCS Data-Coding-Scheme
  • the system [300] further comprises 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.
  • the system [300] further comprises 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.
  • the system [300] further comprises 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.
  • 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.
  • Reduced chances of failure of transmission of data as the exposure function [300ef] is aware of the DCS.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Computer And Data Communications (AREA)

Abstract

La présente divulgation concerne un procédé et un système d'optimisation d'une procédure de déclenchement de dispositif pour un ou plusieurs dispositifs Internet des objets (IoT) [300id] dans une fonction d'exposition (EF) [300ef]. La divulgation concerne la configuration d'un schéma de codage de données (DCS), la réception de demandes de déclenchement de dispositif sur une interface standard, l'extraction d'un DCS depuis les demandes de déclenchement de dispositif sur la base d'un en-tête personnalisé et d'un DCS par défaut prémaintenu, et l'optimisation de la procédure de déclenchement de dispositif pour les dispositifs IoT [300 id] sur la base du DCS extrait des demandes de déclenchement de dispositif.
PCT/IN2024/050749 2023-07-04 2024-06-11 Procédé et système d'optimisation de procédure de déclenchement de dispositif pour dispositifs iot Ceased WO2025008879A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202321044883 2023-07-04
IN202321044883 2023-07-04

Publications (1)

Publication Number Publication Date
WO2025008879A1 true WO2025008879A1 (fr) 2025-01-09

Family

ID=94171339

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IN2024/050749 Ceased WO2025008879A1 (fr) 2023-07-04 2024-06-11 Procédé et système d'optimisation de procédure de déclenchement de dispositif pour dispositifs iot

Country Status (1)

Country Link
WO (1) WO2025008879A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12596868B2 (en) * 2023-10-27 2026-04-07 Beijing Zitiao Network Technology Co., Ltd. Creating a digital assistant

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013166230A2 (fr) * 2012-05-02 2013-11-07 Interdigital Patent Holdings, Inc. Systèmes et procédés pour fournir et/ou mettre en œuvre une communication du type machine (mtc)
US20190025806A1 (en) * 2016-05-09 2019-01-24 Strong Force Iot Portfolio 2016, Llc Methods and systems for optimization of network-sensitive data collection in an industrial drilling environment
US20210219151A1 (en) * 2018-06-20 2021-07-15 Telefonaktiebolaget Lm Ericsson (Publ) Methods and systems for online services applications and application functions to provide ue-generated information to network data analytics to support network automation and optimization

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013166230A2 (fr) * 2012-05-02 2013-11-07 Interdigital Patent Holdings, Inc. Systèmes et procédés pour fournir et/ou mettre en œuvre une communication du type machine (mtc)
US20190025806A1 (en) * 2016-05-09 2019-01-24 Strong Force Iot Portfolio 2016, Llc Methods and systems for optimization of network-sensitive data collection in an industrial drilling environment
US20210219151A1 (en) * 2018-06-20 2021-07-15 Telefonaktiebolaget Lm Ericsson (Publ) Methods and systems for online services applications and application functions to provide ue-generated information to network data analytics to support network automation and optimization

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12596868B2 (en) * 2023-10-27 2026-04-07 Beijing Zitiao Network Technology Co., Ltd. Creating a digital assistant

Similar Documents

Publication Publication Date Title
WO2025008879A1 (fr) Procédé et système d'optimisation de procédure de déclenchement de dispositif pour dispositifs iot
WO2025012936A1 (fr) Procédé et système de rapport d'informations de charge spécifiques à une tranche
WO2025008875A1 (fr) Procédé et système de configuration et de gestion d'enregistrements mandataires dans un réseau
WO2025013047A1 (fr) Procédé et système permettant d'effectuer des changements de configuration en vrac de nœuds de réseau
WO2025012980A1 (fr) Procédé et système pour la réalisation d'une procédure d'interdiction dans une zone de rapport de présence prédéfinie (pra)
WO2025008918A1 (fr) Procédé et système de gestion de demandes de réseau entrantes sur une fonction de réseau producteur surchargée
WO2025012956A2 (fr) Procédé et système permettant de fournir un service de priorité multimédia dans un réseau de communication
WO2025008876A1 (fr) Procédé et système de mise sur liste d'autorisation de dispositifs compatibles avec vowifi
WO2025012979A1 (fr) Procédé et système aux fins d'une gestion basée sur la configuration d'une demande de procédure
WO2025069097A1 (fr) Procédé et système de gestion d'une ou plusieurs politiques de session dans un réseau
WO2025008953A1 (fr) Procédé et système d'activation d'un ou de plusieurs services de communication
WO2025052433A1 (fr) Procédé et système d'extraction automatique de données d'autorisation de tranche au niveau d'une amf d'un réseau
WO2025069062A1 (fr) Procédé et système de continuité de service dans un réseau de communication
WO2025062429A1 (fr) Procédé et système de gestion d'une condition de course dans un réseau de communication
WO2025008865A1 (fr) Procédé et système pour fournir une notification d'abonnement dans un réseau de communication
WO2025012964A1 (fr) Procédé et système de gestion de routage de messages
WO2025057186A1 (fr) Procédé et système de gestion d'enregistrement d'une fonction de réseau
WO2025012943A1 (fr) Procédé et système de création d'un contexte de gestion de session (sm) dans un premier et un second réseau
WO2025012948A1 (fr) Procédé et système de transmission d'un message à un utilisateur cible
WO2025052421A1 (fr) Procédé et système de traitement des demandes de localisation dans un réseau de communication sans fil
WO2025017618A1 (fr) Système et procédé de détermination d'informations d'emplacement d'un utilisateur
WO2025052436A1 (fr) Procédé et système de découverte d'une ou de plusieurs fonctions de réseau homologues
WO2025008871A1 (fr) Procédé et système de routage d'une demande d'enregistrement dans réseau de communication
WO2025052404A1 (fr) Procédé et système permettant de faciliter le routage dans un réseau
WO2025008909A1 (fr) Procédé et système de mise en œuvre d'une plateforme de codage et de décodage de messages de protocoles cibles

Legal Events

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

Ref document number: 24835601

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2024835601

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2024835601

Country of ref document: EP

Effective date: 20260204