CN115374207A

CN115374207A - Service processing method and device, electronic equipment and computer readable storage medium

Info

Publication number: CN115374207A
Application number: CN202211050270.4A
Authority: CN
Inventors: 万金龙
Original assignee: Industrial and Commercial Bank of China Ltd ICBC; ICBC Technology Co Ltd
Current assignee: Industrial and Commercial Bank of China Ltd ICBC; ICBC Technology Co Ltd
Priority date: 2022-08-30
Filing date: 2022-08-30
Publication date: 2022-11-22

Abstract

The present disclosure provides a service processing method and apparatus, an electronic device, and a computer-readable storage medium, which can be applied to the field of computer technologies and financial technologies. The service processing method comprises the following steps: responding to a received service processing request from a calling system, and acquiring a simulation identifier and interface configuration information according to an interface identifier in the service processing request, wherein the service processing request comprises to-be-processed service information corresponding to the to-be-processed service, the to-be-processed service information comprises an interface identifier, the interface identifier is used for identifying a to-be-called interface corresponding to the to-be-processed service, and the simulation identifier and the interface configuration information are associated with the interface identifier; under the condition that the simulation identification representation service processing request is determined to belong to the simulation calling request, acquiring simulation configuration information according to the interface identification; respectively matching the service information to be processed with each preset rule to obtain target simulation information; and returning the target simulation information to the calling system so as to complete the processing of the service to be processed.

Description

Service processing method and device, electronic equipment and computer readable storage medium

Technical Field

The present disclosure relates to the field of computer technology and the field of finance, and more particularly, to a method and an apparatus for processing a service, an electronic device, a computer-readable storage medium, and a computer program product.

Background

With the development of computer technology, data can be converted and transferred between different system interfaces based on communication protocols and data exchange formats.

In the course of implementing the disclosed concept, the inventors found that there are at least the following problems in the related art: the efficiency of data conversion and transmission between different system interfaces cannot be well guaranteed by adopting the related technology.

Disclosure of Invention

In view of this, the present disclosure provides a service processing method and apparatus, an electronic device, a computer-readable storage medium, and a computer program product.

According to an aspect of the present disclosure, there is provided a service processing method, including:

responding to a received service processing request from a calling system, and acquiring a simulation identifier and interface configuration information according to an interface identifier in the service processing request, wherein the service processing request comprises to-be-processed service information corresponding to a to-be-processed service, the to-be-processed service information comprises the interface identifier, the interface identifier is used for identifying an interface to be called corresponding to the to-be-processed service, and the simulation identifier and the interface configuration information are associated with the interface identifier;

under the condition that the simulation identification represents that the service processing request belongs to a simulation calling request, acquiring simulation configuration information according to the interface identification, wherein the simulation configuration information comprises at least one preset rule and simulation information corresponding to each preset rule in the at least one preset rule;

respectively matching the service information to be processed with each preset rule to obtain target simulation information; and

and returning the target simulation information to the calling system so as to complete the processing of the to-be-processed service.

According to an embodiment of the present disclosure, each of the at least one preset rule includes a preset field identifier.

According to an embodiment of the present disclosure, the matching the to-be-processed service information with each preset rule, respectively, to obtain target simulation information includes:

matching the service information to be processed with each preset field identifier in at least one preset field identifier respectively;

under the condition that the service information to be processed is successfully matched with a target preset field identifier in at least one preset field identifier, determining a preset rule corresponding to the target preset field identifier as a target preset rule; and

and determining the simulation information corresponding to the target preset rule as the target simulation information.

According to an embodiment of the present disclosure, the method further includes:

and under the condition that the service information to be processed is determined not to be successfully matched with each preset field identifier, determining preset simulation information as the target simulation information.

According to the embodiment of the present disclosure, the interface configuration information further includes at least one identifier of an interface to be called, an association relationship between the interfaces to be called, and a request packet format conversion rule and a processing result packet format conversion rule respectively corresponding to each interface to be called.

under the condition that the simulation identifier represents that the service processing request belongs to the direct calling request, analyzing the service information to be processed to obtain analyzed service information to be processed;

converting the analyzed to-be-processed service information according to the request message format conversion rule to obtain converted to-be-processed service information;

according to the interface configuration information and the incidence relation, the converted to-be-processed service information is sent to the to-be-called interface; and

receiving a service processing result returned by the interface to be called;

converting the returned service processing result according to the processing result message format conversion rule to obtain a service processing result to be returned;

and returning the service processing result to be returned to the calling system.

According to an embodiment of the present disclosure, in a case that the association relationship of the interface to be called includes serial calling, the sending the converted to-be-processed service information to the interface of the system to be called according to the interface configuration information and the association relationship includes:

determining an initial interface to be called and a termination interface to be called according to the incidence relation;

determining a request message format conversion rule of an initial interface to be called according to the interface configuration information;

converting the service information to be processed according to the request message format conversion rule of the initial interface to be called to obtain converted service information to be processed;

sending the converted to-be-processed service information to the initial to-be-called interface;

receiving a returned candidate service processing result from the starting interface to be called; and

determining a request message format conversion rule and a processing result message format conversion rule for terminating the interface to be called according to the interface configuration information;

converting the returned candidate service processing result according to the request message format conversion rule for terminating the interface to be called to obtain a converted candidate service processing result;

and sending the converted candidate service processing result to the interface to be called.

According to an embodiment of the present disclosure, the receiving a service processing result returned from the interface to be called includes:

receiving the returned service processing result from the interface to be called

According to an embodiment of the present disclosure, in a case that the association relationship of the interface to be called includes parallel calling, the sending, according to the interface configuration information and the association relationship, the converted to-be-processed service information to the interface to be called includes:

determining a request message format conversion rule and a processing result message format conversion rule corresponding to each interface to be called according to the interface configuration information;

converting the analyzed to-be-processed service information according to the request message format conversion rule corresponding to each to-be-called interface to obtain converted to-be-processed service information;

and sending each converted to-be-processed service information to the to-be-called interface in parallel.

According to an embodiment of the present disclosure, the receiving the converted service processing result from the interface to be called includes:

and receiving candidate service processing results from the interface to be called in parallel.

According to the embodiment of the disclosure, the interface identifier, the interface configuration information and the simulation configuration information are stored in a database in an associated manner.

According to another aspect of the present disclosure, there is provided a service processing apparatus, including:

a first obtaining module, configured to, in response to a service processing request received from a calling system, obtain a simulation identifier and interface configuration information according to an interface identifier in the service processing request, where the service processing request includes to-be-processed service information corresponding to a to-be-processed service, the to-be-processed service information includes the interface identifier, the interface identifier is used to identify an interface to be called corresponding to the to-be-processed service, and the simulation identifier and the interface configuration information are associated with the interface identifier;

a second obtaining module, configured to, when it is determined that the simulation identifier represents that the service processing request belongs to a simulation call request, obtain simulation configuration information according to the interface identifier, where the simulation configuration information includes at least one preset rule and simulation information corresponding to each preset rule in the at least one preset rule;

the matching module is used for respectively matching the service information to be processed with each preset rule to obtain simulation information; and

and the first sending module is used for returning the simulation information to the calling system so as to complete the processing of the service to be processed.

According to another aspect of the present disclosure, there is provided an electronic device including:

one or more processors;

a memory to store one or more instructions that,

wherein the one or more instructions, when executed by the one or more processors, cause the one or more processors to implement a method as described in this disclosure.

According to another aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to implement a method as described in the present disclosure.

According to another aspect of the present disclosure, there is provided a computer program product comprising computer executable instructions that when executed are for implementing a method as described in the present disclosure.

According to the embodiment of the disclosure, the interface configuration information is acquired after the service processing request from the calling system is received, and the interface configuration information is acquired based on the interface identifier included in the service information to be processed in the service processing request, so that the adaptation between different system interfaces can be realized, and the flexibility of interface adaptation is improved. In addition, under the condition that the simulation identification representation service processing request is determined to belong to the simulation calling request, the simulation configuration information is obtained, the service information to be processed is matched with each preset rule in the simulation configuration information respectively, and the target simulation information is obtained.

Drawings

The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:

fig. 1 schematically shows a system architecture to which a service processing method may be applied according to an embodiment of the present disclosure;

FIG. 2 schematically shows a flow diagram of a traffic handling method according to an embodiment of the present disclosure;

FIG. 3 schematically illustrates an example diagram of a simulated call request handling process according to an embodiment of this disclosure;

FIG. 4 schematically illustrates an example diagram of a direct Call request handling process according to an embodiment of this disclosure;

fig. 5 schematically shows a block diagram of a traffic processing device according to an embodiment of the present disclosure; and

fig. 6 schematically shows a block diagram of an electronic device adapted to implement a traffic processing method according to an embodiment of the present disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that these descriptions are illustrative only and are not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

In those instances where a convention analogous to "at least one of A, B, and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). Where a convention analogous to "at least one of A, B, or C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, or C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.).

In the technical scheme of the disclosure, the acquisition, storage, application and the like of the personal information of the related user all accord with the regulations of related laws and regulations, necessary security measures are taken, and the customs of the public order is not violated.

In the technical scheme of the disclosure, before the personal information of the user is obtained or collected, the authorization or the consent of the user is obtained.

Because different codes need to be developed according to the communication protocols and the data exchange formats corresponding to different interfaces, labor and time costs are increased. In addition, due to the lack of page configuration, different codes need to be developed for different systems by the same interface, thereby increasing resource consumption. In addition, since there is no MOCK function, in the case that a certain system interface is unavailable, the whole function is unavailable, thereby affecting the development and test progress of different system interfaces.

In order to at least partially solve the technical problems in the related art, the present disclosure provides a business processing method and apparatus, an electronic device, and a computer-readable storage medium, which can be applied to the field of computer technology and the field of finance. The service processing method comprises the following steps: responding to a received service processing request from a calling system, and acquiring a simulation identifier and interface configuration information according to an interface identifier in the service processing request, wherein the service processing request comprises to-be-processed service information corresponding to the to-be-processed service, the to-be-processed service information comprises the interface identifier, the interface identifier is used for identifying an interface to be called corresponding to the to-be-processed service, the simulation identifier and the interface configuration information are associated with the interface identifier, and the interface configuration information comprises the simulation identifier; under the condition that the simulation identification representation service processing request is determined to belong to the simulation calling request, acquiring simulation configuration information according to the interface identification, wherein the simulation configuration information comprises at least one preset rule and simulation information corresponding to each preset rule in the at least one preset rule; respectively matching the service information to be processed with each preset rule to obtain target simulation information; and returning the target simulation information to the calling system so as to complete the processing of the service to be processed.

It should be noted that the service processing method and apparatus provided by the embodiments of the present disclosure may be applied to the field of computer technology and the field of finance, for example, to interface adaptation. The service processing method and device provided by the embodiment of the disclosure can also be used in any fields except the technical field of computers and the financial field, for example, the service processing method and device can be applied to the processing of service requests. The application fields of the service processing method and the service processing device provided by the embodiment of the disclosure are not limited.

Fig. 1 schematically shows a system architecture to which a service processing method may be applied according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.

As shown in fig. 1, the system architecture 100 according to this embodiment may include

terminal devices

101, 102, 103, a network 104 and a server 105. The network 104 serves as a medium for providing communication links between the

terminal devices

101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired and/or wireless communication links, and so forth.

The user may use the

terminal devices

101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The

terminal devices

101, 102, 103 may have installed thereon various communication client applications, such as a shopping-like application, a web browser application, a search-like application, an instant messaging tool, a mailbox client, and/or social platform software, etc. (by way of example only).

The

terminal devices

101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 105 may be a server providing various services, such as a background management server (for example only) providing support for websites browsed by users using the

terminal devices

101, 102, 103. The backend management server may analyze and process the received data such as the user request, and feed back a processing result (for example, a web page, information, or data obtained or generated according to the user request) to the terminal device.

It should be noted that the service processing method provided by the embodiment of the present disclosure may be generally executed by the server 105. Accordingly, the service processing apparatus provided by the embodiment of the present disclosure may be generally disposed in the server 105. The service processing method provided by the embodiment of the present disclosure may also be executed by a server or a server cluster that is different from the server 105 and is capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105. Correspondingly, the service processing apparatus provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server 105 and capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105.

Alternatively, the service processing method provided by the embodiment of the present disclosure may also be generally executed by the

terminal device

101, 102, or 103. Correspondingly, the service processing apparatus provided by the embodiment of the present disclosure may also be disposed in the

terminal device

101, 102, or 103.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

It should be noted that the sequence numbers of the respective operations in the following methods are merely used as a representation of the operations for description, and should not be construed as representing the execution order of the respective operations. The method need not be performed in the exact order shown, unless explicitly stated.

Fig. 2 schematically shows a flow chart of a traffic processing method according to an embodiment of the present disclosure.

As shown in fig. 2, the service processing method 200 includes operations S210 to S240.

In operation S210, in response to receiving a service processing request from a calling system, a simulation identifier and interface configuration information are obtained according to an interface identifier in the service processing request. The service processing request comprises to-be-processed service information corresponding to the to-be-processed service, the to-be-processed service information comprises an interface identifier, the interface identifier is used for identifying a to-be-called interface corresponding to the to-be-processed service, and the simulation identifier and the interface configuration information are associated with the interface identifier.

In operation S220, in a case that it is determined that the simulation identifier representation service processing request belongs to the simulation call request, the simulation configuration information is obtained according to the interface identifier. The simulation configuration information includes at least one preset rule and simulation information corresponding to each preset rule in the at least one preset rule.

In operation S230, the service information to be processed is matched with each preset rule, so as to obtain target simulation information.

In operation S240, the target simulation information is returned to the calling system so as to complete the processing of the to-be-processed service.

According to the embodiment of the disclosure, a code for generating a service processing request can be written into a script in advance, and when service processing needs to be performed between a calling system and a system to be called, a user can run the script through terminal equipment to generate a service processing request message and send the service processing request message to a server, so that the server can process the service processing request according to the service processing request message.

According to the embodiment of the present disclosure, the service processing request may include service information to be processed corresponding to the service to be processed, and the service information to be processed may include an interface identifier. The interface identification may include a request header and a request path. The interface identifier may be used to identify an interface to be invoked corresponding to the service to be processed.

According to the embodiment of the disclosure, after receiving the service processing request from the calling system, the interface configuration information may be acquired according to the service processing request. The interface configuration information may include an analog identification. The emulation identifier can be used to identify whether the service processing request belongs to an emulated call request or a direct call request.

According to the embodiment of the disclosure, under the condition that it is determined that the simulation identifier representation service processing request belongs to the simulation calling request, the simulation configuration information can be acquired according to the interface identifier. The simulation configuration information may include at least one preset rule and simulation information respectively corresponding to each of the at least one preset rule. The specific content of the preset rules and the simulation information can be set by those skilled in the art according to actual requirements.

According to the embodiment of the disclosure, after the simulation configuration information is acquired, the service information to be processed and each preset rule in the simulation configuration information can be respectively matched, the preset rule successfully matched is determined as the target preset rule, and the simulation information corresponding to the target preset rule is determined as the target simulation information.

According to the embodiment of the disclosure, after the target simulation information is obtained, the target simulation information can be sent to a calling system so as to complete processing of the service to be processed.

According to the embodiment of the disclosure, in the process of processing the service request, the complete processing process can be recorded through the log, so that a developer can conveniently monitor, analyze and troubleshoot problems through the log system. The log file may be stored locally, in a database, or on the open source stream processing platform Kafka, etc.

Referring to fig. 3 and 4, a service processing method 200 according to an embodiment of the present invention is further described.

According to the embodiment of the disclosure, the interface identification, the interface configuration information and the simulation configuration information are stored in a database in an associated manner.

According to the embodiment of the present disclosure, the interface configuration information may include an analog identifier, a to-be-called system identifier corresponding to the to-be-called interface, an identifier of the to-be-called interface, an association relationship of the to-be-called interface, a request packet format conversion rule, and a processing result packet format conversion rule. The simulation configuration information may include at least one preset rule and simulation information respectively corresponding to each of the at least one preset rule.

According to the embodiment of the present disclosure, the correspondence between the interface identifier and the interface configuration information and the correspondence between the interface identifier and the simulation configuration information may be realized by a program, a configuration file, or a database. For example, the interface identification, interface configuration information, and simulation configuration information may be stored in association in a database. After receiving the service processing request from the calling system, the corresponding interface configuration information may be obtained from the database according to the interface identifier.

According to the embodiment of the disclosure, under the condition that it is determined that the simulation identifier representation service processing request in the interface configuration information belongs to the simulation call request, the corresponding simulation configuration information can be acquired from the database according to the interface identifier. And under the condition that the simulation identifier in the interface configuration information determines that the service processing request belongs to the direct calling request, processing the to-be-processed service information in the service processing request and calling an interface of the to-be-called system.

According to an embodiment of the present disclosure, each of the at least one preset rule includes a preset field identification.

According to an embodiment of the present disclosure, operation S230 may include the following operations.

And respectively matching the service information to be processed with each preset field identifier in at least one preset field identifier. And under the condition that the matching of the service information to be processed and a target preset field identifier in at least one preset field identifier is determined to be successful, determining a preset rule corresponding to the target preset field identifier as a target preset rule. And determining the simulation information corresponding to the target preset rule as target simulation information.

Operation S230 may further include the following operations according to an embodiment of the present disclosure.

And under the condition that the service information to be processed is determined not to be successfully matched with each preset field identifier, determining the preset simulation information as target simulation information.

According to embodiments of the present disclosure, different interfaces may correspond to different analog information. By dynamically matching different simulation information according to preset rules, message simulation according to interface dimensionality can be realized, namely, the same interface can return different simulation messages according to request messages. The preset rule may include whether a plurality of fields in the request message field satisfy a preset condition.

According to the embodiment of the disclosure, under the condition that it is determined that the simulation identifier representation service processing request belongs to the simulation calling request, the simulation configuration information can be acquired according to the interface identifier. The service information to be processed and the preset field identification in each preset rule can be respectively matched, and under the condition of successful matching, the simulation information corresponding to the target preset rule can be determined as target simulation information; in the case where the mismatch is successful, the preset simulation information may be determined as the target simulation information.

For example, the simulation configuration information may include a first preset rule, a second preset rule, and a third preset rule. The first preset rule may be set to "opType = =1", and the simulation information corresponding to the first preset rule may be a successfully added packet. The second preset rule may be set to "opType = =2", and the simulation information corresponding to the second preset rule may be a successfully deleted packet. The third preset rule may be set to "opType = =3", and the simulation information corresponding to the third preset rule may be a message that is successfully updated. The preset simulation information may be a null message.

According to the embodiment of the disclosure, under the condition that the simulation identification representation service processing request belongs to the simulation calling request, the processing of the service to be processed is completed through message simulation, and the target simulation information is obtained by respectively matching the service information to be processed with each preset rule in the simulation configuration information, so that an unavailable interface of a peripheral system can be supported, and the progress of system development and testing is guaranteed.

FIG. 3 schematically illustrates an example schematic diagram of a simulated call request handling process according to an embodiment of this disclosure.

As shown in fig. 3, in response to receiving a service processing request from a calling system, the service processing request may include pending service information 301, and the pending service information 301 may include an interface identifier 301_1. Interface configuration information 302 may be obtained from the service processing request, and interface configuration information 302 may include a simulation identifier 302_1.

Under the condition that the simulation identifier 302_1 represents that the service processing request belongs to the simulation calling request, the simulation configuration information 303 can be acquired according to the interface identifier 301_1. The simulation configuration information 303 may include at least one preset rule, and each preset rule in the at least one preset rule includes a preset field identifier. For example, preset field identification 303_1, preset field identification 303 _2., preset field identification 303 u _, preset field identification 303 u N, N may be an integer greater than 1, N ∈ {1,2, \8230; (N-1), N }.

The service information 301 to be processed may be respectively matched with preset field identifiers 303_1, 303_2 and 8230, 303_n and 8230, and 303 _N. In a case that it is determined that the pending service information 301 is successfully matched with the target preset field identifier 304, a preset rule corresponding to the target preset field identifier 304 may be determined as the target preset rule 305. Simulation information corresponding to the target preset rule 305 is determined as target simulation information 306.

After determining the target simulation information 306, the target simulation information 306 may be sent to a calling system 307 to complete processing of the business to be processed.

According to the embodiment of the present disclosure, the interface configuration information further includes a to-be-called system identifier, a to-be-called interface identifier, an association relationship between the to-be-called interfaces, and a request packet format conversion rule and a processing result packet format conversion rule, which are respectively corresponding to at least one to-be-called interface.

According to the embodiment of the disclosure, the interface configuration information may further include a communication protocol of the interface to be called. The communication protocol of the interface to be called can provide communication support for the internet connecting different operating systems and different hardware architectures. The communication protocol of the interface to be called may include any one of the following: HTTP (Hypertext Transfer Protocol), RPC (Remote Procedure Call Protocol), socket (Socket), and the like.

According to an embodiment of the present disclosure, the request packet format conversion rule and the processing result packet format conversion rule may include a format for data transmission and exchange between the server and the client. The request message format conversion rule and the processing result message format conversion rule may include any one of the following: XML (EXtensible Markup Language), JSON (Java Script Object Notification), and the like.

According to the embodiment of the disclosure, the conversion of the message format can be completed by configuring different request message format conversion rules and processing result message format conversion rules, so as to interface different system interfaces and realize the adaptation between different interfaces. Alternatively, different request message format conversion rules and processing result message format conversion rules can be configured to support extension of complex parameter conversion, such as error code mapping, dictionary value conversion of interest rate and currency, and the like.

According to an embodiment of the present disclosure, the service processing method 200 may further include the following operations.

And under the condition that the simulation identification representation service processing request belongs to the direct calling request, analyzing the service information to be processed to obtain the analyzed service information to be processed. And converting the analyzed to-be-processed service information according to the request message format conversion rule to obtain the converted to-be-processed service information. And sending the converted to-be-processed service information to an interface of the to-be-called system according to the to-be-called system identifier, the to-be-called interface identifier and the incidence relation. And receiving the converted service processing result from the interface of the system to be called. And converting the received service processing result according to the format conversion rule of the processing result message to obtain a service processing result to be returned. And returning the service processing result to be returned to the calling system.

According to the embodiment of the disclosure, the analyzed to-be-processed service information can be converted according to the target message format, that is, the message format of each to-be-called interface, so as to obtain the converted to-be-processed service information.

According to the embodiment of the disclosure, the service processing method can also support the extension class, and the extension class can be called through instantiation to complete the processing of the complex interface. The extension classes may include extension classes that call multiple interfaces simultaneously, extension classes that support multi-interface transactions, extension classes that support interface exception handling, and the like.

According to the embodiment of the disclosure, the interface general routing can be realized by reading the interface configuration information to support the multi-service combination of the circular scheduling. Whether other interfaces are continuously called can be determined according to the association relation of the interfaces to be called, and return messages of all the interfaces in the association relation can be combined into a service processing result.

According to the embodiment of the disclosure, when the association relationship of the interface to be called includes serial calling, sending the converted to-be-processed service information to the interface of the system to be called according to the interface configuration information and the association relationship may include the following operations.

And determining an initial interface to be called and a termination interface to be called according to the association relation. And determining a request message format conversion rule of the initial interface to be called according to the interface configuration information. And converting the service information to be processed according to the request message format conversion rule of the initial interface to be called to obtain the converted service information to be processed. And sending the converted to-be-processed service information to the initial to-be-called interface according to the to-be-called interface identifier. And receiving a returned candidate service processing result from the starting to-be-called interface. And determining a request message format conversion rule for terminating the interface to be called according to the interface configuration information. And converting the candidate service processing result according to the request message format conversion rule for terminating the interface to be called to obtain the converted candidate service result to be processed. And sending the converted candidate service processing result to the interface to be called.

According to the embodiment of the disclosure, receiving the service processing result returned from the interface to be called may include the following operations.

And receiving a service processing result returned by the interface to be called.

According to the embodiment of the disclosure, under the condition that the incidence relation of the interface to be called comprises serial calling, the incidence relation can be characterized as A1-A2-A3, the starting interface to be called can be determined as A1, and the ending interface to be called is determined as A3.

In this case, the to-be-processed service information is converted according to the request message format conversion rule of the initial to-be-called interface A1, and the converted to-be-processed service information is sent to the initial to-be-called interface A1, so that the initial to-be-called interface A1 processes the converted to-be-processed service information to obtain an initial service processing result. And then, converting the initial service processing result according to the request message format conversion rule of the interface A2 to be called, and sending the converted initial service processing result to the interface A2 to be called so that the interface A2 to be called can process the converted initial service processing result to obtain a candidate service processing result. And then, converting the candidate service processing result according to the request message format conversion rule of the interface A3 to be called, and sending the converted candidate service processing result to the interface A3 to be called so as to facilitate the interface A3 to be called to terminate processing the converted candidate service processing result and obtain a service processing result. And converting the service processing result according to the processing result message format conversion rule to obtain the service processing result to be returned.

According to the embodiment of the disclosure, when the association relationship of the interface to be called includes parallel calling, sending the converted to-be-processed service information to the interface of the system to be called according to the interface configuration information and the association relationship may include the following operations.

And determining a request message format conversion rule and a processing result message format conversion rule of each interface to be called according to the interface configuration information. And converting the service information to be processed according to the request message format conversion rule of each interface to be called to obtain the converted service information to be processed. And sending each converted to-be-processed service information to the to-be-called interfaces respectively corresponding to the to-be-called service identifications in parallel.

According to an embodiment of the disclosure, receiving the service processing result from the interface to be called may include the following operations.

According to the embodiment of the disclosure, in the case that the association of the interface to be called includes parallel calling, the association may be characterized as B1 and B2.

In this case, the service information to be processed is converted according to the request message format conversion rules corresponding to the interfaces B1 and B2 to be called, so as to obtain the converted service processing information C1 and C2. And then, the converted service processing information C1 is sent to an interface B1 to be called and the converted service processing information C2 is sent to an interface B2 to be called in parallel, and candidate service processing results from the interface B1 to be called and the interface B2 to be called are received in parallel. And converting the candidate service processing results of the interfaces B1 and B2 to be called according to the processing result message format conversion rule to obtain the service processing result to be returned.

According to the embodiment of the disclosure, the to-be-processed service information and the service processing result can be encrypted and decrypted based on the encryption and decryption algorithm. The encryption and decryption algorithm may include at least one of: symmetric encryption algorithms and asymmetric encryption algorithms.

According to an embodiment of the present disclosure, a symmetric encryption algorithm may include, for example: advanced Encryption Standard (AES), data Encryption Standard (DES), blowfish Algorithm, international Data Encryption Algorithm (IDEA), RC5 block cipher Algorithm, RC6 block cipher Algorithm, and the like. Asymmetric encryption algorithms may include, for example: RSA algorithm, elgamal algorithm, knapsack algorithm, rabin algorithm, D-H algorithm, elliptic curve cryptography algorithm, etc.

According to the embodiment of the disclosure, under the condition that the simulation identifier representation service processing request is determined to belong to the direct calling request, the processing of the service to be processed is completed according to the system identifier to be called, the interface identifier to be called and the incidence relation, and because the incidence relation of serial calling and/or parallel calling can be set, different interfaces can be adapted through interface configuration information, so that the link of code development is avoided, the efficiency of data conversion and transmission between different system interfaces is ensured, and the efficiency of service processing is improved.

FIG. 4 schematically shows an example schematic of a direct Call request handling process according to an embodiment of the disclosure.

As shown in fig. 4, in response to receiving a service processing request from a calling system, the service processing request may include pending service information 401, and the pending service information 401 may include an interface identifier 401_1. Interface configuration information 402 can be obtained according to the service processing request, and the interface configuration information 402 can include a simulation identifier 402_1, a request message format conversion rule 402_2, a system identifier 402_3 to be called, an interface identifier 402_4 to be called, an association relation 402_5 of the interface to be called, and a processing result message format conversion rule 402_6.

Under the condition that it is determined that the simulation identifier 402_1 represents that the service processing request belongs to the direct call request, the service information to be processed 401 may be analyzed to obtain analyzed service information to be processed 403. And converting the analyzed to-be-processed service information 403 according to the request message format conversion rule 402_2 to obtain converted to-be-processed service information 404. The interface 405 to be called can be determined according to the association relationship 402_3 between the system identifier 402 to be called, the interface identifier 402 to be called 402_4 and the interface 402 to be called, and the converted information 404 of the service to be processed is sent to the interface 405 of the system to be called, so that the interface 405 of the system to be called processes the service to be processed to obtain a service processing result 406. After the service processing result 406 is obtained, the service processing result 406 may be converted according to the processing result message format conversion rule 402_6 to obtain a converted service processing result 407.

The above is only an exemplary embodiment, but is not limited thereto, and may also include other service processing methods known in the art as long as service processing can be implemented.

Fig. 5 schematically shows a block diagram of a traffic processing device according to an embodiment of the present disclosure.

As shown in fig. 5, the service processing apparatus 500 may include a first obtaining module 501, a second obtaining module 502, a matching module 503, and a first sending module 504.

The first obtaining module 501 is configured to, in response to receiving a service processing request from a calling system, obtain a simulation identifier and interface configuration information according to an interface identifier in the service processing request. The service processing request comprises to-be-processed service information corresponding to the to-be-processed service, the to-be-processed service information comprises an interface identifier, the interface identifier is used for identifying a to-be-called interface corresponding to the to-be-processed service, and the simulation identifier and the interface configuration information are associated with the interface identifier.

A second obtaining module 502, configured to obtain the simulation configuration information according to the interface identifier when it is determined that the simulation identifier representation service processing request belongs to the simulation call request. The simulation configuration information includes at least one preset rule and simulation information corresponding to each preset rule in the at least one preset rule.

The matching module 503 is configured to match the service information to be processed with each preset rule, respectively, to obtain target simulation information.

The first sending module 504 is configured to return the target simulation information to the calling system, so as to complete processing of the service to be processed.

According to an embodiment of the present disclosure, the matching module 503 may include a first matching unit, a first determining unit, and a second determining unit.

And the first matching unit is used for respectively matching the service information to be processed with each preset field identifier in the at least one preset field identifier.

The first determining unit is configured to determine, as a target preset rule, a preset rule corresponding to a target preset field identifier when it is determined that the to-be-processed service information is successfully matched with the target preset field identifier in the at least one preset field identifier.

And the second determining unit is used for determining the simulation information corresponding to the target preset rule as the target simulation information.

According to an embodiment of the present disclosure, the matching module 503 may further include a third determining unit.

And the third determining unit is used for determining the preset simulation information as the target simulation information under the condition that the service information to be processed is determined not to be successfully matched with each preset field identifier.

According to the embodiment of the present disclosure, the interface configuration information further includes a system identifier to be called, an interface identifier to be called, an association relationship between the interfaces to be called, and a request packet format conversion rule and a processing result packet format conversion rule corresponding to each interface to be called, respectively, corresponding to at least one interface to be called.

According to an embodiment of the present disclosure, the service processing apparatus 500 may further include a parsing module, a first converting module, a second transmitting module, and a receiving module.

And the analysis module is used for analyzing the service information to be processed under the condition that the simulation identifier representation service processing request is determined to belong to the direct calling request, so as to obtain the analyzed service information to be processed.

And the first conversion module is used for converting the analyzed to-be-processed service information according to the request message format conversion rule to obtain the converted to-be-processed service information.

And the second sending module is used for sending the converted to-be-processed service information to the to-be-called interface of the to-be-called system according to the interface configuration information and the association relation.

And the receiving module is used for receiving the converted service processing result from the interface of the system to be called.

And the second conversion module is used for converting the received service processing result according to the processing result message format conversion rule to obtain the service processing result to be returned.

And the return module is used for returning the service processing result to be returned to the calling system.

According to the embodiment of the disclosure, in the case that the association relationship of the interface to be called includes serial call, the second sending module may include a fourth determining unit, a fifth determining unit, a first converting unit, a first sending unit, a first receiving unit, a sixth determining unit, a second converting unit, and a second sending unit.

And the fourth determining unit is used for determining the interface to be called initially and the interface to be called finally according to the association relation.

And the fifth determining unit is used for determining a request message format conversion rule of the initial interface to be called according to the interface configuration information.

And the first conversion unit is used for converting the service processing request of the service information to be processed according to the request message format conversion rule of the initial interface to be called to obtain the converted service information to be processed.

And the first sending unit is used for sending the converted to-be-processed service information to the initial to-be-called interface according to the to-be-called interface identifier.

And the first receiving unit is used for receiving the converted candidate service processing result from the starting interface to be called.

And a sixth determining unit, configured to determine, according to the interface configuration information, to terminate the request packet format conversion rule to be invoked and to terminate the processing result packet format conversion rule.

And the second conversion unit is used for converting the candidate service processing result according to the request message format conversion rule for terminating the interface to be called, so as to obtain the converted candidate service result to be processed.

And the second sending unit is used for sending the converted candidate service processing result to the interface to be called.

According to an embodiment of the present disclosure, the receiving module may include a second receiving unit.

And the second receiving unit is used for receiving the service processing result returned by the interface to be called.

According to the embodiment of the disclosure, in the case that the association relationship of the interface to be called includes a parallel call, the second sending module may include a seventh determining unit, a third converting unit, and a third sending unit.

And the seventh determining unit is used for determining the request message format conversion rule and the processing result message format conversion rule of each interface to be called according to the interface configuration information.

And the third conversion unit is used for converting the service information to be processed according to the request message format conversion rule of each interface to be called to obtain the converted service information to be processed. And the third sending unit is used for sending each converted to-be-processed service information to the to-be-called interfaces respectively corresponding to the to-be-called interface identifiers in parallel.

According to an embodiment of the present disclosure, the receiving module may include a third receiving unit.

And the third receiving unit is used for receiving the service processing result from the interface to be called in parallel.

Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or by any other reasonable means of hardware or firmware for integrating or packaging a circuit, or by any one of or a suitable combination of any of software, hardware, and firmware. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.

For example, any number of the first obtaining module 501, the second obtaining module 502, the matching module 503 and the first sending module 504 may be combined and implemented in one module/unit/sub-unit, or any one of the modules/units/sub-units may be split into multiple modules/units/sub-units. Alternatively, at least part of the functionality of one or more of these modules/units/sub-units may be combined with at least part of the functionality of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to an embodiment of the present disclosure, at least one of the first obtaining module 501, the second obtaining module 502, the matching module 503 and the first sending module 504 may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementations of software, hardware and firmware, or implemented by a suitable combination of any of them. Alternatively, at least one of the first obtaining module 501, the second obtaining module 502, the matching module 503 and the first sending module 504 may be at least partly implemented as a computer program module, which when executed may perform a corresponding function.

It should be noted that, the service processing apparatus portion in the embodiment of the present disclosure corresponds to the service processing method portion in the embodiment of the present disclosure, and the description of the service processing apparatus portion specifically refers to the service processing method portion, which is not described herein again.

Fig. 6 schematically shows a block diagram of an electronic device adapted to implement a traffic processing method according to an embodiment of the present disclosure. The electronic device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 6, the computer electronic device 600 according to the embodiment of the present disclosure includes a processor 601 which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage section 609 into a Random Access Memory (RAM) 603. Processor 601 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 601 may also include on-board memory for caching purposes. Processor 601 may include a single processing unit or multiple processing units for performing different actions of a method flow according to embodiments of the disclosure.

In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 600 are stored. The processor 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. The processor 601 performs various operations of the method flows according to embodiments of the present disclosure by executing programs in the ROM 602 and/or RAM 603. Note that the programs may also be stored in one or more memories other than the ROM 602 and RAM 603. The processor 601 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.

Electronic device 600 may also include input/output (I/O) interface 605, input/output (I/O) interface 605 also connected to bus 604, according to an embodiment of the present disclosure. The electronic device 600 may also include one or more of the following components connected to the I/O interface 605: an input portion 606 including a keyboard, a mouse, and the like; an output portion 607 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. A driver 610 is also connected to the I/O interface 605 as needed. A removable medium 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 610 as necessary, so that a computer program read out therefrom is mounted in the storage section 608 as necessary.

According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 609, and/or installed from the removable medium 611. The computer program, when executed by the processor 601, performs the above-described functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.

According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. Examples may include, but are not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM 602 and/or RAM 603 described above and/or one or more memories other than the ROM 602 and RAM 603.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method provided by embodiments of the present disclosure, when the computer program product is run on an electronic device, the program code being configured to cause the electronic device to implement the business processing method provided by embodiments of the present disclosure.

The computer program, when executed by the processor 601, performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure. The systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed in the form of a signal on a network medium, downloaded and installed through the communication section 609, and/or installed from the removable medium 611. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In situations involving remote computing devices, the remote computing devices may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to external computing devices (e.g., through the internet using an internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

The embodiments of the present disclosure are described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims

1. A service processing method comprises the following steps:

responding to a received service processing request from a calling system, and acquiring a simulation identifier and interface configuration information according to an interface identifier in the service processing request, wherein the service processing request comprises to-be-processed service information corresponding to-be-processed service, the to-be-processed service information comprises the interface identifier, the interface identifier is used for identifying an interface to be called corresponding to the to-be-processed service, and the simulation identifier and the interface configuration information are associated with the interface identifier;

and returning the target simulation information to the calling system so as to finish the processing of the service to be processed.

2. The method of claim 1, wherein each preset rule of the at least one preset rule includes a preset field identification;

the step of respectively matching the service information to be processed with each preset rule to obtain target simulation information comprises:

and determining simulation information corresponding to the target preset rule as the target simulation information.

3. The method of claim 2, further comprising:

4. The method according to any one of claims 1 to 3, wherein the interface configuration information further includes a system identifier to be called, an interface identifier to be called, an association relationship of interfaces to be called, which correspond to at least one interface to be called, a request packet format conversion rule and a processing result packet format conversion rule, which correspond to each interface to be called.

5. The method of claim 4, further comprising:

under the condition that the simulation identification represents that the service processing request belongs to the direct calling request, analyzing the service information to be processed to obtain analyzed service information to be processed;

according to the interface configuration information and the incidence relation, sending the converted to-be-processed service information to a to-be-called interface of the to-be-called system;

receiving a service processing result returned by the interface to be called;

converting the received service processing result according to the format conversion rule of the processing result message to obtain a service processing result to be returned; and

6. The method of claim 5, wherein, in the case that the associative relationship of the interface to be called comprises a serial call,

the sending the converted to-be-processed service information to the to-be-called interface of the to-be-called system according to the interface configuration information and the association relation comprises:

converting the service information to be processed according to the request message format conversion rule of the initial interface to be called to obtain the converted service information to be processed;

sending the converted to-be-processed service information to the initial to-be-called interface according to the to-be-called interface identifier;

receiving a candidate service processing result returned by the starting interface to be called;

determining to terminate a request message format conversion rule to be called and a processing result message format conversion rule according to the interface configuration information;

converting the candidate service processing result according to the request message format conversion rule for terminating the interface to be called to obtain a converted candidate service result to be processed; and

sending the converted candidate to-be-processed service information to the interface for terminating to be called;

the receiving the service processing result returned from the interface to be called comprises:

7. The method of claim 5, wherein, in the event that the associative relationship of the interface to be invoked comprises a parallel call,

determining a request message format conversion rule and a processing result message format conversion rule of each interface to be called according to the interface configuration information;

converting the service information to be processed according to the request message format conversion rule of each interface to be called to obtain the converted service information to be processed; and

sending each converted to-be-processed service information to the to-be-called interfaces respectively corresponding to the to-be-called interface identifications in parallel;

the receiving the service processing result returned by the interface to be called comprises:

and receiving the service processing result from the interface to be called in parallel.

8. The method of any of claims 1-7, wherein the interface identification, the interface configuration information, and the simulation configuration information are stored in association in a database.

9. A traffic processing apparatus, comprising:

the system comprises a first acquisition module, a first processing module and a second acquisition module, wherein the first acquisition module is used for responding to a received service processing request from a calling system and acquiring a simulation identifier and interface configuration information according to an interface identifier in the service processing request, the service processing request comprises to-be-processed service information corresponding to the to-be-processed service, the to-be-processed service information comprises the interface identifier, the interface identifier is used for identifying a to-be-called interface corresponding to the to-be-processed service, and the simulation identifier and the interface configuration information are associated with the interface identifier;

the matching module is used for respectively matching the service information to be processed with each preset rule to obtain target simulation information; and

and the first sending module is used for returning the target simulation information to the calling system so as to complete the processing of the service to be processed.

10. An electronic device, comprising:

one or more processors;

a memory to store one or more instructions that,

wherein the one or more instructions, when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-8.

11. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to carry out the method of any one of claims 1 to 8.

12. A computer program product comprising computer executable instructions for implementing the method of any one of claims 1 to 8 when executed.