WO2018158047A1

WO2018158047A1 - IMS-BASED IoT INTERACTION

Info

Publication number: WO2018158047A1
Application number: PCT/EP2018/052844
Authority: WO
Inventors: Kasper Reinink; Padmavathi SUDARSAN; Elangovan MANICKAM; Anne Yin-Fee Lee
Original assignee: Nokia Solutions And Networks Oy
Priority date: 2017-02-28
Filing date: 2018-02-06
Publication date: 2018-09-07

Abstract

The present disclosure generally discloses improvements in computer performance for supporting interaction with Internet-of-Things (loT) devices using an Internet Protocol (IP) Multimedia Subsystem (IMS) communication network. Various embodiments of the IMS-based loT interaction capability may support embedding of chatbot technology within the IMS communication network for loT interaction. Various embodiments of the IMS-based loT interaction capability may support embedding of chatbot technology within the IMS communication network for loT interaction that satisfies various service level agreement requirements for loT interaction. Various embodiments of the IMS-based loT interaction capability enable a service provider of an IMS communication network to support loT interactions within the IMS network via augmentation of the IMS network with various chatbot capabilities, thereby enabling the service provider to leverage the various capabilities of the IMS communication network to support improved loT interactions for subscribers based on the various chatbot capabilities.

Description

IMS-BASED loT INTERACTION

TECHNICAL FIELD

The present disclosure relates generally to communication networks and, more particularly but not exclusively, to improvements in computer performance to support interaction with Internet-of-Things (loT) devices using an Internet Protocol (IP) Multimedia Subsystem (IMS) network.

BACKGROUND

Internet-of-Things (loT) devices are becoming increasingly prevalent and tend to be highly diverse (e.g., including many types of devices serving many different purposes). This prevalence and diversity of the loT devices presents various challenges in controlling and managing the loT devices, especially since users increasingly want to be able to remain in continuous communication with the loT devices such that the users are able to receive notifications and issue commands at any time and any place.

SUMMARY

The present disclosure generally discloses improvements in computer performance for supporting interaction with Internet-of-Things (loT) devices using an Internet Protocol (IP) Multimedia Subsystem (IMS) communication network.

In at least some embodiments, an apparatus is provided. The apparatus includes a processor and a memory communicatively connected to the processor. The processor is configured to receive, via an IMS network, a first message including a communication associated with an loT device of a subscriber. The processor is configured to translate the communication, between a subscriber-supported communication format of the subscriber and an loT device communication format supported by the loT device, to provide thereby a translated communication associated with the loT device of the subscriber. The processor is configured to send, via the IMS network, a second message including the translated communication associated with the loT device of the subscriber. In at least some embodiments, a computer- readable storage medium stores instructions which, when executed by a computer, cause the computer to perform a corresponding method for improving computer performance in IMS-based loT interaction. In at least some embodiments, a corresponding method is configured for improving computer performance in IMS-based loT interaction.

In at least some embodiments, an apparatus is provided. The apparatus includes a processor and a memory communicatively connected to the processor. The processor is configured to support a media session between a subscriber device of a subscriber and a server of an IMS network. The processor is configured to support, via the media session, transfer of a communication associated with an loT device of the subscriber, wherein the communication associated with the loT device of the subscriber is in a subscriber-supported communication format. In at least some embodiments, a computer-readable storage medium stores instructions which, when executed by a computer, cause the computer to perform a corresponding method for improving computer performance in IMS-based loT interaction. In at least some embodiments, a corresponding method is configured for improving computer performance in IMS-based loT interaction.

In at least some embodiments, an apparatus is provided. The apparatus includes a processor and a memory communicatively connected to the processor. The processor is configured to obtain, at an loT device of a subscriber, a communication intended for the subscriber, wherein the communication is in an loT device communication format of the loT device, the processor is configured to send, from the loT device toward a server of an IMS network, the communication intended for the subscriber. In at least some embodiments, a computer-readable storage medium stores instructions which, when executed by a computer, cause the computer to perform a corresponding method for improving computer performance in IMS-based loT interaction. In at least some embodiments, a corresponding method is configured for improving computer performance in IMS-based loT interaction.

BRIEF DESCRIPTION OF THE DRAWINGS

The teachings herein can be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which:

FIG. 1 depicts an example communication system configured to support interaction by a subscriber with loT devices via an IMS network using an IMS-based loT interaction capability;

FIGs. 2A and 2B depict an example process, illustrated within the context of the communication system of FIG. 1 , by which the subscriber may use the subscriber device to issue an loT device command to an loT device and may receive an associated loT device response from the loT device after execution of the loT device instruction by the loT device;

FIGs. 3A - 3C depict an example process by which a subscriber may use the subscriber device to issue an loT device command to an loT device and may receive an associated loT device response from the loT device after execution of the loT device instruction by the loT device;

FIG. 4 depicts an embodiment of a method for use by an element of an IMS network to support an IMS-based loT interaction capability;

FIG. 5 depicts an embodiment of a method for use by a subscriber device to support an IMS-based loT interaction capability;

FIG. 6 depicts an embodiment of a method for use by an loT device to support an IMS-based loT interaction capability; and

FIG. 7 depicts a high-level block diagram of a computer suitable for use in performing various functions presented herein.

To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures.

DETAILED DESCRIPTION

The present disclosure generally discloses improvements in computer performance for supporting interaction with Internet-of-Things (loT) devices using an Internet Protocol (IP) Multimedia Subsystem (IMS) communication network, including support for an IMS-based loT interaction capability configured to support interaction with loT devices using an IMS

communication network. Various embodiments of the IMS-based loT interaction capability may support embedding of chatbot technology within the IMS communication network for loT interaction. Various embodiments of the IMS-based loT interaction capability may support embedding of chatbot technology within the IMS communication network for loT interaction that satisfies various service level agreement (SLA) requirements for loT

interaction. Various embodiments of the IMS-based loT interaction capability enable a service provider of an IMS communication network to support loT interactions within the IMS network via augmentation of the IMS network with various chatbot capabilities, thereby enabling the service provider to leverage the various capabilities of the IMS communication network to support improved loT interactions for subscribers based on the various chatbot capabilities. Various embodiments of the IMS-based loT interaction capability enable use of a single, natural human interface in order to communicate with diverse loT equipment supporting diverse communication interfaces (e.g., multiple loT device types, multiple loT suppliers, and the like) in a manner that meets various specifications (e.g., security, reliability, quality-of-service, public safety, or the like, as well as various combinations thereof). Various embodiments of the IMS-based loT interaction capability may support a conversational loT platform using an IMS-embedded chatbot that is

configured to use self-learning natural language processing capabilities and intelligent virtual assistant translation capabilities to mediate between a human subscriber and loT devices. Various embodiments of the IMS-based loT interaction capability may support a chatbot-based speech interface to messaging converter on IMS, with self-learning capabilities to adapt to loT domain-specific behavior and the ability to securely connect subscribers and loT devices for improved interaction with the loT devices. Various

embodiments of the IMS-based loT interaction capability enable a human subscriber to use a natural language interface (e.g., speech, text, or the like) to interact with diverse types of remote loT equipment across one or more networking and operator domains in a manner that incorporates end-to-end security at various network layers, applications, and devices (e.g., security may include access control, authentication (e.g., subscriber authentication and loT device authentication), confidentiality, data integrity, availability (e.g., ensuring availability of service for mission critical applications), or the like, as well as various combinations thereof). It will be appreciated that these and various other embodiments and potential advantages of the IMS-based loT interaction capability may be further understood by way of reference to the example communication system of FIG. 1 .

FIG. 1 depicts an example communication system configured to support interaction by a subscriber with loT devices via an IMS network using an IMS-based loT interaction capability.

The communication system 100 includes a subscriber device 1 10 of a subscriber 101 , a set of Internet-of-Things (loT) devices 120-1 - 120-N (collectively, loT devices 120), and an Internet Protocol (IP) Multimedia Subsystem (IMS) network 130.

The subscriber device 1 10 of the subscriber 101 is a device that may be used by subscriber 101 to perform various functions related to interacting with various loT devices 120. The subscriber device 1 10 may include various types of user interfaces by which the subscriber 101 may interact with various loT device 130. For example, the subscriber device 1 10 may include one or more content entry interfaces (e.g., a microphone for providing audio input, one or more touchscreens or keyboards for providing text-based input, or the like, as well as various combinations thereof) by which the subscriber 101 may initiate loT device instructions to the loT devices 120. For example, the subscriber device 1 10 may include one or more content presentation interfaces (e.g., one or more speakers, one or more graphical user interfaces, or the like, as well as various combinations thereof) by which the subscriber 101 may review loT device responses from the loT devices 120. The subscriber device 1 10 is configured to communicate via the IMS network 130, which may include support for IMS-based communications, support for communications compatible with IMS-based communications, or the like, as well as various combinations thereof. For example, the subscriber device 1 10 may be a smartphone, a tablet computer, a laptop computer, a desktop computer, or the like. The subscriber device 1 10 may be configured to perform various other functions related to interacting with various loT devices 120 via IMS network 130.

The loT devices 120 may include loT devices with which the subscriber 101 may interact using the subscriber device 1 10. For example, the loT devices 120 may include loT end devices with which the subscriber 101 may interact (e.g., sensors, actuators, or the like), loT gateway devices which may be configured to interact with loT end devices at a particular location associated with the subscriber (e.g., a home loT gateway configured to control various loT devices of a home, a business loT gateway configured to control various loT devices of a business, a mobile loT gateway configured to control various loT devices of a mobile platform such as a car or bus, or the like, as well as various combinations thereof). The loT devices 120 may include devices local to the location of the subscriber 101 (e.g., subscriber 101 uses subscriber device 1 10 to control home loT devices while the subscriber is home), devices remote from the location of the subscriber 101 (e.g., subscriber 101 uses subscriber device 1 10 to control home loT devices while the subscriber is at work or traveling), or the like, as well as various combinations thereof. The loT devices 120 are expected to support various types of loT device communication formats (e.g., communication interfaces, languages, commands, command syntaxes, or the like, as well as various combinations thereof). This may be the case for different loT device manufactures and even for different types of loT devices whether supplied by the same manufacturer or different manufacturers (e.g., security systems and climate control systems are typically quite different and, as such, may support different loT device communication formats even when provided by the same loT device supplier). The loT devices 120 may include various other types of loT devices with which the subscriber 101 may interact using the subscriber device 1 10 via the IMS network 130.

The IMS network 130 is configured to support the IMS-based loT interaction capability, thereby enabling subscriber 101 to control various loT devices 120 via subscriber device 1 10.

The IMS network 130 is configured to support various communications capabilities which may be used in order to support the IMS-based loT interaction capability. The IMS network 130 may support IMS control signaling and associated IMS control sessions, IMS-established media sessions (e.g., data sessions, voice sessions, video sessions, or the like), or the like, as well as various combinations thereof. The communication capabilities supported by the IMS network 130 may be based on various IMS- based network elements, various IMS signaling protocols, various media communication protocols, or the like, as well as various combinations thereof. The IMS-based network elements may include call session control functions (CSCFs), home subscriber servers (HSSs), media resource functions (MRFs), media gateway functions (MGFs), or the like, as well as various combinations thereof. The IMS signaling protocols may include Session Initiation Protocol (SIP) or the like. The media communication protocols may include Internet Protocol (IP), User Datagram Protocol (UDP), Real-time Transport Protocol (RTP), or the like, as well as various combinations thereof. For example, speech associated with the subscriber 101 for interaction with an loT device 120 by the subscriber (e.g., speech of the subscriber 101 or speech intended for the subscriber 101 ) may be encoded and transported between the subscriber device 1 10 and the NLP / IVA 135 in IP packets, which may be encapsulated as UDP/IP packets, as RTP/IP packets, or the like. Similarly, for example, text associated with the subscriber 101 for interaction with an loT device 120 by the subscriber (e.g., text of the subscriber 101 or text intended for the subscriber 101 ) may be encoded and transported between the subscriber device 1 10 and the NLP / IVA 135 in IP packets, which may be encapsulated as UDP/IP packets, as RTP/IP packets, or the like. The IMS network 130 may be configured to support various other communications capabilities which may be used in order to support the IMS-based loT interaction capability.

The IMS network 130 includes an IMS access network 131 and an IMS core network 133. The IMS access network 131 includes an IMS access point 132. The IMS core network 133 includes IMS network elements 134, a Natural Language Processing (NLP) / Intelligent Virtual Assistant (IVA) 135, an loT device interaction database 136, a machine-to-machine (M2M) interface (l/F) element 138, and a software development kit (SDK) 139. The IMS access network 131 and the IMS core network 133 may be implemented as physical networks, as cloud-based networks such as where the IMS access network 1 31 is an edge cloud and the IMS core network 133 is a core cloud (e.g., IMS access network 131 is an edge cloud with mobile edge computing (MEC) that is capable of communicating with the cloud-based IMS core network 133), or the like. The IMS access network 131 and the IMS core network 133 may communicate via various types of underlying communication networks (e.g., Ethernet-based networks such as Metro Ethernet networks, optical networks, or the like, as well as various combinations thereof). The IMS core network 133 may be configured to interface with various types of packet data networks (PDNs), such as public PDNs (e.g., the Internet), private PDNs (e.g., enterprise networks, data center networks, or the like), or the like, as well as various combinations thereof.

The IMS access network 131 includes the IMS access point 132, which is the point of access to the IMS network 130 for subscriber device 1 10. The IMS access point 132 may be configured to recognize and propagate IMS- based messages including propagating IMS signaling messages between the subscriber device 1 10 and the IMS core network 133 (e.g., IMS signaling messages configured for establishing and terminating IMS control sessions between the subscriber device 1 10 and the NLP / IVA 135, IMS signaling messages used for establishing and terminating IMS-established media sessions between the subscriber device 1 10 and the NLP / IVA 135, IMS signaling messages using for monitoring IMS control sessions between the subscriber device 1 10 and the NLP / IVA 135, or the like, as well as various combinations thereof), propagating media messages between the subscriber device 1 10 and the IMS core network 133 via IMS-established media sessions between the subscriber device 1 10 and the NLP / IVA 135 (e.g., voice messages exchanged between the subscriber device 1 10 and the NLP / IVA 135 that are associated with interaction with loT devices 120 via IMS- established media sessions, text messages exchanged between the subscriber device 1 10 and the NLP / IVA 135 that are associated with interaction with loT devices 120 via IMS-established media sessions, or the like, as well as various combinations thereof). The IMS access device 132 may be configured to provide other functions supporting the IMS-based loT interaction capability.

The IMS core network 133 includes the IMS network elements 134, the NLP / IVA 135, the loT device interaction database 136, the M2M l/F element 138, and the SDK 139. The IMS network elements 134 may include any network elements typically deployed within an IMS core network, such as CSCFs (e.g., interrogating CSCFs (l-CSCFs), proxy CSCFs (P-CSCFS), serving CSCFs (S-CSCFS), or the like), HSSs, MRFs, MGFs, various types of servers (e.g., IMS application servers, rich communication services (RCS) servers, or the like), or the like, as well as various combinations thereof. The NLP / IVA 135 is configured to perform various functions to support the IMS- based loT interaction capability, thereby enabling the subscriber 101 to interact with various loT devices 120 via subscriber device 1 10. The loT device interaction database 136 is configured to store information which may be used by the NLP / IVA 135 to perform various functions to support the IMS- based loT interaction capability (e.g., subscriber information associated with subscribers such as subscriber 101 , loT device information associated with loT devices 120, or the like, as well as various combinations thereof). The M2M l/F element 138 is configured to operate as a communication interface between the IMS network 130 and the loT devices 120. The SDK 139 is configured to enable third parties (e.g., loT device suppliers, loT integration operators, or the like, as well as various combinations thereof) to interact with the IMS core network 133 to support or utilize the IMS-based loT interaction capability. The operation of the various components of the IMS core network 133 in supporting the IMS-based loT interaction capability is discussed further herein.

The IMS network elements 134 may be configured to support various communications between the subscriber device 1 10 of the subscriber 101 and the NLP / IVA 135. The IMS network elements 134 may include IMS network elements (e.g., CSCFs or the like) configured to recognize and propagate IMS signaling messages between the subscriber device 1 10 and the NLP / IVA 135 (e.g., IMS signaling messages configured for establishing and terminating IMS control sessions between the subscriber device 1 10 and the NLP / IVA 135, IMS signaling messages using for monitoring IMS control sessions between the subscriber device 1 10 and the NLP / IVA 135, IMS signaling messages used for establishing and terminating IMS-established media sessions between the subscriber device 1 10 and the NLP / IVA 135, or the like, as well as various combinations thereof). The IMS network elements 134 may include IMS network elements (e.g., media gateways or the like) configured to recognize and propagate media messages between the subscriber device 1 10 and the NLP / IVA 135 via IMS-established media sessions between the subscriber device 1 10 and the NLP / IVA 135 (e.g., messages transporting voice exchanged via a voice session established between the subscriber device 1 10 and the NLP / IVA 135, messages transporting text via a data session established between the subscriber device 1 10 and the NLP / IVA 135, or the like, as well as various combinations thereof). The IMS network elements 134 may be configured to provide various other functions in support of the IMS-based loT interaction capability.

The NLP / IVA 135 is configured to provide various functions to support the IMS-based loT interaction capability.

The NLP / IVA 135 is configured to facilitate communication between the subscriber 101 and the loT devices 120, including communications from the subscriber 101 to the loT devices 120 and communications from the loT devices 120 to the subscriber 101 .

The NLP / IVA 135 is configured to facilitate communications between the subscriber device 1 10 and the loT devices 120.

The NLP / IVA 135 is configured to support establishment of an IMS- established media session between the NLP / IVA 135 and the subscriber device 1 10, based on IMS signaling between the NLP / IVA 135 and the subscriber device 1 10, for use in exchanging loT device messages (in the subscriber-based communication format of the subscriber 101 ) between the subscriber device 1 10 and the NLP / IVA 135 (e.g., loT device instructions received from the subscriber device 1 10 and intended for delivery to loT devices 120, subscriber-based loT device responses sent from the NLP / IVA 135 to the subscriber device 1 10 based on loT device responses received by the NLP / IVA 135 from loT devices 120, or the like, as well as various combinations thereof). The NLP / IVA 135 is configured to support

termination of the IMS-established media session between the NLP / IVA 135 and the subscriber device 1 10, based on IMS signaling between the NLP / IVA 135 and the subscriber device 1 10, when the IMS-established media session is no longer needed.

The NLP / IVA 135 is configured to support IMS-based messaging for use in exchanging loT device messages (in the loT device communication formats of the loT devices 120, respectively) between the NLP / IVA 135 and the loT devices 120 (e.g., machine-based loT device instructions sent from the NLP / IVA 135 to loT devices 120 based on loT device instructions received by the NLP / IVA 135 from the subscriber device 1 10, loT device responses received by the NLP / IVA 135 from the loT devices 120 and intended for delivery to the subscriber device 1 10, or the like, as well as various combinations thereof). The exchanging of the loT device messages between the NLP / IVA 135 and the loT devices 120 also may utilize other communications capabilities (at least some of which may be supported by the NLP / IVA 135), such as data structuring capabilities for structuring data of the loT device messages (e.g., Extensible Markup Language (XML), JavaScript Object Notation (JSON), or the like), data communication protocols (e.g., SIP, the Representation State Transfer (REST) protocol, or the like), or the like, as well as various combinations thereof.

The NLP / IVA 135 is configured to facilitate communications between the subscriber device 1 10 and the loT devices 120 based on various other types of signaling, messaging, protocols, or the like, as well as various combinations thereof.

The NLP / IVA 135 is configured to facilitate communications from the subscriber 101 to the loT devices 120. The NLP / IVA 135 is configured to receive an loT device instruction of the subscriber 101 that is provided by the subscriber 101 via the subscriber device 1 10 using a natural language communication format of the subscriber 101 (received via an IMS-established media session between the NLP / IVA 135 and the subscriber device 1 10, such as a voice session, data session, or the like), identify the subscriber 101 from which the loT device instruction is received, determine the natural language communication format of the subscriber 101 from which the loT device instruction is received, identify the loT device 120 for which the loT device instruction of the subscriber 101 is intended, determine the loT device communication format of the loT device 120 for which the loT device instruction of the subscriber 101 is intended, translate the loT device instruction of the subscriber 101 from the natural language communication format of the subscriber 101 to the loT device communication format of the loT device 120 for which the loT device instruction of the subscriber 101 is intended to provide thereby a machine-based loT device instruction for the loT device 120, and send the machine-based loT device instruction for the loT device 120 toward the loT device 120 using an IMS signaling message.

These operations of NLP / IVA 135 may be further understood by way of reference to FIGs. 2A - 2B and FIGs. 3A - 3C.

The NLP / IVA 135 is configured to facilitate communications from the loT devices 120 to the subscriber 101 . The NLP / IVA 1 35 is configured to receive an IMS signaling message including an loT device communication of an loT device 120 that is provided by the loT device 120 (e.g., a response to an instruction, information of interest to the subscriber 101 , or the like), identify the loT device 120 from which the loT device communication is received, determine the loT device communication format of the loT device 120 from which the loT device communication is received, identify the subscriber 101 for which the loT device communication is intended, determine the natural language communication format of the subscriber 101 for which the loT device communication is intended, translate the loT device

communication from the loT device communication format of the loT device 120 to the natural language communication format of the subscriber 101 to provide thereby a subscriber-based loT device communication for the subscriber 101 , identify the subscriber device 1 10 for which the subscriber- based loT device communication for the subscriber 101 is intended, and send the subscriber-based loT device communication for the subscriber 101 toward the subscriber device 1 10 of the subscriber 101 (sent via an IMS-established media session between the NLP / IVA 135 and the subscriber device 1 10, such as a voice session, data session, or the like).

The NLP / IVA 135, as noted above, is configured to support translation between a natural language communication format of the subscriber 101 and loT device communication formats of the loT devices 120 in order to facilitate communications between the subscriber 101 and the loT devices 120.

The NLP / IVA 1 35 is configured to support natural language processing functions. The natural language processing functions enable the NLP / IVA 135 to understand natural language of the subscriber 101 , which may include translating a natural language instruction of the subscriber 101 into an understanding of the meaning of the natural language instruction of the subscriber 101 (e.g., for an instruction of the subscriber 101 that is intended for one of the loT devices 120), generating a natural language communication for the subscriber 101 based on an understanding of the meaning of the natural language communication for the subscriber 101 (e.g., for a response of an loT device 120 that is intended for the subscriber 101 ), or the like, as well as various combinations thereof.

The NLP / IVA 135 is configured to support intelligent virtual assistant functions. The intelligent virtual assistant functions enable the NLP / IVA 135 to translate between an understanding of the meaning of natural language of the subscriber 101 and loT device communication formats of the loT devices 120, which may include translating an understanding of the meaning of a natural language instruction of the subscriber 101 into an loT device instruction that is based on the loT device communication format of the loT device 120 for which the instruction of the subscriber 101 is intended (e.g., for an instruction of the subscriber 101 that is intended for one of the loT devices 120), translating an loT device communication of an loT device 120 that is based on the loT device communication format of the loT device 120 into an understanding of the meaning of a natural language communication which can communicate the loT device communication of the loT device 120 to the subscriber 101 (e.g., for a response of an loT device 120 that is intended for the subscriber 101 ), or the like, as well as various combinations thereof.

The NLP / IVA 135 may be configured to provide various functions of the IMS-based loT interaction capability based on information stored within the loT device interaction database 136.

The loT device interaction database 136 may be configured to provide various functions and information in order to support the IMS-based loT interaction capability. The loT device interaction database 136 may be configured to provide various functions and information in order to support user interaction with loT device.

The loT device interaction database 136 may store subscriber information associated with subscribers such as the subscriber 101 . For example, the subscriber information for subscriber 101 may include subscriber account information associated with the subscriber 101 (e.g., name, address, preferences, or the like, as well as various combinations thereof). For example, the subscriber information for subscriber 101 may include subscriber communication format information associated with the subscriber 101 (e.g., the language(s) used by the subscriber). For example, the subscriber information for subscriber 101 may include subscriber device information associated with the subscriber device 1 10 of the subscriber 101 (e.g., a device identifier, device address information (e.g., an IP address, a SIP address, or the like, as well as various combinations thereof), device manufacturer information, device capability information, or the like, as well as various combinations thereof). For example, the subscriber information for subscriber 101 may include subscriber loT device information, which may include information indicative of the loT devices 120 associated with the subscriber 101 and, for each of the loT devices 120 associated with the subscriber 101 , information describing the loT device associated with the subscriber 101 (e.g., manufacturer, model number, software version information, device identifier information, device address information, device capability information, or the like, as well as various combinations thereof). The subscriber information associated with subscribers may include various other subscriber-related information which may be used by the NLP / IVA 135 to provide various functions of the IMS-based loT interaction capability.

The loT device interaction database 136 may store loT device information associated with the loT devices 120. The loT device information may include a catalogue of loT device communication formats for various types of loT devices 120. The loT device communication formats of the loT devices 120 may specify communication interface information of the loT devices 120, communication syntax information of the loT devices 120, communication Application Programming Interfaces (API) information for APIs supported by the loT devices 120, or the like, as well as various combinations thereof. The loT device communication formats for the loT devices 120, as discussed above, may vary widely for different types of loT devices, different loT device manufacturers, or the like, as well as various combinations thereof. The loT device information associated with subscribers may include various other subscriber-related information which may be used by the NLP / IVA 135 to provide various functions of the IMS-based loT interaction capability.

The loT device interaction database 136 may be configured to provide various other functions and information in order to support the IMS-based loT interaction capability.

The NLP / IVA 135 may be configured to support various self-learning capabilities. The self-learning capabilities may include self-learning natural language processing capabilities, self-learning intelligent virtual assistant capabilities, or the like, as well as various combinations thereof. The self- learning capabilities may be based on machine learning technology. The self- learning capabilities may enable the NLP / IVA 135 to adapt to loT domain- specific behavior so as to securely connect subscribers and loT devices for improved interaction with the loT devices. The self-learning capabilities of the NLP / IVA 135 may rely on information of the loT device interaction database 136, result in changes to information of the loT device interaction database 136, or the like, as well as various combinations thereof. The NLP / IVA 135 may be configured to support various other self-learning capabilities.

The NLP / IVA 135 also may be referred to herein as an IMS-based loT chatbot server or chatbot, as it may be configured to function in a manner similar to a chatbot (or using chatbot type capabilities) in order to enable subscriber 101 to use subscriber device 1 10 to interact with various loT devices 120 via the IMS network 130 based on chat-type or chat-like capabilities.

The NLP / IVA 135 may be configured to provide various other functions to support the IMS-based loT interaction capability.

The SDK 139 is configured to enable third parties (e.g., loT device suppliers, IOT integration operators, or the like,) to interact with the IMS core network 133 to support or utilize the IMS-based loT interaction capability. The SDK 139 may be configured to enable loT device suppliers to provide loT device communication formats for loT devices 120, thereby enabling the NLP / IVA 135 to translate between various loT device communication formats of various loT devices 120. The SDK 139 may be configured to enable loT integration operators to access loT data of loT devices 120. The SDK 139 may be configured to enable third parties to build loT interface translations specific to proprietary loT devices (e.g., using APIs), to interface to NLP / IVA 135 to interpret and translate commands and queries between user and loT device, or the like, as well as various combinations thereof. The SDK 139 may be configured to provide various other functions in order to support the IMS-based loT interaction capability.

The IMS network 130 is configured to support various capabilities which may be leveraged to support the IMS-based loT interaction capability of the IMS network 130. These capabilities, as discussed above and also further below, may include control signaling capabilities, security capabilities, media session capabilities, quality-of-experience (QoE) capabilities, presence capabilities, or the like, as well as various combinations thereof.

The IMS network 130 is configured to support control signaling capabilities which may be leveraged to provide the IMS-based loT interaction capability. The control signaling capabilities may be used for establishment, monitoring, and termination of IMS control sessions between the subscriber device 1 10 and the NLP / IVA 135. The control signaling capabilities may be used for establishment and termination of media sessions between the subscriber device 1 10 and the NLP / IVA 135 (primarily referred to herein as IMS-established media sessions). The control signaling capabilities may be based on various IMS-based elements (e.g., CSCFs, HSSs, or the like), various IMS signaling protocols (e.g., SIP or the like), or the like, as well as various combinations thereof. The IMS network 130 may be configured to support various other control plane signaling capabilities which may be leveraged to provide the IMS-based loT interaction capability.

The IMS network 130 is configured to support security capabilities which may be leveraged to provide the IMS-based loT interaction capability. The security capabilities may provide security for interaction by the subscriber 101 with the loT devices 120 using the IMS-based loT interaction capability. The IMS network 130 has direct IMS-based communication with the subscriber device 1 10 and the loT devices 120 such that it may perform access control and authentication in a direct manner without intermediaries. The IMS network 130 has user identity profiles and addressing that determine the levels of authentication that are to be used for registration and session establishment for subscribers such as the subscriber 101 . The IMS network 130 may be configured to support various other security capabilities for securing the interactions by the subscriber 101 with the loT devices 120 using the IMS-based loT interaction capability. The IMS network 130 may be configured to support various other security capabilities which may be leveraged to provide the IMS-based loT interaction capability.

The IMS network 130 is configured to support media session

capabilities which may be leveraged to provide the IMS-based loT interaction capability. The media session capabilities may be used to provide IMS- established media sessions for interaction by the subscriber 101 with the loT devices 120 using the IMS-based loT interaction capability. The media session capabilities may support on-demand establishment of various types of media sessions (e.g., data, voice, video, or the like, as well as various combinations thereof) between the NLP / IVA 135 and the subscriber device 1 10. The IMS-established media sessions may be used to support

exchanges of loT device communications, formatted in the subscriber-based communication format (e.g., voice, text, or the like), between the subscriber device 1 10 and the NLP / IVA 135. The media session capabilities supported by the IMS network 130 may be based on various IMS-based elements (e.g., MRFs, MGFs, or the like), various media communication protocols (e.g., IP, UDP, RTP, or the like, as well as various combinations thereof), or the like, as well as various combinations thereof. The IMS network 130 may be

configured to support various other media capabilities for providing media sessions for interaction by the subscriber 101 with the loT devices 120 using the IMS-based loT interaction capability. The IMS network 130 may be configured to support various other media session capabilities which may be leveraged to provide the IMS-based loT interaction capability.

The IMS network 130 is configured to support QoE capabilities which may be leveraged to provide the IMS-based loT interaction capability. The IMS network 130 is configured to support QoE capabilities which may be leveraged to provide improved QoE for the subscriber 101 during interaction by the subscriber 101 with the loT devices 120 using the IMS-based loT interaction capability. For example, IMS control software may operate to control or influence the network routing paths that are followed by media sessions of the subscriber 101 at the user plane level, provide quality-of- service (QoS) directives when setting up bearers for media sessions, or the like, as well as various combinations thereof. The IMS network 130 may be configured to support various other QoE capabilities for providing media sessions for interaction by the subscriber 101 with the loT devices 120 using the IMS-based loT interaction capability. The IMS network 130 may be configured to support various other QoE capabilities which may be leveraged to provide the IMS-based loT interaction capability.

The IMS network 130 is configured to support presence capabilities which may be leveraged to provide the IMS-based loT interaction capability. The IMS network 130 is configured to support presence capabilities which may be leveraged to provide presence-based functions for the subscriber 101 during interaction by the subscriber 101 with the loT devices 120 using the IMS-based loT interaction capability. For example, IMS may provide presence status which may be used to notify the subscriber 101 of changes in the operational status of loT devices 120. The IMS network 130 may be configured to support various other presence capabilities which may be leveraged to provide the IMS-based loT interaction capability.

The IMS network 130 may be configured to support various other capabilities which may be leveraged to support interaction by the subscriber 101 with the loT devices 120 using the IMS-based loT interaction capability.

The IMS network 130 may be configured to provide various other functions to support the IMS-based loT interaction capability.

It will be appreciated that the operation of the subscriber device 1 10, loT devices 120, and IMS network 130 in supporting the IMS-based loT interaction capability may be further understood by considering a process by which, via capabilities of the IMS network 130, the subscriber 101 may use the subscriber device 1 10 to issue an loT device instruction to the loT device 120 and may receive an associated loT device response from the loT device 120 after execution of the loT device instruction by the loT device 120, as presented with respect to FIGs. 2A and 2B. It will be appreciated that, although omitted from FIG. 1 for purposes of clarity, communication system 100 may include various other communication networks which may interact with IMS networks, including various types of access networks (e.g., Third Generation (3G) wireless networks, Fourth Generation (4G) wireless networks, Fifth Generation (5G) wireless networks, Ethernet networks, or the like, as well as various combinations thereof), various types of underlying transport networks (e.g., cellular core networks, IP-based transport networks, or the like), or the like, as well as various combinations thereof.

FIGs. 2A and 2B depict an example process, illustrated within the context of the communication system of FIG. 1 , by which the subscriber may use the subscriber device to issue an loT device command to an loT device and may receive an associated loT device response from the loT device after execution of the loT device instruction by the loT device.

In FIGs. 2A and 2B, an IMS-established media session is active between the subscriber device 1 10 and the NLP / IVA 135 for transporting communications between the subscriber device 1 10 and the NLP / IVA 135.

FIG. 2A depicts a portion of example process 200, within the context of the communication system 100 of FIG. 1 , by which the subscriber 101 may use the subscriber device 1 10 to issue an loT device command to an loT device 120 via the IMS network 130.

The subscriber 101 creates an loT device instruction intended for an loT device 120 (e.g., the loT device 120-1 ). The subscriber 101 creates the loT device instruction via the subscriber device 1 10. The loT device instruction is created using a subscriber-based communication format. The subscriber-based communication format may be a natural language communication format (e.g., speech, text, or the like). For example, the loT device instruction may be created using speech of the subscriber 101 (e.g., via a microphone of the subscriber device 1 10) or text entered by the subscriber 101 (e.g., via a user interface of the subscriber device 1 10). The loT device instruction may be any suitable type of instruction which may be sent to the loT device 120-1 (which may depend on the loT device type of the loT device 120-1 ), such as a query instruction by which the subscriber 101 requests that the loT device 120-1 provide status data (e.g., a temperature reading of a home thermostat at the home of the subscriber 101 , a lock status of a front door of the home of the subscriber 101 , an indication as to whether the lights at the home of the subscriber 101 are on or off, or the like), an action instruction by which the subscriber 101 requests that the loT device 120-1 perform an action (e.g., lowering or raising the temperature of the home thermostat at the home of the subscriber 101 , locking or unlocking the front door of the home of the subscriber 101 , activating a video feed from a home security camera at the home of the subscriber 101 , or the like), or the like, as well as various combinations thereof. In this example, assume that the loT device 120-1 is a home security system of the subscriber 101 and that the loT device instruction provided by the subscriber 101 in the subscriber-based communication format is a voice-based loT device instruction in which the subscriber 101 speaks the phrase "please lock the front door of my house".

The subscriber device 1 10 captures the loT device instruction of the subscriber 101 that is intended for the loT device 120-1 and sends the loT device instruction of the subscriber 101 that is intended for the loT device 120-1 toward the loT device 120-1 via the IMS-established media session of the IMS network 130. The subscriber device 1 10 sends the loT device instruction of the subscriber 101 that is intended for the loT device 120-1 toward the loT device 120-1 via the IMS network 130 by sending the loT device instruction to the IMS access point 132 of the IMS access network 131 . The loT device instruction may be sent using a message, which may be referred to as an loT device instruction message 201 . The loT device instruction message 201 is sent as a media message via the IMS-established media session. In this example, it is assumed that the IMS-established media session is a voice session and that the voice-based loT device instruction of the subscriber 101 is encoded in IP packets, which may be encapsulated as UDP/IP packets, as RTP/IP packets, or the like.

The IMS network 130 transports the loT device instruction message 201 to the NLP / IVA 135 via the IMS-established media session between the subscriber device 1 10 and the NLP / IVA 135. This may traverse the IMS access point 132 and certain IMS network elements 134 of the IMS core network 133. It will be appreciated that the loT device instruction message 201 may be transported via the IMS-established media session as out-of- band voice packets being forwarded inside of the IMS elements (namely, the IMS access point 132 and certain IMS network elements 134 of the IMS core network 133).

The NLP / IVA 135 receives the loT device instruction message 201 , including the loT device instruction of the subscriber 101 , from the subscriber device 1 10 via the IMS-established media session. The NLP / IVA 135 identifies the loT device instruction within the loT device instruction message 201 (e.g., based on identification of delimiters or other mechanisms) and extracts the loT device instruction from the loT device instruction message 201 (e.g., by decapsulating the IP packets from the UDP/IP or RTP/IP packets and decoding the loT device instruction from the IP packets). The NLP / IVA 135 stores the loT device instruction for further processing (e.g., storing a recording of the voice content in the loT device instruction for processing at the NLP / IVA 135). The NLP / IVA 135 identifies the subscriber 101 from which the loT device instruction is received (e.g., using the loT device interaction database 136, based on an identifier or address of the subscriber device 1 10 that is included in the loT device instruction message 201 ), determines the natural language communication format of the subscriber 101 from which the loT device instruction is received (e.g., using the loT device interaction database 136, based on identification of the subscriber 101 ), identifies the loT device 120-1 for which the loT device instruction of the subscriber 101 is intended (e.g., using the loT device interaction database 136, based on an identifier or address of the loT device 120-1 that is included in the loT device instruction message 201 ), determines the loT device communication format of the loT device 120-1 for which the loT device instruction of the subscriber 101 is intended (e.g., using the loT device interaction database 136, based on the identification of the loT device 120-1 for which the loT device instruction of the subscriber 101 is intended), translates the loT device instruction of the subscriber 101 from the natural language communication format of the subscriber 101 to the loT device communication format of the loT device 120-1 for which the loT device instruction of the subscriber 101 is intended to provide thereby a machine- based loT device instruction for the loT device 120-1 , and sends the machine- based loT device instruction for the loT device 120-1 toward the loT device 120-1 . The machine-based loT device instruction may be sent using a message, which may be referred to as an loT device instruction message 202. The loT device instruction message 202 may be sent as a REST message or other suitable type of message.

The NLP / IVA 135 translates the loT device instruction of the subscriber 101 from the natural language communication format of the subscriber 101 to the loT device communication format of the loT device 120- 1 for which the loT device instruction of the subscriber 101 is intended, to provide thereby the machine-based loT device instruction for the loT device 120-1 , using NLP and IVA capabilities of the NLP / IVA 135. This translation may include (1 ) the NLP of NLP / IVA 135 using natural language processing functions to understand the meaning of the loT device instruction of the subscriber 101 that is in the natural language communication format of the subscriber 101 and (2) the IVA of the NLP / IVA 135 using intelligent virtual assistant capabilities to convert the loT device instruction of the subscriber 101 from the natural language communication format of the subscriber 101 to the loT device communication format of the loT device 120-1 based on the understanding of the meaning of loT device instruction of the subscriber 101 that is in the natural language communication format of the subscriber 101 . In this example, the instruction "please lock the front door of my house" spoken by the subscriber 101 is processed using NLP functions of NLP / IVA 135 in order to understand that subscriber 101 is instructing the home security system to lock the front door at the home location of the subscriber 101 . In this example, the understanding that subscriber 101 is instructing the home security system to lock the front door at the home location of the subscriber 101 is processed using IVA functions of the NLP / IVA 135 to generate an instruction, using a communication format supported by the home security system, that will cause the home security system to lock the front door at the home location of the subscriber 101 . In this example, the instruction in the communication format supported by the home security system may be:

[Command_Type: action; Command_Target: front_door; Command_Action: lock].

The NLP / IVA 135 sends the loT device instruction message 202 toward by the loT device 120-1 by sending the loT device instruction message 202 to the M2M l/F 138.

The M2M l/F 138 receives the loT device instruction message 202 from the NLP / IVA 135 and sends the loT device instruction message 202 toward the loT device 120-1 . The M2M l/F 138, although omitted from FIG. 2A for purposes of clarity, may perform additional processing of the loT device instruction message 202 before sending the loT device instruction message 202 toward the loT device 120-1 (e.g., using JSON, REST, or the like).

The loT device 120-1 receives the loT device instruction message 202 from the M2M l/F 138. The loT device 120-1 extracts the machine-based loT device instruction from the loT device instruction message 202. The loT device 120-1 processes the machine-based loT device instruction. In this example, the processing of the machine-based loT device instruction causes the home security system to lock the front door at the home of the subscriber.

It will be appreciated that the loT device 120-1 , after processing the machine-based loT device instruction, may initiate one or more additional actions, such as responding to the subscriber 101 to indicate that the request of the subscriber has been completed (this portion of the example process 200 is presented with respect to FIG. 2B, which is discussed below).

FIG. 2B depicts a portion of example process 200, within the context of the communication system 100 of FIG. 1 , by which the subscriber 101 may use the subscriber device 1 10 to receive an associated loT device response from the loT device 120 after execution of the loT device instruction by the loT device 120-1 (e.g., after execution of the portion of example process 200 presented in FIG. 2A).

It will be appreciated that the message flow and communication processing along the path from the loT device 120-1 to the subscriber device 1 10 (as presented in FIG. 2B) is essentially the reverse of the message flow and communication processing along the path from the subscriber device 1 10 to the loT device 120-1 (as presented in FIG. 2A).

The loT device 120-1 creates an loT device response intended for subscriber 101 of subscriber device 1 10. The loT device response is created using an loT device communication format of loT device 120-1 . The loT device 120-1 sends the loT device response toward the subscriber device 1 10 using a message, which may be referred to as an loT device response message 203. The loT device response message 203 may be a REST message or other suitable type of message. The loT device 120-1 sends the loT device response message 203 toward the subscriber device 1 10 of the subscriber 101 . In this example, the loT device response in the

communication format supported by the home security system may be:

[Command_Type: action; Command _Target: front_door; Command _Result: success].

The loT device 120-1 sends the loT device response message 203 toward by the subscriber device 1 10 by sending the loT device response message 203 to the M2M l/F 138. The M2M l/F 138 receives the loT device response message 203 from the NLP / IVA 135 and sends the loT device instruction message 202 toward the NLP / IVA 135. The M2M l/F 138, although omitted from FIG. 2B for purposes of clarity, may perform additional processing of the loT device response message 203 before sending the loT device response message 203 toward the loT device 120-1 (e.g., using JSON, REST, or the like).

The NLP / IVA 135 receives the loT device response message 203, including the loT device response, from the M2M l/F 138. The NLP / IVA 135 identifies the loT device response within the loT device response message 203 and extracts the loT device response from the loT device response message 203. The NLP / IVA 135 stores the loT device message for further processing. The NLP / IVA 135 identifies the loT device 120-1 from which the loT device response is received (e.g., using the loT device interaction database 136, based on an identifier or address of the loT device 120-1 that is included in the loT device response message 203), determines the loT device communication format of the loT device 120-1 from which the loT device response is received (e.g., using the loT device interaction database 136, based on identification of the loT device 120-1 ), identifies the subscriber device 1 10 of the subscriber 101 for which the loT device response of the loT device 120-1 is intended (e.g., using the loT device interaction database 136, based on an identifier or address of the subscriber device 1 10 that is included in the loT device response message 203), identifies the subscriber 101 for which the loT device response of the loT device 120-1 is intended (e.g., using the loT device interaction database 136, based on an identifier or address of the subscriber device 1 10 that is included in the loT device response message 203), determines the natural language communication format of the subscriber 101 for which the loT device response of the loT device 120-1 is intended (e.g., using the loT device interaction database 136, based on the identification of the subscriber 101 for which the loT device response of the loT device 120-1 is intended), translates the loT device response of the loT device 120-1 from the loT device communication format of the loT device 120-1 to the natural language communication format of the subscriber 101 for which the loT device response of the loT device 120-1 is intended to provide thereby a subscriber-based loT device response for the subscriber 101 , and sends the subscriber-based loT device response for the subscriber 101 toward the subscriber device 1 10 of the subscriber 101 . The subscriber- based loT device response may be sent using a message, which may be referred to as an loT device response message 204. The loT device response message 204 is sent as a media message via the IMS-established media session.

The NLP / IVA 135 translates the loT device response of the loT device 120-1 from the loT device communication format of the loT device 120-1 to the natural language communication format of the subscriber 101 for which the loT device response is intended, to provide thereby the subscriber-based loT device response for the subscriber 101 , using IVA and NLP capabilities of the NLP / IVA 135. This translation may include (1 ) the IVA of the NLP / IVA 135 using intelligent virtual assistant functions to convert the loT device response of the loT device 120-1 from the loT device communication format of the loT device 120-1 to an understanding of the meaning of the loT device response that is related to the natural language communication format of the subscriber 101 and (2) the NLP of NLP / IVA 135 using natural language processing functions to convert the understanding of the meaning of the loT device response to the subscriber-based loT device response for the subscriber 101 based on the understanding of the meaning of the loT device response. In this example, the loT device response in the communication format supported by the home security system (namely, the format:

[Command_Type: action; Command _Target: front_door; Command _Result: success]) is processed using IVA functions of NLP / IVA 135 in order to understand that the home security system is indicating that the request by the subscriber to lock the front door was successful. In this example, the understanding that the home security system is indicating that the request by the subscriber to lock the front door was successful is processed using NLP functions of NLP / IVA 135 in order to generate an associated voice-based response to be sent to subscriber device 1 10 and played for the subscriber 101 . In this example, the voice-based response may be speech stating "the front door has been locked" so that the subscriber 101 knows that the instruction to lock the front door was successfully completed by the home security system.

The NLP / IVA 135 sends the loT device response message 204, including the subscriber-based loT device response, toward the subscriber device 1 10 via the IMS network 130. The NLP / IVA 135 sends the loT device response message 204 toward the subscriber device 1 10 via the IMS network 130 by sending the loT device response message 204 toward the IMS network elements 134 via the IMS-established media session between the NLP / IVA 135 and the subscriber device 1 10. The loT device response message 204 is sent as a media message via the IMS-established media session. In this example, as previously noted, it is assumed that the IMS- established media session is a voice session and that the subscriber-based loT device response is a voice-based loT device response, such that the subscriber-based loT device response may be encoded in IP packets which may be encapsulated as UDP/IP packets, as RTP/IP packets, or the like.

The IMS network 130 transports the loT device response message 204 to the subscriber device 1 10 via the IMS-established media session between the NLP / IVA 135 and the subscriber device 1 10. This may traverse certain IMS network elements 134 of the IMS core network 133 and IMS access point 132. It will be appreciated that the loT device response message 204 may be transported via the IMS-established media session as out-of-band voice packets being forwarded inside of the IMS elements (namely, certain IMS network elements 134 of the IMS core network 133 and the IMS access point 132). The subscriber device 1 10 receives the loT device response message 204, including the subscriber-based loT device response, from the NLP / IVA 135 via the IMS-established media session established between the NLP / IVA 135 and the subscriber device 1 10. The subscriber device 1 10 identifies the subscriber-based loT device response within the loT device response message 204 (e.g., based on identification of delimiters or other mechanisms) and extracts the subscriber-based loT device response from the loT device response message 204 (e.g., by decapsulating the IP packets from the UDP/IP or RTP/IP packets and decoding the subscriber-based loT device response from the IP packets). The subscriber device 1 10 presents the subscriber-based loT device response to the subscriber 101 using one or more user interfaces of the subscriber device (e.g., playing an audio message via a speaker of the subscriber device 1 10, presenting a text message via a user interface of the subscriber device 1 10, or the like, as well as various combinations thereof). In this example, the speech "the front door has been locked" is presented at the subscriber device 1 10 (e.g., via a speaker of the subscriber device 1 10) so that the subscriber 101 knows that the instruction to lock the front door was successfully performed by the home security system.

FIGs. 3A - 3C depict an example process by which a subscriber may use the subscriber device to issue an loT device command to an loT device and may receive an associated loT device response from the loT device after execution of the loT device instruction by the loT device.

In FIGs. 3A - 3C, the process 300 is performed using functions of and communications between various elements including a user equipment (UE) 301 , an IMS-CSCF 302 (including a PCSCF 303, an SCSCF 304, and a FEE 305), a chatbot server 306, and a home gateway 307. It will be appreciated that the UE 301 may correspond to the subscriber device 1 10 of FIGs. 1 and 2, the IMS-CSF 302 may correspond to IMS network elements 134 of IMS core network 133 of FIGs. 1 and 2, the chatbot server 306 corresponds to the NLP / IVA 135 of FIGs. 1 and 2, and the home gateway 307 corresponds to one of the loT devices 120 of FIGs. 1 and 2.

In FIGs. 3A - 3C, the process 300 includes establishment of a voice session 309 between the UE 301 and the chatbot server 306 in order to support communication between the UE 301 and the chatbot server 306 (depicted in FIG. 3A), use of the voice session 309 to facilitate control of the home gateway 307 by a subscriber of the UE 301 (depicted in FIG. 3B), and termination of the voice session 309 between the UE 301 and the chatbot server 306 after the subscriber of UE 301 is finished controlling the home gateway 307.

In FIGs. 3A - 3C, for purpose of clarity, process 300 is primarily presented within the context of embodiments using specific types of technologies (e.g., using SIP as the control protocol for the IMS network in order to establish and terminate the voice session 309, using REST and JSON to support communication between the chatbot server 306 and the home gateway 307, and so forth).

FIG. 3A depicts a portion of process 300 that supports establishment of the voice session 309 between the UE 301 and the chatbot server 306. At step 310, the UE 301 initiates a call to the chatbot server 306 in order to establish the voice session 309 that may be used to send voice-based instructions to the home gateway 307. At step 31 1 , initiation of establishment of the call by the UE 301 causes the UE 301 to send a SIP INVITE message to the PCSCF 302. At step 312, the PCSCF 303 sends the SIP INVITE message to the SCSCF 304. At step 313, the SCSCF 304 sends the SIP INVITE message to the FEE 305. At step 314, the FEE 305 sends the SIP INVITE message to the chatbot server 306. At step 315, the chatbot server 306 responds to the SIP INVITE message by sending a SIP 200 OK message to the FEE 305. At step 31 6, the FEE 305 sends the SIP 200 OK message to the SCSCF 304. At step 31 7, the SCSCF 304 sends the SIP 200 OK message to the PCSCF 303. At step 318, the CSCF 303 sends the SIP 200 OK message to the UE 301 . At step 319, the UE 301 sends a SIP ACK message to the chatbot server 306. As indicated in FIG. 3A, at this point the call (namely, voice session 309) has been established between the UE 301 and the chatbot server 306 and, as a result, voice may start flowing end-to- end between the UE 301 and the chatbot server 306 (e.g., for issuing voice- based instructions from the UE 301 that are intended to control the home gateway 307 and for receiving voice-based responses at the UE 301 based on handling of the instructions of the UE 301 by the home gateway 307, as presented with respect to FIG. 3B).

FIG. 3B depicts a portion of process 300 that supports use of the voice session between the UE 301 and the chatbot server 306 to facilitate control of the home gateway 307 by a subscriber of the UE 301 . The control of the home gateway 307 by the subscriber of the UE 301 is based on an loT device instruction issued by the subscriber of the UE 301 and intended for delivery to the home gateway 307 and results in delivery of an loT device response of the home gateway 307 to the subscriber of the UE 301 that informs the subscriber of the UE 301 as to whether execution of the loT device instruction by the home gateway 307 was successful or unsuccessful. At step 320, the subscriber of UE 301 sends an loT device instruction using voice over the voice session 309 (which is configured to support end-to-end flow of voice between the UE 301 and the chatbot server 306). At step 321 , the chatbot server 306 records the voice of the subscriber that includes the loT device instruction and translates the loT device instruction from the subscriber-based communication format of the subscriber to the communication format of the home gateway 307. The chatbot server 306 may identify the voice of the subscriber that includes the loT device instruction based on detection of a delimiter. The chatbot server 306 may record the voice of the subscriber that includes the loT device instruction by saving a .wav file or other similar type of audio file based on detection of the delimiter. The chatbot server 306 translates the loT device instruction from the subscriber-based

communication format of the subscriber to the loT device communication format of the home gateway 307, based on processing of the recorded loT device instruction using NLP and IVA capabilities of the chatbot server 306, to provide thereby a machine-based loT device instruction. At step 322, the chatbot server 306 sends the machine-based loT device instruction to the FEE 305 using a SIP OPTIONS message. At step 323, the FEE 305 processes the machine-based loT device instruction to generate JSON content indicative of the machine-based loT device instruction and sends the JSON content indicative of the machine-based loT device instruction to the home gateway 307 using a REST protocol message over a REST API. At step 324, the home gateway 307 receives the REST protocol message including the JSON content indicative of the machine-based loT device instruction to the home gateway 307, processes the JSON content indicative of the machine-based loT device instruction to the home gateway 307 to determine the loT device instruction to be executed by the home gateway 307, executes the loT device instruction, and, based on successful execution of the loT device instruction, generates an loT device response indicative that execution of the loT device instruction was successful and sends the loT device response to the FEE 305 using a REST - 200 OK message. At step 325, the FEE 305 sends a SIP OPTIONS 200 OK message to the chatbot server 307 where the SIP OPTIONS 200 OK message includes the loT device response (in the loT device communication format of the home gateway 307) indicative of successful execution of the loT device instruction by the home gateway 307. At step 326, the chatbot server 306 translates the loT device response from the communication format of the home gateway 307 to the subscriber-based communication format of the subscriber. The chatbot server 306 may generate a voice-based loT device response for the subscriber in the form of a .wav file or other suitable type of audio file. At step 327, the chatbot server 306 sends the voice-based loT device response to the UE 301 over the voice session 309 (e.g., the chatbot server 306 may play the .wav file or other type of audio file over the voice session 309). At step 328, the UE 301 plays the voice-based loT device response of the home gateway 307 for the subscriber of the UE 301 . As indicated FIG. 3B, the voice session 309 between the UE 301 and the chatbot server 306 may be used again to support one or more additional instruction - response sequences which may be initiated by the subscriber of the UE 301 using the voice session 309 (e.g., using one or more additional instructions to the home gateway 307, using one or more instructions to one or more other loT devices of the subscriber of the UE 301 , or the like, as well as various combinations thereof).

FIG. 3C depicts a portion of process 300 that supports termination of the voice session 309 between the UE 301 and the chatbot server 306. At step 330, the UE 301 initiates disconnection of the call to the chatbot server 306 in order to terminate the voice session 309 that was used to send voice- based instructions to the home gateway 307. At step 331 , initiation of termination of the call by the UE 301 causes the UE 301 to send a SIP BYE message to the PCSCF 302. At step 332, the PCSCF 303 sends the SIP BYE message to the SCSCF 304. At step 333, the SCSCF 304 sends the SIP BYE message to the FEE 305. At step 334, the FEE 305 sends the SIP BYE message to the chatbot server 306. At step 335, the chatbot server 306 responds to the SIP BYE message by sending a SIP BYE 200 OK message to the FEE 305. At step 336, the FEE 305 sends the SIP BYE 200 OK message to the SCSCF 304. At step 337, the SCSCF 304 sends the SIP BYE 200 OK message to the PCSCF 303. At step 338, the CSCF 303 sends the SIP BYE 200 OK message to the UE 301 . As indicated in FIG. 3C, at this point the call (namely, voice session 309) has been terminated (and, thus, is not depicted in FIG. 3C).

It will be appreciated that, although process 300 of FIG. 3 is primarily presented within the context of specific types of technologies (e.g., use of SIP, REST, JSON, and so forth), process 300 of FIG. 3 may be implemented using various other types of technologies.

FIG. 4 depicts an embodiment of a method for use by an element of an IMS network to support an IMS-based loT interaction capability. It will be appreciated that, although method 400 is primarily presented as being performed serially, at least a portion of method 400 may be performed contemporaneously or in a different order than as presented in FIG. 4. At block 401 , method 400 begins. At block 410, a first message including a communication associated with an loT device of a subscriber is received via an IMS network. At block 420, the communication is translated, between a subscriber-supported communication format of the subscriber and an loT device communication format supported by the loT device, to provide thereby a translated communication associated with the loT device of the subscriber. At block 430, a second message including the translated communication associated with the loT device of the subscriber is sent via the IMS network. At block 499, method 400 ends.

FIG. 5 depicts an embodiment of a method for use by a subscriber device to support an IMS-based loT interaction capability. It will be

appreciated that, although method 500 is primarily presented as being performed serially, at least a portion of method 500 may be performed contemporaneously or in a different order than as presented in FIG. 5. At block 501 , method 500 begins. At block 510, a media session, between a subscriber device of a subscriber and a server of an IMS network, is supported. At block 520, transfer of a communication associated with an loT device of the subscriber is supported where the communication associated with the loT device of the subscriber is in a subscriber-supported

communication format. At block 599, method 500 ends.

FIG. 6 depicts an embodiment of a method for use by an loT device to support an IMS-based loT interaction capability. It will be appreciated that, although method 600 is primarily presented as being performed serially, at least a portion of method 600 may be performed contemporaneously or in a different order than as presented in FIG. 6. At block 601 , method 600 begins. At block 610, a communication intended for a subscriber is obtained at an loT device of the subscriber where the communication is in an loT device communication format of the loT device. At block 620, the communication intended for the subscriber is sent from the loT device toward a server of an IMS network. At block 699, method 600 ends.

It will be appreciated that, although primarily presented herein with respect to embodiments in which an IMS-established media session between a subscriber device of a subscriber and a chatbot server is used to support interaction by the subscriber with a single loT device, in at least some embodiments an IMS-established media session between a subscriber device of a subscriber and a chatbot server may be used to support interaction by the subscriber with multiple loT devices (e.g., the chatbot server supports translation between the subscriber-based communication format of the subscriber and the loT device communication formats of the multiple loT devices), which may include different types of loT devices from the same loT device provider, similar types of loT devices from different loT device providers, different types of loT devices from different loT device providers, or the like, as well as various combinations thereof. It will be appreciated that, although primarily presented herein with respect to embodiments in which a single IMS-established media session between a subscriber device of a subscriber and a chatbot server is used to support interaction by the subscriber with multiple loT devices, in at least some embodiments multiple IMS-established media sessions between a subscriber device of a subscriber and a chatbot server may be used to support interaction by the subscriber with multiple loT devices, which may include different types of loT devices from the same loT device provider, similar types of loT devices from different loT device providers, different types of loT devices from different loT device providers, or the like, as well as various combinations thereof.

It will be appreciated that various embodiments of the IMS-based loT interaction capability may provide various advantages or potential

advantages. For example, various embodiments of the IMS-based loT interaction capability may replace "over the top" loT solutions (in which the service provider is used purely as a transport medium and, thus, assurance of security, reliability quality-of-service, and public safety cannot be guaranteed). For example, various embodiments of the IMS-based loT interaction capability enable use of a single interface medium to communicate with diverse loT equipment in a manner that meets security, reliability, quality-of-service, and public safety specifications. Various embodiments of the IMS-based loT interaction capability enable subscribers to remain in continuous

communication with loT devices, able to receive notifications and issue commands at any time and any place. For example, various embodiments of the IMS-based loT interaction capability enable a human subscriber to use a natural language interface (e.g., speech, text, or the like) to interact with diverse types of remote loT equipment across one or more networking and operator domains in a manner that incorporates end-to-end security at various network layers, applications, and devices (e.g., security may include access control, authentication (e.g., subscriber and loT device authentication), confidentiality, data integrity, availability (e.g., ensuring availability of service for mission critical applications), or the like, as well as various combinations thereof), thereby preventing or at least reducing the chances of unauthorized or intercepted access of remote loT device sessions (which can potentially result in costly and even disastrous impacts to the owner). For example, various embodiments of the IMS-based loT interaction capability enable an IMS network IMS network to support user to loT device communications remotely while conforming to reliability, security, and public safety SLAs. For example, various embodiments of the IMS-based loT interaction capability enable users to communicate with their loT equipment globally, across service provider domains, and on a variety of user equipment such as, for example, smartphones, tablets, laptops, in-vehicle communication systems including mobility, or the like. It will be appreciated that various embodiments of the IMS-based loT interaction capability may provide various other advantages or potential advantages.

FIG. 7 depicts a high-level block diagram of a computer suitable for use in performing various functions described herein.

The computer 700 includes a processor 702 (e.g., a central processing unit (CPU), a processor having a set of processor cores, a processor core of a processor, or the like) and a memory 704 (e.g., a random access memory (RAM), a read only memory (ROM), or the like). The processor 702 and the memory 704 are communicatively connected.

The computer 700 also may include a cooperating element 705. The cooperating element 705 may be a hardware device. The cooperating element 705 may be a process that can be loaded into the memory 704 and executed by the processor 702 to implement functions as discussed herein (in which case, for example, the cooperating element 705 (including associated data structures) can be stored on a non-transitory computer-readable storage medium, such as a storage device or other storage element (e.g., a magnetic drive, an optical drive, or the like)).

The computer 700 also may include one or more input/output devices 706. The input/output devices 706 may include one or more of a user input device (e.g., a keyboard, a keypad, a mouse, a microphone, a camera, or the like), a user output device (e.g., a display, a speaker, or the like), one or more network communication devices or elements (e.g., an input port, an output port, a receiver, a transmitter, a transceiver, or the like), one or more storage devices (e.g., a tape drive, a floppy drive, a hard disk drive, a compact disk drive, or the like), or the like, as well as various combinations thereof.

It will be appreciated that computer 700 of FIG. 7 may represent a general architecture and functionality suitable for implementing functional elements described herein, portions of functional elements described herein, or the like, as well as various combinations thereof. For example, computer 700 may provide a general architecture and functionality that is suitable for implementing one or more of a subscriber device 1 10, an loT device 120, IMS access point 132, IMS network elements 134, NLP / IVA 135, loT device interaction database 136, M2M l/F 138, SDK 139, UE 301 , IMS-CSCF 302, PCSCF 303, SCSCF 304, FEE 305, chatbot server 306, home gateway 307, or the like.

It will be appreciated that the functions depicted and described herein may be implemented in software (e.g., via implementation of software on one or more processors, for executing on a general purpose computer (e.g., via execution by one or more processors) so as to provide a special purpose computer, and the like) and/or may be implemented in hardware (e.g., using a general purpose computer, one or more application specific integrated circuits (ASIC), and/or any other hardware equivalents).

It will be appreciated that at least some of the functions discussed herein as software methods may be implemented within hardware, for example, as circuitry that cooperates with the processor to perform various functions. Portions of the functions/elements described herein may be implemented as a computer program product wherein computer instructions, when processed by a computer, adapt the operation of the computer such that the methods and/or techniques described herein are invoked or otherwise provided. Instructions for invoking the various methods may be stored in fixed or removable media (e.g., non-transitory computer-readable media), transmitted via a data stream in a broadcast or other signal bearing medium, and/or stored within a memory within a computing device operating according to the instructions.

It will be appreciated that the term "or" as used herein refers to a nonexclusive "or" unless otherwise indicated (e.g., use of "or else" or "or in the alternative").

It will be appreciated that, although various embodiments which incorporate the teachings presented herein have been shown and described in detail herein, those skilled in the art can readily devise many other varied embodiments that still incorporate these teachings.

Claims

What is claimed is:

1 . An apparatus, comprising:

a processor and a memory communicatively connected to the processor, the processor configured to:

receive, via an Internet Protocol (IP) Multimedia Subsystem (IMS) network, a first message including a communication associated with an Internet-of-Things (loT) device of a subscriber;

translate the communication, between a subscriber-supported communication format of the subscriber and an loT device

communication format supported by the loT device, to provide thereby a translated communication associated with the loT device of the subscriber; and

send, via the IMS network, a second message including the translated communication associated with the loT device of the subscriber.

2. The apparatus of claim 1 , wherein, to translate the communication to provide the translated communication, the processor is configured to:

identify, based on the first message, at least one of the subscriber or a subscriber device of the subscriber; and

determine, based on at least one of the subscriber or the subscriber device of the subscriber, the subscriber-supported communication format of the subscriber.

3. The apparatus of claim 1 , wherein, to translate the communication to provide the translated communications, the processor is configured to:

identify, based on the first message, the loT device of the subscriber; and

determine, based on loT device of the subscriber, the loT device communication format supported by the loT device.

4. The apparatus of claim 1 , wherein, to translate the communication to provide the translated communications, the processor is configured to:

determine, based on the communication, an understanding of a meaning of the communication; and

translate the understanding of the meaning of the communication into the translated communication.

5. The apparatus of claim 1 , wherein the communication comprises an instruction of the subscriber and the translated communication comprises an loT device instruction for the loT device.

6. The apparatus of claim 1 , wherein the communication comprises an loT device response of the loT device and the translated communication comprises a response for the subscriber.

7. The apparatus of claim 1 , wherein the subscriber-supported communication format comprises a natural language communication format and the loT device communication format comprises a machine

communication format.

8. The apparatus of claim 1 , wherein the processor is configured to support a natural language processing capability and an intelligent virtual assistant capability.

9. The apparatus of claim 1 , wherein the processor is configured to run a chatbot configured to translate the communication into the translated communication.

10. The apparatus of claim 1 , wherein the processor is configured to:

receive, via the IMS network, a first IMS signaling message indicative of a request by the subscriber device to establish a media session; and

send, via the IMS network, a second IMS signaling message indicative of an acceptance of the request by the subscriber device to establish the media session.

1 1 . An apparatus, comprising:

obtain, at an Internet-of-Things (loT) device of a subscriber, a communication intended for the subscriber, wherein the communication is in an loT device communication format of the loT device; and

send, from the loT device toward a server of an Internet Protocol (IP) Multimedia Subsystem (IMS) network, the communication intended for the subscriber.

12. The apparatus of claim 1 1 , wherein the communication intended for the subscriber comprises a response for the subscriber that is generated by the loT device responsive to execution of an instruction provided to the loT device by the subscriber.

13. The apparatus of claim 1 1 , wherein the processor is configured to: receive, by the loT device, a communication of the subscriber, wherein the communication of the subscriber is formatted using the loT device communication format of the loT device; and

process the communication of the subscriber at the loT device.

14. The apparatus of claim 1 1 , wherein the loT device communication format comprises a machine communication format.

15. The apparatus of claim 1 1 , wherein the communication intended for the subscriber is sent using a Session Initiation Protocol (SIP) message or a Representation State Transfer (REST) protocol message.