CN110636071B - Interface docking method - Google Patents
Interface docking method Download PDFInfo
- Publication number
- CN110636071B CN110636071B CN201910917935.9A CN201910917935A CN110636071B CN 110636071 B CN110636071 B CN 110636071B CN 201910917935 A CN201910917935 A CN 201910917935A CN 110636071 B CN110636071 B CN 110636071B
- Authority
- CN
- China
- Prior art keywords
- message
- code value
- processing
- request
- carrying
- 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
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/14—Routing performance; Theoretical aspects
-
- 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/08—Protocols for interworking; Protocol conversion
-
- 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/22—Parsing or analysis of headers
Abstract
The invention relates to an interface docking method, which comprises the following steps: step S1: receiving a request message sent by an access party, and carrying out standardized processing according to the protocol type of the request message; step S2: carrying out code value conversion and data verification on the message; step S3: carrying out general message conversion; step S4: and carrying out routing judgment. The invention carries out standardized processing on the message before carrying out routing judgment, reduces the requirements of message processing on software and hardware units, and ensures the diversity of processing types through dynamic processing files; the code value conversion is selectively carried out, so that the time and space requirements of message verification are reduced; and the applicable routing strategy is adopted for the synchronous and asynchronous messages, so that the routing efficiency is improved.
Description
[ technical field ] A method for producing a semiconductor device
The invention belongs to the technical field of communication, and particularly relates to an interface docking method.
[ background of the invention ]
Modern communication bandwidth is rapidly increased, and the corresponding communication product system is more and more complex to form: high speed interface and backplane bandwidth, high density port and system layout, high reliability. Along with the complexity increase of communication products, the fault types of the products are more and more, and the fault rate is also increased continuously. Existing data transmission modes can be classified into the following two types: one is a direct mode, and is relative to a remote service, that is, user plane data is directly transmitted between the UE and a remote service server without participation of a local service server; the other is a split mode, and with respect to the local service, that is, user plane data is transmitted only between the UE and the local service server, without the participation of the remote service server. TCP/IP is a common network transmission protocol, wherein ICMP is a connectionless-oriented protocol and is responsible for transmitting errors and control messages that may need attention, where the errors indicate whether there is an error in the communication network, such as that a destination host cannot reach, and an IP router cannot normally transmit a data packet. When a message needs to be processed by different transparent services through different service boards, different service boards need to be connected through respective physical network ports by using physical external lines to ensure that the message is transmitted between different service boards, and the message processing mode wastes physical network port resources of the service boards. In the face of the current situation that the network flow is increased sharply and the fault types are diversified, a new interface docking method is urgently needed. The invention carries out standardized processing on the message before carrying out routing judgment, reduces the requirements of message processing on software and hardware units, and ensures the diversity of processing types through dynamic processing files; the code value conversion is selectively carried out, so that the time and space requirements of message verification are reduced; and the applicable routing strategy is adopted for the synchronous and asynchronous messages, so that the routing efficiency is improved.
[ summary of the invention ]
In order to solve the above problems in the prior art, the present invention provides an interface docking method, including:
step S1: receiving a request message sent by an access party, and carrying out standardized processing according to the protocol type of the request message;
step S2: carrying out code value conversion and data verification on the message;
step S3: carrying out general message conversion;
step S4: and carrying out routing judgment.
Further, the code value conversion is performed on the message, and specifically: and uniformly mapping the code values in the message with the internal code values.
Further, determining whether code value conversion is needed or not according to the check bits of the message and/or the message type; for example: and converting the code value of the message of a specific type or passing the check bit.
Further, for the condition that code value conversion is not needed, data verification of the message is directly performed.
Further, the code value is converted into a code value compression mode, the code value is compressed into an internal code value, the unified mapping is a compression mapping, and the storage and verification cost of the message content after the compression is reduced.
Furthermore, only when the check of the message or check bit of a specific type passes, the check accuracy after compression mapping is not obviously reduced.
Further, whether code value conversion is needed is determined based on the security level of the message.
Further, the specific type is obtained by analyzing historical data; and when the verification accuracy rate is reduced within a preset range after unified mapping of a message type is found through historical data analysis, setting the message type as a specific type.
Further, the data verification of the packet specifically includes: and (4) carrying out message data verification, wherein the verification content comprises duplicate checking, format and message integrity and fraud identification verification.
Further, after the data check is passed, the fixed format message data binding is performed, that is, the checked message data is converted into a general message format according to the standard message specification and the data dictionary requirement.
The beneficial effects of the invention include: the message is subjected to standardized processing before the routing judgment, so that the requirements of message processing on software and hardware units are reduced, and the diversity of processing types is ensured through dynamic processing files; the code value conversion is selectively carried out, so that the time and space requirements of message verification are reduced; and the applicable routing strategy is adopted for the synchronous and asynchronous messages, so that the routing efficiency is improved.
[ description of the drawings ]
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, and are not to be considered limiting of the invention, in which:
fig. 1 is a schematic diagram of an interface docking method according to the present invention.
[ detailed description ] embodiments
The present invention will now be described in detail with reference to the drawings and specific embodiments, wherein the exemplary embodiments and descriptions are provided only for the purpose of illustrating the present invention and are not to be construed as limiting the present invention.
An interface docking method applied in the present invention is described in detail, as shown in fig. 1, the method includes:
step S1: receiving a request message sent by an access party, and carrying out standardized processing according to the protocol type of the request message;
preferably: based on the attributes of the access party, the receiving party and the request message, the standardization processing is specifically as follows: determining the processing mode based on the attributes of the access party, the receiving party and the request message, acquiring a processing file corresponding to the processing mode, and processing the request message based on the processing file; the standardized treatment refers to relative standard of treatment steps;
the request message attribute is protocol type, message sending time, and/or message identification;
the processing mode comprises processing items and an execution sequence thereof; wherein: the processing items comprise access, signature checking, decryption, unpacking, packaging, signature adding, encryption, access processing and the like; by standardizing the processing items, the processing items and the processing sequence can be increased or decreased according to the difference between the receiving party and the message, so that the adaptability of the processing process is stronger;
the determining the processing mode based on the attributes of the access party, the receiving party and the request message specifically comprises the following steps: determining a basic processing mode based on the request message attribute, and adjusting the basic processing mode based on the attributes of the access party and the receiving party to obtain the processing mode; the basic processing mode is a predetermined or common processing mode adopted by the request message attribute; can be obtained by accessing a comparison table and the like; the receiving party is used for processing the message and adjusting the execution sequence of the processing items related in the processing mode, so that the processing efficiency on the current receiving party is highest; operations such as simple replacement of processing items can also be performed, for example, if a special processing module of the pair of encryption B is provided on the current receiver, and the encryption a and the encryption B are actually equal in function, it can be considered that the encryption a is replaced by the processing item of the encryption B; at this time, the attribute of the access party can be introduced to judge whether the adjustment is allowed or not, and whether the adjustment is allowed or not can be determined according to the security requirement of the access party; in the prior art, a standardized processing mode and an adaptive adjustment message processing mode are not carried out;
the adjusting the basic processing mode based on the attributes of the access party and the receiving party to obtain the current processing mode specifically comprises the following steps: carrying out processing item replacement and/or execution sequence adjustment on the basic processing mode based on the receiver attribute, and determining whether the adjustment is allowed or not based on the accessor attribute; if an authentication mode is introduced for the adjustment, the complexity of the adjustment is greatly increased, and through the above mode, the adjustment is closely related to the software and hardware conditions, the pipelining and the disassociation conditions of the receiving party, and in addition, whether the adjustment is allowed or not is determined according to the attribute of the accessing party, if not, the original processing mode is adopted, and the processing efficiency is slightly low;
the acquiring of the processing file corresponding to the processing mode specifically includes: acquiring a code identifier corresponding to the processing mode, and inquiring a corresponding processing file based on the code identifier;
the acquiring of the code identifier corresponding to the processing mode specifically includes: acquiring project codes corresponding to processing projects in a processing mode, and sequencing the project codes through an execution sequence to obtain the code identifiers;
the querying of the corresponding processing file based on the code identifier specifically includes: storing the corresponding relation between the coding identification and the address of the processing file; inquiring the corresponding relation through the coding identification to obtain a processing file address, and obtaining a corresponding processing file based on the processing file address; the processing file is a batch processing file or a compiled binary file; preferably: the file addresses point to different storage spaces; the speed of directly executing the binary file is higher than the processing speed of the processed file, and the file in the binary form is obtained in advance and cached for the commonly used processed file, so that the processing efficiency can be greatly improved;
preferably: judging the use time and the use times of a processed file, if the use time and the use times meet the caching condition, compiling the batch processed file into an executable file in a binary coding form, storing the executable file into a caching space, and replacing a file address with a caching address so as to obtain the processed file as the executable file directly; the caching condition may be, for example, the number of times of use of processing a file in a fixed time period or the like;
step S2: carrying out code value conversion and data verification on the message;
the code value conversion is performed on the message, and specifically comprises the following steps: uniformly mapping the code value in the message with the internal code value;
preferably: determining whether code value conversion is needed or not according to the check bits of the message and/or the message type; for example: code value conversion is carried out on the message of a specific type or passing through the check bit;
preferably: for the condition that code value conversion is not needed, directly checking the data of the message;
the code value is converted into a code value to be compressed, the code value is compressed into an internal code value, the unified mapping is a compression mapping, and the storage and verification cost of the message content after compression is reduced; the calculation and storage expenses possibly generated by subsequent data verification are reduced through unified mapping; certainly, the check after the compression needs to be balanced, only when the check of a specific type of message or check bit passes, the check accuracy after the compression mapping is not obviously reduced, and the check accuracy after the check of the uniformly mapped internal code value is not obviously reduced;
preferably: determining whether code value conversion is needed or not based on the priority of the message, specifically: the message with high priority is not subjected to code value conversion, and the message with low priority is subjected to code value conversion;
preferably: determining whether code value conversion is needed or not based on the security level of the message, specifically: the message with high security level is not subjected to code value conversion, and the message with low security level is subjected to code value conversion;
preferably: the specific type is obtained by analyzing historical data; when the accuracy of verification is reduced within a preset range after unified mapping of a message type is found through historical data analysis, setting the message type as a specific type;
the data verification of the message specifically comprises the following steps: and (4) carrying out message data verification, wherein the verification content comprises duplicate checking, format and message integrity, fraud identification verification and the like.
Step S3: carrying out general message conversion; specifically, the method comprises the following steps: after the data check is passed, the fixed format message data binding is carried out, namely the checked message data is converted into a universal message format according to the standard message specification and the data dictionary requirement;
preferably: obtaining an original data message through reverse mapping;
preferably: if the message is subjected to unified mapping, the data needs to be reversely mapped to obtain an original data message; the reverse mapping is to store the original data message before the uniform mapping is carried out, and store the storage address into a reverse mapping table corresponding to the message identifier; after reverse mapping, acquiring the original data message by inquiring a reverse mapping table;
preferably: before conversion, judging whether the message format is a universal message format, and if the message format is the universal message format, skipping the conversion step;
preferably; before conversion, checking the message format, finding out the part which does not conform to the general message format, and converting the part; for the condition that the message formats are not uniform, only the difference part is converted, so that the conversion efficiency can be greatly improved; whether the message format check before conversion is needed or not can be determined by judging the attribute of the requesting party; the message format problem is often related to the access party;
preferably: determining whether general message conversion is needed or not based on the attribute of the requesting party, and skipping the conversion step for a specific accessing party;
step S4: carrying out routing judgment; specifically, the method comprises the following steps: routing judgment is carried out according to whether the message request is asynchronous or synchronous, if the message request is an asynchronous request message, a response request message is initiated to an external system, the message is routed to an internal system, after the internal system finishes the internal service processing of the system, the processing result is returned to the adapter in a general message format, and the adapter finishes signing encryption according to the requirement and then returns to the external request system, thus finishing the communication; otherwise, if the request is a synchronous request, the general message is directly routed to the target system, after the target system finishes the service processing, the form of the response message request is returned to the adapter, the adapter finishes signing encryption according to the requirement, and then the response message is returned to the external system, so that the communication is finished;
preferably: in the whole process of message communication, conversion and routing, recording an abnormal log in real time and supporting manual intervention abnormal transaction;
preferably: for the message with the error check, carrying out message error reporting or error confirmation; the message error reporting means that the error type and the error content which appear in the current processing are attached to the message and then subsequent routing is carried out; if the error type and the error content processed this time are consistent with the error type and the error content attached to the message, the error is confirmed; for the error confirmation type message, directly discarding the message, reporting the message error, or performing message error reverse routing, and reversely generating an error message identifier, an error type and error content thereof to an access party; the times of message error reporting and error reverse routing are reduced in an error confirmation mode, and the intentional false reporting caused by false reporting and software and hardware errors of a single node which may occur is reduced; the confirmation times in the error confirmation can be limited by the minimum times or/and the maximum times, and joint false alarm of 2 or more nodes is avoided;
the above description is only a preferred embodiment of the present invention, and all equivalent changes or modifications of the structure, characteristics and principles described in the present invention are included in the scope of the present invention.
Claims (4)
1. An interface interfacing method, the method comprising:
step S1: receiving a request message sent by an access party, and carrying out standardized processing according to the protocol type of the request message;
determining the processing mode based on the attributes of the access party, the receiving party and the request message, acquiring a processing file corresponding to the processing mode, and processing the request message based on the processing file;
the determining the processing mode based on the attributes of the access party, the receiving party and the request message specifically comprises the following steps: determining a basic processing mode based on the request message attribute, and adjusting the basic processing mode based on the attributes of the access party and the receiving party to obtain the processing mode;
the request message attribute comprises a protocol type;
step S2: carrying out code value conversion and data verification on the message;
determining whether code value conversion is needed or not according to the check bits of the message and/or the message type; code value conversion is carried out on the message passing the specific type or check bit check;
the code value conversion is performed on the message, and specifically comprises the following steps: uniformly mapping the code value in the message with the internal code value;
the code value is converted into a code value to be compressed, the code value is compressed into an internal code value, the unified mapping is a compression mapping, and the storage and verification cost of the message content after compression is reduced; step S3: carrying out general message conversion; specifically, the method comprises the following steps: after the data passes the verification, the fixed format message data is bound, and the verified message data is converted into a universal message format according to the standard message specification and the data dictionary requirement;
step S4: carrying out routing judgment; specifically, the method comprises the following steps: routing judgment is carried out according to whether the message request is asynchronous or synchronous, if the message request is an asynchronous request message, a response request message is initiated to an external system, the general message is routed to an internal system, after the internal system finishes the internal service processing of the system, the processing result is returned to the adapter in a general message format, and the adapter finishes signing encryption according to the requirement and then returns to the external request system, thus finishing the communication; otherwise, if the request is a synchronous request, the general message is directly routed to the target system, after the target system finishes the service processing, the response message is returned to the adapter, then the adapter finishes the signature encryption according to the requirement, and then the response message is returned to the external system, thus finishing the communication.
2. The interface docking method according to claim 1, wherein, in the case where code value conversion is not required, data verification of the packet is directly performed.
3. The interface docking method according to claim 1, wherein whether code value conversion is required is determined based on a security level of the packet.
4. The interface docking method according to claim 1, wherein the data verification of the packet specifically comprises: and (4) carrying out message data verification, wherein the verification content comprises duplicate checking, format and message integrity and fraud identification verification.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910917935.9A CN110636071B (en) | 2019-09-26 | 2019-09-26 | Interface docking method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910917935.9A CN110636071B (en) | 2019-09-26 | 2019-09-26 | Interface docking method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110636071A CN110636071A (en) | 2019-12-31 |
| CN110636071B true CN110636071B (en) | 2020-07-07 |
Family
ID=68973017
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910917935.9A Active CN110636071B (en) | 2019-09-26 | 2019-09-26 | Interface docking method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110636071B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102118293A (en) * | 2009-12-30 | 2011-07-06 | 上海可鲁系统软件有限公司 | Method for compressing and storing communication messages |
| KR20130082719A (en) * | 2011-12-15 | 2013-07-22 | 주식회사 코스콤 | Apparatus and method for financial data inquiry |
| CN109688148A (en) * | 2018-12-29 | 2019-04-26 | 苏州睿安芯微电子有限公司 | A kind of system and method for making retransmission protocol secure network by oneself based on software configuration |
| CN109802957A (en) * | 2019-01-03 | 2019-05-24 | 深圳壹账通智能科技有限公司 | Interface butt joint method, device, computer equipment and storage medium |
| CN109889553A (en) * | 2019-04-18 | 2019-06-14 | 中国电子科技集团公司第二十九研究所 | A kind of structuring message self-adaptive conversion method and device |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100389556C (en) * | 2004-03-05 | 2008-05-21 | 华为技术有限公司 | A method for implementing parsing of interface code stream |
| US9030771B2 (en) * | 2013-04-26 | 2015-05-12 | Oracle International Corporation | Compressed data verification |
| CN104468401B (en) * | 2014-11-20 | 2017-11-17 | 华为技术有限公司 | A kind of message processing method and device |
| CN105791178B (en) * | 2014-12-26 | 2019-02-15 | 阿里巴巴集团控股有限公司 | Message assemble method and device |
| CN105120002B (en) * | 2015-09-09 | 2019-01-25 | 中国银行股份有限公司 | A kind of information processing method and device |
| CN107483592A (en) * | 2017-08-22 | 2017-12-15 | 中国银行股份有限公司 | A kind of transaction processing method based on General Front End Processor and a kind of General Front End Processor |
-
2019
- 2019-09-26 CN CN201910917935.9A patent/CN110636071B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102118293A (en) * | 2009-12-30 | 2011-07-06 | 上海可鲁系统软件有限公司 | Method for compressing and storing communication messages |
| KR20130082719A (en) * | 2011-12-15 | 2013-07-22 | 주식회사 코스콤 | Apparatus and method for financial data inquiry |
| CN109688148A (en) * | 2018-12-29 | 2019-04-26 | 苏州睿安芯微电子有限公司 | A kind of system and method for making retransmission protocol secure network by oneself based on software configuration |
| CN109802957A (en) * | 2019-01-03 | 2019-05-24 | 深圳壹账通智能科技有限公司 | Interface butt joint method, device, computer equipment and storage medium |
| CN109889553A (en) * | 2019-04-18 | 2019-06-14 | 中国电子科技集团公司第二十九研究所 | A kind of structuring message self-adaptive conversion method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110636071A (en) | 2019-12-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3389219A1 (en) | Access request conversion method and device | |
| US7483384B2 (en) | System and method for monitoring network traffic | |
| US8316422B2 (en) | Propagation of principal authentication data in a mediated communication scenario | |
| US6591304B1 (en) | Dynamic, scaleable attribute filtering in a multi-protocol compatible network access environment | |
| CN108156240B (en) | Method and system for accessing industrial adapter to server | |
| CN111373702B (en) | Interface device for data exchange between a fieldbus network and a cloud | |
| US20060209830A1 (en) | Packet processing system including control device and packet forwarding device | |
| CN109167762B (en) | IEC104 message checking method and device | |
| CN110830442A (en) | Message processing method, device and gateway | |
| CN113301111A (en) | Digital twinning method, edge computing device, mobile terminal and storage medium | |
| US20200257602A1 (en) | High Order Layer Intrusion Detection Using Neural Networks | |
| CN114172929A (en) | Communication method, device and gateway | |
| CN105554042A (en) | Method and system for UDP tele-transmission log | |
| CN100586124C (en) | Securing communications equipment for processing data packets according to the send mechanism | |
| CN110636071B (en) | Interface docking method | |
| CN116707946A (en) | Electronic certificate mutual-trust mutual-authentication platform based on blockchain | |
| CN116383840A (en) | Device for providing security support and operating system supporting national security protocol | |
| CN104753774A (en) | Distributed enterprise integrated access gateway | |
| US20030204586A1 (en) | Intelligent data replicator | |
| CN115941809A (en) | Aggregation processing method and system for multiple Internet of Things terminal protocols for DCIM | |
| CN112769863B (en) | Method and device for processing service request message data, electronic equipment and readable storage medium | |
| CN113746807A (en) | Block chain node point support cryptographic algorithm communication detection method | |
| CN112953677A (en) | Method and device for adding link identification to request message data | |
| CN115152180A (en) | Improved packet transmission | |
| CN110830431A (en) | SQL Server database password hosting method |
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 |