Language selection

Search

Patent 3127882 Summary

Third-party information liability

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

Claims and Abstract availability

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

  • At the time the application is open to public inspection;
  • At the time of issue of the patent (grant).
(12) Patent: (11) CA 3127882
(54) English Title: SHORT MESSAGE SENDING METHOD, DEVICE, AND COMPUTER SYSTEM
(54) French Title: METHODE, DISPOSITIF ET SYSTEME INFORMATIQUE D'ENVOI DE MESSAGE COURT
Status: Granted and Issued
Bibliographic Data
(51) International Patent Classification (IPC):
  • H04L 51/04 (2022.01)
  • H04L 09/06 (2006.01)
  • H04L 09/30 (2006.01)
  • H04W 04/14 (2009.01)
  • H04W 12/033 (2021.01)
  • H04W 12/04 (2021.01)
(72) Inventors :
  • CHENG, WEI (China)
  • JIANG, HAO (China)
(73) Owners :
  • 10353744 CANADA LTD.
(71) Applicants :
  • 10353744 CANADA LTD. (Canada)
(74) Agent: JAMES W. HINTONHINTON, JAMES W.
(74) Associate agent:
(45) Issued: 2024-01-09
(22) Filed Date: 2021-08-12
(41) Open to Public Inspection: 2022-02-14
Examination requested: 2021-10-12
Availability of licence: N/A
Dedicated to the Public: N/A
(25) Language of filing: English

Patent Cooperation Treaty (PCT): No

(30) Application Priority Data:
Application No. Country/Territory Date
202010817242.5 (China) 2020-08-14

Abstracts

English Abstract


Disclosed in the present invention are a short message sending method, device,
and computer
system. The mentioned method comprises: receiving a short message sending
request from a sender,
wherein the described short message sending request includes send-pending
target user tags; acquiring
encrypted send-pending contents corresponding to the described sender;
acquiring and encrypting contact
information for users corresponding to the described target user tags; and
sending the described encrypted
contact information and described encrypted send-pending contents to the
described target short message
service provider, wherein the described target short message service provider
decrypts and sends the
described send-pending contents to the described users according to the
described contact information.
Therefore, short message contents from senders will not be accessed by a third
party except short message
service providers responsible for sending messages to users, wherein senders
cannot access user contact
information, to prevent message content disclosure and protect user privacy.


French Abstract

Il est décrit une méthode denvoi de messages courts, un dispositif et un système informatique. La méthode mentionnée comprend ce qui suit : la réception dune demande denvoi de message court dun expéditeur dans laquelle la demande denvoi de message court décrite comprend des étiquettes dutilisateur cible en attente denvoi; lacquisition de contenus chiffrés en attente denvoi correspondant à lexpéditeur décrit; lacquisition et le chiffrement de coordonnées pour les utilisateurs correspondant aux étiquettes dutilisateur cible décrites; et lenvoi des coordonnées chiffrées décrites et des contenus chiffrés en attente denvoi décrits au fournisseur du service de messages courts cible décrit, dans lequel le fournisseur de services de messages courts cible décrit déchiffre et envoie les contenus en attente denvoi décrits aux utilisateurs décrits en fonction des coordonnées décrites. Par conséquent, les contenus des messages courts des expéditeurs ne seront pas accessibles à un tiers, à lexception des fournisseurs de services de messages courts chargés denvoyer des messages aux utilisateurs, les expéditeurs ne pouvant pas accéder aux coordonnées des utilisateurs, afin dempêcher la divulgation du contenu des messages et de protéger la vie privée des utilisateurs.

Claims

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


Claims:
1. A computer system for sending a short message, the system comprising:
one or more processors, configured to execute a plurality of program commands,
wherein the
plurality of program commands includes:
receiving a short message sending request from a sender, wherein the short
message
sending request includes a plurality of send-pending target user tags;
acquiring encrypted send-pending contents by a primary shared key
corresponding to
the sender, wherein the encrypted send-pending contents append verification
code for a
content review, wherein the encrypted send-pending contents are stored after
the send-
pending contents are passed successfiffly the content review for a plurality
of pre-set
keywords, wherein the primary shared key is generated from a public key from a
target
short message service provider and a private key liom the sender;
acquiring and encrypting contact information of users corresponding to the
target user
tags, wherein each user includes one or more target user tags canying the
contact
information of each user, wherein the contact infoimation is encrypted by
generating a
secondary shared key; and
sending the encrypted contact information and the encrypted send-pending
contents to
a target short message service provider, so as to decrypt and send the send-
pending
contents to the users by the target short message service provider according
to the
contact information; and
a memory connected to the one or more processors, wherein the memory is
configured to store the
plurality of program commands.
2. The system of claim 1, wherein the plurality of program commands further
includes receiving and
storing the encrypted send-pending contents encrypted by a primary shared key
from the sender.
3. The system of claim 2, wherein the primary shared key is generated
from a public key from the target
short message service provider and a private key from the sender.

4. The system of any one of claims 1 to 3, wherein the plurality of program
commands further includes
decrypting the send-pending contents according to the public key from the
sender and the private key
from the target short message service provider by the target short message
service provider, then
sending the send-pending contents.
5. The system of claim 2, wherein the plurality of program commands further
includes verifying that if
the encrypted send-pending contents pass a review.
6. The system of claim 5, wherein the plurality of program commands further
includes, where if the
review is not passed, refusing to store the encrypted send-pending contents.
7. The system of any one of claims 5 to 6, wherein the plurality of program
commands further includes
sending a verification code to a sender, so as to generate a verification
information according to the
verification code where if the send-pending contents do not include a pre-set
keyword.
8. The system of claim 7, where if the verification information is correct,
wherein an encrypted send-
pending contents is determined to pass a review.
9. The system of any one of claims 7 and 8, wherein the verification
information is attached on the
encrypted send-pending contents.
10. The system of any one of claims 2 to 7, wherein the plurality of program
commands further includes:
receiving a send-pending content modification request from the sender;
sending the encrypted send-pending contents to the sender, wherein the sender
uses the primary
shared key to decrypt and modify the send-pending contents, then return the
send-pending contents
encrypted by the primary shared key; and
storing the returned send-pending contents with modifications from the sender.
11. The system of any one of claims 1 to 10, wherein the plurality of program
commands further includes:
16

encrypting the contact information with a secondary shared key by a processing
terminal, wherein
the secondary shared key is generated from a public key from the target short
message service
provider and a private key from the processing terminal; and
decrypting and sending the send-pending contents to the users according to the
contact information
by the target short message service provider, further includes:
decrypting based on the public key from the processing terminal and a private
key from
the target short message service provider and acquiring the contact
information.
12. The system of any one of claims 1 to 11, wherein the public key for each
party is generated by an
independent key generation center on a third-party server.
13. The system of any one of claims 1 to 11, wherein the private key for each
party is generated by an
independent key generation center on a third-party server.
14. A short message sending method, the method comprising:
receiving a short message sending request from a sender, wherein the short
message sending request
includes a plurality of send-pending target user tags;
acquiring encrypted send-pending contents by a primary shared key
corresponding to the sender,
wherein the encrypted send-pending contents append verification code for a
content review,
wherein the encrypted send-pending contents are stored after the send-pending
contents are passed
successfully the content review for a plurality of pre-set keywords, wherein
the primary shared key
is generated from a public key from a target short message service provider
and a private key from
the sender;
acquiring and encrypting contact information of users corresponding to the
target user tags, wherein
each user includes one or more target user tags canying the contact
information of each user,
wherein the contact information is encrypted by generating a secondary shared
key; and
sending the encrypted contact information and the encrypted send-pending
contents to a target short
17

message service provider, so as to decrypt and send the send-pending contents
to the users by the
target short message service provider according to the contact information.
15. The method of claim 14, further includes receiving and storing the
encrypted send-pending contents
encrypted by a primary shared key from the sender.
16. The method of claim 15, wherein the primary shared key is generated from a
public key from the target
short message service provider and a private key from the sender.
17. The method of any one of claims 14 to 16, further includes decrypting the
send-pending contents
according to the public key from the sender and the private key from the
target short message service
provider by the target short message service provider, then sending the send-
pending contents.
18. The method of claim 15, further includes verifying that if the encrypted
send-pending contents pass a
review.
19. The method of claim 18, further includes, where if the review is not
passed, refiising to store the
encrypted send-pending contents.
20. The method of any one of claims 18 to 19, further includes sending a
verification code to a sender, so
as to generate a verification information according to the verification code
where if the send-pending
contents do not include a pre-set keyword.
21. The method of claim 20, further includes, where if the verification
information is correct, wherein an
encrypted send-pending contents is determined to pass a review.
22. The method of any one of claims 20 and 21, wherein the verification
information is attached on the
encrypted send-pending contents.
23. The method of any one of claims 15 to 19, further includes:
receiving a send-pending content modification request from the sender;
18

sending the encrypted send-pending contents to the sender, wherein the sender
uses the primary
shared key to decrypt and modify the send-pending contents, then return the
send-pending contents
encrypted by the primary shared key; and
storing the returned send-pending contents with modifications from the sender.
24. The method of any one of claims 14 to 23, further includes:
encrypting the contact information with a secondary shared key by a processing
terminal, wherein
the secondary shared key is generated from a public key from the target short
message service
provider and a private key from the processing terminal; and
decrypting and sending the send-pending contents to the users according to the
contact information
by the target short message service provider, further includes:
decrypting based on the public key from the processing terminal and a private
key from
the target short message service provider and acquiring the contact
information.
25. The method of any one of claims 14 to 24, wherein the public key for each
party is generated by an
independent key generation center on a third-party server.
26. The method of any one of claims 14 to 24, wherein the private key for each
party is generated by an
independent key generation center on a third-party server.
27. A short message sending method comprising:
a processing terminal receives a short message sending request from a sender,
wherein the short
message sending request includes a plurality of send-pending target user tags;
the processing terminal acquires encrypted send-pending contents by a primary
shared key
corresponding to the sender, wherein the encrypted send-pending contents
append verification code
for a content review, wherein the encrypted send-pending contents are stored
after the send-pending
contents are passed successfully the content review for a plurality of pre-set
keywords, wherein the
19

primary shared key is generated from a public key from a target short message
service provider and
a private key from the sender;
the processing terminal acquires and encrypts contact information for users
corresponding to the
target user tags, wherein each user includes one or more target user tags
carrying the contact
information of each user, wherein the contact information is encrypted by
generating a secondary
shared key; and
the processing terminal sends the encrypted contact information and the
encrypted send-pending
contents to a target short message service provider, so as to decrypt and send
the send-pending
contents to the users by the target short message service provider according
to the contact
information.
28. The method of claim 27, further includes the processing terminal receives
and stores the encrypted
send-pending contents encrypted by a primary shared key from the sender.
29. The method of claim 28, wherein the primary shared key is generated from a
public key from the target
short message service provider and a private key from the sender.
30. The method of any one of claims 27 to 29, further includes the processing
terminal decrypts the send-
pending contents according to the public key from the sender and the private
key from the target short
message service provider by the target short message service provider, then
sends the send-pending
contents.
31. The method of claim 30, further includes the processing terminal verifies
that if the encrypted send-
pending contents pass a review.
32. The method of claim 31, further includes, where if the review is not
passed, the processing terminal
refuses to store the encrypted send-pending contents.
33. The method of any one of claims 31 to 32, further includes the processing
terminal sends a verification
code to a sender, so as to generate a verification information according to
the verification code where
if the send-pending contents do not include a pre-set keyword.

34. The method of claim 33, where if the verification information is correct,
wherein an encrypted send-
pending contents is determined to pass a review.
35. The method of any one of claims 33 and 34, wherein the verification
information is attached on the
encrypted send-pending contents.
36. The method of any one of claims 28 to 32, further includes:
the processing terminal receives a send-pending content modification request
from the sender;
the processing terminal sends the encrypted send-pending contents to the
sender, wherein the
sender uses the primary shared key to decrypt and modify the send-pending
contents, then return
the send-pending contents encrypted by the primary shared key; and
the processing terminal stores the returned send-pending contents with
modifications from the
sender.
37. The method of any one of claims 27 to 36, further includes:
the processing terminal encrypts the contact information with a secondary
shared key by a
processing terminal, wherein the secondary shared key is generated from a
public key from the
target short message service provider and a private key from the processing
terminal; and
the processing terminal decrypts and sends the send-pending contents to the
users according to the
contact information by the target short message service provider, further
includes:
the processing terminal decrypts based on the public key from the processing
terminal
and a private key from the target short message service provider and acquires
the contact
information.
38. The method of any one of claims 27 to 37, wherein the public key for each
party is generated by an
independent key generation center on a third-party server.
21

39. The method of any one of claims 27 to 37, wherein the private key for each
party is generated by an
independent key generation center on a third-party server.
40. A short message sending device comprising:
a receiving module, configured to receive a short message sending request from
a sender, wherein
the short message sending request includes a plurality of send-pending target
user tags;
an acquisition module, configured to acquire encrypted send-pending contents
by a primary shared
key corresponding to the sender, and acquire and encrypt contact information
for users
corresponding to the target user tags, wherein the contact information is
encrypted by generating a
secondary shared key, wherein the encrypted send-pending contents append
verification code for a
content review, wherein the encrypted send-pending contents are stored after
the send-pend
contents are passed successfully the content review for a plurality of pre-set
keywords, wherein
each user includes one or more target user tags carrying the contact
information of each user; and
a processing module, configured to send the encrypted contact information and
the encrypted send-
pending contents to a target short message service provider, so as to decrypt
and send the send-
pending contents to the users by the target short message service provider
according to the contact
information.
41. The device of claim 40, wherein the receiving module is further configured
to receive and store the
encrypted send-pending contents encrypted by a primary shared key from the
sender.
42. The device of claim 41, wherein the primary shared key is generated from a
public key from the target
short message service provider and a private key from the sender.
43. The device of claim 40, wherein the processing module is further
configured to decrypt the send-
pending contents according to a public key from the sender and a private key
from the target short
message service provider by the target short message service provider, then
send the send-pending
contents.
22

44. The device of claim 40, wherein the processing module is further
configured to verify that if the
encrypted send-pending contents pass a review.
45. The device of claim 44, wherein the processing module is further
configured to where if the review is
not passed, refusing to store the encrypted send-pending contents.
46. The device of any one of claims 44 to 45, wherein the processing module is
further configured to send
a verification code to a sender, so as to generate a verification information
according to the verification
code where if the send-pending contents do not include a pre-set keyword.
47. The device of claim 46, where if the verification information is correct,
wherein an encrypted send-
pending contents is determined to pass a review.
48. The device of any one of claims 46 and 47, wherein the verification
information is attached on the
encrypted send-pending contents.
49. The device of any one of claims 40 to 48, wherein the processing module is
further configured to:
receive a send-pending content modification request from the sender;
send the encrypted send-pending contents to the sender, wherein the sender
uses the primary shared
key to decrypt and modify the send-pending contents, then return the send-
pending contents
encrypted by the primary shared key; and
store the returned send-pending contents with modifications from the sender.
50. The device of any one of claims 40 to 49, wherein the processing module is
further configured to
encrypt the contact information with a secondary shared key by a processing
terminal, wherein the
secondary shared key is generated from a public key from the target short
message service provider
and a private key from the processing terminal; and
decrypt and send the send-pending contents to the users according to the
contact information by
23

the target short message service provider, further configured to:
decrypt based on the public key from the processing terminal and a private key
from the
target short message service provider and acquiring the contact information.
51. The device of claim 43, wherein the public key for each party is generated
by an independent key
generation center on a third-party server.
52. The device of claim 43, wherein the private key for each party is
generated by an independent key
generation center on a third-party server.
24

Description

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


SHORT MESSAGE SENDING METHOD, DEVICE, AND COMPUTER SYSTEM
Technical Field
100011 The present invention relates to the field of cloud computing security,
in particular, to a method, a
device, and a computer system for short message sending.
Background
[0002] With rapid growth of the internet, business retailers commonly send
promotion messages to users
for advocating services or products. In order to enhance advocating effects,
business retailers also purchase
the short message sending services from value added ISVs, wherein messages are
compiled by the value-
added ISVs and sent to target users. However, the value-added ISVs are
required to reach target users,
indicating that the value-added ISVs should access contact information of
target users.
[0003] ISV entered cloud platforms are able to send short messages to users
via services provided by the
cloud platforms. However, the cloud platforms should not directly reveal user
contact information to the
value-added ISV, in order to protect the user privacy. On the other hand, the
cloud platforms are not
supposed to access message contents from the value-added ISVs concerning any
possible competitions. As
a result, the value-added ISV are not willing to enter cloud platforms,
consequently suppressing the
development for the cloud platforms.
Summary
[0004] In order to solve the problems due to limitations of the current
technologies, the present invention
aims at providing a method, a device, and a computer system for short message
sending.
[0005] To achieve the forementioned goal, from the first perspective, a short
message sending method is
provided in the present invention, comprising:
[0006] receiving a short message sending request from a sender, wherein the
described short message
sending request includes send-pending target user tags;
[0007] acquiring encrypted send-pending contents corresponding to the
described sender;
[0008] acquiring and encrypting contact information for users corresponding to
the described target user
tags; and
[0009] sending the described encrypted contact information and described
encrypted send-pending
contents to the described target short message service provider, so as to
decrypt and send the described
send-pending contents to the described users by the described target short
message service provider
according to the described contact information.
1
Date Recue/Date Received 2021-10-12

[0010] In some embodiments of the present invention, the described method
includes:
[0011] receiving and storing the described encrypted send-pending contents
encrypted by a primary shared
key from the sender, wherein the described primary shared key is generated
from a public key from the
described target short message service provider and a private key from the
described sender; and
[0012] the procedure of sending the described encrypted contact information
and described encrypted
send-pending contents to the described target short message service provider,
so as to decrypt and send the
described send-pending contents to the described users by the described target
short message service
provider according to the described contact information, consisting of:
[0013] decrypting the described send-pending contents according to the public
key from the described
sender and the private key from the described target short message service
provider by the described target
short message service provider, then sending the described send-pending
contents.
[0014] In some embodiments of the present invention, the procedure of
receiving and storing the described
encrypted send-pending contents encrypted by a primary shared key from the
sender, wherein the described
primary shared key is generated from a public key from the described target
short message service provider
and a private key from the described sender, comprises:
[0015] verifying that if the described encrypted send-pending contents pass a
review; and
[0016] where if the review is not passed, refusing to store the described
encrypted send-pending contents.
[0017] In some embodiments of the present invention, the described short
message sending request
includes a verification information, wherein the procedure of verifying that
if the described encrypted send-
pending contents pass a review comprises:
[0018] sending the verification code to the sender, so as to generate the
verification information according
to the verification code where if the described send-pending contents do not
include a pre-set keyword; and
[0019] where if the described verification information is correct, the
described encrypted send-pending
contents is determined to pass the review.
[0020] In some embodiments of the present invention, the described method
includes:
[0021] receiving a send-pending content modification request from the
described sender;
[0022] sending the described encrypted send-pending contents to the described
sender, wherein the
described sender uses the described primary shared key to decrypt and modify
the described send-pending
contents, then return the described send-pending contents encrypted by the
described primary shared key;
and
[0023] storing the described returned send-pending contents with modifications
from the described sender.
2
Date Recue/Date Received 2021-10-12

[0024] In some embodiments of the present invention, the described contact
information for users
corresponding to the described target user tags are acquired and encrypted, by
means of:
[0025] encrypting the described contact information with a secondary shared
key by a processing terminal,
therein the described secondary shared key is generated from a public key from
the described target short
message service provider and a private key from the described processing
terminal;
[0026] decrypting and sending the described send-pending contents to the
described users according to the
described contact information by the described target short message service
provider, comprising:
[0027] decrypting based on the public key from the described processing
terminal and a private key from
the described target short message service provider and acquiring the
described contact information.
[0028] From the second perspective, a short message sending method is provided
in the present invention,
comprising that:
[0029] the processing terminal receives a short message sending request from a
sender, wherein the
described short message sending request includes send-pending target user
tags;
[0030] the processing terminal acquires encrypted send-pending contents
corresponding to the described
sender;
100311 the processing terminal acquires and encrypts contact information for
users corresponding to the
described target user tags;
[0032] the processing terminal sends the described encrypted contact
information and described encrypted
send-pending contents to the described target short message service provider;
and
[0033] the described target short message service provider decrypts and sends
the described send-pending
contents to the described users according to the described contact
information.
[0034] From the third perspective, a short message sending device is provided
in the present invention,
comprising:
[0035] a receiving module, configured to receive a short message sending
request from a sender, wherein
the described short message sending request includes send-pending target user
tags;
[0036] an acquisition module, configured to acquire encrypted send-pending
contents corresponding to the
described sender; to acquires and encrypt contact information for users
corresponding to the described
target user tags; and
[0037] a processing module, configured to send the described encrypted contact
information and described
encrypted send-pending contents to the described target short message service
provider, so as to decrypt
and send the described send-pending contents to the described users by the
described target short message
service provider according to the described contact information.
[0038] In some embodiments of the present invention, the described receiving
module can also be
configured to receive and store the described encrypted send-pending contents
encrypted by a primary
3
Date Recue/Date Received 2021-10-12

shared key from the sender, wherein the described primary shared key is
generated from a public key from
the described target short message service provider and a private key from the
described sender; and the
described processing module can also be configured to send the described
encrypted contact information
and the described encrypted send-pending contents to the described target
short message service provider,
so as to decrypt and acquire the described send-pending contents by the
described target short message
service provider according to the public key from the described sender and the
private key from the
described target short message service provider.
[0039] From the fourth perspective, a computer system is provided in the
present invention, comprising:
[0040] one or more processors; and
[0041] a memory connected to the described one or more processors, wherein the
described memory is
used to store program commands, for performing the following procedures when
the described program
commands are executed on the described one or more processors:
[0042] receiving a short message sending request from a sender, wherein the
described short message
sending request includes send-pending target user tags;
[0043] acquiring encrypted send-pending contents corresponding to the
described sender;
[0044] acquiring and encrypting contact information for users corresponding to
the described target user
tags; and
[0045] sending the described encrypted contact information and described
encrypted send-pending
contents to the described target short message service provider, so as to
decrypt and send the described
send-pending contents to the described users by the described target short
message service provider
according to the described contact information.
[0046] The present invention provides benefits of that:
[0047] disclosed in the present invention are a short message sending method,
device, and computer
system. The mentioned method comprises: receiving a short message sending
request from a sender,
wherein the described short message sending request includes send-pending
target user tags; acquiring
encrypted send-pending contents corresponding to the described sender;
acquiring and encrypting contact
information for users corresponding to the described target user tags; and
sending the described encrypted
contact information and described encrypted send-pending contents to the
described target short message
service provider, wherein the described target short message service provider
decrypts and sends the
described send-pending contents to the described users according to the
described contact information.
Therefore, short message contents from senders will not be accessed by a third
party except short message
service providers responsible for sending messages to users, wherein senders
cannot access user contact
information, to prevent message content disclosure and protect user privacy.
4
Date Recue/Date Received 2021-10-12

[0048] Furthermore, the present invention also provides that by receiving and
storing the described
encrypted send-pending contents encrypted by a primary shared key from the
sender, the described primary
shared key is generated from a public key from the described target short
message service provider and a
private key from the described sender; and the procedure of sending the
described encrypted contact
information and described encrypted send-pending contents to the described
target short message service
provider, so as to decrypt and send the described send-pending contents to the
described users by the
described target short message service provider according to the described
contact information, comprises:
decrypting the described send-pending contents according to the public key
from the described sender and
the private key from the described target short message service provider by
the described target short
message service provider, then sending the described send-pending contents.
[0049] Products and applications of the present invention do not necessarily
carry all the forementioned
features.
Brief descriptions of the drawings
[0050] In order to make the technical strategies of the present invention
clearer, the accompanying
drawings for the present invention will be briefly introduced below.
Obviously, the following drawings in
the descriptions are only a portion of embodiments of the present invention.
Those skilled in the art are able
to generate other configurations according to the provided drawings without
requiring any creative works.
[0051] Fig. 1 is a structure diagram of the short message sending system
provided in the present invention.
[0052] Fig. 2 is a flow diagram of the short message sending system provided
in the present invention.
[0053] Fig. 3 is a schematic diagram of the thread pool scheduling provided in
the present invention.
[0054] Fig. 4 is a flow diagram of the method provided in the present
invention.
Detailed descriptions
[0055] 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
accompany 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.
[0056] As discussed in the background, in order to solve the forementioned
problems, a short message
sending method is provided in the present invention, as shown in Fig. 1.
Business retailers wanting short
message sending services can use value-added services from the value-added
ISVs, wherein the tasks of
compiling and sending messages are scheduled to the value-added ISVs. Based on
the demands of the
business retailer, target users of marketing messages are determined, and the
marketing messages are
compiled by the value-added ISVs. The value-added services include to store
available short messages to a
Date Recue/Date Received 2021-10-12

short message storage platform. Then, the determined user tags are sent to the
marketing platform, wherein
the marketing platform returns the marketing messages and contact information
of users and the contact
information is sent to the short massage platform. The short message platform
sends marketing messages
and connected information to the value-added ISVs, wherein the value-added
ISVs send the marketing
message to users.
[0057] The forementioned system for short message sending method comprises:
[0058] Step 1, key initialization.
[0059] As shown in Fig. 1, an independent key generation center (KGC) can be
allocated on a third-party
server. The described key generating center can use the CPK algorithm to
generate a public key for each
entity in the system, wherein the public keys are stored in a CPK module. The
described key generate center
can use any other algorithms to generate public keys, not constrained by the
present invention.
[0060] The ISV, the marketing system, and the short message service provider
individually upload the
identifications (ID) and the device fingerprint IDs (such as the IP address of
the major server and the hash
value of the MAC address) to the short message platform.
100611 The short message platform generates a verification ID (Appid) for each
marketing service provider
and a shared key field (Appsecret) between the short message platform and the
described marketing service
provider.
[0062] The short message platform returns a corresponding verification ID
(Appid) for each marketing
platform and a shared key field (Appsecret) between the short message platform
and the described
marketing platform. The short message platform returns a corresponding
verification ID (Appid) for each
short message service provider and a shared key field (Appsecret) between the
short message platform and
the described short message service provider. Preferably, all short message
service providers can have the
same verification ID (Appid) and the same shared key field (Appsecret).
[0063] The short message platform sends the verification IDs (Appid) of short
message service providers
to each marketing service provider and the marketing platform.
[0064] The short message platform synchronizes verification IDs (Appid) and
shared key field (Appsecret)
of all value-added ISV, marketing platforms and short message service
providers to the key generation
center.
[0065] The key generation center generates a public key and a private key for
each ISV, marketing
platform and short message service provider, individually, and stores all
public keys on the CPK module.
[0066] The key generation acquires a request according to the private keys of
the value-added ISVs,
marketing platforms and short message service providers, and returns the CPK
module and corresponding
private keys.
6
Date Recue/Date Received 2021-10-12

[0067] The acquired request of each private key is required to include Appid,
HMAC (Appsecret,
randsMIDI1Appidlltimestamp), rands, ID, and timestamp, wherein the Appid is
the Appid of the request
sender; the HMAC (Appsecret, randsHIDHAppidlltimestamp) is a verification code
generated for applying
the HMAC algorithm according to the Appsecret, rands, ID, Appid, and timestamp
of the request sender;
the rands is randomly generated fields; and the timestamp is the time stamp.
[0068] The key generation center verifies identification of the message
verification code according to
acquired Appsecret of the request sender; and
[0069] after passing the message verification code identification, the key
generation center returns a
private key of the request sender and the corresponding CPK module to the
request sender, wherein the
private key of the request sender is encrypted according to the AES algorithm
based on the Appsecret.
[0070] The request sender decrypts with the own Appsecret to acquire the own
private key and the CPK
module carrying the public key.
[0071] Step 2, based on retailers' demands, compiling message contents on the
short message sending
platform and encrypt by the marketing service vendor; and
[0072] the short message platform provides a short message editing function,
wherein the marketing
service provider can edit short messages with the short message editing
function. The complied message is
reviewed by a pre-set reviewing script on the short message platform, wherein
the pre-set reviewing script
is used to determine that if a short message contains a pre-set key word,
including words related to
pornography, gambling, and drug abuse, as well as any illegal contents. During
the review, a random token
is generated by the short message platform. When no pre-set key word is
detected in the review, the review
script generates a verification code according to the random token and the
Appsecret of the marketing
service provider. The marketing service provider generates a primary shared
key (sharekey 1) based on the
own private key and the public key of the short message service provide stored
in the SPK module, wherein
the generated primary shared key is used to encrypt the short message. The
verification code is appended
to the encrypted short message, and the short message platform determines if
the short message passes the
review according to the verification code. Where if the review is passed, the
short message platform stores
the encrypted short message contents; and where if the review is not passed,
the short message platform
refuses to store the encrypted short message contents.
[0073] Preferably, retailers are allowed to not authorize marketing service
providers, and to compile short
messages on the short message platform by retailers.
[0074] Step 3, based on retailers' demands, determining target user tags for
receiving short messages by
the marketing service provider;
[0075] the marketing platform has pre-set user tags featuring user properties
or demands, wherein one user
has one or more user tags carrying contact information of each user, such as
cell phone numbers.
7
Date Recue/Date Received 2021-10-12

[0076] The marketing service provider can choose one or more user tags, and
the short message can be
sent to all users with the described one or more user tags, or to one of users
with the described one or more
user tags.
[0077] Preferably, retailers are allowed to not authorize the marketing
service provider, to determine target
user tags for receiving short messages by retailers.
[0078] Step 4, based on the determined target user tags, acquiring contact
information of corresponding
users by the marketing service provider;
[0079] Step 5, encrypting user contact information by the marketing service
platform, then sending the
encrypted contact information and the encrypted short message contents to the
short message service
provider; and according to the private key of the marketing service platform
and the public key of the short
message service provider from the CPK module.
[0080] generating a secondary shared key (sharekey2), to encrypt contact
information according to the
secondary shared key by AES algorithm. After encryption, the marketing service
provider sends the
encrypted short message contents and encrypted contact information by the
marketing service provider to
the short message service provider.
[0081] Step 6, decrypting the encrypted short message contents and encrypted
contact information by the
short message service provider, and sending the short message contents to
users according to contact
information based on decryption results;
[0082] generating the primary shared key (sharekey 1) by the short message
service provider via the ECDH
key negotiation algorithm according to the public key of the marketing service
platform and the private key
of the short message service provider from the CPK modules, to decrypt the
encrypted short message
contents based on the primary shared key (sharekey 1), and acquire the send-
pending message contents;
[0083] generating the secondary shared key (sharekey2) by the short message
service provider via the
ECDH key negotiation algorithm according to the public key of the marketing
service platform and the
private key of the short message service provider from the CPK modules, to
decrypt the encrypted contact
information based on the secondary shared key (sharekey2), and acquire the
send-pending contact
information; and
[0084] sending message contents to target users according to contact
information by the short message
service provider.
[0085] The forementioned system prevents irrelevant participants in the system
from accessing clear
message contents or contact information, wherein message content is secured
while the user privacy is
prevented from disclosure. In the meanwhile, the short message service
provider can use a sender public
key and own private key to decrypt received contents, wherein the performance
suppression by key
negotiation is reduced and the overall system operation efficiency is
improved.
8
Date Recue/Date Received 2021-10-12

[0086] Embodiment two
[0087] Corresponding to the forementioned embodiment, as shown in Fig. 2, a
short message sending
method is provided in the present invention, comprising:
[0088] 210, receiving a short message sending request from a sender, wherein
the described short message
sending request includes send-pending target user tags;
[0089] 220, acquiring encrypted send-pending contents corresponding to the
described sender;
[0090] preferably, the procedure of acquiring and encrypting the described
contact information for users
corresponding to the described target user tags, by means of
100911 221, encrypting the described contact information with a secondary
shared key by a processing
terminal, wherein the described secondary shared key is generated from a
public key from the described
target short message service provider and a private key from the described
processing terminal;
[0092] the procedure of decrypting and sending the described send-pending
contents to the described users
by the described target short message service provider according to the
described contact information,
consisting of:
[0093] decrypting the described send-pending contents according to the public
key from the described
sender and the private key from the described target short message service
provider by the described target
short message service provider, then sending the described send-pending
contents.
[0094] 230, acquiring and encrypting contact information for users
corresponding to the described target
user tags; and
[0095] 240, sending the described encrypted contact information and described
encrypted send-pending
contents to the described target short message service provider, so as to
decrypt and send the described
send-pending contents to the described users by the described target short
message service provider
according to the described contact information.
[0096] Preferably, the described method comprises:
[0097] 241, receiving and storing the described encrypted send-pending
contents encrypted by a primary
shared key from the sender, wherein the described primary shared key is
generated from a public key from
the described target short message service provider and a private key from the
described sender; and
[0098] the procedure of sending the described encrypted contact information
and described encrypted
send-pending contents to the described target short message service provider,
so as to decrypt and send the
described send-pending contents to the described users by the described target
short message service
provider according to the described contact information, consisting of:
[0099] 242, decrypting the described send-pending contents according to the
public key from the described
sender and the private key from the described target short message service
provider by the described target
short message service provider, then sending the described send-pending
contents.
9
Date Recue/Date Received 2021-10-12

[0100] Preferably, the procedure of receiving and storing the described
encrypted send-pending contents
encrypted by a primary shared key from the sender, wherein the described
primary shared key is generated
from a public key from the described target short message service provider and
a private key from the
described sender, comprises:
[0101] 243, verifying that if the described encrypted send-pending contents
pass a review; and
[0102] where if the review is not passed, refusing to store the described
encrypted send-pending contents.
[0103] Preferably, the described short message sending request includes a
verification information,
wherein the procedure of verifying that if the described encrypted send-
pending contents pass a review
comprises:
[0104] 244, sending the verification code to the sender, so as to generate the
verification information
according to the verification code where if the described send-pending
contents do not include a pre-set
keyword; and
[0105] where if the described verification information is correct, the
described encrypted send-pending
contents is determined to pass the review.
[0106] Preferably, the described method includes:
[0107] 245, receiving a send-pending content modification request from the
described sender;
[0108] sending the described encrypted send-pending contents to the described
sender, wherein the
described sender uses the described primary shared key to decrypt and modify
the described send-pending
contents, then return the described send-pending contents encrypted by the
described primary shared key;
and
[0109] storing the described returned send-pending contents with modifications
from the described sender.
[0110] Embodiment three
[0111] Corresponding to the forementioned embodiment, as shown in Fig. 3, a
short message sending
device is provided in the present invention, comprising:
[0112] a receiving module 310, configured to receive a short message sending
request from a sender,
wherein the described short message sending request includes send-pending
target user tags;
[0113] an acquisition module 320, configured to acquire encrypted send-pending
contents corresponding
to the described sender; to acquires and encrypt contact information for users
corresponding to the described
target user tags; and
[0114] a processing module 330, configured to send the described encrypted
contact information and
described encrypted send-pending contents to the described target short
message service provider, so as to
Date Recue/Date Received 2021-10-12

decrypt and send the described send-pending contents to the described users by
the described target short
message service provider according to the described contact information.
[0115] Preferably, the described receiving module 310 can also be configured
to receive and store the
described encrypted send-pending contents encrypted by a primary shared key
from the sender, wherein
the described primary shared key is generated from a public key from the
described target short message
service provider and a private key from the described sender; and the
described processing module 330 can
also be configured to send the described encrypted contact information and the
described encrypted send-
pending contents to the described target short message service provider, so as
to decrypt and acquire the
described send-pending contents by the described target short message service
provider according to the
public key from the described sender and the private key from the described
target short message service
provider.
[0116] Preferably, the described processing module 330 can also be configured
to verify that if the
described encrypted send-pending contents pass a review; and where if the
review is not passed, refusing
to store the described encrypted send-pending contents.
[0117] Preferably, the described processing module 330 can also be configured
to send the verification
code to the sender, so as to generate the verification information according
to the verification code where
if the described send-pending contents do not include a pre-set keyword; and
where if the described
verification information is correct, the described encrypted send-pending
contents is determined to pass the
review.
[0118] Preferably, the described processing module 330 can also be configured
to receive a send-pending
content modification request from the described sender; send the described
encrypted send-pending
contents to the described sender, wherein the described sender uses the
described primary shared key to
decrypt and modify the described send-pending contents, then return the
described send-pending contents
encrypted by the described primary shared key; and store the described
returned send-pending contents
with modifications from the described sender.
[0119] Preferably, the described processing module 330 can also be configured
to encrypt the described
contact information with a secondary shared key by a processing terminal,
wherein the described secondary
shared key is generated from a public key from the described target short
message service provider and a
private key from the described processing terminal; and based on the public
key from the described
processing terminal and a private key from the described target short message
service provider, the
described contact information is decrypted and acquired.
[0120] Embodiment four
11
Date Recue/Date Received 2021-10-12

[0121] Corresponding to the forementioned method, device, and system, a
computer system is provided in
the embodiment four of the present invention, comprising: one or more
processors; and a memory
connected to the described one or more processors, wherein the described
memory is used to store program
commands, for performing the following procedures when the described program
commands are executed
on the described one or more processors:
[0122] receiving a short message sending request from a sender, wherein the
described short message
sending request includes send-pending target user tags;
[0123] acquiring encrypted send-pending contents corresponding to the
described sender;
[0124] acquiring and encrypting contact information for users corresponding to
the described target user
tags; and
[0125] sending the described encrypted contact information and described
encrypted send-pending
contents to the described target short message service provider, so as to
decrypt and send the described
send-pending contents to the described users by the described target short
message service provider
according to the described contact information.
[0126] In particular, Fig. 4 illustrates structures of the computer system,
comprising a processor 1510, a
video display adapter 1511, a disk driver 1512, an input/output connection
port 1513, an internet connection
port 1514, and a memory 1520. The forementioned processor 1510, video display
adapter 1511, disk driver
1512, input/output connection port 1513, and internet connection port 1514 are
connected and
communicated via the system bus control 1530.
[0127] In particular, the processor 1510 can adopt a universal CPU (central
processing unit), a
microprocessor, an ASIC (application specific integrated circuit) or the use
of one or more integrated
circuits. The processor is used for executing associated programmes to achieve
the technical strategies
provided in the present invention.
[0128] The memory 1520 can adopt a read-only memory (ROM), a random access
memory (RAM), a
static memory, a dynamic memory, etc. The memory 1520 is used to store the
operating system 1521 for
controlling the electronic apparatus 1500, and the basic input output system
(BIOS) for controlling the low-
level operations of the electronic apparatus 1500. In the meanwhile, the
memory can also store the internet
browser 1523, data storage management system 1524, the device label
information processing system 1525,
etc. The described device label information processing system 1525 can be a
program to achieve the
forementioned methods and procedures in the present invention. In summary,
when the technical strategies
are performed via software or hardware, the codes for associated programs are
stored in the memory 1520,
then called and executed by the processor 1510. The input/output connection
port 1513 is used to connect
with the input/output modules for information input and output. The
input/output modules can be used as
12
Date Recue/Date Received 2021-10-12

components that are installed in the devices (not included in the drawings),
or can be externally connected
to the devices to provide the described functionalities. In particular, the
input devices may include
keyboards, mouse, touch screens, microphones, various types of sensors, etc.
The output devices may
include monitors, speakers, vibrators, signal lights, etc.
[0129] The internet connection port 1514 is used to connect with a
communication module (not included
in the drawings), to achieve the communication and interaction between the
described device and other
equipment. In particular, the communication module may be connected by wire
connection (such as USB
cables or internet cables), or wireless connection (such as mobile data, WIFI,
Bluetooth, etc.).
[0130] The system bus control 1530 include a path to transfer data across each
component of the device
(such as the processor 1510, the video display adapter 1511, the disk driver
1512, the input/output
connection port 1513, the internet connection port 1514 and the memory 1520).
[0131] Besides, the described electronic device 1500 can access the collection
condition information from
the collection condition information database 1541 via a virtual resource
object, so as for conditional
statements and other purposes.
[0132] To clarify, although the schematic of the forementioned device only
includes the processor 1510,
the video display adapter 1511, the disk driver 1512, the input/output
connection port 1513, the internet
connection port 1514, the memory 1520 and the system bus control 1530, the
practical applications may
include the other necessary components to achieve successful operations. It is
comprehensible for those
skilled in the art that the structure of the device may comprise of less
components than that in the drawings,
to achieve successful operations.
[0133] By the forementioned descriptions of the applications and embodiments,
those skilled in the art
can understand that the present invention can be achieved by combination of
software and necessary
hardware platforms. Based on this concept, the present invention is considered
as providing the technical
benefits in the means of software products. The mentioned computer software
products are stored in the
storage media such as ROM/RAM, magnetic disks, compact disks, etc. The
mentioned computer software
products also include using several commands to have a computer device (such
as a personal computer, a
server, or a network device) to perform portions of the methods described in
each or some of the
embodiments in the present invention.
[0134]
The embodiments in the description of the present invention are explained step-
by-step. The
similar contents can be referred amongst the embodiments, while the
differences amongst the embodiments
are emphasized. In particular, the system and the corresponding embodiments
have similar contents to the
method embodiments. Hence, the system and the corresponding embodiments are
described concisely, and
the related contents can be referred to the method embodiments. The described
system and system
embodiments are for demonstration only, where the components that are
described separately can be
13
Date Recue/Date Received 2021-10-12

physically separated or not. The components shown in individual units can be
physical units or not. In other
words, the mentioned components can be at a single location or distributed
onto multiple network units. All
or portions of the modules can be used to achieve the purposes of embodiments
of the present invention
based on the practical scenarios. Those skilled in the art can understand and
apply the associated strategies
without creative works.
[01325] The forementioned contents of preferred embodiments of the present
invention shall not limit the
applications of the present invention. Therefore, all alterations,
modifications, equivalence, improvements
of the present invention fall within the scope of the present invention.
14
Date Recue/Date Received 2021-10-12

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

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

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

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

Event History

Description Date
Inactive: Grant downloaded 2024-01-16
Inactive: Grant downloaded 2024-01-16
Letter Sent 2024-01-09
Grant by Issuance 2024-01-09
Inactive: Cover page published 2024-01-08
Pre-grant 2023-11-27
Inactive: Final fee received 2023-11-27
Inactive: Office letter 2023-11-24
Notice of Allowance is Issued 2023-10-27
Letter Sent 2023-10-27
Inactive: Office letter 2023-10-26
Inactive: Approved for allowance (AFA) 2023-10-24
Inactive: Q2 passed 2023-10-24
Amendment Received - Voluntary Amendment 2023-10-11
Amendment Received - Response to Examiner's Requisition 2023-10-11
Examiner's Report 2023-07-13
Inactive: Report - QC failed - Minor 2023-07-12
Withdraw from Allowance 2023-02-07
Inactive: Office letter 2023-02-07
Inactive: Final fee received 2023-02-02
Letter Sent 2022-12-22
Notice of Allowance is Issued 2022-12-22
Inactive: QS passed 2022-12-20
Inactive: Approved for allowance (AFA) 2022-12-20
Amendment Received - Response to Examiner's Requisition 2022-12-01
Amendment Received - Voluntary Amendment 2022-12-01
Examiner's Report 2022-08-01
Inactive: Report - No QC 2022-07-31
Amendment Received - Response to Examiner's Requisition 2022-06-29
Amendment Received - Voluntary Amendment 2022-06-29
Examiner's Report 2022-03-02
Inactive: Report - No QC 2022-02-28
Letter sent 2022-02-15
Inactive: Cover page published 2022-02-15
Advanced Examination Determined Compliant - paragraph 84(1)(a) of the Patent Rules 2022-02-15
Letter Sent 2022-02-15
Application Published (Open to Public Inspection) 2022-02-14
Inactive: First IPC assigned 2022-02-14
Inactive: IPC assigned 2022-02-14
Inactive: IPC assigned 2022-02-14
Inactive: IPC assigned 2022-02-14
Inactive: IPC assigned 2022-02-14
Inactive: IPC assigned 2022-02-14
Inactive: IPC assigned 2022-02-14
Filing Requirements Determined Compliant 2021-11-18
Letter sent 2021-11-18
Filing Requirements Determined Compliant 2021-11-18
Letter sent 2021-11-18
Priority Claim Requirements Determined Compliant 2021-11-18
Inactive: Inventor deleted 2021-11-17
Inactive: Inventor deleted 2021-11-17
Request for Priority Received 2021-11-16
Common Representative Appointed 2021-11-13
Inactive: Advanced examination (SO) 2021-10-12
Request for Examination Requirements Determined Compliant 2021-10-12
Amendment Received - Voluntary Amendment 2021-10-12
Inactive: Advanced examination (SO) fee processed 2021-10-12
All Requirements for Examination Determined Compliant 2021-10-12
Inactive: Reply received: Missing filing requirements 2021-10-12
Amendment Received - Voluntary Amendment 2021-10-12
Request for Examination Received 2021-10-12
Inactive: Reply received: Missing filing requirements 2021-09-20
Letter sent 2021-09-07
Common Representative Appointed 2021-08-12
Inactive: Pre-classification 2021-08-12
Application Received - Regular National 2021-08-12
Inactive: QC images - Scanning 2021-08-12

Abandonment History

There is no abandonment history.

Maintenance Fee

The last payment was received on 2023-12-15

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

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

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

Fee History

Fee Type Anniversary Year Due Date Paid Date
Application fee - standard 2021-09-20 2021-08-12
Advanced Examination 2021-10-12 2021-10-12
Request for examination - standard 2025-08-12 2021-10-12
MF (application, 2nd anniv.) - standard 02 2023-08-14 2023-06-15
Final fee - standard 2021-08-12 2023-11-27
MF (application, 3rd anniv.) - standard 03 2024-08-12 2023-12-15
Owners on Record

Note: Records showing the ownership history in alphabetical order.

Current Owners on Record
10353744 CANADA LTD.
Past Owners on Record
HAO JIANG
WEI CHENG
Past Owners that do not appear in the "Owners on Record" listing will appear in other documentation within the application.
Documents

To view selected files, please enter reCAPTCHA code :



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

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

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


Document
Description 
Date
(yyyy-mm-dd) 
Number of pages   Size of Image (KB) 
Claims 2023-10-10 10 530
Representative drawing 2023-12-18 1 19
Description 2021-10-11 14 846
Abstract 2021-10-11 1 26
Drawings 2021-10-11 3 149
Claims 2021-10-11 5 177
Description 2021-10-11 14 850
Claims 2021-10-11 9 335
Drawings 2021-10-11 3 149
Abstract 2021-10-11 1 26
Representative drawing 2022-02-14 1 13
Claims 2022-06-28 9 501
Claims 2022-11-30 10 533
Electronic Grant Certificate 2024-01-08 1 2,527
Commissioner's Notice - Outstanding Documents and Information 2021-09-06 1 446
Courtesy - Filing certificate 2021-11-17 1 565
Courtesy - Filing certificate 2021-11-17 1 565
Courtesy - Acknowledgement of Request for Examination 2022-02-14 1 424
Commissioner's Notice - Application Found Allowable 2022-12-21 1 579
Commissioner's Notice - Application Found Allowable 2023-10-26 1 578
Examiner requisition 2023-07-12 4 180
Amendment / response to report 2023-10-10 26 956
Courtesy - Office Letter 2023-10-25 1 157
Courtesy - Office Letter 2023-11-23 1 193
Final fee 2023-11-26 3 63
New application 2021-08-11 4 138
Missing filing requirements 2021-09-19 5 165
Request for examination / Advanced examination (SO) / Amendment / response to report 2021-10-11 37 1,747
Missing filing requirements 2021-10-11 37 1,739
Courtesy - Advanced Examination Request - Compliant (SO) 2022-02-14 1 163
Examiner requisition 2022-03-01 5 262
Amendment / response to report 2022-06-28 25 1,036
Examiner requisition 2022-07-31 6 287
Amendment / response to report 2022-11-30 29 1,151
Withdrawal from allowance 2023-01-26 1 52
Final fee 2023-02-01 3 63
Courtesy - Office Letter 2023-02-06 2 182