# US 11,444,810 B2 · Micro-adapter architecture for cloud native gateway device > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,444,810 B2 - Document ID: US11444810B2 - Status: Granted - Kind: B2 - Application number: 17/142,432 - Filed: 2021-01-06 - Published: 2021-05-27 - Granted: 2022-09-13 - Earliest claimed: 2019-11-21 - Assignees: Verizon Patent and Licensing Inc. - Applicants: Verizon Patent and Licensing Inc. - Inventors: Rezwanul Haque - Web page: https://patentgrep.com/patent/US11444810B2 ## CPC - H04L 67/565: Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561) - G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications} - G06F 9/546: {Message passing systems or structures, e.g. queues} - H04L 12/66: Arrangements for connecting between networks having differing types of switching systems, e.g. gateways - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - H04L 69/326: in the transport layer [OSI layer 4] (H04L69/16 takes precedence) - H04L 69/329: in the application layer [OSI layer 7] - H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A method, a device, and a non-transitory storage medium are described in which a micro-adapter architecture for a device gateway service is provided. The micro-adapter architecture for a device gateway service may be included in a cloud native backend gateway. The cloud native backend gateway may include a set of adapters that are logically grouped in layers for providing device gateway services. The device gateway services may include an application layer, a device layer, and a transport layer. The device gateway services may include bounded contexts based on rules that define the application layer, the device layer, and the transport layer. The device gateway services may be microservices that are distributed within the defined layers. ## Claims ### Claim 1 A method comprising: receiving, by a transport layer of a native cloud backend gateway from an end device, a first message; generating, by the transport layer, a transport event message based on a payload of the first message; transmitting, by the transport layer to a device layer of the native cloud backend gateway, the transport event message; transforming, by the device layer, the transport event message to application event data based on a type of the end device; selecting, by the device layer, a handler service of an application layer of the native cloud backend gateway based on an application type and an operation type associated with the application event data; transmitting, by the device layer to the application layer, an application event message that includes the application event data; selecting, by the application layer, a handler of the application layer for an application event based on an application event domain pertaining to the application event data; generating, by the application layer, a second message based on the application type and the operation type associated with the application event data; and transmitting, by the application layer to an upper application of a service device, the second message. ### Claim 2 (depends on 1) The method of claim 1, wherein generating the transport event message comprises: generating, by the transport layer, transport event data based on the payload of the first message and context information associated with the end device, wherein the transport event message includes the transport event data. ### Claim 3 (depends on 1) The method of claim 1, further comprising: selecting, by the transport layer, the device layer to which to transmit the transport event message based on the type of the end device. ### Claim 4 (depends on 1) The method of claim 1, wherein the transforming comprises: performing, by the device layer, at least one of protocol message conversion, decryption, or decoding of a first payload of the transport event message. ### Claim 5 (depends on 1) The method of claim 1, wherein generating the second message comprises: determining, by the application layer, that the application event message pertains to a complex workflow; generating, by the application layer, workflow data based on an execution of one or more steps of the complex workflow; and including, by the application layer, the workflow data in the second message. ### Claim 6 (depends on 1) The method of claim 1, further comprising: querying, by the application layer, the end device for metadata pertaining to the application event data; and receiving, by the application layer from the end device, the metadata, wherein the second message includes the metadata. ### Claim 7 (depends on 1) The method of claim 1, further comprising: selecting, by the application layer, a message type for the second message based on a messaging system and the application event data. ### Claim 8 (depends on 1) The method of claim 1, wherein the upper application provides a telematics service, and the end device is a wireless telematics device. ### Claim 9 A native cloud backend gateway comprising: a processor configured to: receive, by a transport layer of the native cloud backend gateway from an end device, a first message; generate, by the transport layer, a transport event message based on a payload of the first message; transmit, by the transport layer to a device layer of the native cloud backend gateway, the transport event message; transform, by the device layer, the transport event message to application event data based on a type of the end device; select, by the device layer, a handler service of an application layer of the native cloud backend gateway based on an application type and an operation type associated with the application event data; transmit, by the device layer to the application layer, an application event message that includes the application event data; select, by the application layer, a handler of the application layer for an application event based on an application event domain pertaining to the application event data; generate, by the application layer, a second message based on the application type and the operation type associated with the application event data; and transmit, by the application layer to an upper application of a service device, the second message. ### Claim 10 (depends on 9) The native cloud backend gateway of claim 9, wherein generating the transport event message, the processor is further configured to: generate, by the transport layer, transport event data based on the payload of the first message and context information associated with the end device, wherein the transport event message includes the transport event data. ### Claim 11 (depends on 9) The native cloud backend gateway of claim 9, wherein the processor is further configured to: select, by the transport layer, the device layer to which to transmit the transport event message based on the type of the end device. ### Claim 12 (depends on 9) The native cloud backend gateway of claim 9, wherein transforming the transport event message, the processor is further configured to: perform, by the device layer, at least one of protocol message conversion, decryption, or decoding of a first payload of the transport event message. ### Claim 13 (depends on 9) The native cloud backend gateway of claim 9, wherein generating the second message, the processor is further configured to: determine, by the application layer, that the application event message pertains to a complex workflow; generate, by the application layer, workflow data based on an execution of one or more steps of the complex workflow; and include, by the application layer, the workflow data in the second message. ### Claim 14 (depends on 9) The native cloud backend gateway of claim 9, wherein the processor is further configured to: query, by the application layer, the end device for metadata pertaining to the application event data; and receive, by the application layer from the end device, the metadata, wherein the second message includes the metadata. ### Claim 15 (depends on 9) The native cloud backend gateway of claim 9, wherein the processor is further configured to: select, by the application layer, a message type for the second message based on a messaging system and the application event data. ### Claim 16 (depends on 9) The native cloud backend gateway of claim 9, wherein the upper application provides a telematics service, and the end device is a wireless telematics device. ### Claim 17 A non-transitory computer-readable storage medium storing instructions executable by a processor of a native cloud backend gateway, which when executed cause the native cloud backend gateway to: receive, by a transport layer of the native cloud backend gateway from an end device, a first message; generate, by the transport layer, a transport event message based on a payload of the first message; transmit, by the transport layer to a device layer of the native cloud backend gateway, the transport event message; transform, by the device layer, the transport event message to application event data based on a type of the end device; select, by the device layer, a handler service of an application layer of the native cloud backend gateway based on an application type and an operation type associated with the application event data; transmit, by the device layer to the application layer, an application event message that includes the application event data; select, by the application layer, a handler of the application layer for an application event based on an application event domain pertaining to the application event data; generate, by the application layer, a second message based on the application type and the operation type associated with the application event data; and transmit, by the application layer to an upper application of a service device, the second message. ### Claim 18 (depends on 17) The non-transitory computer-readable storage medium of claim 17, wherein the instructions to generate the transport event message further comprise instructions, which when executed cause the native cloud backend gateway to: generate, by the transport layer, transport event data based on the payload of the first message and context information associated with the end device, wherein the transport event message includes the transport event data. ### Claim 19 (depends on 17) The non-transitory computer-readable storage medium of claim 17, wherein the instructions further comprise instructions, which when executed cause the native cloud backend gateway to: query, by the application layer, the end device for metadata pertaining to the application event data; and receive, by the application layer from the end device, the metadata, wherein the second message includes the metadata. ### Claim 20 (depends on 17) The non-transitory computer-readable storage medium of claim 17, wherein the instructions to generate the second message further comprise instructions, which when executed cause the native cloud backend gateway to: determine, by the application layer, that the application event message pertains to a complex workflow; generate, by the application layer, workflow data based on an execution of one or more steps of the complex workflow; and include, by the application layer, the workflow data in the second message.