Ecological device management method and device, storage medium and electronic device
By generating cross-ecosystem sharing information and transmitting it across applications, the application to be shared can access the target cloud without negotiation, thus solving the problem of difficult cross-ecosystem device management and achieving convenient and efficient device management.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- SHENZHEN TCL NEW-TECH CO LTD
- Filing Date
- 2021-12-23
- Publication Date
- 2026-05-12
AI Technical Summary
Cross-ecosystem device management is difficult, information silos and small networks are hard to disentangle, networking is difficult, and existing cloud-to-cloud interconnection methods require commercial cooperation, resulting in complex management.
By generating cross-ecosystem sharing information and transmitting it across applications to the application to be shared, the application to be shared can access the target cloud of the target ecosystem without negotiation, thus achieving cross-ecosystem control.
It enables convenient and effective cross-ecosystem device management and control, improving the reliability and efficiency of device management.
Smart Images

Figure CN116346842B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of Internet of Things (IoT) technology, specifically to a cross-ecosystem device management method, apparatus, storage medium, and electronic device. Background Technology
[0002] Cross-ecosystem device management refers to the task of managing devices from two different ecosystems (such as manufacturers) through a single entity. Currently, cross-ecosystem device management is typically achieved through prior negotiation between the cloud environments of the two ecosystems. This cloud-to-cloud interoperability is a point-to-point access solution, requiring both parties to establish a business partnership before cross-ecosystem networking can be achieved. This current approach inevitably creates information silos and small networks, making it difficult for users to understand the relationships between these silos and small networks, thus hindering cross-ecosystem networking and consequently, cross-ecosystem device management. Summary of the Invention
[0003] This application provides a solution that can conveniently and effectively manage cross-ecological devices.
[0004] The embodiments of this application provide the following technical solutions:
[0005] According to one embodiment of this application, a cross-ecosystem device management method includes: generating cross-ecosystem sharing information for a device to be shared based on a target application, wherein the device to be shared belongs to the target ecosystem; transmitting the cross-ecosystem sharing information across applications to the application to be shared, wherein the application to be shared and the device to be shared belong to different ecosystems, wherein the application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem management of the device to be shared through the target cloud.
[0006] In some embodiments of this application, before transmitting the cross-ecosystem sharing information across applications to the application to be shared, the method further includes: displaying authorization prompt content for information sharing through the target application; receiving response information from the authorization prompt content, and determining whether to transmit the cross-ecosystem sharing information across applications based on the response information.
[0007] In some embodiments of this application, the cross-ecosystem sharing information includes the basic address information of the cloud, the device information of the device to be shared, and access credentials; the application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem control over the device to be shared through the target cloud, including: the application to be shared obtains the object model and pre-agreed path information, constructs an access address based on the path information and the basic address information, constructs access parameters based on the device information, access credentials, and object model according to a pre-agreed format; and sends a target instruction to the target cloud based on the access address and the access parameters, so that the target cloud can control the device to be shared.
[0008] In some embodiments of this application, the cross-ecosystem sharing information includes the basic address information of the cloud, the device information of the device to be shared, and access credentials; the application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem control over the device to be shared through the target cloud, including: the application to be shared transmits the cross-ecosystem sharing information to the home cloud of the ecosystem to which the application to be shared belongs, wherein the home cloud obtains the object model and pre-agreed path information, constructs an access address based on the path information and the basic address information, constructs access parameters based on the device information, access credentials, and object model according to a pre-agreed format, and the home cloud sends a target instruction to the target cloud based on the access address and the access parameters, so that the target cloud can control the device to be shared.
[0009] In some embodiments of this application, the step of transmitting the cross-ecosystem sharing information across applications to the application to be shared includes: displaying an application list based on the first application; determining the application to be shared selected from the application list; and transmitting the cross-ecosystem sharing information across applications to the application to be shared through the first application.
[0010] In some embodiments of this application, the step of transmitting the cross-ecosystem sharing information across applications to the application to be shared includes: obtaining information transmission content containing the cross-ecosystem sharing information based on the first application; sending the information transmission content to the target terminal through the first application, so that the target terminal opens the application to be shared according to the target protocol and transmits the information transmission content to the application to be shared.
[0011] In some embodiments of this application, the step of transmitting the cross-ecosystem sharing information across applications to the application to be shared includes: obtaining information transmission content containing the cross-ecosystem sharing information based on the first application, and copying the information transmission content to a target location, so that when the target object opens the application to be shared, the application to be shared obtains the information transmission content from the target location.
[0012] According to one embodiment of this application, a cross-ecosystem device management and control device includes: a generation module, configured to generate cross-ecosystem sharing information of a device to be shared based on a target application, wherein the device to be shared belongs to the target ecosystem; and a sharing module, configured to transmit the cross-ecosystem sharing information across applications to the application to be shared, wherein the application to be shared and the device to be shared belong to different ecosystems, wherein the application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem management and control of the device to be shared through the target cloud.
[0013] According to another embodiment of this application, a storage medium stores a computer program thereon, which, when executed by a computer's processor, causes the computer to perform the methods described in the embodiments of this application.
[0014] According to another embodiment of this application, an electronic device may include: a memory storing a computer program; and a processor reading the computer program stored in the memory to execute the methods described in the embodiments of this application.
[0015] In this embodiment, cross-ecosystem sharing information of a device to be shared is generated based on a target application, wherein the device to be shared belongs to the target ecosystem. The cross-ecosystem sharing information is transmitted across applications to the application to be shared, wherein the application to be shared and the device to be shared belong to different ecosystems. The application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem management and control of the device to be shared through the target cloud.
[0016] In this way, cross-application and cross-ecosystem sharing information is transmitted to the application to be shared. The application to be shared can access the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information. The target cloud can then perform cross-ecosystem management and control of the device to be shared, thus achieving convenient and effective cross-ecosystem device management and control. Attached Figure Description
[0017] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0018] Figure 1 A schematic diagram of a system that can be applied to embodiments of this application is shown.
[0019] Figure 2 A flowchart of a cross-ecosystem device management method according to an embodiment of this application is shown.
[0020] Figure 3 A block diagram of a cross-ecological device management device according to an embodiment of this application is shown.
[0021] Figure 4 A block diagram of an electronic device according to an embodiment of this application is shown. Detailed Implementation
[0022] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0023] In the following description, specific embodiments of this application will be illustrated with reference to steps and symbols performed by one or more computers, unless otherwise stated. Therefore, these steps and operations will be referred to several times as being performed by a computer, and computer execution as referred to herein includes operations by a computer processing unit representing electronic signals of data in a structured format. This operation transforms the data or maintains it at a location in the computer's memory system, which can be reconfigured or otherwise alter the operation of the computer in a manner well known to those skilled in the art. The data structure maintained by the data is the physical location of the memory, which has specific characteristics defined by the data format. However, the principles of this application are described in the foregoing text, which is not intended to be limiting, and those skilled in the art will understand that many of the steps and operations described below can also be implemented in hardware.
[0024] Figure 1 A schematic diagram of a system 100 to which embodiments of this application can be applied is shown. Figure 1 As shown, system 100 may include cloud server 101, device 102, and device 103. Device 102 and device 103 may be any computer device, such as a computer, mobile phone, smartwatch, and home appliance. Cloud server 101 may be a server that provides cloud services.
[0025] In one embodiment of this example, device 102 can: generate cross-ecosystem sharing information for a device to be shared based on a target application, wherein the device to be shared belongs to the target ecosystem; transmit the cross-ecosystem sharing information across applications to the application to be shared, wherein the application to be shared and the device to be shared belong to different ecosystems, wherein the application to be shared accesses the target cloud (such as cloud server 101) of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem management and control of the device to be shared (such as device 103) through the target cloud.
[0026] Figure 2 A flowchart illustrating a cross-ecosystem device management method according to an embodiment of this application is shown schematically. The implementing entity of this cross-ecosystem device management method can be any device, such as... Figure 1 The device 102 shown.
[0027] like Figure 2 As shown, the cross-ecological device management method may include steps S210 to S220.
[0028] Step S210: Generate cross-ecosystem sharing information for the device to be shared based on the target application, wherein the device to be shared belongs to the target ecosystem;
[0029] Step S220: The cross-ecosystem sharing information is transmitted across applications to the application to be shared, wherein the application to be shared and the device to be shared belong to different ecosystems; wherein, the application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem management and control of the device to be shared through the target cloud.
[0030] The device to be shared belongs to the target ecosystem, which may include a target manufacturer or a custom-defined device ecosystem. Cross-ecosystem sharing refers to the ability for devices from other ecosystems to directly access the target ecosystem's cloud to manage the device to be shared. The target application and the device to be shared can belong to the same target ecosystem. After the user selects the device to be shared in the target application, the target application can generate the corresponding cross-ecosystem sharing information.
[0031] After generating cross-ecosystem sharing information in the target application, it is transmitted to the application to be shared through cross-application means. The application to be shared and the device to be shared belong to different ecosystems. The application to be shared can access the target cloud of the target ecosystem corresponding to the device to be shared without negotiation based on the cross-ecosystem sharing information. In this way, the application to be shared can perform cross-ecosystem management and control of the device to be shared through the target cloud.
[0032] In this way, based on steps S210 to S240, cross-application sharing information is transmitted to the application to be shared. The application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information. The target cloud then performs cross-ecosystem management and control on the device to be shared, thereby achieving convenient and effective cross-ecosystem device management and control.
[0033] The following describes the specific steps involved in managing cross-ecological devices.
[0034] In step S210, cross-ecosystem sharing information of the device to be shared is generated based on the target application, wherein the device to be shared belongs to the target ecosystem.
[0035] The device to be shared belongs to the target ecosystem, which may include a target manufacturer or a custom-defined device ecosystem. Cross-ecosystem sharing refers to the ability for devices from other ecosystems to directly access the target ecosystem's cloud to manage the device to be shared. The target application and the device to be shared can belong to the same target ecosystem. After the user selects the device to be shared in the target application, the target application can generate the corresponding cross-ecosystem sharing information.
[0036] Cross-ecosystem information sharing can include the target ecosystem's cloud base address information (such as vendor A's cloud base URL), the device information of the devices to be shared (such as a list of unique IDs of the devices to be shared, with each device corresponding to one ID), and access credentials (which may include refresh credential tokens and access credential tokens).
[0037] In one embodiment, before transmitting the cross-ecosystem sharing information across applications to the application to be shared in step S210, the method further includes: displaying authorization prompt content for information sharing through the target application; receiving response information from the authorization prompt content, and determining whether to transmit the cross-ecosystem sharing information across applications based on the response information.
[0038] The authorization prompt is displayed in the target application to prompt the user to grant authorization. For example, the target application might display the authorization prompt "This information is very important; please do not easily distribute it," where distributing it is roughly equivalent to granting device information and control rights, requiring user consent. When the user clicks the authorization response control (e.g., agree or disagree) on the display interface, a response message is generated. Based on this response message, it is determined whether the cross-application, cross-ecosystem sharing information should be transmitted. For example, if the response message is "agree," then cross-application, cross-ecosystem sharing information is confirmed; conversely, if the response message is "disagree," then cross-application, cross-ecosystem sharing information is not allowed. This further enhances the reliability of cross-ecosystem device management.
[0039] In one embodiment, step S210, transmitting the cross-ecosystem sharing information across applications to the application to be shared, includes: displaying an application list based on the target application; determining the application to be shared selected from the application list; and transmitting the cross-ecosystem sharing information across applications to the application to be shared through the target application.
[0040] The target application can display a list of applications, which can show at least one application. Users can select the application to be shared from the application list. Then, the target application can transmit cross-ecosystem sharing information to the application to be shared through a preset cross-application protocol. The cross-application protocol is the protocol for message transmission between the two types of applications. Through the cross-application protocol, messages in the target application can be converted into messages that the application to be shared can accept.
[0041] In one example, the application list can list all applications in the system that conform to the same criteria for the user to select. Optional ways to list all applications include: applications that declare the same URL scheme, such as "Operational Level Agreement (OLA)," where a URL scheme is a system-provided mechanism that applications can register and then other programs can invoke that application through the URL scheme; and / or applications that declare the ability to open the same type of file, such as application / ola.device.sharepayload; and / or applications that declare sharing controls containing the same keywords, such as ola.tcl.shareplayload.
[0042] Furthermore, in one example, the target application and the application to be shared are located on the same device. After the user transmits cross-ecosystem sharing information across application protocols to the application to be shared through the target application, the device can automatically jump to the application to be shared through user operation.
[0043] In one embodiment, step S210, transmitting the cross-ecosystem sharing information across applications to the application to be shared, includes: obtaining information transmission content containing the cross-ecosystem sharing information based on the target application; sending the information transmission content to the target terminal through the target application, so that the target terminal opens the application to be shared according to the target protocol and transmits the information transmission content to the application to be shared.
[0044] The target application can display information that includes cross-ecosystem sharing information, such as QR codes, URLs, or strings. The target application can send the information to the target terminal via email, instant messaging software, or wireless transmission protocols (such as Bluetooth, AirDrop, etc.).
[0045] After receiving the information, the target terminal can open the application to be shared that has declared the target protocol corresponding to the information and pass the information such as QR code, URL or string to the application to be shared.
[0046] In one embodiment, step S210, which involves transmitting the cross-ecosystem sharing information across applications to the application to be shared, includes: obtaining information transmission content containing the cross-ecosystem sharing information based on the target application, and copying the information transmission content to a target location, so that when the target object opens the application to be shared, the application to be shared obtains the information transmission content from the target location.
[0047] The target location, such as the clipboard or a specific storage location, is where the target application copies the information to be transmitted to. When the sharing application opens the application, it can automatically or manually retrieve the information from the target location.
[0048] In step S220, the cross-ecosystem sharing information is transmitted across applications to the application to be shared, wherein the application to be shared and the device to be shared belong to different ecosystems; wherein, the application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem management and control of the device to be shared through the target cloud.
[0049] After generating cross-ecosystem sharing information in the target application, it is transmitted to the application to be shared through cross-application means. The application to be shared and the device to be shared belong to different ecosystems. The application to be shared can access the target cloud of the target ecosystem corresponding to the device to be shared without negotiation based on the cross-ecosystem sharing information. In this way, the application to be shared can perform cross-ecosystem management and control of the device to be shared through the target cloud.
[0050] In one embodiment, the cross-ecosystem sharing information includes the basic address information of the cloud, the device information of the device to be shared, and access credentials. The application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem control over the device to be shared through the target cloud. This includes: the application to be shared obtaining the object model and pre-agreed path information, constructing an access address based on the path information and the basic address information, constructing access parameters based on the device information, access credentials, and object model according to a pre-agreed format, and sending a target instruction to the target cloud based on the access address and the access parameters, so that the target cloud can control the device to be shared.
[0051] The object model abstracts the application to be shared into a data model composed of attributes, services, and events. The pre-agreed path information is the pre-agreed path information for accessing the target cloud. The application to be shared combines the basic address information and path information to form an access path. After constructing access parameters according to a pre-set format based on device information, access credentials, and the object model, the application to be shared can send target instructions to the target cloud based on the access address and access parameters. The target instructions enable the cloud to perform management operations such as acquiring device information, subscribing to device events, controlling devices, and authorizing refresh control for the device to be shared.
[0052] In one embodiment, the cross-ecosystem sharing information includes the basic address information of the cloud, the device information of the device to be shared, and access credentials. The application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem control over the device to be shared through the target cloud. This includes: the application to be shared transmitting the cross-ecosystem sharing information to the home cloud of the ecosystem to which the application to be shared belongs; wherein the home cloud obtains the object model and pre-agreed path information, constructs an access address based on the path information and the basic address information, constructs access parameters based on the device information, access credentials, and object model according to a pre-agreed format, and the home cloud sends a target instruction to the target cloud based on the access address and the access parameters, so that the target cloud can control the device to be shared.
[0053] The object model abstracts the application to be shared into a data model composed of attributes, services, and events. The pre-agreed path information is the pre-agreed path information for accessing the target cloud. The home cloud corresponding to the application to be shared combines the basic address information and path information to form an access path. After constructing access parameters according to a pre-set format based on device information, access credentials, and the object model, the application to be shared can send target instructions to the target cloud through its corresponding home cloud based on the access address and access parameters. The target instructions enable the cloud to perform management operations such as acquiring device information, subscribing to device events, controlling devices, and authorizing refresh control for the device to be shared.
[0054] To facilitate better implementation of the cross-ecosystem device management method provided in this application, this application also provides a cross-ecosystem device management apparatus based on the above-described cross-ecosystem device management method. The meanings of the terms used are the same as in the above-described cross-ecosystem device management method, and specific implementation details can be found in the descriptions in the method embodiments. Figure 3 A block diagram of a cross-ecological device management device according to an embodiment of this application is shown.
[0055] like Figure 3 As shown, the cross-ecological device management and control device 300 may include a generation module 310 and a sharing module 320.
[0056] The generation module 310 can be used to generate cross-ecosystem sharing information for a device to be shared based on a target application, wherein the device to be shared belongs to the target ecosystem; the sharing module 320 can be used to transmit the cross-ecosystem sharing information across applications to the application to be shared, wherein the application to be shared and the device to be shared belong to different ecosystems, wherein the application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem management and control of the device to be shared through the target cloud.
[0057] In some embodiments of this application, the apparatus further includes: a prompt content display unit, configured to display authorization prompt content for information sharing through the target application; and a response information receiving unit, configured to receive response information from the authorization prompt content, so as to determine whether to transmit the cross-application sharing information based on the response information.
[0058] In some embodiments of this application, the cross-ecosystem sharing information includes the basic address information of the cloud, the device information of the device to be shared, and access credentials; the application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem control over the device to be shared through the target cloud, including: the application to be shared obtains the object model and pre-agreed path information, constructs an access address based on the path information and the basic address information, constructs access parameters based on the device information, access credentials, and object model according to a pre-agreed format; and sends a target instruction to the target cloud based on the access address and the access parameters, so that the target cloud can control the device to be shared.
[0059] In some embodiments of this application, the cross-ecosystem sharing information includes the basic address information of the cloud, the device information of the device to be shared, and access credentials; the application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem control over the device to be shared through the target cloud, including: the application to be shared transmits the cross-ecosystem sharing information to the home cloud of the ecosystem to which the application to be shared belongs, wherein the home cloud obtains the object model and pre-agreed path information, constructs an access address based on the path information and the basic address information, constructs access parameters based on the device information, access credentials, and object model according to a pre-agreed format, and the home cloud sends a target instruction to the target cloud based on the access address and the access parameters, so that the target cloud can control the device to be shared.
[0060] In some embodiments of this application, the sharing module includes a first sharing unit, configured to: display an application list based on the first application; determine the application to be shared selected from the application list; and transmit the cross-ecosystem sharing information across application protocols to the application to be shared through the first application.
[0061] In some embodiments of this application, the sharing module includes a second sharing unit, configured to: obtain information transmission content containing the cross-ecosystem sharing information based on the first application; and send the information transmission content to a target terminal through the first application, so that the target terminal opens the application to be shared according to the target protocol and transmits the information transmission content to the application to be shared.
[0062] In some embodiments of this application, the sharing module includes a third sharing unit, configured to: obtain information transmission content containing the cross-ecosystem sharing information based on the first application, and copy the information transmission content to a target location, so that when the target object opens the application to be shared, the application to be shared obtains the information transmission content from the target location.
[0063] In this way, based on the cross-ecosystem device management and control device 300, cross-ecosystem sharing information is transmitted across applications to the application to be shared. The application to be shared can access the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, and then perform cross-ecosystem management and control on the device to be shared through the target cloud, thus achieving convenient and effective cross-ecosystem device management and control.
[0064] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of this application, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.
[0065] Furthermore, embodiments of this application also provide an electronic device, which can be a terminal or a server, such as... Figure 4 As shown, it illustrates a structural schematic diagram of the electronic device involved in the embodiments of this application, specifically:
[0066] The electronic device may include components such as a processor 401 with one or more processing cores, a memory 402 with one or more computer-readable storage media, a power supply 403, and an input unit 404. Those skilled in the art will understand that... Figure 4 The electronic device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein:
[0067] The processor 401 is the control center of the electronic device. It connects to various parts of the computer device via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 402, and by calling data stored in the memory 402, it performs various functions of the computer device and processes data, thereby providing overall monitoring of the electronic device. Optionally, the processor 401 may include one or more processing cores; preferably, the processor 401 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user page, and application programs, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 401.
[0068] The memory 402 can be used to store software programs and modules. The processor 401 executes various functional applications and data processing by running the software programs and modules stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 402 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 402 may also include a memory controller to provide the processor 401 with access to the memory 402.
[0069] The electronic device also includes a power supply 403 that supplies power to the various components. Preferably, the power supply 403 can be logically connected to the processor 401 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 403 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.
[0070] The electronic device may also include an input unit 404, which can be used to receive input digital or character information, and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.
[0071] Although not shown, the electronic device may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 401 in the electronic device loads the executable files corresponding to the processes of one or more computer programs into the memory 402 according to the following instructions, and the processor 401 runs the computer programs stored in the memory 402, thereby realizing the various functions in the foregoing embodiments of this application. For example, the processor 401 can perform the following steps:
[0072] Based on the target application, cross-ecosystem sharing information for the device to be shared is generated, wherein the device to be shared belongs to the target ecosystem. The cross-ecosystem sharing information is transmitted across applications to the application to be shared, wherein the application to be shared and the device to be shared belong to different ecosystems. The application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem management and control of the device to be shared through the target cloud.
[0073] In some embodiments of this application, before transmitting the cross-ecosystem sharing information across applications to the application to which it is to be shared, the processor 401 may execute: displaying authorization prompt content for information sharing through the target application; receiving response information from the authorization prompt content, and determining whether to transmit the cross-ecosystem sharing information across applications based on the response information.
[0074] In some embodiments of this application, the cross-ecosystem sharing information includes the basic address information of the cloud, the device information of the device to be shared, and access credentials. When the application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem management and control of the device to be shared through the target cloud, the processor 401 can execute: the application to be shared obtains the object model and the pre-agreed path information, and constructs an access address based on the path information and the basic address information, and constructs access parameters based on the device information, access credentials, and object model according to the pre-agreed format; and, based on the access address and the access parameters, sends a target instruction to the target cloud so that the target cloud can manage and control the device to be shared.
[0075] In some embodiments of this application, the cross-ecosystem sharing information includes the basic address information of the cloud, the device information of the device to be shared, and access credentials. When the application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem management and control of the device to be shared through the target cloud, the processor 401 can execute: the application to be shared transmits the cross-ecosystem sharing information to the home cloud of the ecosystem to which the application to be shared belongs, wherein the home cloud obtains the object model and the pre-agreed path information, constructs an access address based on the path information and the basic address information, constructs access parameters based on the device information, access credentials, and object model according to the pre-agreed format, and the home cloud sends a target instruction to the target cloud based on the access address and the access parameters, so that the target cloud can manage and control the device to be shared.
[0076] In some embodiments of this application, when transmitting the cross-ecosystem sharing information across applications to the application to be shared, the processor 401 may execute: displaying an application list based on the first application; determining the application to be shared selected from the application list; and transmitting the cross-ecosystem sharing information across applications to the application to be shared through the first application.
[0077] In some embodiments of this application, when transmitting the cross-ecosystem sharing information across applications to the application to be shared, the processor 401 may execute: obtaining information transmission content containing the cross-ecosystem sharing information based on the first application; sending the information transmission content to the target terminal through the first application, so that the target terminal opens the application to be shared according to the target protocol and transmits the information transmission content to the application to be shared.
[0078] In some embodiments of this application, when the cross-ecosystem sharing information is transmitted across applications to the application to be shared, the processor 401 may execute: obtaining information transmission content containing the cross-ecosystem sharing information based on the first application, and copying the information transmission content to a target location, so that when the target object opens the application to be shared, the application to be shared obtains the information transmission content from the target location.
[0079] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by a computer program, or by a computer program controlling related hardware. The computer program can be stored in a computer-readable storage medium and loaded and executed by a processor.
[0080] Therefore, embodiments of this application also provide a storage medium storing a computer program that can be loaded by a processor to execute the steps in any of the methods provided in embodiments of this application.
[0081] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.
[0082] Since the computer program stored in the storage medium can execute the steps of any of the methods provided in the embodiments of this application, the beneficial effects that the methods provided in the embodiments of this application can achieve can be realized. For details, please refer to the previous embodiments, which will not be repeated here.
[0083] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein.
[0084] It should be understood that this application is not limited to the embodiments described above and shown in the accompanying drawings, but various modifications and changes can be made without departing from its scope.
Claims
1. A method for cross-ecological equipment management and control, characterized in that, include: Cross-ecosystem sharing information of the device to be shared is generated based on the target application, wherein the device to be shared belongs to the target ecosystem; The cross-ecosystem sharing information includes the basic address information of the target cloud of the target ecosystem, the device information of the device to be shared, and access credentials. The target application transmits the cross-ecosystem sharing information across applications to the application to be shared, wherein the application to be shared and the device to be shared belong to different ecosystems; wherein the application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem management and control of the device to be shared through the target cloud; The application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem management and control of the device to be shared through the target cloud, including: The application to be shared acquires the object model and pre-agreed path information, constructs an access address based on the path information and the basic address information, and constructs access parameters based on the device information, access credentials and object model according to a pre-agreed format; and sends a target instruction to the target cloud based on the access address and the access parameters, so that the target cloud can control the device to be shared.
2. The method according to claim 1, characterized in that, Before transmitting the cross-ecosystem sharing information across applications to the application to which it is to be shared, the method further includes: The target application displays authorization prompts for information sharing. The system receives a response message from the authorization prompt and determines whether to transmit the cross-ecosystem sharing information across applications based on the response message.
3. The method according to claim 1, characterized in that, The cross-ecosystem sharing information includes the basic address information of the cloud, the device information of the device to be shared, and access credentials. The application to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, so as to perform cross-ecosystem management and control of the device to be shared through the target cloud, including: The application to be shared transmits the cross-ecosystem sharing information to the cloud of the ecosystem to which the application to be shared belongs. Specifically, the cloud-based entity model and pre-agreed path information are obtained, and an access address is constructed based on the path information and the basic address information. Access parameters are constructed according to a pre-agreed format based on the device information, access credentials, and entity model. Furthermore, the home cloud sends a target instruction to the target cloud based on the access address and the access parameters, so that the target cloud can manage and control the device to be shared.
4. The method according to claim 1, characterized in that, The step of transmitting the cross-ecosystem sharing information across applications to the application to be shared includes: Display an application list based on the target application; Determine the application to be shared selected from the application list; The cross-ecosystem sharing information is transmitted to the application to be shared via the target application through the cross-application protocol.
5. The method according to claim 1, characterized in that, The step of transmitting the cross-ecosystem sharing information across applications to the application to be shared includes: Based on the target application, obtain information transmission content containing the cross-ecosystem sharing information; The information content is sent to the target terminal through the target application, so that the target terminal opens the application to be shared according to the target protocol and passes the information content to the application to be shared.
6. The method according to claim 1, characterized in that, The step of transmitting the cross-ecosystem sharing information across applications to the application to be shared includes: Based on the target application, obtain the information transmission content containing the cross-ecosystem sharing information, and copy the information transmission content to the target location so that when the target object opens the application to be shared, the application to be shared obtains the information transmission content from the target location.
7. A cross-ecological equipment management and control device, characterized in that, include: The generation module is used to generate cross-ecosystem sharing information for a device to be shared based on the target application, wherein the device to be shared belongs to the target ecosystem. The cross-ecosystem sharing information includes the basic address information of the target cloud of the target ecosystem, the device information of the device to be shared, and access credentials. A sharing module is used to transmit cross-ecosystem sharing information across applications to a target application, where the target application and the device to be shared belong to different ecosystems. The target application, based on the cross-ecosystem sharing information, accesses the target cloud of the target ecosystem without negotiation to manage the device across ecosystems via the target cloud. This access includes: the target application acquiring an object model and pre-agreed path information, constructing an access address based on the path information and basic address information, and constructing access parameters according to a pre-agreed format based on device information, access credentials, and the object model; and sending a target instruction to the target cloud based on the access address and access parameters, enabling the target cloud to manage the device.
8. A storage medium, characterized in that, It stores a computer program that, when executed by the computer's processor, causes the computer to perform the method described in any one of claims 1 to 6.
9. An electronic device, characterized in that, include: Memory, which stores computer programs; A processor reads a computer program stored in memory to perform the method described in any one of claims 1 to 6.