System and method for detecting and handling machine emergencies in a network

The system uses a machine learning engine to classify and handle mechanical emergencies in 3GPP networks, addressing the lack of emergency handling in IoT and IIoT systems by providing differentiated QoS and SIM-less attach, ensuring timely and appropriate responses.

JP2024541126AActive Publication Date: 2024-11-07JIO PLATFORMS LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2023520005
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2021-09-28
Filing Date
2022-09-28
Publication Date
2024-11-07
Estimated Expiration
2042-09-28

AI Technical Summary

Technical Problem

Existing 3GPP networks lack the capability to effectively handle mechanical emergencies in IoT and IIoT systems, failing to provide priority treatment and unique identity for machine-type communications, which is crucial for efficient emergency response.

Method used

A system and method utilizing a machine learning engine to identify and classify mechanical emergencies within a network, enrich emergency messages with data like location and machine ID, and redirect them to appropriate servers, enabling SIM-less emergency attach and differentiated QoS handling.

Benefits of technology

Enables efficient detection and handling of various mechanical emergencies, ensuring timely and appropriate response through enhanced emergency message handling and resource allocation in 3GPP networks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024541126000001_ABST
    Figure 2024541126000001_ABST
Patent Text Reader

Abstract

The present invention provides an efficient and reliable system for identifying machine emergency types among 3GPP networks / devices such as LTE, 5G, 6G, etc., and enriching emergency messages with appropriate data such as location, machine ID, plant ID, etc. The system may further provide mechanisms for identifying appropriate emergency servers capable of handling that type of emergency, and redirecting the emergency message with the enriched data to one or more servers. The system may further enable architecture systems that may be necessary to handle such emergencies in a time-efficient manner.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE Embodiments of the present disclosure relate generally to detecting emergencies in a network. More particularly, the present disclosure relates to systems and methods for detecting machine emergencies and enabling appropriate handling of the emergency. [Background technology]

[0002] The following discussion of the prior art is intended to provide background information related to the field of the present disclosure. This section may include some aspects of the prior art that may be relevant to various aspects of the present disclosure. However, it should be understood that this section is merely used to enhance the reader's understanding of the present disclosure and is not an admission of prior art.

[0003] The Internet of Things (IoT) describes a network of physical objects / "things" embedded with sensors, software and other technologies for the purpose of connecting and exchanging data with other devices and systems over the Internet. Things have evolved through a confluence of multiple technologies, real-time analytics, machine learning, ubiquitous computing, commodity sensors, and embedded systems. Traditional embedded systems, wireless sensor networks, control systems, automation (including home and building automation), and others all contribute to enabling the Internet of Things. In the consumer market, IoT technology is largely synonymous with products related to the concept of a "smart home," including devices and appliances (lighting fixtures, thermostats, home security systems and cameras, and other household appliances) that support one or more common ecosystems and can be controlled via ecosystem-related devices, such as smartphones and smart speakers. IoT can also be used in healthcare systems. There are several significant concerns about the dangers of the growth of IoT, especially in the areas of privacy and security, and as a result, industry and government efforts to address these concerns have been initiated, including the development of international standards.

[0004] Industrial Internet of Things (IIoT) refers to the expansion and use of the Internet of Things (IoT) in industrial sectors and applications. With an emphasis on machine-to-machine (M2M) communication, big data, and machine learning, IIoT enables industries and enterprises to have better efficiency and reliability in their operations. IIoT encompasses industrial applications including robotics, medical devices, and software-defined production processes. IIoT goes beyond the usual internetworking of consumer devices and physical devices typically associated with IoT. What makes it distinct is the intersection of information technology (IT) and operational technology (OT). OT refers to the networking of operational processes with industrial control systems (ICS), including man-machine interfaces (HMIs), supervisory control and data acquisition (SCADA) systems, distributed control systems (DCSs), and programmable logic controllers (PLCs).

[0005] Such a system can help industries to grow immensely by providing universal and continuous data and help to make better decisions overall. It also helps to automatically provide data about the health of the overall system. For example, in a manufacturing plant, an inserted sensor can help to inform us if there is a harmful gas leak using a smoke sensor, or if there is a water leak or a machine overload and shutdown is required, etc. Such a situation is generally called a machine emergency, and real-time emergency situations are automatically communicated across the system. Such data travels through the cellular network (on next generation cellular networks including 2G, 3G, 4G or NB-IoT as technologies) and reaches an emergency server, SCADA server, or remote control server via the Internet. Such emergency sessions are the most basic and important services offered by telecommunication networks. They require preferential treatment over normal sessions, which is achieved by QoS and resource management techniques. However, existing 3GPP systems or solutions only provide preferential treatment to publicly initiated emergency communications, while it does not offer special treatment for mission-critical calls, or machine emergency types in typical IoT or IIoT in general.

[0006] Handling emergencies in 3GPP® networks has been intended to handle human emergencies so far. The nature of handling human emergencies is very different from the nature of handling machine emergencies. The existing emergency definitions and handling mechanisms in 3GPP® address human emergencies and not machine emergencies. The introduction of IoT and especially IIoT (Industrial IoT) exposes numerous types of emergencies that need to be handled differently from human emergencies. Moreover, it is noted that it is more important to have a unique identity for a subscription such as SIM / USIM / eSIM / Soft SIM, especially for machine-type communications without human intervention. Therefore, SIM-less operation in situations that would otherwise be tolerated in normal 3GPP® systems is simply not possible.

[0007] Therefore, there is a need in the art to provide a system and method that can distinguish between different types of machine emergency situations and suggest mechanisms for handling such emergencies. Summary of the Invention [Problem to be solved by the invention]

[0008] Some of the objectives of the present disclosure that are satisfied by at least one embodiment herein are listed herein below.

[0009] It is an object of the present disclosure to provide a system and method that facilitates SIM-less emergency attach to machine-type devices.

[0010] It is an object of the present disclosure to provide a system and method that covers emergency attachment aspects to machine-type devices.

[0011] An objective of the present disclosure is to provide a system and method for identifying the type of machine emergency in a 3GPP® network / device (covering LTE, 5G, 6G) and enriching the emergency message with appropriate data such as location, machine ID, plant ID, etc.

[0012] It is an object of the present disclosure to provide a system and method for identifying an appropriate emergency server that can handle that type of emergency and redirecting the emergency message with enriched data to the appropriate server. [Means for solving the problem]

[0013] This section is provided to introduce in a simplified form certain objects and aspects of the disclosure that are further described below in the Detailed Description. This Summary is not intended to identify key features or the scope of the claimed subject matter.

[0014] In one aspect, the present disclosure provides a system for detecting and handling a machine emergency in a network. The system may include one or more processors operably coupled to one or more first computing devices, one or more base stations, an open radio access network (O-RAN) radio (RU), and a plurality of nodes. The one or more first computing devices, the one or more base stations, the O-RAN RU, and the plurality of nodes may be operably coupled to the network. The one or more processors may be coupled to a memory storing instructions that, when executed by the one or more processors, cause the system to receive a first set of data packets associated with a plurality of messages from the one or more first computing devices in the network, receive a second set of data packets associated with a plurality of messages from the one or more base stations in the network, receive a third set of data packets associated with a plurality of messages from the O-RAN RU in the network, and receive a fourth set of data packets associated with a plurality of messages from a plurality of nodes in the network. The system may be further configured to extract, by using a machine learning (ML) engine associated with the one or more processors, a set of attributes from the first, second, third and fourth sets of received data packets, the set of attributes associated with one or more emergency situations associated with the one or more first computing devices, the one or more base stations, the O-RAN-RU, and the plurality of nodes. The system may be further configured to classify, by the ML engine, the one or more emergency situations into a set of predetermined classes based on a predetermined set of instructions.

[0015] In one embodiment, the ML engine may be configured to process and handle one or more emergency situations based on a set of instructions associated with each said predefined class.

[0016] In one embodiment, the ML engine may be further configured to define a set of instructions for each said predefined class to handle a pre-mapped industry vertical.

[0017] In one embodiment, the ML engine may be further configured to respond to a number of real-time machine-type emergency situations that occur within one or more IoT applications.

[0018] In one embodiment, the ML engine may be further configured to define, manage, and handle one or more new emergency types associated with the one or more first computing devices, the one or more base stations, the O-RAN-RU, and the plurality of nodes.

[0019] In one embodiment, the ML engine may be further configured to define and classify one or more new emergency types as new classes of emergency situations.

[0020] In one embodiment, the ML engine may be further configured to automatically or manually handle each new emergency type based on a predetermined set of classifications of one or more new emergency types and instructions associated with the classification.

[0021] In one embodiment, an initial bit of the first set of data packets, the second set of data packets, the third set of data packets, and the fourth set of data packets indicates an emergency type, and the remainder of the first set of data packets, the second set of data packets, the third set of data packets, and the fourth set of data packets indicates packet forwarding after establishment of the machine assembly.

[0022] In one embodiment, the ML engine may be further configured to receive newly defined quality of service for handling one or more emergency situations, which are shared among the service request cause, configure and map the newly identified QoS profile, and / or interface and identify the emergency type and necessary signaling identifier to inform the network of the correct type of QoS profile to properly handle, identify and apply the emergency situation.

[0023] In one embodiment, the ML engine may be further configured to collect, store in a cloud-based data lake, and process the carefully collected data to extract actionable insights.

[0024] In one aspect, the present disclosure provides a user equipment (UE) for detecting and handling a machine emergency in a network. The UE may include one or more processors operably coupled to one or more base stations, an open radio access network (O-RAN) radio (RU), and a plurality of nodes. The one or more base stations, the O-RAN RU, and the plurality of nodes may be operably coupled to the network. The one or more processors may be coupled to a memory storing instructions that, when executed by the one or more processors, cause the UE to receive a first set of data packets associated with a plurality of messages from one or more first computing devices in the network, receive a second set of data packets associated with a plurality of messages from one or more base stations in the network, receive a third set of data packets associated with a plurality of messages from an O-RAN RU in the network, and receive a fourth set of data packets associated with a plurality of messages from a plurality of nodes in the network. The UE may be further configured to extract, by using a machine learning (ML) engine associated with the one or more processors, a set of attributes from the first, second, third and fourth set of received data packets, the set of attributes associated with one or more emergency situations associated with the one or more first computing devices, the one or more base stations, the O-RAN-RU, and the plurality of nodes. The UE may be further configured to classify, by the ML engine, the one or more emergency situations into a set of pre-defined classes based on a pre-defined set of instructions.

[0025] In one aspect, the present disclosure provides a method for detecting and handling a machine emergency in a network. The method may include receiving, by one or more processors, a first set of data packets associated with a plurality of messages from one or more first computing devices in the network. The one or more processors may be operatively coupled to the one or more first computing devices, one or more base stations, an open radio access network (O-RAN) radio (RU), and a plurality of nodes. The one or more first computing devices, the one or more base stations, the O-RAN RU, and a plurality of nodes may be operatively coupled to the network. Additionally, the one or more processors may be coupled to a memory storing instructions. The method may also include receiving, by one or more processors, a second set of data packets associated with a plurality of messages from one or more base stations in the network, receiving, by one or more processors, a third set of data packets associated with a plurality of messages from an open radio access network (O-RAN) radio (RU) in the network, and receiving, by one or more processors, a fourth set of data packets associated with a plurality of messages from a plurality of nodes in the network. The method may further include extracting, by a machine learning (ML) engine associated with the one or more processors, a set of attributes from the first, second, third and fourth sets of received data packets, the set of attributes associated with one or more emergency situations associated with the one or more first computing devices, the one or more base stations, the O-RAN-RU, and the plurality of nodes. Additionally, the method may further include classifying, by the ML engine, the one or more emergency situations into a set of predefined classes based on a predefined set of instructions.

[0026] The accompanying drawings, which are incorporated herein and form a part of the present invention, depict exemplary embodiments of the disclosed method and system, in which like reference numbers refer to the same parts throughout the different drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed on clearly illustrating the principles of the invention. Some drawings use block diagrams to illustrate components and do not represent the internal circuitry of each component. Those skilled in the art will appreciate that the inventions in such drawings include inventions in electrical components, electronic components, or circuits commonly used to implement such components. [Brief description of the drawings]

[0027] [Figure 1] FIG. 1 illustrates an example network architecture in or by which the presented system of the present disclosure may be implemented, according to one embodiment of the present disclosure. [Figure 2A] FIG. 1 illustrates an exemplary representation of a presented system for detecting and handling machine emergencies within a network, according to one embodiment of the present disclosure. [Figure 2B] FIG. 2 illustrates an exemplary representation of a presented method for detecting and handling a machine emergency in a network, according to one embodiment of the present disclosure. [Figure 3A] FIG. 2 illustrates an exemplary representation of an existing system network architecture and message flows, according to one embodiment of the present disclosure. [Figure 3B] FIG. 2 illustrates an exemplary representation of an existing system network architecture and message flows, according to one embodiment of the present disclosure. [Figure 4] FIG. 1 illustrates an exemplary representation of a presented network system architecture, according to one embodiment of the present disclosure. [Figure 5A] FIG. 1 illustrates an example of an exemplary call flow for sharing emergency types across systems, according to one embodiment of the present disclosure. [Figure 5B]FIG. 1 illustrates an example of an exemplary call flow for sharing emergency types across systems, according to one embodiment of the present disclosure. [Figure 5C] FIG. 1 illustrates an example of an exemplary call flow for sharing emergency types across systems, according to one embodiment of the present disclosure. [Figure 6] FIG. 1 illustrates an exemplary NB-IOT system, according to one embodiment of the present disclosure. [Figure 7A] FIG. 1 illustrates an embodiment of an alternative call flow example of how a machine emergency is transferred across a cellular network over IMS, according to one embodiment of the disclosure. [Figure 7B] FIG. 1 illustrates an embodiment of an alternative call flow example of how a machine emergency is transferred across a cellular network over IMS, according to one embodiment of the disclosure. [Figure 8] FIG. 1 illustrates an exemplary computer system in or by which embodiments of the present disclosure may be utilized, in accordance with an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0028] The above will become clearer upon reading the more detailed description of the invention.

[0029] In the following description, for purposes of explanation, various specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure. However, it will be apparent that the embodiments of the present disclosure may be practiced without these specific details. Some features described hereafter may be used independently of each other or in any combination with other features. Individual features may not necessarily address all of the problems described above, or may address only some of the problems described above. Some of the problems described above may not necessarily be fully addressed by any of the features described herein.

[0030] The following description merely provides exemplary embodiments and is not intended to limit the scope, applicability, or configuration of the present disclosure. Instead, the following description of exemplary embodiments will provide those skilled in the art with an effective description for implementing the exemplary embodiments. It will be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the invention as described.

[0031] The present invention provides an efficient and reliable system to identify machine emergency types among 3GPP networks / devices such as LTE, 5G, 6G, etc., and enrich the emergency message with appropriate data such as location, machine ID, plant ID, etc. The system may further provide a mechanism to identify appropriate emergency servers that can handle that type of emergency, and redirect the emergency message with the enriched data to one or more servers.

[0032] Referring to FIG. 1, FIG. 1 illustrates an exemplary network architecture (100) (also referred to as network architecture (100)) in or by which the machine emergency detection system (110) of the present disclosure (or simply referred to as system (110)) may be implemented, according to one embodiment of the present disclosure. As shown, the exemplary network architecture (100) is equipped with (110) and may be communicatively coupled to a plurality of first computing devices (102-1, 102-2, 102-3...102-N) (synonymously referred to as user equipment (102-1, 102-2, 102-3...102-N), individually referred to as user equipment (UE) (102), and collectively referred to as UEs (102)) through second computing devices (104-1, 104-2, 104-3,...104-N) (synonymously referred to as base stations (104-1, 104-2,...104-N), individually referred to as base stations (104), and collectively referred to as base stations (104)), and may further be operatively coupled to the base stations (104) via a third computing device (synonymously referred to as an open wireless access network radio (108)). The system (110) may further be communicatively coupled to one or more fourth computing devices (114) (interchangeably referred to as nodes (114)).

[0033] In one embodiment, the system (110) may be equipped with a machine learning engine (ML) (214) that may cause the system for receiving a set of messages related to a related emergency event to receive a first set of data packets related to the multiple messages from one or more first computing devices (102) in the network (106), receive a second set of data packets related to the multiple messages from one or more base stations (104) in the network (106), receive a third set of data packets related to the multiple messages from an O-RAN RU (108) in the network (106), and receive a fourth set of data packets related to the multiple messages from a plurality of nodes (114) in the network (106). The system (110) may extract a set of attributes from the first, second, third, and fourth sets of received data packets by using the ML engine (214), the set of attributes associated with one or more emergency events associated with the one or more first computing devices (102), the one or more base stations (104), the O-RAN-RU (108), and the plurality of nodes (114), and the system (110) may classify the one or more emergency events into a set of pre-defined classes based on a pre-defined set of instructions by the ML engine (214). For example, the one or more emergency events may be any machine emergency associated with a defect or other malfunction occurring in a machine.

[0034] In one embodiment, the ML engine (214) is configured to process and handle one or more emergency situations based on a set of instructions associated with each predefined class.

[0035] For example, machinery emergencies can be defined to address specific verticals such as Industry 4.0, railways, power grids, etc. The new classification of emergency types is to accommodate various real-time machinery type emergencies occurring in IoT applications.

[0036] In an exemplary embodiment, the system 110 may be configured to define new emergency types and handle such emergency situations within the cellular network. For example, a new emergency attach type within the network may allow a particular type of machine to attach different provisions even when a SIM card is unavailable.

[0037] In another exemplary embodiment, new types of emergencies may be defined and classified as new classes of machine emergencies. For example, an emergency at one or more sensors and actuators may be classified as a class A emergency, an emergency in a machine may be classified as a class B emergency, an emergency in a production line may be classified as a class C emergency, an emergency in a plant may be classified as a class D emergency, and so on. The handling for each of the above emergency types varies based on the emergency type. Class A and B emergencies may be handled "automatically" via appropriate responses. For class C and D emergencies, human intervention is visualized as procedures for handling class C and D types of machine emergencies are different.

[0038] In one embodiment, a class A machine emergency at the machine level may be when data from sensors embedded in an individual machine indicating something may be wrong in the machine is claimed as a machine level emergency. As one embodiment, sensors in a lathe machine for detecting wear and tear, correcting thermal deformations, and precisely positioning the blade provide data indicating the machine needs to be attended to for the above issues. Similarly, as a second embodiment, sensors for detecting the efficiency of an individual robot versus speed of motion showing a decrease in accuracy or a negative value as a problem with the machine requiring inspection may be classified as a class A machine emergency type. One or more of the sensors having a processor and software for integrating data from other sensors in the machine integrate data from multiple sensors in the machine to compile an emergency message.

[0039] In one embodiment, class B machine emergency in a production line may be multiple machines that typically define a production line, which may be an automobile paint line, as an example, where multiple individual machines are assigned jobs to complete defined jobs. We define emergency types to indicate problems with the production line, and in the production line, we configure multiple machines and sensors in multiple machines, and data from sensors embedded in the production line supporting functions are integrated by one of the sensors, which acts as a master sensor and helps integrate data from the sensors in the production line to detect if an emergency exists. An emergency may be defined in the master sensor as a correlation table that defines thresholds for sensor data from individual sensors to define a production line emergency.

[0040] In one embodiment of the present invention, a class C machine emergency in a factory work floor may be multiple production lines that typically define a factory work floor, the work floor being responsible for the end-to-end production / assembly of, for example, automobile engines. We define emergency types to indicate issues with the factory work floor, and in the work floor, multiple machines and sensors in multiple machines are configured, and data from sensors embedded in the multiple production lines supporting functions are integrated by one of the sensors that acts as a master sensor and helps to integrate data from the sensors in the multiple production lines to detect if an emergency exists. The emergency is defined in the master sensor as a correlation table that defines thresholds of sensor data from individual sensors to define a production line emergency.

[0041] In one embodiment of the present invention, class D machine emergency at factory level may be a work site of multiple factories that typically define a factory, for example, a factory is responsible for the finished production of making automobiles. We define an emergency type to indicate a problem with the factory itself, where the data from the sensors embedded in the multiple production lines that support the functions are integrated by one of the sensors that acts as a master sensor and helps to integrate the data from the sensors in the multiple production lines to detect whether an emergency exists. The emergency is defined in the master sensor as a correlation table that defines thresholds of sensor data from individual sensors to define a production line emergency. The sensors may include other sensors such as fire detection sensors, images from cameras that indicate attempted or ongoing theft, or motion detection sensors to detect motion that should not exist.

[0042] In one embodiment, emergency access may be requested by a first computing device (102) (also referred to as user equipment 102 or UE 102) via a set of instructions that may be part of a service request IE sent as part of an attach / power distribution unit (PDU) establishment / modification procedure.

[0043] In one exemplary embodiment, a predefined structure may be sent during a PDU establishment procedure.

[0044] In yet another embodiment, an initial bit may be sent upon establishment of the cause to indicate the emergency type and the remainder of the data portion of the packet transfer after establishment of the PDU.

[0045] In one exemplary embodiment, the system (110) may configure a mechanism for handling emergency situations via a newly defined Quality of Service (QoS) profile, which is applied by a network-based emergency type shared among the service request causes. In another embodiment, the application may use a modem interface (AT commands) to configure and map the newly identified QoS profile and / or to make the modem and network aware of the emergency type to properly handle the emergency. The AT commands may interface and identify the emergency type and the necessary signaling identifiers to inform the network of the correct type of QoS profile to identify and apply.

[0046] In one embodiment, the system (110) may be, but is not limited to, a system-on-chip (SoC) system. In another embodiment, the on-site data capture, storage, matching, processing, decision-making, and actuation logic may be coded using, but is not limited to, a microservices architecture (MSA). Multiple microservices may be containerized and event-based to support portability.

[0047] In one embodiment, the network architecture (100) may be modular and flexible to accommodate any type of change in the system (110).

[0048] In one embodiment, the system 110 can be remotely monitored and the data, application and physical security of the system 110 can be fully assured. In one embodiment, data can be carefully collected, stored in a cloud-based data lake and processed to extract actionable insights. Hence, aspects of predictive maintenance can be achieved.

[0049] In an exemplary embodiment, the communications network (106) may include, by way of example and not limitation, one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or combinations thereof, at least a portion of one or more messages, packets, signals, waves, voltage or current levels, some combinations thereof, etc. The networks may include, by way of example and not limitation, one or more of a wireless network, a wired network, the Internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad-hoc network, an infrastructure network, a public switched telephone network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, some combinations thereof, etc.

[0050] In another exemplary embodiment, a centralized server (112) may be included in the architecture (100). The centralized server (112) may include or comprise, by way of example and 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 cloud service or portion of a system, a home server, hardware running a virtual server, one or more processors executing code to function as a server, one or more machines performing server-side functionality described herein, at least a portion of any of the above, some combination thereof.

[0051] In one embodiment, the one or more first computing devices (102), one or more mobile devices (not shown in FIG. 1 ) may communicate with the system (110) via a set of executable instructions present on any operating system, including, but not limited to, Android, iOS, Kai OS, etc. In one embodiment, the one or more first computing devices (102) and one or more mobile devices may include any electrical, electronic, electromechanical equipment, such as, but not limited to, a mobile phone, a smartphone, a virtual reality (VR) device, an augmented reality (AR) device, a laptop, a general purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device, or a combination of one or more of the above devices, and the computing device may include one or more built-in or external accessories, including, but not limited to, a visual aid device such as a camera, a hearing aid, a microphone, a keyboard, an input device that receives input from a user, e.g., a touchpad, a touch-enabled screen, an electronic pen, a receiving device for receiving any auditory or visual signal in any range of frequencies, a transmitting device capable of transmitting any auditory or visual signal in any range of frequencies. It should be appreciated that the one or more first computing devices (102) and the one or more mobile devices are not limited to the above-mentioned devices, and various other devices may be used. The smart computing device may be one of a number of suitable systems for storing data and other private / confidential information.

[0052] FIG. 2, with reference to FIG. 1, illustrates an exemplary representation of a data receiver module (110) for facilitating a real-time event data feed according to one embodiment of the present disclosure. In one aspect, the system (110) may include one or more processors (202). The one or more processors (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuits, and / or any device that processes data based on computational instructions. Among other capabilities, the one or more processors (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the data receiver module (110). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium that may be fetched and executed to generate or share data packets over a network service. The memory (204) may include any non-transitory storage device, including, for example, a volatile memory such as a RAM or a non-volatile memory such as an EPROM, a flash memory, etc.

[0053] In one embodiment, the system (110) may include an interface 206. The interface 206 may include various interfaces, such as interfaces to data input and output devices, referred to as I / O devices, storage devices, and the like. The interface 206 may facilitate communication of the system (110). The interface 206 may also provide a communication path to one or more components of the data receiver module (110). Examples of such components include, but are not limited to, a processing engine 208 and a database 210.

[0054] The processing engine (208) may be implemented as a combination of hardware and programming (e.g., programmable instructions) to implement one or more functions of the processing engine (208). In the examples described herein, such a combination of hardware and programming may be implemented in a number of different ways. For example, the programming for the processing engine (208) may be processor-executable instructions stored on a non-transitory machine-readable storage medium, and the hardware for the processing engine (208) may include processing resources (e.g., one or more processors) to execute such instructions. In this example, the machine-readable storage medium may store instructions that, when executed by the processing resources, implement the processing engine (208). In such an example, the system (110) may include a machine-readable storage medium that stores instructions and processing resources for executing the instructions, or the machine-readable storage medium may be separate but accessible to the system (110) and the processing resources. In other examples, the processing engine (208) may be implemented by electronic circuitry.

[0055] The processing engine (208) may include one or more engines selected from a data acquisition engine (212), a machine learning (ML) engine (214), and any other engines (216).

[0056] 2B illustrates an exemplary representation of a presented method (250) for detecting and handling a machine emergency within a network (106) according to one embodiment of the present disclosure. As shown, the method (250) may include receiving, at 252, by one or more processors (202) a first set of data packets associated with a plurality of messages from one or more first computing devices (102) within the network (106). For example, the plurality of messages may include information about one or more first computing devices, such as user equipment (UE), including any handheld device, telephone, laptop, pager, mobile radio, smartphone, laptop, tablet, etc.

[0057] The method may also include, at 254, receiving, by the one or more processors (202), a second set of data packets associated with the plurality of messages from one or more first base stations (104) in the network. For example, the messages may include information for one or more base stations, such as a macro cell, a micro cell, a pico cell, and the like.

[0058] Further, at 256, the method may include receiving, by the one or more processors 202, a third set of data packets associated with a plurality of messages from an open radio access network (O-RAN) radio (RU) 108 in the network. For example, the plurality of messages may include information about the open network.

[0059] The method may include, at 258, receiving, by the one or more processors (202), a fourth set of data packets associated with a plurality of messages from a plurality of nodes (114) in the network. For example, the plurality of messages may include information about a plurality of nodes, such as gNB nodes, data communications nodes, physical network nodes including data communications equipment or devices between a data terminal equipment (DTE) and a data transmission circuit, Internet networks, LANs and wide area networks, telecommunications networks, cable systems, etc.

[0060] The method may further include, at 260, extracting by a machine learning (ML) engine (214) associated with the one or more processors (202) a set of attributes from the first, second, third and fourth sets of received data packets, the set of attributes associated with one or more emergency situations associated with the one or more first computing devices (102), the one or more base stations (104), the O-RAN-RU (108), and the plurality of nodes (114). For example, the system (110) may be configured to sense any type of anomaly or emergency among the one or more first computing devices (102), the one or more base stations (104), the O-RAN-RU (108), and the plurality of nodes (114).

[0061] Additionally, the method may further include classifying, by the ML engine 214, one or more emergency situations into a set of predefined classes based on a predefined set of instructions. For example, the system 110 may identify a machine emergency type in a 3GPP network / device (covering LTE, 5G, 6G), enrich the emergency message with appropriate data such as location, machine ID, plant ID, etc., identify an appropriate emergency server that can handle that type of emergency, and redirect the emergency message with the enriched data to the appropriate server.

[0062] 3A and 3B show an example representation of an existing network system architecture and message flows according to one embodiment of the present disclosure. As shown, in one aspect, FIG. 3A shows that the existing emergency definition and handling mechanism in 3GPP addresses human emergencies and does not address machine emergencies. The introduction of IoT and especially IIoT (Industrial IoT) exposes numerous types of emergency situations that need to be handled differently from human emergencies. The existing network may include a long-term evolution (LTE) 306, a mobility management entity (302) or MME (302), a home subscriber server (304) or HSS (304), a serving gateway (GW) (308), a PDN gateway (310), a service call session control function (S-CSCF 312), a proxy CSCF 314 (P-CSCF 314), a media gateway (MGW) (318), a media gateway control function (MGCF) (320), a public switched telephone network (PSTN) (322), a location lookup function (LRF) (324), an emergency (E)-CSCF (316), and a public-safety answering point (PSAP) (326). For example, a UE using LTE (306) may request an emergency attach to preferentially connect to an emergency access point name (APN). A signal is sent by the S-CSCF (312) for IP Multimedia System (IMS) emergency registration. The P-CSCF (314) detects the emergency Request-Uniform Resource Identifier (R-URI) and forwards the invitation to the E-CSCF (316). The E-CSCF (316) queries the UE location and forwards to the appropriate PSAP (326). A user plane may be established for voice via the MGW (318) and MGCF (320). The PSAP (326) may also look up the UE location via the LRF (324) to dispatch emergency services to the correct street address.

[0063] 3B shows an exemplary representation of an existing emergency call sequence between a UE (352) and a PSAP (326). For example, the UE (352) detects and initiates an emergency call and allocates a location, a SIP INVITE(emergency) to the P-CSCF (314). The P-CSCF (314) detects the emergency number or URN. The P-CSCF (314) again sends a SIP INVITE(emergency) to the E-CSCF (316) and a SIP Option Location / Routing Request, which the LRF (324) accepts. The E-CSCF (316) updates the R-URI to an Emergency Services Query Key (ESQK) and then sends the SIP INVITE to the PSAP (326). The PSAP (326) requests a location from the LRF (324), which responds with the location details.

[0064] In one example, notification of emergency services to the network is via carrying a normal emergency type information-establishment cause as part of the service request. Emergency access can be requested by the UE (User Equipment) or mobile device via an Establishment_Cause IE that is part of the service request IE sent as part of the Attach / PDU Establishment / Modify procedure. For example, emergency access can be requested in 5G NR: Establishment_Cause ::= ENUMERATED { emergency, highPriorityAccess, mt-Access, mo-Signalling, Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-priorityAccess,mcsPriorityAccess, spare6, spare5, spare4, spare3, spare2, spare1} It can be given by:

[0065] As shown, there is no way in current cellular systems to communicate to the network any other emergency types that may arise from industrial IoT or machine types. Therefore, in current systems, the network always assigns a default QoS profile to machine emergency data and treats them as regular Internet data, which is always on a best effort basis.

[0066] To accommodate such machine emergency requirements, we propose a new establishment cause IE to handle such machine emergency scenarios.

[0067] FIG. 4 illustrates an example representation of a presented network system architecture, according to one embodiment of the present disclosure. As shown, the presented network may include a Long Term Evolution (LTE) 306, a Mobility Management Entity (302) or MME (302), a Home Subscriber Server (304) or HSS (304), a Serving Gateway (GW) (308), a PDN Gateway (310), a Service Call Session Control Function (S-CSCF 312), a Proxy CSCF 314 (P-CSCF 314), a Media Gateway (MGW) (318), a Media Gateway Control Function (MGCF) (320), a Public Switched Telephone Network (PSTN) (322), a Location Lookup Function (LRF) (324), an Emergency (E)-CSCF (316), and a Machine Emergency Response Server (MERS) (402) communicatively coupled to a Machine Emergency Response (MERS) Handler (402) that may reside within an IMS entity.

[0068] In some embodiments of communicating machine emergency, one possible way is to use IMS to share a recorded voice message / SMS to a pre-configured number that may belong to the first / secondary responder. To communicate the same application, MERS (402) can use AT interface to send AT command to modem to share a pre-configured voice message to a pre-configured number. This pre-configured message or pre-configured number can be part of the image in the device in memory storage (ROM) or can be configured by the application / emergency server via http / TCP / MQTT message.

[0069] In one exemplary embodiment, at least three mechanisms for conveying the machine emergency type may be provided by MERS (402). In one exemplary embodiment, the reserve values ​​in the existing EstablishmentCause IE are: EstablishmentCause ::= ENUMERATED { emergency, highPriorityAccess, mt-Access, mo-Signalling, Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-priorityAccess,mcsPriorityAccess, ClassA, ClassB, ClassC, ClassD, spare2, spare1} It can be used as given by:

[0070] In another exemplary embodiment, new information element identifiers (IEIs) may be defined. For example, EstablishmentCause ::= ENUMERATED { ClassA, ClassB, ClassC, ClassD, spare3, spare2, spare1}

[0071] In another exemplary embodiment, a fixed bit stream for identifying the type of machine emergency may be used. For example, EstablishmentCause-ME ::= {11100000} In the above formula, - 8-bit representation :: - 8th bit - Class A - 7th bit - Class B - 6th bit - Class C - 5th bit - Class D - 4th bit - 1st bit - reserved.

[0072] In an exemplary embodiment, a schema for multiple emergency situations may be used. Apart from the above IEI defined to convey the machine emergency type, the following structure: EmergencyType::={ EmergencyClass::={Class A, Class B, Class C, Class D,..}, LocationInfo:={Lat, Long}, <Cell ID> , <Type::={Alert-0, Warning-1, Message-2}, <identifier>::={IMSI / TMSI / P-TMSI>}, <Data::={…..}} It can be given by:

[0073] The defined structure may be shared across the network in at least two possible ways: by initially sending the above defined structure during the PDU establishment procedure, and by sending an initial bit on the establishment cause after the establishment of the PDU to indicate the emergency type and the remainder of the data portion of the packet transfer.

[0074] In an exemplary embodiment, if the computing device does not support GPS / GNSS, the above structural device will share GNSS information on latitude / longitude. If there is no GPS / GNSS capability in the computing device, the network may trigger a measurement report, fetch and report the location information of the device to the LRF / SMLC, through which the emergency server can request the location information (LoC info) via a predefined API in 3GPP / ETSI TS, but is not limited thereto.

[0075] FIG. 5A shows an example of an exemplary call flow for sharing emergency types across the system, so that the network assigns the correct QoS profile and therefore resource management. As shown, SIB 1 broadcasts the capability to support machine type emergency for several classes of machine types. UE 502 (MTC device) reads emergency support and the class (machine type) of UE 502 that can connect to the IOT network. The machine type UE sends an RRCSetupRequest with an establishment cause as a machine type emergency and with other attributes as previously shown (class of emergency type, i.e., class A or class B or class C or class D).

[0076] In an exemplary embodiment, to indicate a mechanical type emergency in the UE / modem, the system may use the application layer in the modem interface, i.e., the AT command interface, to communicate the emergency type, which may then be used by the modem to communicate to the network based on the message / IE. The new AT commands used by the application residing in the end device to communicate to the modem and to the network on the emergency type are highlighted in TABLE 1 below.

[0077] [Table 1]

[0078] For example, an AT command to share the machine emergency type along with its attributes to a modem sent by an application may use a defined value such as, but not limited to, Modem Obtaining application type information by application.

[0079] Another example is that an AT command can be used by the application to inform the modem of the machine emergency type, with the defined values ​​being: <cmd>: "MEMERGENCYTYPE" - indicates that the emergency type settings of the IoT / IIoT device with param1..N are configuration parameters defined by the network or application server. Param 1...N indicates the type or attributes as follows: Class A b. Class B c. Class C d. Class D e. Etc LocInfo CellID Type Identifier = {IMSI,…} <data> Etc <responsetype>: OK / ERROR It can be given by:

[0080] FIG. 5B illustrates another example of a call flow for sharing emergency types across systems so that the network can assign the correct QoS profile and resource management.

[0081] When the modem (510) receives the emergency type from the application (508) via the AT command above over the AT interface, the modem advances the emergency type over the previously defined IE and uses the same part of the service request IE that is then sent as part of the attach (including emergency attach), PDU establishment / modification procedure. Once the network is aware of the emergency cause, the PCF / PCRF assigns the correct QCI / 5QI values ​​as per TABLE 2 defined below or as defined in 3GPP TS 23.501.

[0082] [Table 2]

[0083] In another embodiment, the system comprises: - sending the IMSI / TMSI / P-TMSI as part of the data sent by the device using the newly defined emergency type schema / structure (as described above); - Network triggering for IDENTITY REQ procedure (IMSI as identifier) ​​as mandatory procedure during registration / emergency registration This may enable SIM-less operation.

[0084] FIG. 5C shows another example of a call flow to illustrate the ATTACH procedure including the IDENTITY procedure portion of the Machine Emergency scenario.

[0085] When the modem (510) receives the emergency type from the application (508) via the above AT command over the AT interface, the modem proceeds with the attach (including the emergency attach procedure). When the network (512) notices the attach procedure, in one embodiment, the AMF (506) sends an IDENTITY request to the modem and gets a response from the modem (510). If a timer expires or a maximum number of retries is reached, the AMF (506) sends an attach failure message. In an alternative embodiment, the AMF sends an IDENTITY request to the modem (510) and gets a response from the modem (510). In one embodiment, the AMF sends an IDENTITY request to the modem and gets a response from the modem. Within a predetermined time, the modem (510) provides an attach acknowledgment and the attach procedure is performed on the application (508).

[0086] Figure 6 illustrates an example NB-IOT system according to one embodiment of the present disclosure. As illustrated, for a NB-IOT system, the emergency handler may reside in the MME as an emergency handler proxy, in the MTC-IWF (Interworking Function) (610), or in the Application Server (AS) (626), as illustrated in Figure 6. If the Machine Emergency Handler (402) entity resides in the MME itself, the Machine Emergency Handler (402) entity may handle Class A and Class B type emergency situations with fixed responses that close devices such as sensor types or machines associated with the MTC UE / SIM (616), but are not limited thereto.

[0087] If a Machine Emergency Handler (402) entity is present in the IMS-IWF (602), it can handle machine emergency of types class A, B, C and D. The MME to IMS-IWF, i.e., T5b interface, is enhanced in this case to support the Machine Emergency types.

[0088] In one embodiment, class C and class D type emergencies may be handled in the Application Server (AS) (626) and the IMS-IWF needs to be aware that the call type is a machine emergency call type. In this case, the T5b interface between the MME and the IMS-IWF is enhanced with an emergency type indicator shown in the "emergency schema". It should be understood that the above example covering an IOT system is only an example and the presented invention may be extended to other cellular architectures such as 5G, 6G or any private network variant of the cellular technologies mentioned above.

[0089] In another embodiment, the Emergency Handler (402) entity can reside outside the 5G network in an application server, in such a case a new emergency interface can be defined via a Network Exposure Function (NEF) to reach the emergency handler and set up the appropriate data path between the machine and the server.

[0090] 7A and 7B show an embodiment of an alternative call flow example of how a machine emergency is transferred across a cellular network over IMS in accordance with one embodiment of the present disclosure. As shown, in one embodiment, when the machine type emergency is a Class C or Class D type, the granularity of the emergency is much larger than just the machine, in such a case the emergency server initiates a data channel with the emergency device and simultaneously initiates a broadcast type with multiple other registered numbers called emergency responders.

[0091] In yet another exemplary embodiment, as shown in FIG. 7B, when the type of machine type emergency is Class C or Class D type, the emergency handler can use the Cell Broadcast Center Function (CBCF) / Public Warning System (PWS) to initiate broadcast of the emergency data type. The emergency handler can also use any other broadcast / multicast mechanism to initiate broadcast of relevant data. When a Class C or Class D type emergency is indicated, data not only from the device BUT that is hosting the device across the plant / factory is searched by the emergency server to discover the nature of the emergency. This is also assisted by the human responders that are part of the broadcast group.

[0092] [Table 3]

[0093] FIG. 8 illustrates an exemplary computer system in which or by which embodiments of the present disclosure may be utilized. As shown in FIG. 8, computer system 800 may include an external storage device 810, a bus 820, a main memory 830, a read-only memory 840, a mass storage device 850, a communication port 860, and a processor 870. Those skilled in the art will appreciate that a computer system may include more than one processor and communication port. Examples of processor 870 include, but are not limited to, an Intel® Itanium® or Itanium 2 processor, or an AMD® Opteron® or Athlon MP® processor, a Motorola® line of processors, a FortiSOC™ system-on-chip processor, or other additional processors. Processor 870 may include various modules related to embodiments of the present invention. The communication port 860 may be any of an RS-232 port for use with a modem-based dial-up 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 port 860 may be selected depending on the network, such as a local area network (LAN), a wide area network (WAN), or any network to which the computer system connects. The memory 830 may be a random access memory (RAM) or any other dynamic storage device commonly known in the art. The read-only memory 840 may be any static storage device, such as, but not limited to, a programmable read-only memory (PROM) chip for storing static information, such as boot-up or BIOS instructions for the processor 870. The mass storage 850 may be any current or future mass storage solution, which may 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 a Universal Serial Bus (USB) and / or Firewire interface), such as those available from Seagate (e.g., the Seagate Barracuda 782 family) or Hitachi (e.g., the Hitachi Deskstar 8K800), one or more optical disks, such as an array of disks (e.g., a SATA array) and Redundant Array of Independent Disks (RAID) storage available from a variety of providers, including Dot Hill Systems Corp., LaCie, Nexsan Technologies, Inc., and Enhance Technology, Inc.

[0094] Bus 820 communicatively couples processor 870 to other memory, storage, and communication blocks. Bus 820 may be, for example, a peripheral component interconnect (PCI) / PCI-extension (PCI-X) bus, small computer system interface (SCSI), USB, etc., for connecting expansion cards, drives, and other subsystems, as well as other buses, such as a front-side bus (FSB) that connects processor 870 to a software system.

[0095] Optionally, operator and management interfaces, such as a display, keyboard, and cursor control devices, may also be coupled to bus 820 to support an operator to directly interact with the computer system. Other operator and management interfaces may be provided through a network connection connected through communications port 860. External storage device 810 may be any type of external hard drive, floppy drive, IOMEGA® Zip drive, compact disk read only memory (CD-ROM), rewritable compact disk (CD-RW), digital video disk read only memory (DVD-ROM). The components described above are merely meant to illustrate various possibilities. The exemplary computer system described above is in no way intended to limit the scope of this disclosure.

[0096] Thus, the present disclosure provides a unique and efficient solution for identifying different types of machine emergencies and presents mechanisms for handling such emergencies including architectural systems that may be required for handling such emergencies in a time-efficient manner.

[0097] Although considerable emphasis has been placed herein on the preferred embodiment, it will be appreciated that many embodiments may be made and that many changes may be made in the preferred embodiment without departing from the principles of the invention. These and other changes in the preferred embodiment of the invention will be apparent to those skilled in the art from the disclosure herein, and it should therefore be clearly understood that the foregoing description is merely an illustrative implementation of the invention and is not limiting.

[0098] Advantages of the present disclosure Some of the objectives of the present disclosure that are satisfied by at least one embodiment herein are listed herein below.

[0099] The present disclosure provides systems and methods that facilitate SIM-less emergency attach to machine-type devices.

[0100] The present disclosure provides systems and methods covering aspects of emergency attachment to machine-type devices.

[0101] The present disclosure provides a system and method for identifying the type of machine emergency in a 3GPP® network / device (covering LTE, 5G, 6G) and enriching the emergency message with appropriate data such as location, machine ID, plant ID, etc.

[0102] The present disclosure provides a system and method for identifying an appropriate emergency server that can handle that type of emergency and redirecting the emergency message with enriched data to the appropriate server. [Explanation of symbols]

[0103] 100 Network Architecture 102 First Computing Device, User Equipment (UE) 102-1 First computing device, UE 102-2 First computing device, UE 102-3 First computing device, UE 102-N First computing device, UE 104 Base station 104-1 Second computing device, base station 104-2 Second computing device, base station 104-3 Second computing device, base station 104-N Second Computing Device, Base Station 106 Network 108 Open Radio Access Network (O-RAN) Radio (RU) 110 System, data receiver module 112 Centralized Server 114 Fourth computing device, node 200 Figures 202 Processor 204 Memory 206 Interface 208 Processing Engine 210 Database 212 Data Acquisition Engine 214 Machine Learning Engine (ML) 216 other engines 300 Figures 302 Mobility Management Entity, MME 304 Home Subscriber Server, HSS 306 Long Term Evolution, LTE 308 Serving Gateway, GW 310 PDN Gateway 312 Service Call Session Control Function, S-CSCF 314 Proxy CSCF, P-CSCF 316 Emergency (E)-CSCF 318 Media Gateway (MGW) 320 Media Gateway Control Function (MGCF) 322 Public Switched Telephone Network (PSTN) 324 Location Search Function (LRF) 326 Public Safety Answering Point (PSAP) 352 U.S. 354 IP CAN 356 P-CSCF 402 Machine Emergency Response (MERS) Handler, Machine Emergency Response Server (MERS) 502UE 504 NG RAN 506 AMF 508 Application 510 Modem 512 Network 514 SMF 516 PCF 518DN 602 IMS-IWF 604 SMC-SC GMSC / IW MSC 606 SME 608 MTC AAA 610 MTC-IWF (interaction function) 612 CDF / CGF 614 MSC 616 MTC UE / SIM 620SGSN 622 GGSN / P-GW 624 SCS 626 Application Server (AS) 626-1 AS 628-1 AS 700A Figure 700B Figure 800 Computer Systems 810 External storage device 820 Bus 830 Main Memory 840 Read Only Memory 850 Mass Storage Device 860 communication port 870 Processor< / responsetype> < / data> < / cmd> < / identifier>

Claims

1. A system (110) for detecting and handling machine emergencies in a network, comprising: and one or more processors (202) operably coupled to one or more first computing devices (102), one or more base stations (104), an Open Radio Access Network (O-RAN) Radio (RU) (108), and a plurality of nodes (114), wherein the one or more first computing devices (102), the one or more base stations (104), the O-RAN RU (108), and the plurality of nodes (114) are operably coupled to the network, and the one or more processors are coupled to a memory (204), the memory (204) storing instructions that, when executed by the one or more processors (202), cause the system (110) to: receiving a first set of data packets associated with a plurality of messages from the one or more first computing devices (102) in the network (106); receiving a second set of data packets associated with a plurality of messages from the one or more base stations in the network; receiving a third set of data packets associated with a plurality of messages from the O-RAN RU (108) in the network (106); receiving a fourth set of data packets associated with a plurality of messages from the plurality of nodes (114) in the network (106); extracting a set of attributes from the first, second, third and fourth sets of received data packets by using a machine learning (ML) engine (214), the set of attributes associated with one or more emergency situations associated with the one or more first computing devices (102), the one or more base stations (104), the O-RAN-RU (108), and the plurality of nodes (114), the ML engine associated with the one or more processors (202); and causing the ML engine to classify the one or more emergency situations into a set of predetermined classes based on a set of predetermined instructions.

2. 2. The system of claim 1, wherein the ML engine is configured to process and handle the one or more emergency situations based on a set of instructions associated with each of the predetermined classes.

3. 3. The system of claim 2, wherein the ML engine is further configured to define the set of instructions for each of the predefined classes to handle pre-mapped industries.

4. 3. The system of claim 2, wherein the ML engine is further configured to respond to a plurality of real-time machine-type emergency situations occurring within one or more IoT applications.

5. The ML engine (214) defining one or more new emergency types associated with the one or more first computing devices (102), the one or more base stations (104), the O-RAN RU (108), and the plurality of nodes (114); 3. The system of claim 2, further configured to: manage and handle the one or more new emergency types within the network.

6. The ML engine (214) The system (110) of claim 2, further configured to define and classify the one or more new emergency types as new classes of emergency situations.

7. The ML engine (214) 7. The system (110) of claim 6, further configured to automatically or manually handle each new emergency type based on the classification of the one or more new emergency types and a predetermined set of instructions associated with the classification.

8. 2. The system (110) of claim 1, wherein initial bits of the first set of data packets, the second set of data packets, the third set of data packets, and the fourth set of data packets indicate an emergency type, and the remainder of the first set of data packets, the second set of data packets, the third set of data packets, and the fourth set of data packets indicate packet transfers after establishment of a machine assembly.

9. The ML engine (214) receiving a newly defined quality of service for handling one or more emergency situations, the one or more emergency situations being shared among service request causes; configuring and mapping the newly identified QoS profile and / or handling said emergency situation appropriately; 7. The system (110) of claim 6, further configured to interface with and identify the emergency type and required signaling identifier to inform the network of the correct type of QoS profile to identify and apply.

10. The ML engine (214) 7. The system (110) of claim 6, further configured to collect, store in a cloud-based data lake, and process the carefully collected data to extract actionable insights.

11. A user equipment (UE) for detecting and handling a machine emergency in a network, the UE comprising: The system (110) includes one or more processors (202) operably coupled to one or more base stations (104), an open radio access network (O-RAN) radio (RU) (108), and a plurality of nodes (114), the one or more base stations (104), the O-RAN RU (108), and the plurality of nodes (114) are operably coupled to the network, the one or more processors are coupled to a memory (204), the memory (204) storing instructions that, when executed by the one or more processors (202), cause the system (110) to: receiving a first set of data packets associated with a plurality of messages from the UE in the network; receiving a second set of data packets associated with a plurality of messages from the one or more base stations in the network; receiving a third set of data packets associated with a plurality of messages from the O-RAN RU (108) in the network (106); receiving a fourth set of data packets associated with a plurality of messages from the plurality of nodes (114) in the network (106); extracting a set of attributes from the first, second, third and fourth sets of received data packets by using a machine learning (ML) engine (214), the set of attributes associated with one or more emergency situations associated with the UE, the one or more base stations (104), the O-RAN-RU (108), and the plurality of nodes (114), the ML engine associated with the one or more processors (202); and causing the ML engine (214) to classify the one or more emergency situations into a set of predetermined classes based on a predetermined set of instructions.

12. A method (250) for detecting and handling a machine emergency within a network (106), comprising: receiving, by one or more processors (202), a first set of data packets associated with a plurality of messages from one or more first computing devices (102) in the network (106), the one or more processors (202) operatively coupled to the one or more first computing devices (102), one or more base stations (104), an open radio access network (O-RAN) radio (RU) (108), and a plurality of nodes (114), the one or more first computing devices (102), the one or more base stations (104), the O-RAN RU (108), and the plurality of nodes (114) operatively coupled to the network, the one or more processors coupled to a memory (204), the memory (204) storing instructions executed by the one or more processors; receiving, by the one or more processors (202), a second set of data packets associated with a plurality of messages from the one or more base stations (104) within the network (106); receiving, by the one or more processors (202), a third set of data packets associated with a plurality of messages from the O-RAN RU (108) in the network (106); receiving, by the one or more processors (202), a fourth set of data packets associated with a plurality of messages from the plurality of nodes (114) in the network (106); extracting, by the ML engine (214), a set of attributes from the first, second, third and fourth sets of received data packets, the set of attributes associated with one or more emergency situations associated with the one or more first computing devices (102), the one or more base stations (104), the O-RAN-RU (108), and the plurality of nodes (114); and classifying, by the ML engine (214), the one or more emergency situations into a set of predetermined classes based on a predetermined set of instructions.

13. 13. The method of claim 12, further comprising processing, by the ML engine (214), to handle the one or more emergency situations based on a set of instructions associated with each of the predetermined classes.

14. 14. The method of claim 13, further comprising: defining, by the ML engine (214), the set of instructions for each of the predefined classes to handle pre-mapped industry verticals.

15. 14. The method of claim 13, further comprising responding, by the ML engine (214), to a plurality of real-time machine-type emergency situations occurring within one or more IoT applications.

16. defining, by the ML engine (214), one or more new emergency types associated with the one or more first computing devices (102), the one or more base stations (104), the O-RAN RU (108), and the plurality of nodes (114); and managing and handling the one or more new emergency types within the network by the ML engine.

17. 17. The method of claim 16, further comprising defining and classifying the one or more new emergency types as new classes of emergency situations by the ML engine (214).

18. 20. The method of claim 17, further comprising handling each new emergency type by the ML engine (214) automatically or manually based on the classification of the one or more new emergency types and a predetermined set of instructions associated with the classification.

19. 14. The method of claim 13, wherein initial bits of the first set of data packets, the second set of data packets, the third set of data packets, and the fourth set of data packets indicate an emergency type, and the remainder of the first set of data packets, the second set of data packets, the third set of data packets, and the fourth set of data packets indicate packet forwarding after establishment of a machine assembly.

20. receiving, by the ML engine (214), a newly defined Quality of Service (QoS) for handling one or more emergency situations, the one or more emergency situations being shared among service request causes; configuring and mapping the newly identified QoS profile by said ML engine (214) and / or handling said emergency situation appropriately; and interfacing and identifying, by the ML engine (214), an emergency type and a necessary signaling identifier to inform the network of the correct type of QoS profile to identify and apply.

21. 13. The method of claim 12, further comprising collecting, storing, and processing the carefully collected data in a cloud-based data lake by the ML engine (214) to extract actionable insights.

Citation Information

Patent Citations

  • Information processing apparatus, information processing method, and program

    JP2019062361A

  • Internet of things based determination of machine reliability and automated maintainenace, repair and operation (MRO) logs

    US20170011298A1

  • Data analysis and configuration of a distributed radio access network

    US20210243839A1

  • Monitoring the performance of a plurality of network nodes

    WO2021063514A1