CN113395293B - Network socket realizing method based on RPC - Google Patents
Network socket realizing method based on RPC Download PDFInfo
- Publication number
- CN113395293B CN113395293B CN202110791064.8A CN202110791064A CN113395293B CN 113395293 B CN113395293 B CN 113395293B CN 202110791064 A CN202110791064 A CN 202110791064A CN 113395293 B CN113395293 B CN 113395293B
- Authority
- CN
- China
- Prior art keywords
- network
- rpc
- interface
- control mcu
- main control
- 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
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/133—Protocols for remote procedure calls [RPC]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
- H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention provides a network socket realizing method based on RPC, which is used for solving the problem that a low-resource MCU can not support running a network protocol stack, but still wants to realize network connection by directly calling a network protocol stack interface and using a network socket interface. The method comprises a main control MCU and a network module, wherein the main control MCU does not need to run a network protocol stack, but a network application running on the main control MCU can still use a network socket interface in a mode of directly calling the network protocol stack interface; the network module runs the network protocol stack, executes the network socket function called by the main control MCU, and returns the interface execution result to the main control MCU. The network socket realizing method provided by the invention can reduce the difficulty of realizing the network socket function, reduce the resource occupation of the main control MCU end, and enable the main control MCU with low resources to simply and easily realize the network connection, data transmission and network management capability.
Description
Technical Field
The invention relates to the technical field of network communication, in particular to a network socket realizing method based on RPC.
Background
With the continuous development of the internet of things and the wide use of embedded devices, there are more and more small embedded devices that need to access a network. For embedded devices that need to access a TCP/IP network, the currently common ways are:
1. the TCP/IP network protocol stack, such as lwIP, runs locally. The transplanting and management difficulty of the mode is high, the technical requirements on the developer are also high, and if the transplanting process or the configuration is wrong, the protocol stack is likely to run unreliably. And a TCP/IP network protocol stack is directly operated on the local machine, which is not low in cost for embedded equipment with short resources.
2. By using an AT command mode, an AT network module is externally connected, a developer needs to learn a manual of the network module, the learning cost is increased, and meanwhile, AT network module manufacturers on the market are numerous and all have respective use characteristics, so that unified application codes are difficult to use.
Disclosure of Invention
Aiming at the defects of the prior art, the invention aims to provide a network socket realizing method based on RPC, which comprises a main control MCU and a network module.
The main control MCU does not need to run a network protocol stack, but the network application running on the main control MCU can still use a network socket interface in a mode of directly calling the network protocol stack interface; the network module runs the network protocol stack, executes the network socket function called by the main control MCU, and returns the interface execution result to the main control MCU.
Further, the RPC-based mode refers to remote procedure call, i.e. the network socket interface of the network module is called at the master MCU.
Further, the network application running on the master control MCU may use a network socket interface in the same manner as directly using a network protocol stack interface, including the following procedures:
encapsulating the functional ID, the interface input parameter and the RPC session identifier corresponding to the called socket interface into an RPC request packet at the main control MCU, and transmitting the RPC request packet to the network module;
the network module analyzes the received RPC request packet, calls a network socket operation interface of a corresponding network protocol stack according to the funcID, encapsulates an interface execution result, the funcID and the RPC session identifier into an RPC response packet after the execution is finished, and returns the RPC response packet to the main control MCU;
and the main control MCU receives the RPC response packet, analyzes the interface execution result of the network socket operation interface and returns the interface execution result to the upper network application.
The function ID represents a function ID table which is used by the master control MCU and the network module and uniquely corresponds to each network socket operation interface.
The RPC request packet contains a funcID, an RPC session mark and an interface input parameter.
The RPC response packet contains a funcID, an RPC session mark and an interface execution result.
The RPC session identifier is used for marking a pair of RPC request packets and RPC response packets, and ensuring that an interface execution result in the RPC response packets corresponds to the RPC request packets.
Further, a network protocol stack is operated at the network module and a network socket function called by the main control MCU is executed, namely, the network module analyzes the funcID and the interface input parameters after receiving an RPC request packet sent by the main control MCU, calls a network socket interface corresponding to the funcID of the network module and transmits the interface input parameters, and after execution is completed, the interface execution result and the funcID are packaged into an RPC response packet and returned to the main control MCU.
In order to achieve the above object, the present invention provides the following technical solutions:
the invention provides a method for realizing a network socket function, which comprises a main control MCU and a network module.
The master control MCU includes:
the interface abstract unit 11 is used for providing a network socket interface, packaging the funcID corresponding to the calling interface and the input parameters of the input interface into an RPC request packet, and analyzing the calling result returned by the network module;
RPC session management unit 12: the RPC request packet is used for marking the RPC session and correctly matching the RPC request packet and the RPC response packet;
command transceiver unit 13: the method comprises the steps of sending an RPC request packet and receiving an RPC response packet;
the network module includes:
network protocol stack 21: for performing specific network socket interface functions;
RPC request processing unit 22: the method comprises the steps of analyzing an RPC request packet, and returning an interface execution result called by a network socket interface to an MCU by using an RPC response packet;
command transmitting/receiving unit 23: the method comprises the steps of receiving an RPC request packet and sending an RPC response packet;
the specific steps of the above units for realizing the network socket are as follows:
A1. the network application of the main control MCU calls the network socket interface provided by the interface abstract unit 11, and the interface input parameters are transmitted into the interface abstract unit 11;
A2. the interface abstract unit 11 encapsulates the funcID corresponding to the calling interface and the input parameters of the input interface into an RPC request packet, and transmits the RPC request packet into the RPC session management unit 12;
A3. creating an RPC session in the RPC session management unit 12, adding an RPC session mark to the RPC request packet transmitted by the interface abstraction unit 11, and transmitting the RPC request packet to the command transceiver unit 13;
A4. the command transceiver unit 13 transmits the incoming RPC request packet to the network module through a hardware port connected to the network module;
A5. the command transceiver unit 23 of the network module transmits the received RPC request packet from the hardware port to the RPC request processing unit 22;
the RPC request processing unit 22 parses the incoming RPC request packet, parses out the funcID and the interface input parameter, invokes the network socket interface of the network protocol stack 21 corresponding to the funcID, and inputs the interface input parameter;
A7. the network socket interface of the network protocol stack 21 returns the interface execution result to the RPC request processing unit 22;
the RPC request processing unit 22 encapsulates the interface execution result returned by the network socket interface of the invoked network protocol stack 21 and the funcID into an RPC response packet, adds an RPC session flag of the RPC request packet to the RPC response packet, and transmits the RPC response packet to the command transceiving unit 23;
A9. the command transceiver unit 23 sends the incoming RPC response packet out through a hardware port connected with the main control MCU;
A10. the command transceiver unit 13 of the master control MCU receives the RPC response packet from the hardware port and transmits the RPC response packet to the RPC session management unit 12;
A11. the RPC session management unit 12 of the master MCU identifies the RPC session mark of the RPC response packet, and transmits the RPC response packet into the corresponding RPC request session;
A12. the interface abstract unit 11 of the main control MCU receives the RPC response packet to analyze and verify, and returns the analyzed interface execution result to the network application of the main control MCU.
The invention provides a network socket realizing method based on RPC, which has the beneficial effects that:
the embedded main control MCU does not need to run a network protocol stack, but the network application running on the main control MCU can still use a network socket interface in a mode of directly calling the network protocol stack interface, thereby providing a simple and convenient network access mode. Firstly, the embedded main control MCU does not need to transplant and operate a network protocol stack, thereby bringing great convenience to development work and reducing the occupation of hardware resources of the main control MCU. Secondly, the application of the upper network does not need to consider the using method and the characteristics of the network module too much, only the characteristics of the application service to be realized are concerned, the development and the transplanting of the application layer code are convenient, the workload in the development process is reduced, and the error probability and the later maintenance difficulty are reduced;
the network module referred to in the invention does not refer to a certain section or a certain series of network modules, and the invention can be adapted to different network devices, even tools at the PC end, as long as the network function can be realized and the device of the invention can be realized;
the invention supports the concurrent use of socket ports by multiple threads, and the increase of the application thread number of the main control MCU does not influence the number of processing threads of the network module;
the whole code amount and the resource occupation amount of the software realized by the method are smaller, the occupation of system resources is reduced, and the method is more friendly to embedded equipment with insufficient resources.
In order to make the above objects, features and advantages of the present invention more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
For a clearer description of the technical solutions of the present invention, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present disclosure, and therefore should not be considered as limiting the present invention, and the drawings related to the premise may be obtained according to the drawings without inventive effort for those skilled in the art.
Fig. 1 is a block diagram of a network socket implementation method based on RPC according to the present invention.
Fig. 2 is a schematic diagram of an internal structure of a master control MCU according to the present invention.
Fig. 3 is a schematic diagram of an internal structure of a network module according to the present invention.
Fig. 4 is a flowchart of a web socket interface calling process of the web socket implementation method provided by the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made more apparent, and the embodiments described are only some, but not all, of the embodiments of the present invention. The examples are provided to fully disclose the present invention and to fully convey the scope of the invention to those skilled in the art. Thus, the following detailed description of the embodiments of the invention, as presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. Based on the embodiments of the present invention, all of the obtained precondition embodiments by those of ordinary skill in the art without making creative efforts fall within the protection scope of the present invention.
With the continuous development of the internet of things and the wide use of embedded devices, there are more and more small embedded devices that need to access a network. The conventional TCP/IP network access mode cannot meet the requirements of convenient and quick transplanting and development, and has the defects of large study and maintenance cost and development efficiency reduction for different access modes.
Based on the above research, the invention provides a network socket realizing method based on RPC. As shown in fig. 1, the method includes the master MCU and the network module together implementing the RPC-based network socket function.
As shown in fig. 2, the master MCU further includes an interface abstraction unit 11, an RPC session management unit 12, and a command transceiver unit 13.
The interface abstract unit 11 is used for providing a network socket interface, packaging the funcID corresponding to the calling interface and the input parameters of the input interface into an RPC request packet, and analyzing the calling result returned by the network module;
RPC session management unit 12: the RPC request packet is used for marking the RPC session and correctly matching the RPC request packet and the RPC response packet;
command transceiver unit 13: for transmitting RPC request packets, receiving RPC response packets.
As shown in fig. 3, the network module further includes a network protocol stack 21, an RPC command processing unit 22, and a command transceiving unit 23.
Network protocol stack 21: for performing specific network socket interface functions;
RPC request processing unit 22: the method comprises the steps of analyzing an RPC request packet, and returning an interface execution result called by a network socket interface to an MCU by using an RPC response packet;
command transmitting/receiving unit 23: for receiving the RPC request packet and transmitting the RPC response packet.
As shown in fig. 4, a flowchart of a web socket interface calling process of the web socket implementation method provided by the invention is shown. The processes related to the master MCU in the processes are M1, M2, M3, M4, M5, M6, M7 and M8, and the processes related to the network module in the processes are N1, N2, N3, N4 and N5. The flow starts with M1.
In step M1, the network application of the master control MCU invokes the network socket interface provided by the interface abstraction unit 11, and transmits the interface input parameters to the interface abstraction unit 11;
in step M2, the interface abstract unit 11 encapsulates the funcID corresponding to the calling interface and the input parameters of the input interface into an RPC request packet, and transmits the RPC request packet to the RPC session management unit 12;
in step M3, an RPC session is created in the RPC session management unit, and the RPC request packet transmitted from the interface abstraction unit 11 is added with an RPC session flag, and transmitted to the command transceiver unit 13;
in step M4, the command transceiver unit 13 sends the incoming RPC request packet to the network module through a hardware port connected to the network module;
in step N1, the command transceiver unit 23 of the network module transfers the received RPC request packet from the hardware port to the RPC request processing unit 22;
in step N2, the RPC request processing unit 22 parses the incoming RPC request packet, parses out the funcdo and the interface input parameter, invokes the network socket interface of the network protocol stack 21 corresponding to the funcdo, and inputs the interface input parameter;
in step N3, the network protocol stack 21 will execute the network socket interface call, and the result is returned to the RPC request processing unit 22 after the execution is completed;
in step N4, the RPC request processing unit 22 encapsulates the interface execution result and the funcID returned by the network socket interface of the invoked network protocol stack 21 into an RPC response packet, adds an RPC session flag of the RPC request packet to the RPC response packet, and transmits the RPC response packet to the command transceiver unit 23;
in step N5, the command transceiver unit 23 sends the incoming RPC response packet out through a hardware port connected to the master MCU;
in step M5, the command transceiver unit 13 of the master MCU receives the RPC response packet from the hardware port and transmits it to the RPC session management unit 12;
in step M6, the RPC session management unit 12 of the master MCU recognizes the RPC session flag of the RPC response packet, and transmits the RPC response packet into the corresponding RPC request session;
in step M7, the interface abstraction unit 11 of the master MCU receives the RPC response packet to perform parsing verification, and returns the parsed interface execution result to the network application of the master MCU.
In step M8, the network application of the master control MCU receives the returned interface execution result, and the interface call flow ends.
In summary, the invention provides a network socket implementation method based on RPC. The embedded master control MCU does not need to run a network protocol stack, but the network application running on the master control MCU can still use a network socket interface in a mode of directly calling the network protocol stack interface, so that a simple and convenient network access mode is provided, and development and transplantation of application layer codes are convenient.
In the embodiments provided in the present invention, it should be understood that the disclosed method may be implemented in other manners as well. The above-described method embodiments are merely illustrative, for example, of the flowcharts and block diagrams in the figures that illustrate the architecture, functionality, and operation of possible implementations of methods and computer program products according to embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present invention may be integrated together to form a single part, or each module may exist alone, or two or more modules may be integrated to form a single part. The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, an electronic device, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, the terms "first," "second," and the like, are used merely to distinguish between descriptions and should not be construed as indicating or implying relative importance.
The above description is only of alternative embodiments of the present invention and is not intended to limit the present invention, and various modifications and variations will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (6)
1. A network socket realizing method based on RPC is characterized in that: the system comprises a main control MCU and a network module;
the main control MCU does not need to run a network protocol stack, but the network application running on the main control MCU can still use a network socket interface in a mode of directly calling the network protocol stack interface;
the network module runs a network protocol stack, executes a network socket function called by the main control MCU, and returns an interface execution result to the main control MCU;
the RPC-based mode refers to remote procedure call, namely, a network socket interface of a network module is called at a main control MCU;
the network application running on the master control MCU can use the network socket interface in the same way as the network protocol stack interface is directly used, and the method comprises the following steps:
encapsulating the functional ID, the interface input parameter and the RPC session identifier corresponding to the called socket interface into an RPC request packet at the main control MCU, and transmitting the RPC request packet to the network module;
the network module analyzes the received RPC request packet, calls a network socket operation interface of a corresponding network protocol stack according to the funcID, encapsulates an interface execution result, the funcID and the RPC session identifier into an RPC response packet after the execution is finished, and returns the RPC response packet to the main control MCU;
and the main control MCU receives the RPC response packet, analyzes the interface execution result of the network socket operation interface and returns the interface execution result to the upper network application.
2. The method for implementing an RPC-based network socket of claim 1, wherein: and the same set of funcID tables uniquely corresponding to the operation interfaces of all network sockets are used in the master control MCU and the network module.
3. The method for implementing an RPC-based network socket of claim 1, wherein: the RPC request packet contains a funcID, an RPC session mark and an interface input parameter.
4. The method for implementing an RPC-based network socket of claim 1, wherein: the RPC response packet contains a funcID, an RPC session mark and an interface execution result.
5. The method for implementing an RPC-based network socket of claim 1, wherein: the RPC session identifier is used for marking a pair of RPC request packets and RPC response packets, and ensuring that an interface execution result in the RPC response packets corresponds to the RPC request packets.
6. The method for implementing an RPC-based network socket of claim 1, wherein: and operating a network protocol stack at the network module and executing a network socket function called by the main control MCU, namely analyzing the funcID and the interface input parameters after the network module receives an RPC request packet sent by the main control MCU, calling a network socket interface corresponding to the funcID of the network module and transmitting the interface input parameters, and packaging an interface execution result and the funcID into an RPC response packet after the execution is finished and returning the RPC response packet to the main control MCU.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110791064.8A CN113395293B (en) | 2021-07-13 | 2021-07-13 | Network socket realizing method based on RPC |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110791064.8A CN113395293B (en) | 2021-07-13 | 2021-07-13 | Network socket realizing method based on RPC |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113395293A CN113395293A (en) | 2021-09-14 |
| CN113395293B true CN113395293B (en) | 2023-09-15 |
Family
ID=77626149
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110791064.8A Active CN113395293B (en) | 2021-07-13 | 2021-07-13 | Network socket realizing method based on RPC |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113395293B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101599991A (en) * | 2009-07-07 | 2009-12-09 | 浪潮电子信息产业股份有限公司 | A kind of method of the lifting network file system performance based on high-speed communication protocol |
| CN102223376A (en) * | 2011-06-23 | 2011-10-19 | 中国人民解放军国防科学技术大学 | Network protocol stack compatibility realizing method and device |
| CN103718518A (en) * | 2011-12-06 | 2014-04-09 | 华为技术有限公司 | Data transmission method, network device, and gateway |
| CN104639578A (en) * | 2013-11-08 | 2015-05-20 | 华为技术有限公司 | Multi-protocol-stack load balancing method and multi-protocol-stack load balancing device |
| CN106341266A (en) * | 2016-09-12 | 2017-01-18 | 武汉理工大学 | Hardware TCP/IP protocol stack possessing active and passive transmission modes |
| CN107147655A (en) * | 2017-05-25 | 2017-09-08 | 北京中电普华信息技术有限公司 | A kind of network dual stack parallel process model and its processing method |
| CN108028833A (en) * | 2015-12-30 | 2018-05-11 | 华为技术有限公司 | A kind of method, system and the relevant device of NAS data accesses |
| CN108616855A (en) * | 2018-04-02 | 2018-10-02 | 上海仪电数字技术股份有限公司 | Bluetooth equipment tele-control system and method |
| CN109189718A (en) * | 2018-09-04 | 2019-01-11 | 上海睿赛德电子科技有限公司 | A kind of SOCKET Component that supporting multiple network interface and method |
| CN112448924A (en) * | 2019-08-30 | 2021-03-05 | 北京东土科技股份有限公司 | Message processing method, system and switching equipment compatible with multiple protocols |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170034311A1 (en) * | 2015-07-30 | 2017-02-02 | Netapp, Inc. | Method for selecting between multiple RPC frameworks during a TCP/IP session |
-
2021
- 2021-07-13 CN CN202110791064.8A patent/CN113395293B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101599991A (en) * | 2009-07-07 | 2009-12-09 | 浪潮电子信息产业股份有限公司 | A kind of method of the lifting network file system performance based on high-speed communication protocol |
| CN102223376A (en) * | 2011-06-23 | 2011-10-19 | 中国人民解放军国防科学技术大学 | Network protocol stack compatibility realizing method and device |
| CN103718518A (en) * | 2011-12-06 | 2014-04-09 | 华为技术有限公司 | Data transmission method, network device, and gateway |
| CN104639578A (en) * | 2013-11-08 | 2015-05-20 | 华为技术有限公司 | Multi-protocol-stack load balancing method and multi-protocol-stack load balancing device |
| CN108028833A (en) * | 2015-12-30 | 2018-05-11 | 华为技术有限公司 | A kind of method, system and the relevant device of NAS data accesses |
| CN106341266A (en) * | 2016-09-12 | 2017-01-18 | 武汉理工大学 | Hardware TCP/IP protocol stack possessing active and passive transmission modes |
| CN107147655A (en) * | 2017-05-25 | 2017-09-08 | 北京中电普华信息技术有限公司 | A kind of network dual stack parallel process model and its processing method |
| CN108616855A (en) * | 2018-04-02 | 2018-10-02 | 上海仪电数字技术股份有限公司 | Bluetooth equipment tele-control system and method |
| CN109189718A (en) * | 2018-09-04 | 2019-01-11 | 上海睿赛德电子科技有限公司 | A kind of SOCKET Component that supporting multiple network interface and method |
| CN112448924A (en) * | 2019-08-30 | 2021-03-05 | 北京东土科技股份有限公司 | Message processing method, system and switching equipment compatible with multiple protocols |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113395293A (en) | 2021-09-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111245634B (en) | Virtualization management method and device | |
| WO2018176244A1 (en) | Data collection method, device, and dynamic environment network management system | |
| CN112688915A (en) | Cross-protocol communication method, device and server | |
| CN110166485B (en) | Protocol scheduling and using method and device | |
| CN101529807B (en) | A method and system for realizing universal interfaces in the network management system | |
| CN108810000B (en) | Method and device for generating serialization and deserialization API | |
| CN106559236B (en) | Equipment resource management method and device of service board, main control board and frame type equipment | |
| CN112698930B (en) | Method, device, equipment and medium for obtaining server identification | |
| CN113395293B (en) | Network socket realizing method based on RPC | |
| CN1780237A (en) | Logic topological network for protocol test and method for realizing protocol test | |
| CN107172013B (en) | Data transmission method and system | |
| CN110633162B (en) | Remote call implementation method and device, computer equipment and storage medium | |
| CN117596091A (en) | Method and system for scanning Profinet bus device by adopting DCP protocol | |
| CN101572624A (en) | Cross-platform cross-method SNMP extension MIB realization method | |
| WO2023071717A1 (en) | Operation and maintenance operation method and system, and network device | |
| CN105260179A (en) | Method for achieving flex and servlet interaction | |
| CN109274715A (en) | The platform resource management system of vehicle-mounted multi-channel communication systems | |
| CN112019491B (en) | Message processing method and system | |
| Ren et al. | Research on communication method of OPC UA client based on ARM | |
| CN109814871B (en) | Node management method and system based on DDS bus | |
| CN113448689A (en) | Dubbo protocol conversion device and method in operation period | |
| KR20010055482A (en) | Converting Method of Managing Operation from service management system to Switching Command in a Integrated Network | |
| CN103441947A (en) | Flow control method and device based on desktop virtualization | |
| CN118158079A (en) | Network analysis method based on optimization management | |
| CN117971760A (en) | Edge computing device framework systems, chips, storage media, and apparatus |
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 |