CN113190778A - Business data pushing method, system, computer equipment and computer storage medium - Google Patents
Business data pushing method, system, computer equipment and computer storage medium Download PDFInfo
- Publication number
- CN113190778A CN113190778A CN202110483292.9A CN202110483292A CN113190778A CN 113190778 A CN113190778 A CN 113190778A CN 202110483292 A CN202110483292 A CN 202110483292A CN 113190778 A CN113190778 A CN 113190778A
- Authority
- CN
- China
- Prior art keywords
- server
- client
- target
- service data
- channel
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 55
- 108091006146 Channels Proteins 0.000 claims description 103
- 238000004422 calculation algorithm Methods 0.000 claims description 45
- 238000012795 verification Methods 0.000 claims description 14
- 238000004590 computer program Methods 0.000 claims description 11
- 238000004891 communication Methods 0.000 claims description 10
- 238000012545 processing Methods 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 230000003068 static effect Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008094 contradictory effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
- G06F9/505—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the load
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Data Mining & Analysis (AREA)
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a business data pushing method, which comprises the steps of obtaining a first instruction for requesting to obtain target business data, and indicating a first server to extract the target business data from a message queue according to the first instruction; determining a target client corresponding to the client identifier according to the client identifier in the target service data, wherein the client identifier is a session identifier generated based on the server name and the timestamp of a second server when the second server corresponding to the target client is connected with the target client; according to the first instruction and the client identification, instructing the first server to publish the target service data to a target publishing and subscribing channel corresponding to the target client; determining a second server according to the binding relationship of the target publish-subscribe channel in a preset database; and controlling the second server to send the target service data in the target publishing and subscribing channel to the target client. The invention greatly improves the stability, accuracy and safety of data push.
Description
Technical Field
The embodiment of the invention relates to the technical field of data processing, in particular to a business data pushing method, a business data pushing system, a computer device and a computer readable storage medium.
Background
With the development of the web of the world wide web and the richness of web application scenes, the use of the real-time pushing function of the web is more and more, and the requirement of a user on the real-time pushing is higher and higher.
With the change of business scenes and the upgrade of application architectures, the traditional web real-time push technology meets the challenges of high stability and high security. The inventor realizes that the traditional web real-time pushing technology applied to server cluster deployment only considers server cluster load balance, one server in a server cluster is controlled by a central server to acquire service data and push the service data to a client, the problem of push message loss is easy to occur in the data pushing process, the stability of the server pushed data is poor, and the data acquisition efficiency of the client is greatly influenced.
Disclosure of Invention
In view of this, embodiments of the present invention provide a service data pushing method, a service data pushing system, a computer device, and a computer-readable storage medium, which are used to solve the problem that, based on consideration of load balancing, in a process of pushing data to a client through a server in a server cluster, the pushed data is easily lost, so that data pushing efficiency is low.
The embodiment of the invention solves the technical problems through the following technical scheme:
a business data pushing method comprises the following steps:
receiving a first instruction, and instructing a first server to extract target service data from a message queue according to the first instruction, wherein the first instruction is used for requesting to acquire the target service data;
acquiring the target service data extracted by the first server, and determining a target client corresponding to the client identifier from one or more clients according to the client identifier in the target service data, wherein the client identifier is a session identifier generated based on the server name and the timestamp of a second server when the second server corresponding to the target client is connected with the target client;
according to the first instruction, determining a target publishing and subscribing channel corresponding to the target client, and instructing the first server to publish the target service data to the target publishing and subscribing channel corresponding to the target client;
determining the second server according to the binding relationship of the target publish-subscribe channel in a preset database; and
and instructing the second server to send the target service data in the target publishing and subscribing channel to the corresponding target client.
Optionally, before the step of receiving the first instruction, the method further comprises:
receiving connection requests sent by one or more clients in advance; and
and according to the connection request sent by each client, determining a second server corresponding to each client from the server cluster, so that each client establishes connection with the corresponding second server.
Optionally, the step of determining, according to the connection request sent by each client, a second server corresponding to each client from the server cluster, so that each client establishes a connection with the corresponding second server respectively includes:
according to the connection request, a second server corresponding to the client is determined in the server cluster, the second server is called to receive first handshake information sent by the client, and the first handshake information comprises a timestamp for sending a message;
controlling the second server to send second handshake information to the corresponding client, wherein the second handshake information includes an encryption algorithm associated with a timestamp of the message sending;
receiving third handshake information sent by the client, and controlling the second server and the corresponding client to establish an encrypted connection channel according to the third handshake information, wherein the third handshake information is generated based on the second handshake information and comprises encryption algorithm matching conclusion data or encryption algorithm mismatching conclusion data;
generating a connection feedback message corresponding to the client according to the encrypted connection channel, and sending the connection feedback message to the client corresponding to the second server, wherein the connection feedback message comprises a token packet header protection strategy;
controlling the second server to receive a token sent by a client corresponding to the second server through the encrypted connection channel, wherein the token is a character string reinforced through a corresponding token data packet header protection strategy; and
and verifying the token, generating a verification feedback message, and sending the verification feedback message to a client corresponding to a second server so as to realize the connection between the second server and the corresponding client through the verification feedback message.
Optionally, the step of receiving third handshake information sent by the client, and controlling establishment of an encrypted connection channel between the second server and the corresponding client according to the third handshake information further includes:
when the third handshake information comprises encryption algorithm mismatching conclusion data, controlling the second server to receive an encryption algorithm list sent by a corresponding client, wherein the encryption algorithm list comprises at least one candidate encryption algorithm;
controlling the second server to determine a target encryption algorithm from the encryption algorithm list;
controlling the second server to send fourth handshake information to the corresponding client, wherein the fourth handshake information comprises a target encryption algorithm;
controlling the second server to receive fifth handshake information sent by a corresponding client, wherein the fifth handshake information comprises encryption algorithm matching conclusion data; and
and controlling the second server and the corresponding client to establish an encrypted connection channel through a communication protocol and the fifth handshake information.
Optionally, before the step of obtaining the first instruction and controlling the first server to extract the target service data from the message queue according to the first instruction, the method further includes:
receiving a first instruction sent by the one or more clients through a central server; and
and distributing each first instruction to a first server in the server cluster through the central server according to the load balance of the server cluster.
Optionally, the method further comprises: creating and binding publish-subscribe channels in the preset database in advance, wherein the step of creating and binding publish-subscribe channels comprises the following steps:
acquiring a server name and an ip address of each second server in the server cluster;
combining the server name and the ip address of each second server to generate a publish-subscribe channel corresponding to each second server;
acquiring each client connected with each second server;
binding the server name of each second server, the corresponding publish-subscribe channel binding and the corresponding client to generate a key value pair corresponding to each second server, wherein the key value pair is used for representing the binding relationship among the second server, the corresponding publish-subscribe channel and the corresponding client; and
and storing the key value pair of each second server in the preset database.
Optionally, the step of controlling the first server to publish the target service data to a target publish-subscribe channel corresponding to the target client according to the first instruction includes:
traversing a preset database according to the first instruction to acquire a client identifier of the target client in the preset database, wherein the client identifier is used for representing an association relationship between the target client and a corresponding second server;
determining a target publishing and subscribing channel associated with the target client according to the client identifier of the target client in the preset database; and
and controlling the first server to publish the target service data to the target publishing and subscribing channel corresponding to the target client.
In order to achieve the above object, an embodiment of the present invention further provides a service data pushing system, including:
the acquisition module is used for acquiring a first instruction, wherein the first instruction is used for requesting to acquire target service data and controlling a first server to extract the target service data from a message queue according to the first instruction;
a first determining module, configured to determine, according to a client identifier in the target service data, a target client corresponding to the client identifier from the one or more clients;
the publishing module is used for controlling the first server to publish the target service data to a target publishing and subscribing channel corresponding to the target client according to the first instruction;
the second determining module is used for determining a second server according to the binding relationship of the target publishing and subscribing channel in a preset database; and
and the sending module is used for controlling the second server to send the service data in the target publishing and subscribing channel to the corresponding target client.
In order to achieve the above object, an embodiment of the present invention further provides a computer device, where the computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the service data pushing method when executing the computer program.
In order to achieve the above object, an embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored, where the computer program is executable by at least one processor, so as to cause the at least one processor to execute the steps of the service data pushing method described above.
According to the business data pushing method, the business data pushing system, the computer equipment and the computer readable storage medium, the second server corresponding to the client is determined through the first instruction and the binding relationship among the client, the target publishing and subscribing channel and the second server, the target business data is obtained from the target publishing and subscribing channel through the second server, and the target business data is sent to the corresponding target client. The client and the second server are associated through the client identifier, and business data are pushed through a publish-subscribe mechanism through the binding relationship between a target publish-subscribe channel and the second server; the stability, accuracy and security of data push have greatly been improved, and data push in time has improved user experience.
The invention is described in detail below with reference to the drawings and specific examples, but the invention is not limited thereto.
Drawings
Fig. 1 is a schematic diagram illustrating an environment application of a service data pushing method according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating steps of a business data pushing method according to a first embodiment of the present invention;
fig. 3 is a flowchart illustrating a step of connecting a client to a second server in a business data pushing method according to a first embodiment of the present invention;
fig. 4 is a flowchart of a step in which a client establishes a connection with a corresponding second server in a business data pushing method according to a first embodiment of the present invention;
fig. 5 is a flowchart illustrating steps of verifying a token in a service data pushing method according to a first embodiment of the present invention;
fig. 6 is a flowchart illustrating a step of distributing a first instruction in a business data pushing method according to a first embodiment of the present invention;
fig. 7 is a flowchart illustrating steps of creating and binding publish-subscribe channels in a service data push method according to a first embodiment of the present invention;
fig. 8 is a flowchart illustrating a step of associating a second server with a client identifier in a service data pushing method according to a first embodiment of the present invention;
fig. 9 is a schematic diagram of a program module of a service data pushing system according to a second embodiment of the present invention;
fig. 10 is a schematic hardware configuration diagram of a computer device according to a third embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the descriptions relating to "first", "second", etc. in the embodiments of the present invention are only for descriptive purposes and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In addition, technical solutions between various embodiments may be combined with each other, but must be realized by a person skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope of the present invention.
In the description of the present invention, it should be understood that the numerical references before the steps do not identify the order of performing the steps, but merely serve to facilitate the description of the present invention and to distinguish each step, and thus should not be construed as limiting the present invention.
Fig. 1 schematically shows an environment application diagram of a business data pushing method according to an embodiment of the present application. In an exemplary embodiment, the environment application schematic diagram includes a plurality of clients 10 and a server cluster, the server cluster includes a central server, a plurality of first servers 11, a plurality of second servers 12, and a plurality of publish-subscribe channels 13, wherein each client 10 is associated with a corresponding second server 12, and each second server 12 is bound with a corresponding publish-subscribe channel 13. Several clients 10 may be connected to one second server 12 in the server cluster via a network. The network may include, among other things, physical links such as coaxial cable links, twisted pair cable links, fiber optic links, and the like. The network may also include wireless links, such as cellular links, satellite links, Wi-Fi links, and the like. The network may be the internet.
The plurality of clients 10 are configured to send a first instruction to the server cluster to request to acquire target service data.
The central server is used as a computer device for controlling and calling the first server 11 or the second server 12 to provide the business data push service for the client 10.
And the first server 11 is configured to receive the first instruction under the control of the central server, extract target service data based on the first instruction, and send the target service data to the publish-subscribe channel 13 corresponding to the client 10.
And the second server 12 is configured to, under the control of the central server, acquire target service data from the publish-subscribe channel 13 corresponding to the client 10, and return the target service data to the client 10 corresponding to the second server 12.
The client 10 may be a PC (Personal Computer), a mobile phone, a tablet Computer, a notebook Computer, a virtual host, or the like. The first server 11 and the second server 12 may be rack servers, blade servers, tower servers, or rack servers.
One or more embodiments are provided below to describe a service data pushing scheme in detail.
Example one
Referring to fig. 2, a flowchart illustrating steps of a business data pushing method according to an embodiment of the invention is shown. It is to be understood that the flow charts in the embodiments of the present method are not intended to limit the order in which the steps are performed. The following description is exemplarily described by taking a central server in a server cluster as an execution subject, and specifically includes the following steps:
in an exemplary embodiment, the business data pushing method is applied to a system to realize real-time pushing of business data. In other exemplary embodiments, the service data pushing method may also be abstracted into a common function module, and the service data pushing method may also be applied to other scenes that require the server to stably push data to the client 10 in real time in a form of the common function module.
As shown in fig. 2, the service data pushing method may include steps S100 to S108, where:
step S100, receiving a first instruction, and instructing the first server 11 to extract target service data from the message queue according to the first instruction, where the first instruction is used to request to acquire the target service data.
In an exemplary embodiment, the first server 11 is any server in a server cluster, and the server that acquires the message may be the second server 12 corresponding to the target client, or may be any other server except the second server 12 in the server cluster, or any first server 11.
In an exemplary embodiment, each client 10 needs to connect with the server before receiving the web push message sent by the server. When a server cluster is deployed, each client 10 can only be connected with one server, and due to the load balancing policy of the server cluster, each web push message is also acquired and sent by only one server. If the server performing the message sending operation is not connected to the client 10, the message is lost.
Therefore, in order to ensure that the client 10 can connect with a server that performs a message sending operation; as shown in fig. 3, in an exemplary embodiment, the method further comprises: step S200, receiving connection requests sent by one or more clients 10 in advance; and step S202, according to the connection request sent by each client 10, determining a second server 12 corresponding to each client 10 from the server cluster, so that each client 10 establishes connection with the corresponding second server 12. The operation in this embodiment ensures that each client 10 is able to connect to a second server 12 that is able to perform messaging operations.
In an exemplary embodiment, to solve the security problem of the connection between the client 10 and the second server 12, the connection between the client 10 and the server is divided into two phases, i.e., establishing a channel and transmitting a token. As shown in fig. 4, in an exemplary embodiment, establishing a connection between each client 10 and the corresponding second server 12 may further be achieved by: step S300, according to the connection request, determining a second server 12 corresponding to the client 10 in the server cluster, and calling the client 10 and the second server 12 to receive first handshake information sent by the client 10, wherein the first handshake information includes a timestamp for message sending; step S302, controlling the second server 12 to send second handshake information to the corresponding client 10, where the second handshake information includes an encryption algorithm associated with a timestamp of the message sending; step S304, receiving third handshake information sent by the client 10, and controlling, according to the third handshake information, establishment of an encrypted connection channel between the second server 12 and the corresponding client 10, where the third handshake information is third handshake information generated based on the second handshake information, and the third handshake information includes encryption algorithm matching conclusion data or encryption algorithm mismatching conclusion data; step S306, generating a connection feedback packet corresponding to the client 10 according to the encrypted connection channel, and sending the connection feedback packet to the client 10 corresponding to the second server 12, where the connection feedback packet includes a token packet header protection policy; step S308, controlling the second server 12 to receive a token sent by the client 10 corresponding to the second server 12 through the encrypted connection channel, where the token is a character string reinforced by a corresponding token packet header protection policy; and step S310, verifying the token, generating a verification feedback message, and sending the verification feedback message to the client 10 corresponding to the second server 12, so as to implement the connection between the second server 12 and the corresponding client 10 through the verification feedback message.
The token (token) is used to identify the identity of the client 10, and is a unique identifier of the identity of the client 10. The token is a string of characters generated by the second server 12 and is sent to the client 10 so that it serves as a token requested by the client 10. After the client 10 connects to the second server 12 for the first time, the second server 12 generates a token and returns the token to the client 10, and then the client 10 needs to send the token to the second server 12 for authentication each time it connects to the second server 12.
The connection operation between the client 10 and the second server 12 described above is exemplarily described in stages below.
(1) A channel establishing stage: after the first handshake is performed between the client 10 and the second server 12, the WebSocket connection is established, and after the first handshake is successful, the second handshake is performed between the second server 12 and the client 10, and success response is sent to the second server 12 and the client.
(2) A token transmission stage: after receiving the success response, the client 10 performs a third handshake with the second server 12, and transmits the token to the second server 12 through the encrypted secure socket channel, and after receiving the token, the second server analyzes and verifies the token, and returns a required result if verification is successful, and returns error information if verification is failed, so that the client 10 is reconnected. Where the token on the server sets a validity period and the token and validity period are verified each time the client 10 requests it. The second server 12 analyzes the token and then performs a fourth handshake with the client 10, so that the whole connection process between the client 10 and the corresponding second server 12 is completed. Referring to fig. 5, step S310 may further include the following steps, wherein: step S400, when the third handshake information includes data indicating that the encryption algorithms do not match, controlling the second server 12 to receive an encryption algorithm list sent by the corresponding client 10, where the encryption algorithm list includes at least one candidate encryption algorithm; step S402, controlling the second server 12 to determine a target encryption algorithm from the encryption algorithm list; step S404, controlling the second server 12 to send fourth handshake information to the corresponding client 10, where the fourth handshake information includes a target encryption algorithm; step S406, controlling the second server 12 to receive fifth handshake information sent by the corresponding client 10, where the fifth handshake information includes encryption algorithm matching conclusion data; and step S408, controlling the second server 12 and the corresponding client 10 to establish an encrypted connection channel through a communication protocol and the fifth handshake information.
In an exemplary embodiment, the communication protocol may be a WebSocket communication protocol, wherein the WebSocket communication protocol is a full duplex communication protocol based on TCP (transmission control protocol). The connection channel is a socket channel.
Step S102, obtaining the target service data extracted by the first server 11, and determining a target client corresponding to the client identifier from one or more clients 10 according to a client identifier in the target service data, where the client identifier is a session identifier generated based on a server name and a timestamp of a second server 12 when the second server 12 corresponding to the target client is connected to the target client.
In an exemplary embodiment, the target service data includes, but is not limited to, system notification in a web application, reminding in a web site, IM instant messaging, web page instant quote inquiry, web online game update, and the like, and the target service data may be unified and actively generated data in a server cluster; the target service data may also be data generated in response to a data request of the client terminal 10. The target service data carries the client identifier, whether the target service data is generated actively by the server or generated by the server in response to the data request of the client 10.
Step S104, determining a target publish-subscribe channel corresponding to the target client according to the first instruction and the client identifier, and instructing the first server 11 to publish the target service data to the target publish-subscribe channel corresponding to the target client.
Step S106, determining the second server 12 according to the binding relationship of the target publish-subscribe channel in a preset database.
When a new client 10 connects to the second server 12, a publish command is executed for a corresponding key (equivalent to a channel), and the client 10 is maintained in a linked list of the second server 12, that is, a subscription channel corresponding to the second server 12 is subscribed; when new data needs to be transmitted to the client 10, the data is published to the corresponding key, and the second server 12 subscribed to the channel automatically transmits the data to the client 10 subscribed to the channel, so that the client 10 can perform subsequent processing on the new data.
Step S108, instructing the second server 12 to send the target service data in the target publish-subscribe channel to the corresponding target client.
In an exemplary embodiment, the second server 12 is a server associated with the target client, and introduces a publish-subscribe channel 13 to ensure that the server sending the message is necessarily connected to the client 10, solving the problem of message loss.
Referring to fig. 6, in an exemplary embodiment, to ensure load balancing of a server cluster, the method further includes: step S500, receiving a first instruction sent by the one or more clients 10 through a central server; and step S502, distributing each first instruction to the first server 11 in the server cluster through the central server according to the load balance of the server cluster. When receiving a connection request sent by the client 10 for the first time, load balancing in the server cluster needs to be considered, and a plurality of connection requests are distributed to a plurality of servers according to a load balancing rule, so that the load balancing requirement in the server cluster is met. Wherein the central server is a Nginx (high performance HTTP and reverse proxy web server) server.
As shown in fig. 7, in an exemplary embodiment, the method further comprises: creating and binding publish-subscribe channels 13 in the preset database in advance, wherein the step of creating and binding publish-subscribe channels 13 includes: step S600, obtaining a server name and an ip address of each second server 12 in the server cluster; step S602, combining the server name and the ip address of each second server 12 to generate a publish-subscribe channel 13 corresponding to each second server 12; step S604, acquiring each client 10 establishing connection with each second server 12; step S606, binding the server name of each second server 12, the corresponding publish-subscribe channel 13, and the corresponding client 10, and generating a key value pair corresponding to each second server 12, where the key value pair is used to represent a binding relationship among the second server 12, the corresponding publish-subscribe channel 13, and the corresponding client 10; and step S608, storing the key-value pair of each second server 12 in the preset database.
A unique message publishing subscription channel 13 is created for each second server 12, and the binding relationship between each second server 12 and the corresponding message publishing subscription channel 13 is maintained in a redis list, which is a memory-based, persistent, high-speed storage/reading-supporting database.
Each server deploying the application service has a dedicated server name and ip address, and when the Redis message publishing and subscribing channel 13 is created, the server name and the ip address are combined for naming. The structure of the data stored by Redis is key + value, and we can bind the data only by using the hash code corresponding to the combined data of the server name + the time stamp as a key (key) and using the machine name + the ip address as a value (value) when the service is started, and then find the corresponding publish-subscribe channel 13 according to the key. This binding is static since it does not change. Moreover, the client identifier of each client 10 is associated with the corresponding server, so that the client 10, the publish-subscribe channel 13 and the server are associated and bound with each other in a preset database.
Each server process of the redis database has a rediserver structure representing a server state, in which a data structure pubsub _ channels of a generic dictionary is maintained, the dictionary is also of a key/value structure, the value of the dictionary is of a linked list structure, and a plurality of elements can be stored. Elements can be added into the linked list of the specified key through a subscribe command; when the publish command is executed for a specified key, since the key in the dictionary is auto-snooped for changes, data is sent to and processed by all elements in the linked list for the corresponding key. By utilizing the characteristic, a publish-subscribe mode can be constructed, the second server 12 and the client 10 are connected, the unique identifier can be generated for the second server 12 and used as a key of the dictionary, and the client 10 connected with the key can be saved as an element in a linked list corresponding to the key.
Illustratively, a hash algorithm operation is performed by using the combined data of the server ip + timestamp, and a unique hash code (hash code) belonging to the server is generated and used as a key of the publish _ channel dictionary. And the client 10 needing to be bound with the server acquires the server ip and the recorded timestamp and generates a corresponding hashCode during each connection, and inserts the client identification information into the linked list corresponding to the key. To this end, the server acts as a key (i.e., channel), and the set of clients 10 is constructed as a value publish-subscribe pattern.
Referring to fig. 8, in an exemplary embodiment, after each client 10 successfully connects with a server, a corresponding client identifier is generated according to each client 10, and the client identifier is associated with the server. In an exemplary embodiment, step S108 may further include: step S700, according to the first instruction, traversing a preset database to obtain a client identifier of the target client in the preset database, where the client identifier is used to represent an association relationship between the target client and the corresponding second server 12; step S702, determining a target publishing and subscribing channel associated with the target client according to the client identifier of the target client in the preset database; and step S704, making the first server 11, and publishing the target service data to the target publishing and subscribing channel corresponding to the target client.
In an exemplary embodiment, it is assumed that the second server 12 is a server a, the server a obtains the target service data, determines that the target client is a client B according to a client identifier carried in the server a, determines that the target publish-subscribe channel is a publish-subscribe channel B according to a client identifier of the client B in a preset database, and determines that the second server 12 is a server B according to a binding relationship of the publish-subscribe channel B in the preset database.
Assuming that the second server 12 is a server a, the server a obtains the target service data, determines that the target client is the server a according to the client identifier carried in the server a, determines that the target publish-subscribe channel is the publish-subscribe channel a according to the client identifier of the server a in the preset database, and determines that the second server 12 is the server a according to the binding relationship of the publish-subscribe channel a in the preset database.
Through the operation, the server connected with the target client side is used for sending the message, and the effect of accurately pushing the message can be achieved.
The embodiment of the invention at least has the following beneficial effects:
(1) through the binding relationship among the client 10, the target publish-subscribe channel and the second server 12, the stability, accuracy and safety of data pushing are greatly improved, data is pushed in time, and user experience is improved.
(2) In practical application, the method of the embodiment of the invention enables the message pushing arrival rate of the quotation system to be improved to 99% from the original 50%, optimizes user experience, enables users to receive quotation messages and carry out business operation in the first time, and greatly increases user retention rate and recall rate.
(3) The transmission security of the user token is improved, so that the security of user information is ensured, the user information is prevented from being acquired randomly, and the risk that the system is attacked maliciously is avoided.
Example two
Continuing to refer to fig. 9, a schematic diagram of program modules of the service data pushing system of the present invention is shown. In this embodiment, the service data pushing system 20 may include or be divided into one or more program modules, and the one or more program modules are stored in a storage medium and executed by one or more processors to implement the present invention and implement the service data pushing method. The program module referred to in the embodiments of the present invention refers to a series of computer program instruction segments capable of performing specific functions, and is more suitable for describing the execution process of the business data push system 20 in the storage medium than the program itself. The following description will specifically describe the functions of the program modules of the present embodiment:
an obtaining module 800, configured to receive a first instruction, and control a first server to extract target service data from a message queue according to the first instruction, where the first instruction is used to request to obtain the target service data;
a first determining module 802, configured to obtain the target service data extracted by the first server, and determine, according to a client identifier in the target service data, a target client corresponding to the client identifier from one or more clients, where the client identifier is a session identifier generated based on a server name and a timestamp of a second server when the second server corresponding to the target client is connected to the target client;
a publishing module 804, configured to determine, according to the first instruction, a target publishing and subscribing channel corresponding to the target client, and instruct the first server to publish the target service data to the target publishing and subscribing channel corresponding to the target client;
a second determining module 806, configured to determine the second server according to a binding relationship of the target publish-subscribe channel in a preset database; and
a sending module 808, configured to instruct the second server to send the target service data in the target publish-subscribe channel to a corresponding target client.
In an exemplary embodiment, the service data pushing system 20 further includes a connection module 810, and the connection module 810 is further configured to: receiving connection requests sent by one or more clients in advance; and determining a second server corresponding to each client from the server cluster according to the connection request sent by each client, so that each client establishes connection with the corresponding second server.
In an exemplary embodiment, the connection module 810 is further configured to: according to the connection request, a second server corresponding to the client is determined in the server cluster, the second server is called to receive first handshake information sent by the client, and the first handshake information comprises a timestamp for sending a message; controlling the second server to send second handshake information to the corresponding client, wherein the second handshake information includes an encryption algorithm associated with a timestamp of the message sending; receiving third handshake information sent by the client, and controlling the second server and the corresponding client to establish an encrypted connection channel according to the third handshake information, wherein the third handshake information is generated based on the second handshake information and comprises encryption algorithm matching conclusion data or encryption algorithm mismatching conclusion data; generating a connection feedback message corresponding to the client according to the encrypted connection channel, and sending the connection feedback message to the client corresponding to the second server, wherein the connection feedback message comprises a token packet header protection strategy; controlling the second server to receive a token sent by a client corresponding to the second server through the encrypted connection channel, wherein the token is a character string reinforced through a corresponding token data packet header protection strategy; and verifying the token, generating a verification feedback message, and sending the verification feedback message to a client corresponding to the second server so as to realize the connection between the second server and the corresponding client through the verification feedback message.
In an exemplary embodiment, the connection module 810 is further configured to: when the third handshake information comprises encryption algorithm mismatching conclusion data, controlling the second server to receive an encryption algorithm list sent by a corresponding client, wherein the encryption algorithm list comprises at least one candidate encryption algorithm; controlling the second server to determine a target encryption algorithm from the encryption algorithm list; controlling the second server to send fourth handshake information to the corresponding client, wherein the fourth handshake information comprises a target encryption algorithm; controlling the second server to receive fifth handshake information sent by a corresponding client, wherein the fifth handshake information comprises encryption algorithm matching conclusion data; and controlling the second server and the corresponding client to establish an encrypted connection channel through a communication protocol and the fifth handshake information.
In an exemplary embodiment, the business data pushing system 20 further includes a distribution module 812, and the distribution module 812 is further configured to: receiving a first instruction sent by the one or more clients through a central server; and distributing each first instruction to a first server in the server cluster through the central server according to the load balance of the server cluster.
In an exemplary embodiment, the service data pushing system 20 further includes a creating module 814, and the creating module 814 is further configured to: acquiring a server name and an ip address of each second server in the server cluster; combining the server name and the ip address of each second server to generate a publish-subscribe channel corresponding to each second server; acquiring each client connected with each second server; binding the server name of each second server, the corresponding publish-subscribe channel binding and the corresponding client to generate a key value pair corresponding to each second server, wherein the key value pair is used for representing the binding relationship among the second server, the corresponding publish-subscribe channel and the corresponding client; and storing the key value pair of each second server in the preset database.
In an exemplary embodiment, the publishing module 804 is further configured to: traversing a preset database according to the first instruction to acquire a client identifier of the target client in the preset database, wherein the client identifier is used for representing an association relationship between the target client and a corresponding second server; determining a target publishing and subscribing channel associated with the target client according to the client identifier of the target client in the preset database; and controlling the first server to publish the target service data to the target publishing and subscribing channel corresponding to the target client.
EXAMPLE III
Fig. 10 is a schematic diagram of a hardware architecture of a computer device according to a third embodiment of the present invention. In the present embodiment, the computer device 2 is a device capable of automatically performing numerical calculation and/or information processing in accordance with a preset or stored instruction. The computer device 2 may be a rack server, a blade server, a tower server or a rack server (including an independent server or a server cluster composed of a plurality of servers), and the like. As shown in fig. 10, the computer device 2 includes, but is not limited to, at least a memory 21, a processor 22, a network interface 23, and a service data pushing system 20, which are communicatively connected to each other through a system bus. Wherein:
in this embodiment, the memory 21 includes at least one type of computer-readable storage medium including a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the storage 21 may be an internal storage unit of the computer device 2, such as a hard disk or a memory of the computer device 2. In other embodiments, the memory 21 may also be an external storage device of the computer device 2, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like provided on the computer device 2. Of course, the memory 21 may also comprise both internal and external memory units of the computer device 2. In this embodiment, the memory 21 is generally used for storing an operating system installed in the computer device 2 and various application software, such as the program codes of the business data pushing system 20 of the above embodiment. Further, the memory 21 may also be used to temporarily store various types of data that have been output or are to be output.
The network interface 23 may comprise a wireless network interface or a wired network interface, and the network interface 23 is generally used for establishing communication connection between the computer device 2 and other electronic apparatuses. For example, the network interface 23 is used to connect the computer device 2 to an external terminal through a network, establish a data transmission channel and a communication connection between the computer device 2 and the external terminal, and the like. The network may be a wireless or wired network such as an Intranet (Intranet), the Internet (Internet), a Global System for mobile communication (GSM), Wideband Code Division Multiple Access (WCDMA), a 4G network, a 5G network, Bluetooth (Bluetooth), Wi-Fi, and the like.
It is noted that fig. 10 only shows the computer device 2 with components 20-23, but it is to be understood that not all of the shown components are required to be implemented, and that more or less components may be implemented instead.
In this embodiment, the business data pushing system 20 stored in the memory 21 can be further divided into one or more program modules, and the one or more program modules are stored in the memory 21 and executed by one or more processors (in this embodiment, the processor 22) to complete the present invention.
For example, fig. 9 is a schematic diagram of program modules of the second embodiment of implementing the service data pushing system 20, in this embodiment, the service data pushing system 20 may be divided into an obtaining module 800, a first determining module 802, a publishing module 804, a second determining module 806, and a sending module 808. The program module referred to in the present invention refers to a series of computer program instruction segments capable of performing specific functions, and is more suitable than a program for describing the execution process of the business data push system 20 in the computer device 2. The specific functions of the program modules 800 and 808 have been described in detail in the second embodiment, and are not described herein again.
Example four
The present embodiment also provides a computer-readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App application mall, etc., on which a computer program is stored, which when executed by a processor implements corresponding functions. The computer-readable storage medium of the present embodiment is used for storing the service data pushing system 20, and when executed by a processor, the service data pushing method of the above embodiment is implemented.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A method for pushing service data is characterized by comprising the following steps:
receiving a first instruction, and instructing a first server to extract target service data from a message queue according to the first instruction, wherein the first instruction is used for requesting to acquire the target service data;
acquiring the target service data extracted by the first server, and determining a target client corresponding to the client identifier from one or more clients according to the client identifier in the target service data, wherein the client identifier is a session identifier generated based on the server name and the timestamp of a second server when the second server corresponding to the target client is connected with the target client;
according to the first instruction and the client identification, determining a target publishing and subscribing channel corresponding to the target client, and instructing the first server to publish the target service data to the target publishing and subscribing channel corresponding to the target client;
determining the second server according to the binding relationship of the target publish-subscribe channel in a preset database; and
and instructing the second server to send the target service data in the target publishing and subscribing channel to the corresponding target client.
2. The method for pushing service data according to claim 1, wherein before the step of receiving the first command, the method further comprises:
receiving connection requests sent by one or more clients in advance; and
and according to the connection request sent by each client, determining a second server corresponding to each client from the server cluster, so that each client establishes connection with the corresponding second server.
3. The method for pushing business data according to claim 2, wherein the step of determining a second server corresponding to each client from a server cluster according to the connection request sent by each client, so that each client establishes a connection with the corresponding second server respectively comprises:
according to the connection request, a second server corresponding to the client is determined in the server cluster, the second server is called to receive first handshake information sent by the client, and the first handshake information comprises a timestamp for sending a message;
controlling the second server to send second handshake information to the corresponding client, wherein the second handshake information includes an encryption algorithm associated with a timestamp of the message sending;
receiving third handshake information sent by the client, and controlling the second server and the corresponding client to establish an encrypted connection channel according to the third handshake information, wherein the third handshake information is generated based on the second handshake information and comprises encryption algorithm matching conclusion data or encryption algorithm mismatching conclusion data;
generating a connection feedback message corresponding to the client according to the encrypted connection channel, and sending the connection feedback message to the client corresponding to the second server, wherein the connection feedback message comprises a token packet header protection strategy;
controlling the second server to receive a token sent by a client corresponding to the second server through the encrypted connection channel, wherein the token is a character string reinforced through a corresponding token data packet header protection strategy; and
and verifying the token, generating a verification feedback message, and sending the verification feedback message to a client corresponding to a second server so as to realize the connection between the second server and the corresponding client through the verification feedback message.
4. The method according to claim 3, wherein the step of receiving third handshake information sent by the client and controlling establishment of an encrypted connection channel between the second server and the corresponding client according to the third handshake information further includes:
when the third handshake information comprises encryption algorithm mismatching conclusion data, controlling the second server to receive an encryption algorithm list sent by a corresponding client, wherein the encryption algorithm list comprises at least one candidate encryption algorithm;
controlling the second server to determine a target encryption algorithm from the encryption algorithm list;
controlling the second server to send fourth handshake information to the corresponding client, wherein the fourth handshake information comprises a target encryption algorithm;
controlling the second server to receive fifth handshake information sent by a corresponding client, wherein the fifth handshake information comprises encryption algorithm matching conclusion data; and
and controlling the second server and the corresponding client to establish an encrypted connection channel through a communication protocol and the fifth handshake information.
5. The method according to claim 2, wherein before the step of obtaining the first instruction and controlling the first server to extract the target service data from the message queue according to the first instruction, the method further comprises:
receiving a first instruction sent by the one or more clients through a central server; and
and distributing each first instruction to a first server in the server cluster through the central server according to the load balance of the server cluster.
6. The method for pushing service data according to claim 2, wherein the method further comprises: creating and binding publish-subscribe channels in the preset database in advance, wherein the step of creating and binding publish-subscribe channels comprises the following steps:
acquiring a server name and an ip address of each second server in the server cluster;
combining the server name and the ip address of each second server to generate a publish-subscribe channel corresponding to each second server;
acquiring each client connected with each second server;
binding the server name of each second server, the corresponding publish-subscribe channel binding and the corresponding client to generate a key value pair corresponding to each second server, wherein the key value pair is used for representing the binding relationship among the second server, the corresponding publish-subscribe channel and the corresponding client; and
and storing the key value pair of each second server in the preset database.
7. The method for pushing service data according to claim 1, wherein the step of controlling the first server to publish the target service data to a target publish-subscribe channel corresponding to the target client according to the first instruction includes:
traversing a preset database according to the first instruction to acquire a client identifier of the target client in the preset database, wherein the client identifier is used for representing an association relationship between the target client and a corresponding second server;
determining a target publishing and subscribing channel associated with the target client according to the client identifier of the target client in the preset database; and
and controlling the first server to publish the target service data to the target publishing and subscribing channel corresponding to the target client.
8. A business data push system, comprising:
the system comprises an acquisition module, a message queue and a service processing module, wherein the acquisition module is used for receiving a first instruction and controlling a first server to extract target service data from the message queue according to the first instruction, and the first instruction is used for requesting to acquire the target service data;
a first determining module, configured to obtain the target service data extracted by the first server, and determine, according to a client identifier in the target service data, a target client corresponding to the client identifier from one or more clients, where the client identifier is a session identifier generated based on a server name and a timestamp of a second server when the second server corresponding to the target client is connected to the target client;
the publishing module is used for determining a target publishing and subscribing channel corresponding to the target client according to the first instruction and instructing the first server to publish the target service data to the target publishing and subscribing channel corresponding to the target client;
the second determining module is used for determining the second server according to the binding relationship of the target publishing and subscribing channel in a preset database; and
and the sending module is used for indicating the second server to send the target service data in the target publishing and subscribing channel to the corresponding target client.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the business data pushing method according to any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored, which computer program is executable by at least one processor to cause the at least one processor to perform the steps of the traffic data pushing method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110483292.9A CN113190778A (en) | 2021-04-30 | 2021-04-30 | Business data pushing method, system, computer equipment and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110483292.9A CN113190778A (en) | 2021-04-30 | 2021-04-30 | Business data pushing method, system, computer equipment and computer storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113190778A true CN113190778A (en) | 2021-07-30 |
Family
ID=76983338
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110483292.9A Pending CN113190778A (en) | 2021-04-30 | 2021-04-30 | Business data pushing method, system, computer equipment and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113190778A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114827171A (en) * | 2022-03-23 | 2022-07-29 | 青岛中科曙光科技服务有限公司 | Information synchronization method and device, computer equipment and storage medium |
| CN115348480A (en) * | 2022-07-15 | 2022-11-15 | 海南视联通信技术有限公司 | Media service processing method, device, equipment and storage medium |
| WO2023014286A3 (en) * | 2021-08-04 | 2023-03-09 | Lemon Inc. | Share based augmented reality content service system |
| CN116361038A (en) * | 2023-06-02 | 2023-06-30 | 山东浪潮科学研究院有限公司 | Acceleration computing management method, system, equipment and storage medium |
| CN117082124A (en) * | 2023-10-10 | 2023-11-17 | 腾讯科技（深圳）有限公司 | Data transmission method, device, equipment, medium and product |
| CN117640772A (en) * | 2023-11-24 | 2024-03-01 | 北京中海通科技有限公司 | Customs data distribution method and device based on data rights and electronic equipment |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120030369A1 (en) * | 2010-07-27 | 2012-02-02 | Vikas Lamba | Reliable data message exchange |
| CN102685155A (en) * | 2011-03-07 | 2012-09-19 | 联想(北京)有限公司 | Content delivery method, content delivery server and content delivery proxy server |
| US20160337290A1 (en) * | 2014-01-10 | 2016-11-17 | Huawei Technologies Co., Ltd. | Message Push Method and Apparatus |
| CN106210099A (en) * | 2016-07-18 | 2016-12-07 | 珠海格力电器股份有限公司 | Data processing system and method |
| CN108833521A (en) * | 2018-06-06 | 2018-11-16 | 广州视源电子科技股份有限公司 | Message pushing method, device, system, computer equipment and storage medium |
| CN110300050A (en) * | 2019-05-23 | 2019-10-01 | 中国平安人寿保险股份有限公司 | Information push method, device, computer equipment and storage medium |
| US20200067903A1 (en) * | 2018-08-24 | 2020-02-27 | International Business Machines Corporation | Integration of Publish-Subscribe Messaging with Authentication Tokens |
| US20200076743A1 (en) * | 2018-08-31 | 2020-03-05 | Twitter, Inc. | Event content delivery |
| WO2020211344A1 (en) * | 2019-04-17 | 2020-10-22 | 平安科技（深圳）有限公司 | Mqtt-based message distribution method, server, apparatus, and storage medium |
| CN111857585A (en) * | 2020-07-10 | 2020-10-30 | 苏州浪潮智能科技有限公司 | Method, device, equipment and medium for configuring user-defined service function of storage system |
| CN111970315A (en) * | 2019-05-20 | 2020-11-20 | 北京车和家信息技术有限公司 | Method, device and system for pushing message |
| CN112039942A (en) * | 2017-08-29 | 2020-12-04 | 华为技术有限公司 | Subscription and publishing method and server |
-
2021
- 2021-04-30 CN CN202110483292.9A patent/CN113190778A/en active Pending
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120030369A1 (en) * | 2010-07-27 | 2012-02-02 | Vikas Lamba | Reliable data message exchange |
| CN102685155A (en) * | 2011-03-07 | 2012-09-19 | 联想(北京)有限公司 | Content delivery method, content delivery server and content delivery proxy server |
| US20160337290A1 (en) * | 2014-01-10 | 2016-11-17 | Huawei Technologies Co., Ltd. | Message Push Method and Apparatus |
| CN106210099A (en) * | 2016-07-18 | 2016-12-07 | 珠海格力电器股份有限公司 | Data processing system and method |
| CN112039942A (en) * | 2017-08-29 | 2020-12-04 | 华为技术有限公司 | Subscription and publishing method and server |
| CN108833521A (en) * | 2018-06-06 | 2018-11-16 | 广州视源电子科技股份有限公司 | Message pushing method, device, system, computer equipment and storage medium |
| US20200067903A1 (en) * | 2018-08-24 | 2020-02-27 | International Business Machines Corporation | Integration of Publish-Subscribe Messaging with Authentication Tokens |
| US20200076743A1 (en) * | 2018-08-31 | 2020-03-05 | Twitter, Inc. | Event content delivery |
| WO2020211344A1 (en) * | 2019-04-17 | 2020-10-22 | 平安科技（深圳）有限公司 | Mqtt-based message distribution method, server, apparatus, and storage medium |
| CN111970315A (en) * | 2019-05-20 | 2020-11-20 | 北京车和家信息技术有限公司 | Method, device and system for pushing message |
| CN110300050A (en) * | 2019-05-23 | 2019-10-01 | 中国平安人寿保险股份有限公司 | Information push method, device, computer equipment and storage medium |
| CN111857585A (en) * | 2020-07-10 | 2020-10-30 | 苏州浪潮智能科技有限公司 | Method, device, equipment and medium for configuring user-defined service function of storage system |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023014286A3 (en) * | 2021-08-04 | 2023-03-09 | Lemon Inc. | Share based augmented reality content service system |
| US11627182B2 (en) | 2021-08-04 | 2023-04-11 | Lemon Inc. | Share based augmented reality content service system |
| CN114827171A (en) * | 2022-03-23 | 2022-07-29 | 青岛中科曙光科技服务有限公司 | Information synchronization method and device, computer equipment and storage medium |
| CN114827171B (en) * | 2022-03-23 | 2023-12-15 | 青岛中科曙光科技服务有限公司 | Information synchronization method, apparatus, computer device and storage medium |
| CN115348480A (en) * | 2022-07-15 | 2022-11-15 | 海南视联通信技术有限公司 | Media service processing method, device, equipment and storage medium |
| CN116361038A (en) * | 2023-06-02 | 2023-06-30 | 山东浪潮科学研究院有限公司 | Acceleration computing management method, system, equipment and storage medium |
| CN116361038B (en) * | 2023-06-02 | 2023-09-08 | 山东浪潮科学研究院有限公司 | Acceleration computing management method, system, equipment and storage medium |
| CN117082124A (en) * | 2023-10-10 | 2023-11-17 | 腾讯科技（深圳）有限公司 | Data transmission method, device, equipment, medium and product |
| CN117082124B (en) * | 2023-10-10 | 2024-02-13 | 腾讯科技（深圳）有限公司 | Data transmission method, device, equipment, medium and product |
| CN117640772A (en) * | 2023-11-24 | 2024-03-01 | 北京中海通科技有限公司 | Customs data distribution method and device based on data rights and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113190778A (en) | Business data pushing method, system, computer equipment and computer storage medium | |
| CN107294729B (en) | Communication method and device between different nodes in block chain | |
| CN108833521B (en) | Message pushing method, device, system, computer equipment and storage medium | |
| CN111010372A (en) | Block chain network identity authentication system, data processing method and gateway equipment | |
| EP2633667B1 (en) | System and method for on the fly protocol conversion in obtaining policy enforcement information | |
| CN112235420B (en) | Data synchronization method, system and related equipment based on block chain | |
| CN110599142B (en) | Data storage method, device, computer equipment and storage medium | |
| CN109951514B (en) | File processing method and system based on cloud storage and computer equipment | |
| CN108965107B (en) | Friend adding method, device, system, client and server | |
| WO2013123841A1 (en) | Method, apparatus, and system for resource sharing | |
| CN110351364A (en) | Date storage method, equipment and computer readable storage medium | |
| CN111597537B (en) | Block chain network-based certificate issuing method, related equipment and medium | |
| CN112087475B (en) | Message pushing method and device for cloud platform component application and message server | |
| CN112231415B (en) | Data synchronization method and system of block chain network, electronic device and readable medium | |
| CN111158716B (en) | Version upgrade calling method and device, computer system and readable storage medium | |
| CN112541820B (en) | Digital asset management method, device, computer equipment and readable storage medium | |
| CN109104472B (en) | Block chain network networking method, device, equipment and computer readable storage medium | |
| EP3547231B1 (en) | Electronic device management | |
| CN115150162B (en) | Root certificate updating method and device | |
| CN113497762A (en) | Data message transmission method and device | |
| CN113037848B (en) | File uploading method and system | |
| CN115550884A (en) | Vehicle communication method, device, equipment and medium | |
| CN115840754A (en) | Virtual resource management method and device and electronic equipment | |
| CN110895583A (en) | Method, device and system for acquiring data resources | |
| CN110474954B (en) | Block chain-based file sharing method and device, computer equipment and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |