CN108965392B - Method, system and equipment for receiving server push data - Google Patents
Method, system and equipment for receiving server push data Download PDFInfo
- Publication number
- CN108965392B CN108965392B CN201810623364.3A CN201810623364A CN108965392B CN 108965392 B CN108965392 B CN 108965392B CN 201810623364 A CN201810623364 A CN 201810623364A CN 108965392 B CN108965392 B CN 108965392B
- Authority
- CN
- China
- Prior art keywords
- receiving
- value
- push data
- trigger
- server
- 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.)
- Active
Links
Images
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/50—Network services
- H04L67/55—Push-based network services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Telephonic Communication Services (AREA)
Abstract
The embodiment of the invention provides a method, a system and equipment for receiving server push data, wherein the receiving method comprises the following steps: receiving the push data of the server through any receiving way of a plurality of receiving ways, wherein the push data of the receiving server of each receiving way is the same; and screening finally received push data from the push data of each receiving path receiving server. According to the method, the system and the equipment for receiving the server push data, the push data of the server are received through the multiple receiving ways, the data loss rate can be reduced, and the reliability of data acquisition can be ensured by screening the finally received push data from the push data of the server received through each receiving way.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a method, a system and equipment for receiving data pushed by a server.
Background
When receiving the data pushed by the server, the App can acquire the pushed data in multiple ways, in the prior art, the App acquires the pushed data only by using one receiving way, specifically, a long connection establishing way, a polling way, and the like.
In practical applications, the timed polling has a delay problem, and the way of establishing a long connection may cause data loss.
Disclosure of Invention
Aiming at the problems in the prior art, the embodiment of the invention provides a method, a system and equipment for receiving server push data.
The embodiment of the invention provides a method for receiving server push data, which comprises the following steps: receiving the push data of the server through any receiving way of a plurality of receiving ways, wherein the push data of the receiving server of each receiving way is the same; and screening finally received push data from the push data of each receiving path receiving server.
The embodiment of the invention provides a receiving system for server pushed data, which comprises: the receiving module is used for receiving the push data of the server through any receiving way in a plurality of receiving ways, wherein the push data of the receiving server of each receiving way is the same; and the screening module is used for screening the finally received push data from the push data of each receiving path receiving server.
The embodiment of the invention provides a receiving device for server push data, which comprises: at least one processor; and at least one memory communicatively coupled to the processor, wherein: the memory stores program instructions executable by the processor, and the processor calls the program instructions to execute the receiving method.
An embodiment of the present invention provides a non-transitory computer-readable storage medium, which stores computer instructions, and the computer instructions cause the computer to execute the above receiving method.
According to the method, the system and the equipment for receiving the server push data, the push data of the server are received through the multiple receiving ways, the data loss rate can be reduced, and the reliability of data acquisition can be ensured by screening the finally received push data from the push data of the server received through each receiving way.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
Fig. 1 is a flowchart of an embodiment of a method for receiving server push data according to the present invention;
FIG. 2 is a block diagram of an embodiment of a receiving system for server push data according to the present invention;
fig. 3 is a schematic diagram of a framework of a receiving device for pushing data by a server according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present 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.
Fig. 1 is a flowchart of an embodiment of a method for receiving server push data according to the present invention, as shown in fig. 1, including: s101, receiving the push data of the server through any one of a plurality of receiving ways, wherein the push data of the receiving server of each receiving way is the same; s102, screening the finally received push data from the push data of each receiving path receiving server.
Specifically, each receiving path receives the push data of the server once, and the time for receiving the push data of the server by each receiving path is the same or different.
Further, in step S102, the finally received push data is screened from the push data of each receiving path receiving server, where the finally received push data may be the receiving path that receives the push data first, the receiving path that receives the push data last, and the like.
According to the method for receiving the server push data, the push data of the server are received through the multiple receiving ways, the data loss rate can be reduced, and the reliability of data acquisition can be ensured by screening the finally received push data from the push data of the server received through each receiving way.
Based on the above embodiment, the receiving, by any of the multiple receiving paths, the pushed data of the server further includes: a plurality of reception paths are established with the server, the plurality of reception paths comprising a number of long connections and/or a number of polling services.
Specifically, the plurality of receiving paths include a plurality of long connections and/or a plurality of polling services, that is, the plurality of receiving paths include a plurality of long connections and do not include a polling service, or the plurality of receiving paths include a plurality of polling services and do not include a long connection, or the plurality of receiving paths include a plurality of long connections and include a plurality of polling services.
Further, several of the embodiments of the present invention include one or more. A long connection means that multiple packets can be sent continuously over one connection, and during the connection hold period, if no packet is sent, a link check packet needs to be sent in both directions. Long connections are often used for frequent, point-to-point communications, and the number of connections cannot be too great. Each TCP connection needs three-step handshake, which requires time, and if each operation is a short connection, the processing speed is reduced greatly if the operation is repeated, so that each operation is not disconnected after the operation is completed, and the data packet is OK when the next processing is performed, and the TCP connection does not need to be established. For example: the connection of the database uses a long connection, if the communication is frequent with a short connection, the socket error is caused, and the frequent socket creation is also a waste of resources.
Polling (Polling) is a way for a CPU to decide how to provide services to peripheral devices, and is also called Programmed I/O. The polling method is that CPU sends out inquiry in certain time to inquire each peripheral equipment whether it needs its service, if so, the peripheral equipment gives service, and after the service is over, the peripheral equipment asks the next peripheral equipment, and then the process is repeated.
The receiving method for the server pushed data provided by the embodiment of the invention can ensure the reliability of data acquisition by combining a plurality of receiving modes.
Based on the above embodiment, the screening out the finally received push data from the push data of each receiving path receiving server specifically includes: screening the push data received firstly under the time sequence from the push data of each receiving path receiving server; and taking the push data received first in the time sequence as the finally received push data.
Based on the above embodiment, the receiving the push data of the server through any of the multiple receiving paths specifically includes: and receiving the pushed data of the server through any one of a plurality of receiving ways based on the ServerListener class.
Based on the above embodiment, the screening out the push data received first in time sequence from the push data of each receiving path receiving server specifically includes: under the time sequence, each trigger state value of the push data of any receiving way receiving server is compared with the corresponding preset trigger state value; if each trigger state value of the push data of the receiving server of any receiving way is the same as the corresponding preset trigger state value, taking the push data of the receiving server of any receiving way as the push data received firstly under the time sequence; and if any trigger state value of the push data of the receiving server of any receiving way is different from the corresponding preset trigger state value, discarding the push data of the receiving server of any receiving way.
Based on the above embodiment, the trigger state value includes a trigger event value and a state trigger value; correspondingly, the preset trigger state value comprises a preset trigger event value and a preset state trigger value.
In particular, a state trigger value refers to a value that can trigger a presentation state.
Based on the above embodiment, in time sequence, each trigger state value of the push data of any receiving path receiving server is compared with a corresponding preset trigger state value; if each trigger state value of the push data of the receiving server of any receiving way is the same as the corresponding preset trigger state value, taking the push data of the receiving server of any receiving way as the push data received firstly under the time sequence; if any trigger state value of the push data of the receiving server of any receiving path is different from the corresponding preset trigger state value, discarding the push data of the receiving server of any receiving path, specifically comprising: under the time sequence, respectively corresponding a trigger event value and a state trigger value of the push data of any receiving way receiving server to the preset trigger event value and the preset state trigger value for comparison; if the trigger event value of the push data of the server received by any receiving way is the same as the preset trigger event value, and the state trigger value of the push data of the server received by any receiving way is the same as the preset state trigger value, taking the push data of the server received by any receiving way as the push data received first in the time sequence, and transferring the state trigger value of the push data received first in the time sequence to a preset switching state value; if the trigger event value of the push data of the receiving server of any receiving way is different from the preset trigger event value, and/or the state trigger value of the push data of the receiving server of any receiving way is different from the preset state trigger value, the push data of the receiving server of any receiving way is discarded.
As a preferred embodiment, the method for receiving server push data includes:
a plurality of receive paths are established with the server, the plurality of receive paths including a long connection a, a long connection B, and a polling service C.
And receiving the pushed data of the server through any one of a plurality of receiving ways based on the ServerListener class.
Under the time sequence, based on the StatemAchine class, respectively corresponding a trigger event value event and a state trigger value fromStates of push data of any receiving way receiving server to a preset event and comparing the preset event with the preset fromStates; if the event of receiving the pushed data of the server by any receiving way is the same as the preset event, and the fromStates of receiving the pushed data of the server by any receiving way are the same as the preset fromStates, taking the pushed data of the server received by any receiving way as the pushed data received firstly under the time sequence, and transferring the fromStates of the pushed data received firstly under the time sequence to the preset toState; if the event of the push data of the server received by any receiving way is different from the preset event and/or the fromStates of the push data of the server received by any receiving way are different from the preset fromStates, the push data of the server received by any receiving way is discarded.
Table 1 shows the methods in the StateMachine class and their description.
TABLE 1 Statemmachine class methods and description tables
Referring to table 1, as a specific example, the default status of the StateMachine class is 0, the registered event is 1, the fromStates is 0, and the toState is 1, that is, only when the fromStates is 0, the statemay be migrated to the data state 1, and when the fromStates of the same push data that is subsequently pushed is 1, the data may be discarded.
Based on the above embodiments, fig. 2 is a block diagram of an embodiment of a receiving system for server push data according to the present invention, including: a receiving module 201, configured to receive the push data of the server through any receiving path of multiple receiving paths, where the push data of the receiving servers of each receiving path are the same; and a screening module 202, configured to screen finally received push data from the push data of each receiving route receiving server.
The detection system of the embodiment of the present invention may be used to implement the technical solution of the embodiment of the receiving method for server push data shown in fig. 1, and the implementation principle and the technical effect are similar, which are not described herein again.
Based on the foregoing embodiments, fig. 3 is a schematic diagram of a framework of a receiving device for pushing data by a server in an embodiment of the present invention. Referring to fig. 3, an embodiment of the present invention provides a receiving device for server push data, including: a processor (processor)310, a communication Interface (communication Interface)320, a memory (memory)330 and a bus 340, wherein the processor 310, the communication Interface 320 and the memory 330 complete communication with each other through the bus 340. The processor 310 may call logic instructions in the memory 330 to perform methods comprising: receiving the push data of the server through any receiving way of a plurality of receiving ways, wherein the push data of the receiving server of each receiving way is the same; and screening finally received push data from the push data of each receiving path receiving server.
An embodiment of the present invention discloses a computer program product, which includes a computer program stored on a non-transitory computer readable storage medium, the computer program includes program instructions, and when the program instructions are executed by a computer, the computer can execute the receiving method provided by the above-mentioned method embodiments, for example, the computer includes: receiving the push data of the server through any receiving way of a plurality of receiving ways, wherein the push data of the receiving server of each receiving way is the same; and screening finally received push data from the push data of each receiving path receiving server.
Based on the foregoing embodiments, an embodiment of the present invention provides a non-transitory computer-readable storage medium, where the non-transitory computer-readable storage medium stores computer instructions, where the computer instructions cause the computer to execute the receiving method provided by each method embodiment described above, for example, the method includes: receiving the push data of the server through any receiving way of a plurality of receiving ways, wherein the push data of the receiving server of each receiving way is the same; and screening finally received push data from the push data of each receiving path receiving server.
Those of ordinary skill in the art will understand that: the implementation of the above-described apparatus embodiments or method embodiments is merely illustrative, wherein the processor and the memory may or may not be physically separate components, i.e. may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as a usb disk, a removable hard disk, a ROM/RAM, a magnetic disk, an optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute the method according to the embodiments or some parts of the embodiments.
According to the method, the system and the equipment for receiving the server push data, the push data of the server are received through the plurality of receiving ways, the data loss rate can be reduced, and the reliability of data acquisition can be ensured by screening the finally received push data from the push data of the server received through each receiving way. Through setting and fusing multiple receiving modes, the reliability of data acquisition can be ensured.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (6)
1. A method for receiving server push data is characterized by comprising the following steps:
receiving the push data of the server through any receiving way of a plurality of receiving ways, wherein the push data of the receiving server of each receiving way is the same;
screening the finally received push data from the push data of each receiving path receiving server, specifically comprising:
screening the push data received firstly under the time sequence from the push data of each receiving path receiving server;
taking the push data received first in the time sequence as the finally received push data;
under the time sequence, each trigger state value of the push data of any receiving way receiving server is compared with the corresponding preset trigger state value; the trigger state value comprises a trigger event value event and a state trigger value fromStates; correspondingly, the preset trigger state value comprises a preset trigger event value event and a preset state trigger value fromStates; the value of event is 0 or 1; fromStates have a value of 0 or 1; the value of the preset event is 0 or 1; presetting the value of fromStates as 0 or 1; the trigger event value event refers to a value when an event is triggered at the current moment, the state trigger value fromStates is a value when the display state is triggered at the current moment, and the preset trigger event value event and the preset state trigger value fromStates represent a preset default trigger event value and a preset state trigger value;
if each trigger state value of the push data of the receiving server of any receiving way is the same as the corresponding preset trigger state value, taking the push data of the receiving server of any receiving way as the push data received firstly under the time sequence; if any trigger state value of the push data of the receiving server of any receiving path is different from the corresponding preset trigger state value, discarding the push data of the receiving server of any receiving path, specifically comprising:
under the time sequence, a trigger event value event and a state trigger value fromStates of push data of any receiving way receiving server are respectively corresponding to the preset trigger event value event and the preset state trigger value fromStates to be compared;
if the trigger event value event of the push data of the server received by any receiving way is the same as the preset trigger event value event, and the state trigger value fromStates of the push data of the server received by any receiving way is the same as the preset state trigger value fromStates, taking the push data of the server received by any receiving way as the push data received firstly under the time sequence, and transferring the state trigger value fromStates of the push data received firstly under the time sequence to a preset switching state value toState; presetting the value of toState as 0 or 1; the preset switching state value toState is a state value for triggering successful switching;
if the trigger event value event of the push data of the receiving server of any receiving way is different from the preset trigger event value event and/or the state trigger value fromStates of the push data of the receiving server of any receiving way is different from the preset state trigger value fromStates, the push data of the receiving server of any receiving way is discarded.
2. The receiving method according to claim 1, wherein the receiving push data of the server through any receiving path of the plurality of receiving paths further comprises:
a plurality of reception paths are established with the server, the plurality of reception paths comprising a number of long connections and/or a number of polling services.
3. The receiving method according to claim 1, wherein the receiving push data of the server through any of the plurality of receiving paths specifically includes:
and receiving the pushed data of the server through any one of a plurality of receiving ways based on the ServerListener class.
4. A receiving system for pushing data by a server, comprising:
the receiving module is used for receiving the push data of the server through any receiving way in a plurality of receiving ways, wherein the push data of the receiving server of each receiving way is the same;
the screening module is configured to screen finally received push data from the push data of each receiving path receiving server, and specifically includes:
screening the push data received firstly under the time sequence from the push data of each receiving path receiving server;
taking the push data received first in the time sequence as the finally received push data;
under the time sequence, each trigger state value of the push data of any receiving way receiving server is compared with the corresponding preset trigger state value; the trigger state value comprises a trigger event value event and a state trigger value fromStates; correspondingly, the preset trigger state value comprises a preset trigger event value event and a preset state trigger value fromStates; the value of event is 0 or 1; fromStates have a value of 0 or 1; the value of the preset event is 0 or 1; presetting the value of fromStates as 0 or 1; the trigger event value event refers to a value when an event is triggered at the current moment, the state trigger value fromStates is a value when the display state is triggered at the current moment, and the preset trigger event value event and the preset state trigger value fromStates represent a preset default trigger event value and a preset state trigger value;
if each trigger state value of the push data of the receiving server of any receiving way is the same as the corresponding preset trigger state value, taking the push data of the receiving server of any receiving way as the push data received firstly under the time sequence; if any trigger state value of the push data of the receiving server of any receiving path is different from the corresponding preset trigger state value, discarding the push data of the receiving server of any receiving path, specifically comprising:
under the time sequence, a trigger event value event and a state trigger value fromStates of push data of any receiving way receiving server are respectively corresponding to the preset trigger event value event and the preset state trigger value fromStates to be compared;
if the trigger event value event of the push data of the server received by any receiving way is the same as the preset trigger event value event, and the state trigger value fromStates of the push data of the server received by any receiving way is the same as the preset state trigger value fromStates, taking the push data of the server received by any receiving way as the push data received firstly under the time sequence, and transferring the state trigger value fromStates of the push data received firstly under the time sequence to a preset switching state value toState; presetting the value of toState as 0 or 1; the preset switching state value toState is a state value for triggering successful switching;
if the trigger event value event of the push data of the receiving server of any receiving way is different from the preset trigger event value event and/or the state trigger value fromStates of the push data of the receiving server of any receiving way is different from the preset state trigger value fromStates, the push data of the receiving server of any receiving way is discarded.
5. A receiving device for pushing data by a server, comprising:
at least one processor; and
at least one memory communicatively coupled to the processor, wherein:
the memory stores program instructions executable by the processor, the processor being capable of executing the receiving method as claimed in any one of claims 1 to 3 when invoked by the program instructions.
6. A non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the receiving method according to any one of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810623364.3A CN108965392B (en) | 2018-06-15 | 2018-06-15 | Method, system and equipment for receiving server push data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810623364.3A CN108965392B (en) | 2018-06-15 | 2018-06-15 | Method, system and equipment for receiving server push data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108965392A CN108965392A (en) | 2018-12-07 |
| CN108965392B true CN108965392B (en) | 2021-07-27 |
Family
ID=64489239
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810623364.3A Active CN108965392B (en) | 2018-06-15 | 2018-06-15 | Method, system and equipment for receiving server push data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108965392B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102118434A (en) * | 2010-12-28 | 2011-07-06 | 华为技术有限公司 | Data packet transmission method and device |
| KR101052769B1 (en) * | 2009-12-31 | 2011-08-01 | 한국과학기술원 | Reusable electronic note paper and data processing system including the same |
| CN103716835A (en) * | 2012-09-29 | 2014-04-09 | 国际商业机器公司 | Methods, devices and systems for transmitting and receiving data based on multiple paths |
| CN105450367A (en) * | 2014-09-01 | 2016-03-30 | 电信科学技术研究院 | Method and apparatus for data transmission |
| CN107124440A (en) * | 2016-12-01 | 2017-09-01 | 北京小度信息科技有限公司 | Information push method, message push server, client and system |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7464017B2 (en) * | 2005-01-14 | 2008-12-09 | International Business Machines Corporation | Time multiplexed interface for emulator system |
| CN103825864B (en) * | 2012-11-16 | 2019-02-05 | 腾讯科技（深圳）有限公司 | The method and user equipment of data acquisition and transmission |
| CN105517028B (en) * | 2014-10-17 | 2020-03-24 | 电信科学技术研究院 | Method and equipment for triggering and configuring transmission path |
| CN106254238B (en) * | 2016-09-29 | 2018-12-28 | 胡汉强 | A kind of data transmission method, Centralized Controller and communication device |
-
2018
- 2018-06-15 CN CN201810623364.3A patent/CN108965392B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR101052769B1 (en) * | 2009-12-31 | 2011-08-01 | 한국과학기술원 | Reusable electronic note paper and data processing system including the same |
| CN102118434A (en) * | 2010-12-28 | 2011-07-06 | 华为技术有限公司 | Data packet transmission method and device |
| CN103716835A (en) * | 2012-09-29 | 2014-04-09 | 国际商业机器公司 | Methods, devices and systems for transmitting and receiving data based on multiple paths |
| CN105450367A (en) * | 2014-09-01 | 2016-03-30 | 电信科学技术研究院 | Method and apparatus for data transmission |
| CN107124440A (en) * | 2016-12-01 | 2017-09-01 | 北京小度信息科技有限公司 | Information push method, message push server, client and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108965392A (en) | 2018-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109547511B (en) | WEB message real-time pushing method, server, client and system | |
| US9462053B2 (en) | Method and apparatus for connection establishment | |
| US20160330569A1 (en) | Service Processing Method and Network Device | |
| CN109802995B (en) | Message pushing method, device, equipment and storage medium | |
| WO2017185615A1 (en) | Method for determining service status of service processing device and scheduling device | |
| CN113824723A (en) | End-to-end system solution applied to audio and video data transmission | |
| CN107766149B (en) | Method and device for ZooKeeper cluster configuration based on DUBBO | |
| CN113595927A (en) | Method and device for processing mirror flow in bypass mode | |
| US20150067066A1 (en) | Provisioning Communication Services using Proxy Server in a Cloud | |
| CN111935017A (en) | Cross-network application calling method and device and routing equipment | |
| US10412778B2 (en) | Data transmission method and apparatus for data service | |
| CN108965392B (en) | Method, system and equipment for receiving server push data | |
| CN107423446B (en) | New media automation trusted deployment system and method based on cloud storage | |
| CN108289165B (en) | Method and device for realizing camera control based on mobile phone and terminal equipment | |
| CN112968951B (en) | Service node connection method and device, storage medium and electronic device | |
| CN111200578A (en) | Communication method, client device and server device | |
| EP4044535A1 (en) | Method for acquiring common maximum segment size (mss), and device | |
| CN109413037B (en) | Modbus service processing method and device | |
| US10986190B2 (en) | Information processing device and method for updating a session timer | |
| CN113596325A (en) | Picture capturing method and device, electronic equipment and storage medium | |
| WO2016101223A1 (en) | Method and apparatus for snmp set operations | |
| CN105939317A (en) | Parsing method and parsing device for SSL handshake message | |
| CN108737208B (en) | Connection synchronization method and device based on secure gateway deep packet detection and computer | |
| CN110557728A (en) | short message sending method, device and network equipment | |
| EP2699028A2 (en) | Method and apparatus for sending messages |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |