Language selection

Search

Patent 3176864 Summary

Third-party information liability

Some of the information on this Web page has been provided by external sources. The Government of Canada is not responsible for the accuracy, reliability or currency of the information supplied by external sources. Users wishing to rely upon this information should consult directly with the source of the information. Content provided by external sources is not subject to official languages, privacy and accessibility requirements.

Claims and Abstract availability

Any discrepancies in the text and image of the Claims and Abstract are due to differing posting times. Text of the Claims and Abstract are posted:

  • At the time the application is open to public inspection;
  • At the time of issue of the patent (grant).
(12) Patent Application: (11) CA 3176864
(54) English Title: GENERAL-PURPOSE PROCESSING METHOD AND APPARATUS FOR DATA EXCHANGE
(54) French Title: PROCEDE ET APPAREIL DE TRAITEMENT UNIVERSEL DESTINES A L'INTERACTION DE DONNEES
Status: Deemed Abandoned
Bibliographic Data
(51) International Patent Classification (IPC):
  • G06F 17/00 (2019.01)
  • G06F 09/448 (2018.01)
(72) Inventors :
  • HUANG, WENHAO (China)
  • WU, TINGTING (China)
  • WU, HUIYANG (China)
  • ZHANG, ZHIYONG (China)
  • YANG, CHENGYING (China)
  • SUN, QIAN (China)
(73) Owners :
  • 10353744 CANADA LTD.
(71) Applicants :
  • 10353744 CANADA LTD. (Canada)
(74) Agent: JAMES W. HINTONHINTON, JAMES W.
(74) Associate agent:
(45) Issued:
(86) PCT Filing Date: 2019-09-29
(87) Open to Public Inspection: 2020-10-15
Examination requested: 2022-09-23
Availability of licence: N/A
Dedicated to the Public: N/A
(25) Language of filing: English

Patent Cooperation Treaty (PCT): Yes
(86) PCT Filing Number: PCT/CN2019/109110
(87) International Publication Number: CN2019109110
(85) National Entry: 2022-09-23

(30) Application Priority Data:
Application No. Country/Territory Date
201910280061.0 (China) 2019-04-09

Abstracts

English Abstract

Disclosed are a universal processing method and apparatus for data interaction, belonging to the technical field of big data. The method comprises: setting, according to a preset rule of a data interaction service, an initialization data parameter of the data interaction service (101); in a current usage scenario, invoking the data interaction service according to the initialization data parameter (102); sending a corresponding data request according to a difference data parameter corresponding to the current usage scenario (103); and carrying out, according to data returned regarding the data request, data processing required by the current usage scenario (104). By means of the universal processing method and apparatus for data interaction, the reusability, high efficiency and consistency of a code can be effectively improved, and the consistency between a method and a result of data interaction and functions such as version control, usage scenario extension, environment monitoring and error processing, are also achieved.


French Abstract

L'invention concerne un procédé et un appareil de traitement universel destinés à l'interaction de données, appartenant au domaine technique des mégadonnées. Le procédé consiste : à régler, selon une règle prédéfinie d'un service d'interaction de données, un paramètre de données d'initialisation du service d'interaction de données (101) ; dans un scénario d'utilisation actuel, à invoquer le service d'interaction de données en fonction du paramètre de données d'initialisation (102) ; à envoyer une demande de données correspondante en fonction d'un paramètre de données de différence correspondant au scénario d'utilisation actuel (103) ; et à exécuter, en fonction des données renvoyées concernant la demande de données, un traitement de données requis par le scénario d'utilisation actuel (104). Au moyen du procédé et de l'appareil de traitement universel destinés à l'interaction de données, la réutilisation, l'efficacité élevée et la cohérence d'un code peuvent être efficacement améliorées, et la cohérence entre un procédé et un résultat d'interaction de données et des fonctions telles que la commande de version, l'extension de scénario d'utilisation, la surveillance d'environnement et le traitement d'erreur sont également mises en uvre.

Claims

Note: Claims are shown in the official language in which they were submitted.


CA 03176864 2022-09-23
CLAIMS
What is claimed is:
1. A general-purpose processing method for data exchange, comprising:
according to predetermined rules for a data exchange service, setting up
initialization data
parameters for the data exchange service;
for a current use scenario, according to the initialization data parameters,
calling the data
exchange service;
according to differentiation data parameters corresponding to the current use
scenario, issuing a
corresponding data request; and
according to data returned in response to the data request, performing data
processing required
by the current use scenario.
2. The method of claim 1, wherein the step of according to predetermined rules
for a data
exchange service, setting up initialization data parameters comprises:
according to agreed rules for the data exchange service, setting up basic data
exchange incoming
parameters,
in which the basic data exchange incoming parameters include data exchange
basic addresses,
local encrypted data for recognizing user identities, identifiers for
recognizing user identities.
3. The method of claim 1, wherein before the step of according to
differentiation data parameters
corresponding to the current use scenario, issuing a corresponding data
request, the method
further comprises:
setting up markers for the differentiation data parameters of the specific
address information for
data exchange required by the current use scenario, and setting up delivery
parameter markers
for data exchange required by the current use scenario, and initializing them
into null objects.
4. The method of claim 3, wherein the step of according to differentiation
data parameters
Date Regue/Date Received 2022-09-23

CA 03176864 2022-09-23
corresponding to the current use scenario, issuing a corresponding data
request comprises:
filling in the differentiation data parameters corresponding to the current
use scenario, and filling
out the delivery parameters for data exchange required by the current use
scenario.
5. The method of any of claims 1 through 4, wherein the step of according to
data returned in
response to the data request, performing data processing required by the
current use scenario
comprises:
determining whether the data returned in response to the data request is
normal, and if yes,
returning logic processing corresponding to the normal data, or if no, further
monitoring the
current use scenario to see whether unusual processing is required, and if
unusual processing is
required, placing an unusual processing logic corresponding to the unusual
processing into
unusual callback.
6. A general-purpose processing apparatus for data exchange, comprising:
an initialization data parameter setting up module, for according to
predetermined rules for a data
exchange service, setting up initialization data parameters for the data
exchange service;
a data exchange service calling module, for a current use scenario, according
to the initialization
data parameters, calling the data exchange service;
a data request initiating module, for according to differentiation data
parameters corresponding
to the current use scenario, issuing a corresponding data request; and
a data processing module, for according to data returned in response to the
data request,
performing data processing required by the current use scenario.
7. The apparatus of claim 6, wherein the initialization data parameter setting
up module is for:
according to agreed rules for the data exchange service, setting up basic data
exchange incoming
parameters,
in which the basic data exchange incoming parameters include data exchange
basic addresses,
local encrypted data for recognizing user identities, identifiers for
recognizing user identities.
16
Date Regue/Date Received 2022-09-23

CA 03176864 2022-09-23
8. The apparatus of claim 6, wherein the apparatus further comprises
differentiation setting up
module, which is for:
before the data request initiating module issues a corresponding data request
according to
differentiation data parameters corresponding to the current use scenario,
setting up markers for
the differentiation data parameters of the specific address information for
data exchange required
by the current use scenario, and setting up delivery parameter markers for
data exchange required
by the current use scenario, and initializing them into null objects.
9. The apparatus of claim 8, wherein the data request initiating module is
for:
filling in the differentiation data parameters corresponding to the current
use scenario, and filling
out the delivery parameters for data exchange required by the current use
scenario.
10. The apparatus of any of claims 6 through 9, wherein the data processing
module is for:
determining whether the data returned in response to the data request is
normal, and if yes,
returning logic processing corresponding to the normal data, or if no, further
monitoring the
current use scenario to see whether unusual processing is required, and if
unusual processing is
required, placing an unusual processing logic corresponding to the unusual
processing into
unusual callback.
17
Date Regue/Date Received 2022-09-23

Description

Note: Descriptions are shown in the official language in which they were submitted.


CA 03176864 2022-09-23
GENERAL-PURPOSE PROCESSING METHOD AND APPARATUS FOR DATA
EXCHANGE
BACKGROUND OF THE INVENTION
Technical Field
[0001] The present invention relates to the technical field of big data, and
more particularly to a
general-purpose processing method for data exchange and its apparatus.
Description of Related Art
[0002] Conventionally, in data exchange, data are acquired by sending
particular enquiry
conditions through data interface according to practical use scenarios. The
known method,
however, is not favorable to data processing in scenarios of general-purpose
data
exchange, for example, prompting users with different error messages in
response to
different error state codes, and is favorable to unified version control of
data exchange
interfaces.
SUMMARY OF THE INVENTION
[0003] For addressing the issues of the prior art, embodiment of the present
invention provides
a general-purpose processing method for data exchange and its apparatus, which
effectively enhances reusability, efficiency, and consistency of codes, while
improving
consistency of the method and its results for data exchange, version control,
application
expansion, environment monitoring, and error processing. The technical schemes
used
are described below.
[0004] In a first aspect, the present invention provides a general-purpose
processing method for
data exchange, comprising: according to predetermined rules for a data
exchange service,
setting up initialization data parameters for the data exchange service; for a
current use
scenario, according to the initialization data parameters, calling the data
exchange service;
1
Date Regue/Date Received 2022-09-23

CA 03176864 2022-09-23
according to differentiation data parameters corresponding to the current use
scenario,
issuing a corresponding data request; and according to data returned in
response to the
data request, performing data processing required by the current use scenario.
[0005] Combined with the first aspect, in the first possible implementation,
the step of according
to predetermined rules for a data exchange service, setting up initialization
data
parameters comprises: according to agreed rules for the data exchange service,
setting up
basic data exchange incoming parameters, in which the basic data exchange
incoming
parameters include data exchange basic addresses, local encrypted data for
recognizing
user identities, identifiers for recognizing user identities.
[0006] Combined with the first aspect, in the second possible implementation,
before the step of
according to differentiation data parameters corresponding to the current use
scenario,
issuing a corresponding data request, the method further comprises: setting up
markers
for the differentiation data parameters of the specific address information
for data
exchange required by the current use scenario, and setting up delivery
parameter markers
for data exchange required by the current use scenario, and initializing them
into null
objects.
[0007] Combined with the second possible implementation of the first aspect,
in a third possible
implementation, the step of according to differentiation data parameters
corresponding to
the current use scenario, issuing a corresponding data request comprises:
filling in the
differentiation data parameters corresponding to the current use scenario, and
filling out
the delivery parameters for data exchange required by the current use
scenario.
[0008] Combined with any of the first through the third possible
implementations of the first
aspect, in the fourth through the sixth possible implementations, the step of
according to
data returned in response to the data request, performing data processing
required by the
current use scenario comprises: determining whether the data returned in
response to the
data request is normal, and if yes, returning logic processing corresponding
to the normal
data, or if no, further monitoring the current use scenario to see whether
unusual
processing is required, and if unusual processing is required, placing an
unusual
processing logic corresponding to the unusual processing into unusual
callback.
2
Date Regue/Date Received 2022-09-23

CA 03176864 2022-09-23
[0009] In a second aspect, the present invention provides a general-purpose
processing apparatus
for data exchange, the apparatus comprising: an initialization data parameter
setting up
module, for according to predetermined rules for a data exchange service,
setting up
initialization data parameters for the data exchange service; a data exchange
service
calling module, for a current use scenario, according to the initialization
data parameters,
calling the data exchange service; a data request initiating module, for
according to
differentiation data parameters corresponding to the current use scenario,
issuing a
corresponding data request; and a data processing module, for according to
data returned
in response to the data request, performing data processing required by the
current use
scenario.
[0010] Combined with the second aspect, in the first possible implementation,
the initialization
data parameter setting up module is for: according to agreed rules for the
data exchange
service, setting up basic data exchange incoming parameters, in which the
basic data
exchange incoming parameters include data exchange basic addresses, local
encrypted
data for recognizing user identities, identifiers for recognizing user
identities.
[0011] Combined with the second aspect, in the second possible implementation,
the apparatus
further comprises differentiation setting up module, which is for: before the
data request
initiating module issues a corresponding data request according to
differentiation data
parameters corresponding to the current use scenario, setting up markers for
the
differentiation data parameters of the specific address information for data
exchange
required by the current use scenario, and setting up delivery parameter
markers for data
exchange required by the current use scenario, and initializing them into null
objects.
[0012] Combined with the second possible implementation of the second aspect,
in the third
possible implementation, the data request initiating module is for: filling in
the
differentiation data parameters corresponding to the current use scenario, and
filling out
the delivery parameters for data exchange required by the current use
scenario.
[0013] Combined with any of the first through third possible implementations
of the second
aspect, in the fourth through sixth possible implementations, the data
processing module
is for: determining whether the data returned in response to the data request
is normal,
3
Date Regue/Date Received 2022-09-23

CA 03176864 2022-09-23
and if yes, returning logic processing corresponding to the normal data, or if
no, further
monitoring the current use scenario to see whether unusual processing is
required, and if
unusual processing is required, placing an unusual processing logic
corresponding to the
unusual processing into unusual callback.
[0014] The technical schemes of the embodiments of the present invention
provide the following
beneficial effects:
[0015] (1) Providing consistency: in the project creation stage, the disclosed
apparatus is
initialized according to the regulations agreed with the data providing party.
In practical
use scenarios, data requests can be easily initiated by calling the data
exchange service
so as to obtain data feedback results, thereby realizing consistency of the
data exchange
method and its results, and ensuring unified processing for input parameters
and retuned
data during data exchange between the front- and back-ends for developing the
project.
This in turn reduces repeated works for setting up and data processing in
practical use
scenarios. Use of unified packaging processing for input parameters and
returned data
during data exchange for the project simplifies development in terms of code,
step and
logic, and enhances reusability of project codes, consistency of operation,
centralization
of data exchange, and controllability of versions, leading to significantly
improved
development efficiency.
[0016] (2) Specific to version control: according to the prior-art data
exchange solutions, when
developing a system, the developer has to set up and process input parameters
and output
parameters separately for data exchange between the front- and back-ends
according to
the current use scenario. This is not only adverse to decoupling and reuse of
code
functions, but also makes it challenging to maintain consistency of the
project as a whole.
In other words, the prior-art solution is unable to provide unified processing
and unified
version control for data exchange. The present invention thus innovatively
introduces the
concept of version control, which makes it possible to call different versions
of data
according to practical use scenarios, thereby easily achieving version control
of data and
enabling data control adaptive to different scenarios and different
situations.
[0017] (3) Expanding applications: the present invention reserves calling
parameters to facilitate
4
Date Regue/Date Received 2022-09-23

CA 03176864 2022-09-23
providing custom parameters specific to practical use scenarios. With
different custom
parameters, some unusual types of requests can be handled, thereby expanding
its
application scope and satisfying use needs in more scenarios.
[0018] (4) Providing environment monitoring: the present invention allows
different data request
addresses to be configured for the development stage, the testing stage, and
online release
of the project, so as to automatically acquire data from the corresponding
data providing
party in practical use scenarios.
[0019] (5) Realizing error processing: the present invention provides an error
processing
mechanism, which processes error data as regulated by the rules, and reserves
use
scenarios where the error processing mechanism selectively performs error
callback
processing.
BRIEF DESCRIPTION OF THE DRAWINGS
[0020] To better illustrate the technical schemes as disclosed in the
embodiments of the present
invention, accompanying drawings referred in the description of the
embodiments below
are introduced briefly. It is apparent that the accompanying drawings as
recited in the
following description merely provide a part of possible embodiments of the
present
invention, and people of ordinary skill in the art would be able to obtain
more drawings
according to those provided herein without paying creative efforts, wherein:
[0021] FIG. 1 is a flowchart of a general-purpose processing method for data
exchange according
to Embodiment 1 of the present invention;
[0022] FIG. 2 is a flowchart of sub-steps of a step 104 in the method of
Embodiment 1; and
[0023] FIG. 3 is a structural diagram of a general-purpose processing
apparatus for data
exchange according to Embodiment 2 of the present invention.
DETAILED DESCRIPTION OF THE INVENTION
[0024] To make the foregoing objectives, features, and advantages of the
present invention
clearer and more understandable, the following description will be directed to
some
Date Regue/Date Received 2022-09-23

CA 03176864 2022-09-23
embodiments as depicted in the accompanying drawings to detail the technical
schemes
disclosed in these embodiments. It is, however, to be understood that the
embodiments
referred herein are only a part of all possible embodiments and thus not
exhaustive. Based
on the embodiments of the present invention, all the other embodiments can be
conceived
without creative labor by people of ordinary skill in the art, and all these
and other
embodiments shall be encompassed in the scope of the present invention. It is
to be noted
that, in the description of the present invention, "plural" or "multiple" when
used to
describe an object means there are more than two such objects, unless
otherwise specified
in the context.
[0025] The general-purpose processing method for data exchange and its
apparatus of the
embodiments of the present invention dynamically set parameters so as to
provide and
initialize custom parameters specific to a predetermined use scenario, so that
the use
scenario can, according to predetermined parameter rules, call the parameters,
thereby
effectively enhancing reusability of codes, efficiency, and consistency, while
realizing
functions like consistency of the method and its results for data exchange,
version control,
application expansion, environment monitoring, and error processing.
Therefore, the
general-purpose processing method for data exchange and its apparatus of the
embodiments of the present invention can be applied to various use scenarios
involving
data exchange.
[0026] The general-purpose processing method for data exchange and its
apparatus as disclosed
in the embodiments of the present invention will be explained in detail with
reference to
the accompanying drawings.
[0027] Embodiment 1
[0028] FIG. 1 is a flowchart of a general-purpose processing method for data
exchange according
to Embodiment 1 of the present invention. As shown, the present embodiment of
the
present invention provides a general-purpose processing method for data
exchange,
which comprising the steps described below.
[0029] The step 101 is about, according to predetermined rules for a data
exchange service,
setting up initialization data parameters for the data exchange service.
6
Date Regue/Date Received 2022-09-23

CA 03176864 2022-09-23
[0030] Specifically, the basic data exchange incoming parameters are set
according to agreed
rules of the data exchange service. Therein, the basic data exchange incoming
parameters
include data exchange basic addresses, local encrypted data for recognizing
user identities,
identifiers for recognizing user identities. The agreed rules of the data
exchange service
as used herein refer to predetermined rules for provision of the data exchange
service set
forth in regulations of the project data providing party or agreed between the
project front-
and back-ends for data exchange.
[0031] Exemplarily, according to the rules agreed between the project front-
and back-ends for
data exchange, information from a storage unit or a baseUrl (i.e., a data
exchange basic
address), a cookie (encrypted data stored locally for recognizing the user
identity), a token
(i.e., an identifier agreed by two sides of data exchange for recognizing user
identities),
basic data exchange incoming parameters are set. In the creation stage of the
project,
according to the agreed rules for the project data exchange service,
initialization of data
parameter setting up is performed. In practical use scenarios, a data request
can be
initiated simply by calling the data exchange service so as to obtain the data
feedback
result, thereby maintaining consistency of the method and its results for data
exchange.
[0032] It is to be noted that, in the step 101, initialization data parameters
for the data exchange
service according to the predetermined rules for the data exchange service can
be
implemented in a way different from that described above. The embodiment of
the present
invention puts no specific limitations thereto.
[0033] The step 102 involves calling the data exchange service for the current
use scenario
according to initialized data parameters.
[0034] Specifically, the use scenarios herein include the project development
stage, the testing
stage, and online release. For these scenarios, calling parameters are
reserved to facilitate
providing custom parameters specific to practical use scenarios. With
different custom
parameters, some unusual types of requests can be handled, thereby expanding
its
application scope and satisfying use needs in more scenarios
[0035] It is to be noted that, in the step 102, calling the data exchange
service for the current use
scenario according to the initialized data parameters can be implemented in a
way
7
Date Regue/Date Received 2022-09-23

CA 03176864 2022-09-23
different from that described above. The embodiment of the present invention
puts no
specific limitations thereto.
[0036] The step 103 is about, according to differentiation data parameters
corresponding to the
current use scenario, issuing a corresponding data request.
[0037] Specifically, the differentiation data parameters corresponding to the
current use scenario
are filled in, and the delivery parameters for data exchange required by the
current use
scenario are filled out.
[0038] Exemplarily, to call the data exchange service for the current use
scenario, according to
practical needs, the differentiation data parameters of the exact data
exchange url (i.e.,
the specific address information for data exchange) are filled in the api
(i.e., information
for identifying specific addresses that is agreed for the data exchange
service) parameters,
and the parameters to be transmitted in the current data exchange are filled
in params (i.e.,
identifiers for transmitting parameters agreed for the data exchange service),
so as to
accomplish the corresponding data request for the current data exchange.
[0039] Before the step of according to differentiation data parameters
corresponding to the
current use scenario, issuing a corresponding data request, the general-
purpose processing
method for data exchange of the embodiment of the present invention further
comprises:
[0040] setting up markers for the differentiation data parameters of the
specific address
information for data exchange required by the current use scenario, and
setting up
delivery parameter markers for data exchange required by the current use
scenario, and
initializing them into null objects.
[0041] Exemplarily, the differentiation data parameters of the url (i.e., the
specific address
information for data exchange) for project front- and back-ends data exchange
are
customized as api (i.e., information for identifying specific addresses that
is agreed for
the data exchange service). The input parameter params (i.e., identifiers for
transmitting
parameters agreed for the data exchange service) for the data exchange service
are set and
initialized into null objects.
[0042] It is to be noted that, in the 103, issuing the corresponding data
request according to
differentiation data parameters corresponding to the current use scenario can
be
8
Date Regue/Date Received 2022-09-23

CA 03176864 2022-09-23
implemented in a way different from that described above. The embodiment of
the present
invention puts no specific limitations thereto.
[0043] The step 104 is to perform data processing required by the current use
scenario according
to the data returned in response to the data request.
[0044] FIG. 2 is a flowchart of sub-steps of a step 104 in the method of
Embodiment 1.
[0045] Specifically, as shown in FIG. 2, it is to be determined whether the
data returned in
response to the data request are normal. If yes, logic processing
corresponding to normal
data is returned. Otherwise, it is to be further determined whether the
current use scenario
requires unusual processing. If unusual processing is required, unusual
processing logic
corresponding to such unusual processing is placed into the unusual callback.
[0046] Exemplarily, the returned data are monitored for error codes according
to the agreed rules
for data exchange between the proj ect front- and back-ends, and different
error processing
mechanisms are implemented depending on the error codes. Therein, use
scenarios are
reserved for selective error callback processing conducted by the error
processing
mechanisms. For normal, successful callback without any unusual data, a
response body
for data exchange is returned for the use scenario to use. In practical use
scenarios, normal
requests can be satisfied by writing the logic processing returned for the
normal data used
for this time into the successful callback of the disclosed apparatus. If a
practical use
scenario requires unusual processing such as resetting data for a data-
returning error, the
logic for error processing may be placed into the error callback. If there is
no unusual
processing, this step can be skipped. For different scenarios, the foregoing
process may
be repeated.
[0047] It is to be noted that, in the step 104, performing data processing
required by the current
use scenario according to data returned in response to the data request can be
implemented in a way different from that described above. The embodiment of
the present
invention puts no specific limitations thereto.
[0048] Embodiment 2
[0049] FIG. 3 is a structural diagram of a general-purpose processing
apparatus for data
exchange in Embodiment 2 of the present invention. As shown, the general-
purpose
9
Date Regue/Date Received 2022-09-23

CA 03176864 2022-09-23
processing apparatus for data exchange 2 of the embodiment of the present
invention
comprises: an initialization data parameter setting up module 21, a data
exchange service
calling module 22, a data request initiating module 23, and a data processing
module 24.
[0050] The initialization data parameter setting up module 21 is for according
to predetermined
rules for a data exchange service, setting up initialization data parameters
for the data
exchange service. Specifically, the initialization data parameter setting up
module 21 is
for according to agreed rules for the data exchange service, setting up basic
data exchange
incoming parameters, in which the basic data exchange incoming parameters
include data
exchange basic addresses, local encrypted data for recognizing user
identities, identifiers
for recognizing user identities.
[0051] The data exchange service calling module 22 is used to, for a current
use scenario,
according to the initialization data parameters, call the data exchange
service.
[0052] The data request initiating module 23 is for issuing the corresponding
data request
according to the differentiation data parameters corresponding to the current
use scenario.
Specifically, data request initiating module 23 is for filling in the
differentiation data
parameters corresponding to the current use scenario, and filling out the
delivery
parameters for data exchange required by the current use scenario. 8, in the
apparatus of
claim 6, the apparatus further comprises a differentiation setting up module
25, which is
for:
[0053] before the data request initiating module issues a corresponding data
request according
to differentiation data parameters corresponding to the current use scenario,
setting up
markers for the differentiation data parameters of the specific address
information for
data exchange required by the current use scenario, and setting up delivery
parameter
markers for data exchange required by the current use scenario, and
initializing them into
null objects.
[0054] The data processing module 24 is for performing data processing
according to the data
returned in response to the data request required by the current use scenario.
Specifically,
the data processing module 24 is for determining whether the data returned in
response
to the data request is normal, and if yes, returning logic processing
corresponding to the
Date Regue/Date Received 2022-09-23

CA 03176864 2022-09-23
normal data, or if no, further monitoring the current use scenario to see
whether unusual
processing is required, and if unusual processing is required, placing an
unusual
processing logic corresponding to the unusual processing into unusual
callback.
[0055] It is to be noted that work division among the foregoing functional
modules for the
general-purpose processing apparatus for data exchange of the present
embodiment to
trigger the general-purpose processing method for data exchange is merely
exemplary. In
practical implementations, the work division may be made among different
functional
modules. In other words, the internal architecture of the order-based phoning
system may
be reconfigured with different functional modules to perform all or a part of
the functions
as described previously. In addition, since general-purpose processing
apparatus for data
exchange of the present embodiment and the disclosed general-purpose
processing
method for data exchange in the previous embodiment stem from the same
conception,
the details of its implementation can be learned from the description made to
the method
of the previous embodiment, and no repetition is made herein.
[0056] All of the foregoing alternative technical scheme may be combined in an
arbitrary manner
to form an alternative embodiment of the present invention, and these possible
combinations are not exhaustively described herein.
[0057] To sum up, the general-purpose processing method for data exchange and
its apparatus
as disclosed in the embodiments of the present invention provide the following
beneficial
effects over the prior-art solutions:
[0058] (1) Providing consistency: in the project creation stage, the disclosed
apparatus is
initialized according to the regulations agreed with the data providing party.
In practical
use scenarios, data requests can be easily initiated by calling the data
exchange service
so as to obtain data feedback results, thereby realizing consistency of the
method and its
results for data exchange, and ensuring unified processing for input
parameters and
retuned data during data exchange between the front- and back-ends for
developing the
project. This in turn reduces repeated works for setting up and data
processing in practical
use scenarios. Use of unified packaging processing for input parameters and
returned data
during data exchange for the project simplifies development in terms of code,
step and
11
Date Regue/Date Received 2022-09-23

CA 03176864 2022-09-23
logic, and enhances reusability of project codes, consistency of operation,
centralization
of data exchange, and controllability of versions, leading to significantly
improved
development efficiency.
[0059] (2) Specific to version control: according to the prior-art data
exchange solutions, when
developing a system, the developer has to set up and process input parameters
and output
parameters separately for data exchange between the front- and back-ends
according to
the current use scenario. This is not only adverse to decoupling and reuse of
code
functions, but also makes it challenging to maintain consistency of the
project as a whole.
In other words, the prior-art solution is unable to provide unified processing
and unified
version control for data exchange. The present invention thus innovatively
introduces the
concept of version control, which makes it possible to call different versions
of data
according to practical use scenarios, thereby easily achieving version control
of data and
enabling data control adaptive to different scenarios and different
situations.
[0060] (3) Expanding applications: the present invention reserves calling
parameters to facilitate
providing custom parameters specific to practical use scenarios. With
different custom
parameters, some unusual types of requests can be handled, thereby expanding
its
application scope and satisfying use needs in more scenarios.
[0061] (4) Providing environment monitoring: the present invention allows
different data request
addresses to be configured for the development stage, the testing stage, and
online release
of the project, so as to automatically acquire data from the corresponding
data providing
party in practical use scenarios.
[0062] (5) Realizing error processing: the present invention provides an error
processing
mechanism, which processes error data as regulated by the rules, and reserves
use
scenarios where the error processing mechanism selectively performs error
callback
processing.
[0063] As will be appreciated by people of ordinary skill in the art,
implementation of all or a
part of the steps of the method of the present invention as described
previously may be
realized by having a program instruct related hardware components. The program
may
be stored in a computer-readable storage medium, and the program is about
performing
12
Date Regue/Date Received 2022-09-23

CA 03176864 2022-09-23
the individual steps of the methods described in the foregoing embodiments.
The storage
medium may be a ROM/RAM, a hard drive, an optical disk, or the like.
[0064] The embodiments of the present disclosure have been described with
reference to
flowcharts and/or block diagrams of the method, the system, and the computer
program
product. It is to be understood that every step and/or block in the flowcharts
and/or block
diagrams and every combination of steps and/or blocks in the flowcharts and/or
block
diagrams may be implemented by computer program instructions. These computer
program instructions may be provided to a general-purpose computer, an
application-
specific computer, an embedded processor, or a processor of other programable
data
processing devices to generate a machine, so that the instructions executed by
the
computer or the processor of other programable data processing devices can
generate an
apparatus that realizes the function as specified in one or more steps in a
flowchart or in
one or more blocks in a block diagram.
[0065] These computer program instructions may alternatively be stored in a
computer-readable
memory that can guide a computer or other programable data processing devices
to work
in a particular manner, so that the instructions stored in the computer-
readable memory
generates a produced object comprising the instruction apparatus. The
instruction
apparatus implements the functions as specified in one or more steps in a
flowchart or in
one or more blocks in a block diagram.
[0066] These computer program instructions may alternatively be loaded to a
computer or other
programmable data processing devices, so that a series of operational steps
can be
executed on the computer or the programable device, so as to generate computer-
enabled
processing, so that the instructions executed on the computer or the
programable device
provide the steps realizing the functions as specified in one or more steps in
a flowchart
or in one or more blocks in a block diagram.
[0067] Although the preferred embodiments of the present application have been
described,
people skilled in the art can make additional changes and modifications to
these
embodiments once the basic inventive concepts are known by them. Therefore,
the
appended claims are intended to be construed to include the preferred
embodiments and
13
Date Regue/Date Received 2022-09-23

CA 03176864 2022-09-23
all changes and modifications that fall within the scope of the embodiments of
this
application.
[0068] It is obvious that people skilled in the art might make various
modifications and variations
to the present invention without departing from the spirit and scope of the
present
invention. Provided that these modifications and variations of the present
invention fall
within the scope of the claims of the present invention and their equivalents,
the present
invention is intended to encompass all modifications and variations.
[0069] The preferred embodiments of the present invention described previously
are not intended
to limit the present invention. Any modification, equivalent replacement, and
improvement made under the spirit and principle of the present invention shall
be
included in the scope of the present invention. Anything contained in the
disclosure but
not detailed herein shall be regarded as technology known to people skilled in
the art.
14
Date Regue/Date Received 2022-09-23

Representative Drawing
A single figure which represents the drawing illustrating the invention.
Administrative Status

2024-08-01:As part of the Next Generation Patents (NGP) transition, the Canadian Patents Database (CPD) now contains a more detailed Event History, which replicates the Event Log of our new back-office solution.

Please note that "Inactive:" events refers to events no longer in use in our new back-office solution.

For a clearer understanding of the status of the application/patent presented on this page, the site Disclaimer , as well as the definitions for Patent , Event History , Maintenance Fee  and Payment History  should be consulted.

Event History

Description Date
Correspondent Determined Compliant 2024-09-26
Deemed Abandoned - Failure to Respond to an Examiner's Requisition 2024-09-09
Examiner's Report 2024-03-14
Inactive: Report - No QC 2024-03-13
Amendment Received - Response to Examiner's Requisition 2024-02-15
Amendment Received - Voluntary Amendment 2024-02-15
Examiner's Report 2023-10-18
Inactive: Report - No QC 2023-10-17
Letter sent 2023-10-12
Advanced Examination Determined Compliant - paragraph 84(1)(a) of the Patent Rules 2023-10-12
Inactive: IPC assigned 2023-10-11
Inactive: IPC assigned 2023-10-11
Inactive: First IPC assigned 2023-10-11
Inactive: Advanced examination (SO) fee processed 2023-09-22
Inactive: Advanced examination (SO) 2023-09-22
Amendment Received - Voluntary Amendment 2023-09-22
Amendment Received - Voluntary Amendment 2023-09-22
Letter sent 2022-10-27
Application Received - PCT 2022-10-26
Priority Claim Requirements Determined Compliant 2022-10-26
Letter Sent 2022-10-26
Request for Priority Received 2022-10-26
National Entry Requirements Determined Compliant 2022-09-23
Request for Examination Requirements Determined Compliant 2022-09-23
All Requirements for Examination Determined Compliant 2022-09-23
Application Published (Open to Public Inspection) 2020-10-15

Abandonment History

Abandonment Date Reason Reinstatement Date
2024-09-09

Maintenance Fee

The last payment was received on 2023-12-15

Note : If the full payment has not been received on or before the date indicated, a further fee may be required which may be one of the following

  • the reinstatement fee;
  • the late payment fee; or
  • additional fee to reverse deemed expiry.

Patent fees are adjusted on the 1st of January every year. The amounts above are the current amounts if received by December 31 of the current year.
Please refer to the CIPO Patent Fees web page to see all current fee amounts.

Fee History

Fee Type Anniversary Year Due Date Paid Date
Request for examination - standard 2024-10-01 2022-09-23
MF (application, 2nd anniv.) - standard 02 2021-09-29 2022-09-23
Reinstatement (national entry) 2022-09-23 2022-09-23
Basic national fee - standard 2022-09-23 2022-09-23
MF (application, 3rd anniv.) - standard 03 2022-09-29 2022-09-23
MF (application, 4th anniv.) - standard 04 2023-09-29 2023-06-15
Advanced Examination 2023-09-22 2023-09-22
MF (application, 5th anniv.) - standard 05 2024-10-01 2023-12-15
Owners on Record

Note: Records showing the ownership history in alphabetical order.

Current Owners on Record
10353744 CANADA LTD.
Past Owners on Record
CHENGYING YANG
HUIYANG WU
QIAN SUN
TINGTING WU
WENHAO HUANG
ZHIYONG ZHANG
Past Owners that do not appear in the "Owners on Record" listing will appear in other documentation within the application.
Documents

To view selected files, please enter reCAPTCHA code :



To view images, click a link in the Document Description column. To download the documents, select one or more checkboxes in the first column and then click the "Download Selected in PDF format (Zip Archive)" or the "Download Selected as Single PDF" button.

List of published and non-published patent-specific documents on the CPD .

If you have any difficulty accessing content, you can call the Client Service Centre at 1-866-997-1936 or send them an e-mail at CIPO Client Service Centre.


Document
Description 
Date
(yyyy-mm-dd) 
Number of pages   Size of Image (KB) 
Claims 2024-02-14 11 586
Representative drawing 2023-10-11 1 23
Claims 2023-09-21 11 583
Description 2022-09-22 14 728
Abstract 2022-09-22 1 24
Drawings 2022-09-22 3 78
Claims 2022-09-22 3 119
Amendment / response to report 2024-07-11 1 443
Amendment / response to report 2024-02-14 30 1,115
Examiner requisition 2024-03-13 4 204
Courtesy - Acknowledgement of Request for Examination 2022-10-25 1 423
Courtesy - Letter Acknowledging PCT National Phase Entry 2022-10-26 1 595
Advanced examination (SO) / Amendment / response to report 2023-09-21 17 549
Courtesy - Advanced Examination Request - Compliant (SO) 2023-10-11 1 188
Examiner requisition 2023-10-17 4 200
National entry request 2022-09-22 13 1,301
International search report 2022-09-22 15 558
Amendment - Abstract 2022-09-22 2 106