Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
In order to solve the problems mentioned in the background art, according to an aspect of the embodiments of the present application, embodiments of a device connection method are provided.
As shown in fig. 1, the above-described device connection method may be applied to a device connection system as shown in fig. 1. The device connection system architecture 100 includes a device 101, a dispatch service 103, a temporary connection service 105, and a cloud service 107, where the device 101 is communicatively connected to the dispatch service 103, the temporary connection service 105, and the cloud service 107, respectively, via a network.
Wherein the device 101 may initiate a connection request and communicate to the dispatch service 103, the temporary connection service 105, and the cloud service 107. The dispatch service 103 is communicatively coupled to the cloud service 107 via a network, and the dispatch service 103 may forward the dispatch request of the device 101 directly to the cloud service 107 to facilitate the device 101 establishing a connection with the cloud service 107. Temporary connection service 105 is communicatively coupled to cloud service 107 via a network, and temporary connection service 105 may forward device requests to cloud service 107 to facilitate post-connection communication between device 101 and cloud service 107.
The device 101 is configured to interact with a user, and initiate a request to the temporary connection service 105, the cloud service 107, and the scheduling service 103, where the device 101 may also be referred to as a terminal device. The scheduling service 103 is configured to generate a temporary key, and return the temporary key to the requesting device 101 according to the configuration to connect with the temporary connection service 105 and the cloud service 107, and the scheduling service 103 may also be said to configure the corresponding temporary connection service 105 and cloud service 107 for the device 101. The temporary connection service 105 is configured to temporarily connect with the device 101, receive and forward a device request, and the temporary connection service 105 may be deployed in a distributed manner, or may be a single instance, and set according to an actual service. Cloud service 107 for receiving a request to temporarily connect service 105 and device 101, and establishing a connection with device 101.
Dispatch service 103, temporary connection service 105, and cloud service 107 may be used to provide services to device 101 or a client installed on device 101, and device 101 may connect and communicate with dispatch service 103, temporary connection service 105, and cloud service 107 after dispatch service 103, temporary connection service 105, and cloud service 107 send requests. The network may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
A user may interact with the dispatch service 103, temporary connection service 105, and cloud service 107 over a network using the device 101 to receive or send messages, etc. Various communication client applications may be installed on the device 101, such as a web browser application, a search class application, an instant messaging tool, and the like. Wherein device 101 may be a variety of electronic devices having a display screen and supporting web browsing, including, but not limited to, smartphones, tablet computers, electronic book readers, MP3 players (Moving Picture Experts Group Audio Layer III, dynamic video expert compression standard audio plane 3), MP4 (Moving Picture Experts Group Audio Layer IV, dynamic video expert compression standard audio plane 4) players, laptop and desktop computers, and the like. Scheduling service 103, temporary connection service 105, and cloud service 107 may each be servers that provide various services, such as a background server that provides support for pages displayed on device 101.
It should be noted that, the device connection method provided by the embodiment of the present application is generally executed by the scheduling service 103, the temporary connection service 105, the cloud service 107 and/or the device 101, and accordingly, the device connection apparatus is generally set in the scheduling service 103, the temporary connection service 105, and the cloud service 107/device. And it should be understood that the number of devices 101, networks, scheduling services 103, temporary connection services 105, cloud services 107 in fig. 1 are merely illustrative. There may be any number of devices 101, networks, dispatch services 103, temporary connection services 105, and cloud services 107, as desired for an implementation.
As shown in fig. 2, fig. 2 is a flowchart of an alternative device connection method according to an embodiment of the present invention. As an example of the device connection method being performed by a device, a device connection method includes the steps of:
Step S202, a temporary key returned by the dispatching service is obtained, and the temporary key is generated for the dispatching service according to a dispatching request sent by the equipment.
In the embodiment, the provided device connection method is suitable for a high concurrency scene of device batch connection cloud service in the internet of things. In the device connection process, the device wants to establish communication connection with the cloud service, a scheduling request needs to be initiated to the scheduling service, a temporary key can be generated after the scheduling service receives the scheduling request of the device, and the temporary key is returned to the device.
The temporary key is verification information for communication connection between the device and the temporary connection service and between the device and the cloud service, the temporary key includes device information, cloud service addresses, random check codes and other information, the device information is specific information of the device initiating the scheduling request to the scheduling service, such as specific model, power, size, shape, energy consumption, device usage and other related information of the device, the cloud service addresses are addresses of cloud services which want to establish communication, the device can be connected and communicated with the cloud service through the cloud service addresses, in this embodiment, the number of cloud services can be according to the actual situation, the addresses corresponding to different cloud services are different, namely, the cloud service addresses are variable, the device needs to burn a fixed address when burning, the address of the cloud service cannot be written to death when the device is required to be connected with the cloud service, and the device needs to request the cloud service which corresponds to the scheduling service to obtain different cloud service data. The random verification code is a verification code generated after the scheduling service receives the scheduling request of the equipment, the verification code can be a fixed verification code or a real-time verification code, and the verification code can be obtained by any combination of numbers, chinese characters, letters, characters and the like. Of course, in order to enhance the security of the device connection, the verification code may be a real-time verification code, so that timeliness of the verification code is ensured, and the security of the device connection is further improved.
Step S204, when the equipment connection network of the dispatch service is congested, a temporary connection service address returned by the dispatch service is obtained, and a connection request is initiated to the temporary connection service according to the temporary key and the temporary connection service address so as to establish connection with the temporary connection service.
In some embodiments, when the device connection network of the scheduling service is congested, the scheduling service also needs to acquire a temporary connection service address and return the temporary connection service address to the device, at which time the device may receive the temporary key of the scheduling service and the temporary connection service address.
Step S206, if the cloud service data of the equipment request is detected, the equipment request is forwarded to the cloud service through the temporary connection service.
In this embodiment, after the scheduling service generates the temporary key, the scheduling service configures a temporary connection service address for the device that sends the scheduling request, and returns the temporary connection service address to the device, then the device determines the location of the temporary connection service according to the received temporary connection service address, finds the corresponding temporary connection service, initiates a connection request to the temporary connection service through the received temporary key, and after the temporary connection service parses the temporary key and verifies, obtains device information and a cloud service address in the temporary key, and initiates a request to the cloud service through the cloud service address, where the request information includes device information, the temporary key, and request data when the device requests the temporary connection service. This may have a verification process so that the device does not randomly send requests elsewhere, nor do temporary connection services or cloud services randomly receive strange requests.
In some embodiments, after the device establishes a connection to the temporary connection service, the device starts a broadcast reception return message, i.e. the device opens a network connection, because many devices do not always open the network module, here the network module, due to power consumption problems, waiting for a request sent by a traffic server, such as a cloud service.
Specifically, the temporary connection service has a function of performing long connection with the device, and can forward a request of the device to the cloud service. After the device is connected to the temporary connection service, the device registers its own information with the temporary connection service, and registers the information. When the equipment does not have a real service request, the equipment is disconnected with the temporary connection service, and the equipment is disconnected with the cloud service, so that the congestion of the cloud service network can be avoided. Once the device has a real service request, for example, when a user needs to acquire data of a cloud service, the real service request is usually manually operated, if a person operates the device, the device needs to communicate with a server. And under the condition of network congestion, the equipment initiates the request for acquiring the cloud service data to the temporary connection service, and the temporary connection service forwards the request of the equipment to the cloud service. When the equipment generates an actual request, connection between the equipment and the cloud service is established again, so that peak pressure of the cloud service when the equipment is connected in batches can be reduced, concurrency of equipment connection is reduced, and reliability of the whole Internet of things system is improved.
Step S208, receiving connection data returned by the cloud service, and establishing connection with the cloud service according to the connection data.
In some embodiments, the cloud service receives a request initiated by the temporary connection service, obtains a device address according to the device information in the temporary key, and returns the temporary key and the connection data to the device. After the equipment receives the return of the cloud service, the temporary key is analyzed, the security is requested according to the temporary key verification, and communication can be performed after connection information is acquired through connection data and connection is established with the cloud service. The connection data, that is, information needed for connecting the device with the cloud service, such as some agreed check rules, and the device id of the cloud service returned to the device.
When the equipment of the dispatching service is connected with the cloud service at random, the temporary connection service address returned by the dispatching service is acquired, a connection request is initiated to the temporary connection service according to the temporary key and the temporary connection service address to establish connection with the temporary connection service, when the equipment needs to request cloud service data, the equipment request is forwarded to the cloud service through the temporary connection service, and the equipment request is forwarded to the cloud service through the temporary connection service.
In an alternative embodiment, before the step S202, the method further includes:
sending a scheduling request to the scheduling service;
Detecting the congestion condition of the equipment connection network of the scheduling service according to the scheduling request;
if the equipment connection network of the scheduling service is not congested, generating a temporary key through the scheduling service, and returning the temporary key to the equipment.
In this embodiment, when a user needs to acquire cloud service data, a scheduling request may be sent to a scheduling service through a device, and the scheduling service receives the scheduling request of the device and parses the scheduling request to acquire device information, request content, and the like. In the device connection process, the device wants to establish communication connection with the cloud service, a scheduling request needs to be initiated to the scheduling service, a temporary key can be generated after the scheduling service receives the scheduling request of the device, and the temporary key is returned to the device.
Specifically, after the scheduling service receives the scheduling request of the device, the blocking condition of the device connection network of the scheduling service can be detected according to the current scheduling request, and whether the temporary connection service needs to be added is selected according to the blocking condition of the device connection network of the scheduling service. If the equipment connection network of the scheduling service is not congested, a conventional cloud service request flow can be executed, for example, communication connection is directly carried out between the cloud service request and equipment through the scheduling service, temporary connection service is not required to be added, and only the scheduling service is required to generate a temporary key and return the temporary key to the equipment.
In this embodiment, the connection mode of the device and the cloud service is selected by detecting the congestion condition of the device connection network of the scheduling service, and when the device connection network of the scheduling service is not congested, the device establishes connection with the cloud service only through the temporary key, thereby improving the connection speed of the device and the cloud service.
In an alternative embodiment, after detecting the device connection network congestion condition of the scheduling service according to the scheduling request, the method further comprises:
If the equipment connection network of the scheduling service is congested, acquiring a temporary connection service address through the scheduling service;
and returning the temporary key and the temporary connection service address to the equipment through the dispatching service.
In this embodiment, the congestion of the device connection network may be a network congestion problem generated when the device connects to the cloud service in batches, for example, a high concurrency scenario usually comes from a situation of batch power-off/power-on, and at this time, the device powers up almost at the same time, and also initiates a login request to the server almost at the same time, so as to request to establish a connection with the cloud service.
In this embodiment, when the device connection network of the scheduling service is congested, it is described that too many devices are simultaneously requesting to connect to the cloud service from the scheduling service, and it is necessary to add a temporary connection service to participate in the cloud service connection request. The scheduling service is required to provide the temporary key and the specific address information of the temporary connection service at the same time, so that the equipment can find the corresponding temporary connection service through the temporary key and the specific temporary connection service address, thereby establishing the connection between the equipment and the temporary connection service, facilitating the realization of a delayed connection mode through the temporary connection service, reducing the peak pressure of cloud service when the equipment is connected in batches, reducing the concurrency of equipment connection, solving the problem of equipment connection network congestion generated when the equipment is connected concurrently, and further improving the reliability of the whole Internet of things system.
In an alternative embodiment, the detecting, in step, a congestion condition of a device connection network of the scheduling service according to the scheduling request includes:
Acquiring preset initial monitoring parameters, wherein the preset initial monitoring parameters are thresholds for generating request numbers in a fixed time length by the scheduling service;
And judging whether the equipment connection network of the scheduling service is congested according to the scheduling request and the preset initial monitoring parameters.
In some embodiments, the monitoring parameter is a number of phase requests of the scheduling service, the number of phase requests is a number of scheduling requests generated by the scheduling service within a fixed time period, and the preset initial monitoring parameter is a threshold value of the number of requests set by the scheduling service within the fixed time period.
Specifically, after the scheduling service receives the scheduling request of the device, whether the scheduling service has the problem of congestion of the device connection network can be judged according to the preset initial monitoring parameters.
In this embodiment, whether the high concurrency condition of the device connection occurs in the scheduling service is monitored by presetting an initial monitoring parameter, so that the congestion condition of the device connection network of the scheduling service can be more accurately judged, the connection mode between the device and the cloud service can be more quickly selected, the connection speed between the device and the cloud service can be further improved, and the device connection efficiency can be further improved.
In an optional embodiment, the step of determining whether the device connection network of the scheduling service is congested according to the scheduling request and the preset initial monitoring parameter includes:
Detecting the number of real-time requests generated by the scheduling service in a fixed time length according to the scheduling request;
If the real-time request number generated by the scheduling service in the fixed time length exceeds the preset initial monitoring parameter, determining that the equipment connection network is congested;
And if the number of the real-time requests generated by the scheduling service in the fixed time period does not exceed the preset initial monitoring parameters, determining that the equipment connection network is not congested.
In this embodiment, the number of real-time requests is the current number of requests of the scheduling service within a fixed duration, for example, the fixed duration is set to 10 minutes, the preset initial monitoring parameter is set to 1000, when the device sends the scheduling request to the scheduling service, the scheduling request of the device is just the 1001 st request of the scheduling service within 10 minutes, at this time, the actual number of requests of the scheduling service is 1001, which indicates that when the scheduling service receives the scheduling request of the device, the actual number of requests of the scheduling service has exceeded the preset initial monitoring parameter, which indicates that the device connection has high concurrency, and further indicates that the network connection of the device has congestion.
In this embodiment, when the number of device scheduling requests received by the scheduling service does not exceed the preset initial monitoring parameter, it is indicated that the device connection does not have a high concurrency condition, and at this time, the scheduling service is in a normal request condition and does not have a high concurrency condition, which is further indicated that the device connection network is not congested.
In this embodiment, the device request condition in the scheduling service is monitored in real time by presetting a preset initial monitoring parameter, when the device connection network of the scheduling service is congested, a temporary connection service is added to generate temporary connection with the device, and a temporary key which can be verified quickly by the cloud service is generated at the same time, when the device generates a real request, the device delay connection is realized by establishing a connection mode between the device and the cloud service again, and the concurrent peak value of the device connection is slowed down, so that the device connection speed is improved, the problem of the congestion of the device connection network is solved, or when the device connection network is not congested, a normal connection mode can be selected, the device request is forwarded to the cloud service directly through the scheduling service, the step of temporarily connecting the service is reduced, and the device connection speed is further improved. The method for realizing the connection and communication between the equipment and the cloud service can be flexibly selected according to the equipment request condition, the equipment connection speed can be improved in steps, the problem of equipment connection network congestion is further solved, and the equipment connection reliability is improved.
In an alternative embodiment, the step S202 specifically includes:
When the equipment connection network of the scheduling service is not congested, forwarding a scheduling request of the equipment to the cloud service through the scheduling service;
and connecting with the cloud service based on the temporary key and the scheduling request of the equipment.
In this embodiment, when the device connection network of the scheduling service is not congested, the request of the device may be forwarded to the cloud service directly through the scheduling service. And the connection communication between the equipment and the cloud service is realized by combining the temporary key, so that the connection between the equipment and the cloud service is realized without increasing the temporary connection service, the connection speed between the equipment and the cloud service is improved from the connection step, and the connection efficiency of the equipment and the cloud service is further improved.
In an alternative embodiment, step S206 includes:
sending a device request for acquiring cloud service data to the temporary connection service;
And after the temporary connection service verifies the equipment request, forwarding the equipment request to the cloud service through the temporary connection service.
In this embodiment, when a user needs to request cloud service data, needs to send a device request for acquiring the cloud service data to the temporary connection service, if a device connection network just meeting a scheduling service is in a congestion condition, the device connection network can directly establish temporary connection with the temporary connection service, after the temporary connection service verifies the request information of the device, the device connection service and the temporary connection service can establish connection, and the temporary connection service can forward the device request of the device to the cloud service, so that communication connection between the cloud service and the device can be established.
In an alternative embodiment, as shown in connection with fig. 3, fig. 3 is a flowchart of an alternative device connection method according to an embodiment of the present invention. The device connection system comprises a device, a scheduling service, a temporary connection service and a cloud service, wherein the device is in communication connection with the scheduling service, the temporary connection service and the cloud service respectively, the scheduling service is in communication connection with the cloud service, the temporary connection service is in communication connection with the cloud service, and the device connection method comprises the following steps:
Step S302, a scheduling request of a device is acquired.
In this embodiment, when a user needs to acquire cloud service data, a scheduling request may be sent to a scheduling service by a device, and the scheduling service receives the scheduling request of the device and parses the scheduling request to acquire device information and the like.
And step S304, judging whether the equipment connection network is congested according to the scheduling request and preset initial monitoring parameters.
In some embodiments, after the scheduling service receives the scheduling request of the device, whether the scheduling service has a problem of congestion of the device connection network may be determined according to the preset initial monitoring parameter. The network congestion of the device connection may be a network congestion problem generated when the device connects to the cloud service in batches, for example, a high concurrency scene usually comes from a situation of batch power-off/power-on, and at this time, the device powers up almost at the same time, and also initiates a login request to the server almost at the same time, so as to request to establish a connection with the server.
Step S306, if the equipment connection network is congested, a temporary key is generated according to the scheduling request and a temporary connection service address is acquired.
The device connection method is suitable for high concurrency scenes of device batch connection cloud services in the Internet of things. In the device connection process, the device wants to establish communication connection with the cloud service, a scheduling request needs to be initiated to the scheduling service, a temporary key can be generated after the scheduling service receives the scheduling request of the device, and the temporary key is returned to the device.
The temporary key is verification information for communication connection between the device and the temporary connection service and between the device and the cloud service, the temporary key includes device information, cloud service addresses, random check codes and other information, the device information is specific information of the device initiating the scheduling request to the scheduling service, such as specific model, power, size, shape, energy consumption, device usage and other related information of the device, the cloud service addresses are addresses of cloud services which want to establish communication, the device can be connected and communicated with the cloud service through the cloud service addresses, in this embodiment, the number of cloud services can be according to the actual situation, the addresses corresponding to different cloud services are different, namely, the cloud service addresses are variable, the device needs to burn a fixed address when burning, the address of the cloud service cannot be written to death when the device is required to be connected with the cloud service, and the device needs to request the cloud service which corresponds to the scheduling service to obtain different cloud service data. The random verification code is a verification code generated after the scheduling service receives the scheduling request of the equipment, the verification code can be a fixed verification code or a real-time verification code, and the verification code can be obtained by any combination of numbers, chinese characters, letters, characters and the like. Of course, in order to enhance the security of the device connection, the verification code may be a real-time verification code, so that timeliness of the verification code is ensured, and the security of the device connection is further improved.
When the connection network of the equipment for dispatching the service is congested, the dispatching service also needs to acquire a temporary connection service address and return the temporary connection service address to the equipment, and at the moment, the equipment can receive the temporary key of the dispatching service and the temporary connection service address.
And step S308, the temporary key and the temporary connection service address are sent to the equipment, so that connection is established with the temporary connection service when the equipment is detected to request cloud service data.
In some embodiments, after the scheduling service generates the temporary key, the scheduling service configures a temporary connection service address for the device sending the scheduling request, and returns the temporary connection service address to the device, then the device determines the position of the temporary connection service according to the received temporary connection service address, finds the corresponding temporary connection service, initiates the connection request to the temporary connection service through the received temporary key, and after the temporary connection service analyzes the temporary key and verifies, obtains device information in the temporary key, cloud service address and the like, initiates a request to the cloud service through the cloud service address, and the request information comprises device information, the temporary key and request data when the device requests the temporary connection service. This may have a verification process so that the device does not randomly send requests elsewhere, nor do temporary connection services or cloud services randomly receive strange requests.
And step S310, forwarding the equipment request of the equipment to a cloud service through the temporary connection service, and establishing connection between the equipment and the cloud service based on the equipment request.
In some embodiments, after the device establishes a connection to the temporary connection service, the device starts a broadcast reception return message, i.e. the device opens a network connection, because many devices do not always open the network module, here the network module, due to power consumption problems, waiting for a request sent by a traffic server, such as a cloud service.
Specifically, the temporary connection service has a function of performing long connection with the device, and can forward a request of the device to the cloud service. After the device is connected to the temporary connection service, the device registers its own information with the temporary connection service, and registers the information. When the equipment does not have a real service request, the equipment is disconnected with the temporary connection service, and the equipment is disconnected with the cloud service, so that the congestion of the cloud service network can be avoided. Once the device has a real service request, for example, when a user needs to acquire data of a cloud service, the real service request is usually manually operated, if a person operates the device, the device needs to communicate with a server. And under the condition of network congestion, the equipment initiates the request for acquiring the cloud service data to the temporary connection service, and the temporary connection service forwards the request of the equipment to the cloud service. When the equipment generates an actual request, connection between the equipment and the cloud service is established again, so that peak pressure of the cloud service when the equipment is connected in batches can be reduced, concurrency of equipment connection is reduced, and reliability of the whole Internet of things system is improved.
In the embodiment of the invention, whether a device connection network is congested is judged by acquiring a scheduling request of the device, whether the device connection network is congested is judged according to the scheduling request and a preset initial monitoring parameter, if the device connection network is congested, a temporary key is generated according to the scheduling request, a temporary connection service address is acquired, the temporary key and the temporary connection service address are sent to the device, so that connection is established with the temporary connection service when cloud service data of the device request is detected, the device request of the device is forwarded to the cloud service through the temporary connection service, and connection between the device and the cloud service is established based on the device request. The method can select to increase temporary connection service to realize delayed connection when the equipment connection network is congested, so that peak pressure of cloud service when equipment is connected in batches is reduced, concurrency of equipment connection is reduced, the problem of equipment connection network congestion generated when equipment is connected in concurrency is solved, and reliability of the whole Internet of things system is further improved.
In an alternative embodiment, the step S302 specifically includes:
Presetting initial monitoring parameters, wherein the preset initial monitoring parameters are thresholds of the number of requests in a fixed time length of a scheduling service;
If the real-time request number generated by the scheduling service in the fixed time length exceeds the preset initial monitoring parameter, determining that the equipment connection network is congested;
And if the number of the real-time requests generated by the scheduling service in the fixed time period does not exceed the preset initial monitoring parameters, determining that the equipment connection network is not congested.
In some embodiments, the monitoring parameter is a number of phase requests of the scheduling service, the number of phase requests is a number of scheduling requests generated by the scheduling service within a fixed time period, and the preset initial monitoring parameter is a threshold value of the number of requests set by the scheduling service within the fixed time period.
Specifically, whether the high concurrency condition of equipment connection occurs in the scheduling service is monitored by presetting an initial monitoring parameter.
In this embodiment, when the number of device scheduling requests received by the scheduling service exceeds a preset initial monitoring parameter, it is indicated that high concurrency occurs in device connection, and it is further indicated that congestion exists in the device connection network.
In this embodiment, when the number of device scheduling requests received by the scheduling service does not exceed the preset initial monitoring parameter, it is indicated that the device connection does not have a high concurrency condition, and at this time, the scheduling service is in a normal request condition and does not have a high concurrency condition, which is further indicated that the device connection network is not congested.
In this embodiment, the device request condition in the scheduling service is monitored in real time by presetting a preset initial monitoring parameter, when the device connection network of the scheduling service is congested, a temporary connection service is added to generate temporary connection with the device, and a temporary key which can be verified quickly by the cloud service is generated at the same time, when the device generates a real request, the device delay connection is realized by establishing a connection mode between the device and the cloud service again, and the concurrent peak value of the device connection is slowed down, so that the device connection speed is improved, the problem of the congestion of the device connection network is solved, or when the device connection network is not congested, a normal connection mode can be selected, the device request is forwarded to the cloud service directly through the scheduling service, the step of temporarily connecting the service is reduced, and the device connection speed is further improved. The method for realizing the connection and communication between the equipment and the cloud service can be flexibly selected according to the equipment request condition, the equipment connection speed can be improved in steps, the problem of equipment connection network congestion is further solved, and the equipment connection reliability is improved.
In an optional embodiment, after determining whether the device connection network is congested according to the scheduling request and the preset initial monitoring parameter, the method specifically further includes:
if the equipment connection network of the scheduling service is not congested, generating a temporary key according to the scheduling request;
And sending the temporary key to the equipment, forwarding a scheduling request of the equipment to a cloud service, and establishing connection between the equipment and the cloud service based on the temporary key and the scheduling request.
In this embodiment, when the device connection network of the scheduling service is not congested, the scheduling request of the device may be forwarded to the cloud service directly through the scheduling service. And the connection communication between the equipment and the cloud service is realized by combining the temporary key, so that the connection between the equipment and the cloud service is realized without increasing the temporary connection service, the connection speed between the equipment and the cloud service is improved from the connection step, and the connection efficiency of the equipment and the cloud service is further improved.
According to still another aspect of the embodiment of the present application, as shown in fig. 4, corresponding to the device connection method in the above embodiment, the present embodiment provides a device connection apparatus 400, which is applicable to a device in a device connection system, where the device connection system includes a device, a scheduling service, a temporary connection service, and a cloud service, where the device is communicatively connected to the scheduling service, the temporary connection service, and the cloud service, respectively, where the scheduling service is communicatively connected to the cloud service, and where the temporary connection service is communicatively connected to the cloud service, and where the device connection apparatus 400 includes:
A first obtaining module 401, configured to obtain a temporary key returned by a scheduling service, where the temporary key is generated by the scheduling service according to a scheduling request sent by a device;
A first connection module 403, configured to obtain a temporary connection service address returned by the scheduling service when the device connection network of the scheduling service is congested, and initiate a connection request to the temporary connection service according to the temporary key and the temporary connection service address, so as to establish a connection with the temporary connection service;
A first forwarding module 405, configured to forward, if it is detected that the device requests cloud service data, the device request to a cloud service through the temporary connection service;
and the second connection module 407 is configured to receive connection data returned by the cloud service, and establish connection with the cloud service according to the connection data.
It should be noted that, in this embodiment, the first obtaining module 401 may be used to perform step S202 in the embodiment of the present application, the first connecting module 403 in this embodiment may be used to perform step S204 in the embodiment of the present application, the first forwarding module 405 in this embodiment may be used to perform step S206 in the embodiment of the present application, and the second connecting module 407 in this embodiment may be used to perform step S208 in the embodiment of the present application.
Optionally, before the first obtaining module 401, the apparatus further includes:
the first sending module is used for sending a scheduling request to the scheduling service;
the detection module is used for detecting the congestion condition of the equipment connection network of the scheduling service according to the scheduling request;
And the generation module is used for generating a temporary key through the dispatching service and returning the temporary key to the equipment if the equipment connection network of the dispatching service is not congested.
Optionally, after the detection module, the apparatus further comprises:
The second acquisition module is used for acquiring a temporary connection service address through the scheduling service if the equipment connection network of the scheduling service is congested;
and the return module is used for returning the temporary key and the temporary connection service address to the equipment through the dispatch service.
Optionally, the detection module includes:
the acquisition unit is used for acquiring preset initial monitoring parameters, wherein the preset initial monitoring parameters are thresholds for generating the request number of the scheduling service within a fixed duration;
and the judging unit is used for judging whether the equipment connection network of the scheduling service is congested according to the scheduling request and the preset initial monitoring parameter.
Optionally, the judging unit is further configured to detect, according to the scheduling request, a number of real-time requests generated by the scheduling service within a fixed duration, determine that the device connection network is congested if the number of real-time requests generated by the scheduling service within the fixed duration exceeds the preset initial monitoring parameter, and determine that the device connection network is not congested if the number of real-time requests generated by the scheduling service within the fixed duration does not exceed the preset initial monitoring parameter.
Optionally, after the first obtaining module 401, the apparatus further includes a request sending module, configured to forward, through the scheduling service, a scheduling request of the device to the cloud service when a device connection network of the scheduling service is not congested, and a connection establishing module, configured to connect with the cloud service based on the temporary key and the scheduling request of the device.
Optionally, the first forwarding module 405 is further configured to send a device request for obtaining cloud service data to the temporary connection service, and after the temporary connection service verifies the device request, forward the device request to the cloud service through the temporary connection service.
It should be noted that the above modules are the same as examples and application scenarios implemented by the corresponding steps, but are not limited to what is disclosed in the above embodiments. It should be noted that the above modules may be implemented in software or hardware as a part of the apparatus in the hardware environment shown in fig. 1.
It should be noted here that the suffixes such as modules, components, units, sub-modules, sub-units described in the above-described means are merely for facilitating the description of the present application, and are not of specific significance in themselves, and thus may be used in a mixed manner.
According to still another aspect of the embodiment of the present application, as shown in fig. 5, corresponding to the device connection method in the above embodiment, the present embodiment provides a device connection apparatus 500, where the device connection apparatus 500 includes:
a third obtaining module 501, configured to obtain a scheduling request of a device;
A judging module 503, configured to judge whether the device connection network is congested according to the scheduling request and a preset initial monitoring parameter;
A generating module 505, configured to generate a temporary key and obtain a temporary connection service address according to the scheduling request if the device connection network is congested;
A sending module 507, configured to send the temporary key and the temporary connection service address to the device, so that connection is established with a temporary connection service when it is detected that the device requests cloud service data;
A second forwarding module 509, configured to forward, through the temporary connection service, a device request of the device to a cloud service, and establish a connection between the device and the cloud service based on the device request.
It should be noted that, in this embodiment, the third obtaining module 501 may be used to execute step S302 in the embodiment of the present application, the judging module 503 in this embodiment may be used to execute step S304 in the embodiment of the present application, the generating module 505 in this embodiment may be used to execute step S306 in the embodiment of the present application, the sending module 507 in this embodiment may be used to execute step S308 in the embodiment of the present application, and the second forwarding module 509 in this embodiment may be used to execute step S310 in the embodiment of the present application.
Optionally, the judging module 503 includes a preset unit configured to preset an initial monitoring parameter, where the preset initial monitoring parameter is a threshold value of a number of requests in a fixed duration of a scheduling service, a second determining unit configured to determine that the device connection network is congested if the number of real-time requests generated by the scheduling service in the fixed duration exceeds the preset initial monitoring parameter, and a third determining unit configured to determine that the device connection network is not congested if the number of real-time requests generated by the scheduling service in the fixed duration does not exceed the preset initial monitoring parameter.
Optionally, the device further comprises a third connection module, a third forwarding module and a third forwarding module, wherein the third connection module is used for generating a temporary key according to the scheduling request if the equipment connection network of the scheduling service is not congested, the third forwarding module is used for sending the temporary key to the equipment and forwarding the scheduling request of the equipment to the cloud service, and connection between the equipment and the cloud service is established based on the temporary key and the scheduling request.
It should be noted that the above modules are the same as examples and application scenarios implemented by the corresponding steps, but are not limited to what is disclosed in the above embodiments. It should be noted that the above modules may be implemented in software or hardware as a part of the apparatus in the hardware environment shown in fig. 1.
It should be noted here that the suffixes such as modules, components, units, sub-modules, sub-units described in the above-described means are merely for facilitating the description of the present application, and are not of specific significance in themselves, and thus may be used in a mixed manner.
According to another aspect of the embodiments of the present application, as shown in fig. 6, the present application provides an electronic device, including a memory 601, a processor 603, a communication interface 605 and a communication bus 607, where the memory 601 stores a computer program that can be executed on the processor 603, and the memory 601, the processor 603 communicates with the communication bus 607 through the communication interface 605, and the processor 603 executes the steps of the device connection method when the processor 603 executes the computer program.
The memory and the processor in the electronic device communicate with the communication interface through a communication bus. The communication bus may be a peripheral component interconnect standard (PERIPHERAL COMPONENT INTERCONNECT, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, or the like. The communication bus may be classified as an address bus, a data bus, a control bus, or the like.
The memory may include random access memory (Random Access Memory, RAM) or may include non-volatile memory (non-volatile memory), such as at least one disk memory. Optionally, the memory may also be at least one memory device located remotely from the aforementioned processor.
The processor may be a general-purpose processor, including a central Processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), a digital signal processor (DIGITAL SIGNAL Processing, DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable gate array (FPGA) or other Programmable logic device, discrete gate or transistor logic device, or discrete hardware components.
There is also provided, in accordance with yet another aspect of embodiments of the present application, a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the steps of the device connection method of any of the embodiments described above.
Optionally, in an embodiment of the present application, the computer readable medium is configured to store program code for the processor to perform the steps of the device connection method applicable to a device or to a dispatch service in the above embodiment.
The device connection method suitable for the device comprises the following steps:
The method comprises the steps of S202, obtaining a temporary key returned by a dispatching service, wherein the temporary key is generated by the dispatching service according to a dispatching request sent by equipment, S204, obtaining a temporary connection service address returned by the dispatching service when a network is congested in equipment connection of the dispatching service, initiating a connection request to the temporary connection service according to the temporary key and the temporary connection service address to establish connection with the temporary connection service, S206, if cloud service data is detected to be requested by equipment, forwarding the equipment request to cloud service through the temporary connection service, S208, receiving the connection data returned by the cloud service, and establishing connection with the cloud service according to the connection data.
The device connection method suitable for the dispatch service comprises the following steps:
The method comprises the steps of S302, obtaining a scheduling request of equipment, S304, judging whether an equipment connection network is congested according to the scheduling request and preset initial monitoring parameters, S306, if the equipment connection network is congested, generating a temporary key according to the scheduling request and obtaining a temporary connection service address, S308, sending the temporary key and the temporary connection service address to the equipment so as to establish connection with the temporary connection service when cloud service data of the equipment request is detected, S310, forwarding the equipment request of the equipment to cloud service through the temporary connection service, and establishing connection between the equipment and the cloud service based on the equipment request.
Alternatively, specific examples in this embodiment may refer to examples described in the foregoing embodiments, and this embodiment is not described herein. And when the embodiment of the application is concretely implemented, the embodiment can refer to the above embodiments, and has corresponding technical effects.
It is to be understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For a hardware implementation, the Processing units may be implemented within one or more Application SPECIFIC INTEGRATED Circuits (ASICs), digital signal processors (DIGITAL SIGNAL Processing, DSPs), digital signal Processing devices (DSP DEVICE, DSPD), programmable logic devices (Programmable Logic Device, PLDs), field-Programmable gate arrays (Field-Programmable GATE ARRAY, FPGA), general purpose processors, controllers, micro-controllers, microprocessors, other electronic units for performing the functions described herein, or a combination thereof.
For a software implementation, the techniques described herein may be implemented by means of units that perform the functions described herein. The software codes may be stored in a memory and executed by a processor. The memory may be implemented within the processor or external to the processor.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, and for example, the division of the modules is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment. In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be embodied in essence or a part contributing to the prior art or a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. The storage medium includes various media capable of storing program codes such as a U disk, a mobile hard disk, a ROM, a RAM, a magnetic disk or an optical disk.
It is noted that relational terms such as first, second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms contain, include, or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.
The foregoing is only a specific embodiment of the application to enable those skilled in the art to understand or practice the application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.