CN114257635A - Service calling method, system, computer device, storage medium, and program product - Google Patents

Service calling method, system, computer device, storage medium, and program product Download PDF

Info

Publication number
CN114257635A
CN114257635A CN202111399223.6A CN202111399223A CN114257635A CN 114257635 A CN114257635 A CN 114257635A CN 202111399223 A CN202111399223 A CN 202111399223A CN 114257635 A CN114257635 A CN 114257635A
Authority
CN
China
Prior art keywords
service
calling
code
format
access channel
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
CN202111399223.6A
Other languages
Chinese (zh)
Other versions
CN114257635B (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.)
CCB Finetech Co Ltd
Original Assignee
CCB Finetech 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 CCB Finetech Co Ltd filed Critical CCB Finetech Co Ltd
Priority to CN202111399223.6A priority Critical patent/CN114257635B/en
Publication of CN114257635A publication Critical patent/CN114257635A/en
Application granted granted Critical
Publication of CN114257635B publication Critical patent/CN114257635B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/955Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08Protocols for interworking; Protocol conversion

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

The application relates to a service calling method, a service calling device, computer equipment and a storage medium. The method comprises the following steps: the service calling system receives the service calling information sent by the service calling party, determines a target message format corresponding to the service characteristic information in the service calling information according to the format corresponding relation, performs format conversion on the service calling information according to the target message format, further determines a calling result according to the service calling information after the format conversion, and sends the calling result to the service calling party. In the method, the service calling system does not need to provide corresponding configuration information for each service, and only needs to determine the target message format corresponding to the service according to the service characteristic information in the service calling information, so that the occupation of the storage space on the service calling system is reduced, and the operation efficiency of the service calling system is improved.

Description

Service calling method, system, computer device, storage medium, and program product
Technical Field
The present application relates to the field of big data resource scheduling technologies, and in particular, to a service invocation method, system, computer device, storage medium, and computer program product.
Background
With the increasing service demands of users, the server side correspondingly needs to provide more and more services for the service invoker.
In the conventional technology, a server needs to be configured with configuration information corresponding to each service, where the configuration information includes a channel (which may be understood as a servlet or a service connector) corresponding to the service, a service invoker can generally invoke the service through multiple service channels, each type of service invoked by each service channel corresponds to one servlet, and the server needs to configure how many servlets accordingly. For example, a service caller can call two services of balance inquiry and account transfer payment through two service channels of a bank applet and a bank APP, and a server needs to correspondingly provide four servlets for the service caller.
When the server provides a large amount of services to the outside, the data size of the configuration information is also very large, a large amount of storage space needs to be occupied, and the operating efficiency of the server is reduced.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a service invocation method, apparatus, computer device, storage medium, and computer program product for solving the above technical problems.
A service invocation method, comprising:
receiving service calling information sent by a service calling party; the service calling information comprises service characteristic information of the target service;
determining a target message format corresponding to the service characteristic information according to the format corresponding relation, and performing format conversion on the service calling information according to the target message format; the format corresponding relation comprises the service characteristic information of the service and the corresponding relation between the message format adapted to the component for calling the corresponding service;
and determining a calling result according to the service calling information after the format conversion, and sending the calling result to a service calling party.
In one embodiment, the service feature information includes a transaction code and an access channel code, and determining a target message format corresponding to the service feature information according to the format correspondence includes:
acquiring a message format corresponding to the transaction code and the access channel code according to the format corresponding relation; the transaction code is used for representing the type of the called service, and the access channel code is used for representing the channel of the called service;
and determining the message format corresponding to the transaction code and the access channel code as a target message format.
In one embodiment, determining the invocation result according to the service request information after format conversion includes:
determining the URL address of the component for calling the target service according to the transaction code and the access channel code;
sending the service calling information after format conversion to a URL address;
and receiving a calling result sent by the component corresponding to the URL address.
In one embodiment, determining the URL address of the component invoking the target service based on the transaction code and the access channel code comprises:
determining a service code corresponding to the transaction code and the access channel code according to the format corresponding relation; the format corresponding relation also comprises a corresponding relation among a transaction code, an access channel code and a service code;
and acquiring the URL address corresponding to the service code as the URL address of the component calling the target service.
In one embodiment, the method further includes:
determining a transaction code and an access channel code of the service and a message format adapted to a component calling the corresponding service;
and correspondingly associating the transaction code with the access channel code and the message format matched with the component for calling the corresponding service to obtain a format corresponding relation.
A service invocation system, comprising:
the information receiving module is used for receiving the service calling information sent by the service calling party; the service calling information comprises service characteristic information of the target service;
the message conversion module is used for determining a target message format corresponding to the service characteristic information according to the format corresponding relation and performing format conversion on the service calling information according to the target message format; the format corresponding relation comprises service characteristic information of the service and a message format adaptive to the component for calling the corresponding service;
and the calling feedback module is used for determining a calling result according to the service calling information after the format conversion and sending the calling result to the service calling party.
In one embodiment, the service features include a transaction code and an access channel code, and the message conversion module is specifically configured to:
acquiring a message format corresponding to the transaction code and the access channel code according to the format corresponding relation;
determining a message format corresponding to the transaction code and the access channel code as a target message format; the transaction code is used for representing the type of the called service, and the access channel code is used for representing the channel for calling the service.
In one embodiment, the call feedback module is specifically configured to:
determining the URL address of the component for calling the target service according to the transaction code and the access channel code;
sending the service calling information after format conversion to a URL address;
and receiving a calling result sent by the component corresponding to the URL address.
In one embodiment, the call feedback module is specifically configured to:
determining a service code corresponding to the transaction code and the access channel code according to the format corresponding relation;
and acquiring the URL address corresponding to the service code as the URL address of the component calling the target service.
In one embodiment, the information receiving module is further configured to:
determining a transaction code and an access channel code of the service and a message format adapted to a component calling the corresponding service;
and correspondingly associating the transaction code with the access channel code and the message format matched with the component for calling the corresponding service to obtain a format corresponding relation.
A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements any of the methods described above when executing the computer program.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out any of the methods described above.
A computer program product comprising a computer program which, when executed by a processor, performs any of the methods described above.
According to the service calling method, the service calling device, the computer equipment, the storage medium and the computer program product, the service calling system receives the service calling information sent by the service calling party, determines the target message format corresponding to the service characteristic information in the service calling information according to the format corresponding relation, performs format conversion on the service calling information according to the target message format, further determines the calling result according to the service calling information after the format conversion, and sends the calling result to the service calling party. By the method, the service calling system does not need to provide corresponding configuration information for each service, only needs to determine the target message format corresponding to the service according to the service characteristic information in the service calling information, and particularly does not need to store a large amount of redundant configuration information when the service calling system can provide a large amount of services externally, so that the occupation of the storage space on the service calling system is reduced, and the operation efficiency of the service calling system is improved.
Drawings
FIG. 1 is a diagram of an application environment of a service invocation method in an embodiment provided by the present disclosure;
FIG. 2 is a flowchart illustrating a service invocation method according to a first embodiment;
fig. 3 is a schematic flow chart illustrating the process of determining the format of a target packet in the second embodiment;
FIG. 4 is a schematic structural diagram of a service invocation system in the third embodiment;
FIG. 5 is a flowchart illustrating the determination of the calling result in the fourth embodiment;
FIG. 6 is a flowchart illustrating a service invocation method in the fifth embodiment;
FIG. 7 is a block diagram showing the construction of a service invocation system in the sixth embodiment;
fig. 8 is an internal structural diagram of a computer device in an embodiment provided by the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The service calling method provided by the application can be applied to the application environment shown in fig. 1. Wherein the service invoker 102 communicates with the service invocation system 104 over a network. The service calling system 104 receives service calling information sent by the service calling party 102, the service calling information includes service feature information of a target service, the service calling system 104 determines a target message format corresponding to the service feature information according to the format corresponding relationship, performs format conversion on the service calling information according to the target message format, further determines a calling result according to the service calling information after the format conversion, and sends the calling result to the service calling party 102. The format corresponding relation comprises service characteristic information of the service and a message format adaptive to the component for calling the corresponding service. The service invoker 102 may be, but is not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices, and the service invoker system 104 may be implemented as a stand-alone server or a server cluster consisting of a plurality of servers.
In one embodiment, as shown in fig. 2, a service invocation method is provided, which is described by taking the application of the method to the service invocation system in fig. 1 as an example, and includes the following steps:
s210, receiving service calling information sent by a service calling party.
The service calling information comprises service characteristic information of the target service. The target service is a service to be called by the service calling party, the service characteristic information is used for representing the characteristics of the service, and the service can be the type of the service, such as balance inquiry and transfer payment, and can also be a service channel, such as an internet banking channel, an applet channel or an ATM (automatic Teller Machine) channel. The service characteristic information may indicate a specific service, and the service invocation system may determine the specific service based on the service characteristic information.
Optionally, the user performs a service selection operation on the service invoker to determine the target service, and the service invoker generates service invocation information including service feature information of the target service in response to the service selection operation of the user, and sends the service invocation information to the service invocation system to initiate a service invocation request to the service invocation system. For example, after the user clicks on the mobile phone and enters into APP of the XX bank, balance inquiry is selected, and the mobile phone serves as a service caller to generate service calling information in response to the service selection operation of the user, and sends the service calling information to the service calling system. Wherein, the service characteristic information indicates that the target service is balance inquiry service initiated by the internet banking channel.
Correspondingly, the service calling system receives the service calling information sent by the service calling party.
Optionally, the service invoking system provides servlets matched with the number of service channels for the service invoking party, each service channel corresponds to one servlet, and the service invoking party generates service invoking information in a corresponding message format based on the servlet selected by the user.
S220, determining a target message format corresponding to the service characteristic information according to the format corresponding relation, and performing format conversion on the service calling information according to the target message format.
The format corresponding relation comprises the service characteristic information of the service and the corresponding relation between the message format adapted to the component for calling the corresponding service. The target message format is the message format adapted to the component calling the target service. For example, the format of the message adapted to the component calling the target service is xml format, and the format of the target message is xml format.
Specifically, after receiving the service calling information, the service calling system unpacks the service calling information, obtains service characteristic information of a target service, determines a configuration file corresponding to the service characteristic information according to a format corresponding relation, wherein the configuration file comprises a message format adapted to a component calling the corresponding service, determines that the message format is the target message format, and performs format conversion on the service calling information according to the target message format so as to convert the message format of the service calling information into the target message format, and obtains the service calling information after format conversion.
Optionally, if the service invoking system does not determine the message format corresponding to the service feature information according to the format corresponding relationship, an error is reported to the service invoking party.
And S230, determining a calling result according to the service calling information after the format conversion, and sending the calling result to a service calling party.
Optionally, the service invoking system extracts service feature information in the format-converted service invoking information to determine an assembly for invoking the target service according to the service feature information, and then sends the format-converted service invoking information to the assembly, and the assembly invokes the target service to obtain a corresponding invoking result, and feeds the invoking result back to the service caller.
In this embodiment, the service invocation system determines a target message format corresponding to the service feature information in the service invocation information according to the format correspondence by receiving the service invocation information sent by the service invocation party, performs format conversion on the service invocation information according to the target message format, further determines an invocation result according to the service invocation information after the format conversion, and sends the invocation result to the service invocation party. According to the method, the service calling system does not need to provide corresponding configuration information for each service, only needs to determine the target message format corresponding to the service according to the service characteristic information in the service calling information, and particularly does not need to store a large amount of redundant configuration information when the service calling system can provide a large amount of services externally, so that the occupation of the storage space on the service calling system is reduced, and the operation efficiency of the service calling system is improved.
In one embodiment, the service characteristic information includes a transaction code and an access channel code, as shown in fig. 3, the step S220 includes:
s310, acquiring a message format corresponding to the transaction code and the access channel code according to the format corresponding relation.
The transaction code is used for representing the type of the called service, and the access channel code is used for representing the channel for calling the service. The characteristics of the corresponding service can be represented by the transaction code and the access channel code.
Optionally, in a case that the service feature information includes a transaction code and an access channel code, the format correspondence relationship includes a correspondence relationship between the transaction code of the service, the access channel code, and a message format adapted to the component invoking the corresponding service.
S320, determining that the message format corresponding to the transaction code and the access channel code is the target message format.
Specifically, under the condition that the service characteristic information includes a transaction code and an access channel code, the service calling system acquires a message format corresponding to the transaction code and the access channel code according to the format corresponding relation, and determines that the message format is a target message format adapted to a component calling the target service. For example, the format corresponding relationship including the correspondence between the transaction code of the service, the access channel code, and the message format adapted to the component calling the corresponding service is shown in table 1 below, and if the service feature information of the target service in the service calling information received by the service calling system includes the transaction code a001 and the access channel code B001, the message format adapted to the component calling the target service can be determined to be format a based on the table below.
Table 1 format corresponding relation table
Transaction code Access channel coding Message format
A001 B001 A
A001 B002 B
A001 B003 C
In this embodiment, the service invocation system obtains the message format corresponding to the transaction code and the access channel code according to the format correspondence relationship, and further determines that the message format corresponding to the transaction code and the access channel code is a target message format adapted to the component invoking the target service. The transaction code is used for representing the type of the called service, the access channel code is used for representing the channel of the called service, the service characteristics of the target service can be accurately reflected through the transaction code and the access channel code, the target service can be uniquely determined, the message format adaptive to the component of the called target service can be determined according to the format corresponding relation, and the accuracy of the determined target message format is further improved.
In one embodiment, as shown in fig. 4, the service calling system includes an integration component 401, a common component 402, and a product component 403, and the common component 402 and the product component 403 respectively communicate with the integration component 401 through a network. As shown in fig. 5, the determining, in S230, a call result according to the service call information after format conversion includes:
and S510, determining the URL address of the component for calling the target service according to the transaction code and the access channel code.
Optionally, the integration component 401, the common component 402, and the product component 403 are independent servers.
Specifically, the integration component 401 receives the service calling information sent by the service caller, unpacks the service calling information to obtain service feature information including a transaction code and an access channel code of the target service, and determines a Uniform Resource Locator (URL) address of the component calling the target service according to the transaction code and the access channel code.
Optionally, the format correspondence further includes a correspondence between a transaction code, an access channel code, and a service code, and the integration component 401 determines the service code corresponding to the transaction code and the access channel code according to the format correspondence, and obtains a URL address corresponding to the service code as a URL address of a component that invokes the target service.
It should be noted that the format correspondence is independently pre-stored in the service invocation system in the form of a database table. When the service traffic is increased and the service scale needs to be enlarged, only a database cluster is needed.
Specifically, the integration component 401 may determine a service code corresponding to the transaction code and the access channel code according to the format corresponding relationship, the public component 402 pre-stores a corresponding relationship between the service code and a URL address of the product component, and the integration component 401 acquires, from the public component 402, the URL address of the product component corresponding to the service code corresponding to the transaction code and the access channel code as the URL address of the component calling the target service.
S520, sending the service calling information after format conversion to the URL address.
S530, receiving a calling result sent by the component corresponding to the URL address.
Specifically, after determining the URL address of the component calling the target service, the integration component 401 sends the format-converted service calling information to the URL address, the product component 403 corresponding to the URL address calls the target service according to the format-converted service calling information, and obtains a corresponding calling result, the product component 403 sends the calling result to the integration component 401, and the integration component 401 receives the calling result.
In this embodiment, the service invoking system determines the service code corresponding to the transaction code and the access channel code according to the format correspondence, and obtains the URL address corresponding to the service code as the URL address of the component invoking the target service. The format corresponding relation is used as a database table independent of the server container, when the calling method is applied to other server containers, the format corresponding relation does not need to be changed, decoupling between the server container and the service function is achieved, the database table can be integrally migrated, relevant data required to be changed when the server container is replaced is greatly reduced, and transportability of the whole service calling method is improved.
In one embodiment, the method further includes a process of constructing a format correspondence relationship, as shown in fig. 6, the method further includes:
s610, determining a transaction code and an access channel code of the service and a message format adapted to the component for calling the corresponding service.
Optionally, the service invoking system may determine the transaction code and the access channel code of the service and the message format adapted to the component invoking the corresponding service based on the transaction code and the access channel code of the service input by the system developer and the message format adapted to the component invoking the corresponding service. For example, the service invoking system responds to a corresponding relationship building request initiated by a system developer, displays a corresponding relationship building page through a display device, receives a transaction code input by the system developer in a service transaction code filling area, an access channel code input in a service access channel code filling area, and a message format input in an adapted message format filling area, and can obtain the transaction code and the access channel code of the service and a message format adapted to a component for invoking the corresponding service.
S620, correspondingly associating the transaction code with the access channel code and the message format matched with the component for calling the corresponding service to obtain a format corresponding relation.
Specifically, the service calling system associates the determined transaction code and the access channel code with the message format adapted to the component calling the corresponding service correspondingly to obtain a format corresponding relationship. For example, continuing with the above example, the service invocation system associates the information input by the system developer in the corresponding filling area in the correspondence relationship building page, so as to obtain the format correspondence relationship.
Optionally, the format corresponding relationship may further include a service number corresponding to the transaction code and the access channel code, and the format corresponding relationship including the service number corresponding to the transaction code and the access channel code may also be determined in a manner that the merchant acquires information input by the system developer in the corresponding filling area, which is not described herein again.
Optionally, the format correspondence may further include information such as a service name, a current number of times that the service has been called, and a maximum number of simultaneous calls. The service calling system may use SQL (Structured Query Language) Query statements to insert the format correspondence into the routing table, so as to implement registration of the corresponding service, and at the same time, when information such as service calling condition and total number of services needs to be counted, the service calling system may implement simple SQL Query statements. Meanwhile, the corresponding relation of the formats in the routing table can be modified in batch.
In the embodiment, the service calling system determines the transaction code and the access channel code of the service and the message format adapted to the component for calling the corresponding service, and correspondingly associates the transaction code and the access channel code with the message format adapted to the component for calling the corresponding service to obtain the format corresponding relation, so as to make a data base for subsequent service calling, thereby being beneficial to quickly determining the target message format and improving the overall efficiency of service calling.
It should be understood that although the various steps in the flow charts in fig. 2-6 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps of the flowcharts of fig. 2-6 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least a portion of the steps or stages of the other steps.
In one embodiment, as shown in fig. 7, there is provided a service invocation system, including: an information receiving module 701, a message conversion module 702, and a call feedback module 703, wherein:
the information receiving module 701 is configured to receive service invocation information sent by a service invocation party; the service calling information comprises service characteristic information of the target service;
the message conversion module 702 is configured to determine a target message format corresponding to the service feature information according to the format correspondence, and perform format conversion on the service invocation information according to the target message format; the format corresponding relation comprises service characteristic information of the service and a message format adaptive to the component for calling the corresponding service;
the call feedback module 703 is configured to determine a call result according to the service call information after format conversion, and send the call result to the service caller.
In one embodiment, the service features include a transaction code and an access channel code, and the message conversion module 702 is specifically configured to:
acquiring a message format corresponding to the transaction code and the access channel code according to the format corresponding relation; determining a message format corresponding to the transaction code and the access channel code as a target message format; the transaction code is used for representing the type of the called service, and the access channel code is used for representing the channel for calling the service.
In one embodiment, the call feedback module 703 is specifically configured to:
determining the URL address of the component for calling the target service according to the transaction code and the access channel code; sending the service calling information after format conversion to a URL address; and receiving a calling result sent by the component corresponding to the URL address.
In one embodiment, the call feedback module 703 is specifically configured to:
determining a service code corresponding to the transaction code and the access channel code according to the format corresponding relation; and acquiring the URL address corresponding to the service code as the URL address of the component calling the target service.
In one embodiment, the information receiving module 701 is further configured to:
determining a transaction code and an access channel code of the service and a message format adapted to a component calling the corresponding service; and correspondingly associating the transaction code with the access channel code and the message format matched with the component for calling the corresponding service to obtain a format corresponding relation.
For specific limitations of the service invocation device, reference may be made to the above limitations of the service invocation method, which are not described herein again. The modules in the service invocation device can be wholly or partially implemented by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 8. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing data related to service invocation. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a service invocation method.
Those skilled in the art will appreciate that the architecture shown in fig. 8 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:
receiving service calling information sent by a service calling party; the service calling information comprises service characteristic information of the target service; determining a target message format corresponding to the service characteristic information according to the format corresponding relation, and performing format conversion on the service calling information according to the target message format; the format corresponding relation comprises the service characteristic information of the service and the corresponding relation between the message format adapted to the component for calling the corresponding service; and determining a calling result according to the service calling information after the format conversion, and sending the calling result to a service calling party.
In one embodiment, the service characteristic information includes a transaction code and an access channel code, and the processor executes the computer program to perform the following steps:
acquiring a message format corresponding to the transaction code and the access channel code according to the format corresponding relation; the transaction code is used for representing the type of the called service, and the access channel code is used for representing the channel of the called service; and determining the message format corresponding to the transaction code and the access channel code as a target message format.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
determining the URL address of the component for calling the target service according to the transaction code and the access channel code; sending the service calling information after format conversion to a URL address; and receiving a calling result sent by the component corresponding to the URL address.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
determining a service code corresponding to the transaction code and the access channel code according to the format corresponding relation; the format corresponding relation also comprises a corresponding relation among a transaction code, an access channel code and a service code; and acquiring the URL address corresponding to the service code as the URL address of the component calling the target service.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
determining a transaction code and an access channel code of the service and a message format adapted to a component calling the corresponding service; and correspondingly associating the transaction code with the access channel code and the message format matched with the component for calling the corresponding service to obtain a format corresponding relation.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
receiving service calling information sent by a service calling party; the service calling information comprises service characteristic information of the target service; determining a target message format corresponding to the service characteristic information according to the format corresponding relation, and performing format conversion on the service calling information according to the target message format; the format corresponding relation comprises the service characteristic information of the service and the corresponding relation between the message format adapted to the component for calling the corresponding service; and determining a calling result according to the service calling information after the format conversion, and sending the calling result to a service calling party.
In one embodiment, the service characteristic information comprises a transaction code and an access channel code, and the computer program when executed by the processor further performs the steps of:
acquiring a message format corresponding to the transaction code and the access channel code according to the format corresponding relation; the transaction code is used for representing the type of the called service, and the access channel code is used for representing the channel of the called service; and determining the message format corresponding to the transaction code and the access channel code as a target message format.
In one embodiment, the computer program when executed by the processor further performs the steps of:
determining the URL address of the component for calling the target service according to the transaction code and the access channel code; sending the service calling information after format conversion to a URL address; and receiving a calling result sent by the component corresponding to the URL address.
In one embodiment, the computer program when executed by the processor further performs the steps of:
determining a service code corresponding to the transaction code and the access channel code according to the format corresponding relation; the format corresponding relation also comprises a corresponding relation among a transaction code, an access channel code and a service code; and acquiring the URL address corresponding to the service code as the URL address of the component calling the target service.
In one embodiment, the computer program when executed by the processor further performs the steps of:
determining a transaction code and an access channel code of the service and a message format adapted to a component calling the corresponding service; and correspondingly associating the transaction code with the access channel code and the message format matched with the component for calling the corresponding service to obtain a format corresponding relation.
In one embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, performs the steps of:
receiving service calling information sent by a service calling party; the service calling information comprises service characteristic information of the target service; determining a target message format corresponding to the service characteristic information according to the format corresponding relation, and performing format conversion on the service calling information according to the target message format; the format corresponding relation comprises the service characteristic information of the service and the corresponding relation between the message format adapted to the component for calling the corresponding service; and determining a calling result according to the service calling information after the format conversion, and sending the calling result to a service calling party.
In one embodiment, the service characteristic information comprises a transaction code and an access channel code, and the computer program when executed by the processor further performs the steps of:
acquiring a message format corresponding to the transaction code and the access channel code according to the format corresponding relation; the transaction code is used for representing the type of the called service, and the access channel code is used for representing the channel of the called service; and determining the message format corresponding to the transaction code and the access channel code as a target message format.
In one embodiment, the computer program when executed by the processor further performs the steps of:
determining the URL address of the component for calling the target service according to the transaction code and the access channel code; sending the service calling information after format conversion to a URL address; and receiving a calling result sent by the component corresponding to the URL address.
In one embodiment, the computer program when executed by the processor further performs the steps of:
determining a service code corresponding to the transaction code and the access channel code according to the format corresponding relation; the format corresponding relation also comprises a corresponding relation among a transaction code, an access channel code and a service code; and acquiring the URL address corresponding to the service code as the URL address of the component calling the target service.
In one embodiment, the computer program when executed by the processor further performs the steps of:
determining a transaction code and an access channel code of the service and a message format adapted to a component calling the corresponding service; and correspondingly associating the transaction code with the access channel code and the message format matched with the component for calling the corresponding service to obtain a format corresponding relation.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (13)

1. A method for service invocation, characterized in that the method comprises:
receiving service calling information sent by a service calling party; the service calling information comprises service characteristic information of a target service;
determining a target message format corresponding to the service characteristic information according to the format corresponding relation, and performing format conversion on the service calling information according to the target message format; the format corresponding relation comprises the service characteristic information of the service and the corresponding relation between the message format adapted to the component for calling the corresponding service;
determining a calling result according to the service calling information after format conversion, and sending the calling result to the service calling party.
2. The method of claim 1, wherein the service characteristic information comprises a transaction code and an access channel code, and the determining the target packet format corresponding to the service characteristic information according to the format correspondence comprises:
acquiring a message format corresponding to the transaction code and the access channel code according to the format corresponding relation; the transaction code is used for representing the type of the called service, and the access channel code is used for representing a channel for calling the service;
and determining the message format corresponding to the transaction code and the access channel code as the target message format.
3. The method of claim 2, wherein the determining a call result according to the format-converted service request information comprises:
determining a URL address of a component for calling the target service according to the transaction code and the access channel code;
sending the service calling information after format conversion to the URL address;
and receiving the calling result sent by the component corresponding to the URL address.
4. The method of claim 3, wherein determining the URL address of the component invoking the target service based on the transaction code and the access channel code comprises:
determining a service code corresponding to the transaction code and the access channel code according to the format corresponding relation; the format corresponding relation also comprises a corresponding relation among a transaction code, an access channel code and a service code;
and acquiring a URL address corresponding to the service code as a URL address of a component for calling the target service.
5. The method of any one of claims 1 to 4, further comprising:
determining a transaction code and an access channel code of the service and a message format adapted to a component calling the corresponding service;
and correspondingly associating the transaction code with the access channel code and the message format adapted to the component for calling the corresponding service to obtain the format corresponding relation.
6. A service invocation system, characterized in that said system comprises:
the information receiving module is used for receiving the service calling information sent by the service calling party; the service calling information comprises service characteristic information of a target service;
the message conversion module is used for determining a target message format corresponding to the service characteristic information according to the format corresponding relation and performing format conversion on the service calling information according to the target message format; the format corresponding relation comprises service characteristic information of the service and a message format adaptive to a component for calling the corresponding service;
and the calling feedback module is used for determining a calling result according to the service calling information after format conversion and sending the calling result to the service calling party.
7. The system of claim 6, wherein the service features include a transaction code and an access channel code, and wherein the message conversion module is specifically configured to:
acquiring a message format corresponding to the transaction code and the access channel code according to the format corresponding relation;
determining the message format corresponding to the transaction code and the access channel code as the target message format; the transaction code is used for representing the type of the called service, and the access channel code is used for representing the channel for calling the service.
8. The system of claim 7, wherein the call feedback module is specifically configured to:
determining a URL address of a component for calling the target service according to the transaction code and the access channel code;
sending the service calling information after format conversion to the URL address;
and receiving the calling result sent by the component corresponding to the URL address.
9. The system of claim 8, wherein the call feedback module is specifically configured to:
determining a service code corresponding to the transaction code and the access channel code according to the format corresponding relation;
and acquiring a URL address corresponding to the service code as a URL address of a component for calling the target service.
10. The system of any one of claims 6 to 9, wherein the information receiving module is further configured to:
determining a transaction code and an access channel code of the service and a message format adapted to a component calling the corresponding service;
and correspondingly associating the transaction code with the access channel code and the message format adapted to the component for calling the corresponding service to obtain the format corresponding relation.
11. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 5 when executing the computer program.
12. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 5.
13. A computer program product comprising a computer program, characterized in that the computer program realizes the steps of the method of any one of claims 1 to 5 when executed by a processor.
CN202111399223.6A 2021-11-19 2021-11-19 Service calling method, system, computer device, storage medium and program product Active CN114257635B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111399223.6A CN114257635B (en) 2021-11-19 2021-11-19 Service calling method, system, computer device, storage medium and program product

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111399223.6A CN114257635B (en) 2021-11-19 2021-11-19 Service calling method, system, computer device, storage medium and program product

Publications (2)

Publication Number Publication Date
CN114257635A true CN114257635A (en) 2022-03-29
CN114257635B CN114257635B (en) 2023-05-23

Family

ID=80793067

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111399223.6A Active CN114257635B (en) 2021-11-19 2021-11-19 Service calling method, system, computer device, storage medium and program product

Country Status (1)

Country Link
CN (1) CN114257635B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114938387A (en) * 2022-07-22 2022-08-23 浙江中控技术股份有限公司 Data transmission method, device, system and storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110704521A (en) * 2019-08-30 2020-01-17 深圳壹账通智能科技有限公司 Interface data access method and system
CN111010438A (en) * 2019-12-13 2020-04-14 北京达佳互联信息技术有限公司 Remote procedure calling method, device, server and storage medium
CN111355800A (en) * 2020-02-28 2020-06-30 中国建设银行股份有限公司 Service processing method, device, equipment and storage medium
CN111722947A (en) * 2020-06-28 2020-09-29 深圳壹账通智能科技有限公司 Service calling method and system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110704521A (en) * 2019-08-30 2020-01-17 深圳壹账通智能科技有限公司 Interface data access method and system
CN111010438A (en) * 2019-12-13 2020-04-14 北京达佳互联信息技术有限公司 Remote procedure calling method, device, server and storage medium
CN111355800A (en) * 2020-02-28 2020-06-30 中国建设银行股份有限公司 Service processing method, device, equipment and storage medium
CN111722947A (en) * 2020-06-28 2020-09-29 深圳壹账通智能科技有限公司 Service calling method and system

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114938387A (en) * 2022-07-22 2022-08-23 浙江中控技术股份有限公司 Data transmission method, device, system and storage medium
CN114938387B (en) * 2022-07-22 2022-11-11 浙江中控技术股份有限公司 Data transmission method, device, system and storage medium

Also Published As

Publication number Publication date
CN114257635B (en) 2023-05-23

Similar Documents

Publication Publication Date Title
CN109474578B (en) Message checking method, device, computer equipment and storage medium
CN111092877B (en) Data processing method and device, electronic equipment and storage medium
CN109213770B (en) Data processing method, system, computer device and storage medium
CN111722947A (en) Service calling method and system
CN114172966B (en) Service calling method, service processing method and device under unitized architecture
US9930176B2 (en) Personalizing communications services using environmental data
CN110213392B (en) Data distribution method and device, computer equipment and storage medium
CN112732742B (en) Query page creating method and device, computer equipment and storage medium
CN114257635B (en) Service calling method, system, computer device, storage medium and program product
CN113467855A (en) Webpage request processing method and device, electronic equipment and storage medium
CN114125050A (en) Message scheduling method, device, equipment and storage medium
CN113763043B (en) Advertisement landing page display method and device, storage medium and computer equipment
CN112260933A (en) Communication method, communication device, electronic equipment and medium
CN116414628A (en) Transaction request processing method and device in new and old system switching process
CN115617924A (en) Financial data processing method, device, equipment and storage medium
CN114186161A (en) Page display information configuration method, device, equipment and readable storage medium
CN110888901B (en) System management method, device, computer equipment and storage medium
CN114297552A (en) Form expansion method and device, computer equipment and storage medium
CN109460230B (en) Method and system for multiplexing transmission value and service logic between pages
CN110717743A (en) Distribution method, electronic equipment and storage medium
CN113222765B (en) Market data pushing method and device, electronic equipment and storage medium
CN113901377B (en) Service calling method, device, storage medium and equipment of legacy system
CN114003414B (en) Service return visit processing method and device, computer equipment and storage medium
CN115964398A (en) Data acquisition method, device, equipment and storage medium
CN117035855A (en) Resource management method, apparatus, device, storage medium, and program product

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