CN113760582A - Document declaration method and device - Google Patents

Document declaration method and device Download PDF

Info

Publication number
CN113760582A
CN113760582A CN202111056821.3A CN202111056821A CN113760582A CN 113760582 A CN113760582 A CN 113760582A CN 202111056821 A CN202111056821 A CN 202111056821A CN 113760582 A CN113760582 A CN 113760582A
Authority
CN
China
Prior art keywords
declaration
message
interface
document
template
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.)
Granted
Application number
CN202111056821.3A
Other languages
Chinese (zh)
Other versions
CN113760582B (en
Inventor
徐晓光
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Jingdong Zhenshi Information Technology Co Ltd
Original Assignee
Beijing Jingdong Zhenshi Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Jingdong Zhenshi Information Technology Co Ltd filed Critical Beijing Jingdong Zhenshi Information Technology Co Ltd
Priority to CN202111056821.3A priority Critical patent/CN113760582B/en
Publication of CN113760582A publication Critical patent/CN113760582A/en
Application granted granted Critical
Publication of CN113760582B publication Critical patent/CN113760582B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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/541—Interprogram communication via adapters, e.g. between incompatible applications
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/166—Editing, e.g. inserting or deleting
    • G06F40/186—Templates
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12—Accounting
    • G06Q40/123—Tax preparation or submission
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • 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/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/541—Client-server
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/549—Remote execution

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • General Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Artificial Intelligence (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Computational Linguistics (AREA)
  • General Health & Medical Sciences (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The application discloses a document declaration method and a document declaration device, relates to the technical field of computers, and particularly relates to a method for realizing document declaration by using a document declaration server; calling a routing configuration file, and analyzing a demand identifier to determine declaration information; calling a receiving template interface to generate a corresponding declaration interface message according to the declaration information; and sending a declaration interface message to a preset approval node to obtain an approval result and forwarding the approval result. Therefore, when different new declaration interfaces are docked and different declaration types are responded, repeated declaration processes are not needed, document declaration can be easily realized by calling the receipt template interface, logic of interaction with customs is isolated, and user document declaration experience is improved.

Description

Document declaration method and device
Technical Field
The application relates to the technical field of computers, in particular to a document declaration method and device.
Background
At present, message creation and reporting mashup of various reporting documents are mixed together, a reporting flow can be repeated once again when a new reporting interface is connected, codes are more and more bloated, the logic of a certain reporting interface is modified to influence the reporting of other reporting interfaces, and continuous online optimization and improvement are required along with more and more bonded areas and more frequent connection work.
In the process of implementing the present application, the inventor finds that at least the following problems exist in the prior art:
when different new declaration interfaces are docked and different declaration types are responded, repeated declaration processes are needed for many times, and the problem that codes are more and more bloated is caused.
Disclosure of Invention
In view of this, embodiments of the present application provide a document declaration method and apparatus, which can solve the problem that codes are increasingly bloated due to repeated declaration processes when different new declaration interfaces are docked and different declaration types are handled in the prior art.
To achieve the above object, according to an aspect of an embodiment of the present application, there is provided a document declaration method, including:
acquiring a report document message and further acquiring a demand identifier in the report document message;
calling a routing configuration file, and analyzing a demand identifier to determine declaration information;
calling a receiving template interface to generate a corresponding declaration interface message according to the declaration information;
and sending a declaration interface message to a preset approval node to obtain an approval result and forwarding the approval result.
Optionally, determining the declaration information includes:
and matching the requirement identification with each identification in the routing configuration file to determine a declaration interface, a message type and a declaration mode corresponding to the requirement identification.
Optionally, before invoking the order receiving template interface, the document declaration method further includes:
acquiring various types of declaration data;
generating serial number identifications corresponding to various types of declaration data;
generating each message template according to the declaration data and the corresponding serial number identification;
and packaging each message template to obtain a single template interface.
Optionally, generating a corresponding declaration interface message includes:
and calling a corresponding message template in the receipt template interface according to the message type so as to generate a corresponding declaration interface message according to the declaration interface and the declaration document message.
Optionally, generating a corresponding declaration interface message according to the declaration interface and the declaration document message includes:
and acquiring parameters required by the corresponding message template from the declaration form message, and splicing the messages according to the parameters and the declaration interface to generate the corresponding declaration interface message.
Optionally, the document declaration method further includes:
and under the condition that the declaration interface message fails to be sent, generating a corresponding declaration interface message sending task and carrying out asynchronous retransmission.
In addition, the present application further provides a document declaration apparatus, including:
the acquiring unit is configured to acquire the declaration document message and further acquire a requirement identifier in the declaration document message;
the analysis unit is configured to call the routing configuration file and analyze the requirement identification to determine declaration information;
the message generating unit is configured to call the order receiving template interface to generate a corresponding declaration interface message according to the declaration information;
and the sending unit is configured to send the declaration interface message to a preset approval node so as to obtain an approval result and forward the approval result.
Optionally, the parsing unit is further configured to:
and matching the requirement identification with each identification in the routing configuration file to determine a declaration interface, a message type and a declaration mode corresponding to the requirement identification.
Optionally, the document declaration apparatus further comprises an encapsulation unit configured to:
acquiring various types of declaration data;
generating serial number identifications corresponding to various types of declaration data;
generating each message template according to the declaration data and the corresponding serial number identification;
and packaging each message template to obtain a single template interface.
Optionally, the message generating unit is further configured to:
and calling a corresponding message template in the receipt template interface according to the message type so as to generate a corresponding declaration interface message according to the declaration interface and the declaration document message.
Optionally, the message generating unit is further configured to:
and acquiring parameters required by the corresponding message template from the declaration form message, and splicing the messages according to the parameters and the declaration interface to generate the corresponding declaration interface message.
Optionally, the document declaration apparatus further comprises an asynchronous retransmission unit configured to:
and under the condition that the declaration interface message fails to be sent, generating a corresponding declaration interface message sending task and carrying out asynchronous retransmission.
In addition, the present application also provides a document declaration electronic device, comprising: one or more processors; storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to carry out a document declaration method as described above.
Additionally, the present application provides a computer readable medium having stored thereon a computer program which, when executed by a processor, implements a document declaration method as described above.
One embodiment of the above invention has the following advantages or benefits: according to the method, the requirement identification in the declaration form message is further acquired by acquiring the declaration form message; calling a routing configuration file, and analyzing a demand identifier to determine declaration information; calling a receiving template interface to generate a corresponding declaration interface message according to the declaration information; and sending a declaration interface message to a preset approval node to obtain an approval result and forwarding the approval result. Therefore, the workload of development, maintenance, on-line and the like of developers is reduced through simple and efficient configuration, and the system development and maintenance cost is reduced. When different new declaration interfaces are butted and different declaration types are responded, the document declaration can be easily realized by calling the receipt template interface without repeating the declaration flow for many times, so that a user does not need to care about a declaration system, the logic of interaction with customs is isolated, the functional isolation is realized, the problem that codes are more and more bloated is solved, and the document declaration experience of the user is improved.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a further understanding of the application and are not to be construed as limiting the application. Wherein:
FIG. 1 is a schematic illustration of the main flow of a document declaration method according to a first embodiment of the present application;
FIG. 2 is a schematic illustration of the main flow of a document declaration method according to a second embodiment of the present application;
FIG. 3 is a schematic diagram of an application scenario of a document declaration method according to a third embodiment of the present application;
FIG. 4 is a schematic diagram of the primary elements of a document declaration apparatus according to an embodiment of the present application;
FIG. 5 is an exemplary system architecture diagram to which embodiments of the present application may be applied;
fig. 6 is a schematic structural diagram of a computer system suitable for implementing the terminal device or the server according to the embodiment of the present application.
Detailed Description
The following description of the exemplary embodiments of the present application, taken in conjunction with the accompanying drawings, includes various details of the embodiments of the application for the understanding of the same, which are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a schematic diagram of a main flow of a sheet declaration method according to a first embodiment of the present application, and as shown in fig. 1, the sheet declaration method includes:
step S101, acquiring a report document message, and further acquiring a demand identifier in the report document message.
In this embodiment, an executing body (for example, a server) of the order document declaration method may obtain declaration document data input by a user from a terminal device in a wired connection or wireless connection manner, and further generate a declaration document message according to the declaration order document data. A message (message) is a data unit exchanged and transmitted in the network, i.e. a data block to be sent by a station at one time. The message contains complete data information to be sent, and the length of the message is not consistent, and is not limited and variable. The generated order document message may include a requirement identifier, and the requirement identifier may be formed by splicing various types of identifiers. After the execution main body obtains the report order document message, the execution main body can obtain the demand identification in the report order document message. For example, the requirement identifier may be a-01-HTTPS, where a represents an declaration interface, 01 represents a message type (e.g., 01 corresponds to an order document message), and HTTPS represents a declaration mode. The declaration interface may be, for example, a declaration port.
In this embodiment, the documents may include orders, shipping orders, bills, payment orders, and the like. The document is not limited in the present application.
For example, the order, the enterprise procurement department, issues the order certification (including all procurement processes of finished products, raw materials, fuel, parts, office supplies, services, etc.) to the supplier. Since order types may specify processing rules and order entry defaults, the system may require order types when entering orders and returns. You can assign an order period to each order type to control order processing and provide a default value for this order type.
The manifest is a "one-time" written contract between the carrier and shipper for the matter of freight transportation. Is the contract certificate of the goods transportation and transportation agency, and is also the certificate for the transportation operator to accept the goods and take care of keeping and delivering the goods according to the transportation period. The name of the consignment, the packaging, various fees and amounts, the port of origin and arrival, the shipper and receiver, the carrier and arrival date, and other items related to the shipment of the goods are listed. When the shipper consigns goods, the shipper must fill in the freight bill according to the regulations, the remark column of the freight bill which has special transportation requirements signs, and the transportation contract is proved to be established after the consignor or the shipper signs. In the whole transportation process, the freight bill is the basic basis for carrying out various transportation operations and handling related matters (such as freight accidents, freight charge and the like). Freight bills are divided into three types, namely A, B and C: the A-type freight bill is suitable for common freight transportation, large cargo transportation, dangerous cargo transportation and transportation agent business; the B kind freight bill is suitable for container transportation; the C kind freight bill is suitable for transportation of the piece goods. However, the waybill does not have the function of a rights voucher and is a non-transferable rights voucher.
The list refers to a sheet in which related items are registered in detail. And the payment order is mainly used for checking the payment condition of the order and managing the number, payment amount and payment state of the payment order.
The payment order is generated in two ways: and the third party payment platform returns data to automatically generate a payment order and manually add the payment order. Manual addition of payment orders is primarily used for offline payments, such as transfers, remittances, etc., where no third party payment return is available.
And step S102, calling a routing configuration file, and analyzing the requirement identification to determine declaration information.
In this embodiment, after acquiring the requirement identifier, the execution main body may call the routing configuration file to analyze the requirement identifier and determine the declaration information. The routing configuration file may be a routing configuration table, that is, a table of mapping relationships between the stored declaration interfaces, packet types, declaration manners, and respective corresponding identifiers (the identifiers may also be referred to as numbers). The declaration information may be a specific declaration interface, a message type, and a declaration mode corresponding to the determined requirement identifier based on a mapping relationship in the routing configuration file. Namely, the determination of the declaration information includes: and matching the requirement identification with each identification in the routing configuration file one by one to determine a declaration interface, a message type and a declaration mode corresponding to the requirement identification. That is, the routing configuration file may include a declaration interface, a packet type, a declaration manner, and respective corresponding identifiers and mapping relationships of the declaration interface, the packet type, and the declaration manner. For example, the declaration interface, the packet type, the declaration mode, and the corresponding identifier in the routing configuration file may be represented as follows: the method comprises the following steps that A declares an interface-A (indicating that the identifier corresponding to the A declares the interface is A), B declares an interface-B, a document message-01, a waybill message-02 and a payment sheet message-03, declares-https in an https mode, declares-ftp in an ftp mode, and declares-web service in a web service mode (indicating that the identifier corresponding to the A declares the interface is web service). Of course, the identifier corresponding to the declaration interface, the message type, and the declaration mode in the routing configuration file may also be represented by other suitable numbers or characters, which is not specifically limited in this application. The declaration interface may be, for example, a declaration port.
And step S103, calling a receipt template interface to generate a corresponding declaration interface message according to the declaration information.
In this embodiment, the order template interface may be obtained by encapsulating data from various sources. The execution body can call the order receiving template interface to generate a corresponding declaration interface message according to a format specified by a declaration interface in the declaration information. I.e. may be to generate a corresponding declaration port message.
In some optional implementations of this embodiment, before invoking the order taking template interface, the document declaration method further includes: acquiring various types of declaration data; generating serial number identifications corresponding to various types of declaration data; generating each message template according to the declaration data and the corresponding serial number identification; and packaging each message template to obtain a single template interface. In this embodiment, each type of declaration data may be information that must be filled in the specification of each of the order, the waybill, the manifest, and the payment slip, and after the execution subject obtains each type of declaration data, the execution subject may generate a number identifier corresponding to each type of declaration data, for example, the number identifier corresponding to the information that must be filled in corresponding to the order may be 1 to 10, the number identifier corresponding to the information that must be filled in corresponding to the waybill may be 11 to 20, the number identifier corresponding to the information that must be filled in corresponding to the manifest may be 21 to 30, and the number identifier corresponding to the information that must be filled in corresponding to the payment slip may be 31 to 40. The "corresponding information that needs to be filled in" may be information that needs to be included in a message information filling format of a declaration interface corresponding to the declaration form message, and the information that needs to be included may be preset according to requirements of the declaration interface and a highest declaration auditing node (for example, may be a customs service). Each reporting interface (which may be a reporting port, for example) may interface with one or more merchants (i.e., users), each reporting interface in communication with a highest reporting audit node. When a document is required to be declared, declaration interfaces are required to be declared, each declaration interface has different requirements on the format and the content of a declaration document message, and the execution main body can generate a message template meeting the requirements of the declaration interfaces according to various types of declaration data and the generated corresponding serial number identifications according to the requirements on the format and the content of the declaration document message corresponding to each declaration interface stored in a routing configuration file. And the execution main body can encapsulate each message template, hide the attribute and implementation details of each message template, and only externally disclose the interface of the interface single template for calling and generating the declaration interface message corresponding to the determined declaration interface. The format of the message sent to the highest declaration auditing node is defined by customs. The encapsulation is to fill the declared content required by the client according to the message format required by customs.
Wherein, for example, the declaration source of each type of declaration data is composed of the following classes: self-service commodities; the third-party merchant can only use warehousing and distribution; the client can only require the declaration of the document on a declaration system (or declaration platform), and the client has own storage and delivery. The different declaration sources can be docked with the customs declaration system in a system docking mode.
The execution principal may determine the declaration type prior to docking the highest declaration audit node. For example, the need for small eastern self-service merchandise states: payment order, waybill, and invoice to a facilitator. This is because the self-owned merchandise needs to be paid to the small east for shipment and the small east for delivery. While some third parties need only the delivery of the small east, this situation only requires the declaration of the waybill. That is, before reporting, the type of the message (or called message type) to be reported is determined according to the user requirement.
And step S104, sending the declaration interface message to a preset approval node to obtain an approval result and forwarding the approval result.
After the execution main body generates the corresponding declaration interface message, the declaration interface message can be sent to a preset approval node, for example, the highest declaration approval node, so that the preset approval node approves the declaration interface message and returns an approval result; and the execution main body receives the approval result returned by the approval node and forwards the approval result to the terminal equipment used by the user. For example, the approval result may be that the user's annual consumption amount does not exceed a threshold and the number of purchased goods does not exceed a threshold, and the approval is passed; of course, the approval result may be that the annual consumption amount of the user exceeds a threshold value, and the commodity cannot be purchased again in the year and the approval is not passed. The present application does not specifically limit the details and forms of the approval rules and the approval results.
According to the embodiment, the requirement identification in the declaration form message is further acquired by acquiring the declaration form message; calling a routing configuration file, and analyzing a demand identifier to determine declaration information; calling a receiving template interface to generate a corresponding declaration interface message according to the declaration information; and sending a declaration interface message to a preset approval node to obtain an approval result and forwarding the approval result. Therefore, the workload of development, maintenance, on-line and the like of developers is reduced through simple and efficient configuration, and the system development and maintenance cost is reduced. When different new declaration interfaces are butted and different declaration types are responded, the document declaration can be easily realized by calling the receipt template interface without repeating the declaration flow for many times, so that a user does not need to care about a declaration system, the logic of interaction with customs is isolated, the functional isolation is realized, the problem that codes are more and more bloated is solved, and the document declaration experience of the user is improved.
Fig. 2 is a schematic main flow diagram of a document declaration method according to a second embodiment of the present application, and as shown in fig. 2, the document declaration method includes:
step S201, acquiring a report document message, and further acquiring a demand identifier in the report document message.
Step S202, calling a routing configuration file, and analyzing the requirement identification to determine declaration information.
Step S203, calling the order receiving template interface to generate a corresponding declaration interface message according to the declaration information.
The principle of step S201 to step S203 is similar to that of step S101 to step S103, and is not described here again.
Specifically, step S203 may also be implemented by step S2031:
step S2031, according to the message type, calling the corresponding message template in the order receiving template interface, so as to generate the corresponding declaration interface message according to the declaration interface and the declaration receipt message.
In this embodiment, the order receiving template interface includes all information of orders, waybills, lists, and payment orders to deal with different declaration types. Subsequent document composition and declared data sources are all from the document receiving template interface, so that various document sources can be shielded, and repeated work of declaration, signature adding and the like can be reduced.
Specifically, step S2031 may also be implemented by step S20311:
step S20311, obtaining parameters needed by the corresponding message template from the declaration form message, and further splicing the message according to the parameters and the declaration interface to generate a corresponding declaration interface message.
In this embodiment, the execution body stores the routing configuration information in the routing configuration file, and provides page configuration for service personnel to configure. The type of the reported message and the technical docking mode can be determined in the service docking stage. For example, when a new a declaration interface is docked, an order needs to be declared in an https manner, and a waybill and a web service docking list are docked in an ftp manner, the executive agent can record the information in the routing configuration file after acquiring the information, and then can receive a drag event triggered by a service person, so as to configure the information on a page based on the drag of the service person. An interface, which is a collection of abstract methods, contains the methods that a class is to implement. The execution main body can call the order receiving template interface so as to call the methods for generating the declaration order, the declaration waybill, the declaration list and the declaration payment order, which are contained in the interface. The execution main body can call a corresponding message template in the order receiving template interface, wherein the message template can be an implementation method for generating various types of declaration forms in the order receiving template interface. The execution body can determine the message format information corresponding to the declaration interface according to the declaration interface. The execution subject can determine the parameters required to be acquired from the declaration form message according to the message format information corresponding to the declaration interface. The message format information may include a message format and content included in the message. After determining the message format corresponding to the declaration interface and the content required to be included in the message, the execution main body can extract the content required to be included in the message from the declaration form message, and further generate the corresponding declaration interface message according to the message format. It can be understood that the contents of the declaration interface message may be less than that of the declaration document message, and the declaration interface message may contain the most important declaration information in the declaration document message.
Among them, FTP (File Transfer Protocol) is one of protocols in the TCP/IP Protocol suite. The FTP protocol includes two components, one being an FTP server and the other being an FTP client. Wherein the FTP server is used for storing files, and the user can use the FTP client to access resources located on the FTP server through the FTP protocol. When a Web site is developed, Web pages or programs are typically transferred to a Web server using the FTP protocol. In addition, since FTP is very efficient in transmission, the protocol is also generally used when large files are transmitted over a network. The Web Service technology can ensure that different applications running on different machines can exchange data or be integrated with each other without additional and special third-party software or hardware. Applications implemented according to the Web Service specification may exchange data with each other regardless of the language, platform, or internal protocol used by them. Web Service is a self-describing, self-contained, available network module that can perform specific business functions. Web services are also easy to deploy because they are based on some conventional industry standards and some existing technologies, such as subset XML, HTTP under a standard generic markup language. Web Service reduces the cost of application interfaces. Web Service provides a generic mechanism for the integration of business processes throughout an enterprise and even across multiple organizations.
In the embodiment, the receipt template interface is packaged to deal with different declaration types, so that various document sources can be shielded, and repeated work such as declaration, signature adding and the like can be reduced.
And step S204, sending the declaration interface message to a preset approval node to obtain an approval result and forwarding the approval result.
The principle of step S204 is similar to that of step S104, and is not described here again.
In some optional implementations of this embodiment, the document declaration method further includes: and under the condition that the declaration interface message fails to be sent, generating a corresponding declaration interface message sending task and carrying out asynchronous retransmission. Under the condition that the declaration interface message fails to be sent to the highest declaration auditing node, the execution main body can generate an asynchronous task based on the declaration interface message, and then send the asynchronous task to the task pool for waiting execution so as to perform asynchronous retransmission until the transmission is successful.
Fig. 3 is a schematic view of an application scenario of a document declaration method according to a third embodiment of the present application. The document declaration method is applied to a scene of performing document declaration in a new bonded area. As shown in fig. 3, the server 303 obtains the declaration form message 301, and further obtains the requirement identifier 302 in the declaration form message 301. The server 303 invokes the routing profile 304 to parse the requirement identification 302 to determine the declaration information 305. The server invokes the pick-up template interface 304 to generate a corresponding declaration interface message 306 based on the declaration information 305. The server 303 sends a declaration interface message 306 to a preset approval node 307 to obtain an approval result 308 and forward the approval result.
FIG. 4 is a schematic diagram of the main elements of a document declaration apparatus according to an embodiment of the present application. As shown in fig. 4, the document declaration apparatus includes an acquisition unit 401, an analysis unit 402, a message generation unit 403, and a transmission unit 404.
The obtaining unit 401 is configured to obtain the declaration form message, and further obtain the requirement identifier in the declaration form message.
The parsing unit 402 is configured to invoke the routing configuration file and parse the requirement identifier to determine the declaration information.
A message generating unit 403 configured to call the order receiving template interface to generate a corresponding declaration interface message according to the declaration information.
The sending unit 404 sends the declaration interface message to a preset approval node to obtain an approval result and forward the approval result.
In some embodiments, parsing unit 402 is further configured to: and matching the requirement identification with each identification in the routing configuration file to determine a declaration interface, a message type and a declaration mode corresponding to the requirement identification.
In some embodiments, the document declaration apparatus further includes a packaging unit, not shown in fig. 4, configured to: acquiring various types of declaration data; generating serial number identifications corresponding to various types of declaration data; generating each message template according to the declaration data and the corresponding serial number identification; and packaging each message template to obtain a single template interface.
In some embodiments, the message generating unit 403 is further configured to: and calling a corresponding message template in the receipt template interface according to the message type so as to generate a corresponding declaration interface message according to the declaration interface and the declaration document message.
In some embodiments, the message generating unit 403 is further configured to: and acquiring parameters required by the corresponding message template from the declaration form message, and splicing the messages according to the parameters and the declaration interface to generate the corresponding declaration interface message.
In some embodiments, the document declaration apparatus further includes an asynchronous retransmission unit, not shown in fig. 4, configured to: and under the condition that the declaration interface message fails to be sent, generating a corresponding declaration interface message sending task and carrying out asynchronous retransmission.
It should be noted that, in the document declaration method and the document declaration apparatus of the present application, the specific implementation contents have corresponding relationships, and therefore, the repeated contents are not described again.
FIG. 5 illustrates an exemplary system architecture 500 to which the document declaration method or apparatus of embodiments of the present application may be applied.
As shown in fig. 5, the system architecture 500 may include terminal devices 501, 502, 503, a network 504, and a server 505. The network 504 serves to provide a medium for communication links between the terminal devices 501, 502, 503 and the server 505. Network 504 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 501, 502, 503 to interact with a server 505 over a network 504 to receive or send messages or the like. The terminal devices 501, 502, 503 may have installed thereon various communication client applications, such as shopping-like applications, web browser applications, search-like applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 501, 502, 503 may be various electronic devices having document declaration processing screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 505 may be a server providing various services, such as a back-office management server (for example only) providing support for declaration forms submitted by users using the terminal devices 501, 502, 503. The background management server can acquire the declaration document message and further acquire a requirement identifier in the declaration document message; calling a routing configuration file, and analyzing a demand identifier to determine declaration information; calling a receiving template interface to generate a corresponding declaration interface message according to the declaration information; and sending a declaration interface message to a preset approval node to obtain an approval result and forwarding the approval result. Therefore, when different new declaration interfaces are docked and different declaration types are responded, repeated declaration processes are not needed, document declaration can be easily realized by calling the receipt template interface, logic of interaction with customs is isolated, and user document declaration experience is improved.
It should be noted that the document declaration method provided in the embodiment of the present application is generally executed by the server 505, and accordingly, the document declaration apparatus is generally disposed in the server 505.
It should be understood that the number of terminal devices, networks, and servers in fig. 5 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 6, shown is a block diagram of a computer system 600 suitable for use in implementing a terminal device of an embodiment of the present application. The terminal device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.
As shown in fig. 6, the computer system 600 includes a Central Processing Unit (CPU)601 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 603. In the RAM603, various programs and data necessary for the operation of the computer system 600 are also stored. The CPU601, ROM602, and RAM603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, a mouse, and the like; an output section 607 including a signal processing section such as a Cathode Ray Tube (CRT), a liquid crystal credit authorization inquiry processor (LCD), and the like, and a speaker and the like; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The driver 610 is also connected to the I/O interface 605 as needed. A removable medium 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 610 as necessary, so that a computer program read out therefrom is mounted in the storage section 608 as necessary.
In particular, according to embodiments disclosed herein, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, embodiments disclosed herein include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 609, and/or installed from the removable medium 611. The above-described functions defined in the system of the present application are executed when the computer program is executed by the Central Processing Unit (CPU) 601.
It should be noted that the computer readable medium shown in the present application may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. 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 or flowchart illustration, and combinations of blocks in the block diagrams 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.
The units described in the embodiments of the present application may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor includes an acquisition unit, an analysis unit, a message generation unit, and a transmission unit. Wherein the names of the elements do not in some way constitute a limitation on the elements themselves.
As another aspect, the present application also provides a computer-readable medium, which may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs, and when the one or more programs are executed by the equipment, the equipment acquires the declaration form message and further acquires the requirement identification in the declaration form message; calling a routing configuration file, and analyzing a demand identifier to determine declaration information; calling a receiving template interface to generate a corresponding declaration interface message according to the declaration information; and sending a declaration interface message to a preset approval node to obtain an approval result and forwarding the approval result. Therefore, when different new declaration interfaces are docked and different declaration types are responded, repeated declaration processes are not needed, document declaration can be easily realized by calling the receipt template interface, logic of interaction with customs is isolated, and user document declaration experience is improved.
According to the technical scheme of the embodiment of the application, the requirement identification in the declaration form report is further acquired by acquiring the declaration form message; calling a routing configuration file, and analyzing a demand identifier to determine declaration information; calling a receiving template interface to generate a corresponding declaration interface message according to the declaration information; and sending a declaration interface message to a preset approval node to obtain an approval result and forwarding the approval result. Therefore, the workload of development, maintenance, on-line and the like of developers is reduced through simple and efficient configuration, and the system development and maintenance cost is reduced. When different new declaration interfaces are butted and different declaration types are responded, the document declaration can be easily realized by calling the receipt template interface without repeating the declaration flow for many times, so that a user does not need to care about a declaration system, the logic of interaction with customs is isolated, the functional isolation is realized, the problem that codes are more and more bloated is solved, and the document declaration experience of the user is improved.
The above-described embodiments should not be construed as limiting the scope of the present application. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims (12)

1. A document declaration method, comprising:
acquiring an application document message and further acquiring a demand identifier in the application document message;
calling a routing configuration file, and analyzing a demand identifier to determine declaration information;
calling a receiving template interface to generate a corresponding declaration interface message according to the declaration information;
and sending the declaration interface message to a preset approval node to obtain an approval result and forwarding the approval result.
2. The method of claim 1, wherein determining the declaration information comprises:
and matching the requirement identification with each identification in the routing configuration file to determine a declaration interface, a message type and a declaration mode corresponding to the requirement identification.
3. The method of claim 2, wherein prior to said invoking the order template interface, the method further comprises:
acquiring various types of declaration data;
generating serial number identifications corresponding to the various types of declaration data;
generating each message template according to the declaration data and the corresponding serial number identification;
and packaging the message templates to obtain a list receiving template interface.
4. The method of claim 3, wherein generating the corresponding declaration interface message comprises:
and calling a corresponding message template in the order receiving template interface according to the message type so as to generate a corresponding declaration interface message according to the declaration interface and the declaration document message.
5. The method of claim 4, wherein generating a corresponding declaration interface message from the declaration interface and the declaration document message comprises:
and acquiring parameters required by the corresponding message template from the declaration form report, and splicing the messages according to the parameters and the declaration interface to generate the corresponding declaration interface message.
6. The method of claim 1, further comprising:
and under the condition that the declaration interface message fails to be sent, generating a corresponding declaration interface message sending task and carrying out asynchronous retransmission.
7. A document declaration apparatus, comprising:
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is configured to acquire an declaration document message and further acquire a requirement identification in the declaration document message;
the analysis unit is configured to call the routing configuration file and analyze the requirement identification to determine declaration information;
the message generating unit is configured to call a receiving template interface to generate a corresponding declaration interface message according to the declaration information;
and the sending unit is configured to send the declaration interface message to a preset approval node to obtain an approval result and forward the approval result.
8. The apparatus of claim 7, wherein the parsing unit is further configured to:
and matching the requirement identification with each identification in the routing configuration file to determine a declaration interface, a message type and a declaration mode corresponding to the requirement identification.
9. The apparatus of claim 8, further comprising an encapsulation unit configured to:
acquiring various types of declaration data;
generating serial number identifications corresponding to the various types of declaration data;
generating each message template according to the declaration data and the corresponding serial number identification;
and packaging the message templates to obtain a list receiving template interface.
10. The apparatus of claim 9, wherein the message generation unit is further configured to:
and calling a corresponding message template in the order receiving template interface according to the message type so as to generate a corresponding declaration interface message according to the declaration interface and the declaration document message.
11. A document declaration electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-6.
12. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-6.
CN202111056821.3A 2021-09-09 2021-09-09 Document reporting method and device Active CN113760582B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111056821.3A CN113760582B (en) 2021-09-09 2021-09-09 Document reporting method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111056821.3A CN113760582B (en) 2021-09-09 2021-09-09 Document reporting method and device

Publications (2)

Publication Number Publication Date
CN113760582A true CN113760582A (en) 2021-12-07
CN113760582B CN113760582B (en) 2024-05-24

Family

ID=78794368

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111056821.3A Active CN113760582B (en) 2021-09-09 2021-09-09 Document reporting method and device

Country Status (1)

Country Link
CN (1) CN113760582B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116503887A (en) * 2023-06-29 2023-07-28 南京元圈软件科技有限公司 Goods generation order processing method based on image recognition

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109039751A (en) * 2018-08-14 2018-12-18 深圳壹账通智能科技有限公司 Configure method, apparatus, computer equipment and the storage medium of routing
CN111369253A (en) * 2020-03-18 2020-07-03 中国建设银行股份有限公司 Foreign exchange service declaration method, device, equipment and storage medium
CN111815400A (en) * 2020-06-16 2020-10-23 上海中通吉网络技术有限公司 Cross-border trade electronic commerce logistics information customs declaration method and device
CN112232769A (en) * 2020-10-16 2021-01-15 拜耳医药保健有限公司 Method, apparatus, device and medium for genetic resource related declaration
CN112418812A (en) * 2020-12-02 2021-02-26 上海三稻智能科技有限公司 Distributed full-link automatic intelligent clearance system, method and storage medium
WO2021062717A1 (en) * 2019-09-30 2021-04-08 华为技术有限公司 Buffer status report transmission method and device
CN112769700A (en) * 2020-12-29 2021-05-07 浙江合众新能源汽车有限公司 Routing method and routing system based on application method number

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109039751A (en) * 2018-08-14 2018-12-18 深圳壹账通智能科技有限公司 Configure method, apparatus, computer equipment and the storage medium of routing
WO2021062717A1 (en) * 2019-09-30 2021-04-08 华为技术有限公司 Buffer status report transmission method and device
CN111369253A (en) * 2020-03-18 2020-07-03 中国建设银行股份有限公司 Foreign exchange service declaration method, device, equipment and storage medium
CN111815400A (en) * 2020-06-16 2020-10-23 上海中通吉网络技术有限公司 Cross-border trade electronic commerce logistics information customs declaration method and device
CN112232769A (en) * 2020-10-16 2021-01-15 拜耳医药保健有限公司 Method, apparatus, device and medium for genetic resource related declaration
CN112418812A (en) * 2020-12-02 2021-02-26 上海三稻智能科技有限公司 Distributed full-link automatic intelligent clearance system, method and storage medium
CN112769700A (en) * 2020-12-29 2021-05-07 浙江合众新能源汽车有限公司 Routing method and routing system based on application method number

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
朱利妍;牛鹏;: "金融自助终端报文通信系统研究", 计算机与网络, no. 16, 26 August 2018 (2018-08-26) *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116503887A (en) * 2023-06-29 2023-07-28 南京元圈软件科技有限公司 Goods generation order processing method based on image recognition
CN116503887B (en) * 2023-06-29 2023-09-19 南京元圈软件科技有限公司 Goods generation order processing method based on image recognition

Also Published As

Publication number Publication date
CN113760582B (en) 2024-05-24

Similar Documents

Publication Publication Date Title
CN110866709B (en) Method and device for merging orders
US20070233575A1 (en) Architectural design for strategic sourcing application software
CN110619555A (en) Unified management method and device for order information, terminal equipment and medium
KR101883694B1 (en) Automation system for import-export customs procedure and adjustment
WO2021073477A1 (en) Method and apparatus for supporting modification of consignee information
CN111950249A (en) Message generation method and device, electronic equipment and storage medium
CN113760582B (en) Document reporting method and device
US9454737B2 (en) Solution that leverages an instant messaging system to manage ad hoc business process workflows
CN113298484B (en) Order information customs declaration method and device and electronic equipment
CN113780969A (en) Customs declaration method and system
CN113296613A (en) Customs clearance information processing method and device and electronic equipment
CN113535101B (en) Print file generation method and device, storage medium and electronic equipment
CN112785321A (en) Incentive management method and device
US20240054451A1 (en) Inventory information processing method and device
US9268514B2 (en) Formatting data
CN114138712A (en) File processing method, processing device, electronic equipment and storage medium
CN109472592B (en) Method and device for managing virtual assets
CN110414881B (en) Foreign trade information processing method and system
CN113992761A (en) Transaction processing method, apparatus, electronic device, medium, and program product
CN108718241B (en) Charging method and device
CN113760279A (en) Method and device for generating page
CN112785361A (en) Interactive processing method and device for ordering goods
CN113643014B (en) Block chain-based transaction management method, apparatus, device, medium, and program
JP7489361B2 (en) Information processing system and information processing device
TWM647330U (en) Product propagating system

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