CN116016639A - Link management method, device and system - Google Patents

Link management method, device and system Download PDF

Info

Publication number
CN116016639A
CN116016639A CN202211717618.0A CN202211717618A CN116016639A CN 116016639 A CN116016639 A CN 116016639A CN 202211717618 A CN202211717618 A CN 202211717618A CN 116016639 A CN116016639 A CN 116016639A
Authority
CN
China
Prior art keywords
equipment
connection state
cloud server
state information
link
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211717618.0A
Other languages
Chinese (zh)
Inventor
孙立欢
许义星
赵建华
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Grandstream Networks Technologies Co ltd
Original Assignee
Shenzhen Grandstream Networks Technologies Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Grandstream Networks Technologies Co ltd filed Critical Shenzhen Grandstream Networks Technologies Co ltd
Priority to CN202211717618.0A priority Critical patent/CN116016639A/en
Publication of CN116016639A publication Critical patent/CN116016639A/en
Pending legal-status Critical Current

Links

Images

Abstract

The application provides a link management method, a device and a system, which are applied to a client, and are used for firstly acquiring equipment connection state information and cloud server connection state information, initiating an equipment list acquisition request to the cloud server to acquire an equipment list when the equipment connection state information and the cloud server connection state information meet normal connection conditions, extracting current management equipment information from the equipment list, and selecting a cloud link communication mode or a local link communication mode to communicate with target equipment based on the current management equipment information. The method comprises the steps that based on equipment connection state information and cloud server connection state information, current management equipment information can be obtained, an optimal communication mode can be determined according to the current management equipment information, and communication is carried out with target equipment based on the communication mode, so that a client can accurately select an appropriate equipment management mode according to actual application conditions, normal management of the target equipment by the client can be guaranteed, and equipment management efficiency is improved.

Description

Link management method, device and system
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a link management method, device, and system.
Background
Along with the continuous progress of the technology level, the internet of things technology has also been rapidly developed, and the meaning of the internet of things technology is that devices are connected with a network, so that the devices can communicate through an information transmission medium, people can effectively manage life and production activities more intelligently and conveniently, and therefore, the internet of things technology is widely applied to various fields.
The current methods for managing devices generally include a direct method (where a client directly communicates with a device) and an indirect method (where a client transmits communication data to a cloud server to forward the communication data to the device through the cloud server), however, when an abnormality occurs in the cloud server or the device (for example, when a network abnormality/load of the cloud server is large, when a configuration of the device is abnormal), since the client cannot accurately select an appropriate device management method according to the actual situation, a situation where the client cannot normally manage the device easily occurs, resulting in a low device management efficiency.
Disclosure of Invention
The application provides a link management method, device and system, which are used for solving the technical problem of low management efficiency of the current equipment.
In order to solve the technical problems, the application provides the following technical scheme:
The application provides a link management method, which is applied to a client, and comprises the following steps:
acquiring equipment connection state information and cloud server connection state information; the device connection state information characterizes the connection state between the client and the target device, and the cloud server connection state information characterizes the connection state between the client and the cloud server;
when the equipment connection state information and the cloud server connection state information meet normal connection conditions, initiating an equipment list acquisition request to the cloud server;
receiving an equipment list returned by the cloud server based on the equipment list acquisition request, and extracting current management equipment information from the equipment list;
and selecting a cloud link communication mode or a local link communication mode to communicate with the target equipment based on the current management equipment information.
Before the step of obtaining the device connection state information and the cloud server connection state information, the method further comprises the following steps:
creating a local link and Yun Lianlu; the local link comprises a link used for connecting the client and the target equipment, and the cloud link comprises a link used for connecting the client and a cloud server.
The step of obtaining the equipment connection state information and the cloud server connection state information comprises the following steps:
initiating a device connection request to the target device based on the local link, and acquiring device connection state information returned by the target device based on the device connection request;
logging in to the cloud server to initiate a cloud server connection request to the cloud server based on the cloud link, and acquiring cloud server connection state information returned by the cloud server based on the cloud server connection request.
When the device connection state information and the cloud server connection state information both meet normal connection conditions, initiating a device list acquisition request to the cloud server, including:
when the equipment connection state information indicates that the client is normally connected with the target equipment, and the cloud server connection state information indicates that the client is normally connected with the cloud server, determining that the equipment connection state information and the cloud server connection state information both meet normal connection conditions, and initiating an equipment list acquisition request to the cloud server.
The step of receiving the device list returned by the cloud server based on the device list acquisition request and extracting the current management device information from the device list comprises the following steps:
Receiving an equipment list returned by the cloud server based on the equipment list acquisition request; wherein, the mapping relation between each device and each device information is stored in the device list;
determining a current management device from the device list; the current management equipment comprises equipment currently in a cloud server management state;
determining a current management equipment identification code based on the mapping relation, and taking the current management equipment identification code as the current management equipment information; wherein the current management device identification code comprises a unique identification code of the current management device.
After the step of receiving the device list returned by the cloud server based on the device list acquisition request and extracting the current management device information from the device list, the method further comprises the following steps:
comparing the current management equipment identification code with a target equipment identification code to obtain a comparison result; wherein the target device identification code comprises a unique identification code of the target device.
The step of selecting a cloud link communication mode or a local link communication mode to communicate with the target device based on the current management device information includes:
When the current management equipment information meets cloud link communication conditions, communicating with the target equipment based on the cloud link;
and when the current management device information meets the communication condition of a local link, communicating with the target device based on the local link.
When the current management device information meets cloud link communication conditions, the step of communicating with the target device based on a cloud link comprises the following steps:
when the comparison result shows that the identification code of the current management device is different from the identification code of the target device, determining that the information of the current management device meets cloud link communication conditions;
and communicating with the target device based on the cloud link.
The step of communicating with the target device based on the local link when the current management device information meets the communication condition of the local link includes:
when the comparison result shows that the current management equipment identification code is the same as the target equipment identification code, determining that the current management equipment information meets the local link communication condition;
and communicating with the target device based on the local link.
The embodiment of the application also provides a link management device, which is applied to the client, and comprises:
the acquisition module is used for acquiring equipment connection state information and cloud server connection state information; the device connection state information characterizes the connection state between the client and the target device, and the cloud server connection state information characterizes the connection state between the client and the cloud server;
the request initiating module is used for initiating a device list acquisition request to the cloud server when the device connection state information and the cloud server connection state information meet normal connection conditions;
the receiving module is used for receiving an equipment list returned by the cloud server based on the equipment list acquisition request and extracting current management equipment information from the equipment list;
and the communication module is used for selecting a cloud link communication mode or a local link communication mode to communicate with the target equipment based on the current management equipment information.
The embodiment of the application also provides a link management system which comprises a client, a cloud server and target equipment;
the client is used for acquiring equipment connection state information and cloud service end connection state information, initiating an equipment list acquisition request to the cloud service end when the equipment connection state information and the cloud service end connection state information meet normal connection conditions, receiving an equipment list returned by the cloud service end based on the equipment list acquisition request, extracting current management equipment information from the equipment list, and selecting a cloud link communication mode or a local link communication mode to communicate with the target equipment based on the current management equipment information;
The cloud server is used for receiving the equipment list acquisition request initiated by the client and sending the equipment list to the client based on the equipment list acquisition request;
the target device is configured to communicate with the client based on the local link communication manner or the cloud link communication manner.
The beneficial effects are that: the application provides a link management method, a device and a system, wherein the current management equipment information can be acquired based on the equipment connection state information and the cloud server connection state information, a proper communication mode can be determined according to the current management equipment information, and the client can accurately select a proper equipment management mode according to actual application conditions by communicating with target equipment based on the determined communication mode, so that the client can normally manage the target equipment in real time, and the equipment management efficiency is improved.
Drawings
Technical solutions and other advantageous effects of the present application will be made apparent from the following detailed description of specific embodiments of the present application with reference to the accompanying drawings.
Fig. 1 is a flow chart of a link management method according to an embodiment of the present application.
Fig. 2 is a schematic structural diagram of a link management device according to an embodiment of the present application.
Fig. 3 is a schematic diagram of a link management system according to an embodiment of the present application.
Fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Fig. 5 is another schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
The embodiment of the application provides a link management method, a device and a system.
As shown in fig. 1, fig. 1 is a flow chart of a link management method provided in an embodiment of the present application, where the link management method is applied to a client. The specific flow can be as follows:
s101, acquiring equipment connection state information and cloud server connection state information, wherein the equipment connection state information represents the connection state between a client and target equipment, and the cloud server connection state information represents the connection state between the client and the cloud server.
The target equipment comprises Internet of things equipment with network access capability and data transmission capability, the client comprises a program for providing local service for users, and the cloud service end comprises a service platform for providing comprehensive service capability for various Internet users.
Specifically, the internet of things devices (e.g., intelligent home devices, intelligent wearable devices, etc.) have entered into production and life of people, and the internet of things devices can communicate with each other to automatically perform corresponding tasks, so that users can realize efficient management of life and production activities through control of the internet of things devices. In order to ensure that the internet of things equipment can normally operate, the client is required to manage the internet of things equipment, and currently, two equipment management modes are generally adopted: 1. the client side directly communicates with the Internet of things equipment to carry out local management on the Internet of things equipment; 2. the client communicates with the cloud server to indirectly perform remote management on the internet of things device through the cloud server, however, when the cloud server or the internet of things device is abnormal (for example, when the cloud server network is abnormal/the load is large and the device configuration is abnormal), the client cannot accurately select a proper device management mode according to actual conditions, so that the client cannot normally manage the internet of things device.
In order to avoid the occurrence of the above situation, in this embodiment, the connection state between the client and the target device and the connection state between the client and the cloud server are known by acquiring the device connection state information and the cloud server connection state information, so that a device management mode most suitable for the selection of the client is determined according to the two connection states, and therefore the client is ensured to be able to normally manage the target device in real time.
For example, when the connection state between the client represented by the device connection state information and the target device is normal connection, and the connection state between the client represented by the cloud server connection state information and the cloud server is abnormal, the client selects a local management mode to perform device management (i.e., directly communicates with the target device); when the connection state between the client represented by the cloud server connection state information and the cloud server is normal in connection and the connection state between the client represented by the device connection state information and the device is abnormal, the client selects a remote management mode to perform device management (namely, indirectly communicates with the target device through the cloud server); when the connection state between the client and the device, represented by the device connection state information, and the connection state between the client and the cloud server, represented by the cloud server connection state information, are normal, further judgment needs to be performed to determine the most suitable device management mode.
Specifically, in this embodiment, a local link (a link for connecting a client and a target device) and Yun Lianlu (a link for connecting a client and a cloud server) are created in advance, then a device connection request is initiated to the target device based on the local link and device connection state information returned by the target device based on the device connection request is acquired, and then the client logs in to the cloud server to initiate a cloud server connection request to the cloud server based on the cloud link and cloud server connection state information returned by the cloud server based on the cloud server connection request is acquired.
Optionally, since the WebSocket protocol has the characteristic of keeping the two connected parties in a long connection state, the WebSocket protocol can effectively improve connection efficiency, and in order to ensure connection efficiency between the client and the target device, and between the client and the cloud server, in this embodiment, a local link and a cloud link are created based on the WebSocket protocol.
Further, in order to ensure continuity of the device management work, it is necessary to avoid as much as possible that the device management cannot be performed normally due to abnormal connection (including abnormal connection between the client and the target device, abnormal connection between the client and the cloud server, and abnormal connection between the client and the target device and abnormal connection between the client and the cloud server) so that, in the practical application process, multiple connection may be tried to ensure that the connection between the client and the target device and between the client and the cloud server is normal as much as possible, and in addition, after the device connection status information and the cloud server connection status information are obtained, links of both successful connection parties (for example, successful connection between the client and the target device and successful connection between the client and the cloud server) are stored in the connection pool.
S102, when the equipment connection state information and the cloud server connection state information meet normal connection conditions, initiating an equipment list acquisition request to the cloud server.
The normal connection condition is a basis for judging whether the client is successfully connected with the target device/the client and the cloud server, and the device list acquisition request comprises a message for requesting to acquire the device list.
Specifically, as described above, when the connection state between the client and the device and the connection state between the client and the cloud service end are normal, further judgment is required to determine the most suitable device management mode, for this purpose, in this embodiment, when the device connection state information indicates that the client is normally connected with the target device and the cloud service end connection state information indicates that the client is normally connected with the cloud service end, it is determined that the device connection state information and the cloud service end connection state information both satisfy the normal connection condition, and at the same time, the client initiates a device list acquisition request to the cloud service end, and initiates an initialization request to the target device to request to acquire the device information of the target device, so that the most suitable device management mode is determined according to the device list and the device information of the target device.
S103, receiving a device list returned by the cloud service end based on the device list acquisition request, and extracting current management device information from the device list.
The device list stores all devices bound to the cloud server and mapping relations among device information of the devices, and the current management device comprises devices currently in a cloud server management state and is used for identifying the current management device. The cloud server stores a device list with all devices (target devices are contained in the device list) and corresponding device information which are bound with the cloud server, and after the cloud server receives a device list acquisition request initiated by a client, the device list is sent to the client based on the device list acquisition request, so that the client can extract current management device information corresponding to current management devices currently managed by the cloud server after receiving the device list. Optionally, in the actual application process, one of all the devices bound to the cloud service end may be selected as the current management device by default.
Specifically, in this embodiment, firstly, a device list returned by a cloud service end based on a device list acquisition request is received, then a current management device currently in a management state of the cloud service end is determined from the device list, and a current management device identification code is determined based on a mapping relationship between the device and device information, so that the current management device identification code is used as current management device information. Optionally, the current management device identification code includes a UUID (Universally Unique Identifier, unique identification code) of the current management device.
For example, the device list stores: when the client receives the device list, it determines that the current management device is the device a, and therefore determines that the current management device information is a11.
Further, after the current management device identification code is obtained, the current management device identification code is compared with the target device identification code (i.e. the device information of the target device) to obtain a comparison result, so that the comparison result is used as a selection basis of a device management mode. Optionally, the target device identification code includes a UUID of the target device.
S104, selecting a cloud link communication mode or a local link communication mode to communicate with the target device based on the information of the current management device.
When the current management equipment information meets cloud link communication conditions, communication is carried out with the target equipment based on a cloud link; and when the current management device information meets the communication condition of the local link, communicating with the target device based on the local link.
Specifically, the cloud link communication condition is a basis for judging whether the client and the target device can use the cloud link to communicate, and the local link communication condition is a basis for judging whether the client and the target device can use the local link to communicate.
Further, in this embodiment, if all links of both the normal connected parties are queried from the connection pool, if only the local link/cloud link (i.e. only the client is successfully connected with the target device/client and the cloud service end) is in the connection pool, the client directly communicates with the target device based on the link, and if the local link and the cloud link exist in the connection pool at the same time, further analysis is performed based on the comparison result:
when the comparison result shows that the identification code of the current management device is different from the identification code of the target device, the target device is not currently managed by the cloud server, namely the target device possibly has the problems of abnormal configuration and the like, so that the client cannot directly communicate with the target device, the current management device information is determined to meet the cloud link communication condition, communication is carried out with the target device based on the cloud link, namely the subsequent initiated instructions of the client are indirectly forwarded to the target device (namely remote management) through the cloud server.
When the comparison result shows that the identification code of the current management device is the same as the identification code of the target device, the cloud service end is managing the target device at the moment, and the situation that the load capacity and the flow consumption are large is indicated, so that the management resource of the cloud service end is avoided being occupied for ensuring the device management efficiency, the current management device information is determined to meet the local link communication condition, and the communication is carried out with the target device based on the local link, namely, the subsequent initiated instructions of the client end are directly sent to the target device (namely, the local management).
Further, because the client and the target device, and the client and the cloud server are in a long connection state, communication with the target device can be quickly performed based on the link after the optimal link is determined, so that the target device is managed, and the device management efficiency is effectively improved.
As can be seen from the foregoing, the link management method provided by the present application is applied to a client, and is firstly used for obtaining device connection state information for representing a connection state between the client and a target device, and cloud service end connection state information for representing a connection state between the client and a cloud service end, when the device connection state information and the cloud service end connection state information both meet normal connection conditions, a device list obtaining request is initiated to the cloud service end, then a device list returned by the cloud service end based on the device list obtaining request is received, and current management device information is extracted from the device list, so that a cloud link communication mode or a local link communication mode is selected to communicate with the target device based on the current management device information. The method comprises the steps that based on equipment connection state information and cloud server connection state information, current management equipment information can be obtained, a proper communication mode can be determined according to the current management equipment information, and communication is carried out with target equipment based on the determined communication mode, so that a client can accurately select a proper equipment management mode according to actual application conditions, normal management of the target equipment can be guaranteed to be carried out in real time by the client, and equipment management efficiency is improved.
According to the method described in the above embodiment, the present embodiment will be further described from the viewpoint of the link management apparatus.
Referring to fig. 2, fig. 2 specifically illustrates a link management device provided in an embodiment of the present application, where the link management device is applied to a client, the link management device may include: the device comprises an acquisition module 10, a request initiation module 20, a receiving module 30 and a communication module 40, wherein:
(1) Acquisition Module 10
The acquisition module 10 acquires equipment connection state information and cloud server connection state information; the device connection state information characterizes the connection state between the client and the target device, and the cloud server connection state information characterizes the connection state between the client and the cloud server.
The acquiring module 10 is specifically configured to:
initiating a device connection request to a target device based on a local link, and acquiring device connection state information returned by the target device based on the device connection request;
logging in to the cloud server to initiate a cloud server connection request to the cloud server based on the cloud link, and acquiring cloud server connection state information returned by the cloud server based on the cloud server connection request.
(2) Request initiating module 20
The request initiating module 20 is configured to initiate a device list obtaining request to the cloud server when the device connection status information and the cloud server connection status information both satisfy the normal connection condition.
The request initiation module 20 is specifically configured to:
when the equipment connection state information indicates that the client is normally connected with the target equipment and the cloud server connection state information indicates that the client is normally connected with the cloud server, the equipment connection state information and the cloud server connection state information are determined to meet normal connection conditions, and an equipment list acquisition request is initiated to the cloud server.
(3) Receiving module 30
And the receiving module 30 is used for receiving the equipment list returned by the cloud service end based on the equipment list acquisition request and extracting the current management equipment information from the equipment list.
The receiving module 30 is specifically configured to:
receiving a device list returned by the cloud service end based on the device list acquisition request; wherein, the mapping relation between each device and each device information is stored in the device list;
determining a current management device from a device list; the current management equipment comprises equipment currently in a cloud server management state;
determining a current management equipment identification code based on the mapping relation, and taking the current management equipment identification code as current management equipment information; wherein the current management device identification code comprises a unique identification code of the current management device.
(4) Communication module 40
The communication module 40 is configured to select a cloud link communication mode or a local link communication mode to communicate with the target device based on the current management device information.
The communication module 40 is specifically configured to:
when the current management equipment information meets cloud link communication conditions, communication is carried out with target equipment based on a cloud link;
and when the current management device information meets the communication condition of the local link, communicating with the target device based on the local link.
Specifically, the communication module 40 is further configured to:
when the comparison result shows that the identification code of the current management device is different from the identification code of the target device, determining that the information of the current management device meets the cloud link communication condition;
communication with the target device is based on the cloud link.
Further, the communication module 40 is further configured to:
when the comparison result shows that the identification code of the current management device is the same as the identification code of the target device, determining that the current management device information meets the local link communication condition;
communication with the target device is based on the local link.
In the implementation, each module may be implemented as an independent entity, or may be combined arbitrarily, and implemented as the same entity or several entities, and the implementation of each module may be referred to the foregoing method embodiment, which is not described herein again.
As can be seen from the foregoing, the link management apparatus provided in the present application is applied to a client, and first, device connection state information for characterizing a connection state between the client and a target device and cloud service end connection state information for characterizing a connection state between the client and the cloud service end are acquired through the acquisition module 10, when the device connection state information and the cloud service end connection state information both satisfy normal connection conditions, a device list acquisition request is initiated to the cloud service end through the request initiation module 20, then, a device list returned by the cloud service end based on the device list acquisition request is received through the receiving module 30, and current management device information is extracted from the device list, so that a cloud link communication mode or a local link communication mode is selected to communicate with the target device through the communication module 40 based on the current management device information.
The method comprises the steps that based on equipment connection state information and cloud server connection state information, current management equipment information can be obtained, a proper communication mode can be determined according to the current management equipment information, and communication is carried out with target equipment based on the determined communication mode, so that a client can accurately select a proper equipment management mode according to actual application conditions, normal management of the target equipment can be guaranteed to be carried out in real time by the client, and equipment management efficiency is improved.
Correspondingly, the embodiment of the invention also provides a link management system which comprises a client, a cloud server and target equipment. Specifically, as shown in fig. 3, the link management system includes a client 31, a cloud server 32, and a target device 33, and the client 31 first performs step S301: acquiring the equipment connection state information and the cloud server connection state information, and executing step S302 when the equipment connection state information and the cloud server connection state information both meet the normal connection conditions: initiating a device list acquisition request to the cloud server 32, and then executing step S303 by the cloud server 32: receiving the device list acquisition request, and transmitting the device list to the client 31 based on the device list acquisition request, and then the client 31 performs step S304: extracting current management device information from the device list, and executing step S305 if the current management device information satisfies the cloud link communication condition: based on the cloud link communication mode, the communication with the target device 33 is performed, and if the current management device information satisfies the local link communication condition, step S306 is performed: and communicates with the target device 33 based on the local link communication scheme.
Since the link management system may include any of the link management devices provided by the embodiments of the present invention, the beneficial effects that any of the link management devices provided by the embodiments of the present invention can achieve are detailed in the previous embodiments and are not described herein.
In addition, the embodiment of the present application further provides an electronic device with a client, where the functions of the client are as in the foregoing embodiment, and the electronic device may be a smart phone or a computer, which is not described herein. As shown in fig. 4, the electronic device 400 includes a processor 401, a memory 402. The processor 401 is electrically connected to the memory 402.
The processor 401 is a control center of the electronic device 400, connects various parts of the entire electronic device using various interfaces and lines, and performs various functions of the electronic device and processes data by running or loading application programs stored in the memory 402 and calling data stored in the memory 402, thereby performing overall monitoring of the electronic device.
In this embodiment, the processor 401 in the electronic device 400 loads the instructions corresponding to the processes of one or more application programs into the memory 402 according to the following steps, and the processor 401 executes the application programs stored in the memory 402, so as to implement various functions:
acquiring equipment connection state information and cloud server connection state information; the device connection state information characterizes the connection state between the client and the target device, and the cloud server connection state information characterizes the connection state between the client and the cloud server;
When the equipment connection state information and the cloud server connection state information meet the normal connection conditions, initiating an equipment list acquisition request to the cloud server;
receiving an equipment list returned by the cloud service end based on the equipment list acquisition request, and extracting current management equipment information from the equipment list;
and selecting a cloud link communication mode or a local link communication mode to communicate with the target device based on the current management device information.
Fig. 5 shows a specific block diagram of an electronic device according to an embodiment of the present invention, which may be used to implement the link management method provided in the above embodiment.
The RF circuit 510 is configured to receive and transmit electromagnetic waves, and to perform mutual conversion between the electromagnetic waves and the electrical signals, thereby communicating with a communication network or other devices. RF circuitry 510 may include various existing circuit elements for performing these functions, such as an antenna, a radio frequency transceiver, a digital signal processor, an encryption/decryption chip, a Subscriber Identity Module (SIM) card, memory, and the like. The RF circuitry 510 may communicate with various networks such as the internet, intranets, wireless networks or with other devices via wireless networks. The wireless network may include a cellular telephone network, a wireless local area network, or a metropolitan area network. The wireless network may use various communication standards, protocols, and technologies including, but not limited to, global system for mobile communications (Global System for Mobile Communication, GSM), enhanced mobile communications technology (Enhanced Data GSM Environment, EDGE), wideband code division multiple access technology (Wideband Code Division Multiple Access, WCDMA), code division multiple access technology (Code Division Access, CDMA), time division multiple access technology (Time Division Multiple Access, TDMA), wireless fidelity technology (Wireless Fidelity, wi-Fi) (e.g., american society of electrical and electronic engineers standard IEEE802.11a, IEEE 802.11.11 b, IEEE802.11g, and/or IEEE802.11 n), internet telephony (Voice over Internet Protocol, voIP), worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, wi-Max), other protocols for mail, instant messaging, and short messaging, and any other suitable communication protocols, even those not currently developed.
The memory 520 may be used to store software programs and modules, and the processor 580 performs various functional applications and data processing, i.e., implements functions for storing 5G capability information, by executing the software programs and modules stored in the memory 520. Memory 520 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, memory 520 may further include memory located remotely from processor 580, which may be connected to electronic device 500 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input unit 530 may be used to receive input numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control. In particular, the input unit 530 may include a touch-sensitive surface 531 and other input devices 532. The touch-sensitive surface 531, also referred to as a touch display screen or touch pad, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch-sensitive surface 531 or thereabout by using any suitable object or accessory such as a finger, stylus, etc.), and actuate the corresponding connection means according to a pre-set program. Alternatively, the touch-sensitive surface 531 may comprise two parts, a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device and converts it into touch point coordinates, which are then sent to the processor 580, and can receive commands from the processor 580 and execute them. In addition, the touch-sensitive surface 531 may be implemented in a variety of types, such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch-sensitive surface 531, the input unit 530 may also comprise other input devices 532. In particular, other input devices 532 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, mouse, joystick, etc.
The display unit 540 may be used to display information entered by a user or provided to a user as well as various graphical user interfaces of the electronic device 500, which may be composed of graphics, text, icons, video, and any combination thereof. The display unit 540 may include a display panel 541, and alternatively, the display panel 541 may be configured in the form of an LCD (Liquid Crystal Display ), an OLED (Organic Light-Emitting Diode), or the like. Further, the touch-sensitive surface 531 may overlay the display panel 541, and when the touch-sensitive surface 531 detects a touch operation thereon or thereabout, the touch-sensitive surface 531 is transferred to the processor 580 to determine the type of touch event, and the processor 580 then provides a corresponding visual output on the display panel 541 in accordance with the type of touch event. Although in fig. 5 the touch-sensitive surface 531 and the display panel 541 are implemented as two separate components for input and output functions, in some embodiments the touch-sensitive surface 531 may be integrated with the display panel 541 for input and output functions.
The electronic device 500 may also include at least one sensor 550, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor that may adjust the brightness of the display panel 541 according to the brightness of ambient light, and a proximity sensor that may turn off the display panel 541 and/or the backlight when the electronic device 500 moves to the ear. As one of the motion sensors, the gravity acceleration sensor can detect the acceleration in all directions (generally three axes), and can detect the gravity and the direction when the mobile phone is stationary, and can be used for applications of recognizing the gesture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometer and knocking), and the like; other sensors such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc. that may also be configured with the electronic device 500 are not described in detail herein.
Audio circuitry 560, speakers 561, and microphone 562 may provide an audio interface between the user and the electronic device 500. The audio circuit 560 may transmit the received electrical signal converted from audio data to the speaker 561, and the electrical signal is converted into a sound signal by the speaker 561 and output; on the other hand, microphone 562 converts the collected sound signal into an electrical signal, which is received by audio circuit 560 and converted into audio data, which is processed by audio data output processor 580 for transmission to, for example, another terminal via RF circuit 510, or which is output to memory 520 for further processing. Audio circuitry 560 may also include an ear bud jack to provide communication of the peripheral headphones with electronic device 500.
The electronic device 500 may facilitate user email, web browsing, streaming media access, etc. via a transmission module 570 (e.g., wi-Fi module) that provides wireless broadband internet access to the user. Although fig. 5 shows the transmission module 570, it is understood that it does not belong to the necessary constitution of the electronic device 500, and can be omitted entirely as required within the scope not changing the essence of the invention.
Processor 580 is a control center of electronic device 500 that utilizes various interfaces and lines to connect the various portions of the overall handset, perform various functions of electronic device 500 and process data by running or executing software programs and/or modules stored in memory 520, and invoking data stored in memory 520. Optionally, processor 580 may include one or more processing cores; in some embodiments, processor 580 may integrate an application processor that primarily processes operating systems, user interfaces, applications, etc., with a modem processor that primarily processes wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 580.
The electronic device 500 also includes a power supply 590 (e.g., a battery) that provides power to the various components, and in some embodiments, may be logically coupled to the processor 580 via a power management system to perform functions such as managing charging, discharging, and power consumption via the power management system. Power supply 590 may also include one or more of any of a direct current or alternating current power supply, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.
Although not shown, the electronic device 500 may further include a camera (e.g., front camera, rear camera), a bluetooth module, etc., which will not be described in detail herein. In particular, in this embodiment, the display unit of the electronic device is a touch screen display, the electronic device further includes a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for:
acquiring equipment connection state information and cloud server connection state information; the device connection state information characterizes the connection state between the client and the target device, and the cloud server connection state information characterizes the connection state between the client and the cloud server;
When the equipment connection state information and the cloud server connection state information meet the normal connection conditions, initiating an equipment list acquisition request to the cloud server;
receiving an equipment list returned by the cloud service end based on the equipment list acquisition request, and extracting current management equipment information from the equipment list;
and selecting a cloud link communication mode or a local link communication mode to communicate with the target device based on the current management device information.
In the implementation, each module may be implemented as an independent entity, or may be combined arbitrarily, and implemented as the same entity or several entities, and the implementation of each module may be referred to the foregoing method embodiment, which is not described herein again.
Those of ordinary skill in the art will appreciate that all or a portion of the steps of the various methods of the above embodiments may be performed by instructions, or by instructions controlling associated hardware, which may be stored in a computer-readable storage medium and loaded and executed by a processor. To this end, an embodiment of the present invention provides a storage medium having stored therein a plurality of instructions capable of being loaded by a processor to perform the steps of any of the link management methods provided by the embodiments of the present invention.
Wherein the storage medium may include: read Only Memory (ROM), random access Memory (RAM, random Access Memory), magnetic or optical disk, and the like.
The steps in any link management method provided by the embodiment of the present invention can be executed by the instructions stored in the storage medium, so that the beneficial effects that any link management method provided by the embodiment of the present invention can be achieved, and detailed descriptions of the previous embodiments are omitted herein.
The specific implementation of each operation above may be referred to the previous embodiments, and will not be described herein.
In summary, although the present application has been described with reference to the preferred embodiments, the preferred embodiments are not intended to limit the application, and those skilled in the art can make various modifications and adaptations without departing from the spirit and scope of the application, and the scope of the application is therefore defined by the claims.

Claims (11)

1. A link management method, applied to a client, comprising:
acquiring equipment connection state information and cloud server connection state information; the device connection state information characterizes the connection state between the client and the target device, and the cloud server connection state information characterizes the connection state between the client and the cloud server;
When the equipment connection state information and the cloud server connection state information meet normal connection conditions, initiating an equipment list acquisition request to the cloud server;
receiving an equipment list returned by the cloud server based on the equipment list acquisition request, and extracting current management equipment information from the equipment list;
and selecting a cloud link communication mode or a local link communication mode to communicate with the target equipment based on the current management equipment information.
2. The link management method according to claim 1, further comprising, before the step of acquiring the device connection state information and the cloud service connection state information:
creating a local link and Yun Lianlu; the local link comprises a link used for connecting the client and the target equipment, and the cloud link comprises a link used for connecting the client and a cloud server.
3. The link management method according to claim 2, wherein the step of acquiring the device connection state information and the cloud service connection state information includes:
initiating a device connection request to the target device based on the local link, and acquiring device connection state information returned by the target device based on the device connection request;
Logging in to the cloud server to initiate a cloud server connection request to the cloud server based on the cloud link, and acquiring cloud server connection state information returned by the cloud server based on the cloud server connection request.
4. The link management method according to claim 3, wherein the step of initiating a device list acquisition request to the cloud server when the device connection status information and the cloud server connection status information both satisfy a normal connection condition, comprises:
when the equipment connection state information indicates that the client is normally connected with the target equipment, and the cloud server connection state information indicates that the client is normally connected with the cloud server, determining that the equipment connection state information and the cloud server connection state information both meet normal connection conditions, and initiating an equipment list acquisition request to the cloud server.
5. The link management method according to claim 4, wherein the step of receiving the device list returned by the cloud service based on the device list acquisition request and extracting current management device information from the device list includes:
Receiving an equipment list returned by the cloud server based on the equipment list acquisition request; wherein, the mapping relation between each device and each device information is stored in the device list;
determining a current management device from the device list; the current management equipment comprises equipment currently in a cloud server management state;
determining a current management equipment identification code based on the mapping relation, and taking the current management equipment identification code as the current management equipment information; wherein the current management device identification code comprises a unique identification code of the current management device.
6. The link management method according to claim 5, further comprising, after the step of receiving the device list returned by the cloud service based on the device list acquisition request and extracting current management device information from the device list:
comparing the current management equipment identification code with a target equipment identification code to obtain a comparison result; wherein the target device identification code comprises a unique identification code of the target device.
7. The link management method according to claim 6, wherein the step of selecting a cloud link communication mode or a local link communication mode to communicate with the target device based on the current management device information includes:
When the current management equipment information meets cloud link communication conditions, communicating with the target equipment based on the cloud link;
and when the current management device information meets the communication condition of a local link, communicating with the target device based on the local link.
8. The link management method according to claim 7, wherein the step of communicating with the target device based on a cloud link when the current management device information satisfies cloud link communication conditions, comprises:
when the comparison result shows that the identification code of the current management device is different from the identification code of the target device, determining that the information of the current management device meets cloud link communication conditions;
and communicating with the target device based on the cloud link.
9. The link management method according to claim 7, wherein the step of communicating with the target device based on a local link when the current management device information satisfies a local link communication condition, comprises:
when the comparison result shows that the current management equipment identification code is the same as the target equipment identification code, determining that the current management equipment information meets the local link communication condition;
And communicating with the target device based on the local link.
10. A link management apparatus, applied to a client, comprising:
the acquisition module is used for acquiring equipment connection state information and cloud server connection state information; the device connection state information characterizes the connection state between the client and the target device, and the cloud server connection state information characterizes the connection state between the client and the cloud server;
the request initiating module is used for initiating a device list acquisition request to the cloud server when the device connection state information and the cloud server connection state information meet normal connection conditions;
the receiving module is used for receiving an equipment list returned by the cloud server based on the equipment list acquisition request and extracting current management equipment information from the equipment list;
and the communication module is used for selecting a cloud link communication mode or a local link communication mode to communicate with the target equipment based on the current management equipment information.
11. The link management system is characterized by comprising a client, a cloud server and target equipment;
The client is used for acquiring equipment connection state information and cloud service end connection state information, initiating an equipment list acquisition request to the cloud service end when the equipment connection state information and the cloud service end connection state information meet normal connection conditions, receiving an equipment list returned by the cloud service end based on the equipment list acquisition request, extracting current management equipment information from the equipment list, and selecting a cloud link communication mode or a local link communication mode to communicate with the target equipment based on the current management equipment information;
the cloud server is used for receiving the equipment list acquisition request initiated by the client and sending the equipment list to the client based on the equipment list acquisition request;
the target device is configured to communicate with the client based on the local link communication manner or the cloud link communication manner.
CN202211717618.0A 2022-12-29 2022-12-29 Link management method, device and system Pending CN116016639A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211717618.0A CN116016639A (en) 2022-12-29 2022-12-29 Link management method, device and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211717618.0A CN116016639A (en) 2022-12-29 2022-12-29 Link management method, device and system

Publications (1)

Publication Number Publication Date
CN116016639A true CN116016639A (en) 2023-04-25

Family

ID=86031349

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211717618.0A Pending CN116016639A (en) 2022-12-29 2022-12-29 Link management method, device and system

Country Status (1)

Country Link
CN (1) CN116016639A (en)

Similar Documents

Publication Publication Date Title
WO2015090248A1 (en) Server overload protection method and device
US20220150788A1 (en) Communication processing method, terminal device, and medium
CN111273955B (en) Thermal restoration plug-in optimization method and device, storage medium and electronic equipment
CN111008090B (en) Battery electric quantity control method and device, storage medium and terminal equipment
CN107317828B (en) File downloading method and device
CN111045737B (en) Equipment identifier acquisition method, device, terminal equipment and storage medium
CN110022600B (en) Driving current adjusting method and device, storage medium and mobile terminal
CN110891262A (en) Bluetooth pairing method, system and terminal equipment
CN113613310B (en) WIFI connection method and device, storage medium and mobile terminal
CN112867171B (en) WIFI connection method and device, storage medium and mobile terminal
CN105635379B (en) Noise suppression method and device
CN112261634B (en) Bluetooth transmission control method and device, terminal equipment and storage medium
CN110995324B (en) Bluetooth communication method, device, storage medium and terminal equipment
CN116016639A (en) Link management method, device and system
CN112286849A (en) Wireless charging base data switching method and system, storage medium and terminal equipment
CN110913022A (en) Method, device and system for downloading network file of mobile terminal and storage medium
CN108111553B (en) Method and device for providing service
CN116684467B (en) Data acquisition method, electronic device and storage medium
CN114095585B (en) Data transmission method, device, storage medium and electronic equipment
CN109995441B (en) Communication information processing method, device and storage medium
CN111405649B (en) Information transmission method and device and mobile terminal
CN111010477B (en) Audio signal calling method and system, storage medium and terminal equipment
CN114245427B (en) Network switching method and device and mobile terminal
CN111031588B (en) Network searching method, device, terminal equipment and storage medium
CN110891304B (en) gPS power consumption control method for mobile terminal

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination