System service sharing between endpoint devices for increased endpoint device capability

The method and system allow endpoint devices to share system services across devices with different operating systems, addressing limitations in existing ecosystems by enhancing flexibility and simplifying device management.

JP2024156873AActive Publication Date: 2024-11-06GOOGLE LLC
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2024127747
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2020-08-17
Filing Date
2024-08-02
Publication Date
2024-11-06
Estimated Expiration
2041-08-17

AI Technical Summary

Technical Problem

Existing device ecosystems face challenges in adding new capabilities due to limited operating systems, communication protocols, and user data restrictions, making it cumbersome and complex to manage device capabilities.

Method used

A method and system that enable endpoint devices to share system services across devices with different operating systems, allowing for flexible integration and operation by discovering, requesting, and implementing available system services using communication protocols.

Benefits of technology

Enhances flexibility and simplifies the addition of new capabilities in device ecosystems by enabling operating system-independent service sharing, reducing complexity and enhancing device management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024156873000001_ABST
    Figure 2024156873000001_ABST
Patent Text Reader

Abstract

To provide an endpoint device system that provides a method and a system for sharing one or more system services between one or more endpoint devices.SOLUTION: A system includes a first endpoint device configured to detect one or more other endpoint devices communicatively coupled to the first endpoint device. From at least one of the detected endpoint devices, the first endpoint device requests a respective list of available system services. After determining one or more applicable system services based on the application being run, the first endpoint device requests available resolutions for the applicable system services from the detected endpoint devices. The first endpoint device then implements the functionality of the application using one or more of the applicable system services based on the available resolutions.SELECTED DRAWING: Figure 7
Need to check novelty before this filing date? Find Prior Art

Description

[Background technology]

[0001] REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application Serial No. 63 / 066,602, filed August 17, 2020, and entitled "SYSTEM FOR GAINING CAPABILITIES AT AN ENDPOINT," which is incorporated by reference in its entirety.

[0002] background In a device ecosystem, multiple devices, each with its own capabilities, are networked together to provide their own capabilities to one or more users. Traditionally, to add new capabilities to a device ecosystem, a new device is added to the network and executes the new capabilities upon request by the network. However, adding new devices to a device ecosystem can be cumbersome and restrictive because the operating systems and communication protocols supported by the device ecosystem, such as in a closed device ecosystem, are limited. In addition, frequent addition of devices to the device ecosystem makes management of the capabilities of each device in the device ecosystem more complicated.

[0003] Often, devices that are added to a device ecosystem are tied to user data that limits which device ecosystems each device can be added to. Additionally, many device ecosystems are configured to communicate using a small number of communication protocols, which also limits which devices can be added to a particular device ecosystem. Summary of the Invention

[0004] According to an example embodiment, a method includes receiving, by a first endpoint device, from a second endpoint device, a list of available system services associated with the second endpoint device. Further, the method may include receiving an available resolution for at least one available system service from the list of available system services. The method may additionally include executing, by the first endpoint device, one or more applications associated with a function. Executing the one or more applications may include transmitting data from the first endpoint device to the second endpoint device that implements the function using at least one available system service from the list of available system services based on the available resolution.

[0005] The method may also include receiving, by the first endpoint device, a plurality of available solutions from the second endpoint device based on at least one available system service from the list of available system services. The available solution may be one of the plurality of available solutions. In addition, the method may include receiving, by the first endpoint device, data from the second endpoint device representative of an interaction with the one or more applications, and modifying, by the first endpoint device, execution of the one or more applications based on the data representative of the interaction with the one or more applications.

[0006] The method may further include receiving, by the first endpoint device, from the second endpoint device, a second list of available system services associated with a third endpoint device communicatively coupled to the second endpoint device. The method may also include requesting, by the first endpoint device, from the second endpoint device a second available resolution for a system service from the second list of available system services. Executing the one or more applications may also include transmitting, by the first endpoint device, data to the third endpoint device that implements the function using the system service from the second list of available system services based on the second available resolution.

[0007] Additionally, the method may include detecting, by the first endpoint device, the second endpoint device, and receiving, by the first endpoint device, resolution service data associated with the second endpoint device from the second endpoint device. The method may further include requesting, by the first endpoint device, over a communication protocol of a plurality of communication protocols from the second endpoint device based on the resolution service data, the list of available system services associated with the second endpoint device.

[0008] In another example embodiment, a method includes detecting, by a first endpoint device, a second endpoint device including one or more system services, and receiving, by the first endpoint device, available solutions associated with the one or more system services of the second endpoint device. The method may also include executing, on the first endpoint device, one or more applications using the one or more system services of the second endpoint device based on the available solutions associated with the one or more system services.

[0009] The method may additionally include receiving resolution service data from the second endpoint device and requesting, by the first endpoint device, a list including the one or more system services over a communication protocol based on the resolution service data. The method may further include receiving, by the first endpoint device, data from the second endpoint device representative of an interaction with the one or more applications and executing the one or more applications based on the data representative of the interaction with the one or more applications. The available solution may be one of a plurality of available solutions received from the second endpoint device. Also, the second endpoint device may be detected by a first communication protocol and the available solution may be received by a second communication protocol.

[0010] Additionally, the method may include, in response to detecting the second endpoint device, requesting access by the first endpoint device to a discovery service engine of the second endpoint device. Further, the method may include, at the first endpoint device, receiving resolution service data associated with the discovery service engine of the second endpoint device and accessing the discovery service engine of the second endpoint device based on the resolution service data. The method may also include, in response to detecting the second endpoint device, requesting access by the first endpoint device to a discovery service engine of the second endpoint device based on the resolution service data. The discovery service engine may include accessing the discovery service engine of an intranet device.

[0011] Generally, with respect to the methods described herein, one or more applications may be configured to render one or more notifications. Also, executing the one or more applications may include rendering one or more notifications on a display electronically coupled to the second endpoint device. Furthermore, generally, the first endpoint device may have a first operating system and the second endpoint device may have a second operating system separate from the first operating system. The second operating system may have at least one interface, language, memory management technique, communication protocol, encryption, or network stack different from the first operating system. Generally, the second endpoint device may be in proximity to the first endpoint device. Additionally, the second endpoint device may include device ID data of a third endpoint device.

[0012] According to some example embodiments, a system may include a first endpoint device including one or more processors storing executable instructions configured to operate the one or more processors to perform the methods disclosed herein.

[0013] According to additional example embodiments, a system may include an endpoint device framework including one or more endpoint devices communicatively coupled to one or more other endpoint devices, the system configured to perform the methods disclosed herein.

[0014] BRIEF DESCRIPTION OF THE DRAWINGS The present disclosure may be better understood, and its numerous features and advantages made apparent to those skilled in the art by referencing the accompanying drawings, in which: The use of the same reference numbers in different drawings indicates similar or identical elements. [Brief description of the drawings]

[0015] [Figure 1] FIG. 2 is a block diagram illustrating an endpoint device framework for shared system services according to some embodiments. [Diagram 2] 2 is a block diagram illustrating an endpoint device configured to import and export one or more system services within the endpoint device framework of FIG. 1 according to some embodiments. [Diagram 3] FIG. 2 is a flow diagram illustrating an example bootstrapping operation of an endpoint device according to some embodiments. [Figure 4] 2 is a block diagram illustrating communicatively coupled endpoint devices configured to share one or more system services within the endpoint device framework of FIG. 1 according to some embodiments. [Diagram 5]4 is a signal flow diagram illustrating an example discovery service access request operation for an endpoint device according to some embodiments. [Figure 6] 4 is a signal flow diagram illustrating an example available system service request according to some embodiments. [Figure 7] FIG. 1 is a flow diagram illustrating a process for executing an application using shared system services according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] Detailed Description The techniques and systems described herein address providing flexibility in a device ecosystem of multiple endpoint devices by sharing system services across one or more endpoint devices. Specifically, such techniques and systems described herein enable an endpoint device to obtain capabilities of shared system services from one or more other endpoint devices. To obtain these capabilities, a first endpoint device running an application detects one or more other endpoint devices communicatively coupled to the first endpoint device. For example, the first endpoint device detects one or more other endpoint devices that are near or in close proximity to the first endpoint device. The first endpoint device requests a respective list of available system services from each of the detected endpoint devices. After determining one or more applicable system services based on the running application, the first endpoint device requests data necessary to access the applicable system services from each endpoint device. The endpoint device then realizes the functionality of the application using one or more of the applicable system services. In this manner, the first endpoint device obtains capabilities of the applicable system services shared from the other endpoint devices.

[0017] In addition, the techniques and systems described herein enable operating system independent sharing of system services between endpoint devices. That is, an endpoint device having a first operating system may share system services with one or more endpoint devices having one or more different operating systems. Such a framework allows for more flexibility in adding endpoint devices to a device ecosystem.

[0018] 1 illustrates an endpoint device framework 100 for enabling shared system services according to some embodiments. The endpoint device framework 100 includes one or more endpoint devices 102, each communicatively coupled to at least one other endpoint device, and is configured to enable sharing of system services 106 between the communicatively coupled endpoint devices. As used herein, "communicatively coupled" includes two or more devices each configured to enable transmission of data, reception of data, or both between them, e.g., by wired communication, wireless communication, network communication, bridge communication, etc., to name a few. As used herein, an "endpoint device" includes hardware and software resources configured to execute one or more applications 104, and further includes, for example, one or more desktop computers, servers, virtual servers, notebook computers, tablet computers, virtual reality systems, augmented reality systems, computing-enabled mobile phones (i.e., "smartphones"), computing-enabled wearable devices (i.e., "wearables"), communications hubs, vehicle integrated displays, computing-enabled displays (i.e., "smart displays"), computing-enabled televisions (i.e., "smart TVs"), or any combination thereof.

[0019] In some embodiments, each application 104 is associated with one or more functions that are implemented by the endpoint device 102 when executing the application 104. For example, each application 104 includes logic for implementing one or more functions. Such functions may include, for example, streaming video data, streaming audio data, controlling a data stream, controlling playback, generating notifications, displaying notifications, or any combination thereof, to name a few. To achieve this, each endpoint device 102 includes one or more system services 106 configured to implement at least a portion of the functionality of the applications 104 when they execute. As used herein, a "system service" includes the hardware and software of the endpoint device 102 configured to implement at least a portion of the functionality of the applications 104. For example, the system services 106 include hardware and software configured to render audio data (e.g., one or more audio encoders, audio decoders, speakers), render video data (e.g., one or more video encoders, one or more video decoders, displays), receive data, transmit data, receive input, receive interaction (e.g., interactive touch screen, mouse, keyboard, game controller), generate queries, or any combination thereof, to name a few. As another example, the system services 106 include one or more application interfaces (APIs) configured to implement one or more functions of the applications 104 executing on the endpoint device 102. As shown in the drawings, the system services 106 may include one or more application interfaces (APIs) configured to implement one or more functions of the applications 104 executing on the endpoint device 102. In the embodiment shown, three system services 106-1, 106-2, and 106-3 are presented to implement functionality associated with two applications 104-1 and 104-2, although in other embodiments, any number of system services may implement functionality for any number of applications.

[0020] According to some embodiments, each endpoint device 102 is configured to export one or more system services 106 to one or more other endpoint devices to enable access to and control (i.e., exposure) of the exported system services 106 to one or more other endpoint devices. Each system service 106 of an endpoint device 102 may be configured to support one or more communication protocols, wired communication connections, and wireless communication connections, such as Bluetooth, Bluetooth Low Energy (BLE), Multicast Domain Name System (mDNS), QR Code, ultra-wideband, ultrasonic, generic web services API, USB, radio frequency identification (RFID), Near-field Communication (NFC), Short Message Service (SMS), WLAN, and the like. The first endpoint device is configured to export one or more system services 106 to one or more other endpoint devices using a network connection such as i-Fi, the Internet, a local area network (LAN), Ethernet, or any combination thereof. In some embodiments, when a first endpoint device (e.g., endpoint device 102-1) exports a system service 106 to a second endpoint device (e.g., endpoint device 102-2), the second endpoint device can access and control the system service 106, for example, to implement at least a portion of one or more functions associated with an application 104 executing on the second endpoint device. That is, the second endpoint device uses the system service 106 of the first endpoint device to implement the functions of the application 104 executing on the second endpoint device. For example, in the illustrated embodiment, the system service 106-3 can be exported to endpoint devices 102-2, 102-3, or 102-4 and used to implement at least a portion of the functions of the respective applications executing on endpoint devices 102-2, 102-3, or 102-4. By exporting one or more system services 106 to one or more other endpoint devices, the one or more other endpoint devices effectively acquire new capabilities associated with the hardware and software of the exported system services 106.

[0021] In some embodiments, each endpoint device 102 includes one or more proxy system services 108. The one or more proxy system services 108 include software and hardware configured to access and control one or more exported system services 106 from one or more other endpoint devices. According to some embodiments, the proxy system service 108 is configured to realize at least a portion of one or more functions of an application 104 (also referred to herein as a "supported application") using one or more exposed system services from another endpoint device. In some embodiments, the proxy system service 108 realizes the functions of the supported application by sending data to the exposed system services 106 that realize the functions associated with the supported application. For example, the proxy system service 108 sends data representing the logic of the application 104 to realize the functions associated with the application 104 using the exported system services 106 from the other endpoint device. In the illustrated embodiment, three proxy system services 108-1, 108-2, and 108-3 are demonstrated to realize the functionality of one supported application 104-3 using three endpoint devices 102-2, 102-3, and 102-4, but in other embodiments, any number of proxy system services may be used to realize the functionality of any number of applications running on any number of endpoint devices. In this manner, at least a portion of an application running on a first endpoint device may be realized on a second endpoint device. For example, an application 104 running on a first endpoint device 102-1 may have functionality including generating and displaying notifications. Here, at least a portion of the application 104 running on the first endpoint device 102-1, e.g., displaying notifications, may be realized on a second endpoint device 102-2.

[0022] According to some embodiments, the proxy system service 108 is configured to receive input data from one or more exported system services 106 from other endpoint devices. As used herein, "input data" includes data representing interactions (e.g., gestures on a touch screen, taps on a touch screen, text input, mouse clicks, button presses, to name a few) on an input device, such as an interactive touch screen, a mouse, a keyboard, or a game controller, to name a few. In some embodiments, each proxy system service 108 is configured to modify the execution of a supported application based on the input data. For example, the proxy system service 108 provides the input data as input to the supported application. As another example, the proxy system service 108 starts or stops the execution of the supported application based on the input data.

[0023] In some embodiments, each endpoint device 102 of the endpoint device framework 100 includes one or more operating systems, each having, for example, one or more interfaces, languages, memory management techniques, communication protocols, encryption, network stacks, or any combination thereof, to name a few. According to some embodiments, the endpoint device framework 100 is configured to be operating system independent. As used herein, "operating system independent" includes the endpoint device framework 100 configured to support at least one endpoint device 102 having a first operating system and at least one other endpoint device having a second, separate operating system. That is, within the endpoint device framework 100, a first endpoint device 102 with a first operating system is configured to support at least one other endpoint device 102 having a second, separate operating system. The device 102 can export or import one or more system services 106 from a first operating system to a second endpoint device having a second, different operating system including one or more different interfaces, memory management techniques, communication protocols, network stacks, or any combination thereof.

[0024] For example, a first endpoint device (e.g., endpoint device 102-1) includes a first operating system having a first interface and a first memory management system. Within the endpoint device framework 100, the first endpoint device can import one or more system services from a second endpoint device having a second, separate operating system with a second, separate interface and a second, separate memory management system. As described below with reference to FIG. 2, the first endpoint device can request access to one or more system services 106 on the second endpoint device. In response, the second endpoint device transmits data indicating how to access the system service 106 according to the operating system executed on the second endpoint device. In other words, the second endpoint device transmits data indicating how to access the system service 106 according to one or more interfaces, memory management techniques, communication protocols, network stacks, or any combination thereof, of the second operating system. From this data, the first endpoint device can then access the system services of the second endpoint device.

[0025] 2, an exemplary endpoint device 202 configured to share system services is presented. In some embodiments, the endpoint device 202 implements aspects of the endpoint device framework 100 as described in FIG. 1. For example, the endpoint device 202 may be similar or the same as the endpoint device 102 described in FIG. 1. The endpoint device 202 includes hardware and software for exporting and importing one or more system services to one or more other endpoint devices. According to some embodiments, the endpoint device 202 is part of an electronic device that supports exporting and importing system services to one or more other endpoint devices including, for example, a desktop computer, a notebook computer, a tablet computer, a virtual reality system, an augmented reality system, a smartphone, a communication hub, a smart display, or a smart TV, to name a few. In some embodiments, the endpoint device 202 includes one or more peripherals 212, for example, a display, an input device, a speaker, lighting (e.g., light-emitting diodes (LEDs), organic light-emitting diodes (OLEDs), and the like. In the illustrated embodiment, the endpoint device 202 is communicatively coupled to three peripherals 212-1, 212-2, and 212-3, although in other embodiments, the endpoint device 202 may be communicatively coupled to any number of peripherals.

[0026] In some embodiments, the endpoint device 202 includes a processing element 230 communicatively coupled to a memory 210. The memory 210 includes electronic storage, such as a solid-state drive, a hard disk drive, a random access memory (RAM), a read-only memory (ROM), an electronically erasable programmable ROM (EEPROM), an optical storage device, or any combination thereof. The memory 210 may include one or more It includes instructions and data related to the execution of applications and the export and import of system services from one or more endpoint devices, such as device ID data 222, list of system services 224, and resolved services data 226.

[0027] According to some embodiments, the processing element 230 may be one or more control processing units (CPUs), microprocessors, field programmable gates, FPGA (field-programmable gate array), graphics processing unit (graphics processing unit: GPU), application-specific integrated circuit ASIC, ASICs, or any combination thereof, The endpoint device 202 is configured to perform import and export of one or more system services to one or more other endpoint devices. In some embodiments, the endpoint device 202 includes a list 224 of system services stored in the memory 210. The list 224 of system services includes data indicating system services 106 available to the endpoint device 202. The system services available to the endpoint device 202 include system services 106 included in the endpoint device 202 and system services exported to the endpoint device 202 from one or more other endpoint devices (i.e., system services of the other endpoint devices controlled by one or more proxy system services 108). According to some embodiments, the list 224 of system services may further include system services available to one or more other endpoint devices communicatively coupled to the endpoint device 202.

[0028] According to some embodiments, the memory 210 includes resolution service data 226 including available resolutions associated with one or more components of the endpoint device 202 (e.g., the bootstrap engine 214, the identification engine 216, the discovery services engine 220, the peripherals 212), one or more system services in the list of system services 224, or both. As used herein, an "available resolution" includes data indicating how one or more components of the endpoint device 202 or the system services 106 of the endpoint device 202 may be accessed using one or more communication protocols. For example, the available resolutions may include data indicating how one or more protocols (e.g., Internet Protocol, port, Bluetooth®, Universal Port, to name a few) may be accessed using one or more protocols (e.g., Internet Protocol, port, Universal Port ... Generic Attribute Profile (GATT) The resolution service data 226 includes data indicating one or more addressable locations for the system services 106. In some embodiments, the available resolutions include multiple addressable locations where more than one communication protocol is available. Thus, the resolution service data 226 includes data indicating how to access the system services 106 using multiple communication protocols. According to some embodiments, the resolution service data 226 includes available resolutions for one or more of the system services 106 available to the endpoint device 202, including system services exported to the endpoint device 202 from one or more other endpoint devices. In some embodiments, the resolution service data 226 further includes available resolutions for one or more system services available to one or more other endpoint devices communicatively coupled to the endpoint device 202.

[0029] The processing element 230 includes a bootstrapping engine 214 configured to perform a bootstrapping operation to discover one or more other endpoint devices for the endpoint device 202 and to initiate contact with the one or more other endpoint devices. According to some embodiments, the bootstrapping operation of the bootstrap engine 214 may include detecting one or more endpoint devices in proximity to the endpoint device 202. The bootstrapping engine 214 includes a detection stage configured to detect the presence of a point device. As used herein, an endpoint device is in proximity to the endpoint device 202 if it is discoverable by the bootstrapping engine 214 using one or more protocols, such as BLE, mDNS, or NFC, to name a few. That is, a proximate endpoint device is within a distance from the endpoint device 202 that allows it to be detected by the bootstrapping engine 214. In some embodiments, the detection stage of the bootstrapping engine 214 is configured to detect the presence of one or more endpoint devices communicatively coupled or associated with the endpoint device 202, for example, by one or more accounts (e.g., one or more endpoint devices that share a user account with the endpoint device 202), a server (e.g., one or more endpoint devices registered with a server), to name a few. According to some embodiments, the bootstrapping operation of the bootstrapping engine 214 further includes an initialization stage configured to query and return device identification data (device ID data) from one or more detected endpoint devices.

[0030] In some embodiments, the memory 210 includes device ID data 222 that includes a device ID for the endpoint device 202 that indicates the identity, ownership, access, certification, or any combination thereof, of the endpoint device 202. According to some embodiments, the device ID is an Internet protocol (IP) The device ID includes an addressable label for the endpoint device 202, similar to a device ID (P) address. According to some embodiments, the endpoint devices are configured to communicate with other endpoint devices (e.g., endpoint device 202) by providing each other with their device IDs and addressable labels. In some embodiments, the device ID includes a public half of an asymmetric key pair. According to some embodiments, the endpoint device (e.g., endpoint device 202) is configured to use the key pair for digital signatures. In this manner, an endpoint device receiving a digital signature from a second endpoint device can verify the signature of the second endpoint device. In some embodiments, the device ID includes a certification token that includes one or more certifications of the endpoint device. The certification includes data representative of one or more capabilities, configurations, or integrity of the endpoint device. For example, the certification may include data indicating that the system software of the endpoint device has not been modified since its manufacture. In one exemplary embodiment, the device ID is 32 bytes in length, although a different number of bytes may be used in other embodiments. According to some embodiments, the device ID further includes communication information, such as address information for one or more system services, engines, modules, or processors of the endpoint device, and one or more communication protocols supported by the endpoint device or its one or more system services, engines, modules, or processors. As an example, the device ID for the endpoint device 202 may include communication information indicating how to access the resolution services engine 218 (e.g., one or more addressable locations of the resolution services engine 218) and the communication protocols supported by the resolution services engine 218.In some embodiments, the device ID data includes device IDs for one or more other endpoint devices, e.g., device IDs for endpoint devices to which the endpoint device 202 is communicatively coupled, was previously communicatively coupled, or is both communicatively coupled and previously communicatively coupled.

[0031] According to some embodiments, the processing element 230 generates, stores, modifies, maintains, and authenticates device IDs, e.g., device IDs stored in the device ID data 222. The identification engine 216 includes an identification engine configured to authenticate the device IDs received from one or more endpoint devices. In some embodiments, the identification engine 216 is configured to authenticate the device IDs received from one or more endpoint devices. For example, the identification engine 216 is configured to verify the ownership of the device ID, verify the address of the device ID, verify the certification of the device ID (e.g., that the endpoint device has not been tampered with), verify the identity of the device ID, determine a timestamp for the device ID, or any combination thereof. As an example, the identification engine 216 verifies the identity of the received device ID by comparing the identity indicated in the received device ID with an identity obtained from the certification service. As another example, the device ID may include a public half of an asymmetric key pair used in digital signatures, which allows the identification engine 216 to verify a signature received from an endpoint device associated with the device ID. The identification engine 216 is configured to store the one or more received device IDs in the device ID data 222. According to some embodiments, the identification engine 216 stores only authenticated device IDs in the device ID data 222.

[0032] In some embodiments, the processing element 230 includes a resolution service engine 218 that includes software and hardware configured to process incoming discovery access resolution requests and resolution queries received from one or more other endpoint devices. As used herein, a "discovery access resolution request" includes a request received from one or more other endpoint devices for access to the discovery service engine 220 of the endpoint device 202. Based on the discovery access resolution request, the resolution engine 218 is configured to transmit one or more available resolutions associated with the discovery service engine 220 to the endpoint device that sent the discovery access resolution request. That is, the resolution engine 218 is configured to transmit data to the requesting endpoint device indicating how to access the discovery service engine 220 using one or more communication protocols. As used herein, a "resolution query" includes a request for access to one or more identified system services included in the list of system services 224. Based on the received resolution query, the resolution engine 218 is configured to transmit one or more available resolutions associated with the identified system services to the endpoint device that sent the resolution query. In other words, the resolution engine 218 is configured to transmit data to the requesting endpoint device indicating how to access the identified system service (e.g., one or more addressable locations) using one or more communication protocols.

[0033] According to some embodiments, the processing element 230 includes a discovery service engine 220 that includes hardware and software configured to process incoming system service queries received from one or more other endpoint devices. As used herein, a "system service query" includes a request for an identification or list of one or more system services available to the endpoint device 202. Based on the received system service query, the discovery service engine 220 accesses the list of system services 224 to determine the system services available to the endpoint device 202. According to some embodiments, the discovery service engine 220 is configured to transmit data to the requesting endpoint device that includes the list of available system services. In some embodiments, the discovery service engine 220 is further configured to transmit one or more additional lists of available system services to the requesting endpoint device. Each of the additional lists of available system services indicates system services available to a respective endpoint device communicatively coupled to the endpoint device 202. In this manner, the endpoint device 202 is configured to transmit data to the requesting endpoint device that includes the list of available system services. It acts as an intermediary or bridge between the device and the point device.

[0034] 3 illustrates an example bootstrapping operation 300 performed by a bootstrapping engine similar to or the same as bootstrapping engine 214 of a first endpoint device similar to or the same as endpoint device 202. In step 305, the bootstrap engine initiates a discovery phase. In some embodiments, initiating the discovery phase includes the bootstrap engine detecting one or more communication protocols, such as Bluetooth, BLE, Multicast, to name a few. The bootstrapping process includes initiating (e.g., activating) a local domain mDNS, QR Code, ultra-wideband, RFID, NFC, or any combination thereof. In step 310, the bootstrapping engine detects one or more proximate endpoint devices according to one or more of the initiated protocols. In some embodiments, one or more of the initiated protocols include a first device operating as a scanning device (e.g., the first endpoint device) and a second device operating as an advertising device (e.g., one or more other endpoint devices). As used herein, an "advertising device" is configured to announce its presence based on one or more of the initiated protocols. For example, the advertising device is configured to transmit a signal or beacon indicating the presence of the advertising device according to one or more of the initiated protocols. As used herein, a "scanning device" is configured to detect the presence of one or more advertising devices, for example, by receiving a signal or beacon transmitted by the advertising device. According to some embodiments, a single device may operate simultaneously as a scanning device and an advertising device.

[0035] In step 315, after the bootstrap engine detects the presence of one or more endpoint devices, the bootstrap engine initiates an initialization phase. In the initialization phase, the bootstrap engine is configured to initiate contact with one or more detected endpoint devices using one or more communication protocols. In some embodiments, the bootstrap engine initiates contact with one or more detected endpoint devices using one or more of the initiated protocols. In step 320, once the bootstrap engine initiates contact with the detected endpoint devices, the bootstrap engine constructs a device ID query and sends the constructed device ID query to the detected endpoint devices. The device ID query includes a request for device IDs of connected endpoint devices. That is, the bootstrap engine requests identification data for each detected endpoint device. According to some embodiments, the device ID query includes the device ID of the endpoint device that initiates the bootstrapping process. In step 325, the bootstrap engine receives respective device IDs from one or more detected endpoint devices. According to some embodiments, the bootstrap engine further receives one or more device IDs from the detected endpoint devices that identify one or more respective endpoint devices coupled to the detected endpoint devices. In some embodiments, the bootstrapping engine may provide the received device ID to an identification engine similar to or the same as identification engine 216. The identification engine is configured to authenticate the device ID, for example, by verifying ownership of the device ID, verifying the address of the device ID, verifying certification of the device ID with an attestation service, verifying the identity of the device ID, determining a timestamp for the device ID (e.g., verifying that the device ID has not expired), or any combination thereof.According to some embodiments, the device IDs received from the detected endpoint devices are each matched to one or more available resolutions (i.e., the number of connected endpoints) associated with a respective discovery service engine of the connected endpoint device. The discovery service engine for each endpoint device is included in the device ID.

[0036] 4, a block diagram of communicatively coupled endpoint devices configured to share system services is shown. In some embodiments, endpoint device 402-1 (including discovery service engine 420-1, resolution service engine 418-1, and system services 406-1) and endpoint device 402-2 (including discovery service engine 420-2, resolution service engine 418-2, and system services 406-2) implement aspects of endpoint device framework 100 as described in FIG. 1. For example, endpoint devices 402-1 and 402-2 may be similar or the same as endpoint device 102 shown in FIG. 1. In the illustrated embodiment, endpoint device 402-1 is communicatively coupled to one other endpoint device 402-2, but in other embodiments, endpoint device 402-1 may be communicatively coupled to any number of other endpoint devices. According to some embodiments, the endpoint device 402-1 initiates contact with the endpoint device 402-2 using one or more communication protocols, for example, by implementing the example bootstrapping operation 300 described above with reference to FIG.

[0037] In some embodiments, each endpoint device 402 is configured to implement or execute one or more applications 404-1 and 404-2, each associated with one or more functions. Each endpoint device is configured to realize these functions using system services 406 that are within or specific to the endpoint device 402, or using one or more exported system services 406 shared from another endpoint device 402. For example, in the illustrated embodiment, endpoint device 402-1 is configured to realize one or more functions of application 404-1 using system services 406-1, 406-2, or both on endpoint device 402-2. In this manner, the capabilities of endpoint device 402-1 are increased as more system services become available to realize the application's functions. According to some embodiments, to access system services 406 on another endpoint device, one or more applications 404 running on endpoint device 402 are configured to access a discovery service engine 420 similar or the same as discovery service engine 220 of one or more other endpoint devices. In the illustrated embodiment, one application 404-1 running on the first endpoint device 402-1 accesses a discovery service engine 420-2 of one of the other endpoint devices 402, but in other embodiments, any number of applications 404 running on the first endpoint device 402-1 may access any number of discovery service engines of any number of other endpoint devices. In some embodiments, the application 404 running on the first endpoint device 402-1 accesses the discovery service engine 420-2 running on the second endpoint device 402-2 based on a device ID received from the second endpoint device 402-2 during a bootstrapping operation similar or the same as the bootstrapping operation 300.For example, during a bootstrapping operation, the endpoint device 402-1 receives from the endpoint device 402-2 a device ID (i.e., data indicating how to access the discovery service engine 420-2) that includes one or more available resolutions associated with the discovery service engine 420-2 running on the endpoint device 402-2. Based on these available resolutions, the application 404-1 may access the discovery service engine 420-2 using one or more communication protocols. In some embodiments, the endpoint device 402-1 receives from the endpoint device 402-2 a device ID that includes one or more available resolutions associated with one or more discovery service engines of one or more other endpoint devices communicatively coupled to the endpoint device 402-2. In other embodiments, an application 404-1 running on a first endpoint device 402-1 requests access to the discovery service engine 420-2 by first querying a resolution service engine 418-2 running on the endpoint device 402-2.

[0038] For example, referring now to FIG. 5, an exemplary request operation 500 for access to a discovery service engine is shown. According to some embodiments, a first endpoint device 502-1 similar or the same as the endpoint device 102 is configured to request access to a discovery service engine similar or the same as the discovery service engine 220 operating on a second endpoint device 502-2 communicatively coupled to the first endpoint device 502-1. The second endpoint device 502-2 includes a resolution service engine 518 similar or the same as the resolution service engine 218 and an identification engine 516 similar or the same as the identification engine 216. The request operation 500 includes the first endpoint device 502-1 sending an identification query 501 to the second endpoint device 502-2. In some embodiments, the identification query 501 includes data requesting a device ID of the second endpoint device 502-2. According to some embodiments, in response to receiving the identification query 501, the identification engine 516 of the second endpoint device 502-2 is configured to transmit device ID data 503 of the second endpoint device 502-2 to the first endpoint device 502-1. The device ID data 503 transmitted to the first endpoint device 502-1 includes data indicative of how to access the resolution services engine 518 of the second endpoint device 502-2. For example, the device ID data 503 includes data indicative of a communication protocol supported by the resolution services engine 518, an addressable location of the resolution services engine 518, or both.

[0039] The first endpoint device 502-1 generates a discovery access resolution request 505 based on the received device ID data 503, and transmits the discovery access resolution request 505 to the resolution service engine 518 of the second endpoint device 502-2. The discovery access resolution request 505 includes data requesting access information for a discovery service engine running on the second endpoint device 502-2. For example, the discovery access resolution request 505 includes a query of available resolutions for the discovery service engine of the second endpoint device 502-2. In response to receiving the discovery access resolution request 505, the resolution service engine 518 is configured to transmit resolution data 507 to the first endpoint device. The resolution data 507 includes one or more available resolutions for the discovery service engine of the second endpoint device 502-2. That is, the resolution data 507 includes data indicating how to access the discovery service engine of the second endpoint device 502-2. For example, the resolution data 507 includes one or more communication protocols supported by the discovery service engine and an addressable location of the discovery service engine. The first endpoint device 502-1 can access the discovery service engine of the second endpoint device 502-2 from the resolution data 507. For example, the resolution data 507 can include the address of the discovery service engine of the second endpoint device (e.g., Bluetooth LT). E) and one or more open ports over which the discovery service engine is available. Based on the identified communication protocols and open ports, the first endpoint device 502-1 can access the discovery service engine of the second endpoint device 502-2. In some embodiments, the resolution data 507 further includes one or more available resolutions for a discovery service engine of one or more endpoint devices communicatively coupled to the second endpoint device 502-2.

[0040] Referring again to FIG. 4, after accessing the discovery service engine 420-2 of the second endpoint device 402-2, the application 404-1 executing on the first endpoint device 402-1 queries for and receives from the discovery service engine 420-2 a list of available system services. The list of available system services includes each system service available to the second endpoint device 402-2, including those exported (i.e., shared) by one or more other endpoint devices. According to some embodiments, the first endpoint device 402-1 queries for and receives from the discovery service engine 420-2 one or more additional lists of available system services, including system services available to one or more respective other endpoint devices communicatively coupled to the second endpoint device 402-2. In this manner, the discovery service engine 420-2 serves as a bridge or intermediary between the first endpoint device 402-1 and one or more other endpoint devices communicatively coupled to the second endpoint device 402-2.

[0041] In some embodiments, the application 404-1 determines one or more applicable system services from one or more lists of available system services based on the functionality associated with one or more applications executed on the first endpoint device 402, where the applicable system services include system services that assist in or are necessary for the realization of one or more functionality associated with the applications executed on the endpoint device. For example, the application 404-1 determines one or more applicable system services from the list of system services that assist in or are necessary for the realization of one or more functionality associated with the application 404-1. After determining the applicable system services, the application 404-1 queries the resolution service engine 418-2 of the second endpoint device 402-2 for available resolutions associated with the applicable system services. In other words, the application 404-1 requests data from the resolution service engine 418-2 indicating how to access the applicable system services.

[0042] For example, referring now to FIG. 6, an exemplary request operation 600 for available system services from an endpoint device is presented. In some embodiments, a first endpoint device 602-1, similar or the same as the endpoint device 102, generates and transmits a system service query 601 to a discovery service engine 620 of a second endpoint device 602-2. The system service query 601 includes data requesting a list of system services available to the second endpoint device 602-2. In response to receiving the system service query 601, the discovery service engine 620 operating on the second endpoint device 602-2 transmits a list of available system services 603 to the first endpoint device 602-1. The list of available system services 603 includes data identifying each system service available to the second endpoint device 602-2. Such system services include system services running on the second endpoint device 602-2 and system services exported to or shared with the second endpoint device 602-2 by one or more other endpoint devices. According to some embodiments, the second endpoint device 602-2 transmits one or more additional lists of available system services. The one or more additional lists of available system services each include data identifying system services available to a respective other endpoint device communicatively coupled to the second endpoint device 602-2. Based on the list of available system services 603 or the one or more additional lists of available system services, the first endpoint device 602-1 determines one or more applicable system services based on one or more capabilities of applications executing on the first endpoint device 602-1.

[0043] After the first endpoint device 602-1 determines the one or more applicable applications, the first endpoint device 602-1 generates and transmits a resolution query 605 to the resolution service engine 618 of the second endpoint device 602-2. The resolution query 605 includes data requesting how to access the determined applicable system services (i.e., requesting one or more available resolutions for the applicable system services). In response to receiving the resolution query 605, the resolution service engine 618 of the second endpoint device 602-2 determines one or more available resolutions 607 for the applicable system services. For example, the resolution service engine 618 analyzes the resolution service data to determine one or more available resolutions 607 for the application system services. Once the resolution service engine 618 determines the available resolutions 607 for the applicable system services, the available resolutions 607 are transmitted to the first endpoint device 602-1.

[0044] Referring again to FIG. 4, after an application 404-1 executing on a first endpoint device 402-1 receives available resolutions for applicable system services, the application 404-1 accesses those applicable system services of the endpoint device 402-2 such that the application 404-1 controls the applicable system services. After the application 404-1 accesses the applicable system services, the first endpoint device 402-1 executes one or more applications 404 by implementing functionality associated with those applications 404 using the applicable system services. For example, the endpoint device 402-1 implements functionality associated with the application 404-1 using the system service 406-2 of the second endpoint device 402-2. In some embodiments, implementing the functionality of the application includes executing at least a portion of the application using the applicable system service. In this manner, the first endpoint device 402-1 gains the capabilities of the system service 406-2 of the second endpoint device 402-2.

[0045] As an example, the application 404-1 includes one or more notification functions, e.g., generating, displaying, and interacting with one or more notifications. The application 404-1 determines, from a list of available system services from the second endpoint device 402-2, one or more applicable system services that support displaying and interacting with one or more notifications, e.g., display APIs, input APIs, and interfaces of the second endpoint device 402-2. Once the application 404-1 receives available resolutions for the display APIs, input APIs, and interfaces of the second endpoint device 402-2, the application 404-1 facilitates displaying the one or more notifications, e.g., using the display APIs and interfaces of the second endpoint device 402-2, as well as interacting with the one or more notifications, e.g., using the input APIs and interfaces of the second endpoint device 402-2.

[0046] As another example, the application 404-1 may include one or more functions, such as receiving and streaming telephone calls. From the list of possible system services, the application 404-1 determines one or more applicable system services that support receiving and streaming telephone calls, e.g., the telecom API of the second endpoint device 402-2. Once the application 404-1 receives an available resolution for the telecom API of the second endpoint device 402-2, the application 404-1 uses, e.g., the telecom API of the second endpoint device 402-2 to achieve receiving and streaming telephone calls.

[0047] 7, a flow diagram of an example process 700 for executing an application using shared system services is shown. In step 705, a first endpoint device, similar or identical to the endpoint device 102, first accesses a discovery service engine of one or more other endpoint devices communicatively coupled to the first endpoint device. In some embodiments, to access the discovery service engine, the first endpoint device is configured to first detect one or more other endpoint devices according to one or more communication protocols. The first endpoint device then requests a device ID of each detected endpoint device. According to some embodiments, each device ID of the detected endpoint devices includes data indicating how to access a respective discovery service engine for that endpoint device.

[0048] Further, in step 705, when the first endpoint device accesses the discovery service engines of one or more other endpoint devices communicatively coupled to the first endpoint device, the first endpoint device queries for available system services for each of the other endpoint devices. That is, the first endpoint device queries from each of the other endpoint devices for system services running on the other endpoint devices and system services exported (i.e., shared) to the other endpoint devices from at least another different endpoint device. In step 710, the first endpoint device receives a list of available system services from each of the queried endpoint devices. The first endpoint device identifies one or more applicable system services from the list of available system services. The applicable system services include one or more system services that aid in or are necessary for the realization of one or more functions associated with one or more applications running on the first endpoint device. In step 715, the first endpoint device queries for resolution data regarding the applicable system services from one or more of the endpoint devices that listed the applicable system services. That is, the first endpoint device queries for endpoint devices that sent a list of available system services that include the applicable system services. In step 720, the first endpoint device receives one or more available solutions for each of the applicable system services from each endpoint device (i.e., the queried endpoint device). The available solutions include data indicating how to access and control the applicable system services, such as data indicating one or more communication protocols associated with the applicable system services and one or more addressable locations of the applicable system services.

[0049] In step 725, the first endpoint device executes one or more applications. Executing the one or more applications includes implementing one or more functions associated with the applications using one or more of the applicable system services. In this manner, the first endpoint device is able to communicate with other endpoints. In step 730, the first endpoint device receives data representative of an interaction with the respective endpoint device, including applicable system services that implement the functionality of the application executed on the first endpoint device. That is, the first endpoint device receives data representative of an interaction with the application executed on the first endpoint device from the second endpoint device, including applicable system services used to implement the functionality of the application executed on the first endpoint device. In this manner, the second endpoint device serves as a remote input device for the application executed on the first endpoint device. In step 735, the first endpoint device is configured to modify the execution of one or more applications according to the data representative of the interaction with the respective endpoint device. For example, the first endpoint device provides the data representative of the interaction with the respective endpoint device as input to one or more applications, initiates execution of one or more applications based on the data, stops execution of one or more applications based on the data, or performs any combination thereof, to name a few examples.

[0050] In some embodiments, some aspects of the techniques described above may be implemented by one or more processors of a processing system executing software. The software includes one or more sets of executable instructions stored or tangibly embodied on a non-transitory computer-readable storage medium. The software may include instructions and some data that, when executed by one or more processors, operate the one or more processors to perform one or more aspects of the techniques described above. The non-transitory computer-readable storage medium may include, for example, magnetic or optical disk storage, solid-state storage, such as flash memory, cache, random access memory (RAM), or other non-volatile memory devices. The executable instructions stored on the non-transitory computer-readable storage medium may be source code, assembly language code, object code, or other instruction formats that are interpreted or executable by one or more processors.

[0051] A computer-readable storage medium may include any storage medium or combination of storage media that can be accessed by a computer system while being used to provide instructions and / or data to the computer system. Such storage media may include, but are not limited to, optical media (e.g., compact discs (CDs), digital versatile discs (DVDs), Blu-ray discs), magnetic media (e.g., floppy disks, magnetic tapes, or magnetic hard drives), volatile memory (e.g., random access memory (RAM) or cache), non-volatile memory (e.g., read-only memory (ROM) or flash memory), or microelectromechanical systems (MEMS) based storage media. A computer readable storage medium may be embedded in a computing system (e.g., system RAM or ROM), fixedly attached to a computing system (e.g., a magnetic hard drive), removably attached to a computing system (e.g., an optical disk or Universal Serial Bus (USB)-based flash memory), or coupled to a computer system via a wired or wireless network (e.g., network accessible storage (NAS)).

[0052] It should be noted that not all of the operations or elements described above in the general description may be required, and some of the particular operations or devices may not be required, and one or more further operations may be performed or elements may be included in addition to those described above. Moreover, the order in which the operations are listed is not necessarily the order in which they are performed. Moreover, concepts have been described with reference to specific embodiments. However, those skilled in the art will recognize that various modifications and changes can be made without departing from the scope of the present disclosure as set forth in the appended claims. Accordingly, the specification and drawings should be interpreted in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of the present disclosure.

[0053] The word "or" used in the context of "at least one of A, B, or C" is used herein to mean "non-exclusive or." That is, in the above and similar contexts, it is used to mean "at least one or any combination thereof." For example, "at least one of A, B, and C" is used to mean "at least one of A, B, C, or any combination thereof."

[0054] Advantages, other advantages, and solutions to problems have been described above with respect to specific embodiments. However, these advantages, advantages, solutions to problems, and any features that may bring about or make any advantages, advantages, or solutions more prominent should not be construed as key, necessary, or essential features of any or all of the claims. Moreover, the above-disclosed subject matter may be modified and embodied in various but equivalent manners apparent to those skilled in the art having the benefit of the teachings herein. No limitation is intended to be imposed on the details of construction or design shown herein, other than as set forth in the appended claims. It is therefore apparent that the above-disclosed specific embodiments may be altered or modified, and all such variations are deemed to be within the scope of the disclosed subject matter. Accordingly, the protection sought herein is as set forth in the appended claims.

Claims

1. 1. A method comprising: receiving, by a first endpoint device, from a second endpoint device, a list of available system services associated with the second endpoint device and an available solution for at least one available system service from the list of available system services; and executing, by the first endpoint device, one or more applications associated with a function, wherein executing the one or more applications includes transmitting data from the first endpoint device to the second endpoint device that implements the function using at least one available system from the list of available system services based on the available resolution.

2. The method further comprises: receiving, by the first endpoint device, a plurality of available solutions from the second endpoint device based on at least one available system service from the list of available system services; The method of claim 1 , wherein the available solution is one of the plurality of available solutions.

3. receiving, by the first endpoint device, data from the second endpoint device representative of an interaction with the one or more applications; and modifying, by the first endpoint device, execution of the one or more applications based on the data representing the interaction with the one or more applications.

4. receiving, by the first endpoint device, from the second endpoint device, a second list of available system services associated with a third endpoint device communicatively coupled to the second endpoint device; and requesting, by the first endpoint device, from the second endpoint device, a second available solution for a system service from the second list of available system services.

5. 5. The method of claim 4, wherein executing the one or more applications further comprises transmitting, by the first endpoint device, data to the third endpoint device that implements the functionality using the system services from the second list of available system services based on the second available resolution.

6. detecting, by the first endpoint device, the second endpoint device; and receiving, by the first endpoint device, from the second endpoint device, resolution service data associated with the second endpoint device.

7. and transmitting, by the first endpoint device, the second endpoint device over a communication protocol of a plurality of communication protocols based on the resolution service data.

7. The method of claim 6, further comprising the step of requesting from the second endpoint device the list of available system services associated with the second endpoint device.

8. 1. A method comprising: detecting, by a first endpoint device, a second endpoint device that includes one or more system services; receiving, by the first endpoint device, available solutions associated with the one or more system services of the second endpoint device; and executing, on the first endpoint device, one or more applications using the one or more system services of the second endpoint device based on the available solutions associated with the one or more system services.

9. receiving resolution service data from the second endpoint device; and requesting, by the first endpoint device, a list including the one or more system services over a communication protocol based on the resolution service data.

10. receiving, by the first endpoint device, data from the second endpoint device representative of an interaction with the one or more applications; and executing the one or more applications based on the data representative of the interaction with the one or more applications.

11. The method of claim 8 , wherein the available solution is one of a plurality of available solutions received from the second endpoint device.

12. 12. The method of claim 8, wherein the second endpoint device is detected by a first communication protocol and the available solution is received by a second communication protocol.

13. 13. The method of claim 8, further comprising the step of requesting, by the first endpoint device, access to a discovery service engine of the second endpoint device in response to detecting the second endpoint device.

14. receiving, at the first endpoint device, resolution service data associated with the discovery service engine of the second endpoint device; and accessing the discovery service engine of the second endpoint device based on the resolution service data.

15. 15. The method of claim 14, further comprising accessing the discovery service engine of the second endpoint device via a communication protocol of a plurality of communication protocols based on the resolution service data.

16. The method of claim 1 , wherein the one or more applications are configured to render one or more notifications.

17. The step of executing the one or more applications includes the step of rendering one or more notifications on a display electronically coupled to the second endpoint device. The method of claim 1 , further comprising:

18. 18. The method of claim 1, wherein the first endpoint device has a first operating system and the second endpoint device has a second operating system that is separate from the first operating system.

19. 20. The method of claim 18, wherein the second operating system has at least one different interface, language, memory management technique, communications protocol, encryption, or network stack than the first operating system.

20. The method of claim 1 , wherein the second endpoint device is proximate to the first endpoint device.

21. The method of claim 1 , wherein the second endpoint device includes device ID data of a third endpoint device.

22. 1. A system comprising:

22. A system comprising: a first endpoint device including one or more processors, the first endpoint device storing executable instructions configured to operate the one or more processors to perform the method of any one of claims 1 to 21.

23. 1. A system comprising:

22. A system comprising an endpoint device framework including one or more endpoint devices communicatively coupled to one or more other endpoint devices, the system configured to perform the method of any one of claims 1 to 21.

Citation Information

Patent Citations

  • System and method for distributed processing, computer- readable recording medium with program for computer to execute the same method recorded therein, server device and client device

    JP2000172657A

  • Household electric appliance network system

    JP2006065871A

  • System and Method for Transmitting a Services List to a Playback Device

    US20130067527A1