WO2023185796A1 - 一种信息推送方法及服务器、客户端、存储介质 - Google Patents

一种信息推送方法及服务器、客户端、存储介质 Download PDF

Info

Publication number
WO2023185796A1
WO2023185796A1 PCT/CN2023/084272 CN2023084272W WO2023185796A1 WO 2023185796 A1 WO2023185796 A1 WO 2023185796A1 CN 2023084272 W CN2023084272 W CN 2023084272W WO 2023185796 A1 WO2023185796 A1 WO 2023185796A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
client
server
control protocol
transmission control
Prior art date
Application number
PCT/CN2023/084272
Other languages
English (en)
French (fr)
Inventor
王永军
王晰源
王添枝
朱跃棕
胡本奎
Original Assignee
北京沃东天骏信息技术有限公司
北京京东世纪贸易有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京沃东天骏信息技术有限公司, 北京京东世纪贸易有限公司 filed Critical 北京沃东天骏信息技术有限公司
Publication of WO2023185796A1 publication Critical patent/WO2023185796A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions

Definitions

  • This application relates to the technical field of information push, involving but not limited to an information push method, server, client, and storage medium.
  • the server will predict the resources that the browser may use and push these resources to the client so that the browser can directly use the resources. Obtained from the client memory where the browser is located.
  • the server when the server receives a Hypertext Transfer Protocol (HTTP) request sent by the client, it obtains the request information corresponding to the HTTP request, obtains the information that needs to be pushed, and sends the request to the client.
  • HTTP Hypertext Transfer Protocol
  • the request information When sending request information, the request information carries the information that needs to be pushed, which reduces the speed of the server pushing information to the client.
  • embodiments of the present application are expected to provide an information pushing method, server, client, and storage medium, which can improve the speed of pushing information.
  • the embodiment of the present application provides an information push method, which is applied to a server.
  • the information push method Methods include:
  • the information to be pushed corresponding to the client is obtained, the information to be pushed is pushed to the client using the transmission control protocol connection in the storage pool.
  • the embodiment of the present application also provides an information push method, which is applied to the client.
  • the information push method includes:
  • the transmission control protocol connection is added to a connection pool, and information to be pushed transmitted by the server is received according to the transmission control protocol connection in the connection pool.
  • This embodiment of the present application provides a server, which includes:
  • the establishment part is configured to, upon receiving a hypertext transmission request transmitted by the client, establish a transmission control protocol connection with the client according to the hypertext transmission request;
  • the first adding part is configured to add the transmission control protocol connection to a storage pool, where the storage pool includes at least one transmission control protocol connection;
  • the push part is configured to push the information to be pushed to the client using the transmission control protocol connection in the storage pool when the information to be pushed corresponding to the client is obtained.
  • This embodiment of the present application provides a client, which includes:
  • the transmission part is configured to send a hypertext transmission request to the server; to establish a transmission control protocol connection with the server according to the hypertext transmission request;
  • the adding part is configured to add the transmission control protocol connection to the connection pool
  • the second receiving part is configured to connect a connection according to the transmission control protocol in the connection pool. Receive the information to be pushed transmitted by the server.
  • An embodiment of the present application further provides a server, which includes:
  • a first memory a first processor and a first communication bus
  • the first memory communicates with the first processor through the first communication bus
  • the first memory stores the first processor executable
  • the first processor executes the above-mentioned information push method applied to the server.
  • This embodiment of the present application further provides a client, which includes:
  • the second memory communicates with the second processor through the second communication bus, the second memory stores the second processor executable When the information push program is executed, the second processor executes the above-mentioned information push method applied to the client.
  • Embodiments of the present application provide a storage medium on which a computer program is stored, which is applied to the client and the server.
  • the computer program is executed by the first processor, the above-mentioned information push method applied to the server is implemented; the When the computer program is executed by the second processor, the above-mentioned information pushing method applied to the client is implemented.
  • Embodiments of the present application provide an information push method, a server, a client, and a storage medium.
  • the information push method includes: upon receiving a hypertext transmission request transmitted by the client, establishing a connection with the client according to the hypertext transmission request. Transmission Control Protocol connection between The control protocol connection pushes the information to be pushed to the client.
  • the server adds the TCP connection to the storage pool and uses the storage pool to store the TCP connection, so that the server can When the information to be pushed is obtained, the server can directly use the transmission control protocol connection to push the information to be pushed to the client, which improves the speed of pushing the information to be pushed.
  • Figure 1(a) is a schematic diagram 1 of an HTTP persistent connection in the prior art provided by an embodiment of the present application;
  • Figure 1(b) is a schematic diagram 2 of an HTTP persistent connection in the prior art provided by an embodiment of the present application;
  • Figure 1(c) is a schematic diagram 3 of an HTTP persistent connection in the prior art provided by an embodiment of the present application;
  • FIG. 2 is a schematic diagram of an HTTP/2 service push protocol in the prior art provided by an embodiment of the present application
  • Figure 3 is a flow chart 1 of an information pushing method provided by an embodiment of the present application.
  • Figure 4 is a flow chart 2 of an information pushing method provided by an embodiment of the present application.
  • Figure 5 is a schematic diagram of an exemplary improved HTTP/2 service push protocol provided by an embodiment of the present application.
  • Figure 6 is a schematic structural diagram of an exemplary information push provided by an embodiment of the present application.
  • Figure 7 is a schematic structural diagram of a server provided by an embodiment of the present application.
  • Figure 8 is a schematic diagram 2 of the composition and structure of a server provided by an embodiment of this application.
  • Figure 9 is a schematic structural diagram of a client provided by an embodiment of the present application.
  • Figure 10 is a schematic structural diagram 2 of a client provided by an embodiment of the present application.
  • HTTP1.0 has no reuse.
  • the server receives the data sent by the client.
  • the request information corresponding to the HTTP request is obtained; the request information is transmitted to the client, and there needs to be a period of time between the client receiving the request information and the client sending the next HTTP request;
  • HTTP1.1 is connection multiplexing.
  • the server receives an HTTP request sent by the client, it obtains the request information corresponding to the HTTP request; transmits the request information to the client, And there is no interval between the client receiving the request information and the client sending the next HTTP request; as shown in Figure 1(c): HTTP/2 is multiplexing, and the server receives the HTTP request sent by the client.
  • the request information corresponding to the HTTP request is obtained; the request information is transmitted to the client. If the client has not received the request information, the client can send the next HTTP request to the server.
  • the client sends a hypertext transfer request (index.html request, specifically including: stream 1 type: 1; method get; path/index.html; etc to the server; the server obtains the response to the HTTP request
  • the request information (stream 1 type: 1; date xxxx; cache-controller%), the server will also obtain the information that needs to be pushed, and the server transmits the request information and the information that needs to be pushed to the client; among them, the information that needs to be pushed includes index .css information and index.js information.
  • index.css information includes Push promise frame-Push preface (stream 2 type: 5; method get; path/index.css; authority ip: 443; scheme https), Header frame-Header (stream 2 type: 1; status 200; content-type xx; content-length xxx;...), Date frame-body (stream 2 type: 0; body ⁇ ... ⁇ ...);
  • index.js information includes Push promise frame-push preface (stream 4 type: 5; method get; path/index.js; authority ip: 443; scheme https), Header frame-Header (stream 4 type: 1; status 200; content-type xx; content-length xxx; ...), Date Frame-body(stream4 type: 0; function click() ⁇ ... ⁇ ).
  • the embodiment of the present application provides an information push method.
  • An information push method is applied to a server.
  • Figure 3 is a flow chart of an information push method provided by an embodiment of the present application. As shown in Figure 3, the information push method may include:
  • An information push method provided by the embodiment of the present application is suitable for the scenario where the server sends information to be pushed to the client.
  • the server can be implemented in various forms.
  • the server described in this application may include mobile phones, cameras, tablets, notebook computers, PDAs, personal digital assistants (Personal Digital Assistant, PDA), portable media players (Portable Media Player, PMP), navigation devices , wearable devices, smart bracelets, pedometers and other devices, as well as devices such as digital TVs, desktop computers, servers and other devices.
  • the hypertext transmission request may be an HTTP request.
  • the transmission control protocol connection may be a transmission control protocol (Transmission Control Protocol, TCP) connection.
  • TCP Transmission Control Protocol
  • the process of establishing a transmission control protocol connection between the server and the client according to the hypertext transmission request is the TCP connection method between the server and the client in the prior art.
  • the specific embodiment of the present application No detailed explanation will be given here.
  • the client is a client that integrates an open source network library that supports HTTP/2; and the client has turned on the push switch of the HTTP/2 Setting frame.
  • the server establishes a TCP connection with the client based on a hypertext transmission request.
  • the server can set the unique code (uuid)/user identification (userid) of the connection and the response status code for the server.
  • the HTTP request path (Path) of 204 is used to establish a TCP connection when the application (Application, App) is started (if the App starts to send an HTTP request to the target server, this Path is not defined).
  • requests with response status code 204 refer to requests without response information.
  • the responsibility push Server service in the server is divided into push work (Worker) and push management (Manager), that is, the server is divided into push Worker and push Manager.
  • Worker is used to collect and manage HTTP TCP persistent connections, send push messages and reverse proxy HTTP requests from the target server;
  • Manger is used to register and manage Workers, assign push tasks to Workers, and provide a content management system (content management system).
  • cms application programming interface
  • api Application Programming Interface
  • Manger and Worker can communicate through Message Queuing (MQ).
  • the server first generates a server certificate (Secure socket layer, SSL), builds a Netty HTTP/2 container for push Worker, turns on HTTP gzip compression, and uses port 443 to respond to HTTP/2 network requests; server push Worker has a reverse proxy function added. You can use the configuration file push.properties to read the target server port (port). Worker reads the port number of the target server port when starting and reverse-proxyes the http request of the target server (only done once Network access to http://localhost:port/ ⁇ path ⁇ ).
  • SSL Secure Socket Transfer Protocol Secure
  • Netty is an asynchronous event-driven network application framework and tool, used to implement the parsing and response of the HTTP/2 protocol.
  • push tasks can be assigned to push workers through MQ, and cms push and api interfaces can be provided.
  • Deploy Push Worker and Push Manager and set the push.properties configuration file. The content is the port used by the target server (since port 443 is used to push Worker, the port here can be other ports except port 443). Deploy Push Worker to target drone. Push Manager can be deployed separately.
  • CMS push refers to pushing a certain task on a web page.
  • the frequently accessed HTTP/2 TCP connection is reused as a TCP long connection channel.
  • the HTTP/2 server is called the target server, and the host where it is located is called the target machine.
  • the server after the server establishes the TCP connection with the client according to the hypertext transfer request, the server adds the TCP connection to the storage pool.
  • the storage pool includes at least one Transmission Control Protocol connection.
  • the storage pool may be a global Map; the storage pool may also be other storage areas; the specific storage pool may be determined according to the actual situation, which is not limited in the embodiment of the present application.
  • the server before the server adds the TCP connection to the storage pool, the server also configures the corresponding relationship between the TCP connection and the client; accordingly, the server adds the TCP connection to the storage pool.
  • the process includes: the server adds the correspondence between the Transmission Control Protocol connection and the client and the Transmission Control Protocol connection to the storage pool.
  • the server can complete the HTTP/2 request transmission (Netty HTTP/2 OnSettingsAckRead callback) and establish the transmission control protocol connection between the server and the client.
  • the TCP connection is placed in the storage pool (global Map), where the key of the global Map is the client uuid/userid parameter carried in the HTTP request, and the value of the Map is the TCP connection (userid is the tcp list).
  • the server after the server adds the TCP connection to the storage pool, the server will also delete the TCP connection from the storage pool when the TCP connection is disconnected.
  • the server uses the transmission control protocol connection in the storage pool to push Information is pushed to the client.
  • the information to be pushed can be Cascading Style Sheets (CSS) resources; the information to be pushed can also be javascript (JS) resources; the information to be pushed can also be other information; the specific information to be pushed
  • CSS Cascading Style Sheets
  • JS javascript
  • the information can be determined according to the actual situation, which is not limited in the embodiments of this application.
  • the information to be pushed is the information that will be pushed to the client and will be used by the client. information.
  • the process of the server pushing the information to be pushed to the client using the transmission control protocol connection in the storage pool includes: the server obtains the original header frame and the original information frame corresponding to the original push service; the server determines the corresponding information of the information to be pushed.
  • the server adds the information to be pushed to the original information frame, and the process of obtaining the information frame includes the server encrypting the information to be pushed to obtain the encrypted information, and then the server adds the encrypted information to the original information frame.
  • the information frame is obtained; the server can also compress the information to be pushed to obtain the compressed information, and then the server adds the compressed information to the original information frame to obtain the information frame; the server can also directly add the information to be pushed to the original information frame.
  • obtain the information frame the specific server adds the information to be pushed to the original information frame, and the process of obtaining the information frame can be determined according to the actual situation, which is not limited in the embodiments of the present application.
  • the server encrypts the push information and obtains the encrypted information by using the Advanced Encryption Standard (Advanced Encryption Standard, AES) to encrypt the push information and obtains the encrypted information; the server can also use other methods to obtain the encrypted information.
  • the information is encrypted to obtain the encrypted information; the specific server encrypts the information to be pushed, and the method of obtaining the encrypted information can be determined according to the actual situation, which is not limited in the embodiments of this application.
  • the server uses AES to encrypt the push information
  • the encryption key when obtaining the encrypted information can be dynamically generated using the magic number, device uuid, stream identity document (ID) and path specification algorithm.
  • the server compresses the information to be pushed to obtain the compressed information.
  • the server can use the Http gzip compression method to compress the information to be pushed to obtain the compressed information. compress the information; the server can also use other compression methods to compress the information to be pushed to obtain the compressed information; the specific server compresses the information to be pushed, and the method of obtaining the compressed information can be determined according to the actual situation.
  • the embodiments of this application are Not limited.
  • the server when the push worker receives the push task issued by the push manager through the message queue (MQ), the server obtains the transmission control protocol connection corresponding to the client from the storage pool (global map) (TCP connection), use the client push path to add to the original header frame (header frame) and set the status value in the header frame to 200 (the status value can also be other values, the specific value can be determined according to the actual situation , the embodiments of the present application do not limit this), add the information to be pushed (data AES encryption) to the information frame (Data frame), and push the header frame and the information frame to the client.
  • TCP connection storage pool
  • the client push path to add to the original header frame (header frame) and set the status value in the header frame to 200
  • the status value can also be other values, the specific value can be determined according to the actual situation , the embodiments of the present application do not limit this
  • add the information to be pushed data AES encryption
  • the server will also modify Netty's HTTP/2 parsing source code and delete the relevant checksum logic processing corresponding to the Push Promise frame.
  • the server when the server pushes the information to be pushed to the client, it will send three types of frames to the client.
  • the first frame is the Push Promise frame.
  • the Push Promise frame contains the Path and Method of the pushed resource (predicted http Method), Scheme, Authority, push stream ID (ID is an even number) and active network request stream ID (ID is an odd number), etc.
  • the client When the client receives the Push Promise frame, the client will check whether the client has Turn on push, check whether the current status of the main request stream can receive Push, establish the mapping relationship between Path and push stream ID, etc. After that, the server will also send the second frame, Header (Http header), and the third frame, Data (Http body) frame.
  • Header Http header
  • Data Http body
  • the Push Promise frame is deleted (that is, the Push Promise frame is not sent) and the subsequent inspection, related verification and logical processing corresponding to the Push Promise frame are deleted, and the Path in the Push Promise frame is added to the Header frame for delivery. , only using Header and Data frames to complete the pushing process of information to be pushed.
  • the server after the server uses the transmission control protocol connection in the storage pool to push the information to be pushed to the client, the server will also receive the push success response information transmitted by the client.
  • the response information of a successful push can be an ACK frame; the response information of a successful push can also be other forms of response information; the specific response information of a successful push can be determined according to the actual situation, and this is not the case in the embodiments of this application. limited.
  • the server is also configured to parse and process the push success receipt Ack frame (0x0A).
  • the ID of the stream corresponding to the Ack frame is the ID of the push stream.
  • the format of the ACK frame is the same as the format of the Ping frame.
  • the server adds the TCP connection to the storage pool and uses the storage pool to store the TCP connection, so that the server obtains the TCP connection.
  • the server can directly use the transmission control protocol connection to push the information to be pushed to the client, which improves the speed of pushing the information to be pushed.
  • FIG. 4 is a flow chart 2 of an information push method provided by the embodiment of the present application. As shown in Figure 4, the information push method may include:
  • S201 Send a hypertext transmission request to the server; to establish a transmission control protocol connection with the server according to the hypertext transmission request.
  • An information push method provided by the embodiment of the present application is suitable for the scenario where the server sends information to be pushed to the client.
  • the client can be implemented in various forms.
  • the client described in this application may include mobile phones, cameras, tablets, laptops, PDAs, personal digital assistants (Personal Digital Assistant, PDA), portable media players (Portable Media Player, PMP), navigation devices, wearable devices, smart bracelets, pedometers and other devices, as well as devices such as digital TVs, desktop computers and other devices.
  • the hypertext transmission request may be an HTTP request.
  • the transmission control protocol connection may be a transmission control protocol (Transmission Control Protocol, TCP) connection.
  • TCP Transmission Control Protocol
  • the process of establishing a transmission control protocol connection between the server and the client according to the hypertext transmission request is the TCP connection method between the server and the client in the prior art.
  • the specific embodiment of the present application No detailed explanation will be given here.
  • the client is a client that integrates an open source network library that supports HTTP/2; and the client has turned on the push switch of the HTTP/2 Setting frame.
  • the client modified the network library, that is, deleted the Push Promise frame and related checks before and after, and directly parsed the header frame (Header) and information in the service to be pushed when the Stream ID is an even number.
  • Frame(Data) the header frame (Header) and information in the service to be pushed when the Stream ID is an even number.
  • the server when the server pushes the information to be pushed to the client, it will send three types of frames to the client.
  • the first frame is the Push Promise frame.
  • the Push Promise frame contains the Path and Method of the pushed resource (predicted http Method), Scheme, Authority, push stream ID (even number) and active network request stream ID (odd number), etc.
  • the client When the client receives the Push Promise frame, the client will check whether the client has turned on push, main Whether the current status of the requested stream can receive Push, establish the mapping relationship between Path and push stream ID, etc. After that, the server will also send the second frame, Header (Http header), and the third frame, Data (Http body) frame.
  • Header Http header
  • Data Http body
  • the Push Promise frame is deleted (that is, the Push Promise frame is not sent) and the subsequent inspection, related verification and logical processing corresponding to the Push Promise frame are deleted, and the Path in the Push Promise frame is added to the Header frame for delivery. , only using Header and Data frames to complete the pushing process of information to be pushed.
  • the client after the client sends a hypertext transmission request to the server, the client will also obtain the sending time of the hypertext transmission request; the client adjusts the first time to send heartbeat information to the server next time based on the sending time; the client When the client arrives for the first time, it sends the next heartbeat information to the server.
  • HTTP/2 provides a heartbeat (PING) mechanism to maintain the connection and calculate the RTT round-trip time.
  • the RTT time optimization heartbeat sending interval can be achieved by reusing the PING.
  • the client enables the heartbeat function of HTTP/2, treats the HTTP request as a heartbeat, and optimizes the next heartbeat sending time based on the network round-trip time (RTT) of the heartbeat frame. separated.
  • RTT network round-trip time
  • the client can send a heartbeat frame to the server at a preset time interval. For example, a heartbeat frame will be sent to the server every 5 minutes. That is, a heartbeat frame will be sent to the server every 1 minute, and then sent to the server after an interval of 5 minutes.
  • the server sends a heartbeat frame. At the 7th minute, it gets a hypertext transfer request, and then sends a hypertext transfer request to the server at the 7th minute. After 5 minutes, that is, at the 12th minute, it continues to send heartbeats to the server. frame,....
  • the client sends a hypertext transfer request to the server; after establishing a TCP connection with the server based on the hypertext transfer request, the client can add the TCP connection to the connection pool, And according to the transmission control protocol connection in the connection pool, the information to be pushed is received from the server.
  • the connection pool includes at least one Transmission Control Protocol connection.
  • the client puts the HTTP/2 TCP long connection (Transmission Control Protocol connection) used for push into the multiplexed connection pool (connection pool), adds a whitelist, and permanently controls the Transmission Control Protocol connection. No active release and elimination processing will be performed, and TCP anti-kill and automatic restart will be added (if required to support App offline push).
  • HTTP/2 TCP long connection Transmission Control Protocol connection
  • the process of the client connecting to receive the information to be pushed transmitted by the server according to the transmission control protocol in the connection pool also includes: the client connecting and receiving the service to be pushed transmitted by the server according to the transmission control protocol; accordingly, the client
  • the process of the client receiving the information to be pushed transmitted by the server according to the transmission control protocol connection in the connection pool includes: the client obtains the header frame and information frame from the service to be pushed; the client obtains the client push path from the header frame; and obtains the client push path from the information Obtain the information to be pushed; the client transmits the information to be pushed to the target application corresponding to the client push path.
  • the client provides push information registration and information distribution entrances.
  • the client receives the service to be pushed, the client first processes the encrypted information in the information frame (Data frame).
  • the information is decrypted to obtain the information to be pushed, and then the client transmits the information to be pushed to the corresponding registrant (such as an application) according to the path (Path) in the header frame (Header).
  • the client after the client receives the information to be pushed transmitted by the server according to the transmission control protocol connection in the connection pool, the client will also send a push success response message to the server.
  • the response information of successful push can be an ACK frame; the response information of successful push can also be other forms of response information; the specific response information of successful push can be determined according to the actual situation.
  • the embodiment of this application This is not a limitation.
  • the client when the client receives a Header frame and a Data frame, the client sends an ACK frame (frame type 0x0A) to the server.
  • the format of the ACK frame is the same as that of the Ping frame.
  • the ID of the stream corresponding to the ACK frame is the ID of the push stream.
  • the Push protocol is shown in Figure 5: the client sends a hypertext transmission request (index.html request, specifically including: stream 1 type: 1; method get; path/index.html;...); the server Obtain the request information corresponding to the HTTP request (stream 1 type: 1; date xxxx; cache-controller...), and the server transmits the request information to the client; the server establishes a transmission control protocol with the client based on the hypertext transfer request Connection; the server adds the transmission control protocol connection to the storage pool; the client adds the transmission control protocol connection to the connection pool, and the server obtains the information to be pushed (x.json or xx.pb) corresponding to the client Next, the server uses the transmission control protocol connection in the storage pool to push the information to be pushed to the client. When the client receives the information to be pushed, the client sends a push success response message (ACK frame) to the server.
  • ACK frame push success response message
  • x.json includes: push business identifier (stream 2n type: 1; status: 200; path/business xxx) and push message (stream 2n type: 0 ⁇ "xx"; "xxx" ⁇ ).
  • xx.pb includes: push service identification (stream 2n+2 type: 1; status: 200; path/business xxxxx) and push message (stream 2n+2 type: 0; 0101111000).
  • the push manager obtains the push CMS (including information source: businessid; information content (msg): hello; client (user): xxxx), the push manager is in the database (DB), queries the push path (path) based on the businessid, and then the push manager creates a push task based on the obtained information, and Broadcast the push task (path:/xxx; client: xxxx; msg: 010100111...) to the push worker of each target machine.
  • the push worker obtains the information to be pushed (header frame, data frame: aes (msg)) from the push task. ), and push the push information to the corresponding client (APP).
  • Push workers can also be pushed to the target server HTTP or nginx through a reverse proxy.
  • the server also receives Http requests transmitted by the APP through push workers.
  • the client after the client establishes a TCP connection with the server based on a hypertext transfer request, the client adds the TCP connection to the connection pool and uses the connection pool to store the TCP connection, so that The client can use the transmission control protocol connection to promptly receive the information to be pushed from the server, which improves the speed of pushing the information to be pushed.
  • the embodiment of the present application provides a server 1, corresponding to an information push method applied to the server;
  • Figure 7 is a diagram of a server provided by the embodiment of the present application.
  • Composition structure diagram 1 the server 1 may include:
  • the establishment part 11 is configured to, upon receiving a hypertext transmission request transmitted by the client, establish a transmission control protocol connection with the client according to the hypertext transmission request;
  • the first adding part 12 is configured to add the transmission control protocol connection to a storage pool, where the storage pool includes at least one transmission control protocol connection;
  • the push part 13 is configured to push the information to be pushed to the client using the transmission control protocol connection in the storage pool when the information to be pushed corresponding to the client is obtained.
  • the server further includes a first obtaining part and a determining part
  • the first acquisition part is configured to acquire the original header frame and the original information frame corresponding to the original push service
  • the determining part is configured to determine the client push path corresponding to the information to be pushed;
  • the first adding part 12 is configured to add the client push path to the original header frame to obtain a header frame; add the information to be pushed to the original information frame to obtain an information frame; according to the The information frame and the header frame are served to be pushed;
  • the push part 13 is configured to push the service to be pushed to the client using the transmission control protocol connection.
  • the server further includes a configuration part
  • the configuration part is configured to configure the corresponding relationship between the transmission control protocol connection and the client;
  • the first adding part 12 is configured to add the transmission control protocol connection and the corresponding relationship between the transmission control protocol connection and the client to the storage pool.
  • the server further includes a deletion part
  • the deletion part is configured to delete the TCP connection from the storage pool when the TCP connection is disconnected.
  • the server further includes a first receiving part
  • the first receiving part is configured to receive the push success response information transmitted by the client.
  • the above-mentioned establishment part 11, first adding part 12 and push part 13 can be implemented by the first processor 14 on the server 1, specifically a CPU (Central Processing Unit, central processing unit), MPU (Microprocessor Unit, microprocessor), DSP (Digital Signal Processing, digital signal processor) or field programmable gate array (FPGA, Field Programmable Gate Array), etc.; the above data storage can be implemented by the first memory 15 on the server 1 .
  • CPU Central Processing Unit, central processing unit
  • MPU Microprocessor Unit, microprocessor
  • DSP Digital Signal Processing, digital signal processor
  • FPGA Field Programmable Gate Array
  • the embodiment of the present application also provides a server 1.
  • the server 1 includes: A first processor 14, a first memory 15 and a first communication bus 16.
  • the first memory 15 communicates with the first processor 14 through the first communication bus 16.
  • the first memory 15 stores all
  • the first processor 14 is a program executable. When the program is executed, the first processor 14 executes the information pushing method as described above.
  • the above-mentioned first memory 15 can be a volatile memory (volatile memory), such as a random access memory (Random-Access Memory, RAM); or a non-volatile memory (non-volatile memory), such as a random access memory (RAM).
  • volatile memory such as a random access memory (Random-Access Memory, RAM); or a non-volatile memory (non-volatile memory), such as a random access memory (RAM).
  • RAM Random-Access Memory
  • RAM random access memory
  • RAM random access memory
  • non-volatile memory such as a random access memory (RAM).
  • ROM Read-Only Memory
  • flash memory flash memory
  • HDD Hard Disk Drive
  • SSD solid-state drive
  • Embodiments of the present application provide a computer-readable storage medium with a computer program thereon.
  • the program is executed by the first processor 14, the information pushing method as described above is implemented.
  • the server adds the TCP connection to the storage pool and uses the storage pool to store the TCP connection, so that the server obtains the TCP connection.
  • the server can directly use the transmission control protocol connection to push the information to be pushed to the client, which improves the speed of pushing the information to be pushed.
  • the embodiment of the present application provides a client 2, corresponding to an information push method applied in the client;
  • Figure 9 is a schematic structural diagram of a client provided by the embodiment of the present application.
  • the client 2 may include :
  • the transmission part 21 is configured to send a hypertext transmission request to the server; to establish a transmission control protocol connection with the server according to the hypertext transmission request;
  • the second adding part 22 is configured to add the transmission control protocol connection to the connection pool
  • the second receiving part 23 is configured to receive the information to be pushed transmitted by the server according to the transmission control protocol connection in the connection pool.
  • the second receiving part 23 is configured to receive the service to be pushed transmitted by the server according to the transmission control protocol connection;
  • the client also includes a second acquisition part
  • the second acquisition part is configured to acquire a header frame and an information frame from the service to be pushed; acquire the client push path from the header frame; and acquire the information to be pushed from the information;
  • the transmission part 21 is configured to transmit the information to be pushed to the target application corresponding to the client push path.
  • the client further includes an adjustment part and a sending part
  • the second acquisition part is configured to acquire the sending time of the hypertext transmission request
  • the adjustment part is configured to adjust the first time for next sending heartbeat information to the server according to the sending time
  • the sending part is configured to send the next heartbeat information to the server when the first time arrives.
  • the sending part is configured to send response information indicating a successful push to the server.
  • the above-mentioned transmission part 21, the second adding part 22 and the second receiving part 23 can be implemented by the second processor 24 on the client 2, specifically a CPU (Central Processing Unit). ), MPU (Microprocessor Unit, Microprocessor), DSP (Digital Signal Processing, Digital Signal Processor) or Field Programmable Gate Array (FPGA, Field Programmable Gate Array), etc.; the above data storage can be implemented by the third client on Client 2 Two memories 25 are implemented.
  • CPU Central Processing Unit
  • MPU Microprocessor Unit, Microprocessor
  • DSP Digital Signal Processing, Digital Signal Processor
  • FPGA Field Programmable Gate Array
  • the embodiment of the present application also provides a client 2.
  • the client 2 includes: a second processor 24, a second memory 25 and a second communication bus 26.
  • the second memory 25 passes The second communication bus 26 communicates with the second processor 24, and the second memory 25 stores a program executable by the second processor 24.
  • the second memory 25 stores a program executable by the second processor 24.
  • the processor 24 executes the information pushing method as described above.
  • the above-mentioned second memory 25 can be a volatile memory (volatile memory), such as a random access memory (Random-Access Memory, RAM); or a non-volatile memory (non-volatile memory), such as a random access memory (RAM); Read-Only Memory (ROM), flash memory (flash memory), hard disk (Hard Disk Drive, HDD) or solid-state drive (Solid-State Drive, SSD); or a combination of the above types of memory, and submit to the third Second processor 24 provides instructions and data.
  • volatile memory such as a random access memory (Random-Access Memory, RAM); or a non-volatile memory (non-volatile memory), such as a random access memory (RAM); Read-Only Memory (ROM), flash memory (flash memory), hard disk (Hard Disk Drive, HDD) or solid-state drive (Solid-State Drive, SSD); or a combination of the above types of memory, and submit to the third Second processor 24 provides instructions and data.
  • volatile memory such as
  • the embodiment of the present application provides a computer-readable storage medium with a computer program on it.
  • the program is executed by the second processor 24, the information pushing method as described above is implemented.
  • the client after the client establishes a TCP connection with the server based on a hypertext transfer request, the client adds the TCP connection to the connection pool and uses the connection pool to store the TCP connection, so that The client can use the transmission control protocol connection to promptly receive the information to be pushed from the server, which improves the speed of pushing the information to be pushed.
  • embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, magnetic disk storage and optical storage, etc.) embodying computer-usable program code therein.
  • a computer-usable storage media including, but not limited to, magnetic disk storage and optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions
  • the device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device.
  • Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.
  • Embodiments of the present application provide an information push method, a server, a client, and a storage medium.
  • the information push method includes: upon receiving a hypertext transmission request transmitted by the client, establishing a connection with the client according to the hypertext transmission request. Transmission Control Protocol connection between The control protocol connection pushes the information to be pushed to the client.
  • the server adds the TCP connection to the storage pool and uses the storage pool to store the TCP connection, so that the server can When the information to be pushed is obtained, the server can directly use the transmission control protocol connection to push the information to be pushed to the client, which improves the speed of pushing the information to be pushed.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请实施例公开了一种信息推送方法及服务器、客户端、存储介质，包括：在接收到客户端传输的超文本传输请求的情况下，根据超文本传输请求建立与客户端之间的传输控制协议连接；将传输控制协议连接添加至存储池中，存储池中包括至少一个传输控制协议连接；在获取到与客户端对应的待推送信息的情况下，利用存储池中的传输控制协议连接将待推送信息推送至客户端。

Description

一种信息推送方法及服务器、客户端、存储介质
相关申请的交叉引用
本申请要求在2022年03月29日提交中国专利局、申请号为202210323009.0、申请名称为“一种信息推送方法及服务器、客户端、存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及信息推送技术领域，涉及但不限于一种信息推送方法及服务器、客户端、存储介质。
背景技术
随着互联网技术的高速发展，网络的使用量逐渐增加，为了提升网页的加载速度，服务器会预测浏览器可能使用到的资源，并将这些资源推送至客户端，以供浏览器使用资源时直接从浏览器所处的客户端内存中获取。
相关技术中，是服务器在接收到客户端发送的超文本传输协议(Hypertext Transfer Protocol，HTTP)请求的情况下，获取与该HTTP请求对应的请求信息，并获取需要推送的信息，在向客户端发送请求信息的情况下，在请求信息中携带需要推送的信息，如此降低了服务器向客户端推送信息时的速度。
发明内容
为解决上述技术问题，本申请实施例期望提供一种信息推送方法及服务器、客户端、存储介质，能够提高推送信息时的速度。
本申请的技术方案是这样实现的：
本申请实施例提供一种信息推送方法，应用于服务器，所述信息推送 方法包括：
在接收到客户端传输的超文本传输请求的情况下，根据所述超文本传输请求建立与所述客户端之间的传输控制协议连接；
将所述传输控制协议连接添加至存储池中，所述存储池中包括至少一个传输控制协议连接；
在获取到与所述客户端对应的待推送信息的情况下，利用所述存储池中的所述传输控制协议连接将所述待推送信息推送至所述客户端。
本申请实施例又提供一种信息推送方法，应用于客户端，所述信息推送方法包括：
向服务器发送超文本传输请求；以根据所述超文本传输请求建立与所述服务器之间的传输控制协议连接；
将所述传输控制协议连接添加至连接池中，并根据所述连接池中的所述传输控制协议连接接收所述服务器传输的待推送信息。
本申请实施例提供了一种服务器，所述服务器包括：
建立部分，配置于在接收到客户端传输的超文本传输请求的情况下，根据所述超文本传输请求建立与所述客户端之间的传输控制协议连接；
第一添加部分，配置于将所述传输控制协议连接添加至存储池中，所述存储池中包括至少一个传输控制协议连接；
推送部分，配置于在获取到与所述客户端对应的待推送信息的情况下，利用所述存储池中的所述传输控制协议连接将所述待推送信息推送至所述客户端。
本申请实施例提供了一种客户端，所述客户端包括：
传输部分，配置于向服务器发送超文本传输请求；以根据所述超文本传输请求建立与所述服务器之间的传输控制协议连接；
添加部分，配置于将所述传输控制协议连接添加至连接池中；
第二接收部分，配置于根据所述连接池中的所述传输控制协议连接接 收所述服务器传输的待推送信息。
本申请实施例又提供了一种服务器，所述服务器包括：
第一存储器、第一处理器和第一通信总线，所述第一存储器通过所述第一通信总线与所述第一处理器进行通信，所述第一存储器存储所述第一处理器可执行的信息推送的程序，当所述信息推送的程序被执行时，通过所述第一处理器执行上述所述的应用于服务器中的信息推送方法。
本申请实施例又提供了一种客户端，所述客户端包括：
第二存储器、第二处理器和第二通信总线，所述第二存储器通过所述第二通信总线与所述第二处理器进行通信，所述第二存储器存储所述第二处理器可执行的信息推送的程序，当所述信息推送的程序被执行时，通过所述第二处理器执行上述所述的应用于客户端中的信息推送方法。
本申请实施例提供了一种存储介质，其上存储有计算机程序，应用于客户端和服务器，该计算机程序被第一处理器执行时实现上述所述的应用于服务器中的信息推送方法；该计算机程序被第二处理器执行时实现上述所述的应用于客户端中的信息推送方法。
本申请实施例提供了一种信息推送方法及服务器、客户端、存储介质，信息推送方法包括：在接收到客户端传输的超文本传输请求的情况下，根据超文本传输请求建立与客户端之间的传输控制协议连接；将传输控制协议连接添加至存储池中，存储池中包括至少一个传输控制协议连接；在获取到与客户端对应的待推送信息的情况下，利用存储池中的传输控制协议连接将待推送信息推送至客户端。采用上述方法实现方案，服务器在建立了与客户端之间的传输控制协议连接之后，服务器通过将传输控制协议连接添加至存储池中，利用存储池来将传输控制协议连接进行存储，使得服务器在获取到待推送信息的情况下，服务器可以直接利用该传输控制协议连接向该客户端推送待推送信息，提高了推送待推送信息时的速度。
附图说明
此处的附图被并入说明书中构成本说明书的一部分，这些附图示出了符合本申请的实施例，并与说明书一起用于说明本申请的技术方案。
图1(a)为本申请实施例提供的一种现有技术中的HTTP持久性连接示意图一；
图1(b)为本申请实施例提供的一种现有技术中的HTTP持久性连接示意图二；
图1(c)为本申请实施例提供的一种现有技术中的HTTP持久性连接示意图三；
图2为本申请实施例提供的一种现有技术中的HTTP/2服务推送协议示意图；
图3为本申请实施例提供的一种信息推送方法流程图一；
图4为本申请实施例提供的一种信息推送方法流程图二；
图5为本申请实施例提供的一种示例性的改进的HTTP/2服务推送协议示意图；
图6为本申请实施例提供的一种示例性的信息推送结构示意图；
图7为本申请实施例提供的一种服务器的组成结构示意图一；
图8本申请实施例提供的一种服务器的组成结构示意图二；
图9为本申请实施例提供的一种客户端的组成结构示意图一；
图10为本申请实施例提供的一种客户端组成结构示意图二。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
如图1(a)所示：HTTP1.0无复用，是服务器在接收到客户端发送的 HTTP请求的情况下，就获取该HTTP请求对应的请求信息；将该请求信息传输至客户端处，且客户端接收到该请求信息与客户端下一个发送HTTP请求之间需要间隔一段时间；如图1(b)所示：HTTP1.1是连接复用，服务器在接收到客户端发送的HTTP请求的情况下，就获取该HTTP请求对应的请求信息；将该请求信息传输至客户端处，且客户端接收到该请求信息与客户端下一个发送HTTP请求之间不需要间隔；如图1(c)所示：HTTP/2是多路复用，服务器在接收到客户端发送的HTTP请求的情况下，就获取该HTTP请求对应的请求信息；将该请求信息传输至客户端处，在客户端还未接收到该请求信息的情况下，客户端就可以向服务器发送下一个HTTP请求。
如图2所示：客户端向服务器发送超文本传输请求(index.html请求，具体包括：stream 1 type：1；method get；path/index.html；…)；服务器并获取与该HTTP请求对应的请求信息(stream 1 type：1；date xxxx；cache-controller…)，服务器还会获取需要推送的信息，服务器向客户端传输该请求信息和需要推送的信息；其中，需要推送的信息包括index.css信息和index.js信息。需要说明的是，index.css信息包括Push promise帧-推送序言(stream 2 type：5；method get；path/index.css；authority ip:443；scheme https)、Header帧-Header(stream 2 type：1；status 200；content-type xx；content-length xxx；…)、Date帧-body(stream 2 type：0；body{…}…)；index.js信息包括Push promise帧-推送序言(stream 4 type：5；method get；path/index.js；authority ip:443；scheme https)、Header帧-Header(stream 4 type：1；status 200；content-type xx；content-length xxx；…)、Date帧-body(stream4 type：0；function click(){…}…)。
对于现有技术中存在的问题，具体可通过下述实施例中的方法进行解决。
本申请实施例提供了一种信息推送方法，一种信息推送方法应用于服务器，图3为本申请实施例提供的一种信息推送方法流程图，如图3所示，信息推送方法可以包括：
S101、在接收到客户端传输的超文本传输请求的情况下，根据超文本传输请求建立与客户端之间的传输控制协议连接。
本申请实施例提供的一种信息推送方法适用于服务器向客户端发送待推送信息的场景下。
在本申请实施例中，服务器可以以各种形式来实施。例如，本申请中描述的服务器可以包括诸如手机、照相机、平板电脑、笔记本电脑、掌上电脑、个人数字助理(Personal Digital Assistant，PDA)、便捷式媒体播放器(Portable Media Player，PMP)、导航装置、可穿戴设备、智能手环、计步器等装置，以及诸如数字TV、台式计算机、服务器等装置。
在本申请实施例中，超文本传输请求可以为HTTP请求。传输控制协议连接可以为传输控制协议(Transmission Control Protocol，TCP)连接。
在本申请实施例中，服务器根据超文本传输请求建立与客户端之间的传输控制协议连接的过程，为现有技术中建立服务器与客户端之间的TCP连接方式，具体的本申请实施例在此不作具体的阐述。
在本申请实施例中，客户端为集成支持HTTP/2的开源网络库的客户端；且该客户端已打开HTTP/2 Setting帧的推送(Push)开关。
在本申请实施例中，服务器根据超文本传输请求建立与客户端之间的传输控制协议连接的过程，可以为服务器设置连接的唯一编码(uuid)/用户身份标识(userid)的，响应状态码为204的HTTP请求路径(Path)，在应用程序(Application，App)启动时，用于建立TCP连接(若App启动发Http请求靶服务器，则不定义此Path)。
需要说明的是，响应状态码为204的请求是指没有响应信息的请求。
在本申请实施例中，服务器中的职责推送Server服务分为推送工作 (Worker)和推送管理(Manager)，即服务器分为推送Worker和推送Manager。其中，Worker用于收集和管理HTTP的TCP长连接、发送推送消息和反向代理靶服务器的Http请求；Manger用于Worker的注册、管理、给Worker下达推送任务、提供内容管理系统(content management system，cms)应用程序接口(Application Programming Interface，api)等。Manger和Worker之间可以通过消息队列(MQ)进行通信。
在本申请实施例中，服务器先生成服务器证书(Secure socket layer，SSL)、搭建Netty HTTP/2容器作推送Worker，开启Http gzip压缩，使用443端口，用于响应HTTP/2网络请求；服务器推送Worker添加有反向代理功能，使用配置文件push.properties可以读取靶服务器端口(port)，Worker在启动时读取靶服务器端口的端口号，反向代理靶服务器的http请求(只做了一次http://localhost:port/{{path}}的网络访问)。
需要说明的是，Netty为以异步事件驱动的网络应用程序框架和工具，用于实现HTTP/2协议的解析与响应。
需要说明的是，搭建推送Manager，集成消息队列(MQ)，可以通过MQ给推送Worker下达推送任务，提供cms推送和api接口等。部署推送Worker和推送Manager，并设置push.properties配置文件，内容为靶服务器使用的端口(由于443端口用于推送Worker，故此处的端口可以为除443端口外的其他端口)，部署推送Worker至靶机。推送Manager可以单独部署。
还需要说明的是，CMS推送是指在网页上操作推送某个任务。
在本申请实施例中，复用频繁访问的HTTP/2的TCP连接作为TCP长连接通道，HTTP/2的服务器称为靶服务器，其所在的主机称为靶机。
S102、将传输控制协议连接添加至存储池中，存储池中包括至少一个传输控制协议连接。
在本申请实施例中，服务器根据超文本传输请求建立与客户端之间的传输控制协议连接之后，服务器就将传输控制协议连接添加至存储池中。
需要说明的是，存储池中包括至少一个传输控制协议连接。
在本申请实施例中，存储池可以为全局Map；存储池也可以为其他的存储区域；具体的存储池可以根据实际情况进行确定，本申请实施例对此不作限定。
在本申请实施例中，服务器将传输控制协议连接添加至存储池中之前，服务器还会配置传输控制协议连接与客户端之间的对应关系；相应的，服务器将传输控制协议连接添加至存储池中的过程，包括：服务器将传输控制协议连接与客户端之间的对应关系和传输控制协议连接添加至存储池中。
在本申请实施例中，服务器在建立了TCP连接之后，服务器可以在HTTP/2请求传输结束(Netty HTTP/2 OnSettingsAckRead回调)，建立服务器与客户端之间的传输控制协议连接之后，服务器就把TCP连接放入存储池(全局Map)内，其中，全局Map的键为Http请求带的客户端uuid/userid参数，Map的值为TCP连接(userid为tcp列表)。
在本申请实施例中，服务器将传输控制协议连接添加至存储池中之后，服务器还会在传输控制协议连接断开的情况下，从存储池中删除传输控制协议连接。
S103、在获取到与客户端对应的待推送信息的情况下，利用存储池中的传输控制协议连接将待推送信息推送至客户端。
在本申请实施例中，服务器将传输控制协议连接添加至存储池中之后，服务器在获取到与客户端对应的待推送信息的情况下，服务器就利用存储池中的传输控制协议连接将待推送信息推送至客户端。
在本申请实施例中，待推送信息可以为层叠样式表(Cascading Style Sheets，CSS)资源；待推送信息也可以为javascript(JS)资源；待推送信息还可以为其他的信息；具体的待推送信息可以根据实际情况进行确定，本申请实施例对此不作限定。
需要说明的是，待推送信息为将要为客户端推送的、客户端会用到的 信息。
在本申请实施例中，服务器利用存储池中的传输控制协议连接将待推送信息推送至客户端的过程，包括：服务器获取原始推送服务对应的原始头帧和原始信息帧；服务器确定待推送信息对应的客户端推送路径；并将客户端推送路径添加至原始头帧中，得到头帧；服务器将所述待推送信息添加至原始信息帧中，得到信息帧；服务器根据信息帧和头帧得到待推送服务；并利用传输控制协议连接将待推送服务推送至客户端。
在本申请实施例中，服务器将所述待推送信息添加至原始信息帧中，得到信息帧的过程，包括服务器对待推送信息进行加密，得到加密信息，之后服务器就将加密信息添加至原始信息帧中，得到信息帧；服务器也可以对待推送信息进行压缩，得到压缩信息，之后服务器就将压缩信息添加至原始信息帧中，得到信息帧；服务器还可以直接将待推送信息添加至原始信息帧中，得到信息帧；具体的服务器将所述待推送信息添加至原始信息帧中，得到信息帧的过程可以根据实际情况进行确定，本申请实施例对此不作限定。
需要说明的是，服务器对待推送信息进行加密，得到加密信息的方式，可以为服务器利用高级加密标准(Advanced Encryption Standard，AES)对待推送信息进行加密，得到加密信息；服务器也可以利用其他方式对待推送信息进行加密，得到加密信息；具体的服务器对待推送信息进行加密，得到加密信息的方式可以根据实际情况进行确定，本申请实施例对此不作限定。
还需要说明的是，服务器利用AES对待推送信息进行加密，得到加密信息时的加密密钥可以为利用魔数、设备uuid、流身份标识(Identity document，ID)和路径指定算法动态生成。
在本申请实施例中，服务器对待推送信息进行压缩，得到压缩信息的过程，可以为服务利用Http gzip压缩方式对待推送信息进行压缩，得到压 缩信息；也可以为服务器利用其他的压缩方式对对待推送信息进行压缩，得到压缩信息；具体的服务器对待推送信息进行压缩，得到压缩信息的方式可以根据实际情况进行确定，本申请实施例对此不作限定。
在本申请实施例中，在推送Worker通过消息队列(MQ)接收到推送Manager下发的推送任务的情况下，服务器就从存储池(全局Map)中获取与该客户端对应的传输控制协议连接(TCP连接)，利用客户端推送路径添加至原始头帧(header帧)并设置header帧中的状态(status)值为200(状态值也可以为其他的数值，具体的可以根据实际情况进行确定，本申请实施例对此不作限定)，将待推送信息(数据aes加密)后添加至信息帧(Data帧)中，并将头帧和信息帧推给给客户端。
在本申请实施例中，服务器还会修改Netty的HTTP/2解析源码，删除Push Promise帧对应的相关校验和逻辑处理。
需要说明的是，服务器向客户端推送待推送信息的过程中会连接发送三种帧给客户端，第一帧是Push Promise帧，Push Promise帧内有被推送资源的Path、Method(预测的http方法)、Scheme、Authority、推送流ID(ID为偶数)和的主动网络请求的流ID(ID为奇数)等，客户端在收到Push Promise帧的情况下，客户端会检查客户端是否已开启推送、主请求的流当前状态是否能接收Push、建立Path与推送流ID映射关系等，之后服务器还会发送第二帧即Header(Http头)、第三帧即Data(Http body)帧。在本申请实施例中，删除了Push Promise帧(即不发送Push Promise帧)以及Push Promise帧对应的后续检查、相关校验和逻辑处理，把Push Pomise帧内的Path添加至Header帧中下发，只使用Header和Data帧完成待推送信息的推送过程。
在本申请实施例中，服务器利用存储池中的传输控制协议连接将待推送信息推送至客户端之后，服务器还会接收客户端传输的推送成功的响应信息。
需要说明的是，推送成功的响应信息可以为ACK帧；推送成功的响应信息也可以为其他形式的响应信息；具体的推送成功的响应信息可以根据实际情况进行确定，本申请实施例对此不作限定。
在本申请实施例中，服务器还配置有推送成功回执Ack帧(0x0A)的解析和处理。Ack帧对应流的ID为推送流的ID。
需要说明的是，ACK帧的格式与Ping帧的格式相同。
可以理解的是，服务器在建立了与客户端之间的传输控制协议连接之后，服务器通过将传输控制协议连接添加至存储池中，利用存储池来将传输控制协议连接进行存储，使得服务器在获取到待推送信息的情况下，服务器可以直接利用该传输控制协议连接向该客户端推送待推送信息，提高了推送待推送信息时的速度。
本申请实施例又提供了一种信息推送方法，应用于客户端中，图4为本申请实施例提供的一种信息推送方法流程图二，如图4所示，信息推送方法可以包括：
S201、向服务器发送超文本传输请求；以根据超文本传输请求建立与服务器之间的传输控制协议连接。
本申请实施例提供的一种信息推送方法适用于服务器向客户端发送待推送信息的场景下。
在本申请实施例中，客户端可以以各种形式来实施。例如，本申请中描述的客户端可以包括诸如手机、照相机、平板电脑、笔记本电脑、掌上电脑、个人数字助理(Personal Digital Assistant，PDA)、便捷式媒体播放器(Portable Media Player，PMP)、导航装置、可穿戴设备、智能手环、计步器等装置，以及诸如数字TV、台式计算机等装置。
在本申请实施例中，超文本传输请求可以为HTTP请求。传输控制协议连接可以为传输控制协议(Transmission Control Protocol，TCP)连接。
在本申请实施例中，服务器根据超文本传输请求建立与客户端之间的传输控制协议连接的过程，为现有技术中建立服务器与客户端之间的TCP连接方式，具体的本申请实施例在此不作具体的阐述。
在本申请实施例中，客户端为集成支持HTTP/2的开源网络库的客户端；且该客户端已打开HTTP/2 Setting帧的推送(Push)开关。
在本申请实施例中，客户端为修改了网络库，即删除了Push Promise帧及前后相关校验，在Stream ID为偶数时直接解析下发的待推送服务中的头帧(Header)和信息帧(Data)。
需要说明的是，服务器向客户端推送待推送信息的过程中会连接发送三种帧给客户端，第一帧是Push Promise帧，Push Promise帧内有被推送资源的Path、Method(预测的http方法)、Scheme、Authority、推送流ID(偶数)和的主动网络请求的流ID(奇数)等，客户端在收到Push Promise帧的情况下，客户端会检查客户端是否已开启推送、主请求的流当前状态是否能接收Push、建立Path与推送流ID映射关系等，之后服务器还会发送第二帧即Header(Http头)、第三帧即Data(Http body)帧。在本申请实施例中，删除了Push Promise帧(即不发送Push Promise帧)以及Push Promise帧对应的后续检查、相关校验和逻辑处理，把Push Pomise帧内的Path添加至Header帧中下发，只使用Header和Data帧完成待推送信息的推送过程。
在本申请实施例中，客户端向服务器发送超文本传输请求之后，客户端还会获取超文本传输请求的发送时间；客户端根据发送时间调整下一次向服务器发送心跳信息的第一时间；客户端在第一时间到达时，向服务器发送下一心跳信息。
在本申请实施例中，HTTP/2提供心跳(PING)机制来保持连接和计算RTT往返时间，可以通过复用该PING，来实现RTT时间优化心跳发送间隔。客户端启用HTTP/2的心跳功能，把Http请求也作为一次心跳，根据心跳帧的网络往返时间Round-Trip Time(RTT)来优化下一次心跳发送间 隔。
需要说明的时，客户端可以间隔预设时间段就向服务器发送一次心跳帧，如间隔5分钟会向服务器发送一次心跳帧，即1分钟时向服务器发送一次心跳帧，间隔5分钟后再向服务器发送一次心跳帧，在第7分钟时，得到了超文本传输请求，则在第7分钟时向服务器发送超文本传输请求，经过5分钟后，即第12分钟时，则继续向服务器发送心跳帧，…。
S202、将传输控制协议连接添加至连接池中，并根据连接池中的传输控制协议连接接收服务器传输的待推送信息。
在本申请实施例中，客户端向服务器发送超文本传输请求；以根据超文本传输请求建立与服务器之间的传输控制协议连接之后，客户端就可以将传输控制协议连接添加至连接池中，并根据连接池中的传输控制协议连接接收服务器传输的待推送信息了。
在本申请实施例中，连接池中包括至少一个传输控制协议连接。
在本申请实施例中，客户端把用于推送的HTTP/2的TCP长连接(传输控制协议连接)放入复用连接池(连接池)中，加白名单，对于该传输控制协议连接永不做主动释放和淘汰处理，并添加TCP防杀和自动重启(若要求支持App离线推送)。
在本申请实施例中，客户端根据连接池中的传输控制协议连接接收服务器传输的待推送信息的过程，还包括：客户端根据传输控制协议连接接收服务器传输的待推送服务；相应的，客户端根据连接池中的传输控制协议连接接收服务器传输的待推送信息的过程，包括：客户端从待推送服务中获取头帧和信息帧；客户端从头帧中获取客户端推送路径；并从信息中获取待推送信息；客户端向客户端推送路径对应的目标应用传输待推送信息。
在本申请实施例中，客户端提供推送信息注册和信息分发入口，客户端在收到待推送服务的情况下，客户端先对信息帧(Data帧)内的加密信 息进行解密得到待推送信息，之后客户客户端再根据头帧(Header)中的路径(Path)将待推送信息传输至对应的注册者(如：应用)。
在本申请实施例中，客户端根据连接池中的传输控制协议连接接收服务器传输的待推送信息之后，客户端还会向服务器发送推送成功的响应信息。
在本申请实施例中，推送成功的响应信息可以为ACK帧；推送成功的响应信息也可以为其他形式的响应信息；具体的推送成功的响应信息可以根据实际情况进行确定，本申请实施例对此不作限定。
在本申请实施例中，客户端在接收搭配Header帧、Data帧的情况下，客户端就发送ACK帧(帧类型0x0A)至服务端，其中，ACK帧的格式与Ping帧的格式相同。ACK帧对应流的ID为推送流的ID。
示例性的，Push协议如图5所示：客户端向服务器发送超文本传输请求(index.html请求，具体包括：stream 1 type：1；method get；path/index.html；…)；服务器并获取与该HTTP请求对应的请求信息(stream 1 type：1；date xxxx；cache-controller…)，服务器向客户端传输该请求信息；服务器根据超文本传输请求建立与客户端之间的传输控制协议连接；服务器将传输控制协议连接添加至存储池中；客户端将传输控制协议连接添加至连接池中，在服务器获取到与客户端对应的待推送信息(x.json或者xx.pb)的情况下，服务器利用存储池中的传输控制协议连接将待推送信息推送至客户端，客户端在接收到待推送信息的情况下，客户端就向服务器发送推送成功的响应信息(ACK帧)。
需要说明的是，x.json包括：推送业务标识(stream 2n type：1；status:200；path/业务xxx)和推送报文(stream 2n type：0{“xx”；“xxx”})。xx.pb包括：推送业务标识(stream 2n+2 type：1；status:200；path/业务xxxxx)和推送报文(stream 2n+2 type：0；0101111000…)。
示例性的，如图6所示：推送manager获取推送CMS(包括信息来源： businessid；信息内容(msg)：hello；客户端(user)：xxxx)，推送manager在数据库(DB)中，根据businessid查询推送路径(path)，之后推送manager就根据获取的信息建立推送任务，并广播该推送任务(path:/xxx；客户端：xxxx；msg：010100111…)至各个靶机的推送worker，推送worker从该推送任务中获取待推送信息(header帧、data帧：aes(msg))，并将该推送信息推送至对应的客户端(APP)。推送worker也可以通过反向代理至靶服务器Http或者nginx。服务器也是通过推送worker接收APP传输的Http请求。
可以理解的是，客户端在根据超文本传输请求与服务器之间建立了传输控制协议连接之后，客户端通过将传输控制协议连接添加至连接池中，利用连接池来存储传输控制协议连接，使得客户端可以利用传输控制协议连接来及时接收服务器发送的待推送信息，提高了推送待推送信息时的速度。
基于应用于服务器中的信息推送方法同一发明构思，本申请实施例提供了一种服务器1，对应于一种应用于服务器中的信息推送方法；图7为本申请实施例提供的一种服务器的组成结构示意图一，该服务器1可以包括：
建立部分11，配置于在接收到客户端传输的超文本传输请求的情况下，根据所述超文本传输请求建立与所述客户端之间的传输控制协议连接；
第一添加部分12，配置于将所述传输控制协议连接添加至存储池中，所述存储池中包括至少一个传输控制协议连接；
推送部分13，配置于在获取到与所述客户端对应的待推送信息的情况下，利用所述存储池中的所述传输控制协议连接将所述待推送信息推送至所述客户端。
在本申请的一些实施例中，所述服务器还包括第一获取部分和确定部分；
所述第一获取部分，配置于获取原始推送服务对应的原始头帧和原始信息帧；
所述确定部分，配置于确定待推送信息对应的客户端推送路径；
所述第一添加部分12，配置于将所述客户端推送路径添加至原始头帧中，得到头帧；将所述待推送信息添加至所述原始信息帧中，得到信息帧；根据所述信息帧和所述头帧得到待推送服务；
所述推送部分13，配置于利用所述传输控制协议连接将所述待推送服务推送至所述客户端。
在本申请的一些实施例中，所述服务器还包括配置部分；
所述配置部分，配置于配置所述传输控制协议连接与所述客户端之间的对应关系；
相应的，所述第一添加部分12，配置于将所述传输控制协议连接以及所述传输控制协议连接与所述客户端之间的对应关系添加至所述存储池中。
在本申请的一些实施例中，所述服务器还包括删除部分；
所述删除部分，配置于在所述传输控制协议连接断开的情况下，从所述存储池中删除所述传输控制协议连接。
在本申请的一些实施例中，所述服务器还包括第一接收部分；
所述第一接收部分，配置于接收所述客户端传输的推送成功的响应信息。
需要说明的是，在实际应用中，上述建立部分11、第一添加部分12和推送部分13可由服务器1上的第一处理器14实现，具体为CPU(Central Processing Unit，中央处理器)、MPU(Microprocessor Unit，微处理器)、DSP(Digital Signal Processing，数字信号处理器)或现场可编程门阵列(FPGA，Field Programmable Gate Array)等实现；上述数据存储可由服务器1上的第一存储器15实现。
本申请实施例还提供了一种服务器1，如图8所示，所述服务器1包括： 第一处理器14、第一存储器15和第一通信总线16，所述第一存储器15通过所述第一通信总线16与所述第一处理器14进行通信，所述第一存储器15存储所述第一处理器14可执行的程序，当所述程序被执行时，通过所述第一处理器14执行如上述所述的信息推送方法。
在实际应用中，上述第一存储器15可以是易失性存储器(volatile memory)，例如随机存取存储器(Random-Access Memory，RAM)；或者非易失性存储器(non-volatile memory)，例如只读存储器(Read-Only Memory，ROM)，快闪存储器(flash memory)，硬盘(Hard Disk Drive，HDD)或固态硬盘(Solid-State Drive，SSD)；或者上述种类的存储器的组合，并向第一处理器14提供指令和数据。
本申请实施例提供了一种计算机可读存储介质，其上有计算机程序，所述程序被第一处理器14执行时实现如上述所述的信息推送方法。
可以理解的是，服务器在建立了与客户端之间的传输控制协议连接之后，服务器通过将传输控制协议连接添加至存储池中，利用存储池来将传输控制协议连接进行存储，使得服务器在获取到待推送信息的情况下，服务器可以直接利用该传输控制协议连接向该客户端推送待推送信息，提高了推送待推送信息时的速度。
本申请实施例提供了一种客户端2，对应于一种应用于客户端中的信息推送方法；图9为本申请实施例提供的一种客户端的组成结构示意图一，该客户端2可以包括：
传输部分21，配置于向服务器发送超文本传输请求；以根据所述超文本传输请求建立与所述服务器之间的传输控制协议连接；
第二添加部分22，配置于将所述传输控制协议连接添加至连接池中；
第二接收部分23，配置于根据所述连接池中的所述传输控制协议连接接收所述服务器传输的待推送信息。
在本申请的一些实施例中，所述第二接收部分23，配置于根据所述传输控制协议连接接收所述服务器传输的待推送服务；
相应的，所述客户端还包括第二获取部分；
所述第二获取部分，配置于从所述待推送服务中获取头帧和信息帧；从所述头帧中获取客户端推送路径；并从所述信息中获取所述待推送信息；
所述传输部分21，配置于向所述客户端推送路径对应的目标应用传输所述待推送信息。
在本申请的一些实施例中，所述客户端还包括调整部分和发送部分；
所述第二获取部分，配置于获取所述超文本传输请求的发送时间；
所述调整部分，配置于根据所述发送时间调整下一次向所述服务器发送心跳信息的第一时间；
所述发送部分，配置于在所述第一时间到达时，向所述服务器发送所述下一心跳信息。
在本申请的一些实施例中，所述发送部分，配置于向服务器发送推送成功的响应信息。
需要说明的是，在实际应用中，上述传输部分21、第二添加部分22和第二接收部分23可由客户端2上的第二处理器24实现，具体为CPU(Central Processing Unit，中央处理器)、MPU(Microprocessor Unit，微处理器)、DSP(Digital Signal Processing，数字信号处理器)或现场可编程门阵列(FPGA，Field Programmable Gate Array)等实现；上述数据存储可由客户端2上的第二存储器25实现。
本申请实施例还提供了一种客户端2，如图10所示，所述客户端2包括：第二处理器24、第二存储器25和第二通信总线26，所述第二存储器25通过所述第二通信总线26与所述第二处理器24进行通信，所述第二存储器25存储所述第二处理器24可执行的程序，当所述程序被执行时，通过所述第二处理器24执行如上述所述的信息推送方法。
在实际应用中，上述第二存储器25可以是易失性存储器(volatile memory)，例如随机存取存储器(Random-Access Memory，RAM)；或者非易失性存储器(non-volatile memory)，例如只读存储器(Read-Only Memory，ROM)，快闪存储器(flash memory)，硬盘(Hard Disk Drive，HDD)或固态硬盘(Solid-State Drive，SSD)；或者上述种类的存储器的组合，并向第二处理器24提供指令和数据。
本申请实施例提供了一种计算机可读存储介质，其上有计算机程序，所述程序被第二处理器24执行时实现如上述所述的信息推送方法。
可以理解的是，客户端在根据超文本传输请求与服务器之间建立了传输控制协议连接之后，客户端通过将传输控制协议连接添加至连接池中，利用连接池来存储传输控制协议连接，使得客户端可以利用传输控制协议连接来及时接收服务器发送的待推送信息，提高了推送待推送信息时的速度。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
以上所述，仅为本申请的较佳实施例而已，并非用于限定本申请的保护范围。
工业实用性
本申请实施例提供了一种信息推送方法及服务器、客户端、存储介质，信息推送方法包括：在接收到客户端传输的超文本传输请求的情况下，根据超文本传输请求建立与客户端之间的传输控制协议连接；将传输控制协议连接添加至存储池中，存储池中包括至少一个传输控制协议连接；在获取到与客户端对应的待推送信息的情况下，利用存储池中的传输控制协议连接将待推送信息推送至客户端。采用上述方法实现方案，服务器在建立了与客户端之间的传输控制协议连接之后，服务器通过将传输控制协议连接添加至存储池中，利用存储池来将传输控制协议连接进行存储，使得服务器在获取到待推送信息的情况下，服务器可以直接利用该传输控制协议连接向该客户端推送待推送信息，提高了推送待推送信息时的速度。

Claims (14)

  1. 一种信息推送方法，所述方法包括：
    在接收到客户端传输的超文本传输请求的情况下，根据所述超文本传输请求建立与所述客户端之间的传输控制协议连接；
    将所述传输控制协议连接添加至存储池中，所述存储池中包括至少一个传输控制协议连接；
    在获取到与所述客户端对应的待推送信息的情况下，利用所述存储池中的所述传输控制协议连接将所述待推送信息推送至所述客户端。
  2. 根据权利要求1所述的方法，其中，所述利用所述存储池中的所述传输控制协议连接将所述待推送信息推送至所述客户端，包括：
    获取原始推送服务对应的原始头帧和原始信息帧；
    确定待推送信息对应的客户端推送路径；并将所述客户端推送路径添加至原始头帧中，得到头帧；
    将所述待推送信息添加至所述原始信息帧中，得到信息帧；
    根据所述信息帧和所述头帧得到待推送服务；并利用所述传输控制协议连接将所述待推送服务推送至所述客户端。
  3. 根据权利要求1所述的方法，其中，所述将所述传输控制协议连接添加至存储池中之前，所述方法还包括：
    配置所述传输控制协议连接与所述客户端之间的对应关系；
    相应的，所述将所述传输控制协议连接添加至存储池中，包括：
    将所述传输控制协议连接以及所述传输控制协议连接与所述客户端之间的对应关系添加至所述存储池中。
  4. 根据权利要求1所述的方法，其中，所述将所述传输控制协议连接添加至存储池中之后，所述方法还包括：
    在所述传输控制协议连接断开的情况下，从所述存储池中删除所述传 输控制协议连接。
  5. 根据权利要求1所述的方法，其中，所述利用所述存储池中的所述传输控制协议连接将所述待推送信息推送至所述客户端之后，所述方法还包括：
    接收所述客户端传输的推送成功的响应信息。
  6. 一种信息推送方法，所述方法包括：
    向服务器发送超文本传输请求；以根据所述超文本传输请求建立与所述服务器之间的传输控制协议连接；
    将所述传输控制协议连接添加至连接池中，并根据所述连接池中的所述传输控制协议连接接收所述服务器传输的待推送信息。
  7. 根据权利要求6所述的方法，其中，所述根据所述连接池中的所述传输控制协议连接接收所述服务器传输的待推送信息，还包括：
    根据所述传输控制协议连接接收所述服务器传输的待推送服务；
    相应的，所述根据所述连接池中的所述传输控制协议连接接收所述服务器传输的待推送信息，包括：
    从所述待推送服务中获取头帧和信息帧；
    从所述头帧中获取客户端推送路径；并从所述信息中获取所述待推送信息；
    向所述客户端推送路径对应的目标应用传输所述待推送信息。
  8. 根据权利要求6所述的方法，其中，所述向服务器发送超文本传输请求之后，所述方法还包括：
    获取所述超文本传输请求的发送时间；
    根据所述发送时间调整下一次向所述服务器发送心跳信息的第一时间；
    在所述第一时间到达时，向所述服务器发送所述下一心跳信息。
  9. 根据权利要求6所述的方法，其中，所述根据所述连接池中的所述传输控制协议连接接收所述服务器传输的待推送信息之后，所述方法还包 括：
    向服务器发送推送成功的响应信息。
  10. 一种服务器，所述服务器包括：
    建立部分，配置于在接收到客户端传输的超文本传输请求的情况下，根据所述超文本传输请求建立与所述客户端之间的传输控制协议连接；
    第一添加部分，配置于将所述传输控制协议连接添加至存储池中，所述存储池中包括至少一个传输控制协议连接；
    推送部分，配置于在获取到与所述客户端对应的待推送信息的情况下，利用所述存储池中的所述传输控制协议连接将所述待推送信息推送至所述客户端。
  11. 一种客户端，所述客户端包括：
    传输部分，配置于向服务器发送超文本传输请求；以根据所述超文本传输请求建立与所述服务器之间的传输控制协议连接；
    第二添加部分，配置于将所述传输控制协议连接添加至连接池中；
    第二接收部分，配置于根据所述连接池中的所述传输控制协议连接接收所述服务器传输的待推送信息。
  12. 一种服务器，所述服务器包括：
    第一存储器、第一处理器和第一通信总线，所述第一存储器通过所述第一通信总线与所述第一处理器进行通信，所述第一存储器存储所述第一处理器可执行的信息推送的程序，当所述信息推送的程序被执行时，通过所述第一处理器执行如权利要求1至5任一项所述的方法。
  13. 一种客户端，所述客户端包括：
    第二存储器、第二处理器和第二通信总线，所述第二存储器通过所述第二通信总线与所述第二处理器进行通信，所述第二存储器存储所述第二处理器可执行的信息推送的程序，当所述信息推送的程序被执行时，通过所述第二处理器执行如权利要求6至9任一项所述的方法。
  14. 一种存储介质，其上存储有计算机程序，应用于服务器和客户端，该计算机程序被第一处理器执行时实现权利要求1至5任一项所述的方法，该计算机程序被第二处理器执行时实现权利要求6至9任一项所述的方法。
PCT/CN2023/084272 2022-03-29 2023-03-28 一种信息推送方法及服务器、客户端、存储介质 WO2023185796A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210323009.0A CN114900510A (zh) 2022-03-29 2022-03-29 一种信息推送方法及服务器、客户端、存储介质
CN202210323009.0 2022-03-29

Publications (1)

Publication Number Publication Date
WO2023185796A1 true WO2023185796A1 (zh) 2023-10-05

Family

ID=82715637

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/084272 WO2023185796A1 (zh) 2022-03-29 2023-03-28 一种信息推送方法及服务器、客户端、存储介质

Country Status (2)

Country Link
CN (1) CN114900510A (zh)
WO (1) WO2023185796A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114900510A (zh) * 2022-03-29 2022-08-12 北京沃东天骏信息技术有限公司 一种信息推送方法及服务器、客户端、存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101473660B1 (ko) * 2013-10-14 2014-12-18 경북대학교 산학협력단 웹 기반 실시간 데이터 푸싱 방법 및 그 시스템
CN105450771A (zh) * 2015-12-16 2016-03-30 北京浩瀚深度信息技术股份有限公司 信息推送和信息推送优化方法、服务器及系统
CN106941536A (zh) * 2017-05-03 2017-07-11 华东交通大学 基于http协议的客户端与服务器之间的数据交互方法
CN110971703A (zh) * 2019-12-11 2020-04-07 腾讯科技（深圳）有限公司 基于连接池的服务请求方法、装置、服务器和存储介质
CN111092809A (zh) * 2019-12-30 2020-05-01 北京每日优鲜电子商务有限公司 实时推送信息的方法、装置、计算机设备及存储介质
CN114900510A (zh) * 2022-03-29 2022-08-12 北京沃东天骏信息技术有限公司 一种信息推送方法及服务器、客户端、存储介质

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020165907A1 (en) * 2001-04-13 2002-11-07 Matthew Dornquast System and method for real time interactive network communications
CN101599982B (zh) * 2008-06-06 2014-03-05 广东宇天科技有限公司 手机信息浏览装置、系统及实现方法
CN108390950A (zh) * 2018-05-28 2018-08-10 中国建设银行股份有限公司 一种消息推送方法、装置及设备
CN112600926A (zh) * 2020-12-16 2021-04-02 平安消费金融有限公司 一种消息推送方法、装置及计算机可读存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101473660B1 (ko) * 2013-10-14 2014-12-18 경북대학교 산학협력단 웹 기반 실시간 데이터 푸싱 방법 및 그 시스템
CN105450771A (zh) * 2015-12-16 2016-03-30 北京浩瀚深度信息技术股份有限公司 信息推送和信息推送优化方法、服务器及系统
CN106941536A (zh) * 2017-05-03 2017-07-11 华东交通大学 基于http协议的客户端与服务器之间的数据交互方法
CN110971703A (zh) * 2019-12-11 2020-04-07 腾讯科技（深圳）有限公司 基于连接池的服务请求方法、装置、服务器和存储介质
CN111092809A (zh) * 2019-12-30 2020-05-01 北京每日优鲜电子商务有限公司 实时推送信息的方法、装置、计算机设备及存储介质
CN114900510A (zh) * 2022-03-29 2022-08-12 北京沃东天骏信息技术有限公司 一种信息推送方法及服务器、客户端、存储介质

Also Published As

Publication number Publication date
CN114900510A (zh) 2022-08-12

Similar Documents

Publication Publication Date Title
CN108293058B (zh) 使用安全信令建立通信事件
EP3332534B1 (en) Scalable, real-time messaging system
US11025724B2 (en) Transport of control data in proxy-based network communications
US8200971B2 (en) Method for the provision of a network service
US11469896B2 (en) Method for securing the rendezvous connection in a cloud service using routing tokens
JP4575980B2 (ja) コンピュータシステムにおける通信のための方法、システム、及びコンピュータプログラム
EP3142306B1 (en) Openflow communication method, system, controller, and service gateway
US10250637B2 (en) System and method of pre-establishing SSL session connections for faster SSL connection establishment
US11632247B2 (en) User security token invalidation
CN108718347B (zh) 一种域名解析方法、系统、装置及存储介质
CN109413219B (zh) 一种域名解析方法和装置、服务器及存储介质
EP3633949A1 (en) Method and system for performing ssl handshake
WO2023185796A1 (zh) 一种信息推送方法及服务器、客户端、存储介质
US11323529B2 (en) TCP fast open hardware support in proxy devices
EP2521311A1 (en) Resource control method, apparatus and system in peer-to-peer network
US9390101B1 (en) Social deduplication using trust networks
US20240069977A1 (en) Data transmission method and data transmission server
EP2874376A1 (en) Method and system for information synchronization between cloud storage gateways, and cloud storage gateway
CN114338844B (zh) 一种客户端服务器之间的跨协议通信方法及装置
US20070226745A1 (en) Method and system for processing a service request
US20180198870A1 (en) Information processing apparatus, method for controlling the same, non-transitory computer-readable storage medium, and information processing system
WO2023151264A1 (zh) 负载均衡方法、装置、节点及存储介质
WO2006001137A1 (ja) データ通信システム、サーバ装置及びデータ通信方法並びにそのプログラム
CN111771366A (zh) 具有可协商和自适应的加密级别的用于加密数据流的方法
TWI416923B (zh) 網路服務中之安全資料通信

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23778161

Country of ref document: EP

Kind code of ref document: A1