Cross-ecosystem device management control method, device, storage medium, and electronic device

Abstract

The present application discloses a method, apparatus, storage medium and electronic device for managing and controlling a cross-ecosystem device, which relates to the field of Internet of Things technology, and the method generates cross-ecosystem shared information of a device waiting to share, and transmits it across applications to an application waiting to share, where the application waiting to share belongs to a different ecosystem from the device waiting to share, and the application waiting to share accesses a target cloud without negotiation based on the cross-ecosystem shared information to perform cross-ecosystem management control for the device waiting to share. The present application realizes convenient and effective management control of a cross-ecosystem device.

Description

[Technical Field]

[0001] The present application relates to the field of Internet of Things (IoT) technology, and in particular to a method, apparatus, storage medium and electronic device for managing and controlling cross-ecosystem devices. [Background technology]

[0002] Management control of cross-ecosystem devices is the act of one of the devices in two different ecosystems (e.g., manufacturers) exercising management control over the other. Currently, management control of cross-ecosystem devices is typically achieved by two ecosystem clouds communicating through pre-negotiations. Such communication between clouds is a point-to-point access scheme, and both parties must first achieve commercial cooperation before a cross-ecosystem network can be realized. Summary of the Invention [Problem to be solved by the invention]

[0003] With the current method, the emergence of information silos and small networks is inevitable, and users usually find it difficult to organize the relationships between these information silos and small networks, which makes ecosystem networks difficult, making it difficult to manage and control cross-ecosystem devices. [Means for solving the problem]

[0004] The embodiments of the present application provide a technical solution for convenient and effective management and control of cross-ecosystem devices.

[0005] The embodiments of the present application provide the following technical solutions.

[0006] According to one embodiment of the present application, a method for managing and controlling a cross-ecosystem device includes: generating cross-ecosystem sharing information of a device waiting to be shared based on a target application, where the device waiting to be shared belongs to the target ecosystem; and transmitting the cross-ecosystem sharing information to an application waiting to be shared across applications, where the application waiting to be shared belongs to a different ecosystem from the device waiting to be shared; wherein the application waiting to be shared accesses a target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, and performs cross-ecosystem management control on the device waiting to be shared by the target cloud.

[0007] In some embodiments of the present application, before transmitting the cross-ecosystem shared information across applications to the application to be shared, the method further includes: displaying a permission offer for information sharing by the target application; receiving response information of the permission offer; and determining whether to transmit the cross-ecosystem shared information across applications based on the response information.

[0008] In some embodiments of the present application, the cross-ecosystem shared information is the goalThe shared information includes base address information of the target cloud, device information of the device to be shared, and access authentication information. The shared application accessing the target cloud of the target ecosystem without negotiation based on the cross-ecosystem shared information and exercising cross-ecosystem management control over the device to be shared by the target cloud includes the shared application obtaining a thing model and predetermined path information, constructing an access address based on the path information and the base address information, and constructing access parameters based on a preset format, the device information, access authentication information, and the thing model, and the shared application sending a target command to the target cloud based on the access address and the access parameters, so that the target cloud exercises management control over the device to be shared.

[0009] In some embodiments of the present application, the cross-ecosystem shared information is the goal The shared information includes a base address information of the target cloud, device information of the device to be shared, and access authentication information. The shared information is shared by the application to be shared without negotiation to access the target cloud of the target ecosystem without negotiation, and the target cloud performs cross-ecosystem management control on the device to be shared. Yes The method includes transmitting the shared waiting device to an attribution cloud of an ecosystem to which the waiting application belongs, wherein the attribution cloud obtains a mono model and predetermined path information, constructs an access address based on the path information and the base address information, and constructs access parameters based on a preset format, the device information, access authentication information and the mono model; and the attribution cloud sends a target command to the target cloud based on the access address and the access parameters, so that the target cloud performs management control over the shared waiting device.

[0010] In some embodiments of the present application, transmitting the cross-ecosystem shared information across applications to the applications waiting to share includes displaying an application list based on a first application, determining the applications waiting to share selected from the application list, and transmitting the cross-ecosystem shared information by the first application to the applications waiting to share using a cross-application protocol.

[0011] In some embodiments of the present application, transmitting the cross-ecosystem shared information across applications to the application waiting to share includes obtaining information transmission content including the cross-ecosystem shared information based on the first application. ,eye The information transmission content is transmitted by the first application so that the target terminal opens the application waiting to share based on the target protocol and transmits the information transmission content to the application waiting to share. The aforementioned and transmitting the received signal to the target terminal.

[0012] In some embodiments of the present application, transmitting the cross-ecosystem shared information across applications to the application waiting to share includes: obtaining information transmission content including the cross-ecosystem shared information based on the first application, copying the information transmission content to a target location, and when a target object opens the application waiting to share, the application waiting to share obtains the information transmission content from the target location.

[0013] According to one embodiment of the present application, a management and control device for a cross-ecosystem device includes: a generation module that generates cross-ecosystem sharing information for a device waiting to be shared based on a target application, and is used for the device waiting to be shared to belong to the target ecosystem; and a sharing module that transmits the cross-ecosystem sharing information to an application waiting to be shared across applications, and is used for the application waiting to be shared and the device waiting to be shared to belong to different ecosystems, wherein the application waiting to be shared accesses a target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, and the target cloud performs cross-ecosystem management and control for the device waiting to be shared.

[0014] Another embodiment of the present application provides a storage medium, which stores a computer program, which, when executed by a processor of a computer, causes the computer to perform a method according to an embodiment of the present application.

[0015] Another embodiment of the present application provides an electronic device, the electronic device including a memory in which a computer program is stored, and a processor that reads the computer program stored in the memory and performs a method according to an embodiment of the present application. [Effects of the Invention]

[0016] In an embodiment of the present application, cross-ecosystem sharing information of a device waiting to be shared is generated based on a target application, the device waiting to be shared belongs to the target ecosystem, the cross-ecosystem sharing information is transmitted to the application waiting to be shared across applications, the application waiting to be shared and the device waiting to be shared belong to different ecosystems, and the application waiting to be shared accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, and the target cloud performs cross-ecosystem management control on the device waiting to be shared.

[0017] By using the above means, cross-ecosystem shared information is transmitted across applications to the application waiting to share, so that the application waiting to share can access the target cloud of the target ecosystem without negotiation based on the cross-ecosystem shared information, and the target cloud performs cross-ecosystem management control on the device waiting to share, thereby realizing convenient and effective management control of the cross-ecosystem device. [Brief explanation of the drawings]

[0018] In order to more clearly explain the technical solutions in the embodiments of the present application, the drawings necessary for describing the embodiments are briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present application, and those skilled in the art can obtain other drawings based on these drawings without any creative efforts.

[0019] [Figure 1] FIG. 1 is a schematic diagram illustrating a system that can be applied to an embodiment of the present application. [Figure 2] FIG. 1 is a flow chart illustrating a method for managing and controlling cross-ecosystem devices provided in an embodiment of the present application. [Figure 3] FIG. 1 is a block diagram illustrating a management and control device for cross-ecosystem devices provided in an embodiment of the present application. [Figure 4] 1 is a block diagram illustrating an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0020] The technical solutions in the embodiments of the present application will be described below clearly and completely with reference to the accompanying drawings, but it is clear that the described embodiments are only some of the embodiments of the present application and do not represent all of the embodiments, and all other embodiments that can be obtained by those skilled in the art based on the embodiments of the present application without any creative effort fall within the scope of protection of the present application.

[0021] In the following description, specific embodiments of the present application are described with reference to steps and symbols executed by one or more computers, unless otherwise specified. Accordingly, these steps and operations are often referred to as being computer-executed. The computer-executed aspects of the present application include the operation of a computer processing unit as electrical signals of data in a structure. The operations may transform the data and maintain it in the memory system of the computer. The operations may be reconfigured or otherwise modified to alter the operation of the computer in a manner known to those skilled in the art. The data maintained by the data structures are physical locations in the memory and have specific characteristics defined by the data format. However, the concepts of the present application are described above and are not limited thereto, and those skilled in the art should understand that various steps and operations described below may also be implemented in hardware.

[0022] 1 is a schematic diagram illustrating a system 100 that can be applied to an embodiment of the present application. As shown in FIG. 1, the system 100 may include a cloud server 101, a device 102, and a device 103. The device 102 and the device 103 may be any computing device, such as a computer, a mobile phone, a smart watch, or a home appliance device. The cloud server 101 may be a server that provides cloud services.

[0023] In one exemplary embodiment, the device 102 generates cross-ecosystem sharing information of the device waiting to be shared based on a target application, the device waiting to be shared belongs to the target ecosystem, and transmits the cross-ecosystem sharing information to the application waiting to be shared across applications, and the application waiting to be shared and the device waiting to be shared belong to different ecosystems, where the application waiting to be shared accesses a target cloud (e.g., cloud server 101) of the target ecosystem without negotiation based on the cross-ecosystem sharing information, and the target cloud performs cross-ecosystem management control over the device waiting to be shared (e.g., device 103).

[0024] 2 is a flow diagram illustrating a cross-ecosystem device management and control method provided in an embodiment of the present application. The execution entity of this cross-ecosystem device management and control method may be any device, such as the device 102 shown in FIG. 1.

[0025] As shown in FIG. 2, the cross-ecosystem device management and control method may include steps S210 to S220.

[0026] In step S210, cross-ecosystem sharing information of a device waiting to be shared is generated based on the target application, and the device waiting to be shared belongs to the target ecosystem.

[0027] In step S220, the cross-ecosystem shared information is transmitted across applications to the application waiting to share, and the application waiting to share and the device waiting to share belong to different ecosystems, where the application waiting to share accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem shared information, and the target cloud performs cross-ecosystem management control over the device waiting to share.

[0028] The device to be shared belongs to a target ecosystem, such as a target manufacturer or a custom-classified device ecosystem. Cross-ecosystem shared information is information that a device for another ecosystem directly accesses the cloud of the target ecosystem to manage and control the device to be shared. The target application and the device to be shared can belong to the same target ecosystem. After a user selects the device to be shared in the target application, the target application can generate corresponding cross-ecosystem shared information.

[0029] After the target application selects the device waiting to be shared, it is transmitted to the application waiting to be shared by a cross-application means, and the application waiting to be shared and the device waiting to be shared belong to different ecosystems, and the application waiting to be shared can access the target cloud of the target ecosystem corresponding to the device waiting to be shared without negotiation based on the shared information of the cross-ecosystem, and thus the target cloud can perform cross-ecosystem management control over the device waiting to be shared.

[0030] By the above means, based on steps S210 to S220, the cross-ecosystem shared information is transmitted across applications to the application waiting to share, so that the application waiting to share can access the target cloud of the target ecosystem without negotiation based on the cross-ecosystem shared information, and the target cloud performs cross-ecosystem management control on the device waiting to share, thereby realizing convenient and effective management control of the cross-ecosystem device.

[0031] Below, we will explain the specific process of each step when managing and controlling cross-ecosystem devices.

[0032] In step S210, cross-ecosystem sharing information of a device waiting to be shared is generated based on the target application, and the device waiting to be shared belongs to the target ecosystem.

[0033] The device to be shared belongs to a target ecosystem, such as a target manufacturer or a custom-classified device ecosystem. Cross-ecosystem shared information is information that a device for another ecosystem directly accesses the cloud of the target ecosystem to manage and control the device to be shared. The target application and the device to be shared can belong to the same target ecosystem. After a user selects the device to be shared in the target application, the target application can generate corresponding cross-ecosystem shared information.

[0034] Here, the cross-ecosystem sharing information may include the base address information of the cloud of the target ecosystem (e.g., Manufacturer A's cloud base URL), device information of devices waiting to be shared (e.g., a list of unique IDs of devices waiting to be shared, with one ID corresponding to each device waiting to be shared), and access authentication information (which may include a refresh certificate token and an access authentication information token), etc.

[0035] In one embodiment, in step S210, before sending the cross-ecosystem sharing information across applications to the application waiting to share, the method further includes: displaying a permission proposal for information sharing by the target application; receiving response information of the permission proposal; and determining whether to transmit the cross-ecosystem sharing information across applications based on the response information.

[0036] The permission prompt is displayed in the target application to prompt the user to grant permission. For example, the target application may display a permission prompt saying, "This information is very important, please do not casually transmit it to the outside." Here, transmitting it to the outside usually corresponds to granting device information or control rights, etc., and requires user permission. When the user clicks a permission response control, such as "Allow" or "Not Allow," in the display interface, response information is generated, and based on the response information, it is determined whether to transmit the cross-ecosystem shared information across applications. For example, if the response information is "Allow," it is determined to transmit the cross-ecosystem shared information across applications, and conversely, it is determined not to transmit the cross-ecosystem shared information across applications. This can further improve the reliability of management and control of cross-ecosystem devices.

[0037] In one embodiment, in step S210, transmitting the cross-ecosystem shared information across applications to the application waiting to share includes displaying an application list based on the target application, determining the application waiting to share selected from the application list, and transmitting the cross-ecosystem shared information to the application waiting to share by the target application using a cross-application protocol.

[0038] An application list can be displayed in the target application, and at least one application can be displayed in the application list. A user selects an application waiting to be shared from the application list. Then, the target application can transmit cross-ecosystem sharing information to the application waiting to be shared through a pre-established cross-application protocol between the target application and the application waiting to be shared. The cross-application protocol is a protocol for transmitting messages between two types of applications, and the cross-application protocol can convert a message in the target application into a message that can be received by the application waiting to be shared.

[0039] In one example, the application list may list all applications in the system that meet the same standards for user selection. Preferably, all applications are listed based on whether they have declared the same URL scheme, such as an Operational Level Agreement (OLA) (where the URL scheme is a system-provided scheme that can be registered by the application and other programs can open this application via the URL scheme), and / or whether they can open files of the same type, such as applications that have declared application / ola.device.sharepayload, and / or applications that have declared share controls with the same keyword, such as ola.tcl.shareplayload.

[0040] Furthermore, in one example, the target application is located on the same device as the application waiting to be shared, and after the user uses the target application to protocol-transmit cross-ecosystem shared information across applications to the application waiting to be shared, the device can be automatically transitioned to the sharing application by user operation.

[0041] In one embodiment, in step S210, transmitting the cross-ecosystem shared information to the application waiting to share across applications includes obtaining information transmission content including the cross-ecosystem shared information based on the target application. ,eye The target terminal opens the application waiting to share based on the target protocol and transmits the information transmission content to the application waiting to share. The aforementioned and transmitting the received signal to the target terminal.

[0042] The target application can display information transmission content including cross-ecosystem shared information, such as a two-dimensional code, a URL, a character string, etc. The target application can send the information transmission content to the target terminal by email, instant communication software, wireless transmission protocol (e.g., Bluetooth, AirDrop, etc.), etc.

[0043] After receiving the information transmission content, the target terminal can open a sharing application that declares a target protocol corresponding to the information transmission content, and transmit the information transmission content, such as a QR code (registered trademark), a URL, or a character string, to the sharing application.

[0044] In one embodiment, in step S210, transmitting the cross-ecosystem shared information to the application waiting to share across applications includes obtaining information transmission content including the cross-ecosystem shared information based on the target application, copying the information transmission content to a target location, and when the target object opens the application waiting to share, the application waiting to share obtains the information transmission content from the target location.

[0045] The target location may be a clipboard or a specific storage location, etc., and after the target application copies the information transmission content to the target location, when the application waiting to be shared is opened, the information transmission content can be obtained from the target location automatically or manually by the user.

[0046] In step S220, the cross-ecosystem shared information is transmitted across applications to the application waiting to share, and the application waiting to share and the device waiting to share belong to different ecosystems, where the application waiting to share accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem shared information, and the target cloud performs cross-ecosystem management control over the device waiting to share.

[0047] After the target application selects the device waiting to be shared, it is transmitted to the application waiting to be shared by a cross-application means, and the application waiting to be shared and the device waiting to be shared belong to different ecosystems, and the application waiting to be shared can access the target cloud of the target ecosystem corresponding to the device waiting to be shared without negotiation based on the shared information of the cross-ecosystem, and thus the target cloud can perform cross-ecosystem management control over the device waiting to be shared.

[0048] In one embodiment, the cross-ecosystem shared information is the goalThe shared information includes base address information of the target cloud, device information of the device to be shared, and access authentication information. The shared information of the application to be shared accesses the target cloud of the target ecosystem without negotiation based on the shared information of the cross-ecosystem and performs cross-ecosystem management control over the device to be shared by the target cloud includes the application to be shared obtaining a mono model and predetermined path information, constructing an access address based on the path information and the base address information, and constructing access parameters based on a preset format, the device information, access authentication information, and the mono model, and the application to be shared sending a target command to the target cloud based on the access address and the access parameters, so that the target cloud performs management control over the device to be shared.

[0049] The Mono model is a model that abstracts a sharing application into a data model consisting of attributes, services, and events. The predetermined path information is predetermined path information for accessing a target cloud. The sharing application combines base address information and path information to form an access path, and after constructing access parameters based on a preset format, device information, access authentication information, and the Mono model, the sharing application can send a target command to the target cloud based on the access address and access parameters. The target command causes the cloud to perform management control operations on the sharing device, such as obtaining device information, monitoring device events, and refreshing permission control.

[0050] In one embodiment, the cross-ecosystem shared information is the goalThe shared information includes a base address information of the target cloud, device information of the device to be shared, and access authentication information. The shared information is shared by the application to be shared without negotiation to access the target cloud of the target ecosystem without negotiation, and the target cloud performs cross-ecosystem management control on the device to be shared. Yes The method includes transmitting the shared waiting device to an attribution cloud of an ecosystem to which the waiting application belongs, wherein the attribution cloud obtains a mono model and predetermined path information, constructs an access address based on the path information and the base address information, and constructs access parameters based on a preset format, the device information, access authentication information and the mono model; and the attribution cloud sends a target command to the target cloud based on the access address and the access parameters, so that the target cloud performs management control over the shared waiting device.

[0051] The Mono model is a model that abstracts applications to be shared into a data model consisting of attributes, services, and events. The predetermined path information is predetermined path information for accessing a target cloud. The home cloud corresponding to the application to be shared combines base address information and path information to form an access path, and constructs access parameters based on a preset format, device information, access authentication information, and the Mono model. After that, the application to be shared can send a target command to the target cloud based on the access address and access parameters via the home cloud. The target command causes the cloud to perform management control operations on the device to be shared, such as obtaining device information, monitoring device events, and granting permission for refresh.

[0052] In order to better implement the cross-ecosystem device management and control method provided in the embodiments of the present application, the embodiments of the present application further provide a cross-ecosystem device management and control device based on the above cross-ecosystem device management and control method. Here, the meaning of the name is the same as the above cross-ecosystem device management and control method, and for specific embodiments, please refer to the description of the method embodiments. Figure 3 is a block diagram showing the cross-ecosystem device management and control device provided in one embodiment of the present application.

[0053] As shown in FIG. 3, the cross-ecosystem device management control device 300 may include a generating module 310 and a sharing module 320.

[0054] The generation module 310 generates cross-ecosystem sharing information of the device waiting to share based on a target application, and can be used to allow the device waiting to share to belong to the target ecosystem. The sharing module 320 transmits the cross-ecosystem sharing information to the application waiting to share across applications, and can be used to allow the application waiting to share and the device waiting to share to belong to different ecosystems. Here, the application waiting to share accesses the target cloud of the target ecosystem without negotiation based on the cross-ecosystem sharing information, and performs cross-ecosystem management control over the device waiting to share through the target cloud.

[0055] In some embodiments of the present application, the device further includes a presentation content display unit used to display permission presentation content for information sharing by the target application, and a response information receiving unit used to receive response information of the permission presentation content and determine whether to transmit the cross-ecosystem sharing information across applications based on the response information.

[0056] In some embodiments of the present application, the cross-ecosystem shared information is the goalThe shared information includes base address information of the target cloud, device information of the device to be shared, and access authentication information. The shared information of the application to be shared accesses the target cloud of the target ecosystem without negotiation based on the shared information of the cross-ecosystem and performs cross-ecosystem management control over the device to be shared by the target cloud includes the application to be shared obtaining a mono model and predetermined path information, constructing an access address based on the path information and the base address information, and constructing access parameters based on a preset format, the device information, access authentication information, and the mono model, and the application to be shared sending a target command to the target cloud based on the access address and the access parameters, so that the target cloud performs management control over the device to be shared.

[0057] In some embodiments of the present application, the cross-ecosystem shared information is the goal The shared information includes a base address information of the target cloud, device information of the device to be shared, and access authentication information. The shared information is shared by the application to be shared without negotiation to access the target cloud of the target ecosystem without negotiation, and the target cloud performs cross-ecosystem management control on the device to be shared. Yes The method includes transmitting the shared waiting device to an attribution cloud of an ecosystem to which the waiting application belongs, wherein the attribution cloud obtains a mono model and predetermined path information, constructs an access address based on the path information and the base address information, and constructs access parameters based on a preset format, the device information, access authentication information and the mono model; and the attribution cloud sends a target command to the target cloud based on the access address and the access parameters, so that the target cloud performs management control over the shared waiting device.

[0058] In some embodiments of the present application, the sharing module includes a first sharing unit, which is used 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 by the first application to the application to be shared via a cross-application protocol.

[0059] In some embodiments of the present application, the sharing module includes a second sharing unit, and the second sharing unit obtains information transmission content including the cross-ecosystem shared information according to the first application. ,eye The information transmission content is transmitted by the first application so that the target terminal opens the application waiting to share based on the target protocol and transmits the information transmission content to the application waiting to share. The aforementioned and transmitting the received signal to the target terminal.

[0060] In some embodiments of the present application, the sharing module includes a third sharing unit, which is used to obtain information transmission content including the cross-ecosystem shared information based on the first application, copy the information transmission content to a target location, and when a target object opens the sharing-waiting application, the sharing-waiting application obtains the information transmission content from the target location.

[0061] By the above means, based on the cross-ecosystem device management and control device 300, the cross-ecosystem shared information is transmitted across applications to the application waiting to share, so that the application waiting to share can access the target cloud of the target ecosystem without negotiation based on the cross-ecosystem shared information, and the target cloud performs cross-ecosystem management control on the device waiting to share, thereby realizing convenient and effective management control of the cross-ecosystem device.

[0062] It should be noted that although the above detailed description refers to several modules or units of a device for performing operations, such division is not required. In fact, according to embodiments of the present application, the features and functions of two or more of the modules or units described above may be embodied in one module or unit. Conversely, the features and functions of one module or unit described above may be further divided to be embodied by multiple modules or units.

[0063] In addition, the embodiment of the present application further provides an electronic device, which may be a terminal or a server. As shown in Figure 4, Figure 4 is a block diagram showing the configuration of the electronic device provided by the embodiment of the present application. Specifically, it is as follows:

[0064] The electronic device may include components such as one or more core processors 401, one or more computer-readable storage media memories 402, a power supply 403, and an input unit 404. Those skilled in the art should understand that the configuration of the electronic device shown in Figure 4 is not limiting and the electronic device may include more or fewer components than those shown, and some components may be combined or arranged in different components.

[0065] Here, the processor 401 is the control center of the electronic device, and is connected to each part of the entire computer device using various interfaces and wiring. It executes or runs software programs and / or modules stored in the memory 402 and activates data stored in the memory 402 to perform various functions and data processing of the computer device, thereby monitoring the electronic device as a whole. The processor 401 may include one or more core processors. Preferably, the processor 401 can integrate an application processor and a modem processor, where the application processor is mainly used for the operating system, user pages, applications, etc., and the modem processor is mainly used for wireless communication. It can be understood that the modem processor does not have to be integrated into the processor 401.

[0066] The memory 402 can be used to store software programs and modules, and the processor 401 executes the software programs and modules stored in the memory 402 to perform various functional applications and data processing. The memory 402 can mainly include a program storage area and a data storage area, where the program storage area can store an operating system, an application required for at least one function (e.g., an audio playback function, an image playback function, etc.), etc. The data storage area can store data generated in response to the use of the computer device, etc. Furthermore, the memory 402 can include a high-speed random access memory or a nonvolatile memory, such as at least one magnetic disk storage device, a flash memory device, or another nonvolatile solid-state memory device. Accordingly, the memory 402 can include a memory controller to provide access to the memory 402 by the processor 401.

[0067] The electronic device further includes a power supply 403 for supplying power to each component, and preferably, the power supply 403 is logically connected to the processor 401 through a power management system, thereby realizing functions such as charging, discharging, and power consumption management through the power management system. The power supply 403 may include any component such as one or more DC or AC power sources, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, etc.

[0068] The electronic device may also include an input unit 404 for receiving input numeric or textual information and for keyboard, mouse, joystick, optical or trackball signal input for user settings and function control.

[0069] Although not shown, the electronic device may also include a display unit, etc., which will not be described here. Specifically, in this embodiment, the processor 401 in the electronic device loads executable files corresponding to the processes of one or more computer programs into the memory 402 in accordance with the following instructions, and causes the processor 401 to execute the computer programs stored in the memory 402, thereby achieving various functions in the above-described embodiments of the present application. For example, the processor 401 can perform the following steps:

[0070] Cross-ecosystem shared information of the device waiting to share is generated based on a target application, the device waiting to share belongs to the target ecosystem, the cross-ecosystem shared information is transmitted across applications to the application waiting to share, the application waiting to share and the device waiting to share belong to different ecosystems, and the application waiting to share accesses a target cloud of the target ecosystem without negotiation based on the cross-ecosystem shared information, and the target cloud performs cross-ecosystem management control over the device waiting to share.

[0071] In some embodiments of the present application, before transmitting the cross-ecosystem shared information across applications to the application waiting to share, the processor 401 may perform the following: displaying permission proposal content for information sharing by the target application; receiving response information of the permission proposal content; and determining whether to transmit the cross-ecosystem shared information across applications based on the response information.

[0072] In some embodiments of the present application, the cross-ecosystem shared information is the goal The shared information includes base address information of the target cloud, device information of the device to be shared, and access authentication information. When the application to be shared accesses the target cloud of the target ecosystem without negotiation based on the shared information of the cross-ecosystem and performs cross-ecosystem management control over the device to be shared by the target cloud, the processor 401 can execute the following: the application to be shared obtains a mono model and predetermined path information, constructs an access address based on the path information and the base address information, constructs access parameters based on a preset format, the device information, access authentication information, and the mono model, and sends a target command to the target cloud based on the access address and the access parameters, so that the target cloud performs management control over the device to be shared.

[0073] In some embodiments of the present application, the cross-ecosystem shared information is the goal The shared information includes a base address information of the target cloud, device information of the device to be shared, and access authentication information. When the application to be shared accesses the target cloud of the target ecosystem without negotiation based on the shared information of the cross ecosystem and performs cross ecosystem management control on the device to be shared by the target cloud, the processor 401 Yes The home cloud transmits the shared waiting device to an home cloud of an ecosystem to which the waiting application belongs, where the home cloud obtains a mono model and predetermined path information, constructs an access address based on the path information and the base address information, and constructs access parameters based on a preset format, the device information, access authentication information, and the mono model; and the home cloud sends a target command to the target cloud based on the access address and the access parameters, so that the target cloud performs management control over the shared waiting device.

[0074] In some embodiments of the present application, when transmitting the cross-ecosystem shared information across applications to an application waiting to share, the processor 401 may perform the following: displaying an application list based on the first application; determining the application waiting to be shared selected from the application list; and transmitting the cross-ecosystem shared information to the application waiting to be shared by the first application using a cross-application protocol.

[0075] In some embodiments of the present application, when the cross-ecosystem shared information is transmitted across applications to a sharing application, the processor 401 obtains information transmission content including the cross-ecosystem shared information according to the first application. ,eye The information transmission content is transmitted by the first application so that the target terminal opens the application waiting to share based on the target protocol and transmits the information transmission content to the application waiting to share. The aforementioned and transmitting the message to the target terminal.

[0076] In some embodiments of the present application, when the cross-ecosystem shared information is transmitted across applications to a sharing-desired application, the processor 401 may obtain, based on the first application, information transmission content including the cross-ecosystem shared information, copy the information transmission content to a target location, and when the target object opens the sharing-desired application, the sharing-desired application may obtain the information transmission content from the target location.

[0077] As will be understood by those skilled in the art, all or part of the steps in the various methods of the above-described embodiments may be executed by a computer program, or may be executed by a computer program controlling associated hardware, and the computer program may be stored in a computer-readable storage medium and loaded and executed by a processor.

[0078] Therefore, an embodiment of the present application further provides a storage medium having a computer program stored therein, the computer program being capable of being loaded by a processor to perform the steps of any of the methods provided by the embodiment of the present application.

[0079] Here, the storage medium may be a read only memory (ROM), a random access memory (RAM), a magnetic disk, an optical disk, or the like.

[0080] The computer program stored in this storage medium can implement the steps of any of the methods provided in the embodiments of the present application, thereby achieving the effects of the invention realized by the methods provided in the embodiments of the present specification. For detailed descriptions, please refer to the above embodiments, and further description will be omitted here.

[0081] Those skilled in the art will readily contemplate other implementations of the present application after considering this specification and practicing the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that comply with the general principles of the present application and include matters of well-known or customary design in the art that are not disclosed herein.

[0082] It should be noted that the present application is not limited to the embodiments described above and shown in the drawings, and various modifications and variations are possible without departing from the scope of the present application.

Claims

1. Generate cross-ecosystem sharing information of a device waiting to be shared according to a target application, and the device waiting to be shared belongs to the target ecosystem; The cross-ecosystem shared information is transmitted across applications to an application to be shared, and the application to be shared belongs to an ecosystem different from that of the device to be shared; wherein the application waiting to share accesses the target cloud of the target ecosystem without negotiation based on the shared information of the cross-ecosystem, and performs cross-ecosystem management control of the device waiting to share through the target cloud; A method for managing and controlling cross-ecosystem devices.

2. Before transmitting the cross-ecosystem shared information across applications to the application waiting to share, displaying an information sharing permission offer by the target application; receiving response information of the permission proposal content; and determining whether to transmit the cross-ecosystem shared information across applications based on the response information; The cross-ecosystem device management and control method according to claim 1 .

3. The cross-ecosystem sharing information includes base address information of the target cloud, device information of the device waiting to be shared, and access authentication information; The application to be shared accesses the target cloud of the target ecosystem without negotiation based on the shared information of the cross-ecosystem, and performs cross-ecosystem management control on the device to be shared by the target cloud. The application to be shared acquires a mono model and predetermined path information, constructs an access address based on the path information and the base address information, and constructs access parameters based on a preset format, the device information, access authentication information, and the mono model; The sharing application sends a target command to the target cloud based on the access address and the access parameters, so that the target cloud exercises management control over the sharing device. The cross-ecosystem device management and control method according to claim 1 .

4. The cross-ecosystem sharing information includes base address information of the target cloud, device information of the device waiting to be shared, and access authentication information; The application to be shared accesses the target cloud of the target ecosystem without negotiation based on the shared information of the cross-ecosystem, and performs cross-ecosystem management control on the device to be shared by the target cloud. The application to be shared transmits the cross-ecosystem shared information to an attribution cloud of the ecosystem to which the application to be shared belongs, wherein the attribution cloud obtains a mono model and predetermined path information, constructs an access address based on the path information and the base address information, and constructs access parameters based on a preset format, the device information, access authentication information, and the mono model; The home cloud sends a target command to the target cloud based on the access address and the access parameters, so that the target cloud performs management control over the device waiting to be shared. The cross-ecosystem device management and control method according to claim 1 .

5. Transmitting the cross-ecosystem shared information to the application waiting to share across applications includes: displaying an application list based on the target application; determining the application waiting to be shared selected from the application list; The target application transmits the cross-ecosystem shared information to the application waiting to share using a cross-application protocol. The cross-ecosystem device management and control method according to claim 1 .

6. Transmitting the cross-ecosystem shared information to a sharing application across applications includes: Obtaining a message content including the cross-ecosystem shared information according to the target application; Sending the information transmission content to the target terminal by the target application, so that the target terminal opens the application to be shared according to a target protocol and transmits the information transmission content to the application to be shared; The cross-ecosystem device management and control method according to claim 1 .

7. Transmitting the cross-ecosystem shared information to the application waiting to share across applications includes: According to the target application, obtain a message content including the cross-ecosystem shared information, copy the message content to a target location, and when the target object opens the application to be shared, the application to be shared obtains the message content from the target location. The cross-ecosystem device management and control method according to claim 1 .

8. In the application list, all applications in the system that meet the same standards are listed so that the user can select them. The manner of listing applications in the application list is as follows: A method for listing applications that declare the same URL scheme. A method for listing applications that declare they can open files of the same type, and a method for listing applications that have declared shared controls with the same keyword; The cross-ecosystem device management and control method according to claim 5 .

9. transmitting the cross-ecosystem shared information by the target application to the application to be shared using a cross-application protocol; converting the cross-ecosystem shared information in the target application into a message to be received by the application waiting to share through a cross-application protocol, and transmitting the message received by the application waiting to share to the application waiting to share; The cross-ecosystem device management and control method according to claim 5 .

10. determining whether to transmit the cross-ecosystem shared information across applications based on the response information; If the response information is permission, determining to transmit cross-ecosystem shared information across applications; and determining not to transmit cross-ecosystem shared information across applications if the response information is unauthorized. The cross-ecosystem device management and control method according to claim 2 .

11. after displaying an information sharing permission indication by the target application; generating the response information in response to a user clicking an authorization response control on a display interface; The cross-ecosystem device management and control method according to claim 2 .

12. A generating module that generates cross-ecosystem sharing information of a device waiting to be shared according to a target application, and the device waiting to be shared belongs to the target ecosystem; a sharing module that transmits the cross-ecosystem shared information to an application that is requesting sharing across applications, and the application that is requesting sharing and the device that is requesting sharing belong to different ecosystems; wherein the application waiting to share accesses the target cloud of the target ecosystem without negotiation based on the shared information of the cross-ecosystem, and performs cross-ecosystem management control of the device waiting to share through the target cloud; Management and control of cross-ecosystem devices.

13. a proposal display unit for displaying a permission proposal for information sharing by the target application; a response information receiving unit for receiving response information of the permission proposal content, and determining whether to transmit the cross-ecosystem shared information across applications based on the response information; The cross-ecosystem device management control device according to claim 12 .

14. The cross-ecosystem sharing information includes base address information of the target cloud, device information of the device waiting to be shared, and access authentication information; The application to be shared accesses the target cloud of the target ecosystem without negotiation based on the shared information of the cross-ecosystem, and performs cross-ecosystem management control on the device to be shared by the target cloud. The application to be shared acquires a mono model and predetermined path information, constructs an access address based on the path information and the base address information, and constructs access parameters based on a preset format, the device information, access authentication information, and the mono model; The sharing application sends a target command to the target cloud based on the access address and the access parameters, so that the target cloud exercises management control over the sharing device. The cross-ecosystem device management control device according to claim 12 .

15. The cross-ecosystem sharing information includes base address information of the target cloud, device information of the device waiting to be shared, and access authentication information; The application to be shared accesses the target cloud of the target ecosystem without negotiation based on the shared information of the cross-ecosystem, and performs cross-ecosystem management control on the device to be shared by the target cloud. The application to be shared transmits the cross-ecosystem shared information to an attribution cloud of the ecosystem to which the application to be shared belongs, wherein the attribution cloud obtains a mono model and predetermined path information, constructs an access address based on the path information and the base address information, and constructs access parameters based on a preset format, the device information, access authentication information, and the mono model; The home cloud sends a target command to the target cloud based on the access address and the access parameters, so that the target cloud performs management control over the device waiting to be shared. The cross-ecosystem device management control device according to claim 12 .

16. The sharing module includes a first sharing unit, which is used to: display an application list based on a first application; determine the application to be shared selected from the application list; and transmit the cross-ecosystem sharing information by the first application to the application to be shared using a cross-application protocol. The cross-ecosystem device management control device according to claim 12 .

17. The sharing module includes a second sharing unit, and the second sharing unit is used for: obtaining, based on a first application, information transmission content including the cross-ecosystem shared information; and sending, by the first application, the information transmission content to the target terminal, so that the target terminal opens the application to be shared based on a target protocol and transmits the information transmission content to the application to be shared. The cross-ecosystem device management control device according to claim 12 .

18. The sharing module includes a third sharing unit, which is used for obtaining, based on the first application, information transmission content including the cross-ecosystem shared information, and copying the information transmission content to a target location, so that when a target object opens the sharing application, the sharing application obtains the information transmission content from the target location. The cross-ecosystem device management control device according to claim 12 .

19. a computer program stored in the computer, the computer program being executed by a processor of the computer to cause the computer to perform the cross-ecosystem device management and control method according to any one of claims 1 to 11; storage medium.

20. A memory for storing a computer program, and a processor for reading the computer program stored in the memory and implementing the cross-ecosystem device management and control method according to any one of claims 1 to 11. Electronic devices.

Images