Note : Les descriptions sont présentées dans la langue officielle dans laquelle elles ont été soumises.
ELECTRONIC INVOICE MANAGEMENT METHOD, DEVICE, COMPUTER
APPARATUS, AND STORAGE MEDIUM
Technical Field
[0001] The present invention relates to the field of invoice management
technologies, in particular,
to a method, a device, a computer apparatus, and a storage medium for
electronic invoice
management.
Background
[0002] According to the national policies of "promoting the use of electronic
invoice, supporting
companies and operators to issue electronic invoices according to rules, and
allowing the use of
electronic invoices for reimbursement", the use of electronic invoice has been
greatly developed
and covers many service fields such as retailers, e-commerce, and travels.
Especially in the fast-
moving service fields such as supermarkets and restaurants, the application of
electronic invoice
has become more prevalent. Generally, the merchants print a QR code on each
purchase receipt,
and customers can obtain issued electronic invoices by scanning the QR codes.
[0003] However, the traditional scanning-based electronic invoice issuing
encounters problems of
that:
[0004] in the fields applying scanning-based electronic invoice issuing, a
great portion of
customers is occupied by non-member customers. After issuing electronic
invoices, the back end
cannot access user information of the non-member customers, wherein the order-
receipt-customer
relations are difficult to obtain, consequently with difficult invoice
management of the customer
electronic invoices.
Summary
[0005] Accordingly, aiming at the aforementioned technical problems, an
electronic invoice
management method, device, computer apparatus, and storage medium are provided
in the present
invention, permitting electronic invoice management for customer purchases
without customer
user information.
[0006] An electronic invoice management method, comprises: receiving an
invoice request
carrying an access token from a third-party application, wherein the invoice
request is used to
1
Date Recue/Date Received 2022-02-01
request an electronic invoice for a target order; when the third-party
application identified by the
access token is an authorized application, generating the invoice issuing page
for the target order
based on the invoice request and sending the invoice issuing page to the third-
party application;
receiving invoice information sent from the third-party application to
generate the electronic
invoice for the target order based on the invoice information; and relating
the electronic invoice
with the access token, wherein electronic invoices for target orders are
managed by access tokens.
[0007] In one of embodiments, the described method further includes: when the
invoice
permission request carrying an access token from a third-party application is
received, acquiring a
username on the described third-party application and the secret key
corresponding to the
described use name, wherein the described invoice permission request is used
to request
peimission to issue the electronic invoice of the described target order; and
acquiring the described
access token based on the described username and the described secret key, and
sending the
described access token to the described third-party application.
[0008] In one of embodiments, after relating the electronic invoice with the
access token, the
described method further includes: sending a notification to the described
third-party application
for indicating that the electronic invoice has been successfully issued; when
the invoice reviewing
request sent from the described third-party application is received, where if
the described invoice
reviewing request is detected to carry the described access token, acquiring
the invoice information
of the described electronic invoice based on the described access token, and
sending the invoice
information of the described electronic invoice to the described third-party
application.
[0009] In one of embodiments, after relating the electronic invoice with the
access token, the
described method further includes: receiving the title modification request
sent form the described
third-party application, wherein the described title modification request is
used to request
modifications on the invoice title of described electronic invoice; where if
the described title
modification request is detected to carry the described access token, sending
the title medication
page to the described third-party application; receiving the modified invoice
title from the title
medication page sent from the described third-party application so as to
replace the invoice title in
the described electronic invoice by the described modified invoice title for
obtaining the modified
electronic invoice, wherein the described modified electronic invoice and the
described access
token are related.
2
Date Recue/Date Received 2022-02-01
[0010] Preferably, after obtaining the modified electronic invoice, the method
further includes:
off-writing the described electronic invoice before the modification; and
sending the invoice
information of the described modified electronic invoice to the described
third-party application.
[0011] In one of embodiments, before sending the title medication page to the
described third-
party application, the described method further includes: identifying the
primary invoice
information according to the described title modification request; querying
recorded title
modification times of the described electronic invoice in a modification table
based on the
described primary invoice information; where if the number of the described
title modification
times is greater than a pre-set number, sending a notification to the
described third-party
application indicating the failure of the described electronic invoice title
modification; and where
if the number of the described title modification times is smaller than the
described pre-set number,
proceeding to the procedure of sending the title medication page to the
described third-party
application.
[0012] In one of embodiments, after generating the electronic invoice for the
target order based
on the described invoice information, the described method further includes:
receiving the
exchange request for a paper-based invoice sent by the described third-party
application, wherein
the described exchange request for a paper-based invoice is used to request
the exchange from the
described electronic invoice to a paper-based invoice; where if the described
exchange request for
a paper-based invoice is detected to carry the described access token, saving
the secondary invoice
information of the described electronic invoice into the paper-based invoice
pool, wherein the
described paper-based invoice pool is configured to store the order
information for issuing-pending
paper-based invoices; and off-writing the described electronic invoice.
[0013] In one of embodiments, before receiving the invoice request sent from
the described third-
party application, the described method further includes: receiving the
issuing-pending order
information of the described target order sent by the order issuing system;
generating an
identification code for the described target order; generating a primary
encrypting information of
the described identification code by the salt according to the described
issuing-pending order
information; encrypting the described identification code by the described
primary encrypting
information to obtain the encrypted identification code; and sending the
encrypted identification
code to the described order issuing system. The invoice request by the third-
party application is
received, by means of: receiving the invoice request sent by the third-party
application, wherein
3
Date Recue/Date Received 2023-03-07
the described invoice request is obtained by scanning the described encrypted
identification code
provided by the described order issuing system by the described third-party
application. The
described method further includes: extracting the secondary encrypting
information from the
described invoice request, and where if the described secondary encrypting
information matches
with the described primary encrypting information, proceeding to the procedure
of sending the
invoice issuing page to the third-party application.
[0014] An electronic invoice management device, comprises: a receiving module,
configured to
receive an invoice request carrying an access token from a third-party
application, wherein the
invoice request is used to request an electronic invoice for a target order; a
sending module,
configured to generate the invoice issuing page for the target order based on
the invoice request
when the third-party application identified by the access token is an
authorized application, and
send the invoice issuing page to the third-party application; a generation
module, configured to
receive invoice information sent from the third-party application and generate
the electronic
invoice for the target order based on the invoice information; and a
management module,
configured to relate the electronic invoice with the access token, wherein
electronic invoices for
target orders are managed by access tokens.
[0015] A computer apparatus, comprises a memory unit, a processor, and
computer programs
stored in the memory unit executable on the processor, wherein any methods in
the aforementioned
embodiments are performed when the described processor executes the described
computer
programs.
[0016] A readable computer storage medium with computer programs stored, is
characterized in
that, any methods in the aforementioned embodiments are performed when the
described computer
programs are executed on the described processor.
[0017] The aforementioned electronic invoice management method, device,
computer apparatus,
and storage medium receive an invoice request carrying an access token from a
third-party
application, wherein the invoice request is used to request an electronic
invoice for a target order;
when the third-party application identified by the access token is an
authorized application,
generate the invoice issuing page for the target order based on the invoice
request and sending the
invoice issuing page to the third-party application; receive invoice
information sent from the third-
party application to generate the electronic invoice for the target order
based on the invoice
information; and relate the electronic invoice with the access token, wherein
electronic invoices
4
Date Recue/Date Received 2022-02-01
for target orders are managed by access tokens. Therefore, the back end is
permitted to manage
electronic invoices for customer purchases without customer user information
by authorizing the
access token to the third-party application, achieve non-member customer
management, and
expand management on non-member electronic invoice.
Brief descriptions of the drawings
[0018] Fig. 1 is an application environment diagram of an electronic invoice
management method
provided in one of embodiments;
[0019] Fig. 2 is an application scenario diagram of an electronic invoice
management method
provided in one of embodiments;
[0020] Fig. 3 is a procedure flow diagram of an electronic invoice management
method provided
in one of embodiments;
[0021] Fig. 4 is illustrative diagram of a general electronic invoice format
provided in one of
embodiments;
[0022] Fig. 5 is a diagram of information interaction process amongst all
devices for querying
electronic invoices in one of embodiments;
[0023] Fig. 6 is an interface display diagram of a display interface in the
third-party application in
one of embodiments;
[0024] Fig. 7 is a procedure flow diagram of the electronic invoice title
modification provided in
one of embodiments;
[0025] Fig. 8 is a procedure flow diagram of the exchange to a paper-based
invoice provided in
one of embodiments;
[0026] Fig. 8 is a procedure flow diagram of the exchange process for an
electronic invoice to a
paper-based invoice provided in one of embodiments;
[0027] Fig. 9 is a diagram of information interaction process amongst all
devices for issuing
electronic invoice for a target order in one of embodiments;
[0028] Fig. 10 is a structure diagram of an electronic invoice management
device provided in one
of embodiments; and
[0029] Fig. 11 is a structure diagram of the computer apparatus provided in
one of embodiments.
Detailed descriptions
Date Recue/Date Received 2022-02-01
[0030] In order to make the objective, the technical scheme, 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.
[0031] An electronic invoice management method provided in the present
invention can be applied
to the application environment shown in Fig. 1. As shown in Fig. 1, the back
end 104 is configured
to perform an electronic invoice management method in the present invention.
In particular, a user
accesses the third-party application on the terminal 102 to send the invoice
request carrying the
access token to the back end 104, wherein the invoice request is used to
request an electronic
invoice for a target order. When the back end 104 identifies a third-party
application by the access
token as an authorized application, the invoice issuing page for the target
order is generated based
on the invoice request and sent to the third-party application on the terminal
102. Furthermore, the
third-party application displays the invoice issuing page to the user to ask
the user to fill invoice
information for the target order on the invoice issuing page. The terminal 102
sends an invoice
issuing page with the invoice information to the back end 104. Furthermore,
the back end 104
receives invoice information sent from the third-party application to generate
the electronic invoice
for the target order based on the invoice information. Then, the back end 104
relates the electronic
invoice with the access token, wherein electronic invoices for target orders
are managed by access
tokens. Therefore, the back end is permitted to manage electronic invoice for
customer purchases
without customer user information by authorizing the access token to the third-
party application,
achieve non-member customer management, and expand management on non-member
electronic
invoice.
[0032] An electronic invoice management method provided in the present
invention can further
be applied to the application environment shown in Fig. 2. As shown in Fig. 2,
the application
environment includes merchant invoice issuing subsystem, the third-party
application, the invoice
pre-issuing subsystem, and the invoice issuing subsystem. Wherein, the invoice
pre-issuing
subsystem and the invoice issuing subsystem are allocated in the back end 104.
The third-party
application on the terminal 102 is configured to manage user-issued electronic
invoice. The
merchant invoice issuing subsystem is configured to provide order information
of the target order
6
Date Recue/Date Received 2022-02-01
to the user, so as to send the invoice request to the back end 104 for
requesting to issue the
electronic invoice for the target order. As shown in Fig. 2, the user is a
customer. The merchant
invoice issuing subsystem print the target order receipt for the customer; the
customer scans the
QR code on the receipt via the third-party application to acquire order
information of the target
order; the customer uses the third-party application to submit the invoice
issuing application to the
invoice pre-issuing subsystem; and the customer accesses and manages the
invoice information of
the electronic invoice returned by the invoice pre-issuing subsystem via the
third-party application.
The information interactions amongst individual systems and devices in the
application
environment shown in Fig. 2 can refer to detailed descriptions for an
electronic invoice
management method in the following embodiments.
[0033] In an embodiment, as shown in Fig. 2, an electronic invoice management
method is
provided. For example, the described method can be applied to the back end
shown in Fig. 1. In
particular, the back end comprises the invoice pre-issuing subsystem and the
invoice issuing
subsystem. An electronic invoice management method comprises the following
steps:
[0034] S302, receiving an invoice request carrying an access token from a
third-party application,
wherein the invoice request is used to request an electronic invoice for a
target order.
[0035] In the present embodiment, the user submits the invoice request to the
invoice pre-issuing
subsystem via the third-party application on the terminal for requesting to
issue the electronic
invoice for the target order. The invoice request carries an access token. The
access token is used
to identify authorized third-party applications. In detail, the invoice pre-
issuing subsystem
generates an access token and send the access token to the teiininal. The
third-party application on
the terminal attaches the access token to the invoice request to identify
authorized third-party
applications to the invoice pre-issuing subsystem based on the access token in
the invoice request.
[0036] S304, when the third-party application identified by the access token
is an authorized
application, generating the invoice issuing page for the target order based on
the invoice request,
and sending the invoice issuing page to the third-party application.
[0037] In the present embodiment, the invoice pre-issuing subsystem parses the
invoice request to
acquire the access token in the invoice request. Furthermore, the access token
is recognized. When
the third-party application identified by the access token is an authorized
application, the invoice
issuing page for the target order is generated based on the invoice request.
In particular, the invoice
request is used for requesting to issue the electronic invoice of the target
order. Possibly, the
7
Date Recue/Date Received 2022-02-01
invoice pre-issuing subsystem can be pre-set as a primary general template on
the invoice issuing
page, wherein the primary general template contains general information for
issuing electronic
invoices, such as "tax identification number", "title", "address", "contact
number", and other
general fields for the electronic invoices. When the invoice request is
received, acquiring data
information to be filled in the electronic invoice for the target order
according to the target order
indicated in the invoice request, wherein the data information is filled in
the primary general
template to generate the invoice issuing page for the target order. In
particular, data information to
be filled in the electronic invoice for the target order can include company
basic information,
transaction data, reimbursing objects, etc. For example, the invoice issuing
page can be a HTML
web page form, wherein the HTML 5 web page form includes company basic
information,
transaction data, reimbursing objects. Furthermore, the invoice issuing page
is sent to the third-
party application.
[0038] S306, receiving invoice information sent from the third-party
application to generate the
electronic invoice for the target order based on the invoice information.
[0039] In the present embodiment, when the third-party application receives
the invoice issuing
page, the invoice issuing page is displayed on the terminal. The user fills
invoice information of
the electronic invoice on the invoice issuing page, such as the title
information and the tax
identification number. Then, the third-party application sends the invoice
information on the
invoice issuing page to the invoice pre-issuing subsystem. As shown in Fig. 2,
the invoice pre-
issuing subsystem sends invoice data carrying invoice information to the
invoice issuing
subsystem via a message middleware to generate the electronic invoice for the
target order
according to the invoice data by the invoice issuing subsystem. In detail, the
invoice issuing
subsystem is allocated with a pre-set electronic invoice secondary general
template, wherein the
general format of electronic invoice is set in the secondary general template
as shown in Fig. 4.
The invoice issuing subsystem fills invoice data into the secondary general
template to generate
the electronic invoice for the target order. Furthermore, the invoice issuing
subsystem feedbacks
the electronic invoice to the invoice pre-issuing subsystem.
[0040] S308, relating the electronic invoice with the access token, wherein
electronic invoices for
target orders are managed by access tokens.
[0041] In the present embodiment, the invoice pre-issuing subsystem relates
the electronic invoice
for the target invoice with the access token. The target order electronic
invoice can be accessed by
8
Date Recue/Date Received 2022-02-01
the relationship with the access token in the invoice pre-issuing subsystem,
wherein the access
token can be used for invoice management of the target order electronic
invoices. Besides, the
access token is used to identify authorized third-party applications,
therefore, the invoice pre-
issuing subsystem can manage third-party applications by access tokens. When a
third-party
application carrying an access token accesses the invoice pre-issuing
subsystem, the invoice pre-
issuing subsystem can query target order electronic invoice by access tokens.
For non-member
users, third-party applications can be directly used to apply for issuing
target order electronic
invoices, wherein the third-party applications can query target order of
electronic invoices from
the invoice pre-issuing subsystem. The invoice pre-issuing subsystem performs
invoice
management for the target order invoices via access tokens related with third-
party applications,
wherein the third-party application target order of electronic invoices can be
queried by access
tokens and the invoice information of electronic invoices are returned to the
third-party
applications. Therefore, the order management for non-member users on the back
end can be
achieved, with expanded non-member electronic invoice management on the back
end.
[0042] The aforementioned electronic invoice management method can receive an
invoice request
carrying an access token from a third-party application, wherein the invoice
request is used to
request an electronic invoice for a target order; when the third-party
application identified by the
access token is an authorized application, generate the invoice issuing page
for the target order
based on the invoice request and sending the invoice issuing page to the third-
party application;
receive invoice information sent from the third-party application to generate
the electronic invoice
for the target order based on the invoice information; and relate the
electronic invoice with the
access token, wherein electronic invoices for target orders are managed by
access tokens.
Therefore, the back end is permitted to manage electronic invoice for customer
purchases without
customer user information by authorizing the access token to the third-party
application, achieve
non-member customer management, and expand management on non-member electronic
invoice.
[0043] In an embodiment, before receiving an invoice request carrying an
access token from a
third-party application, the described method further includes: when the
invoice permission
request carrying an access token from a third-party application is received,
acquiring a usemame
on the described third-party application and the secret key corresponding to
the described use name,
wherein the described invoice permission request is used to request permission
to issue the
electronic invoice of the described target order; and acquiring the described
access token based on
9
Date Recue/Date Received 2022-02-01
the described usemame and the described secret key, and sending the described
access token to
the described third-party application.
[0044] In the present embodiment, the access token is acquired based on the
usemame on the third-
party application and corresponding secret key by the invoice pre-issuing
subsystem. The invoice
pre-issuing subsystem identifies authorized third-party applications by access
tokens. When the
third-party application submits an invoice request to the invoice pre-issuing
subsystem for the first
time, the invoice pre-issuing subsystem sends the access token to the third-
party application. In
other words, in the first invoice request, the third-party application
requests permissions from the
invoice pre-issuing subsystem. At the same time, the invoice pre-issuing
subsystem acquires the
usemame on the third-party application and corresponding secret key, then
acquires the access
token by the usemame on the third-party application and corresponding secret
key. Possibly, the
access token for the third-party application is generated by the usemame on
the third-party
application and corresponding secret key to acquire the access token. In
another possible way, the
invoice pre-issuing subsystem carries multiple access tokens to be distributed
to third-party
applications, and the access tokens are related to the user names on the third-
party applications
and corresponding secret keys wherein corresponding access tokens can be
acquired by the user
names on the third-party applications and corresponding secret keys.
Furthermore, the third-party
applications can attach the access tokens in the following invoice requests
for issuing electronic
invoices, wherein the invoice pre-issuing subsystem responds to the invoice
request based on the
access token to issue the electronic invoice corresponding to the invoice
request. Possibly, the
third-party application attaches the access token in the following invoice
requests for issuing target
order electronic invoices, wherein the invoice pre-issuing subsystem responds
to the invoice
request based on the access token to issue the electronic invoice
corresponding to the invoice
request. Therefore, the target order of electronic invoices for users on the
third-party applications
can be managed based on access tokens, to achieve non-member customer
management and
expand management on non-member electronic invoice.
[0045] In one of embodiments, after relating the electronic invoice with the
access token, the
described method further includes: sending a notification to the described
third-party application
for indicating that the electronic invoice has been successfully issued; when
the invoice reviewing
request sent from the described third-party application is received, where if
the described invoice
reviewing request is detected to carry the described access token, acquiring
the invoice information
Date Recue/Date Received 2022-02-01
of the described electronic invoice based on the described access token, and
sending the invoice
information of the described electronic invoice to the described third-party
application.
[0046] In the present embodiment, after receiving the target order of
electronic invoices by the
invoice pre-issuing subsystem, a notification is sent to the third-party
application for indicating
that the electronic invoice has been successfully issued. When a user searches
issued electronic
invoices via the third-party application, the third-party application sends an
invoice reviewing
request to the invoice pre-issuing subsystem. Where if the described invoice
reviewing request is
detected to carry the described access token by the invoice pre-issuing
subsystem, the invoice
information is sent to the third-party application. For example, as shown in
Fig. 5, a customer uses
the third-party application to review the applied electronic invoices from the
invoice pre-issuing
system via remote service ports by the authorized access tokens as the
searching certificates. The
invoice pre-issuing system searches the electronic invoices applied by the
described customer
based on the access tokens for invoice applications and the relationships with
the target order
electronic invoices, wherein invoice information, formatting files, order
information, and other
related information are acquired and written in the invoice detail pages.
Moreover, the invoice
detail pages are returned to the third-party application. Therefore, the
linking relationships between
the third-party applications and electronic invoices in the back end is
achieved by access tokens,
wherein the back end is permitted to manage customer electronic invoices
without customer user
information and users can review user electronic invoices without registration
information.
[0047] In an embodiment, after relating the electronic invoice with the access
token, the described
method further includes: receiving the title modification request sent form
the described third-
party application, wherein the described title modification request is used to
request modifications
on the invoice title of described electronic invoice; where if the described
title modification request
is detected to carry the described access token, sending the title medication
page to the described
third-party application; receiving the modified invoice title from the title
medication page sent
from the described third-party application so as to replace the invoice title
in the described
electronic invoice by the described modified invoice title for obtaining the
modified electronic
invoice, wherein the described modified electronic invoice and the described
access token are
related.
11
Date Recue/Date Received 2022-02-01
[0048] Preferably, after obtaining the modified electronic invoice, the method
further includes:
off-writing the described electronic invoice before the modification; and
sending the invoice
information of the described modified electronic invoice to the described
third-party application.
[0049] In the present embodiment, the back end provides the title modification
service for issued
electronic invoices. Possibly, the invoice pre-issuing subsystem on the back
end can provide the
title modification service for issued electronic invoices. As shown in Fig. 6,
the third-party
applications provide title modification elements. Uses can trigger the title
modification elements
to submit the title modification requests to the back end. When the back end
detects the access
tokens in the title modification requests, the title modification page is sent
to the third-party
application. The title modification page contains editable elements to receive
the desired invoice
title edited by users. And/or, the title modification page can provide
available invoice titles for the
modification. The users can select corresponding desired invoice titles. The
modified invoice titles
can be determined on the title modification page. The back end changes the
previous invoice title
into the desired invoice title to obtain the modified electronic invoice,
wherein the modified
electronic invoice is related to the access token. Therefore, when the third-
party application
searches the modified electronic invoices, the back end can access the
modified electronic invoices
by the access tokens. Furthermore, the back end off-writes the electronic
invoice before the
modification and sends the invoice information of the described modified
electronic invoice to the
described third-party application. Herein, the titles of issued electronic
invoices are modified to
satisfy user demands.
[0050] To clarify, in the traditional electronic invoice issuing approaches,
the electronic invoice
title modification service is not provided. Where if an electronic invoice
title is needed to modify,
the user needs to contact the customer service to manually modify the
electronic invoice to obtain
the modified electronic invoices. In the present embodiment, the self-
modification service for
invoice titles is provided to users. Users can initiate the title modification
request from the third-
party applications, wherein the back end provides the invoice title
modification service. Therefore,
the automated invoice title modification process is achieved for electronic
invoices.
[0051] In an embodiment, before sending the title medication page to the
described third-party
application, the described method further includes: identifying the primary
invoice information
according to the described title modification request; querying recorded title
modification times of
the described electronic invoice in a modification table based on the
described primary invoice
12
Date Recue/Date Received 2022-02-01
information; where if the number of the described title modification times is
greater than a pre-set
number, sending a notification to the described third-party application
indicating the failure of the
described electronic invoice title modification; and where if the number of
the described title
modification times is smaller than the described pre-set number, proceeding to
the procedure of
sending the title medication page to the described third-party application.
[0052] In the present embodiment, in the automated invoice title modification
process provided
by the invoice pre-issuing subsystem, the number of times to modify invoice
title is restricted. In
detail, a pre-set number of times is set in advance to restrict the number of
times to modify invoice
title. The invoice pre-issuing subsystem records the number of title
modification times for each
issued electronic invoice by a modification recording table. The numbers of
times for electronic
invoice title modification are related to order information of each electronic
invoice. The invoice
pre-issuing subsystem identifies the primary order information of the
electronic invoice based on
the title modification request, recorded title modification times of the
described electronic invoice
in a modification table is queried based on the described primary invoice
information. Where if
the number of the described title modification times is less or equal to a pre-
set number, the
procedure of sending the title medication page to the described third-party
application is performed.
Otherwise, a notification to the described third-party application indicating
the failure of the
described electronic invoice title modification is sent.
[0053] In detail, the invoice title is a necessary component of an electronic
invoice. The invoice
titles are generally selected by a customer from several invoice titles. In
the meanwhile, the invoice
title modification is a normal invoice exchange process in the field of
invoice. For example,
referring to the process shown in Fig. 7, the automated invoice title
modification service for issued
invoices is provided to users. A customer can click the title modification
button on the third-party
application, and the front end sends the title modification request to the
invoice pre-issuing
subsystem. To prevent unlimited malicious title modifications for electronic
invoice frauds, the
invoice pre-issuing subsystem configures a unified management platform to
restrict the numbers
of times for electronic invoice title modification. The invoice pre-issuing
subsystem receives the
title modification requests by customers and verifies that whether the numbers
of times for
electronic invoice title modification pass the restriction by searching the
title modification
recording table based on the order information. Where if the restriction is
passed, the front-end
description message is returned as "The limit of title modification times has
been passed. No more
13
Date Recue/Date Received 2022-02-01
self-modification allowed. Please visit customer service for title
modifications". Where if the
restriction remains, the title modification page is directed to allow
customers edit the title
information and resubmit the invoice request to the invoice pre-issuing
subsystem.
[0054] After the invoice pre-issuing subsystem receives the title modification
applications by
customers, the records are saved into the title modification table. The
original electronic invoices
are off-written with the status updated to being off-written. Then, the new
electronic invoices with
modified titles are issued. Customers can review invoice information from the
invoice query lists.
[0055] In an embodiment, after generating the electronic invoice for the
target order based on the
described invoice information, the described method further includes:
receiving the exchange
request for a paper-based invoice sent by the described third-party
application, wherein the
described exchange request for a paper-based invoice is used to request the
exchange from the
described electronic invoice to a paper-based invoice; where if the described
exchange request for
a paper-based invoice is detected to carry the described access token, saving
the secondary invoice
information of the described electronic invoice into the paper-based invoice
pool, wherein the
described paper-based invoice pool is configured to store the order
information for issuing-pending
paper-based invoices; and off-writing the described electronic invoice.
[0056] As a new invoice format, electronic invoices are not accepted by some
customers. In the
meanwhile, some companies require the VAT special invoices for expense
verification, wherein
the electronic invoices are not usable for expense verification. Therefore,
the service to exchange
electronic invoices to paper-based invoices is significantly important. In the
present embodiment,
the self-exchange to normal VAT paper-based invoices is supported. As shown in
Fig. 6, the third-
party applications provide elements for paper-based invoice exchange. Users
can trigger the
elements for paper-based invoice exchange to submit requests for paper-based
invoice exchange
to the back end. When the back end detects the access tokens in the paper-
based invoice exchange
requests, the secondary invoice information of the described electronic
invoice is saved into the
paper-based invoice pool, so as to acquire the secondary order information
from the invoice pool
and issue the paper-based invoices corresponding to the electronic invoices
based on the secondary
order information. In particular, the primary order information can be
identical to the secondary
order information. In the meanwhile, the electronic invoice is off-written.
Besides, when the access
tokens in paper-based invoice exchange requests are detected, the paper-based
invoice exchange
page can be sent to the third-party application, wherein the paper-based
invoice exchange page is
14
Date Recue/Date Received 2022-02-01
configured to receive mailing address by users. The paper-based invoice
exchange page is shown
in Fig. 8. After the back end receives the mailing address for the paper-based
invoice exchange
page sent by the third-party applications, the mailing address of the paper-
based invoices are
related to the secondary order information in the invoice pool, to locate the
mailing address of the
paper-based invoices according to the secondary order information.
[0057] For example, as the process shown in Fig. 9, for the issued electronic
invoices, the self-
exchange to paper-based invoices is provided to customers. When the customers
click the button
of paper-based invoice exchange on the third-party applications, the front end
sends the paper-
based invoice exchange requests to the invoice pre-issuing subsystem. The
invoice pre-issuing
subsystem searches for invoice exchange records based on the secondary order
information of the
electronic invoice, to verify that whether the paper-based invoices for the
target orders are
exchanged. Where if the paper-based invoices have been exchanged, the front
description message
is returned as "the paper-based invoices have been exchanged; no more exchange
request is
proceeded". Where if the paper-based invoices have not been exchanged, the
front paper-based
invoice exchange page is returned to allow customers to fill the mailing
address for the paper-
based invoice and submit the paper-based invoice exchange request.
[0058] After the invoice pre-issuing subsystem receives paper-based invoice
exchange requests
submitted by the front end, the record is saved into the exchange record
table. The original
electronic invoices are off-written with the status updated to being off-
written. The secondary
order information for paper-based invoice exchange is saved into the paper-
based invoice pool.
The invoice issuing officers can query order information of the paper-based
invoices via the
invoice pool by the invoice pre-issuing subsystem. The paper-based invoices
are issued offline and
mailed according to the mailing information submitted by customers.
[0059] To clarify, in the traditional electronic invoice issuing approaches,
the paper-based invoice
exchange service for electronic invoices is not provided. Where if an
electronic invoice is needed
to be exchanged to a paper-based invoice, the user needs to contact the
customer service for manual
operations to obtain the exchanged paper-based invoice. In the present
embodiment, the self-
exchange service for electronic invoices to paper-based invoices is provided
to users. Users can
initiate the paper-based invoice exchange request from the third-party
applications, wherein the
back end provides the paper-based invoice exchange service. Therefore, the
automated paper-
based invoice exchange process is achieved for electronic invoices.
Date Recue/Date Received 2022-02-01
[0060] In an embodiment, before receiving the invoice request sent from the
described third-party
application, the described method further includes: receiving the issuing-
pending order
information of the described target order sent by the order issuing system;
generating an
identification code for the described target order; generating the primary
encrypting information
of the described identification code by the salt according to the described
issuing-pending order
information; encrypting the described identification code by the described
primary encrypting
information to obtain the encrypted identification code; and sending the
encrypted identification
code to the described order issuing system. The invoice request by the third-
party application is
received, by means of: receiving the invoice request sent by the third-party
application, wherein
the described invoice request is obtained by scanning the described encrypted
identification code
provided by the described order issuing system by the described third-party
application. The
described method further includes: extracting the secondary encrypting
information from the
described invoice request, and where if the described secondary encrypting
information matches
with the described primary encrypting information, proceeding to the procedure
of sending the
invoice issuing page to the third-party application.
[0061] In the present embodiment, the target order electronic invoice issuing
process is encrypted
by the means of identification code encryption. The invoice issuing system
sends issuing-pending
invoice information of the target order to the back end. The back end
generates an identification
code for the target order based on the issuing-pending invoice information of
the target order. In
particular, the identification code can be a QR code. Furthermore, a primary
encrypting
information of the described identification code is generated by the salt
according to the described
issuing-pending order information. Then, the described identification code is
encrypted by the
described primary encrypting information to obtain the encrypted
identification code. The
encrypted identification code contains the primary encrypting information.
Finally, the back end
sends the encrypted identification code to the invoice issuing system. Users
scan the encrypted
identification codes by the third-party applications to obtain the primary
encrypting information
and the order information of the target order. Then, the third-party
applications send invoice
requests to the back end, wherein the invoice requests contain the secondary
encrypting
information. In general, the secondary encrypting information is identical to
the primary
encrypting information. The back end extracts the secondary encrypting
information from the
described invoice request, and recognizes the secondary encrypting information
and the primary
16
Date Recue/Date Received 2022-02-01
encrypting information generated by the back end. Where if the secondary
encrypting information
is identical to the primary encrypting information, the secondary encrypting
information matches
with the primary encrypting information. The back end performs the procedure
of sending the
invoice issuing page to the third-party application. In other applications,
the encrypted
identification code contains information related to the primary encrypting
information. Finally, the
back end sends the encrypted identification code to the invoice issuing
system. Users scan the
encrypted identification codes by the third-party applications to obtain the
primary encrypting
information and the order information of the target order. Then, the third-
party applications send
invoice requests to the back end, wherein the invoice requests contain the
secondary encrypting
information. Presently, the secondary encrypting information contains
information related to the
primary encrypting information. Where if the matching result indicates the
correlation between the
primary and the secondary encrypting information, the primary encrypting
information and the
secondary encrypting information are matched.
[0062] For example, as shown in Fig. 10, the order issuing system is the
invoice issuing subsystem
of the merchants, and the identification codes are QR codes. When a customer
places an order, the
voice issuing subsystem of the merchant sends the order information of the
target order via the
remote service calling port to the invoice pre-issuing subsystem. The invoice
pre-issuing
subsystem receives the order information of the target order, then generates a
QR code signature
field by encryption using salt and issuing-pending order information. The
signature field is to
prevent network attack and protect the QR code information security. In
particular, the salt is
randomly generated arbitrary characters. Finally, the QR code link is sent to
the invoice issuing
subsystem of the merchant. The invoice issuing subsystem of the merchant
prints a purchase
receipt with the QR code, handed to the customer. The customer acquires
encrypted information
in the QR code by scanning the QR code, wherein the encrypted information is
attached to the
invoice request, so as for identifying the invoice request by the invoice
issuing subsystem by the
encrypted information in the invoice request. Then a target order electronic
invoice is issued.
[0063] The electronic invoice management method described in the
aforementioned embodiments
allows management of non-member customer electronic invoices by the back end.
For example,
the user scans codes based on third-party applications for invoice issuing,
wherein more diverse
off-line code scanning scenarios are involved to overcome limitations by the
traditional invoice
issuing system of no unified non-member customer electronic invoice
management. In the
17
Date Recue/Date Received 2022-02-01
meanwhile, access tokens of authorized third-party applications are used for
collectively managing
non-member customer electronic invoices. Besides, more user-side electronic
invoice self-services
are involved. In detail, compared with traditional code scan-based invoice
issuing, the third-party
applications can provide various self-services to users, including invoice
title modifications,
downloading electronic invoice format files, sending invoice issuing results,
and integrated
functions with the third-party applications. The user experience is improved
with reduced
workload for the personnel, tax risks, and human labors.
[0064] To clarify, although the operations in the aforementioned flow diagrams
follow the arrow
and explained in sequence, these steps are not necessarily performed strictly
following the
sequence directed by the arrows. Except the clear indications in the present
invention, the
implementation of these operations should not be restricted by certain
sequences. In other words,
these steps are allowed to follow the other implementation sequences. In the
meanwhile, at least
some parts of the flow diagrams may include multiple sub-steps or multiple
phases. These sub-
steps or phases are not necessarily performed in a restricted sequence.
Indeed, the fulfillment of
the sub-parts or phases may be achieved in turns or in an alternative manner.
[0065] An electronic invoice management device is further provided in the
present invention. As
shown in Fig. 11, the electronic invoice management device comprises: a
receiving module 112, a
sending module 114, a generation module 116, and a management module 118. The
receiving
module 112 is configured to receive an invoice request carrying an access
token from a third-party
application, wherein the invoice request is used to request an electronic
invoice for a target order;
a sending module 114 is configured to generate the invoice issuing page for
the target order based
on the invoice request when the third-party application identified by the
access token is an
authorized application, and send the invoice issuing page to the third-party
application; a
generation module 116 is configured to receive invoice information sent from
the third-party
application and generate the electronic invoice for the target order based on
the invoice information;
and a management module 118 is configured to relate the electronic invoice
with the access token,
wherein electronic invoices for target orders are managed by access tokens.
[0066] In an embodiment, the electronic invoice management device further
includes a primary
sending module, configured when the invoice permission request carrying an
access token from a
third-party application is received, to acquire usemame on the described third-
party application
and the secret key corresponding to the described use name, wherein the
described invoice
18
Date Recue/Date Received 2022-02-01
permission request is used to request permission to issue the electronic
invoice of the described
target order; and acquire the described access token based on the described
usemame and the
described secret key, and send the described access token to the described
third-party application.
[0067] In an embodiment, the electronic invoice management device further
includes a secondary
sending module, configured to send a notification to the described third-party
application for
indicating that the electronic invoice has been successfully issued; when the
invoice reviewing
request sent from the described third-party application is received, where if
the described invoice
reviewing request is detected to carry the described access token, acquire the
invoice information
of the described electronic invoice based on the described access token, and
send the invoice
information of the described electronic invoice to the described third-party
application.
[0068] In an embodiment, the electronic invoice management device further
includes a primary
modification module, configured to receive the title modification request sent
form the described
third-party application, wherein the described title modification request is
used to request
modifications on the invoice title of described electronic invoice; where if
the described title
modification request is detected to carry the described access token, send the
title medication page
to the described third-party application; receive the modified invoice title
from the title medication
page sent from the described third-party application so as to replace the
invoice title in the
described electronic invoice by the described modified invoice title for
obtaining the modified
electronic invoice, wherein the described modified electronic invoice and the
described access
token are related. Preferably, after obtaining the modified electronic
invoice, the method further
includes: off-writing the described electronic invoice before the
modification; and sending the
invoice information of the described modified electronic invoice to the
described third-party
application.
[0069] In an embodiment, the electronic invoice management device further
includes a judgement
module, configured to identify the primary invoice information according to
the described title
modification request; query recorded title modification times of the described
electronic invoice
in a modification table based on the described primary invoice information;
where if the number
of the described title modification times is greater than a pre-set number,
send a notification to the
described third-party application indicating the failure of the described
electronic invoice title
modification; and where if the number of the described title modification
times is smaller than the
19
Date Recue/Date Received 2022-02-01
described pre-set number, proceed to the procedure of sending the title
medication page to the
described third-party application.
[0070] In an embodiment, the electronic invoice management device further
includes a secondary
modification module, configured to receive the exchange request for a paper-
based invoice sent
by the described third-party application, wherein the described exchange
request for a paper-based
invoice is used to request the exchange from the described electronic invoice
to a paper-based
invoice; where if the described exchange request for a paper-based invoice is
detected to carry the
described access token, save the secondary invoice information of the
described electronic invoice
into the paper-based invoice pool, wherein the described paper-based invoice
pool is configured
to store the order information for issuing-pending paper-based invoices; and
off-write the
described electronic invoice.
[0071] In an embodiment, the electronic invoice management device further
includes an
encryption module, configured to receive the issuing-pending order information
of the described
target order sent by the order issuing system; generate an identification code
for the described
target order; generate a primary encrypting information of the described
identification code by the
salt according to the described issuing-pending order information; encrypt the
described
identification code by the described primary encrypting information to obtain
the encrypted
identification code; and send the encrypted identification code to the
described order issuing
system. The receiving module 113 is further configured to receive the invoice
request sent by the
third-party application, wherein the described invoice request is obtained by
scanning the
described encrypted identification code provided by the described order
issuing system by the
described third-party application. The electronic invoice management device
further includes a
matching module, configured to extract the secondary encrypting information
from the described
invoice request, and where if the described secondary encrypting information
matches with the
described primary encrypting information, proceed to the procedure of sending
the invoice issuing
page to the third-party application.
[0072] The detailed specifications of the electronic invoice management device
can refer to the
aforementioned specifications for the electronic invoice management method,
and are not
explained in detail hereby. Each described module in the electronic invoice
management device,
in whole or in part, may be accomplished by software, hardware, and their
combinations. Each
described module may be independent hardware or hardware embedded in the
processors of the
Date Recue/Date Received 2022-02-01
computer apparatus. In the meanwhile, each described module may be software
that is stored in
the memory unit of the computer apparatus, to invoke and execute the
corresponding performances
of the described modules.
[0073] In an embodiment of the present invention, a computer apparatus is
provided, wherein the
described computer apparatus can be a server supporting the back end with the
internal structure
diagram shown in Fig. 12. The computer apparatus comprises a processor, a
memory unit, a
network connection port, and a database connected by system bus control. The
memory unit of the
computer apparatus includes a nonvolatile storage medium and an internal
memory. The operating
system, computer programs, and databases are stored in the nonvolatile storage
medium. The
internal memory provides the operation environment for the execution of the
operating system and
the computer programs stored in the nonvolatile storage medium. The database
of the computer
apparatus is configured to store the message execution results. The network
connection port of the
computer apparatus is configured for communication with the external terminals
via network
connection. The execution of the computer apparatus by the processor permits
the method of
electronic invoice management.
[0074] It is comprehensible for those skilled in the art that the structure
shown in Fig. 12 represents
only a portion of structure associated with the applications of the present
invention. The computer
apparatus associated with the applications of the present invention are not
restricted or limited by
the structure. An exact computer apparatus may include more components or less
components than
that is shown in the drawings, possibly with combinations of some components
or different
component layouts.
[0075] In an embodiment, a computer apparatus is provided, comprising a memory
unit, a
processor, and computer programs stored in the memory unit executable on the
processor. When
the described processor executes the described computer programs, the
following procedures are
performed: receiving an invoice request carrying an access token from a third-
party application,
wherein the invoice request is used to request an electronic invoice for a
target order; when the
third-party application identified by the access token is an authorized
application, generating the
invoice issuing page for the target order based on the invoice request and
sending the invoice
issuing page to the third-party application; receiving invoice information
sent from the third-party
application to generate the electronic invoice for the target order based on
the invoice information;
21
Date Recue/Date Received 2022-02-01
and relating the electronic invoice with the access token, wherein electronic
invoices for target
orders are managed by access tokens.
[0076] When the described processor executes the described computer programs,
the following
procedures are performed: acquiring a usemame on the described third-party
application and the
secret key corresponding to the described use name when the invoice permission
request carrying
an access token from a third-party application is received, wherein the
described invoice
permission request is used to request permission to issue the electronic
invoice of the described
target order; and acquiring the described access token based on the described
usemame and the
described secret key, and sending the described access token to the described
third-party
application.
[0077] When the described processor executes the described computer programs,
the following
procedures are performed: sending a notification to the described third-party
application for
indicating that the electronic invoice has been successfully issued; when the
invoice reviewing
request sent from the described third-party application is received, where if
the described invoice
reviewing request is detected to carry the described access token, acquiring
the invoice information
of the described electronic invoice based on the described access token, and
sending the invoice
information of the described electronic invoice to the described third-party
application.
[0078] When the described processor executes the described computer programs,
the following
procedures are performed: receiving the title modification request sent form
the described third-
party application, wherein the described title modification request is used to
request modifications
on the invoice title of described electronic invoice; where if the described
title modification request
is detected to carry the described access token, sending the title medication
page to the described
third-party application; receiving the modified invoice title from the title
medication page sent
from the described third-party application so as to replace the invoice title
in the described
electronic invoice by the described modified invoice title for obtaining the
modified electronic
invoice, wherein the described modified electronic invoice and the described
access token are
related. Preferably, after obtaining the modified electronic invoice, the
method further includes:
off-writing the described electronic invoice before the modification; and
sending the invoice
information of the described modified electronic invoice to the described
third-party application.
[0079] When the described processor executes the described computer programs,
the following
procedures are performed: identifying the primary invoice information
according to the described
22
Date Recue/Date Received 2022-02-01
title modification request; querying recorded title modification times of the
described electronic
invoice in a modification table based on the described primary invoice
information; where if the
number of the described title modification times is greater than a pre-set
number, sending a
notification to the described third-party application indicating the failure
of the described
electronic invoice title modification; and where if the number of the
described title modification
times is smaller than the described pre-set number, proceeding to the
procedure of sending the title
medication page to the described third-party application.
[0080] When the described processor executes the described computer programs,
the following
procedures are performed: receiving the exchange request for a paper-based
invoice sent by the
described third-party application, wherein the described exchange request for
a paper-based
invoice is used to request the exchange from the described electronic invoice
to a paper-based
invoice; where if the described exchange request for a paper-based invoice is
detected to carry the
described access token, saving the secondary invoice information of the
described electronic
invoice into the paper-based invoice pool, wherein the described paper-based
invoice pool is
configured to store the order information for issuing-pending paper-based
invoices; and off-writing
the described electronic invoice.
[0081] When the described processor executes the described computer programs,
the following
procedures are performed: receiving the issuing-pending order information of
the described target
order sent by the order issuing system; generating an identification code for
the described target
order; generating a primary encrypting information of the described
identification code by the salt
according to the described issuing-pending order information; encrypting the
described
identification code by the described primary encrypting information to obtain
the encrypted
identification code; and sending the encrypted identification code to the
described order issuing
system. The invoice request by the third-party application is received, by
means of: receiving the
invoice request sent by the third-party application, wherein the described
invoice request is
obtained by scanning the described encrypted identification code provided by
the described order
issuing system by the described third-party application. The described method
further includes:
extracting the secondary encrypting information from the described invoice
request, and where if
the described secondary encrypting information matches with the described
primary encrypting
information, proceeding to the procedure of sending the invoice issuing page
to the third-party
application.
23
Date Recue/Date Received 2022-02-01
[0082] In an embodiment, a readable computer storage medium with computer
programs stored is
provided in the present invention. When the described computer programs are
executed on the
described processor, the following procedures are performed: receiving an
invoice request carrying
an access token from a third-party application, wherein the invoice request is
used to request an
electronic invoice for a target order; when the third-party application
identified by the access token
is an authorized application, generating the invoice issuing page for the
target order based on the
invoice request and sending the invoice issuing page to the third-party
application; receiving
invoice information sent from the third-party application to generate the
electronic invoice for the
target order based on the invoice information; and relating the electronic
invoice with the access
token, wherein electronic invoices for target orders are managed by access
tokens.
[0083] When the described computer programs are executed on the described
processor, the
following procedures are performed: acquiring a username on the described
third-party application
and the secret key corresponding to the described use name when the invoice
permission request
carrying an access token from a third-party application is received, wherein
the described invoice
permission request is used to request permission to issue the electronic
invoice of the described
target order; and acquiring the described access token based on the described
username and the
described secret key, and sending the described access token to the described
third-party
application.
[0084] When the described computer programs are executed on the described
processor, the
following procedures are performed: sending a notification to the described
third-party application
for indicating that the electronic invoice has been successfully issued; when
the invoice reviewing
request sent from the described third-party application is received, where if
the described invoice
reviewing request is detected to carry the described access token, acquiring
the invoice information
of the described electronic invoice based on the described access token, and
sending the invoice
information of the described electronic invoice to the described third-party
application.
[0085] When the described computer programs are executed on the described
processor, the
following procedures are performed: receiving the title modification request
sent form the
described third-party application, wherein the described title modification
request is used to
request modifications on the invoice title of described electronic invoice;
where if the described
title modification request is detected to carry the described access token,
sending the title
medication page to the described third-party application; receiving the
modified invoice title from
24
Date Recue/Date Received 2022-02-01
the title medication page sent from the described third-party application so
as to replace the invoice
title in the described electronic invoice by the described modified invoice
title for obtaining the
modified electronic invoice, wherein the described modified electronic invoice
and the described
access token are related. Preferably, after obtaining the modified electronic
invoice, the method
further includes: off-writing the described electronic invoice before the
modification; and sending
the invoice information of the described modified electronic invoice to the
described third-party
application.
[0086] When the described computer programs are executed on the described
processor, the
following procedures are performed: identifying the primary invoice
information according to the
described title modification request; querying recorded title modification
times of the described
electronic invoice in a modification table based on the described primary
invoice information;
where if the number of the described title modification times is greater than
a pre-set number,
sending a notification to the described third-party application indicating the
failure of the described
electronic invoice title modification; and where if the number of the
described title modification
times is smaller than the described pre-set number, proceeding to the
procedure of sending the title
medication page to the described third-party application.
[0087] When the described computer programs are executed on the described
processor, the
following procedures are performed: receiving the exchange request for a paper-
based invoice sent
by the described third-party application, wherein the described exchange
request for a paper-based
invoice is used to request the exchange from the described electronic invoice
to a paper-based
invoice; where if the described exchange request for a paper-based invoice is
detected to carry the
described access token, saving the secondary invoice information of the
described electronic
invoice into the paper-based invoice pool, wherein the described paper-based
invoice pool is
configured to store the order information for issuing-pending paper-based
invoices; and off-writing
the described electronic invoice.
[0088] When the described computer programs are executed on the described
processor, the
following procedures are performed: receiving the issuing-pending order
information of the
described target order sent by the order issuing system; generating an
identification code for the
described target order; generating a primary encrypting information of the
described identification
code by the salt according to the described issuing-pending order information;
encrypting the
described identification code by the described primary encrypting information
to obtain the
Date Recue/Date Received 2022-02-01
encrypted identification code; and sending the encrypted identification code
to the described order
issuing system. The invoice request by the third-party application is
received, by means of:
receiving the invoice request sent by the third-party application, wherein the
described invoice
request is obtained by scanning the described encrypted identification code
provided by the
described order issuing system by the described third-party application. The
described method
further includes: extracting the secondary encrypting information from the
described invoice
request, and where if the described secondary encrypting information matches
with the described
primary encrypting information, proceeding to the procedure of sending the
invoice issuing page
to the third-party application.
[0089] All or portions of the aforementioned procedures are comprehensible for
those skilled in
the art, and may be achieved by the computer program configured for sending
commands to the
related hardware. The computer programs are stored in the computer readable
nonvolatile memory
unit. When the computer programs are executed on the processor, the
aforementioned procedure
of the embodiments may be included. In particular, all the referred memory
units, storages,
databases, as well as any other media in the embodiments provided in the
present invention, may
include nonvolatile and/or volatile memory units. The nonvolatile memory units
may include read-
only memory (ROM), programmable ROM (PROM), electrical programmable ROM
(EPROM),
electrically erasable programmable ROM (EEPROM) or flash memory. The volatile
memory units
may include random access memory (RAM) or external cache memory. To describe
RAM without
limiting, RAM may be different formats such as static RAM (SRAM), dynamic RAM
(DRAM),
synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced
DDRSDRAM (EDDRSDRAM), Synchlink DRAM (SLDRAM), direct rambus RAM (RDRAM),
direct rambus dynamic RAM (DRDRAM) and rambus dynamic RAM (RDRAM).
[0090] The aforementioned technical strategies can be combined as possible. To
be concise, not
all possible combinations of each technical strategy in the aforementioned
embodiments are
explained. However, the combinations of these technical strategies without any
conflict shall fall
in the protection scope of the present invention.
[0091] The aforementioned contents are preferred embodiments of the present
invention, and 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.
26
Date Recue/Date Received 2022-02-01
