U.S. patent application number 15/454653 was filed with the patent office on 2017-06-29 for method and server for pushing information proactively.
The applicant listed for this patent is Huawei Device Co., Ltd.. Invention is credited to Zhigang CHEN, Haizhang CHI, Cheng LIU, Yanmin WANG.
Application Number | 20170185654 15/454653 |
Document ID | / |
Family ID | 43485186 |
Filed Date | 2017-06-29 |
United States Patent
Application |
20170185654 |
Kind Code |
A1 |
CHEN; Zhigang ; et
al. |
June 29, 2017 |
METHOD AND SERVER FOR PUSHING INFORMATION PROACTIVELY
Abstract
A method for pushing information proactively includes: receiving
updated data; querying search records that match the updated data;
determining search records that meet a push condition, and
obtaining user information corresponding to the search records that
meet the push condition; pushing, according to the user
information, the updated data to all or part of users corresponding
to the user information. In the embodiments of the present
invention, after receiving updated data, the server proactively
obtains the search records of users, screens the users according to
the push condition, and pushes the updated data to the screened
users. In this way, the information is proactively pushed, which
shortens the time interval of providing information for the users,
and improves the efficiency of obtaining needed information by the
users.
Inventors: |
CHEN; Zhigang; (Shenzhen,
CN) ; LIU; Cheng; (Shenzhen, CN) ; CHI;
Haizhang; (Shenzhen, CN) ; WANG; Yanmin;
(Warsaw, PL) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Huawei Device Co., Ltd. |
Shenzhen |
|
CN |
|
|
Family ID: |
43485186 |
Appl. No.: |
15/454653 |
Filed: |
March 9, 2017 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
13728141 |
Dec 27, 2012 |
9646060 |
|
|
15454653 |
|
|
|
|
PCT/CN2011/080206 |
Sep 27, 2011 |
|
|
|
13728141 |
|
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G06F 16/248 20190101;
G06F 16/951 20190101; H04L 67/26 20130101; G06F 16/2468
20190101 |
International
Class: |
G06F 17/30 20060101
G06F017/30; H04L 29/08 20060101 H04L029/08 |
Foreign Application Data
Date |
Code |
Application Number |
Sep 30, 2010 |
CN |
201010505939.5 |
Claims
1. A method for pushing information proactively, comprising:
receiving, by a server, a key word input by a user; providing, by
the server, one or more search results that matches the key word;
recording, by the server, user information according of the user
and the key word; recording, by the server, a search result on
which the user performs an user operation, wherein the search
result is one of the one or more search results; updating, by the
server, the search result on which the user operation is performed;
pushing, by the server, according to the user information, the
updated search result to the user.
2. The method according to claim 1, wherein the user operation
performed on the search result of the one or more search results
comprises: collection.
3. The method according to claim 2, wherein the user information is
login information of the user or identifier information of a
terminal used by the user stored on the server; wherein the login
information of the user comprises one or more of the following: a
user name, a nickname, and an Email address associated with the
user; and wherein the identifier information of the terminal used
by the user comprises a telephone number of the user.
4. The method according to claim 2, wherein the key word is sent by
the terminal used by the user.
5. The method according to claim 2, wherein the pushing, by the
server, according to the user information, the updated search
result to the user comprises: pushing, by the server, according to
the user information, the updated search result to the user without
the user initiating another search using the key word.
6. A method for pushing information proactively, comprising:
receiving, by a server, a key word input by a user; providing, by
the server, one or more search results that matches the key word;
recording, by the server, user information according of the user
and the key word; recording, by the server, a search result on
which the user performs an user operation, wherein the search
result is one of the one or more search results; receiving, by the
server, updated data relates to the search result on which the user
operation is performed; pushing, by the server, according to the
user information, the updated data to the user.
7. The method according to claim 6, wherein the user operation
performed on the search result of the one or more search results
comprises: collection.
8. The method according to claim 6, wherein the user information is
login information of the user or identifier information of a
terminal used by the user stored on the server; wherein the login
information of the user comprises one or more of the following: a
user name, a nickname, and an Email address associated with the
user; and wherein the identifier information of the terminal used
by the user comprises a telephone number of the user.
9. The method according to claim 6, wherein the updated data
matches the key word input by the user.
10. The method according to claim 6, wherein the key word is sent
by the terminal used by the user.
11. The method according to claim 6, wherein the pushing, by the
server, according to the user information, the updated data to the
user comprises: pushing, by the server, according to the user
information, the updated data to the user without the user
initiating another search using the key word.
12. A server for pushing information proactively, comprising: a
memory storing a computer program comprising instructions; and
computer hardware configured to execute the instructions in the
computer program to: receive a key word input by a user; provide
one or more search results that matches the key word; record user
information according of the user and the key word; record a search
result on which the user performs an user operation, wherein the
search result is one of the one or more search results; update the
search result on which the user operation is performed; push
according to the user information, the updated search result to the
user.
13. The server according to claim 12, wherein the user operation
performed on the search result of the one or more search results
comprises: collection.
14. The server according to claim 13, wherein the user information
is login information of the user or identifier information of a
terminal used by the user stored on the server; wherein the login
information of the user comprises one or more of the following: a
user name, a nickname, and an Email address associated with the
user; and wherein the identifier information of the terminal used
by the user comprises a telephone number of the user.
15. The server according to claim 13, wherein the instructions
further include instructions to: receive the key word input by the
user from the terminal used by the user.
16. The server according to claim 13, wherein the instructions
further include instructions to: push, according to the user
information, the updated search result to the user without the user
initiating another search using the key word.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of U.S. patent
application Ser. No. 13/728,141, filed on Dec. 27, 2012, which is a
continuation of International Patent Application No.
PCT/CN2011/080206, filed on Sep. 27, 2011. The International
Application claims priority to Chinese Patent Application No.
201010505939.5, filed on Sep. 30, 2010. All of the afore-mentioned
patent applications are hereby incorporated by reference in their
entireties.
FIELD OF THE INVENTION
[0002] The present invention relates to the field of network
technologies, and in particular, to a method and a server for
pushing information proactively.
BACKGROUND OF THE INVENTION
[0003] With the development and popularity of the Internet and
related technologies, some service systems provide people with a
huge amount of information through the Internet. More and more
marketing activities are conducted online, and searching for
information by using the Internet and shopping online gradually
become part of people's daily life.
[0004] Currently, people search for information or do shopping
online mainly by sending information requests, and related service
systems that provide information mainly provide information
passively. For example, a user enters a key word in the search box
on a service provider website to search for information related to
the key word, and the search engine of the service provider
captures related information in the database according to the key
word and provides the related information as a search result for
the user, so that the user performs subsequent operations.
[0005] However, when the search engine fails to find information
that matches the key word in the database, it displays information
indicating no search result is found to the user and then ends the
information provision process; if data is updated in the database
subsequently and information that matches the key word is added,
the service system can provide the user with the matched
information only when the user initiates access next time and
enters the key word to search for information again. The prior art
has the following disadvantages: For the service system, providing
information passively prolongs the time interval of providing
information and reduces the efficiency of obtaining information by
users.
SUMMARY OF THE INVENTION
[0006] Embodiments of the present invention provide a method and a
server for pushing information proactively, so that after updated
data is received, information can be proactively pushed to users
related to the information, thereby shortening the time interval of
providing information.
[0007] In order to solve the foregoing technical problems,
technical solutions of the embodiments of the present invention are
as follows:
[0008] An embodiment of the present invention provides a method for
pushing information proactively, including:
[0009] receiving updated data;
[0010] querying search records that match the updated data;
[0011] determining whether the search records that match the
updated data meet a push condition, and obtaining user information
corresponding to the search records that meet the push condition;
and
[0012] pushing, according to the user information, the updated data
to all or part of users corresponding to the user information.
[0013] An embodiment of the present invention further provides a
server for pushing information proactively, including:
[0014] a data receiving unit, configured to receive updated
data;
[0015] a record querying unit, configured to query search records
that match the updated data;
[0016] an information querying unit, configured to determine
whether the search records that match the updated data meet a push
condition, and obtain user information corresponding to the search
records that meet the push condition; and
[0017] an information pushing unit, configured to push, according
to the user information, the updated data to all or part of users
corresponding to the user information.
[0018] In the embodiments of the present invention, after receiving
updated data, the server proactively obtains the search records of
users, screens the users according to the push condition, and
pushes the updated data to the screened users. In this way, the
information is proactively pushed, thereby shortening the time
interval of providing information for the users, and improving the
efficiency of obtaining needed information by the users. In
addition, users are screened by adding a push condition, which
effectively saves resources needed for pushing the information and
increases the accuracy of pushing information to users, thereby
improving the user experience.
BRIEF DESCRIPTION OF THE DRAWINGS
[0019] To illustrate the technical solutions in the embodiments of
the present invention more clearly, the accompanying drawings
required for describing the embodiments or the prior art are
introduced briefly in the following. Apparently, the accompanying
drawings in the following description merely show some embodiments
of the present invention, and persons of ordinary skill in the art
can derive other drawings from the accompanying drawings without
creative efforts.
[0020] FIG. 1 is a flowchart of a method for pushing information
proactively according to an embodiment of the present
invention;
[0021] FIG. 2 is a flowchart of another method for pushing
information proactively according to an embodiment of the present
invention;
[0022] FIG. 3 is a flowchart of another method for pushing
information proactively according to an embodiment of the present
invention;
[0023] FIG. 4 is a schematic structural diagram of a server for
pushing information proactively according to an embodiment of the
present invention; and
[0024] FIG. 5 is a schematic structural diagram of another server
for pushing information proactively according to an embodiment of
the present invention.
DETAILED DESCRIPTION OF THE EMBODIMENTS
[0025] To enable persons skilled in the art to further understand
the features and technical contents of the present invention, the
present invention is hereinafter described in detail with reference
to the accompanying drawings. The accompanying drawings are
provided for reference only, and are not intended to limit the
present invention.
[0026] In the prior art, the service system provides information
passively. When data information is updated in the database, the
service system can provide information for a user only when the
user initiates a request to access the data information. This
prolongs the time interval of providing information by the service
system and reduces the efficiency of obtaining information by the
user, and therefore cannot meet people's requirements and is
disadvantageous for the user to obtain information. Based on this,
embodiments of the present invention provide a method and a server
for pushing information proactively, so that information can be
pushed to users related to the information proactively after
updated data is received.
[0027] The following describes the technical solutions of the
present invention with the help of drawings and embodiments.
[0028] FIG. 1 is a flowchart of a method for pushing information
proactively according to an embodiment of the present
invention.
[0029] The method may include:
[0030] Step 101: Receive updated data.
[0031] When data in a database is updated, the updated data may be
sent to a server and received by the server. The server may
specifically be a recommendation engine server. The receiving
action of the server may be triggered immediately when data is
updated, or a time interval is preset, and the server is triggered
to receive updated data once at the time interval, or a times
threshold may be set, for example, when data update occurs three
times in the database, the server is triggered to receive the
updated data of the three times. The updated data may specifically
include a newly added field in the database or an updated field
value of an old field in the database, which is not limited
herein.
[0032] Step 102: Query search records that match the updated
data.
[0033] After receiving the updated data, the server queries search
records that match the data, where the search records are records
about a user's search actions made by the server each time when the
server receives a search request from the user. The content of the
search records may include key words, database data that matches
the key words, search results, browsing times, whether to collect,
whether to download, user information, and so on, or a part
thereof, which is not limited herein. When querying search records,
the server may query the search records according to a matching
relationship between the updated data and key words in the search
records. Details are provided in the subsequent embodiments.
[0034] Step 103: Determine search records that meet a push
condition, and obtain user information corresponding to the search
records that meet the push condition.
[0035] After finding the search records that match the updated
data, the server checks whether the search records meet the push
condition; if yes, the server further retrieves user information
corresponding to the search records. The push condition may be set
according to an actual need. The search records that meet the push
condition may include one or more of the following: a search record
with a search result indicating that no matching item is found, a
search record where after a search result is output, the user does
not download the found information, a search record where after a
search result is output, the user collects one or more pieces of
found information, or a search record where after a search result
is output, the number of times/pieces of found information browsed
by the user exceeds a threshold, where the threshold may be set
according to the actual need, for example, three times. The search
record with a search result indicating that no matching item is
found may be a record where according to the search request of a
user, the server fails to find items that match the key word
entered by the user. The search record with no downloading may be a
record where after the search is completed, the user's final action
is no downloading the found information; the search record with
collection may be a record that the user may collect information
found by the user; the search record with browsing may be a record
that the user browses the found information.
[0036] After obtaining the search records that meet the push
condition, the server further obtains user information
corresponding to the search records, where the user information may
be login information of the user or identifier information of a
terminal used by the user, for example, the login information of
the user may be one or more of the following: user name, nickname,
and Email; the identifier information of the terminal used by the
user may be one or more of the user's mobile phone number or
telephone number. A user information database may be set up in
advance.
[0037] Step 104: Push, according to the user information, the
updated data to all or part of users corresponding to the user
information.
[0038] After obtaining the user information, the server may choose
to push the updated data to all or part of users. For example, if
the server obtains the Email box of a user, the server may push the
updated data by sending an Email to the Email box of the user; or
if the server obtains the identifier of a terminal used by the
user, for example, a mobile phone number, the server may push the
updated data to the terminal of the user by using a PUSH
technology. Certainly, other modes may also be used to push the
updated data, which are not limited herein.
[0039] In this embodiment of the present invention, after receiving
updated data, the server proactively obtains the search records of
users, screens the users according to the push condition, and
pushes the updated data to the screened users. In this way, the
information is proactively pushed, thereby shortening the time
interval of providing information for the users, and improving the
efficiency of obtaining needed information by the users. In
addition, users are screened by adding a push condition, which
effectively saves resources needed for pushing the information and
increases the accuracy of pushing information to users, thereby
improving the user experience.
[0040] FIG. 2 is a flowchart of another method for pushing
information proactively according to an embodiment of the present
invention.
[0041] The method may include:
[0042] Step 201: Receive updated data, where the updated data
includes a newly added field.
[0043] In this embodiment, if a user A enters a key word "camping
tent" to search, when the search engine fails to find a search
result that matches the key word "camping tent" in the database,
the search engine displays information indicating that no matching
item is found to the user A. The server keeps the search record of
the user A, where the search record may include user information of
the user A (for example, Email of the user A), key word "camping
tent", and search result indicating that no matching item is
found.
[0044] When data is updated in the database, the server is
triggered to receive updated data. In this embodiment, the updated
data includes a newly added field "tent" in the database and the
field value of the newly added field is "camping tent" and
"mountaineering tent".
[0045] Step 202: Query search records that match the newly added
field.
[0046] The server may query, by using the field name of the newly
added field, search records stored on the server, and when the key
word or part of the key word of one or more search records is the
field name or field value of the newly added field, use the one or
more search records as the search record(s) matching the newly
added field; or the server may also query, by using the field name
of the newly added field, search records stored on the server, and
when the key word or part of the key word of one or more search
records fuzzily matches the field name or field value of the newly
added field, use the one or more search records as the search
record(s) matching the newly added field.
[0047] In this embodiment, after receiving the newly added field
"tent" and the field value thereof, the server retrieves the search
records and queries for whether there are search records that match
the field name "tent" or field values such as "camping tent" and
"mountaineering tent" of the field "tent". In this embodiment,
because the key word "camping tent" in the search records of the
user A is the same as the field value "camping tent" of the newly
added field "tent", the search records of the user A about the key
word "camping tent" match the newly added field "tent". Certainly,
in other embodiments, a matching rule may be set according to the
actual need, for example, the matching rule is set to be that part
of the newly added field name or part of the field value
corresponding to the newly added field is the same as part of the
key word. In this case, using the above example, the search records
about the key word "camping tent" may match data of the field value
"camping tent", data including the field name "tent", and data of
the field value "mountaineering tent", that is, the data of the
field name "tent" and the data of the field value "mountaineering
tent" match the word "tent" in the key word "camping tent". Then,
the search records about the key word "camping tent" are considered
to match the newly added field "tent".
[0048] Step 203: Obtain user information corresponding to the
search record with a search result indicating that no matching item
is found.
[0049] By querying the search records of the user A, the server
knows that the record where "the search result indicates that no
matching item is found" meets the push condition, and then obtains
information of the user A, which may specifically be the Email of
the user A.
[0050] Step 204: Send, according to the user information of the
user A, the updated data through the Email.
[0051] In this step, the server sends the newly added field "tent"
in the database and its specific information, for example, the
field value, to the Email box of the user A according to the Email
address obtained in step 203. Then, the data information is
automatically pushed.
[0052] In this embodiment, when receiving new information of the
database, the server queries for and screens pre-stored search
records, and sends the new information to users corresponding to
the screened search records. In this way, the information is pushed
proactively, thereby shortening the time interval of providing
information for users and increasing the efficiency of obtaining
needed information by the users. In addition, the users are
screened by adding a push condition, which effectively saves
resources needed for pushing the information and increases the
accuracy of pushing information to the users, thereby improving the
user experience.
[0053] FIG. 3 is a flowchart of another method for pushing
information proactively according to an embodiment of the present
invention.
[0054] The method may include:
[0055] Step 301: Receive updated data, where the updated data
includes an updated field value of an old field.
[0056] In this embodiment, if a user B searches by entering a key
word "tent", after the search engine finds search results that
match the key word "tent" in the database, it displays the search
results that match the key word "tent" to the user B. Then, the
user B collects one or more pieces of information of the search
results. The server keeps the search record of the user B, where
the search record may include user information of the user B,
search key word "tent", and one or more pieces of information
collected from the search results.
[0057] When data is updated in the database, the server is
triggered to receive updated data. In this embodiment, the updated
data information is the updated field value of the old field "tent"
in the database.
[0058] Step 302: Query search records that match the old field.
[0059] The server may query, by using the updated field value of
the old field, search records stored on the server, and when the
key word or part of the key word of one or more search records is
the field name or updated field value of the old field, use the one
or more search records as the search record(s) matching the old
field; or, the server may also query, by using the updated field
value of the old field, search records stored on the server, and
when the key word or part of the key word of one or more search
records fuzzily matches the field name or updated field value of
the old field, use the one or more search records as the search
record(s) matching the old field.
[0060] In this embodiment, after receiving the updated data of the
old field "tent", the server retrieves the search records and query
whether there are search records that match the field "tent". In
this embodiment, the key word "tent" in the search records of the
user B is the same as the field name "tent" of the old field, and
therefore the search records of the user B about the key word
"tent" match the old field "tent".
[0061] Step 303: Obtain terminal identifier information
corresponding to the search records that meet the push
condition.
[0062] By querying the search records of the user B, it can be
known that the user B collects one or more pieces of information of
the search result, so that the search records meet the push
condition. In this case, the server further obtains the user
information of the user B. In this embodiment, the user information
of the user B is the terminal identifier information of the user B,
for example, mobile phone number. In other embodiments, the push
condition may be set to a record of "no downloading" or a record
where the number of times and/or pieces of information in the
"browsed" search result exceeds a preset threshold.
[0063] Step 304: Push, by using the PUSH technology, the updated
data to a terminal that has the identifier information.
[0064] In this step, the server pushes, by using the PUSH
technology, the updated field value of the old field "tent" in the
database to the terminal that has the above identifier information,
so that the data information is automatically pushed. The PUSH
technology is the prior art, and is not further described
herein.
[0065] In this embodiment, when receiving updated field value
information of the database, the server queries for and screens
pre-stored search records, and sends the updated data to users
corresponding to the screened search records. In this way, the
information is pushed proactively, thereby shortening the time
interval of providing information for users and increasing the
efficiency of obtaining needed information by the users. In
addition, the users are screened by adding a push condition, which
effectively saves resources needed for pushing the information and
increases the accuracy of pushing information to the users, thereby
improving the user experience.
[0066] Persons of ordinary skill in the art may understand that all
or part of the steps in the preceding embodiments may be completed
by hardware following instructions of a program. The program may be
stored in a computer readable storage medium such as a read-only
memory (ROM), a random access memory (RAM), a magnetic disk or a
compact disk.
[0067] Detailed above is a method provided in embodiments of the
present invention. The following briefly describes the structure of
a server that implements the above method.
[0068] FIG. 4 is a schematic structural diagram of a server for
pushing information proactively according to an embodiment of the
present invention.
[0069] The server may include the following units:
[0070] a data receiving unit 401, configured to receive updated
data;
[0071] a record querying unit 402, configured to query search
records that match the updated data;
[0072] an information querying unit 403, configured to determine
search records that meet a push condition, and obtain user
information corresponding to the search records that meet the push
condition; and
[0073] an information pushing unit 404, configured to push,
according to the user information, the updated data to all or part
of users corresponding to the user information.
[0074] In this embodiment, when data is updated in the database,
the updated data may be sent to the server, and then received by
the data receiving unit 401 of the server, where the updated data
may specifically include a newly added field or an updated field
value of an old field in the database. After the data receiving
unit 401 receives the updated data, the record querying unit 402
queries search records that match the updated data. When querying
the search records, the data querying unit 402 may query according
to a matching relationship between the updated data and the key
word in the search records. After the record querying unit 402
finds search records that match the updated data, the information
querying unit 403 checks whether the search records meet a push
condition; if true, the information querying unit 403 further
retrieves the user information corresponding to the search records,
where the push condition may be set according to the actual need
and the search records that meet the push condition may include one
or more of the following: a search record with a search result
indicating that no matching item is found, a search record where
after a search result is output, the user does not download the
found information, a search record where after a search result is
output, the user collects one or more pieces of found information,
or a search record where after a search result is output, the
number of times and/or pieces of found information browsed by the
user exceeds a threshold, where the threshold may be set according
to the actual need, for example, three times; and the user
information may be login information of the user or identifier
information of a terminal used by the user, for example, the login
information of the user may be one or more of the following: user
name, nickname, and Email, and the identifier information of the
terminal used by the user may be one or more of the user's mobile
phone number and telephone number, and a user information database
may be set up in advance. After the information querying unit 403
obtains user information, the information pushing unit 404 pushes
updated data according to the user information.
[0075] In this embodiment, by using the above units, the
information is pushed proactively, which shortens the time interval
of providing information for users and increases the efficiency of
obtaining needed information by users; in addition, users are
screened by adding a push condition, which effectively saves
resources needed for pushing the information and increases the
accuracy of pushing information to users, thereby improving the
user experience.
[0076] FIG. 5 is a schematic structural diagram of another server
for pushing information proactively according to an embodiment of
the present invention.
[0077] The server may include a data receiving unit 501, a record
querying unit 502, an information querying unit 503, and an
information pushing unit 504.
[0078] The record querying unit 502 may further include:
[0079] a first querying subunit 5021, configured to: when the
updated data includes a newly added field, query search records
that match the newly added field; and
[0080] a second querying subunit 5022, configured to: when the
updated data includes an updated field value of an old field, query
search records that match the old field.
[0081] In another embodiment, the first querying subunit 5021 may
specifically query, by using the field name of the newly added
field, search records stored on the server, and when the key word
or part of the key word of one or more search records is the field
name or field value of the newly added field, use the one or more
search records as the search record(s) matching the newly added
field; or the server may also query, by using the field name of the
newly added field, search records stored on the server, and when
the key word or part of the key word of one or more search records
fuzzily matches the field name or field value of the newly added
field, use the one or more search records as the search record(s)
matching the newly added field.
[0082] The second querying subunit 5022 may specifically query, by
using the updated field value of the old field, search records
stored on the server, and when the key word or part of the key word
of one or more search records is the field name or updated field
value of the old field, use the one or more search records as the
search record(s) matching the old field; or, query, by using the
updated field value of the old field, search records stored on the
server, and when the key word or part of the key word of one or
more search records fuzzily matches the field name or updated field
value of the old field, use the one or more search records as the
search record(s) matching the old field.
[0083] The information querying unit 503 may be specifically
configured to obtain user information of users who initiate the
search records that meet the push condition, where the user
information is similar to that provided in the foregoing
embodiments, and is not further described herein. The information
pushing unit 504 may be specifically configured to obtain terminal
identifier information in the user information, and push, by using
a PUSH technology, the updated data to a terminal that has the
identifier information.
[0084] In this embodiment, by using the above units, the
information is pushed proactively, which shortens the time interval
of providing information for users and increases the efficiency of
obtaining needed information by users; in addition, users are
screened by adding a push condition, which effectively saves
resources needed for pushing the information and increases the
accuracy of pushing information to users, thereby improving the
user experience. The specific implementation of each unit on the
server refers to the method provided in the foregoing embodiments,
and is not further described herein.
[0085] Embodiments of the present invention described in the
foregoing are not limitations for the protection scope of the
present invention. Any modification, equivalent replacement, and
improvement made without departing from the spirit and principle of
the present invention all fall in the protection scope of the
embodiments of the present invention.
* * * * *