Note : Les descriptions sont présentées dans la langue officielle dans laquelle elles ont été soumises.
INTERFACE MESSAGE CONVERSION METHOD, DEVICE, AND SYSTEM
Technical Field
[0001] The present invention relates to the field of application programming
interface adaptation
technologies, in particular, to a method, a device, and a system for
converting interface messages.
Background
[0002] An application programming interface (API) is an intermedium using a
set of pre-set definitions,
programs, and agreements to achieve communication amongst applications.
Currently, user operations
such as information query and data uploading normally require APIs for command
conversion between
the service request end and the service providing end, wherein both the
service request end and the
service providing end are supposed to use the same interface component
protocol (known as an interface
message). However, in practical scenarios, sometimes the service request end
adopts a customized
interface component protocol, wherein the described interface component
protocol is different from the
interface component protocol of the service providing end, leading to
difficulty of matching the interface
between the service request end and the service providing end. Therefore, a
conversion of either the
interface component protocol of the service request end or the interface
component protocol of the service
providing end is required for consistency and data exporting. Hence, interface
message conversion
techniques are in demand.
[0003] In the current technologies, the interface message conversion mainly
adopts two methods,
wherein one method is to develop customized interface service by hard coding
of the service providing
end based on the customized interface specifications of the service request
end; and the other method is to
construct data transmission between the customized platform of the service
request end and the service
providing end according to a standard API open-source interface component
protocol of the service
providing end. However, in the first forementioned method, different massage
formats and customized
development and data conversion of the file specifications by the service
request end lead to little
reproducibility with a long development period and high costs for backstage
support. On the other hand,
in the second forementioned method with standardized interface service for the
service request end, the
development costs for the service request end are reduced, although the costs
for system modification and
development of the service providing end are increased, bringing inconvenience
to the service providing
end.
Summary
1
Date Recue/Date Received 2021-10-18
[0004] Aiming at solving the current technical problems, a method, a device,
and a system for interface
message conversion are provided in the present invention. The described
technical proposal consists of
the following:
[0005] From the first perspective, an interface message conversion method is
provided in the present
invention, comprising:
[0006] acquiring a target interface corresponding to a conversion-pending
interface;
[0007] based on the described target interface, matching a target field with a
conversion-pending field in
the conversion-pending interface message;
[0008] based on the described conversion-pending field and the described
target field, generating a field
mapping instruction; and
[0009] mapping the described conversion-pending field to the described target
field according to the
described field mapping instruction.
[0010] Furthermore, the target field is matched with a conversion-pending
field in the conversion-
pending interface message based on the described target interface, by means
of:
[0011] based on the described target interface, calling a corresponding
parameter table for the described
target interface; and
[0012] matching the described conversion-pending field with the described
parameter table of the target
interface, to acquire the described target field.
[0013] Furthermore, the described target field is acquired, by means of:
[0014] acquiring a message structure tree based on the described message of
the conversion-pending
interface, wherein the nodes of the described message structure tree are the
fields in the described
conversion-pending message; and
[0015] identifying the fields corresponding to the nodes in the described
message structure tree selected
by the user as the described conversion-pending fields.
[0016] Furthermore, the described conversion-pending interface messages
include request parameter
message or returning parameter message.
[0017] Furthermore, the described method further includes:
[0018] where if a command of parsing the field value of the described
conversion-pending field is
received, acquiring field-value parsing rules;
[0019] based on the user selected field-value parsing rules, generating a
parsing command; and
[0020] parsing the field value of the described conversion-pending field
according to the described
parsing command.
[0021] Furthermore, the described method further includes:
2
Date Recue/Date Received 2021-10-18
[0022] matching a target exception code for a received conversion-pending
exception code based on the
described target interface;
[0023] generating an exception code mapping instruction based on the described
conversion-pending
exception code and the described target exception code; and
[0024] converting the described conversion-pending exception code to the
described target exception
code according to the described exception code mapping instruction.
[0025] Furthermore, a target exception code is matched for a received
conversion-pending exception
code based on the described target interface, by means of:
[0026] calling the associated target interface exception code table based on
the described target interface;
and
[0027] matching the described conversion-pending field with the described
target interface exception
code table, to acquire the described target exception code.
[0028] Furthermore, the target interface corresponding to the described
conversion-pending interface is
acquired, by means of:
[0029] based on the user account, acquiring the correspondence between the
described conversion-
pending interface and the described target interface, to acquire the described
target interface
corresponding to the described conversion-pending interface according to the
described correspondence;
and
[0030] procedures before acquiring the described target interface
corresponding to the described
conversion-pending interface, consisting of:
100311 acquiring conversion-pending interface information corresponding to the
conversion-pending
interface message, and calling user interface information linked with the
described user account; and
[0032] comparing the described conversion-pending interface message and the
described user interface
information, and yielding a successful verification where if the information
is consistent.
[0033] From the second perspective, an interface message conversion device is
provided in the present
invention, comprising:
[0034] a target interface acquisition module, configured to acquire a target
interface corresponding to a
conversion-pending interface;
[0035] a matching module, configured to match a target field with a conversion-
pending field in the
conversion-pending interface message based on the described target interface;
[0036] a conversion command generation module, configured to generate a field
mapping instruction
based on the described conversion-pending field and the described target
field; and
[0037] a field conversion module, configured to map the described conversion-
pending field to the
described target field according to the described field mapping instruction.
3
Date Recue/Date Received 2021-10-18
[0038] Furthermore, the described field conversion module further includes:
[0039] a calling module, configured to call a corresponding parameter table
for the described target
interface based on the described target interface; and
[0040] a target field acquisition module, configured to acquire the described
target field by matching the
described conversion-pending field with the described parameter table of the
target interface.
[0041] Furthermore, the described field conversion module further includes:
[0042] a message structure tree determination module, configured to acquire a
message structure tree
based on the described message of the conversion-pending interface, wherein
the nodes of the described
message structure tree are the fields in the described conversion-pending
message; and
[0043] a conversion-pending field determination module, configured to identify
the fields corresponding
to the nodes in the described message structure tree selected by the user as
the described conversion-
pending fields.
[0044] Furthermore, the described conversion-pending interface messages
include request parameter
message or returning parameter message.
[0045] Furthermore, the described device further includes:
[0046] a field value parsing rules acquisition module, configured to acquire
field-value parsing rules
where if a command of parsing the field value of the described conversion-
pending field is received;
[0047] a parsing command generation module, configured to generate a parsing
command based on the
user selected field-value parsing rules; and
[0048] a field value conversion module, configured to parse the field value of
the described conversion-
pending field according to the described parsing command.
[0049] Furthermore, the described device further includes:
[0050] a target exception code matching module, configured to match a target
exception code for a
received conversion-pending exception code based on the described target
interface;
[0051] an exception code mapping instruction generation module, configured to
generate an exception
code mapping instruction based on the described conversion-pending exception
code and the described
target exception code; and
[0052] a target exception code matching module, configured to convert the
described conversion-
pending exception code to the described target exception code according to the
described exception code
mapping instruction.
[0053] Furthermore, the target exception code matching module is configured to
call the associated
target interface exception code table based on the described target interface;
and
[0054] match the described conversion-pending field with the described target
interface exception code
table, to acquire the described target exception code.
4
Date Recue/Date Received 2021-10-18
[0055] Furthermore, the described target interface acquisition module is
configured to acquire the
correspondence between the described conversion-pending interface and the
described target interface
based on the user account, then acquire the described target interface
corresponding to the described
conversion-pending interface according to the described correspondence; and
[0056] the described device further includes:
[0057] a user interface information acquisition module, configured to acquire
conversion-pending
interface information corresponding to the conversion-pending interface
message, and call user interface
information linked with the described user account.
[0058] A verification module, configured to compare the described conversion-
pending interface
message and the described user interface information, and yield a successful
verification where if the
information is consistent.
[0059] From the third perspective, a computer system is provided in the
present invention, comprising:
[0060] one or more processors; and
[0061] a memory connected to the described one or more processors, wherein the
described memory is
used to store program commands, for implementing the forementioned methods in
the first perspective
when the described program commands are executed on the described one or more
processors.
[0062] The technical proposal in the present invention provides benefits of:
[0063] 1. the technical proposal disclosed in the present invention acquires a
target interface linked with
a user account, followed by automated matching a target field for the target
interface based on the
conversion-pending interface code, to generate field mapping instruction,
wherein the field mapping
instruction is reproducible, wherein without involvement of the previous
project initiation via hard coding,
the present invention allows fast and effective communication with service
provider ends, to prevent
wasting research resources due to frequent requests of the side interface from
users; and
[0064] 2. the technical proposal disclosed in the present invention parses the
conversion-pending
message according to the message structure tree, to achieve visible management
for deployment,
providing better project flexibility with multi-project reproducibility,
wherein costs for development
resource and project maintenance are reduced and user address data accuracy
and completeness are
ensured, improving customer procurement efficiency.
Brief descriptions of the drawings
[0065] In order to make the technical strategies of the present invention
clearer, the accompanying
drawings for the present invention will be briefly introduced below.
Obviously, the following drawings in
the descriptions are only a portion of embodiments of the present invention.
Those skilled in the art are
Date Recue/Date Received 2021-10-18
able to generate other configurations according to the provided drawings
without requiring any creative
works.
[0066] Fig. 1 is a flow diagram of the interface message conversion method
provided in the present
invention.
[0067] Fig. 2 is a flow diagram of the method for interface message conversion
with an exception code
provided in the present invention.
[0068] Fig. 3 is a structure diagram of the interface message conversion
device provided in the present
invention.
[0069] Fig. 4 is a structure diagram of the computer system provided in the
present invention.
Detailed descriptions
[0070] In order to make the objective, the technical protocol, and the
advantages of the present invention
clearer, the present invention will be explained further in detail precisely
below with references to the
accompanying drawings. Obviously, the embodiments described below are only a
portion of
embodiments of the present invention and cannot represent all possible
embodiments. Based on the
embodiments in the present invention, the other applications by those skilled
in the art without any
creative works are falling within the scope of the present invention.
[0071] In order to ensure the process of internal procurement auctions being
open and transparent with
effective procurement, some large corporate clients will construct internal
procurement platforms,
wherein various levels of vendors participate in auctions and join the
platforms via means of e-commerce.
The systems for corporate and vendors allow data transmission along full
transaction chains such as
products, orders, logistics, customer service, account checking, and
invoicing, wherein the data
transmission is performed via API integration.
[0072] For a better management of multiple vendors with satisfying associated
policy and regulations for
internal procurement, the corporate clients will introduce a standard vendor
system API integration plan.
The integration plan includes detailed definitions of interface protocols,
submissions, data formats, URL
for each interface, interface input and output parameters, parameter type
requirement, message format,
and sample descriptions. However, the vendor APIs are generally customized,
inconsistent with the target
interface by the corporates. Therefore, the consistency between interface
messages from the vendor
systems and interface messages from the corporate clients' procurement
platform is required.
[0073] During the conversion process, great practical discrepancies exist
between the corporate clients'
requirements with the procurement platforms and services, including, but not
limited to, different
definitions and requirements for field standard of product name inputs and
outputs, field types, and
message structures, wherein the specifications should be standardized
according to user files. Based on
6
Date Recue/Date Received 2021-10-18
features of the vendor internal service and system, detailed requirements are
analyzed, followed by
project applications and development resource deployment, to implement an API
integration plan,
satisfying user requirements. The E-commerce integrates with the main process
via APIs, normally
related to 8 modules of products, price, inventory, orders, logistics, account
checking, and invoicing and
over 20 independent interfaces. With the interface component service, a closed-
loop transaction
information flow can be constructed. The described project requires at least
80 ¨ 100 people per day from
undertaking to launching, producing, and operating without counting for later
stage maintenance. Herein,
with limited research resources, the project may not be launched on time
according to user bidding
contracts, leading to credibility crisis and a great amount of default loss.
On the other hand, if the project
quality is declined due to aimless speeding-up, the system security for later
stage maintenance is put at
risk.
[0074] Therefore, in order to solve the problems of the current technologies,
a method, a device, and a
system for interface message conversion are provided in the present invention.
The detailed technical
proposal comprises:
[0075] As shown in Fig. 1, an interface message conversion method, comprises:
[0076] Si, acquiring a target interface corresponding to a conversion-pending
interface.
[0077] The forementioned target interface is selected at user registration and
linked with user accounts,
wherein multiple target interfaces can be selected. Therefore, the target
interface linked with the user
accounts can be acquired by one or more target interfaces.
[0078] S2, based on the described target interface, matching a target field
with a conversion-pending
field in the conversion-pending interface message.
[0079] In particular, for input parameters, the conversion-pending interface
message is a request
parameter message; and for out parameters, the conversion-pending interface
message is a returning
parameter message.
[0080] In an embodiment of the present invention, the described conversion-
pending field is S2 is
acquired by:
[0081] S21, acquiring a message structure tree based on the described message
of the conversion-
pending interface, wherein the nodes of the described message structure tree
are the fields in the described
conversion-pending message.
[0082] S22, identifying the fields corresponding to the nodes in the described
message structure tree
selected by the user as the described conversion-pending fields.
[0083] In particular, the forementioned identification of the conversion-
pending fields is fields to be
converted when the conversion-pending interface message is converted to the
target interface message.
7
Date Recue/Date Received 2021-10-18
Therefore, after identification of the conversion-pending fields, the user
only needs to determine a
conversion-pending interface and the target interface when the conversion is
executed.
[0084] In particular, the message structure tree is acquired by two means:
[0085] one method is parsing the conversion-pending interface message to the
message structure tree;
and
[0086] the other method is creating a father node for the conversion-pending
interface message, and
constructing nodes according to selected fields of conversion-pending
interface messages, to construct the
message structure tree step by step.
[0087] In an embodiment of the present invention, the step S2 includes:
[0088] S23, calling the associated target interface exception code table based
on the described target
interface.
[0089] S24, matching the described conversion-pending field with the described
target interface
exception code table, to acquire the described target exception code.
[0090] In particular, the forementioned target interface parameter table
contains target fields
corresponding to each conversion-pending field assigned by service personnel
according to the target
interface message.
100911 In an embodiment of the present invention, wherein the associated
target interface parameter table
is called according to the target interface, the described method comprises:
[0092] S231, identifying the target interface table by matching the interface
type of the target interface
and the target interface type table.
[0093] S232, identifying the target interface parameter table by matching the
interface name of the target
interface and the target interface table.
[0094] In particular, the target interface type table, the target interface
table, and the target interface
parameters are determined by the technical personnel according to the target
interface information, using
SQL for initialization, wherein SQL increment is performed for change
maintenance with the follow-up
changes.
[0095] S3, based on the described conversion-pending field and the described
target field, generating a
field mapping instruction.
[0096] In particular, the field mapping instruction contains the mapping
relationships between the
conversion-pending field and the target field, and the field mapping
instruction is stored in the databased
for reuse, so as to select a corresponding conversion-pending interface and a
target interface for upcoming
events.
[0097] S4, mapping the described conversion-pending field to the described
target field according to the
described field mapping instruction.
8
Date Recue/Date Received 2021-10-18
[0098] In particular, the step S4 performs the mapping from the conversion-
pending field to the target
field. All fields in the conversion-pending interface message can be mapping
converted in the same
manner, for consistency of the conversion-pending interface message and the
target interface message.
[0099] In an embodiment of the present invention, the forementioned method
further includes:
[0100] S5, where if a command of parsing the field value of the described
conversion-pending field is
received, acquiring field-value parsing rules;
[0101] S6, based on the user selected field-value parsing rules, generating a
parsing command; and
[0102] S7, parsing the field value of the described conversion-pending field
according to the described
parsing command.
[0103] In particular, after the forementioned identification of the conversion-
pending field from the step
S22, the user can further deploy the basic parameter information, the mapping
field information, and the
field value parsing rule information for the described conversion-pending
field.
[0104] In particular, the basic parameter information includes field name,
being a mandatory field or not,
being a number set or not, field type, input parameter sample and the field
descriptions. The field type can
be "String", "int", "long", "double", "object", etc.
[0105] The mapping field information includes one or more target fields
matched in the step S2.
[0106] The field value parsing rule information includes being parsed or not,
and field value parsing
rules.
[0107] The field value parsing rules at least include seven types of: basic
type conversion, mapping value
type conversion, conversion of basic number arrays to target number arrays,
conversion of "," separation
to target number arrays, date format conversion, number format conversion, and
arithmetic. The
descriptions of corresponding rules are as the following:
[0108] basic type conversion: for example, int, integer ¨> string, character
string, 123 ¨> "123".
[0109] Mapping value type conversion: such as converting a customized value to
a standard value, or
vice versa. For example, 0 ¨> false, and 1 ¨> true. The conversion value rules
should be configured; the
mapping standard value must be the enumerated type; manual input is not
supported for selecting values;
and recording enumerated values by the basic table can be chosen from the
configuration items.
[0110] Conversion of basic number arrays to target number arrays, as a
structure command conversion,
wherein the basic number array is converted to the target number array.
[0111] conversion of"," separation to target number arrays, as a structure
command conversion, wherein
the target data array is converted to the string split with comma separation.
[0112] Date format conversion, converting the date format from the user side
to a recognizable date
format by the target field. For example, yyyyMMddHHmmss "YYYY-MM-DD hh:mm:ss".
9
Date Recue/Date Received 2021-10-18
[0113] Number format conversion, converting data format of the user size to a
recognizable number
format by the target field, to ensure the number precision and decimal numbers
required from the user
size is consistent with the target interface.
[0114] Arithmetic, by input of constants, to perform arithmetic of the
selected field value and the
constants such as addition, subtraction, multiplying and division.
Field types Data Parsing rules
array or Basic type Mappingtype Conversion
Conversion Date format Number Arithmetic
not conversion conversion of basic of "," conversion
format
number separation to conversion
arrays to target
target number
number arrays
arrays
[0117] Character string x V V x V V
V V
Value x V V x x x V
V
Boolean x V V x x x x
x
x x x
Object x x x x
x
Character string V x x V x x x
x
Value V x x V x x x
x
Boolean V x x V x x x
x
x x x Object V x x x x
[0116] Table I
[0118] To clarify, the forementioned methods disclosed in steps Si ¨ S7 can be
applied to cases of
conversion-pending interface massages being request parameters or being return
parameters, wherein for
the returning parameters, the field value parsing rules are reversed with the
request parameters, including:
[0119] conversion of target number arrays to basic number arrays, conversion
of target number arrays to
"," separation, null-value judgement, setting fixed values, and conversion of
input parameters to output
parameters. The descriptions of corresponding rules are as the following:
[0120] conversion of target number arrays to basic number arrays,
corresponding to the rules of
"conversion of basic number arrays to target number arrays" for input
parameters, with reversed
conversion target value.
[0121] Conversion of target number arrays to "," separation, corresponding to
the rules of "Conversion
of basic number arrays to target number arrays" for input parameters, with
reversed conversion target
value.
[0122] Null-value judgement, for cases with no returning parameter fields at
the target interface,
returning successful or unsuccessful deployment according to the standard
eerorCode fields.
[0123] Setting fixed values, directly setting returning values for customizing
a certain interface field.
Date Recue/Date Received 2021-10-18
[0124] Conversion of input parameters to output parameters, identifying the
mapping item as the input
customized interface deployment; and for output parameters, the request field
value is directly returned
without any conversion rules for field values required.
[0125] The linkage logic of the data type and parsing rules is shown in Table
2 below. The number types
include: int, long, and double.
[0126] Table 2
Parsing rules
Conversion
Conversion
of target
Conversion
Data of target
Field Mapping number Date Number Setting
of input
array or Basic type number
types type arrays to format format Arithmetic
fixed parameters
not conversion arrays to
conversion basic conversion conversion
values to output
õ,õ
number
parameters
separation
arrays
Character
. v v . v v v v v v
. .
Value x V V x V V V V
Boolean x V V x x x x x V V
x x
Object x x x x x x x V
Character V x x V x x x V
x x
string
Value V x x V x x x V
x x
Boolean V x x V x x x V
x x
Object V x x x x x x x x V
[0128] In an embodiment of the present invention, the forementioned method
further includes
[0129] S8, matching a target exception code for a received conversion-pending
exception code based on
the described target interface;
[0130] S9, generating an exception code mapping instruction based on the
described conversion-pending
exception code and the described target exception code; and
[0131] S10, converting the described conversion-pending exception code to the
described target
exception code according to the described exception code mapping instruction.
[0132] In particular, the forementioned exception code is the returned code
for interface exceptions. The
exception code for the conversion-pending interface message may be
inconsistent with the exception code
of the target interface message. Therefore, a technical solution for the
exception code conversion is
provided in the present invention.
[0133] To clarify, as shown in Fig. 2, in an embodiment of the present
invention, the message conversion
for the request parameters is performed first, followed by the message
conversion for the returning
parameters, then the conversion for the exception code is performed lastly.
Before the conversion for the
returning parameters, the mandatory fields of the target interface are judged
for missing or omissions.
Where if missing or omitted fields are detected, constants are deployed to
fill, and where if no missing or
omitted field is detected, the returning parameter deployment processing is
directly operated. Similarly,
11
Date Recue/Date Received 2021-10-18
after the returning parameter conversion and before the exception code
conversion, the mandatory fields
of the target interface are further judged for missing or omissions.
[0134] In an embodiment of the present invention, the forementioned method
further includes:
[0135] acquiring the correspondence between the described conversion-pending
interface and the
described target interface based on the user account, to acquire the described
target interface
corresponding to the described conversion-pending interface according to the
described correspondence;
and
[0136] procedures before the step Si, consisting of:
[0137] acquiring conversion-pending interface information corresponding to the
conversion-pending
interface message, and calling user interface information linked with the
described user account.
[0138] In particular, the forementioned conversion-pending interface message
includes interface
affiliation users, interface types, interface name, and interface codes. The
user interface information is
acquired at user registration, and linked with the user account. The user
interface information includes
interface affiliation users, interface types, interface name, interface codes,
as well as interface descriptions
and input returning message format.
[0139] The conversion-pending interface message and the user interface
information are compared,
yielding a successful verification where if the information is consistent.
[0140] In particular, the forementioned comparison of the conversion-pending
interface message and the
user interface information is the verification of the user and the conversion-
pending interface message, to
prevent the problem of conversion-pending interface messages not conforming to
the user interface
message.
[0141] As shown in Fig. 3, based on the forementioned interface message
conversion method, an
interface message conversion device is provided in the present invention,
comprising a request parameter
message conversion module 31 and a returning parameter message conversion
module 32. Particularly,
the request parameter message conversion module 31 and the returning parameter
message conversion
module 32 are configured with the same structure, consisting of:
[0142] A target interface acquisition module 311, configured to acquire a
target interface corresponding
to a conversion-pending interface.
[0143] A matching module 312, configured to match a target field with a
conversion-pending field in the
conversion-pending interface message based on the described target interface.
[0144] A conversion command generation module 313, configured to generate a
field mapping
instruction based on the described conversion-pending field and the described
target field.
[0145] A field conversion module 314, configured to map the described
conversion-pending field to the
described target field according to the described field mapping instruction.
12
Date Recue/Date Received 2021-10-18
[0146] In an embodiment of the present invention, the described field
conversion module 314 further
includes:
[0147] A message structure tree determination module, configured to acquire a
message structure tree
based on the described message of the conversion-pending interface, wherein
the nodes of the described
message structure tree are the fields in the described conversion-pending
message.
[0148] A conversion-pending field determination module, configured to identify
the fields corresponding
to the nodes in the described message structure tree selected by the user as
the described conversion-
pending fields.
[0149] In particular, the detailed operation means of the forementioned
message structure tree
determination module can be parsing the conversion-pending interface message
to the message structure
tree; or can also be creating a father node for the conversion-pending
interface message, and construct
nodes according to selected fields of conversion-pending interface messages,
to construct the message
structure tree step by step.
[0150] In an embodiment of the present invention, the described field
conversion module 314 further
includes:
[0151] A calling module, configured to call a corresponding parameter table
for the described target
interface based on the described target interface.
[0152] A target field acquisition module, configured to acquire the described
target field by matching the
described conversion-pending field with the described parameter table of the
target interface.
[0153] In an embodiment of the present invention, the calling module
particularly configured to:
[0154] call the associated target interface exception code table based on the
described target interface;
and
[0155] match the described conversion-pending field with the described target
interface exception code
table, to acquire the described target exception code.
[0156] In an embodiment of the present invention, the forementioned device
further includes:
[0157] A field value parsing rules acquisition module 315, configured to
acquire field-value parsing rules
where if a command of parsing the field value of the described conversion-
pending field is received.
[0158] A parsing command generation module 316, configured to generate a
parsing command based on
the user selected field-value parsing rules.
[0159] A field value conversion module 317, configured to parse the field
value of the described
conversion-pending field according to the described parsing command.
[0160] In particular, specifications for the field value parsing rules of the
request parameter message and
the returning parameter message can be referred to the forementioned method
embodiments.
13
Date Recue/Date Received 2021-10-18
[0161] In an embodiment of the present invention, the forementioned device
further includes an
exception code conversion module 33, comprising:
[0162] a target exception code matching module 331, configured to match a
target exception code for a
received conversion-pending exception code based on the described target
interface.
[0163] In particular, the forementioned target exception code matching module
is configured to call the
associated target interface exception code table based on the described target
interface; and match the
described conversion-pending field with the described target interface
exception code table, to acquire the
described target exception code.
[0164] An exception code mapping instruction generation module 332, configured
to generate an
exception code mapping instruction based on the described conversion-pending
exception code and the
described target exception code.
[0165] A target exception code matching module 333, configured to convert the
described conversion-
pending exception code to the described target exception code according to the
described exception code
mapping instruction.
[0166] In an embodiment of the present invention, the target exception code
matching module 331 is
configured to acquire the correspondence between the described conversion-
pending interface and the
described target interface based on the user account, then acquire the
described target interface
corresponding to the described conversion-pending interface according to the
described correspondence.
[0167] The described device further includes:
[0168] a user interface information acquisition module 34, configured to
acquire conversion-pending
interface information corresponding to the conversion-pending interface
message, and call user interface
information linked with the described user account.
[0169] A user interface information acquisition module, configured to compare
the described
conversion-pending interface message and the described user interface
information, and yield a successful
verification where if the information is consistent.
[0170] Based on the forementioned method embodiment, a computer system is
provided by the present
invention, comprising:
[0171] one or more processors; and
[0172] a memory connected to the described one or more processors, wherein the
described memory is
used to store program commands, for performing the procedures of the
forementioned method in the first
perspective when the described program commands are executed on the described
one or more processors.
[0173] In particular, a schematic of the computer system structure, shown in
Fig. 4, comprises a
processor 410, a video display adapter 411, a disk driver 412, an input/output
connection port 413, an
internet connection port 414, and a memory 420. The forementioned processor
410, video display adapter
14
Date Recue/Date Received 2021-10-18
411, disk driver 412, input/output connection port 413, and internet
connection port 414 are connected
and communicated via the system bus control 430.
[0174] In particular, the processor 410 can adopt a universal CPU (central
processing unit), a
microprocessor, an ASIC (application specific integrated circuit) or the use
of one or more integrated
circuits. The processor is used for executing associated programmes to achieve
the technical strategies
provided in the present invention.
[0175] The memory 420 can adopt a read-only memory (ROM), a random access
memory (RAM), a
static memory, a dynamic memory, etc. The memory 420 is used to store the
operating system 421 for
controlling the electronic apparatus 400, and the basic input output system
(BIOS) 422 for controlling the
low-level operations of the electronic apparatus 400. In the meanwhile, the
memory can also store the
internet browser 424, data storage management system 424, the device label
information processing
system 425, etc. The described device label information processing system 425
can be a program to
achieve the forementioned methods and procedures in the present invention. In
summary, when the
technical strategies are performed via software or hardware, the codes for
associated programs are stored
in the memory 420, then called and executed by the processor 410.
[0176] The input/output connection port 413 is used to connect with the
input/output modules for
information input and output. The input/output modules can be used as
components that are installed in
the devices (not included in the drawings), or can be externally connected to
the devices to provide the
described functionalities. In particular, the input devices may include
keyboards, mouse, touch screens,
microphones, various types of sensors, etc. The output devices may include
monitors, speakers, vibrators,
signal lights, etc.
[0177] The internet connection port 414 is used to connect with a
communication module (not included
in the drawings), to achieve the communication and interaction between the
described device and other
equipment. In particular, the communication module may be connected by wire
connection (such as USB
cables or internet cables), or wireless connection (such as mobile data, WIFI,
Bluetooth, etc.)
[0178] The system bus control 430 include a path to transfer data across each
component of the device
(such as the processor 410, the video display adapter 411, the disk driver
412, the input/output connection
port 413, the internet connection port 414 and the memory 420).
[0179] Besides, the described electronic device 400 can access the collection
condition information from
the collection condition information database 441 via a virtual resource
object, so as for conditional
statements and other purposes.
[0180] To clarify, although the schematic of the forementioned device only
includes the processor 410,
the video display adapter 411, the disk driver 412, the input/output
connection port 413, the internet
connection port 414, the memory 420 and the system bus control 430, the
practical applications may
Date Recue/Date Received 2021-10-18
include the other necessary components to achieve successful operations. It is
comprehensible for those
skilled in the art that the structure of the device may comprise of less
components than that in the
drawings, to achieve successful operations.
[0181] By the forementioned descriptions of the applications and embodiments,
those skilled in the art
can understand that the present invention can be achieved by combination of
software and necessary
hardware platforms. Based on this concept, the present invention is considered
as providing the technical
benefits in the means of software products. The mentioned computer software
products are stored in the
storage media such as ROM/RAM, magnetic disks, compact disks, etc. The
mentioned computer software
products also include using several commands to have a computer device (such
as a personal computer, a
server, or a network device) to perform portions of the methods described in
each or some of the
embodiments in the present invention.
[0182] The embodiments in the description of the present invention are
explained step-by-step. The
similar contents can be referred amongst the embodiments, while the
differences amongst the
embodiments are emphasized. In particular, the system and the corresponding
embodiments have similar
contents to the method embodiments. Hence, the system and the corresponding
embodiments are
described concisely, and the related contents can be referred to the method
embodiments. The described
system and system embodiments are for demonstration only, where the components
that are described
separately can be physically separated or not. The components shown in
individual units can be physical
units or not. In other words, the mentioned components can be at a single
location or distributed onto
multiple network units. All or portions of the modules can be used to achieve
the purposes of
embodiments of the present invention based on the practical scenarios. Those
skilled in the art can
understand and apply the associated strategies without creative works.
[0183] The technical proposal in the present invention provides benefits of:
[0184] 1. the technical proposal disclosed in the present invention acquires a
target interface linked with
a user account, followed by automated matching a target field for the target
interface based on the
conversion-pending interface code, to generate field mapping instruction,
wherein the field mapping
instruction is reproducible, wherein without involvement of the previous
project initiation via hard coding,
the present invention allows fast and effective communication with service
provider ends, to prevent
wasting research resources due to frequent requests of the side interface from
users; and
[0185] 2. the technical proposal disclosed in the present invention parses the
conversion-pending
message according to the message structure tree, to achieve visible management
for deployment,
providing better project flexibility with multi-project reproducibility,
wherein costs for development
resource and project maintenance are reduced and user address data accuracy
and completeness are
ensured, improving customer procurement efficiency.
16
Date Recue/Date Received 2021-10-18
[0186] The forementioned contents of preferred embodiments of the present
invention shall not limit the
applications of the present invention. Therefore, all alterations,
modifications, equivalence, improvements
of the present invention fall within the scope of the present invention.
17
Date Recue/Date Received 2021-10-18
