A method, apparatus, electronic device and storage medium for message interaction linkage

Abstract

The present invention discloses a message interaction linkage method, device, electronic device and storage medium. The method includes: in response to the message interaction between a first application of a target terminal and a first cloud server, sending the identification information of the target terminal to a second cloud server; and sending an uplink inquiry delay instruction to a second application of the target terminal through the first application; establishing a connection link between the second cloud server and the second application based on the identification information; when there is data to be sent down in the second cloud server, sending a downlink data message to the second application based on the connection link; and delaying the uplink inquiry of the second application to the second cloud server by one cycle based on the uplink inquiry delay instruction. The present invention establishes linkages between multiple applications and between multiple cloud services, realizes the automatic push of downlink messages, reduces the actions of the terminal waking up from low power consumption to actively make an uplink inquiry, saves the power consumption and data traffic of the terminal, and can be widely applied to the field of data processing technology.

Description

Technical Field

[0001] The present invention relates to the technical field of data processing, and in particular, to a method, device, electronic device, and storage medium for message interaction linkage. Background Art

[0002] Multiple application tasks run simultaneously in a low-power mobile Internet of Things terminal. Some applications in the terminal interact with the cloud for uplink and downlink data messages relatively frequently; some applications only need to occasionally receive data messages sent by the cloud. In order to let the cloud know that the terminal has woken up from the low-power state and is reachable for downlink, the terminal application asks the cloud every communication cycle whether there are data messages to be sent.

[0003] In the prior art, a fixed-cycle logic is usually adopted for message interaction. The terminal application that occasionally receives data messages sent by the cloud wakes up from the low-power state every communication cycle to initiate an uplink inquiry message. It is possible that the cloud has no data messages to be sent, but the actions of waking up from the low-power state and performing data communication will consume the battery power and data traffic of the terminal. Summary of the Invention

[0004] The present invention aims to solve at least one of the technical problems in the related art to some extent. For this purpose, the present invention provides a method, device, electronic device, and storage medium for message interaction linkage, which can efficiently perform message interaction linkage.

[0005] On the one hand, an embodiment of the present invention provides a method for message interaction linkage, including:

[0006] In response to the message interaction between the first application of the target terminal and the first cloud server, send the identification information of the target terminal to the second cloud server; and send an uplink inquiry delay instruction to the second application of the target terminal through the first application; the second cloud server is associated with the second application of the target terminal for interaction;

[0007] Based on the identification information, establish a connection link between the second cloud server and the second application;

[0008] When there is data to be sent in the second cloud server, send a downlink data message to the second application based on the connection link;

[0009] Based on the uplink inquiry delay instruction, delay the uplink inquiry of the second application to the second cloud server by one cycle.

[0010] Optionally, in response to the message interaction between the first application of the target terminal and the first cloud server, sending the identification information of the target terminal to the second cloud server includes:

[0011] When the first cloud server receives the uplink message of the first application of the target terminal, it sends the identification information of the target terminal to the second cloud server through the first cloud server.

[0012] Optionally, the identification information includes the International Mobile Equipment Identity (IMEI) and IP address of the target terminal; based on the identification information, establishing a connection link between the second cloud server and the second application includes:

[0013] Locate the target terminal based on the International Mobile Equipment Identity (IMEI);

[0014] Establish a connection link between the second cloud server and the second application according to the IP address.

[0015] Optionally, the method further includes:

[0016] Obtain the IP protocol stacks of the first application and the second application;

[0017] When the first application and the second application use different IP protocol stacks, do not send an uplink inquiry delay instruction to the second application of the target terminal through the first application.

[0018] Optionally, when the second application uses a domain name to interact with the second cloud server, the method further includes:

[0019] Locate the target terminal based on the identification information; and then obtain the domain name of the second application from the target terminal;

[0020] Based on the domain name, obtain the IP address corresponding to the domain name in the non-volatile storage of the target terminal;

[0021] When the IP address is obtained in the non-volatile storage, establish a connection link between the second cloud server and the second application according to the IP address;

[0022] When the IP address is not obtained in the non-volatile storage, perform a DNS query based on the domain name to obtain the IP address corresponding to the domain name; and then store the IP address in the non-volatile storage.

[0023] Optionally, the method further includes:

[0024] When the IP address is obtained in the non-volatile storage, obtain the storage time of the IP address;

[0025] When the time interval between the storage time and the current time exceeds the preset period, establish a connection link between the second cloud server and the second application using the domain name.

[0026] Optionally, the method further includes at least one of the following:

[0027] Perform DNS queries regularly, and then periodically update the IP addresses in the non-volatile storage according to the results of the DNS queries;

[0028] When the second application receives a downlink data packet from the second cloud server, it performs a DNS query, and then updates the IP address in the non-volatile storage according to the result of the DNS query;

[0029] Before the second application sends an uplink inquiry packet to the second cloud server, it performs a DNS query, and then updates the IP address in the non-volatile storage according to the result of the DNS query.

[0030] On the other hand, an embodiment of the present invention provides a message interaction linkage device, including:

[0031] A first module, configured to, in response to the message interaction between the first application of the target terminal and the first cloud server, send the identification information of the target terminal to the second cloud server; and send an uplink inquiry delay instruction to the second application of the target terminal through the first application; the second cloud server is associated and interacted with the second application of the target terminal;

[0032] A second module, configured to establish a connection link between the second cloud server and the second application based on the identification information;

[0033] A third module, configured to, when there is data to be sent down in the second cloud server, send a downlink data packet to the second application based on the connection link;

[0034] A fourth module, configured to delay the uplink inquiry of the second application to the second cloud server by one period based on the uplink inquiry delay instruction.

[0035] Optionally, the device further includes:

[0036] A fifth module, configured to obtain the IP protocol stacks of the first application and the second application;

[0037] A sixth module, configured to, when the first application and the second application use different IP protocol stacks, not send an uplink inquiry delay instruction to the second application of the target terminal through the first application.

[0038] Optionally, when the second application uses a domain name to be associated and interacted with the second cloud server, the device further includes:

[0039] A seventh module, configured to locate the target terminal based on the identification information; and then obtain the domain name of the second application from the target terminal;

[0040] An eighth module, configured to obtain the IP address corresponding to the domain name from the non-volatile storage of the target terminal based on the domain name;

[0041] A ninth module, configured to, when an IP address is obtained from the non-volatile storage, establish a connection link between the second cloud server and the second application according to the IP address;

[0042] The tenth module is used to perform a DNS query based on a domain name to obtain an IP address corresponding to the domain name when the IP address cannot be obtained from non-volatile storage; and then store the IP address in the non-volatile storage.

[0043] Optionally, the device further includes:

[0044] The eleventh module is used to obtain the storage time of the IP address when the IP address is obtained from non-volatile storage;

[0045] The twelfth module is used to establish a connection link between the second cloud server and the second application using the domain name when the time interval between the storage time and the current time exceeds a preset period.

[0046] Optionally, the device further includes at least one of the following:

[0047] The thirteenth module is used to perform a DNS query regularly, and then update the IP address in the non-volatile storage periodically according to the result of the DNS query;

[0048] The fourteenth module is used to perform a DNS query when the second application receives a downlink data packet from the second cloud server, and then update the IP address in the non-volatile storage according to the result of the DNS query;

[0049] The fifteenth module is used to perform a DNS query before the second application sends an uplink inquiry packet to the second cloud server, and then update the IP address in the non-volatile storage according to the result of the DNS query.

[0050] On the other hand, an embodiment of the present invention provides an electronic device, including: a processor and a memory; the memory is used to store a program; the processor executes the program to implement the above-mentioned message interaction linkage method.

[0051] On the other hand, an embodiment of the present invention provides a computer storage medium, in which a program executable by a processor is stored, and the program executable by the processor is used to implement the above-mentioned message interaction linkage method when executed by the processor.

[0052] In an embodiment of the present invention, in response to the message interaction between a first application of a target terminal and a first cloud server, the identification information of the target terminal is sent to a second cloud server; and an uplink inquiry delay instruction is sent to a second application of the target terminal through the first application; the second cloud server is associated and interacted with the second application of the target terminal; based on the identification information, a connection link between the second cloud server and the second application is established; when there is data to be sent down in the second cloud server, a downlink data message is sent to the second application based on the connection link; based on the uplink inquiry delay instruction, the uplink inquiry of the second application to the second cloud server is delayed by one cycle. In an embodiment of the present invention, by establishing linkages between multiple applications in the terminal and between multiple cloud services, one application helps the cloud of another application to know that the terminal is in a state where downlink is reachable, realizing the automatic push of downlink messages, reducing the action of the terminal waking up from low power consumption to actively send an uplink inquiry, and saving the power consumption and data traffic of the terminal. Description of the Drawings

[0053] The drawings are used to provide a further understanding of the technical solutions of the present invention, and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the technical solutions of the present invention, and do not constitute a limitation to the technical solutions of the present invention.

[0054] Figure 1 It is a schematic diagram of an implementation environment for message interaction linkage provided by an embodiment of the present invention;

[0055] Figure 2 It is a schematic flowchart of a message interaction linkage method provided by an embodiment of the present invention;

[0056] Figure 3 It is a schematic diagram of an example of a message interaction linkage application scenario provided by an embodiment of the present invention;

[0057] Figure 4 It is a schematic diagram of another example of a message interaction linkage application scenario provided by an embodiment of the present invention;

[0058] Figure 5 It is a schematic diagram of the process principle for regularly performing DNS queries provided by an embodiment of the present invention;

[0059] Figure 6 It is a schematic diagram of the process principle for performing DNS queries when receiving a downlink message provided by an embodiment of the present invention;

[0060] Figure 7 It is a schematic diagram of the process principle for performing DNS queries before sending an uplink inquiry message provided by an embodiment of the present invention;

[0061] Figure 8 It is a schematic diagram of the structure of a message interaction linkage device provided by an embodiment of the present invention;

[0062] Figure 9 A schematic structural diagram of an electronic device provided by an embodiment of the present invention;

[0063] Figure 10 A block diagram of a computer system structure of an electronic device suitable for implementing the embodiment of the present invention provided by the embodiment of the present invention. Detailed implementation manners

[0064] In order to make the objectives, technical solutions and advantages of the present invention clearer and more understandable, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0065] It should be noted that although functional module division is performed in the system schematic diagram and the logical sequence is shown in the flowchart, in some cases, the steps shown or described may be executed in a different module division in the system or a different sequence in the flowchart. The terms "first / S100", "second / S200", etc. in the description, claims and the above-mentioned drawings are used to distinguish similar objects and do not necessarily need to describe a specific order or sequence.

[0066] Referring to "embodiment" herein means that a specific feature, structure or characteristic described in connection with the embodiment may be included in at least one embodiment of the present invention. The phrase appears in various places in the specification and does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art will explicitly and implicitly understand that the embodiments described herein can be combined with other embodiments.

[0067] For the convenience of understanding the technical solutions of the present invention, first, professional technical terms that may appear in the embodiments of the present invention will be explained:

[0068] PSM (Power Saving Mode): Power saving mode.

[0069] DNS (Domain Name System): Domain Name System, which is a service of the Internet. As a distributed database that maps domain names and IP addresses to each other, it enables people to access the Internet more conveniently.

[0070] IMEI: International Mobile Equipment Identity, which is usually referred to as the mobile phone serial number or the mobile phone "IMEI number". It is used to identify each independent mobile communication device such as a mobile phone in the mobile phone network and is equivalent to the ID card of the mobile phone. The serial number consists of 15 to 17 digits. The first 8 digits (TAC) are the model approval numbers (6 digits in the early days) and are used to distinguish the mobile phone brand and model.

[0071] It can be understood that the message interaction linkage method provided by the embodiments of the present invention can be applied to any computer device with data processing and computing capabilities, and this computer device can be various types of terminals or servers. When the computer device in the embodiment is a server, the server is an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud data blocks, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. Optionally, the terminal is a smart phone, a tablet computer, a laptop computer, a desktop computer, etc., but is not limited thereto.

[0072] As Figure 1 shown, it is a schematic diagram of an implementation environment provided by the embodiments of the present invention. Referring to Figure 1 , the implementation environment includes at least one terminal 102 and a server 101. The terminal 102 and the server 101 can be network-connected wirelessly or wiredly to complete data transmission and exchange.

[0073] The server 101 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud data blocks, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms.

[0074] In addition, the server 101 can also be a node server in a blockchain network. Among them, the blockchain is a new application mode of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, and encryption algorithms.

[0075] The terminal 102 may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, etc., but is not limited thereto. The terminal 102 and the server 101 may be directly or indirectly connected through wired or wireless communication means, and the embodiments of the present invention do not limit this here.

[0076] Exemplarily based on Figure 1 the implementation environment shown, the embodiments of the present invention provide a message interaction linkage method. Taking the application of this message interaction linkage method to the server 101 as an example for illustration, it can be understood that this message interaction linkage method can also be applied to the terminal 102.

[0077] Referring to Figure 2 , Figure 2 is a flowchart of the message interaction linkage method applied to the server provided by the embodiments of the present invention. The execution subject of this message interaction linkage method may be any of the foregoing computer devices (including the server or the terminal). Referring to Figure 2 , the method includes the following steps:

[0078] S100. In response to the message interaction between the first application of the target terminal and the first cloud server, send the identification information of the target terminal to the second cloud server; and send an uplink inquiry delay instruction to the second application of the target terminal through the first application;

[0079] It should be noted that the second cloud server is associated and interacts with the second application of the target terminal; in some embodiments, in response to the message interaction between the first application of the target terminal and the first cloud server, sending the identification information of the target terminal to the second cloud server may include: when the first cloud server receives the uplink message of the first application of the target terminal, sending the identification information of the target terminal to the second cloud server through the first cloud server.

[0080] Exemplarily, the first application and the second application in the embodiments of the present invention are not limited to a single specific application; in some specific embodiments, for example, the uplink and downlink message interactions between the terminal application A and the cloud server A are relatively frequent, while the terminal application B only needs to occasionally receive the data messages sent by the cloud server B. The terminal application B sends an uplink message to the cloud server B every communication cycle (for example: 7 days) to inquire whether there are data messages to be sent down. When the terminal application A and the cloud server A perform uplink and downlink message interactions, the cloud server A sends the identification information of the terminal (which may include the terminal IMEI and the terminal IP address) to the cloud server B, so that the cloud server B knows that the terminal has woken up from the low-power state at this time and is in a state where it can receive downlinks. At the same time, the terminal application A knows the timing when the cloud server A sends the terminal IP address to the cloud server B, and the terminal application A can send an uplink inquiry delay instruction to the terminal application B.

[0081] S200. Establish a connection link between the second cloud server and the second application based on the identification information.

[0082] It should be noted that the identification information includes the International Mobile Equipment Identity (IMEI) and the IP address of the target terminal. In some embodiments, step S200 may include: locating the target terminal based on the IMEI; establishing a connection link between the second cloud server and the second application according to the IP address. Among them, the IMEI is used to indicate which target terminal it is when the first cloud server notifies the second cloud server.

[0083] It should be noted that the connection link in the embodiments of the present invention represents a virtual data transmission channel established based on a protocol, without a physical reference. For example, it can implement a data packet-based transmission method through the UDP (User Datagram Protocol). Among them, UDP is a connectionless protocol.

[0084] S300. When there is data to be sent down in the second cloud server, send a downlink data packet to the second application based on the connection link.

[0085] Exemplarily, in some specific embodiments, taking the scenario of the specific embodiment in step S100 as an example, when the terminal application B is in a state where downlink is reachable, if the cloud server B has data to be sent down, push a downlink data packet to the terminal application B; if there is no data packet to be sent down, do not push a downlink data packet to the terminal application B.

[0086] It should be noted that the second cloud server uses the IP address of the target terminal to send a downlink packet to this IP address. After the downlink packet is delivered to this IP address, the second application in the target terminal receives the packet. The second application can receive the packet. A common way can be a pre-agreed port number specified when the packet is delivered.

[0087] S400. Based on the uplink inquiry delay instruction, delay the uplink inquiry of the second application to the second cloud server by one cycle.

[0088] Exemplarily, in some specific embodiments, taking the scenario of the specific embodiment in step S100 as an example, the terminal application A knows the timing when the cloud server A sends the terminal IP address to the cloud server B. The terminal application A delays the time when the terminal application B sends an uplink inquiry packet to the cloud server B by one communication cycle, thereby saving terminal power consumption and traffic.

[0089] Among them, in some embodiments, the method may further include: obtaining the IP protocol stacks of the first application and the second application; when the first application and the second application adopt different IP protocol stacks, not sending an uplink inquiry delay instruction to the second application of the target terminal through the first application.

[0090] Exemplarily, in some specific embodiments, the terminal may support both IPv4 and IPv6 stacks, and multiple application tasks running on the terminal independently decide to use the IPv4 or IPv6 protocol to interact with their respective cloud applications for message exchange. When terminal application A and terminal application B use different IP protocol stacks to communicate with the cloud, application A cannot help application B achieve the aforementioned automatic push of downlink messages.

[0091] For example, application A uses IPv4 and application B uses IPv6. The cloud server A sends the IPv4 address of the terminal to the cloud server B, and the cloud server B sends a message to the IPv4 address of the terminal. However, terminal application B only enables the function of receiving downlink messages for the IPv6 protocol. After the downlink message of this IPv4 arrives at the terminal, no application task receives and processes the message, and the message is discarded.

[0092] When terminal application A notifies terminal application B to delay the time for the next uplink inquiry message to be sent to cloud server B, it first determines whether the IP protocol stacks of terminal application A and terminal application B are the same. If they are the same, the time for application B to send the next uplink inquiry message is delayed. If they are different, the sending time of the uplink inquiry message remains unchanged.

[0093] It should be noted that in some embodiments, when the second application uses a domain name to interact with the second cloud server, the method may further include: locating the target terminal based on the identification information; then obtaining the domain name of the second application from the target terminal; based on the domain name, obtaining the IP address corresponding to the domain name in the non-volatile storage of the target terminal; when the IP address is obtained in the non-volatile storage, establishing a connection link between the second cloud server and the second application according to the IP address; when the IP address is not obtained in the non-volatile storage, performing a DNS query based on the domain name to obtain the IP address corresponding to the domain name; and then storing the IP address in the non-volatile storage.

[0094] Exemplarily, in some specific embodiments, when terminal application B uses a domain name to establish a connection with the cloud, if the domain name is used every time application B enables the receiving function, DNS query message interaction will occur, consuming the terminal's battery power and data traffic. To minimize the number of DNS queries, the IP address corresponding to the domain name is saved in the non-volatile memory (abbreviated as NVM) of the terminal for recent use.

[0095] When terminal application B uses a domain name to establish a connection with the cloud:

[0096] If the IP address corresponding to this domain name is not saved locally on the terminal, perform a DNS query, use the IP address in the DNS response as the IP address of cloud service B, and save the IP address in the DNS response in the non-volatile storage of the terminal locally.

[0097] If the IP address corresponding to this domain name has been saved locally on the terminal:

[0098] If the protocol stack of the IP address corresponding to this domain name saved locally is the same as the protocol stack used by application B, do not perform a DNS query and directly use the IP address saved locally.

[0099] If the protocol stack of the IP address corresponding to this domain name saved locally is different from the protocol stack used by application B, perform a DNS query, use the IP address in the DNS response as the IP address of the cloud server, and save the IP address in the DNS response in the non-volatile storage of the terminal locally.

[0100] Among them, in some embodiments, the method may further include: when obtaining an IP address from non-volatile storage, obtaining the storage time of the IP address; when the time interval between the storage time and the current moment exceeds a preset period, establish a connection link between the second cloud server and the second application using the domain name.

[0101] Exemplarily, in some specific embodiments, the terminal non-volatile storage saves the moment of the last DNS query. When the terminal application B newly establishes a connection with cloud service B, if the current moment exceeds 7 days from the moment of the last DNS query (corresponding to the storage time), it is considered that the IP address obtained from the last DNS query has expired, establish a connection with cloud service B using the domain name, and perform a DNS query during this process, and save the IP address in the DNS response in the non-volatile storage of the terminal locally.

[0102] Among them, in some embodiments, the method may further include at least one of the following:

[0103] Perform a DNS query regularly, and then periodically update the IP address in the non-volatile storage according to the result of the DNS query;

[0104] Exemplarily, in some specific embodiments, based on a preset period (such as 7 days), the terminal non-volatile storage saves the moment of the last DNS query. If the current moment exceeds 7 days from the moment of the last DNS query, perform a DNS query, and save the IP address in the DNS response in the non-volatile storage of the terminal locally.

[0105] When the second application receives a downlink data packet from the second cloud server, perform a DNS query, and then update the IP address in the non-volatile storage according to the result of the DNS query;

[0106] Exemplarily, in some specific embodiments, when the message receiving thread receives a downlink data message sent by cloud service B, if an uplink message needs to be replied originally, before sending this uplink message, a connection with cloud service B is re-established using the domain name. During this process, a DNS query will be performed, and the IP address of the DNS response will be saved in the non-volatile storage of the terminal local. If no uplink message is to be replied, a connection with cloud service B is immediately re-established using the domain name.

[0107] Before the second application sends an uplink inquiry message to the second cloud server, a DNS query is performed, and then the IP address in the non-volatile storage is updated according to the result of the DNS query.

[0108] Exemplarily, in some specific embodiments, if no downlink message automatically pushed by cloud service B has been received for a long time, when the sending time of the preset uplink inquiry message arrives, before sending the uplink inquiry message, a connection with cloud service B is re-established using the domain name. During this process, a DNS query will be performed, and the IP address of the DNS response will be saved in the non-volatile storage of the terminal local.

[0109] To explain the principle of the technical solution of the present invention in detail, the overall process of the present invention will be described below in conjunction with some specific embodiments. It is easy to understand that the following is an explanation of the technical principle of the present invention and should not be regarded as a limitation of the present invention.

[0110] First of all, it should be noted that in order to save the terminal power consumption, the Internet of Things terminal of cellular mobile communication will enter the low power consumption mode during the period when no data communication is carried out. If the terminal enables the PSM (Power Saving Mode) function, the terminal does not listen for network paging and is in a downlink unreachable state and cannot receive downlink data messages.

[0111] For low-power Internet of Things terminals, when they want to obtain downlink data messages, they usually need to first send an uplink message to notify the cloud that this terminal is in a downlink reachable state, and then the cloud sends a downlink data message to the terminal.

[0112] With the application and promotion of IPv6, the applications in the Internet of Things terminal will gradually support IPv6. When multiple application tasks are running simultaneously in the Internet of Things terminal, each application task can independently decide to use IPv4 or IPv6 to communicate with the cloud.

[0113] The deployed low-power Internet of Things terminals, such as NB-IoT terminals, usually establish communication with the cloud using the IP address of the cloud service. For the flexibility of the cloud service deployment, the Internet of Things terminal is also gradually turning to establish a communication connection with the cloud service using the domain name.

[0114] Multiple application tasks are running simultaneously in a low-power mobile IoT terminal. Some applications in the terminal frequently exchange uplink and downlink data messages with the cloud; some applications only need to occasionally receive data messages sent by the cloud. In order to let the cloud know that the terminal has woken up from a low-power state and is reachable downlink, the terminal application asks the cloud whether there are data messages to be sent every communication cycle. Terminal applications that occasionally receive messages sent by the cloud wake up from a low-power state every communication cycle to initiate an uplink inquiry message. There may be no data messages to be sent from the cloud, but the action of waking up from low power and performing data communication will consume the terminal's battery power and data traffic.

[0115] In view of the shortcomings of the existing message interaction logic, an embodiment of the present invention sends the terminal identification and terminal IP address to the cloud server of another application in the terminal through the cloud server of an application in the terminal, so that the cloud server of another application knows that the terminal has woken up from a low-power state and is in a downlink reachable state. If there is data to be sent, the downlink data message can be pushed to another application in the terminal. At the same time, the sending time of the uplink inquiry message of another application in the terminal is delayed by one communication cycle.

[0116] When the terminal runs in IPv4 and IPv6 dual-stack mode, if different applications use different IP protocol stacks to interact with the cloud, the downlink message push mechanism linked between the above applications will become invalid, and the sending time of the uplink inquiry message of another application in the terminal will not be extended by one communication cycle.

[0117] When a terminal application uses a domain name to establish a connection with a cloud service, the terminal application saves the IP address corresponding to the domain name in non-volatile storage for recent use, avoiding DNS queries every time the downlink message receiving function is turned on, which consumes terminal battery power and data traffic.

[0118] The following describes in detail various possible specific application scenarios of the embodiments of the present invention:

[0119] like Figure 3 As shown, the uplink and downlink message interactions between terminal application A and cloud server A are relatively frequent.

[0120] Terminal application B only needs to occasionally receive data messages sent by cloud server B. Terminal application B sends an uplink message to cloud server B every other communication cycle (for example, 7 days) to inquire whether there are data messages to be sent.

[0121] When the terminal application A and the cloud server A perform uplink and downlink message interactions, the cloud server A sends the terminal IMEI and the terminal IP address to the cloud server B, so that the cloud server B knows that the terminal has woken up from the low-power state at this time and is in a state where downlink is reachable. If there is data to be sent down, it pushes a downlink data message to the terminal application B. If there is no message to be sent down, it does not push a downlink data message to the terminal application B.

[0122] The terminal application A knows the timing when the cloud server A sends the terminal IP address to the cloud server B. The terminal application A extends the time when the terminal application B will send an uplink inquiry message to the cloud server B next time by one communication cycle, thereby saving terminal power consumption and traffic.

[0123] Exemplarily, in some specific embodiments, the method of the embodiment of the present invention needs to handle the following several special cases when applied:

[0124] One case is when the terminal supports different IP protocol stacks:

[0125] For example, if the terminal supports both IPv4 and IPv6 stacks, multiple application tasks running on the terminal independently decide to use the IPv4 or IPv6 protocol to perform message interactions with their respective cloud applications. When the terminal application A and the terminal application B use different IP protocol stacks to communicate with the cloud, application A cannot help application B achieve the aforementioned automatic push of downlink messages.

[0126] For example, as Figure 4 shown, application A uses IPv4 and application B uses IPv6. The cloud server A sends the terminal's IPv4 address to the cloud server B, and the cloud server B sends a message to the terminal's IPv4 address. However, only the function of receiving downlink messages for the IPv6 protocol is enabled for the terminal application B on the terminal. When this IPv4 downlink message arrives at the terminal, no application task receives and processes the message, and the message is discarded.

[0127] When the terminal application A notifies the terminal application B to delay the time when it sends an uplink inquiry message to the cloud server B next time, it first determines whether the IP protocol stacks of the terminal application A and the terminal application B are the same. If they are the same, it delays the time when application B sends an uplink inquiry message next time. If they are different, it does not change the sending time of the uplink inquiry message.

[0128] Another case is when communicating using domain names:

[0129] Since the terminal application B does not know when a downlink data message will arrive, the message receiving function of the terminal application B needs to run continuously, but it only occasionally receives a downlink data message from the cloud.

[0130] When the terminal application B establishes a connection with the cloud using a domain name, if the domain name is used every time the application B enables the receiving function, DNS query messages will be exchanged, consuming the terminal's battery power and data traffic. To minimize the number of DNS queries, the IP address corresponding to the domain name is saved in the non-volatile storage of the terminal for recent use.

[0131] When the terminal application B establishes a connection with the cloud using a domain name:

[0132] If the IP address corresponding to this domain name is not saved locally on the terminal, a DNS query is performed, and the IP address in the DNS response is used as the IP address of the cloud service B, and the IP address in the DNS response is saved in the non-volatile storage of the terminal local.

[0133] If the IP address corresponding to this domain name is already saved locally on the terminal:

[0134] If the protocol stack of the IP address corresponding to this domain name saved locally is the same as the protocol stack used by application B, no DNS query is performed, and the locally saved IP address is directly used.

[0135] If the protocol stack of the IP address corresponding to this domain name saved locally is different from the protocol stack used by application B, a DNS query is performed, and the IP address in the DNS response is used as the IP address of the cloud server, and the IP address in the DNS response is saved in the non-volatile storage of the terminal local.

[0136] When the terminal application B establishes a connection with the cloud using a domain name, the IP address corresponding to the domain name is saved locally for recent use. To avoid the terminal being unaware when the IP address corresponding to the domain name changes, it is necessary to select an appropriate time to perform a DNS query to update the IP address corresponding to the domain name saved locally, including but not limited to the following update methods:

[0137] Method 1: Perform DNS queries regularly:

[0138] As Figure 5 shown, for example: The time of the last DNS query is saved in the non-volatile storage of the terminal. When the terminal application B newly establishes a connection with the cloud service B, if the current time exceeds 7 days from the time of the last DNS query, it is considered that the IP address obtained from the last DNS query has expired. Use the domain name to establish a connection with the cloud service B, and a DNS query will be performed during this process, and the IP address in the DNS response will be saved in the non-volatile storage of the terminal local.

[0139] Method 2: Perform DNS queries when sending and receiving messages (update after receiving a downstream message):

[0140] As Figure 6 shown, for example, each of the message receiving and message sending of application B in the terminal uses a thread.

[0141] When the message receiving thread receives the downlink data message sent by cloud service B, if an uplink message needs to be replied originally, before sending this uplink message, re - establish a connection with cloud service B using the domain name. During this process, DNS query will be performed, and the IP address of the DNS response will be saved in the non - volatile storage of the terminal local. If no uplink message is to be replied, immediately re - establish a connection with cloud service B using the domain name.

[0142] Method 3: Perform DNS query when sending and receiving messages (update before sending the uplink inquiry message):

[0143] Such as Figure 7 As shown, if the downlink message automatically pushed by cloud service B has not been received for a long time, when the sending time of the preset uplink inquiry message arrives, before sending the uplink inquiry message, re - establish a connection with cloud service B using the domain name. During this process, DNS query will be performed, and the IP address of the DNS response will be saved in the non - volatile storage of the terminal local.

[0144] In summary, for low - power IoT terminals, if they want to obtain downlink data messages, they usually need to send an uplink message first to notify the cloud that this terminal is in a downlink - reachable state. The embodiments of the present invention establish linkages between multiple applications in the terminal and between multiple cloud services, and one application helps another application to achieve automatic push of downlink messages, reducing the active uplink inquiry actions of the terminal waking up from low - power state, saving the power consumption and data traffic of the terminal.

[0145] On the other hand, as Figure 8 shown, the embodiments of the present invention provide a message interaction linkage device 800, including: a first module 810, configured to, in response to the message interaction between the first application of the target terminal and the first cloud server, send the identification information of the target terminal to the second cloud server; and send an uplink inquiry delay instruction to the second application of the target terminal through the first application; the second cloud server is associated and interacts with the second application of the target terminal; a second module 820, configured to establish a connection link between the second cloud server and the second application based on the identification information; a third module 830, configured to, when there is data to be sent down in the second cloud server, send a downlink data message to the second application based on the connection link; a fourth module 840, configured to delay the uplink inquiry of the second application to the second cloud server by one period based on the uplink inquiry delay instruction.

[0146] In some embodiments, the device may further include: a fifth module, configured to obtain the IP protocol stacks of the first application and the second application; a sixth module, configured to, when the first application and the second application adopt different IP protocol stacks, not send an uplink inquiry delay instruction to the second application of the target terminal through the first application.

[0147] In some embodiments, when the second application associates and interacts with the second cloud server using a domain name, the apparatus may further include: a seventh module, configured to locate a target terminal based on identification information; and then obtain the domain name of the second application from the target terminal; an eighth module, configured to obtain an IP address corresponding to the domain name in the non-volatile storage of the target terminal based on the domain name; a ninth module, configured to establish a connection link between the second cloud server and the second application according to the IP address when the IP address is obtained in the non-volatile storage; a tenth module, configured to perform a DNS query based on the domain name to obtain an IP address corresponding to the domain name when the IP address is not obtained in the non-volatile storage; and then store the IP address in the non-volatile storage.

[0148] In some embodiments, the apparatus may further include: an eleventh module, configured to obtain the storage time of the IP address when the IP address is obtained in the non-volatile storage; a twelfth module, configured to establish a connection link between the second cloud server and the second application using the domain name when the time interval between the storage time and the current moment exceeds a preset period.

[0149] In some embodiments, the apparatus may further include at least one of the following: a thirteenth module, configured to perform a DNS query regularly, and then periodically update the IP address in the non-volatile storage according to the result of the DNS query; a fourteenth module, configured to perform a DNS query when the second application receives a downlink data packet from the second cloud server, and then update the IP address in the non-volatile storage according to the result of the DNS query; a fifteenth module, configured to perform a DNS query before the second application sends an uplink inquiry packet to the second cloud server, and then update the IP address in the non-volatile storage according to the result of the DNS query.

[0150] The content of the method embodiments of the present invention is applicable to the apparatus embodiments of the present invention. The functions specifically implemented by the apparatus embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those of the above methods.

[0151] On the other hand, as Figure 9 shown, an embodiment of the present invention further provides an electronic device 900, which includes at least one processor 910, and further includes at least one memory 920 for storing at least one program; taking one processor 910 and one memory 920 as an example.

[0152] The processor 910 and the memory 920 may be connected through a bus or other means.

[0153] The memory 920, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. In addition, the memory 920 may include high-speed random access memory and may also include non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices. In some embodiments, the memory 920 may optionally include memories that are remotely located relative to the processor, and these remote memories can be connected to the device through a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0154] The embodiments of the electronic device described above are merely illustrative. The units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0155] Specifically, Figure 10 Schematically shows a block diagram of a computer system of an electronic device for implementing the embodiments of the present invention.

[0156] It should be noted that Figure 10 The computer system 1000 of the electronic device shown is only an example and should not impose any limitations on the functions and usage scope of the embodiments of the present invention.

[0157] As Figure 10 shown, the computer system 1000 includes a central processing unit 1001 (Central Processing Unit, CPU), which can perform various appropriate actions and processes according to the program stored in the read-only memory 1002 (Read-Only Memory, ROM) or the program loaded from the storage section 1008 into the random access memory 1003 (Random Access Memory, RAM). In the random access memory 1003, various programs and data required for system operation are also stored. The central processing unit 1001, the read-only memory 1002, and the random access memory 1003 are connected to each other through a bus 1004. The input / output interface 1005 (Input / Output interface, that is, I / O interface) is also connected to the bus 1004.

[0158] The following components are connected to the input / output interface 1005: an input section 1006 including a keyboard, a mouse, etc.; an output section 1007 including such as a cathode ray tube (CRT), a liquid crystal display (LCD), etc. and a speaker, etc.; a storage section 1008 including a hard disk, etc.; and a communication section 1009 including a network interface card such as a local area network card, a modem, etc. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the input / output interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is mounted on the drive 1010 as needed so that a computer program read from it is installed into the storage section 1008 as needed.

[0159] Specifically, according to an embodiment of the present invention, the processes described in each method flowchart can be implemented as a computer software program. For example, an embodiment of the present invention includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes program codes for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 1009, and / or installed from the removable medium 1011. When the computer program is executed by the central processing unit 1001, various functions defined in the system of the present invention are executed.

[0160] It should be noted that the computer-readable medium shown in the embodiments of the present invention can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of the computer-readable storage medium can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, the computer-readable storage medium can be any tangible medium that contains or stores a program, and this program can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present invention, a computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, and this computer-readable medium can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0161] Another aspect of the embodiments of the present invention also provides a computer-readable storage medium, and the storage medium stores a program, and the program is executed by a processor to implement the previous method.

[0162] The content of the method embodiments of the present invention is applicable to the embodiments of this computer-readable storage medium. The functions specifically implemented by the embodiments of this computer-readable storage medium are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method.

[0163] The embodiments of the present invention also disclose a computer program product or a computer program. The computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device can read the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the previous method.

[0164] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagram may represent a module, a segment of a program, or a portion of code that contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions noted in the blocks may occur in a different order than that noted in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, or they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, and combinations of blocks in the block diagram or flowchart, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or by a combination of dedicated hardware and computer instructions.

[0165] It should be noted that although several modules of devices for action execution are mentioned in the above detailed description, such a division is not mandatory. In fact, according to the embodiments of the present invention, the features and functions of two or more of the above-described modules or units can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0166] From the description of the above embodiments, those skilled in the art can easily understand that the example embodiments described herein can be implemented by software, or by a combination of software and necessary hardware. Therefore, the technical solutions according to the embodiments of the present invention can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the embodiments of the present invention.

[0167] In some alternative embodiments, the functions / operations mentioned in the block diagram may not occur in the order mentioned in the operation diagram. For example, depending on the functions / operations involved, two consecutive blocks shown may actually be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order. In addition, the embodiments presented and described in the flowcharts of the present invention are provided by way of example for the purpose of providing a more comprehensive understanding of the technology. The disclosed methods are not limited to the operations and logical flows presented herein. Alternative embodiments are contemplated, in which the order of various operations is changed and in which sub-operations described as part of a larger operation are executed independently.

[0168] In addition, although the present invention has been described in the context of functional modules, it should be understood that, unless otherwise stated to the contrary, one or more of the functions and / or features may be integrated in a single physical device and / or software module, or one or more functions and / or features may be implemented in separate physical devices or software modules. It should also be understood that a detailed discussion of the actual implementation of each module is not necessary for understanding the present invention. Rather, given the attributes, functions, and internal relationships of the various functional modules in the devices disclosed herein, the actual implementation of the modules will be understood within the ordinary skills of an engineer. Thus, those skilled in the art can implement the present invention as set forth in the claims without undue experimentation. It should also be understood that the specific concepts disclosed are merely illustrative and are not intended to limit the scope of the present invention, which is determined by the full scope of the appended claims and their equivalents.

[0169] If a function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of the various embodiments of the present invention. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical discs that can store program codes.

[0170] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a defined sequence of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by an instruction execution device, apparatus, or equipment (such as a computer-based device, a device including a processor, or other devices that can fetch and execute instructions from the instruction execution device, apparatus, or equipment), or in combination with such instruction execution devices, apparatuses, or equipment. For the purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by or in connection with an instruction execution device, apparatus, or equipment.

[0171] More specific examples (a non-exhaustive list) of computer-readable media include the following: an electrical connection (electronic device) having one or more wirings, a portable computer diskette (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable media can even be paper or other suitable media on which a program can be printed, as the program can be obtained electronically, for example, by optically scanning the paper or other media, followed by editing, interpretation, or otherwise processing it as appropriate, and then storing it in a computer memory.

[0172] It should be understood that various parts of the present invention can be implemented by hardware, software, firmware, or a combination thereof. In the above-described embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution device. For example, if implemented in hardware, as in another embodiment, any one or a combination of the following techniques well known in the art can be used: a discrete logic circuit having logic gate circuits for implementing logical functions on data signals, an application specific integrated circuit having appropriate combinational logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0173] In the description of this specification, the descriptions referring to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples", etc. mean that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0174] Although the embodiments of the present invention have been shown and described, those of ordinary skill in the art can understand that various changes, modifications, substitutions, and variations can be made to these embodiments without departing from the principles and spirit of the present invention, and the scope of the present invention is defined by the claims and their equivalents.

[0175] The above has specifically described the preferred embodiments of the present invention, but the present invention is not limited to the embodiments. Those skilled in the art can also make various equivalent deformations or substitutions without departing from the spirit of the present invention, and these equivalent deformations or substitutions are all included in the scope defined by the claims of the present invention.

Claims

1. A message interaction linkage method, characterized in that, Including: In response to the message interaction between the first application of the target terminal and the first cloud server, sending the identification information of the target terminal to the second cloud server; and sending an uplink inquiry delay instruction to the second application of the target terminal through the first application; the second cloud server is associated and interacts with the second application of the target terminal; the associated interaction means that the second application of the target terminal sends an uplink message to the second cloud server every other communication cycle. Based on the identification information, establish a connection link between the second cloud server and the second application; the connection link represents a virtual data transmission channel built based on a protocol. When there is data to be sent down in the second cloud server, send a downlink data message to the second application based on the connection link. Based on the uplink inquiry delay instruction, delay the uplink inquiry of the second application to the second cloud server by one cycle. Wherein, the method further includes: Obtain the IP protocol stacks of the first application and the second application. When the first application and the second application use different IP protocol stacks, do not send the uplink inquiry delay instruction to the second application of the target terminal through the first application.

2. The message interaction linkage method according to claim 1, characterized in that, The step of sending the identification information of the target terminal to the second cloud server in response to the message interaction between the first application of the target terminal and the first cloud server includes: When the first cloud server receives the uplink message of the first application of the target terminal, send the identification information of the target terminal to the second cloud server through the first cloud server.

3. The message interaction linkage method according to claim 1, characterized in that, The identification information includes the International Mobile Equipment Identity (IMEI) and the IP address of the target terminal; the step of establishing a connection link between the second cloud server and the second application based on the identification information includes: Locate the target terminal based on the International Mobile Equipment Identity (IMEI). Establish a connection link between the second cloud server and the second application of the target terminal according to the IP address.

4. The message interaction linkage method according to claim 1, characterized in that, When the second application uses a domain name to be associated and interact with the second cloud server, the method further includes: Locate the target terminal based on the identification information; and then obtain the domain name of the second application from the target terminal. Based on the domain name, obtain the IP address corresponding to the domain name in the non-volatile storage of the target terminal. When the IP address is obtained in the non-volatile storage, establish a connection link between the second cloud server and the second application according to the IP address. When the IP address is not obtained in the non-volatile storage, perform a DNS query based on the domain name to obtain the IP address corresponding to the domain name; and then store the IP address in the non-volatile storage.

5. The message interaction linkage method according to claim 4, characterized in that, The method further includes: When the IP address is obtained in the non-volatile storage, obtain the storage time of the IP address. When the time interval between the storage time and the current time exceeds a preset period, establish a connection link between the second cloud server and the second application using the domain name.

6. The message interaction linkage method according to claim 4, characterized in that, The method further includes at least one of the following: Perform the DNS query regularly, and then update the IP address in the non-volatile storage periodically according to the result of the DNS query; When the second application receives the downlink data packet from the second cloud server, perform the DNS query, and then update the IP address in the non-volatile storage according to the result of the DNS query; Before the second application sends an uplink inquiry packet to the second cloud server, perform the DNS query, and then update the IP address in the non-volatile storage according to the result of the DNS query.

7. A message interaction linkage device, characterized in that, It includes: A first module, configured to, in response to the message interaction between the first application of the target terminal and the first cloud server, send the identification information of the target terminal to the second cloud server; and send an uplink inquiry delay instruction to the second application of the target terminal through the first application; the second cloud server is associated and interacted with the second application of the target terminal; the associated interaction indicates that the second application of the target terminal sends an uplink message to the second cloud server every other communication cycle; A second module, configured to establish a connection link between the second cloud server and the second application based on the identification information; the connection link represents a virtual data transmission channel established based on a protocol; A third module, configured to, when there is data to be sent down in the second cloud server, send a downlink data packet to the second application based on the connection link; A fourth module, configured to delay the uplink inquiry of the second application to the second cloud server by one cycle based on the uplink inquiry delay instruction; Wherein, the device further includes: A fifth module, configured to obtain the IP protocol stacks of the first application and the second application; A sixth module, configured to, when the first application and the second application adopt different IP protocol stacks, not send an uplink inquiry delay instruction to the second application of the target terminal through the first application.

8. An electronic device, characterized in that, It includes a processor and a memory; The memory is used to store programs; The processor executes the program to implement the method according to any one of claims 1 to 6.

9. A computer storage medium storing a program executable by a processor, characterized in that, The program executable by the processor, when executed by the processor, is used to implement the method according to any one of claims 1 to 6.

Images