WO2020000720A1 - 服务器、报文处理方法、程序和计算机可读存储介质 - Google Patents

服务器、报文处理方法、程序和计算机可读存储介质 Download PDF

Info

Publication number
WO2020000720A1
WO2020000720A1 PCT/CN2018/107506 CN2018107506W WO2020000720A1 WO 2020000720 A1 WO2020000720 A1 WO 2020000720A1 CN 2018107506 W CN2018107506 W CN 2018107506W WO 2020000720 A1 WO2020000720 A1 WO 2020000720A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
information
query
preset
type
Prior art date
Application number
PCT/CN2018/107506
Other languages
English (en)
French (fr)
Inventor
周鹏华
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2020000720A1 publication Critical patent/WO2020000720A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5048—Automatic or semi-automatic definitions, e.g. definition templates
    • 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
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a server, a message processing method, a program, and a computer-readable storage medium.
  • the gateway interface mainly involves the definition of the processing method of the gateway interface message.
  • the existing method of defining the processing method of the gateway interface message is based on the data processing of the gateway interface of the financial institution.
  • Logic writes corresponding code at the gateway interface proxy layer to implement the assembly of gateway interface messages, the analysis of gateway interface return messages, and the call of gateway interfaces.
  • the disadvantage of this method is that when the data processing logic of the interface of the financial institution changes, it is necessary to modify the code again and restart the business requester server.
  • the main purpose of this application is to provide a server, a message processing method, a program, and a computer-readable storage medium.
  • the purpose is to solve the need to re-modify the code and restart the service requester when the data processing logic of the gateway interface of the service processor changes. Problems with the server.
  • a server provided in this application includes a memory and a processor, and a message processing program is stored on the memory, and the message processing program is executed by the processor to implement the following steps:
  • Obtaining step when receiving a preset first type service request instruction, obtaining service information of the preset first type service;
  • First query step Query the preset first type of service according to the obtained mapping relationship between the service processor service identification information in the service information and the predetermined service processor service identification information and configuration information. Corresponding configuration information;
  • the second query step query the preset first type according to the obtained mapping relationship between the service processor service identification information in the service information and the predetermined service processor service identification information and gateway interface information. Gateway interface information corresponding to the service;
  • Assembly step Assemble a preset first type service request message according to the service information and the configuration information;
  • Sending step sending the assembled first preset type service request message to a service requester gateway interface corresponding to the queried gateway interface information, for the service requester gateway interface to send the preset first A type of service request message is sent to the corresponding service processor gateway interface.
  • the present application also proposes a message processing method, which is characterized in that the method includes:
  • Obtaining step when receiving a preset first type service request instruction, obtaining service information of the preset first type service;
  • First query step Query the preset first type of service according to the obtained mapping relationship between the service processor service identification information in the service information and the predetermined service processor service identification information and configuration information. Corresponding configuration information;
  • the second query step query the preset first type according to the obtained mapping relationship between the service processor service identification information in the service information and the predetermined service processor service identification information and gateway interface information. Gateway interface information corresponding to the service;
  • Assembly step Assemble a preset first type service request message according to the service information and the configuration information;
  • Sending step sending the assembled first preset type service request message to a service requester gateway interface corresponding to the queried gateway interface information, for the service requester gateway interface to send the preset first A type of service request message is sent to the corresponding service processor gateway interface.
  • this application also proposes a message processing program, which includes:
  • An obtaining module configured to obtain service information of the preset first type service when receiving a preset first type service request instruction
  • a first query module configured to query the preset first according to the mapping relationship between the service processor service identification information in the obtained service information and the predetermined service processor service identification information and configuration information; Configuration information corresponding to type services;
  • a second querying module is configured to query the preset number according to the mapping relationship between the service processor service identification information in the obtained service information and the predetermined service processor service identification information and gateway interface information.
  • Gateway interface information corresponding to a type of service
  • An assembly module configured to assemble a preset first type service request message according to the service information and the configuration information
  • a sending module configured to send the assembled first preset type service request message to a service requester gateway interface corresponding to the queried gateway interface information, for the service requester gateway interface to send the It is assumed that the first type service request message is sent to the corresponding service processor gateway interface.
  • the present application also proposes a computer-readable storage medium, where the computer-readable storage medium stores a message processing program, and the message processing program can be executed by at least one processor to enable all Said at least one processor performs the following steps:
  • Obtaining step when receiving a preset first type service request instruction, obtaining service information of the preset first type service;
  • First query step Query the preset first type of service according to the obtained mapping relationship between the service processor service identification information in the service information and the predetermined service processor service identification information and configuration information. Corresponding configuration information;
  • the second query step query the preset first type according to the obtained mapping relationship between the service processor service identification information in the service information and the predetermined service processor service identification information and gateway interface information. Gateway interface information corresponding to the service;
  • Assembly step Assemble a preset first type service request message according to the service information and the configuration information;
  • Sending step sending the assembled first preset type service request message to a service requester gateway interface corresponding to the queried gateway interface information, for the service requester gateway interface to send the preset first A type of service request message is sent to the corresponding service processor gateway interface.
  • This application obtains the service information of the preset first type service, and queries the configuration information and gateway interface information corresponding to the first type service according to the service information of the preset first type service.
  • a first type service request message is set, and an assembled preset first type service request message is sent to a corresponding gateway interface.
  • the present application sets configuration information according to the gateway interface data processing logic of the service processor, and when the service requester needs to call the service processor for service processing, according to the configuration Information assembling, parsing messages, and calling gateway interfaces.
  • the data processing logic of the gateway interface of the service processor changes, this application does not need to modify the code and restart the server. It only needs to modify the corresponding configuration information. Once the modified configuration information is saved, it will take effect immediately without affecting the business request. Under the premise of normal operation of the square system, the system maintenance efficiency is improved.
  • FIG. 1 is a schematic diagram of an optional application environment of each embodiment of the present application.
  • FIG. 2 is a schematic diagram of an operating environment of the first, second, and third embodiments of a message processing program of this application;
  • FIG. 3 is a program module diagram of a first embodiment of a message processing program of the present application.
  • FIG. 4 is a detailed program module diagram of the first acquisition module in FIG. 3;
  • FIG. 5 is a detailed program module diagram of the first query module in FIG. 3;
  • FIG. 6 is a program module diagram of a second embodiment of a message processing program of the present application.
  • FIG. 7 is a program module diagram of a third embodiment of an interface message processing program of the present application.
  • FIG. 8 is a schematic flowchart of a first embodiment of a message processing method of the present application.
  • FIG. 9 is a detailed flowchart of step S10 in FIG. 8;
  • FIG. 10 is a detailed flowchart of step S20 in FIG. 8; FIG.
  • FIG. 11 is a schematic flowchart of a second embodiment of a message processing method of this application.
  • FIG. 12 is a schematic flowchart of a third embodiment of a message processing method of this application.
  • FIG. 1 is a schematic diagram of an optional application environment of each embodiment of the present application.
  • the present application can be applied to, but is not limited to, a server 1, multiple clients 2, multiple service requester gateway interfaces 3, multiple service processor gateway interfaces 4, service processor server 5 Application environment.
  • Server 1 communicates with multiple clients 2 and multiple service requester gateway interfaces, and each service requester gateway interface 3 communicates with the corresponding service processor gateway interface 4, and multiple service processor gateway interfaces 4 communicate with the service.
  • the processor server 5 is communicatively connected.
  • the client 2 is a client of a service requester.
  • the client 2 is used to provide a user operation interface, and sends a preset first type of service request instruction triggered by a user to the server 1 for processing, and receives a service returned by the server 1 process result.
  • the server 1 is a server of a service requester, and the server 1 is configured to run a message processing program to implement the steps of the message processing method of the present application.
  • the service requester gateway interface 3 is configured to receive a message sent by the server 1 and send the message to a corresponding service processor gateway interface 4.
  • the service requester gateway interface 3 is further configured to receive a service processor gateway The packet returned by the interface 4 is sent to the service requester gateway interface 3.
  • the service processor gateway interface 4 is configured to receive a message sent by the service requester gateway interface 3, and parse the message into data readable by the service processor server 5.
  • the service processor gateway interface 4 is further configured to: The data sent by the service processor server 5 is assembled into a message and sent to the corresponding service requester gateway interface 3.
  • the service processor server 5 is configured to receive data sent by the service processor gateway interface 4, perform service processing according to the data, and return a result of the service processing to the service processor gateway interface 4.
  • This application proposes a message processing program.
  • FIG. 2 is a schematic diagram of an operating environment of the first embodiment of the message processing program 10 of the present application.
  • the message processing program 10 is installed and run on the server 1.
  • the server 1 is a device capable of automatically performing calculation and / or information processing according to an instruction set or stored in advance.
  • the server 1 may include, but is not limited to, a memory 11, a processor 12, and a display 13.
  • FIG. 2 only shows the server 1 with components 11-13, but it should be understood that it is not required to implement all the components shown, and more or fewer components may be implemented instead.
  • the memory 11 may be an internal storage unit of the server 1 in some embodiments, such as a hard disk or a memory of the server 1.
  • the memory 11 may also be an external storage device of the server 1 in other embodiments, such as a plug-in hard disk, a Smart Media Card (SMC), and a Secure Digital (SD) card provided on the server 1. Flash cards, etc.
  • the memory 11 may include both an internal storage unit of the server 1 and an external storage device.
  • the memory 11 is configured to store application software installed on the server 1 and various types of data, such as program codes of the message processing program 10.
  • the memory 11 may also be used to temporarily store data that has been output or is to be output.
  • the processor 12 may be a central processing unit (CPU), a microprocessor or other data processing chip in some embodiments, and is configured to run program codes or process data stored in the memory 11, for example, to perform message processing. Procedure 10 and so on.
  • CPU central processing unit
  • microprocessor or other data processing chip in some embodiments, and is configured to run program codes or process data stored in the memory 11, for example, to perform message processing. Procedure 10 and so on.
  • the display 13 may be an LED display, a liquid crystal display, a touch-type liquid crystal display, an OLED (Organic Light-Emitting Diode) touch device, or the like.
  • the display 13 is used to display information processed in the server 1 and to display a visualized user interface.
  • the components 11-13 of the server 1 communicate with each other through a program bus.
  • FIG. 3 is a program module diagram of the first embodiment of the message processing program 10 of the present application.
  • the message processing program 10 may be divided into one or more modules, and the one or more modules are stored in the memory 11 and processed by one or more processors (the processor 12 in this embodiment) Implemented to complete this application.
  • the message processing program 10 may be divided into a first acquisition module 101, a first query module 102, a second query module 103, an assembly module 104, and a sending module 105.
  • the module referred to in this application refers to a series of computer program instruction segments capable of performing specific functions, which is more suitable than the program to describe the execution process of the message processing program 10 in the server 1, wherein:
  • the first obtaining module 101 is configured to obtain service information of the preset first type service when receiving a preset first type service request instruction.
  • the above-mentioned preset first-type service request instruction may be initiated by a user through a client.
  • the user needs to pay through a service processor, and when jumping to a payment page, the preset first-type service request is triggered.
  • the above-mentioned preset first types of services include, but are not limited to: collection services, payment services, and authentication services.
  • the so-called collection service refers to the business in which the cardholder signs a business commission agreement with a merchant (for example, an e-commerce platform operated by a business requester), and allows the merchant to request and complete the payment of the specified amount to the cardholder's designated account according to the agreement. It is used to realize the directed transfer of funds from the cardholder account to the merchant account based on the agreed use.
  • a merchant for example, an e-commerce platform operated by a business requester
  • the so-called payment service refers to the business where the merchant (for example, an e-commerce platform operated by the business requester) transfers funds from its own settlement account to the cardholder's designated bank card account, such as insurance claims, fund dividends, and payment on behalf of customers .
  • the merchant for example, an e-commerce platform operated by the business requester
  • the so-called authentication service refers to the service where the service processor verifies whether the user has the right to access the system.
  • the first obtaining module 101 includes a selecting unit 1011 and an obtaining unit 1012, where:
  • a selecting unit 1011 is configured to extract service request information in the preset first type service request instruction, and select an optimal service channel among a plurality of predetermined service channels according to the service request information and a predetermined selection rule. .
  • the above service request information includes a service type, service identification information, and service content information.
  • the service types include collection service, payment service and authentication service.
  • the service identification information includes a service number, for example, an order number.
  • the above business content information is different based on the type of business. For example, if the business type is collection service or payment service, the business content information includes payer information, payee information, and transaction amount. Rights business, the business content information includes user identity information, bank card information, and so on.
  • the above service channel is a service processing link divided according to a service provided by a service processor.
  • a service processor For example, UnionPay collection channel, UnionPay payment channel, UnionPay authentication channel, Bank A collection channel, Bank A payment channel, Bank A authentication channel, etc.
  • the services provided by the business processor mentioned above are the services that the business processor can handle.
  • the service channel may be divided according to a specific application scenario, which is not limited in this application.
  • the foregoing predetermined selection rule in this embodiment includes:
  • a service channel supporting the service is determined as a candidate service channel.
  • the method for determining whether a service channel supports the preset first type of service is as follows:
  • the service type determine whether the service channel has the authority to process the preset first type service; if not, determine that the service channel does not support the preset first type service, and if so, continue to determine the service Whether the channel is open (for example, if some channels may fail, the channel is closed).
  • the preset first type service is an authentication service
  • the service channel is opened, it is determined that the service channel supports the preset first type service, and if the service channel is not opened, it is determined that the service channel is not supported. This item presets the first type of service.
  • the preset first type of service is a collection service or a payment service
  • determine whether the opened service channel meets a preset limit condition for example, determine the opening Whether the total amount of the transaction amount processed on the day of the business channel plus the amount of the transaction amount in the business content information does not exceed the preset threshold
  • a preset limit condition for example, determine the opening Whether the total amount of the transaction amount processed on the day of the business channel plus the amount of the transaction amount in the business content information does not exceed the preset threshold
  • sorting parameters include service rate, business timeliness (that is, the time required for the business processor to complete the collection service or the payment service), priority, and the like.
  • This sorting parameter can be set according to requirements, and is not limited to the content listed above.
  • the foregoing steps of sorting the candidate service channels based on the sorting parameters of the candidate service channels specifically include:
  • the candidate business channels of the same priority are sorted based on the order of the service rates from low to high.
  • the candidate business channels with the same priority and payment rate are sorted based on the order of the business aging from short to long to obtain the ranking results of the candidate business channels from good to bad.
  • the above service charge rate refers to the service charge rate charged by the business processor to the business requester. And if the service type is an authentication service, the service time limit is not used as a sorting parameter.
  • the candidate business channel that satisfies the preset conditions is taken as the optimal business channel.
  • the above-mentioned preset conditions can be set according to requirements. For example, if the sorting result is a result of the order of the business channels to be selected in descending order, the preset condition is to select the business channel to be selected first.
  • the obtaining unit 1012 is configured to obtain service channel information of the optimal service channel, and use the service request information and service channel information as service information of the preset first type of service.
  • the business channel information of the optimal business channel includes service processor service identification information.
  • service processor service identification information refers to the identification information of the service provided by the service processor.
  • the service identification information is 001002.
  • the service channel information of the optimal service channel may further include service processor organization identification information, for example, the bank A organization identification information is 001.
  • the first querying module 102 is configured to query the preset number according to the mapping relationship between the service processor service identification information in the obtained service information and the predetermined service processor service identification information and configuration information. Configuration information corresponding to a type of service.
  • the configuration information is set in advance according to the gateway interface data processing logic of the service processor.
  • the first query module 102 includes a first query unit 1021 and a second query unit 1022, where:
  • the first querying unit 1021 is configured to query a configuration information identifier corresponding to the service processor service identification information in the service information according to a predetermined mapping relationship between the service processor service identification information and the configuration information identifier. (For example, configuration information ID).
  • the configuration information identifier corresponding to the service processor service identification information is the configuration information identifier corresponding to the preset first type of service.
  • mapping relationship between the service processor service identification information and the configuration information identifier may be stored in a corresponding mapping relationship table.
  • a second querying unit 1022 is configured to determine, according to a predetermined mapping relationship between the configuration information identifier and the configuration information, the configuration information corresponding to the queryed configuration information identifier, where the configuration information is the Preset configuration information corresponding to the first type of service.
  • mapping relationship between the configuration information identifier and the configuration information may be stored in a corresponding mapping relationship table.
  • the above-mentioned first query unit 1021, the second query unit 1022 may be replaced by a third query unit (not shown in the figure), which is used for :
  • the corresponding configuration information is the configuration information corresponding to the preset first type of service.
  • the service processor service identification information in the obtained service information and the service processor service identification information determined in advance according to the obtained service information may further include the following steps: loading (ie parsing) all configuration information in the memory, and subsequently processing the application message All required configuration information can be queried from memory. In addition, whether the configuration information is updated in real time or periodically is detected, and if so, the configuration information is reloaded in the memory.
  • the second querying module 103 is configured to query the preset according to the mapping relationship between the service processor service identification information in the obtained service information and the predetermined service processor service identification information and gateway interface information. Gateway interface information corresponding to the first type of service.
  • the foregoing gateway interface refers to a gateway interface provided by a service requester.
  • the service requester sets a gateway for each service processor, and sets multiple gateway interfaces according to various services provided by the service processor.
  • the above-mentioned gateway interface information includes a gateway interface identifier (for example, a gateway interface ID).
  • mapping relationship between the business processor service identification information and the gateway interface information may be stored in the same mapping relationship table as the mapping relationship between the business processor service identification information and the configuration information identifier, or the business processor service
  • the mapping relationship between the identification information and the gateway interface information may be stored in different mapping relationship tables with the above-mentioned mapping relationship between the service processor service identification information and the configuration information identifier.
  • the assembling module 104 is configured to assemble a preset first type service request message according to the service information and the configuration information.
  • the above configuration information defines a preset first type service request message assembly template according to the service processor's gateway interface data processing logic. Therefore, based on the assembly template, the service information is assembled as the message content, so that the service processor can When the first type service request message is received, the preset first type service request message can be directly read.
  • a sending module 105 is configured to send the assembled first preset type service request message to a service requester gateway interface corresponding to the queried gateway interface information, so that the service requester gateway interface may The preset first type service request message is sent to the corresponding service processor gateway interface.
  • the assembled preset first type service request message is sent to the queried service requester gateway interface, and the service information corresponding to the preset first type service request message is stored and processed (for example, Stored in a database). Then, the service requester gateway interface sends the preset first type service request message to the corresponding service processor gateway interface. After the service processor gateway interface receives the preset first type service request message, Process the preset first type of service.
  • service information of a preset first type service is acquired, and configuration information and gateway interface information corresponding to the first type service are queried according to the service information of the preset first type service, and assembled according to the service information and configuration information.
  • the preset first type service request message is sent, and the assembled preset first type service request message is sent to the corresponding gateway interface.
  • the configuration information is set according to the data processing logic of the gateway interface of the service processor.
  • FIG. 6 is a program module diagram of the second embodiment of the message processing program 10 of this application.
  • the program further includes a receiving module 106.
  • the receiving module 106 is configured to receive a preset first type service return message returned by the service requester gateway interface, and according to the query result, The configuration information parses the preset first type of service return message.
  • the service processor gateway interface returns a preset first type service return message to the corresponding service requester gateway interface, and the service requester gateway interface returns the preset first type service return message. Since the configuration information includes parsing data of the return message field preset according to the service processor gateway interface data processing logic, the preset first type of service return message can be parsed according to the configuration information.
  • the preset first type of service return message contains an error code
  • the service identification information and the error code parsing information find the corresponding error code parsing information, and according to the search
  • the error code analysis information is used to escape the error code.
  • the message processing program 10 when the service type of the preset first type of service is a collection service or a payment service, the message processing program 10 further includes an update module (not shown in the figure), and the update The module is configured to update the recorded daily transaction limit data of the payer (deduct the transaction amount from the daily transaction limit data) according to the amount of the transaction amount in the service request information.
  • the update module is further configured to update the recorded daily transaction limit data of the payer (from the daily transaction limit) when it is determined that the collection service fails or the payment service fails according to the parsed preset first type service return message. Roll back the deducted transaction amount in the data).
  • FIG. 7 is a program module diagram of the third embodiment of the message processing program 10 of this application.
  • the program further includes a startup module 107 and a query service module 108, where:
  • the starting module 107 is configured to start a preset second type service when the preset first type service return message is not received within a preset period of time.
  • the preset second type of service includes a query service.
  • the program further includes a query service module 108, and the query service module 108 is configured to:
  • query service identification information is generated, and service information corresponding to the preset first type service request message to be queried is obtained, and extracted from the service information.
  • the service processor service identification information and business identification information are used as query business information.
  • the service information corresponding to the to-be-queried preset first type service request message is stored and processed. Therefore, only It is necessary to find out the service information corresponding to the preset first type of service request message to be queried from the storage space.
  • the query service correspondence is obtained.
  • Configuration information
  • the query service is queried according to a mapping relationship among service processor service identification information, query service identification information, and the predetermined service processor service identification information, query service identification information, and configuration information identifier.
  • Corresponding configuration information identifier for example, configuration information ID.
  • the above-mentioned predetermined mapping relationship between the service processor service identification information, query service identification information, and configuration information identifier may be stored in a corresponding mapping relationship table.
  • the configuration information corresponding to the configuration information identifier is the configuration information corresponding to the query service.
  • the mapping relationship between the configuration information identifier and the configuration information may be stored in a corresponding mapping relationship table.
  • the query service is obtained according to the mapping relationship among the service processor service identification information, the query service identification information, and the predetermined service processor service identification information, the query service identification information, and the gateway interface information.
  • Gateway interface information corresponding to the information.
  • mapping relationship between the predetermined service processor service identification information, query service identification information, and gateway interface information, and the predetermined service processor service identification information, query service identification information, and configuration information identifier are determined in advance.
  • the mapping relationship between the three symbols can be stored in the same mapping relationship table, or can be stored in different mapping relationship tables respectively.
  • a query request message is assembled, and the assembled query request message is sent to a service requester gateway interface corresponding to the obtained gateway interface information for The service requester gateway interface sends the query request message to a corresponding service processor gateway interface.
  • the above configuration information defines an assembly template for the query request message according to the gateway interface data processing logic of the service processor, based on the assembly template, the query service information is assembled as the message content, so that the service processor can When the query request message is received, the query request message can be directly read.
  • the configuration information includes parsing data of the query return message field preset according to the service processor gateway interface data processing logic, the query return message can be parsed according to the configuration information to obtain search result.
  • the status of the current processing of the preset first type of service by the service processor can be learned, so that according to the processing The state even adjusts business processing strategies.
  • the present application proposes a message processing method.
  • FIG. 8 is a schematic flowchart of a first embodiment of a message processing method of this application.
  • the method includes:
  • Step S10 When receiving a preset first type service request instruction, obtain service information of the preset first type service.
  • the above-mentioned preset first-type service request instruction may be initiated by a user through a client.
  • the user needs to pay through a service processor, and when jumping to a payment page, the preset first-type service request is triggered.
  • the above-mentioned preset first types of services include, but are not limited to: collection services, payment services, and authentication services.
  • the so-called collection service refers to the business in which the cardholder signs a business commission agreement with a merchant (for example, an e-commerce platform operated by a business requester), and allows the merchant to request and complete the payment of the specified amount to the cardholder's designated account according to the agreement. It is used to realize the directed transfer of funds from the cardholder account to the merchant account based on the agreed use.
  • a merchant for example, an e-commerce platform operated by a business requester
  • the so-called payment service refers to the business where the merchant (for example, an e-commerce platform operated by the business requester) transfers funds from its own settlement account to the cardholder's designated bank card account, such as insurance claims, fund dividends, and payment on behalf of customers .
  • the merchant for example, an e-commerce platform operated by the business requester
  • the so-called authentication service refers to the service where the service processor verifies whether the user has the right to access the system.
  • step S10 specifically includes:
  • Step S11 Extract service request information in the preset first type service request instruction, and select an optimal service channel among a plurality of predetermined service channels according to the service request information and a predetermined selection rule.
  • the above service request information includes a service type, service identification information, and service content information.
  • the service types include collection service, payment service and authentication service.
  • the service identification information includes a service number, for example, an order number.
  • the above business content information is different based on different business types. For example, if the business type is collection service or payment service, the business content information includes payer information, payee information, and transaction amount; if the service type is authentication Business, the business content information includes user identity information, bank card information, and so on.
  • the above service channel is a service processing link divided according to a service provided by a service processor.
  • a service processor For example, UnionPay collection channel, UnionPay payment channel, UnionPay authentication channel, Bank A collection channel, Bank A payment channel, Bank A authentication channel, etc.
  • the services provided by the business processor mentioned above are the services that the business processor can handle.
  • the service channel may be divided according to a specific application scenario, which is not limited in this application.
  • the foregoing predetermined selection rule in this embodiment includes:
  • a service channel supporting the service is determined as a candidate service channel.
  • the method for determining whether a service channel supports the preset first type of service is as follows:
  • the service type determine whether the service channel has the authority to process the preset first type service; if not, determine that the service channel does not support the preset first type service, and if so, continue to determine the service Whether the channel is open (for example, if some channels may fail, the channel is closed).
  • the preset first type service is an authentication service
  • the service channel is opened, it is determined that the service channel supports the preset first type service, and if the service channel is not opened, it is determined that the service channel is not supported. This item presets the first type of service.
  • the preset first type of service is a collection service or a payment service
  • determine whether the opened service channel meets a preset limit condition for example, determine the opening Whether the total amount of the transaction amount processed on the day of the business channel plus the amount of the transaction amount in the business content information does not exceed the preset threshold
  • a preset limit condition for example, determine the opening Whether the total amount of the transaction amount processed on the day of the business channel plus the amount of the transaction amount in the business content information does not exceed the preset threshold
  • sorting parameters include service rate, business timeliness (that is, the time required for the business processor to complete the collection service or the payment service), priority, and the like.
  • This sorting parameter can be set according to requirements, and is not limited to the content listed above.
  • the foregoing steps of sorting the candidate service channels based on the sorting parameters of the candidate service channels specifically include:
  • the candidate business channels of the same priority are sorted based on the order of the service rates from low to high.
  • the candidate business channels with the same priority and payment rate are sorted based on the order of the business aging from short to long to obtain the ranking results of the candidate business channels from good to bad.
  • the above service charge rate refers to the service charge rate charged by the business processor to the business requester. And if the service type is an authentication service, the service time limit is not used as a sorting parameter.
  • the candidate business channel that satisfies the preset conditions is taken as the optimal business channel.
  • the above-mentioned preset conditions can be set according to requirements. For example, if the sorting result is a result of the order of the business channels to be selected in descending order, the preset condition is to select the business channel to be selected first.
  • Step S12 Obtain service channel information of the optimal service channel, and use the service request information and service channel information as service information of the preset first type of service.
  • the business channel information of the optimal business channel includes service processor service identification information.
  • service processor service identification information refers to the identification information of the service provided by the service processor.
  • the service identification information is 001002.
  • the service channel information of the optimal service channel may further include service processor organization identification information, for example, the bank A organization identification information is 001.
  • step S20 according to the obtained service processor service identification information in the service information and a predetermined mapping relationship between the service processor service identification information and configuration information, a query is performed for the preset first type of service. Configuration information.
  • the configuration information is set in advance according to the gateway interface data processing logic of the service processor.
  • step S20 specifically includes:
  • Step S21 Query a configuration information identifier (for example, configuration information) corresponding to the service processor service identification information in the service information according to a predetermined mapping relationship between the service processor service identification information and the configuration information identifier. ID).
  • a configuration information identifier for example, configuration information
  • the configuration information identifier corresponding to the service processor service identification information is the configuration information identifier corresponding to the preset first type of service.
  • mapping relationship between the service processor service identification information and the configuration information identifier may be stored in a corresponding mapping relationship table.
  • Step S22 Determine the configuration information corresponding to the queried configuration information identifier according to a predetermined mapping relationship between the configuration information identifier and the configuration information, and the configuration information is the preset first type. Configuration information corresponding to the service.
  • mapping relationship between the configuration information identifier and the configuration information may be stored in a corresponding mapping relationship table.
  • steps S21 and S22 may be replaced by the following steps:
  • the corresponding configuration information is the configuration information corresponding to the preset first type of service.
  • the method before step S20, further includes: loading (that is, parsing) all configuration information in the memory, and all configuration information required for subsequent message processing methods of this application can be queried from the memory. In addition, whether the configuration information is updated in real time or periodically is detected, and if so, the configuration information is reloaded in the memory.
  • Step S30 Query the correspondence of the preset first type of service according to the obtained mapping relationship between the service processor service identification information in the service information and the predetermined service processor service identification information and gateway interface information. Gateway interface information.
  • the foregoing gateway interface refers to a gateway interface provided by a service requester.
  • the service requester sets a gateway for each service processor, and sets multiple gateway interfaces according to various services provided by the service processor.
  • the above-mentioned gateway interface information includes a gateway interface identifier (for example, a gateway interface ID).
  • mapping relationship between the business processor service identification information and the gateway interface information may be stored in the same mapping relationship table as the mapping relationship between the business processor service identification information and the configuration information identifier, or the business processor service
  • the mapping relationship between the identification information and the gateway interface information may be stored in different mapping relationship tables with the above-mentioned mapping relationship between the service processor service identification information and the configuration information identifier.
  • steps S20 and S30 may be performed simultaneously or separately, and the order of execution of steps S20 and S30 is not limited in this application.
  • Step S40 Assemble a preset first type service request message according to the service information and the configuration information.
  • the above configuration information defines a preset first type service request message assembly template according to the service processor's gateway interface data processing logic. Therefore, based on the assembly template, the service information is assembled as the message content, so that the service processor can When the first type service request message is received, the preset first type service request message can be directly read.
  • Step S50 Send the assembled first preset type service request message to a service requester gateway interface corresponding to the queried gateway interface information, so that the service requester gateway interface can set the preset The first type of service request message is sent to the corresponding service processor gateway interface.
  • the assembled preset first type service request message is sent to the queried service requester gateway interface, and the service information corresponding to the preset first type service request message is stored and processed (for example, Stored in a database). Then, the service requester gateway interface sends the preset first type service request message to the corresponding service processor gateway interface. After the service processor gateway interface receives the preset first type service request message, Process the preset first type of service.
  • service information of a preset first type service is acquired, and configuration information and gateway interface information corresponding to the first type service are queried according to the service information of the preset first type service, and assembled according to the service information and configuration information.
  • the preset first type service request message is sent, and the assembled preset first type service request message is sent to the corresponding gateway interface.
  • the configuration information is set according to the data processing logic of the gateway interface of the service processor.
  • FIG. 11 is a schematic flowchart of a second embodiment of a message processing method of this application.
  • This embodiment is based on the first embodiment, and the method further includes:
  • Step S60 Receive a preset first-type service return message returned by the service requester gateway interface, and parse the preset first-type service return message according to the queried configuration information.
  • the service processor gateway interface returns a preset first type service return message to the corresponding service requester gateway interface, and the service requester gateway interface returns the preset first type service return message. Since the configuration information includes parsing data of the return message field preset according to the service processor gateway interface data processing logic, the preset first type of service return message can be parsed according to the configuration information.
  • the preset first type of service return message contains an error code
  • the service identification information and the error code parsing information find the corresponding error code parsing information, and according to the search
  • the error code analysis information is used to escape the error code.
  • the method further includes:
  • Update the recorded daily transaction limit data of the payer (deduct the transaction amount from the daily transaction limit data) according to the amount of the transaction amount in the business request information.
  • the method further includes:
  • FIG. 12 is a schematic flowchart of a third embodiment of a message processing method of the present application.
  • This embodiment is based on the first and second embodiments, and the method further includes:
  • step S70 when the preset first type service return message is not received within a preset time period, a preset second type service is started.
  • the preset second type of service includes a query service.
  • the method further includes:
  • query service identification information is generated, and service information corresponding to the preset first type service request message to be queried is obtained, and extracted from the service information.
  • the service processor service identification information and business identification information are used as query business information.
  • step S80 it is only necessary to find out the service information corresponding to the preset first type of service request message to be queried from the storage space.
  • the query service correspondence is obtained.
  • Configuration information
  • the query service is queried according to a mapping relationship among service processor service identification information, query service identification information, and the predetermined service processor service identification information, query service identification information, and configuration information identifier.
  • Corresponding configuration information identifier for example, configuration information ID.
  • the above-mentioned predetermined mapping relationship between the service processor service identification information, query service identification information, and configuration information identifier may be stored in a corresponding mapping relationship table.
  • the configuration information corresponding to the configuration information identifier is the configuration information corresponding to the query service.
  • the mapping relationship between the configuration information identifier and the configuration information may be stored in a corresponding mapping relationship table.
  • the query service is obtained according to the mapping relationship among the service processor service identification information, the query service identification information, and the predetermined service processor service identification information, the query service identification information, and the gateway interface information.
  • Gateway interface information corresponding to the information.
  • mapping relationship between the predetermined service processor service identification information, query service identification information, and gateway interface information, and the predetermined service processor service identification information, query service identification information, and configuration information identifier are determined in advance.
  • the mapping relationship between the three symbols can be stored in the same mapping relationship table, or can be stored in different mapping relationship tables respectively.
  • a query request message is assembled, and the assembled query request message is sent to a service requester gateway interface corresponding to the obtained gateway interface information for The service requester gateway interface sends the query request message to a corresponding service processor gateway interface.
  • the above configuration information defines an assembly template for the query request message according to the gateway interface data processing logic of the service processor, based on the assembly template, the query service information is assembled as the message content, so that the service processor can When the query request message is received, the query request message can be directly read.
  • the configuration information includes parsing data of the query return message field preset according to the service processor gateway interface data processing logic, the query return message can be parsed according to the configuration information to obtain search result.
  • the status of the current processing of the preset first type of service by the service processor can be learned, so that according to the processing The state even adjusts business processing strategies.
  • the present application further proposes a computer-readable storage medium, where the computer-readable storage medium stores a message processing program, and the message processing program can be executed by at least one processor to enable the at least one processing
  • the processor executes the steps of the message processing method in any of the foregoing embodiments.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Marketing (AREA)
  • Theoretical Computer Science (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请公开一种服务器、报文处理方法、程序和计算机可读存储介质。本申请获取预设第一类型业务的业务信息，根据该项预设第一类型业务的业务信息查询该项第一类型业务对应的配置信息及网关接口信息，根据业务信息及配置信息，组装预设第一类型业务请求报文，并将组装后的预设第一类型业务请求报文发送至对应的网关接口。相较于现有技术，本申请在业务处理方的网关接口数据处理逻辑发生变化时，无需修改代码及重启服务器，提高了系统维护效率。

Description

服务器、报文处理方法、程序和计算机可读存储介质
优先权申明
本申请基于巴黎公约申明享有2018年06月29日递交的申请号为CN 201810694255.0、名称为“服务器、报文处理方法和计算机可读存储介质”中国专利申请的优先权，该中国专利申请的整体内容以参考的方式结合在本申请中。
技术领域
本申请涉及通信技术领域，特别涉及一种服务器、报文处理方法、程序和计算机可读存储介质。
背景技术
现有的电子商务平台(即业务请求方)在工作时，需要调用银行、第三方支付公司等金融机构(即业务处理方)进行业务处理，在调用一金融机构进行业务处理之前，该电子商务平台与该金融机构之间需进行网关接口对接，网关接口对接时主要涉及网关接口报文处理方式的定义，现有的定义网关接口报文处理方式的方法是：根据金融机构网关接口的数据处理逻辑在网关接口代理层编写对应的代码以实现网关接口报文的组装、网关接口返回报文的解析以及网关接口的调用等。该方法的缺陷在于，当金融机构接口的数据处理逻辑发生变化时，需要重新修改代码并重启业务请求方服务器。
发明内容
本申请的主要目的是提供一种服务器、报文处理方法、程序和计算机可读存储介质，旨在解决在业务处理方网关接口的数据处理逻辑发生变化时，需重新修改代码并重启业务请求方服务器的问题。
为实现上述目的，本申请提出的一种服务器，所述服务器包括存储器和处理器，所述存储器上存储有报文处理程序，所述报文处理程序被所述处理器执行时实现如下步骤：
获取步骤：在接收到预设第一类型业务请求指令时，获取该项预设第一类型业务的业务信息；
第一查询步骤：根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与配置信息之间的映射关系，查询所述预设第一类型业务对应的配置信息；
第二查询步骤：根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与网关接口信息之间的映射关系，查询所述预设第一类型业务对应的网关接口信息；
组装步骤：根据所述业务信息及所述配置信息，组装预设第一类型业务请求报文；
发送步骤：将组装后的所述预设第一类型业务请求报文发送至查询到的所述网关接口信息对应的业务请求方网关接口，供所述业务请求方网关接口将所述预设第一类型业务请求报文发送至对应的业务处理方网关接口。
此外，为实现上述目的，本申请还提出一种报文处理方法，其特征在于，该方法包括：
获取步骤：在接收到预设第一类型业务请求指令时，获取该项预设第一类型业务的业务信息；
第一查询步骤：根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与配置信息之间的映射关系，查询所述预设第一类型业务对应的配置信息；
第二查询步骤：根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与网关接口信息之间的映射关系，查询所述预设第一类型业务对应的网关接口信息；
组装步骤：根据所述业务信息及所述配置信息，组装预设第一类型业务请求报文；
发送步骤：将组装后的所述预设第一类型业务请求报文发送至查询到的所述网关接口信息对应的业务请求方网关接口，供所述业务请求方网关接口将所述预设第一类型业务请求报文发送至对应的业务处理方网关接口。
此外，为实现上述目的，本申请还提出一种报文处理程序，所述报文处理程序包括：
获取模块，用于在接收到预设第一类型业务请求指令时，获取该项预设第一类型业务的业务信息；
第一查询模块，用于根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与配置信息之间的映射关系，查询所述预设第一类型业务对应的配置信息；
第二查询模块，用于根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与网关接口信息之间的映射关系，查询所述预设第一类型业务对应的网关接口信息；
组装模块，用于根据所述业务信息及所述配置信息，组装预设第一类型业务请求报文；
发送模块，用于将组装后的所述预设第一类型业务请求报文发送至查询到的所述网关接口信息对应的业务请求方网关接口，供所述业务请求方网关接口将所述预设第一类型业务请求报文发送至对应的业务处理方网关接口。
此外，为实现上述目的，本申请还提出一种计算机可读存储介质，所述计算机可读存储介质存储有报文处理程序，所述报文处理程序可被至少一个处理器执行，以使所述至少一个处理器执行如下步骤：
获取步骤：在接收到预设第一类型业务请求指令时，获取该项预设第一类型业务的业务信息；
第一查询步骤：根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与配置信息之间的映射关系，查询所述预设第一类型业务对应的配置信息；
第二查询步骤：根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与网关接口信息之间的映射关系，查询所述预设第一类型业务对应的网关接口信息；
组装步骤：根据所述业务信息及所述配置信息，组装预设第一类型业务请求报文；
发送步骤：将组装后的所述预设第一类型业务请求报文发送至查询到的所述网关接口信息对应的业务请求方网关接口，供所述业务请求方网关接口将所述预设第一类型业务请求报文发送至对应的业务处理方网关接口。
本申请获取预设第一类型业务的业务信息，根据该项预设第一类型业务的业务信息查询该项第一类型业务对应的配置信息及网关接口信息，根据业务信息及配置信息，组装预设第一类型业务请求报文，并将组装后的预设第一类型业务请求报文发送至对应的网关接口。相较于现有技术，本申请在与业务处理方进行接口对接时，根据业务处理方的网关接口数据处理逻辑设置配置信息，当业务请求方需要调用业务处理方进行业务处理时，根据该配置信息组装、解析报文以及调用网关接口。本申请在业务处理方的网关接口数据处理逻辑发生变化时，无需修改代码及重启服务器，仅需对相应的配置信息进行修改，修改后的配置信息一旦保存，则立即生效，在不影响业务请求方系统正常运行的前提下，提高了系统维护效率。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请 的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图示出的结构获得其他的附图。
图1为本申请各个实施例一可选的应用环境示意图；
图2为本申请报文处理程序第一、第二、第三实施例的运行环境示意图；
图3为本申请报文处理程序第一实施例的程序模块图；
图4为图3中第一获取模块的细化程序模块图；
图5为图3中第一查询模块的细化程序模块图；
图6为本申请报文处理程序第二实施例的程序模块图；
图7为本申请接口报文报文处理程序第三实施例的程序模块图
图8为本申请报文处理方法第一实施例的流程示意图；
图9为图8中步骤S10的细化流程示意图；
图10为图8中步骤S20的细化流程示意图；
图11为本申请报文处理方法第二实施例的流程示意图；
图12为本申请报文处理方法第三实施例的流程示意图。
本申请目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
具体实施方式
以下结合附图对本申请的原理和特征进行描述，所举实例只用于解释本申请，并非用于限定本申请的范围。
参阅图1所示，是本申请各个实施例一可选的应用环境示意图。
在本实施例中，本申请可应用于包括，但不仅限于，服务器1、多个客户端2、多个业务请求方网关接口3、多个业务处理方网关接口4、业务处理方服务器5的应用环境中。服务器1分别与多个客户端2及多个业务请求方网关接口通信连接，且各业务请求方网关接口3与对应的业务处理方网关接口4通信连接，多个业务处理方网关接口4与业务处理方服务器5通信连接。
所述客户端2为业务请求方的客户端，该客户端2用于提供用户操作界面，并将用户触发的预设第一类型业务请求指令发送至服务器1处理，且接收服务器1返回的业务处理结果。
所述服务器1为业务请求方的服务器，该服务器1用于运行报文处理程序以实现本申请报文处理方法的步骤。
所述业务请求方网关接口3用于接收服务器1发送的报文，并将该报文发送至对应的业务处理方网关接口4，所述业务请求方网关接口3还用于接收业务处理方网关接口4返回的报文，并将该返回的报文发送至业务请求方网关接口3。
所述业务处理方网关接口4用于接收业务请求方网关接口3发送的报文，并将该报文解析成业务处理方服务器5可读的数据，所述业务处理方网关接口4还用于将业务处理方服务器5发送的数据组装成报文，并发送至对应的业务请求方网关接口3。
所述业务处理方服务器5用于接收业务处理方网关接口4发送的数据，根据该数据进行业务处理，并将业务处理的结果返回值业务处理方网关接口4。
至此，己经详细介绍了本申请各个实施例的应用环境和相关设备的硬件结构和功能。下面，将基于上述应用环境和相关设备，提出本申请的各个实施例。
本申请提出一种报文处理程序。
请参阅图2，是本申请报文处理程序10第一实施例的运行环境示意图。
在本实施例中，报文处理程序10安装并运行于服务器1中。服务器1是一种能够按照事先设定或者存储的指令，自动进行计算和/或信息处理的设备。该服务器1可包括，但 不仅限于，存储器11、处理器12及显示器13。图2仅示出了具有组件11-13的服务器1，但是应理解的是，并不要求实施所有示出的组件，可以替代的实施更多或者更少的组件。
存储器11在一些实施例中可以是服务器1的内部存储单元，例如该服务器1的硬盘或内存。存储器11在另一些实施例中也可以是服务器1的外部存储设备，例如服务器1上配备的插接式硬盘，智能存储卡(Smart Media Card,SMC)，安全数字(Secure Digital,SD)卡，闪存卡(Flash Card)等。进一步地，存储器11还可以既包括服务器1的内部存储单元也包括外部存储设备。存储器11用于存储安装于服务器1的应用软件及各类数据，例如报文处理程序10的程序代码等。存储器11还可以用于暂时地存储已经输出或者将要输出的数据。
处理器12在一些实施例中可以是一中央处理器(Central Processing Unit,CPU)，微处理器或其他数据处理芯片，用于运行存储器11中存储的程序代码或处理数据，例如执行报文处理程序10等。
显示器13在一些实施例中可以是LED显示器、液晶显示器、触控式液晶显示器以及OLED(Organic Light-Emitting Diode，有机发光二极管)触摸器等。显示器13用于显示在服务器1中处理的信息以及用于显示可视化的用户界面。服务器1的部件11-13通过程序总线相互通信。
请参阅图3，是本申请报文处理程序10第一实施例的程序模块图。在本实施例中，报文处理程序10可以被分割成一个或多个模块，一个或者多个模块被存储于存储器11中，并由一个或多个处理器(本实施例为处理器12)所执行，以完成本申请。例如，在图3中，报文处理程序10可以被分割成第一获取模块101、第一查询模块102、第二查询模块103、组装模块104及发送模块105。本申请所称的模块是指能够完成特定功能的一系列计算机程序指令段，比程序更适合于描述报文处理程序10在服务器1中的执行过程，其中：
第一获取模块101，用于在接收到预设第一类型业务请求指令时，获取该项预设第一类型业务的业务信息。
具体地，上述预设第一类型业务请求指令可由用户通过客户端发起，例如，用户需要通过业务处理方支付，当跳转至支付页面时，触发该预设第一类型业务请求。
上述预设第一类型业务包括但不限于：代收业务、代付业务及鉴权业务。
所谓代收业务是指基于持卡人与商户(例如，业务请求方运营的电子商务平台)签订业务委托协议，许可商户根据协议约定，向持卡人指定账户请求并完成指定款项支付的业务，用于实现基于约定用途下的持卡人账户资金向商户账户定向划转。
所谓代付业务是指商户(例如，业务请求方运营的电子商务平台)从自身单位结算账户向持卡人指定银行卡账户进行款项划付的业务，如保险理赔、基金分红、代付货款等。
所谓鉴权业务是指业务处理方验证用户是否拥有访问系统权利的业务。
参照图4，所述第一获取模块101包括选择单元1011、获取单元1012，其中：
选择单元1011，用于提取所述预设第一类型业务请求指令中的业务请求信息，根据所述业务请求信息及预先确定的选择规则在预先确定的多条业务通道中选择一最优业务通道。
具体地，上述业务请求信息包括业务类型、业务标识信息、业务内容信息。
其中，所述业务类型包括代收业务、代付业务及鉴权业务。
所述业务标识信息包括业务编号，例如，订单编号等。
上述业务内容信息基于业务类型的不同有所不同，例如若业务类型为代收业务或者代付业务，则业务内容信息包括支付方信息、收款方信息、交易金额数量等；若业务类型为鉴权业务，则业务内容信息包括用户身份信息、银行卡信息等。
上述业务通道是根据业务处理方提供的服务划分的业务处理链路。例如，银联代收通道、银联代付通道、银联鉴权通道、银行A代收通道、银行A代付通道、银行A鉴权通 道等。
上述业务处理方提供的服务即为该业务处理方可处理的业务。
在除本实施例以外的其他实施例中，还可根据具体的应用场景划分业务通道，本申请对此不作限定。
优选地，本实施例中上述预先确定的选择规则包括：
首先，根据所述业务请求信息，确定支持该项业务的业务通道作为待选业务通道。
一业务通道是否支持该项预设第一类型业务的判断方法如下：
根据所述业务类型，判断该业务通道是否拥有处理该项预设第一类型业务的权限，若否，则判定该业务通道不支持该项预设第一类型业务，若是，则继续判断该业务通道是否开启(例如，一些通道可能故障，则该通道关闭)。
当所述预设第一类型业务为鉴权业务时，若该业务通道开启，则判定该业务通道支持该项预设第一类型业务，若该业务通道未开启，则判定该业务通道不支持该项预设第一类型业务。
当所述预设第一类型业务为代收业务或者代付业务时，根据所述业务内容信息中的交易金额数量，判断该开启的业务通道是否满足预设的限额条件(例如，判断该开启的业务通道当日已处理交易金额总量加上所述业务内容信息中的交易金额数量得到的新的交易金额总量是否未超过预设阈值)，若满足，则判定该业务通道支持该项预设第一类型业务的业务通道，若不满足，则判定该业务通道不支持该项预设第一类型业务。
接着，基于各所述待选业务通道的排序参数对所述待选业务通道进行排序处理，并输出排序结果。
上述排序参数包括服务费率、业务时效(即业务处理方完成代收业务或者代付业务所需时间)、优先级等。可根据需求对该排序参数进行设定，并不限于上述列举的内容。
上述基于各所述待选业务通道的排序参数对所述待选业务通道进行排序处理的步骤，具体包括：
基于优先级由高到低的顺序，将所述待选业务通道进行排序。
将相同优先级的待选业务通道基于服务费率由低到高的顺序进行排序。
将优先级及支付费率均相同的待选业务通道基于业务时效由短到长的顺序进行排序，以得到待选业务通道由优到劣的排序结果。
上述的服务费率是指业务处理方向业务请求方收取的服务费率。且若业务类型为鉴权业务，则业务时效不作为排序参数。
最后，基于所述排序结果，将满足预设条件的待选业务通道作为最优业务通道。
上述预设条件可根据需要设置，例如，若所述排序结果为待选业务通道由优到劣的顺序排序的结果，则该预设条件为选择排序第一位的待选业务通道。
获取单元1012，用于获取所述最优业务通道的业务通道信息，并将所述业务请求信息及业务通道信息作为所述预设第一类型业务的业务信息。
优选地，本实施例中，上述最优业务通道的业务通道信息包括业务处理方服务标识信息，所谓业务处理方服务标识信息是指业务处理方提供的服务的标识信息，例如，银行A代收服务标识信息为001002。
在除本实施例以外的其他实施例中，上述最优业务通道的业务通道信息还可包括业务处理方机构标识信息，例如，银行A机构标识信息为001。
第一查询模块102，用于根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与配置信息之间的映射关系，查询所述预设第一类型业务对应的配置信息。
具体地，上述配置信息是预先根据业务处理方的网关接口数据处理逻辑设置的。
参照图5，优选地，本实施例中，上述第一查询模块102包括第一查询单元1021、第 二查询单元1022，其中：
第一查询单元1021，用于根据预先确定的所述业务处理方服务标识信息与配置信息标识符之间的映射关系，查询所述业务信息中的业务处理方服务标识信息对应的配置信息标识符(例如，配置信息ID)。
所述业务处理方服务标识信息对应的配置信息标识符即为所述预设第一类型业务对应的配置信息标识符。
上述业务处理方服务标识信息与配置信息标识符之间的映射关系可存储于对应的映射关系表中。
第二查询单元1022，用于根据预先确定的所述配置信息标识符与配置信息之间的映射关系，确定查询到的所述配置信息标识符对应的配置信息，所述配置信息即为所述预设第一类型业务对应的配置信息。
具体地，所述配置信息标识符与配置信息之间的映射关系可存储于对应的映射关系表中。
此外，参照图在除本实施例以外的其他实施例中，上述第一查询单元1021、第二查询单元1022可由第三查询单元(图中未示出)替换，所述第三查询单元用于：
根据获取的业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息、配置信息标识符及配置信息三者之间的映射关系，查询所述业务处理方服务标识信息对应的配置信息，即得到所述预设第一类型业务对应的配置信息。
优选地，本实施例中，报文处理程序10被处理器12执行时，在所述根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与配置信息之间的映射关系，查询所述预设第一类型业务对应的配置信息的步骤之前，还实现如下步骤：在内存中加载(即解析)所有配置信息，后续本申请报文处理所需的所有配置信息均可从内存中查询。此外，实时或定时侦测所述配置信息是否有更新，若是，则在内存中重新加载所述配置信息。
第二查询模块103，用于根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与网关接口信息之间的映射关系，查询所述预设第一类型业务对应的网关接口信息。
具体地，上述网关接口是指业务请求方设置的网关接口，通常情况下，业务请求方为每一个业务处理方设置一个网关，且根据该业务处理方提供的各项服务设置多个网关接口。
上述网关接口信息包括网关接口标识符(例如，网关接口ID)。
上述业务处理方服务标识信息与网关接口信息之间的映射关系可与上述业务处理方服务标识信息与配置信息标识符之间的映射关系存储于同一映射关系表中，或者，上述业务处理方服务标识信息与网关接口信息之间的映射关系可与上述业务处理方服务标识信息与配置信息标识符之间的映射关系分别存储于不同的映射关系表中。
组装模块104，用于根据所述业务信息及所述配置信息，组装预设第一类型业务请求报文。
上述配置信息根据业务处理方的网关接口数据处理逻辑定义了预设第一类型业务请求报文的组装模板，因此，基于该组装模板，将业务信息作为报文内容进行组装，以便业务处理方在接收到该第一类型业务请求报文时能直接读取该预设第一类型业务请求报文。
发送模块105，用于将组装后的所述预设第一类型业务请求报文发送至查询到的所述网关接口信息对应的业务请求方网关接口，以供所述业务请求方网关接口将所述预设第一类型业务请求报文发送至对应的业务处理方网关接口。
具体地，首先，将组装后的预设第一类型业务请求报文发送至查询到的业务请求方网关接口，并将预设第一类型业务请求报文对应的业务信息进行存储处理(例如，存储于数据库中)。接着，由业务请求方网关接口将所述预设第一类型业务请求报文发送至对应的 业务处理方网关接口，业务处理方网关接口在接收到该预设第一类型业务请求报文后，对该项预设第一类型业务进行处理。
本实施例获取预设第一类型业务的业务信息，根据该项预设第一类型业务的业务信息查询该项第一类型业务对应的配置信息及网关接口信息，根据业务信息及配置信息，组装预设第一类型业务请求报文，并将组装后的预设第一类型业务请求报文发送至对应的网关接口。相较于现有技术，本实施例在与业务处理方进行接口对接时，根据业务处理方的网关接口数据处理逻辑设置配置信息，当业务请求方需要调用业务处理方进行业务处理时，根据该配置信息组装、解析报文以及调用网关接口。本实施例在业务处理方的网关接口数据处理逻辑发生变化时，无需修改代码及重启服务器，仅需对相应的配置信息进行修改，修改后的配置信息一旦保存，则立即生效，在不影响业务请求方系统正常运行的前提下，提高了系统维护效率。
如图6所示，图6为本申请报文处理程序10第二实施例的程序模块图。
本实施例在第一实施例的基础上，该程序还包括接收模块106，接收模块106用于接收所述业务请求方网关接口返回的预设第一类型业务返回报文，且根据查询到的所述配置信息，解析所述预设第一类型业务返回报文。
具体地，业务处理方网关接口返回预设第一类型业务返回报文至对应的业务请求方网关接口，业务请求方网关接口返回该预设第一类型业务返回报文。由于所述配置信息中包含有根据服务处理方网关接口数据处理逻辑预先设置的返回报文字段的解析数据，因此，根据该配置信息，即可对预设第一类型业务返回报文进行解析。
若该预设第一类型业务返回报文中包含错误码，则根据预先确定的业务处理方式服务标识信息与错误码解析信息之间的映射关系，查找对应的错误码解析信息，并根据该查找到的错误码解析信息对所述错误码进行转义。
优选地，本实施例中，当所述预设第一类型业务的业务类型为代收业务或者代付业务时，报文处理程序10还包括更新模块(图中未示出)，所述更新模块用于，根据所述业务请求信息中的交易金额数量，更新记录的支付方的每日交易限额数据(从每日交易限额数据中扣减交易金额)。
所述更新模块还用于，当根据解析的预设第一类型业务返回报文确定代收业务失败或者代付业务失败时，更新记录的支付方的每日交易限额数据(从每日交易限额数据中回滚扣减的交易金额)。
如图7所示，图7为本申请报文处理程序10第三实施例的程序模块图。
本实施例在第一、第二实施例的基础上，该程序还包括启动模块107、查询业务模块108，其中：
启动模块107，用于当在预设时长内未接收到所述预设第一类型业务返回报文时，启动预设第二类型业务。
具体地，所述预设第二类型业务包括查询业务。
优选地，本实施例中该程序还包括查询业务模块108，查询业务模块108用于：
首先，当启动的所述预设第二类型业务为查询业务时，生成查询业务标识信息，并获取待查询预设第一类型业务请求报文对应的业务信息，并从所述业务信息中提取业务处理方服务标识信息及业务标识信息作为查询业务信息。
具体地，由于在待查询预设第一类型业务请求报文发送至服务请求方网关接口时，以将该待查询预设第一类型业务请求报文对应的业务信息进行存储处理，因此，仅需从存储空间中查找出该待查询预设第一类型业务请求报文对应的业务信息即可。
然后，根据所述业务处理方服务标识信息、查询业务标识信息及预先确定的所述业务处理方服务标识信息、查询业务标识信息及配置信息三者之间的映射关系，获取所述查询业务对应的配置信息。
具体地，根据业务处理方服务标识信息、查询业务标识信息及预先确定的所述业务处理方服务标识信息、查询业务标识信息及配置信息标识符三者之间的映射关系，查询所述查询业务对应的配置信息标识符(例如，配置信息ID)。具体地，上述预先确定的所述业务处理方服务标识信息、查询业务标识信息及配置信息标识符三者之间的映射关系可存储于对应的映射关系表中。
根据查询到的所述配置信息标识符及预先确定的所述配置信息标识符与配置信息之间的映射关系，查询所述配置信息标识符对应的配置信息。查询得到的配置信息标识符对应的配置信息即为所述查询业务对应的配置信息。所述配置信息标识符与配置信息之间的映射关系可存储于对应的映射关系表中。
接着，根据所述业务处理方服务标识信息、查询业务标识信息及预先确定的所述业务处理方服务标识信息、查询业务标识信息及网关接口信息三者之间的映射关系，获取所述查询业务信息对应的网关接口信息。
上述预先确定的所述业务处理方服务标识信息、查询业务标识信息及网关接口信息三者之间的映射关系与上述预先确定的所述业务处理方服务标识信息、查询业务标识信息及配置信息标识符三者之间的映射关系可存储于同一映射关系表中，也可分别存储于不同的映射关系表中。
接着，根据所述查询业务信息及所述配置信息，组装查询请求报文，并将组装后的所述查询请求报文发送至获取的所述网关接口信息对应的业务请求方网关接口，供所述业务请求方网关接口将所述查询请求报文发送至对应的业务处理方网关接口。
具体地，由于上述配置信息根据业务处理方的网关接口数据处理逻辑定义了查询请求报文的组装模板，因此，基于该组装模板，将查询业务信息作为报文内容进行组装，以便业务处理方在接收到该查询请求报文时能直接读取该查询请求报文。
最后，接收所述业务请求方网关接口返回的查询返回报文，且根据所述配置信息，解析所述查询返回报文，以获得查询结果。
具体地，由于该配置信息中包含有根据服务处理方网关接口数据处理逻辑预先设置的查询返回报文字段的解析数据，因此，根据该配置信息，即可对查询返回报文进行解析，以获得查询结果。
本实施例当在预设时长内未接收到所述预设第一类型业务返回报文时，通过启动查询业务，可获知业务处理方当前处理预设第一类型业务的状态，从而根据该处理状态即使调整业务处理策略。
此外，本申请提出一种报文处理方法。
如图8所示，图8为本申请报文处理方法第一实施例的流程示意图。
本实施例中，该方法包括：
步骤S10，在接收到预设第一类型业务请求指令时，获取该项预设第一类型业务的业务信息。
具体地，上述预设第一类型业务请求指令可由用户通过客户端发起，例如，用户需要通过业务处理方支付，当跳转至支付页面时，触发该预设第一类型业务请求。
上述预设第一类型业务包括但不限于：代收业务、代付业务及鉴权业务。
所谓代收业务是指基于持卡人与商户(例如，业务请求方运营的电子商务平台)签订业务委托协议，许可商户根据协议约定，向持卡人指定账户请求并完成指定款项支付的业务，用于实现基于约定用途下的持卡人账户资金向商户账户定向划转。
所谓代付业务是指商户(例如，业务请求方运营的电子商务平台)从自身单位结算账户向持卡人指定银行卡账户进行款项划付的业务，如保险理赔、基金分红、代付货款等。
所谓鉴权业务是指业务处理方验证用户是否拥有访问系统权利的业务。
参照图9，所述步骤S10具体包括：
步骤S11，提取所述预设第一类型业务请求指令中的业务请求信息，根据所述业务请求信息及预先确定的选择规则在预先确定的多条业务通道中选择一最优业务通道。
具体地，上述业务请求信息包括业务类型、业务标识信息、业务内容信息。
其中，所述业务类型包括代收业务、代付业务及鉴权业务。
所述业务标识信息包括业务编号，例如，订单编号等。
上述业务内容信息基于业务类型不同有所不同，例如若业务类型为代收业务或者代付业务，则业务内容信息包括支付方信息、收款方信息、交易金额数量等；若业务类型为鉴权业务，则业务内容信息包括用户身份信息、银行卡信息等。
上述业务通道是根据业务处理方提供的服务划分的业务处理链路。例如，银联代收通道、银联代付通道、银联鉴权通道、银行A代收通道、银行A代付通道、银行A鉴权通道等。
上述业务处理方提供的服务即为该业务处理方可处理的业务。
在除本实施例以外的其他实施例中，还可根据具体的应用场景划分业务通道，本申请对此不作限定。
优选地，本实施例中上述预先确定的选择规则包括：
首先，根据所述业务请求信息，确定支持该项业务的业务通道作为待选业务通道。一业务通道是否支持该项预设第一类型业务的判断方法如下：
根据所述业务类型，判断该业务通道是否拥有处理该项预设第一类型业务的权限，若否，则判定该业务通道不支持该项预设第一类型业务，若是，则继续判断该业务通道是否开启(例如，一些通道可能故障，则该通道关闭)。
当所述预设第一类型业务为鉴权业务时，若该业务通道开启，则判定该业务通道支持该项预设第一类型业务，若该业务通道未开启，则判定该业务通道不支持该项预设第一类型业务。
当所述预设第一类型业务为代收业务或者代付业务时，根据所述业务内容信息中的交易金额数量，判断该开启的业务通道是否满足预设的限额条件(例如，判断该开启的业务通道当日已处理交易金额总量加上所述业务内容信息中的交易金额数量得到的新的交易金额总量是否未超过预设阈值)，若满足，则判定该业务通道支持该项预设第一类型业务的业务通道，若不满足，则判定该业务通道不支持该项预设第一类型业务。
接着，基于各所述待选业务通道的排序参数对所述待选业务通道进行排序处理，并输出排序结果。
上述排序参数包括服务费率、业务时效(即业务处理方完成代收业务或者代付业务所需时间)、优先级等。可根据需求对该排序参数进行设定，并不限于上述列举的内容。
上述基于各所述待选业务通道的排序参数对所述待选业务通道进行排序处理的步骤，具体包括：
基于优先级由高到低的顺序，将所述待选业务通道进行排序。
将相同优先级的待选业务通道基于服务费率由低到高的顺序进行排序。
将优先级及支付费率均相同的待选业务通道基于业务时效由短到长的顺序进行排序，以得到待选业务通道由优到劣的排序结果。
上述的服务费率是指业务处理方向业务请求方收取的服务费率。且若业务类型为鉴权业务，则业务时效不作为排序参数。
最后，基于所述排序结果，将满足预设条件的待选业务通道作为最优业务通道。
上述预设条件可根据需要设置，例如，若所述排序结果为待选业务通道由优到劣的顺序排序的结果，则该预设条件为选择排序第一位的待选业务通道。
步骤S12，获取所述最优业务通道的业务通道信息，并将所述业务请求信息及业务通道信息作为所述预设第一类型业务的业务信息。
优选地，本实施例中，上述最优业务通道的业务通道信息包括业务处理方服务标识信息，所谓业务处理方服务标识信息是指业务处理方提供的服务的标识信息，例如，银行A代收服务标识信息为001002。
在除本实施例以外的其他实施例中，上述最优业务通道的业务通道信息还可包括业务处理方机构标识信息，例如，银行A机构标识信息为001。
步骤S20，根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与配置信息之间的映射关系，查询所述预设第一类型业务对应的配置信息。
具体地，上述配置信息是预先根据业务处理方的网关接口数据处理逻辑设置的。
参照图10，优选地，本实施例中，上述步骤S20具体包括：
步骤S21，根据预先确定的所述业务处理方服务标识信息与配置信息标识符之间的映射关系，查询所述业务信息中的业务处理方服务标识信息对应的配置信息标识符(例如，配置信息ID)。
所述业务处理方服务标识信息对应的配置信息标识符即为所述预设第一类型业务对应的配置信息标识符。
上述业务处理方服务标识信息与配置信息标识符之间的映射关系可存储于对应的映射关系表中。
步骤S22，根据预先确定的所述配置信息标识符与配置信息之间的映射关系，确定查询到的所述配置信息标识符对应的配置信息，所述配置信息即为所述预设第一类型业务对应的配置信息。
具体地，所述配置信息标识符与配置信息之间的映射关系可存储于对应的映射关系表中。
此外，在除本实施例以外的其他实施例中，上述步骤S21、S22可由如下步骤替换：
根据获取的业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息、配置信息标识符及配置信息三者之间的映射关系，查询所述业务处理方服务标识信息对应的配置信息，即得到所述预设第一类型业务对应的配置信息。
优选地，本实施例中，在步骤S20之前，该方法还包括：在内存中加载(即解析)所有配置信息，后续本申请报文处理方法所需的所有配置信息均可从内存中查询。此外，实时或定时侦测所述配置信息是否有更新，若是，则在内存中重新加载所述配置信息。
步骤S30，根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与网关接口信息之间的映射关系，查询所述预设第一类型业务对应的网关接口信息。
具体地，上述网关接口是指业务请求方设置的网关接口，通常情况下，业务请求方为每一个业务处理方设置一个网关，且根据该业务处理方提供的各项服务设置多个网关接口。
上述网关接口信息包括网关接口标识符(例如，网关接口ID)。
上述业务处理方服务标识信息与网关接口信息之间的映射关系可与上述业务处理方服务标识信息与配置信息标识符之间的映射关系存储于同一映射关系表中，或者，上述业务处理方服务标识信息与网关接口信息之间的映射关系可与上述业务处理方服务标识信息与配置信息标识符之间的映射关系分别存储于不同的映射关系表中。
上述步骤S20与步骤S30可同时执行也可分别执行，且本申请对步骤S20及步骤S30的执行先后顺序不作限定。
步骤S40，根据所述业务信息及所述配置信息，组装预设第一类型业务请求报文。
上述配置信息根据业务处理方的网关接口数据处理逻辑定义了预设第一类型业务请求报文的组装模板，因此，基于该组装模板，将业务信息作为报文内容进行组装，以便业务处理方在接收到该第一类型业务请求报文时能直接读取该预设第一类型业务请求报文。
步骤S50，将组装后的所述预设第一类型业务请求报文发送至查询到的所述网关接口信息对应的业务请求方网关接口，以供所述业务请求方网关接口将所述预设第一类型业务请求报文发送至对应的业务处理方网关接口。
具体地，首先，将组装后的预设第一类型业务请求报文发送至查询到的业务请求方网关接口，并将预设第一类型业务请求报文对应的业务信息进行存储处理(例如，存储于数据库中)。接着，由业务请求方网关接口将所述预设第一类型业务请求报文发送至对应的业务处理方网关接口，业务处理方网关接口在接收到该预设第一类型业务请求报文后，对该项预设第一类型业务进行处理。
本实施例获取预设第一类型业务的业务信息，根据该项预设第一类型业务的业务信息查询该项第一类型业务对应的配置信息及网关接口信息，根据业务信息及配置信息，组装预设第一类型业务请求报文，并将组装后的预设第一类型业务请求报文发送至对应的网关接口。相较于现有技术，本实施例在与业务处理方进行接口对接时，根据业务处理方的网关接口数据处理逻辑设置配置信息，当业务请求方需要调用业务处理方进行业务处理时，根据该配置信息组装、解析报文以及调用网关接口。本实施例在业务处理方的网关接口数据处理逻辑发生变化时，无需修改代码及重启服务器，仅需对相应的配置信息进行修改，修改后的配置信息一旦保存，则立即生效，在不影响业务请求方系统正常运行的前提下，提高了系统维护效率。
如图11所示，图11为本申请报文处理方法第二实施例的流程示意图。
本实施例在第一实施例的基础上，该方法还包括：
步骤S60，接收所述业务请求方网关接口返回的预设第一类型业务返回报文，且根据查询到的所述配置信息，解析所述预设第一类型业务返回报文。
具体地，业务处理方网关接口返回预设第一类型业务返回报文至对应的业务请求方网关接口，业务请求方网关接口返回该预设第一类型业务返回报文。由于所述配置信息中包含有根据服务处理方网关接口数据处理逻辑预先设置的返回报文字段的解析数据，因此，根据该配置信息，即可对预设第一类型业务返回报文进行解析。
若该预设第一类型业务返回报文中包含错误码，则根据预先确定的业务处理方式服务标识信息与错误码解析信息之间的映射关系，查找对应的错误码解析信息，并根据该查找到的错误码解析信息对所述错误码进行转义。
优选地，本实施例中，当所述预设第一类型业务的业务类型为代收业务或者代付业务时，在步骤S50之前，还包括：
根据所述业务请求信息中的交易金额数量，更新记录的支付方的每日交易限额数据(从每日交易限额数据中扣减交易金额)。
当所述预设第一类型业务的业务类型为代收业务或者代付业务时，在步骤S60之后，还包括：
若根据解析的预设第一类型业务返回报文，确定代收业务失败或者代付业务失败，则更新记录的支付方的每日交易限额数据(从每日交易限额数据中回滚扣减的交易金额)。
如图12所示，图12为本申请报文处理方法第三实施例的流程示意图。
本实施例在第一、第二实施例的基础上，该方法还包括：
步骤S70，当在预设时长内未接收到所述预设第一类型业务返回报文时，启动预设第二类型业务。
具体地，所述预设第二类型业务包括查询业务。
优选地，本实施例中，在步骤S70之后，该方法还包括：
首先，当启动的所述预设第二类型业务为查询业务时，生成查询业务标识信息，并获取待查询预设第一类型业务请求报文对应的业务信息，并从所述业务信息中提取业务处理方服务标识信息及业务标识信息作为查询业务信息。
具体地，由于在待查询预设第一类型业务请求报文发送至服务请求方网关接口时，以将该待查询预设第一类型业务请求报文对应的业务信息进行存储处理，因此，在步骤S80中，仅需从存储空间中查找出该待查询预设第一类型业务请求报文对应的业务信息即可。
然后，根据所述业务处理方服务标识信息、查询业务标识信息及预先确定的所述业务处理方服务标识信息、查询业务标识信息及配置信息三者之间的映射关系，获取所述查询业务对应的配置信息。
具体地，根据业务处理方服务标识信息、查询业务标识信息及预先确定的所述业务处理方服务标识信息、查询业务标识信息及配置信息标识符三者之间的映射关系，查询所述查询业务对应的配置信息标识符(例如，配置信息ID)。具体地，上述预先确定的所述业务处理方服务标识信息、查询业务标识信息及配置信息标识符三者之间的映射关系可存储于对应的映射关系表中。
根据查询到的所述配置信息标识符及预先确定的所述配置信息标识符与配置信息之间的映射关系，查询所述配置信息标识符对应的配置信息。查询得到的配置信息标识符对应的配置信息即为所述查询业务对应的配置信息。所述配置信息标识符与配置信息之间的映射关系可存储于对应的映射关系表中。
接着，根据所述业务处理方服务标识信息、查询业务标识信息及预先确定的所述业务处理方服务标识信息、查询业务标识信息及网关接口信息三者之间的映射关系，获取所述查询业务信息对应的网关接口信息。
上述预先确定的所述业务处理方服务标识信息、查询业务标识信息及网关接口信息三者之间的映射关系与上述预先确定的所述业务处理方服务标识信息、查询业务标识信息及配置信息标识符三者之间的映射关系可存储于同一映射关系表中，也可分别存储于不同的映射关系表中。
接着，根据所述查询业务信息及所述配置信息，组装查询请求报文，并将组装后的所述查询请求报文发送至获取的所述网关接口信息对应的业务请求方网关接口，供所述业务请求方网关接口将所述查询请求报文发送至对应的业务处理方网关接口。
具体地，由于上述配置信息根据业务处理方的网关接口数据处理逻辑定义了查询请求报文的组装模板，因此，基于该组装模板，将查询业务信息作为报文内容进行组装，以便业务处理方在接收到该查询请求报文时能直接读取该查询请求报文。
最后，接收所述业务请求方网关接口返回的查询返回报文，且根据所述配置信息，解析所述查询返回报文，以获得查询结果。
具体地，由于该配置信息中包含有根据服务处理方网关接口数据处理逻辑预先设置的查询返回报文字段的解析数据，因此，根据该配置信息，即可对查询返回报文进行解析，以获得查询结果。
本实施例当在预设时长内未接收到所述预设第一类型业务返回报文时，通过启动查询业务，可获知业务处理方当前处理预设第一类型业务的状态，从而根据该处理状态即使调整业务处理策略。
进一步地，本申请还提出一种计算机可读存储介质，所述计算机可读存储介质存储有报文处理程序，所述报文处理程序可被至少一个处理器执行，以使所述至少一个处理器执行上述任一实施例中的报文处理方法的步骤。
以上所述仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是在本申请的发明构思下，利用本申请说明书及附图内容所作的等效结构变换，或直接/间接运用在其他相关的技术领域均包括在本申请的专利保护范围内。

Claims (20)

  1. 一种服务器，所述服务器包括存储器和处理器，其特征在于，所述存储器上存储有报文处理程序，所述报文处理程序被所述处理器执行时实现如下步骤：
    获取步骤：在接收到预设第一类型业务请求指令时，获取该项预设第一类型业务的业务信息；
    第一查询步骤：根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与配置信息之间的映射关系，查询所述预设第一类型业务对应的配置信息；
    第二查询步骤：根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与网关接口信息之间的映射关系，查询所述预设第一类型业务对应的网关接口信息；
    组装步骤：根据所述业务信息及所述配置信息，组装预设第一类型业务请求报文；
    发送步骤：将组装后的所述预设第一类型业务请求报文发送至查询到的所述网关接口信息对应的业务请求方网关接口，供所述业务请求方网关接口将所述预设第一类型业务请求报文发送至对应的业务处理方网关接口。
  2. 如权利要求1所述的服务器，其特征在于，所述第一查询步骤包括：
    根据预先确定的所述业务处理方服务标识信息与配置信息标识符之间的映射关系，查询所述业务信息中的业务处理方服务标识信息对应的配置信息标识符；
    根据预先确定的所述配置信息标识符与配置信息之间的映射关系，确定查询到的所述配置信息标识符对应的配置信息，所述配置信息即为所述预设第一类型业务对应的配置信息。
  3. 如权利要求1所述的服务器，其特征在于，所述获取步骤包括：
    提取所述预设第一类型业务请求指令中的业务请求信息，根据所述业务请求信息及预先确定的选择规则在预先确定的多条业务通道中选择一最优业务通道；
    获取所述最优业务通道的业务通道信息，并将所述业务请求信息及业务通道信息作为所述预设第一类型业务的业务信息。
  4. 如权利要求1至3中任一项所述的服务器，其特征在于，所述处理器执行所述报文处理程序，在所述发送步骤之后，还实现以下步骤：
    接收所述业务请求方网关接口返回的预设第一类型业务返回报文，且根据查询到的所述配置信息，解析所述预设第一类型业务返回报文。
  5. 如权利要求1至3中任一项所述的服务器，其特征在于，所述处理器执行所述报文处理程序，在所述发送步骤之后，还实现以下步骤：
    当在预设时长内未接收到所述预设第一类型业务返回报文时，启动预设第二类型业务，所述预设第二类型业务包括查询业务；
    当启动的所述预设第二类型业务为查询业务时，生成查询业务标识信息，并获取待查询预设第一类型业务请求报文对应的业务信息，并从所述业务信息中提取业务处理方服务标识信息及业务标识信息作为查询业务信息；
    根据所述业务处理方服务标识信息、查询业务标识信息及预先确定的所述业务处理方服务标识信息、查询业务标识信息及配置信息三者之间的映射关系，获取所述查询业务对应的配置信息；
    根据所述业务处理方服务标识信息、查询业务标识信息及预先确定的所述业务处理方服务标识信息、查询业务标识信息及网关接口信息三者之间的映射关系，获取所述查询业务信息对应的网关接口信息；
    根据所述查询业务信息及所述配置信息，组装查询请求报文，并将组装后的所述查询请求报文发送至获取的所述网关接口信息对应的业务请求方网关接口，供所述业务请求方 网关接口将所述查询请求报文发送至对应的业务处理方网关接口；
    接收所述业务请求方网关接口返回的查询返回报文，且根据所述配置信息，解析所述查询返回报文，以获得查询结果。
  6. 一种报文处理方法，其特征在于，该方法包括：
    获取步骤：在接收到预设第一类型业务请求指令时，获取该项预设第一类型业务的业务信息；
    第一查询步骤：根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与配置信息之间的映射关系，查询所述预设第一类型业务对应的配置信息；
    第二查询步骤：根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与网关接口信息之间的映射关系，查询所述预设第一类型业务对应的网关接口信息；
    组装步骤：根据所述业务信息及所述配置信息，组装预设第一类型业务请求报文；
    发送步骤：将组装后的所述预设第一类型业务请求报文发送至查询到的所述网关接口信息对应的业务请求方网关接口，供所述业务请求方网关接口将所述预设第一类型业务请求报文发送至对应的业务处理方网关接口。
  7. 如权利要求6所述的报文处理方法，其特征在于，所述第一查询步骤包括：
    根据预先确定的所述业务处理方服务标识信息与配置信息标识符之间的映射关系，查询所述业务信息中的业务处理方服务标识信息对应的配置信息标识符；
    根据预先确定的所述配置信息标识符与配置信息之间的映射关系，确定查询到的所述配置信息标识符对应的配置信息，所述配置信息即为所述预设第一类型业务对应的配置信息。
  8. 如权利要求6所述的报文处理方法，其特征在于，所述获取步骤包括：
    提取所述预设第一类型业务请求指令中的业务请求信息，根据所述业务请求信息及预先确定的选择规则在预先确定的多条业务通道中选择一最优业务通道；
    获取所述最优业务通道的业务通道信息，并将所述业务请求信息及业务通道信息作为所述预设第一类型业务的业务信息。
  9. 如权利要求6至8中任一项所述的报文处理方法，其特征在于，在所述发送步骤之后，该方法还包括：
    接收所述业务请求方网关接口返回的预设第一类型业务返回报文，且根据查询到的所述配置信息，解析所述预设第一类型业务返回报文。
  10. 如权利要求6至8中任一项所述的报文处理方法，其特征在于，在所述发送步骤之后，该方法还包括：
    当在预设时长内未接收到所述预设第一类型业务返回报文时，启动预设第二类型业务，所述预设第二类型业务包括查询业务；
    当启动的所述预设第二类型业务为查询业务时，生成查询业务标识信息，并获取待查询预设第一类型业务请求报文对应的业务信息，并从所述业务信息中提取业务处理方服务标识信息及业务标识信息作为查询业务信息；
    根据所述业务处理方服务标识信息、查询业务标识信息及预先确定的所述业务处理方服务标识信息、查询业务标识信息及配置信息三者之间的映射关系，获取所述查询业务对应的配置信息；
    根据所述业务处理方服务标识信息、查询业务标识信息及预先确定的所述业务处理方服务标识信息、查询业务标识信息及网关接口信息三者之间的映射关系，获取所述查询业务信息对应的网关接口信息；
    根据所述查询业务信息及所述配置信息，组装查询请求报文，并将组装后的所述查询 请求报文发送至获取的所述网关接口信息对应的业务请求方网关接口，供所述业务请求方网关接口将所述查询请求报文发送至对应的业务处理方网关接口；
    接收所述业务请求方网关接口返回的查询返回报文，且根据所述配置信息，解析所述查询返回报文，以获得查询结果。
  11. 一种报文处理程序，其特征在于，所述报文处理程序包括：
    获取模块，用于在接收到预设第一类型业务请求指令时，获取该项预设第一类型业务的业务信息；
    第一查询模块，用于根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与配置信息之间的映射关系，查询所述预设第一类型业务对应的配置信息；
    第二查询模块，用于根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与网关接口信息之间的映射关系，查询所述预设第一类型业务对应的网关接口信息；
    组装模块，用于根据所述业务信息及所述配置信息，组装预设第一类型业务请求报文；
    发送模块，用于将组装后的所述预设第一类型业务请求报文发送至查询到的所述网关接口信息对应的业务请求方网关接口，供所述业务请求方网关接口将所述预设第一类型业务请求报文发送至对应的业务处理方网关接口。
  12. 如权利要求11所述的报文处理程序，其特征在于，所述第一查询模块包括：
    第一查询单元，用于根据预先确定的所述业务处理方服务标识信息与配置信息标识符之间的映射关系，查询所述业务信息中的业务处理方服务标识信息对应的配置信息标识符；
    第二查询单元，用于根据预先确定的所述配置信息标识符与配置信息之间的映射关系，确定查询到的所述配置信息标识符对应的配置信息，所述配置信息即为所述预设第一类型业务对应的配置信息。
  13. 如权利要求11所述的报文处理程序，其特征在于，所述获取模块包括：
    选择单元，用于提取所述预设第一类型业务请求指令中的业务请求信息，根据所述业务请求信息及预先确定的选择规则在预先确定的多条业务通道中选择一最优业务通道；
    获取单元，用于获取所述最优业务通道的业务通道信息，并将所述业务请求信息及业务通道信息作为所述预设第一类型业务的业务信息。
  14. 如权利要求11至13中任一项所述的报文处理程序，其特征在于，所述报文处理程序还包括：
    接收模块，用于接收所述业务请求方网关接口返回的预设第一类型业务返回报文，且根据查询到的所述配置信息，解析所述预设第一类型业务返回报文。
  15. 如权利要求11至13中任一项所述的报文处理程序，其特征在于，所述报文处理程序还包括：
    启动模块，用于当在预设时长内未接收到所述预设第一类型业务返回报文时，启动预设第二类型业务，所述预设第二类型业务包括查询业务；
    查询业务模块，用于当启动的所述预设第二类型业务为查询业务时，生成查询业务标识信息，并获取待查询预设第一类型业务请求报文对应的业务信息，并从所述业务信息中提取业务处理方服务标识信息及业务标识信息作为查询业务信息；根据所述业务处理方服务标识信息、查询业务标识信息及预先确定的所述业务处理方服务标识信息、查询业务标识信息及配置信息三者之间的映射关系，获取所述查询业务对应的配置信息；根据所述业务处理方服务标识信息、查询业务标识信息及预先确定的所述业务处理方服务标识信息、查询业务标识信息及网关接口信息三者之间的映射关系，获取所述查询业务信息对应的网关接口信息；根据所述查询业务信息及所述配置信息，组装查询请求报文，并将组装后的所述查询请求报文发送至获取的所述网关接口信息对应的业务请求方网关接口，供所述业 务请求方网关接口将所述查询请求报文发送至对应的业务处理方网关接口；接收所述业务请求方网关接口返回的查询返回报文，且根据所述配置信息，解析所述查询返回报文，以获得查询结果。
  16. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有报文处理程序，所述报文处理程序可被至少一个处理器执行，以使所述至少一个处理器执行如下步骤：
    获取步骤：在接收到预设第一类型业务请求指令时，获取该项预设第一类型业务的业务信息；
    第一查询步骤：根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与配置信息之间的映射关系，查询所述预设第一类型业务对应的配置信息；
    第二查询步骤：根据获取的所述业务信息中的业务处理方服务标识信息及预先确定的所述业务处理方服务标识信息与网关接口信息之间的映射关系，查询所述预设第一类型业务对应的网关接口信息；
    组装步骤：根据所述业务信息及所述配置信息，组装预设第一类型业务请求报文；
    发送步骤：将组装后的所述预设第一类型业务请求报文发送至查询到的所述网关接口信息对应的业务请求方网关接口，供所述业务请求方网关接口将所述预设第一类型业务请求报文发送至对应的业务处理方网关接口。
  17. 如权利要求16所述的计算机可读存储介质，其特征在于，所述第一查询步骤包括：
    根据预先确定的所述业务处理方服务标识信息与配置信息标识符之间的映射关系，查询所述业务信息中的业务处理方服务标识信息对应的配置信息标识符；
    根据预先确定的所述配置信息标识符与配置信息之间的映射关系，确定查询到的所述配置信息标识符对应的配置信息，所述配置信息即为所述预设第一类型业务对应的配置信息。
  18. 如权利要求16所述的计算机可读存储介质，其特征在于，所述获取步骤包括：
    提取所述预设第一类型业务请求指令中的业务请求信息，根据所述业务请求信息及预先确定的选择规则在预先确定的多条业务通道中选择一最优业务通道；
    获取所述最优业务通道的业务通道信息，并将所述业务请求信息及业务通道信息作为所述预设第一类型业务的业务信息。
  19. 如权利要求16至18中任一项所述的计算机可读存储介质，其特征在于，所述报文处理程序被所述处理器执行时，在所述发送步骤之后，还实现如下步骤：
    接收所述业务请求方网关接口返回的预设第一类型业务返回报文，且根据查询到的所述配置信息，解析所述预设第一类型业务返回报文。
  20. 如权利要求16至18中任一项所述的计算机可读存储介质，其特征在于，所述报文处理程序被所述处理器执行时，在所述发送步骤之后，还实现如下步骤：
    当在预设时长内未接收到所述预设第一类型业务返回报文时，启动预设第二类型业务，所述预设第二类型业务包括查询业务；
    当启动的所述预设第二类型业务为查询业务时，生成查询业务标识信息，并获取待查询预设第一类型业务请求报文对应的业务信息，并从所述业务信息中提取业务处理方服务标识信息及业务标识信息作为查询业务信息；
    根据所述业务处理方服务标识信息、查询业务标识信息及预先确定的所述业务处理方服务标识信息、查询业务标识信息及配置信息三者之间的映射关系，获取所述查询业务对应的配置信息；
    根据所述业务处理方服务标识信息、查询业务标识信息及预先确定的所述业务处理方 服务标识信息、查询业务标识信息及网关接口信息三者之间的映射关系，获取所述查询业务信息对应的网关接口信息；
    根据所述查询业务信息及所述配置信息，组装查询请求报文，并将组装后的所述查询请求报文发送至获取的所述网关接口信息对应的业务请求方网关接口，供所述业务请求方网关接口将所述查询请求报文发送至对应的业务处理方网关接口；
    接收所述业务请求方网关接口返回的查询返回报文，且根据所述配置信息，解析所述查询返回报文，以获得查询结果。
PCT/CN2018/107506 2018-06-29 2018-09-26 服务器、报文处理方法、程序和计算机可读存储介质 WO2020000720A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810694255.0 2018-06-29
CN201810694255.0A CN109194495B (zh) 2018-06-29 2018-06-29 服务器、报文处理方法和计算机可读存储介质

Publications (1)

Publication Number Publication Date
WO2020000720A1 true WO2020000720A1 (zh) 2020-01-02

Family

ID=64948645

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/107506 WO2020000720A1 (zh) 2018-06-29 2018-09-26 服务器、报文处理方法、程序和计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN109194495B (zh)
WO (1) WO2020000720A1 (zh)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110209377A (zh) * 2019-04-26 2019-09-06 平安科技（深圳）有限公司 基于工厂类的接口报文处理方法、装置、设备和存储介质
CN111724249A (zh) * 2020-06-29 2020-09-29 深圳壹账通智能科技有限公司 智能资金归集方法、装置、电子设备和存储介质
CN111935174A (zh) * 2020-09-02 2020-11-13 平安国际智慧城市科技股份有限公司 基于中间件网关的区块链业务系统对接方法、装置及设备
CN112116353B (zh) * 2020-09-28 2023-08-08 中国工商银行股份有限公司 账户数据处理方法、装置及系统
CN113055494B (zh) * 2021-03-30 2022-11-29 中国工商银行股份有限公司 通讯方法及通讯装置
CN113220759A (zh) * 2021-04-27 2021-08-06 深圳市云网万店科技有限公司 大数据存储服务共享方法、装置、计算机设备和存储介质
CN113434175B (zh) * 2021-06-29 2024-02-27 平安科技（深圳）有限公司 数据处理方法、装置、存储介质及设备
CN114172979A (zh) * 2021-12-02 2022-03-11 上海电力设计院有限公司 一种报文解析方法、平台、网关及存储介质
CN114500358B (zh) * 2022-02-14 2023-10-24 西藏创煌信息科技有限公司 网关报文分发方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3098772A1 (en) * 2003-06-17 2016-11-30 Nasdaq Technology AB A trading system supporting credit rating
CN107169756A (zh) * 2017-05-10 2017-09-15 北京凤凰理理它信息技术有限公司 支付通道分配方法、装置、存储介质和支付路由系统
CN107241315A (zh) * 2017-05-23 2017-10-10 广州唯品会网络技术有限公司 银行网关接口的接入方法、装置及计算机可读存储介质
CN107705118A (zh) * 2017-09-19 2018-02-16 深圳金融电子结算中心有限公司 基于渠道路由的交易支付方法、系统、服务器及存储介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9551983B2 (en) * 2011-11-15 2017-01-24 Rockwell Automation Technologies, Inc. Activity set management in a Manufacturing Execution System
CN105791178B (zh) * 2014-12-26 2019-02-15 阿里巴巴集团控股有限公司 报文组装方法及装置
CN104980488B (zh) * 2015-03-20 2019-01-29 深圳市腾讯计算机系统有限公司 报文传输方法及相关装置和通信系统
CN105049256B (zh) * 2015-08-10 2018-11-13 北京思特奇信息技术股份有限公司 一种通用自定义接口报文实现方法及系统
CN107918562B (zh) * 2016-10-11 2021-11-26 北京京东尚科信息技术有限公司 一种统一接口管理方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3098772A1 (en) * 2003-06-17 2016-11-30 Nasdaq Technology AB A trading system supporting credit rating
CN107169756A (zh) * 2017-05-10 2017-09-15 北京凤凰理理它信息技术有限公司 支付通道分配方法、装置、存储介质和支付路由系统
CN107241315A (zh) * 2017-05-23 2017-10-10 广州唯品会网络技术有限公司 银行网关接口的接入方法、装置及计算机可读存储介质
CN107705118A (zh) * 2017-09-19 2018-02-16 深圳金融电子结算中心有限公司 基于渠道路由的交易支付方法、系统、服务器及存储介质

Also Published As

Publication number Publication date
CN109194495A (zh) 2019-01-11
CN109194495B (zh) 2021-08-24

Similar Documents

Publication Publication Date Title
WO2020000720A1 (zh) 服务器、报文处理方法、程序和计算机可读存储介质
CN106649488B (zh) 多数据源交互接口的调用方法及装置
CN106503974B (zh) 交易数据处理方法及装置
US20110145844A1 (en) Systems and methods for facilitating call request aggregation over a network
CN111881329A (zh) 一种账户余额管理方法和系统
US11379191B2 (en) Presentation oriented rules-based technical architecture display framework
CN112181628B (zh) 资源转移方法、装置、系统和电子设备
CN110782310B (zh) 从第三方平台异步获取用户属性信息的方法、装置和系统
CN107451301B (zh) 实时投递账单邮件的处理方法、装置、设备和存储介质
CN116993523A (zh) 配置化对账方法、装置、设备及存储介质
CN109271564A (zh) 保单查询方法及设备
CN112950191A (zh) 基于退费业务的业务数据处理方法、装置及计算机设备
US20150154606A1 (en) System, method, and software for enterprise-wide complaint aggregation
CN110674173A (zh) 一种风控云上的数据缓存的方法和系统
CN113095806B (zh) 工单处理方法与装置、电子设备和计算机可读存储介质
CN111176588B (zh) 业务单据出单方法、装置、介质及电子设备
US11341581B2 (en) System and method for regular expression generation for improved data transfer
US9342541B1 (en) Presentation oriented rules-based technical architecture display framework (PORTRAY)
CN112270626A (zh) 一种企业信用额度管理方法、装置、存储介质及服务器
CN113971007B (zh) 信息处理方法、装置、电子设备及介质
CN113900895B (zh) 信息处理方法、信息处理装置、存储介质与电子设备
US11532023B2 (en) System and method for streamlining a checkout process of e-commerce websites
US20230244859A1 (en) System and method for automatically sharing verified user information across remote systems
CN113138999B (zh) 数据处理方法及装置、计算机存储介质、电子设备
CN116630072A (zh) 流水式资金对账的方法、装置、设备及存储介质

Legal Events

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

Ref document number: 18925015

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18925015

Country of ref document: EP

Kind code of ref document: A1