Language selection

Search

Patent 2690731 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 2690731
(54) English Title: METHOD, SYSTEM FOR CONTROLLING SERVICE ACCESS AND SERVER
(54) French Title: METHODE SERVEUR ET SYSTEME DE CONTROLE D'ACCES A DES SERVICES
Status: Granted
Bibliographic Data
(51) International Patent Classification (IPC):
  • A63F 13/30 (2014.01)
  • A63F 13/87 (2014.01)
  • H04L 12/16 (2006.01)
(72) Inventors :
  • YAN, MIN (China)
  • YANG, CAISHI (China)
  • HU, LIANG (China)
(73) Owners :
  • TENCENT TECHNOLOGY (SHENZHEN) COMPANY LIMITED (China)
(71) Applicants :
  • TENCENT TECHNOLOGY (SHENZHEN) COMPANY LIMITED (China)
(74) Agent: BORDEN LADNER GERVAIS LLP
(74) Associate agent:
(45) Issued: 2016-01-19
(86) PCT Filing Date: 2008-03-20
(87) Open to Public Inspection: 2008-12-18
Examination requested: 2009-12-14
Availability of licence: N/A
(25) Language of filing: English

Patent Cooperation Treaty (PCT): Yes
(86) PCT Filing Number: PCT/CN2008/070545
(87) International Publication Number: WO2008/151523
(85) National Entry: 2009-12-14

(30) Application Priority Data:
Application No. Country/Territory Date
200710111340.1 China 2007-06-15

Abstracts

English Abstract





A method for controlling service access is provided. the method includes:
creating a
service group comprising more than one client; searching, by a server, for a
service
component, wherein the number of users allowed to access the service component
is
larger than or equal to the number of the clients in the service group;
configuring the
service component as being accessible to only the clients in the service
group; and
informing the clients in the service group that the service component is
accessible; and
accessing, by the clients in the service group, the service component. A
server and a
system corresponding to the method are provided at the same time. By applying
the
method and system of the present invention, success ratio of the invitation is
improved
and the implementation procedure is simplified.


French Abstract

L'invention porte sur une méthode de contrôle d'accès à des services consistant: à créer un groupe de services incluant au moins deux clients; à faire rechercher par un serveur un module de service dont le nombre des utilisateurs accessibles est supérieur ou égal au nombre des clients du groupe de services; à rendre le module de services uniquement accessible aux clients du groupe de services; et à informer les clients du groupe de services qu'on peut accéder au module de service auquel ils accèdent. L'invention porte également sur un serveur et un système correspondant à la méthode. On améliore ainsi la probabilité de succès de l'invitationet le flux peut être simplifié en appliquant la méthode et le système de l'invention.

Claims

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


CLAIMS:
1. A
method for controlling service access, wherein an inviter client comprises an
inviter messenger client, an inviter game client and an inviter game client
plug-in; the inviter
game plug-in is configured to implement communications between the inviter
messenger
client, the inviter game client and a game server; an invitee client comprises
an invitee
messenger client, an invitee game client and an invitee game client plug-in;
the invitee game
client plug-in is configured to implement communications between the invitee
messenger
client, the invitee game client and the game server; the method comprising:
when desiring to send a game invitation to the invitee client, starting, by
the inviter
client, the inviter messenger client and the inviter game client plug-in;
sending, by the inviter messenger client, an invitation message generated by
the
inviter game client plug-in to the invitee game client plug-in;
after accepting the invitation, sending, by the invitee messenger client, a
response
message to the inviter game client plug-in; wherein the inviter client and the
invitee client
generates a service group;
receiving, by the inviter game client plug-in, the response message;
the inviter client and the invitee client starting the inviter game client and
the invitee
game client respectively, and waiting, by the inviter game client and the
invitee game client,
the game server to select a game position;
selecting, by the game server, the game position, and sending game position
information to the inviter game client and the invitee game client; wherein
the game position
is a game table, and the selecting the game position comprises: selecting, by
the game server
among all game tables, a game table with most seats currently available as the
game position;
after the game server selects the game position, the method further comprises:
configuring, by the game server, the game position as being accessible to only

the clients in the service group; and informing, by the game server, the
clients in the
service group that the game position is accessible; and
wherein configuring the game position as being accessible to only the clients
in
the service group comprises:
storing, by the game server, UIDs of all the clients in the service group;
14

writing, by the game server, the UIDs of all the clients in the service
group into an access control list; and
configuring, by the game server, an access control parameter of the
game position as access according to the UIDs in the access control list;
the method further comprises: after determining that UIDs of clients currently

access the game position comprises the UIDs of all the clients in the service
group, configuring, by the game server, the access control parameter of the
game position as accessible to all clients in the service group and accessible
to
clients not in the service group.
2. The method of claim 1, further comprising:
obtaining, by the inviter game client plug-in, a game list from the game
server;
the generating the invitation message comprises:
determining, by the inviter game client plug-in, game information according to

the game list, and generating, by the inviter game client plug-in, the
invitation
message in a fixed format according to the game information determined.
3. The method of claim 1, wherein the inviter client and the invitee client
starting the
inviter game client and the invitee game client respectively comprises any one
of:
starting the invitee game client when the invitee messenger client sends the
response
message to the inviter game client plug-in; and starting the inviter game
client after the inviter
game client plug-in receives the response message; and
starting the inviter game client before the inviter game client plug-in sends
the
invitation message; and starting the invitee game client when the invitee
messenger client
sends the response message.
4. The method of claim 1, further comprising:
after the inviter game client and the invitee game client join in the game
position,
starting, by the inviter game client and invitee game client, an inviter sub-
game end and an
invitee sub-game end to start a game.

5. A system for controlling service access, comprising: an inviter client,
an invitee client,
and a game server; wherein the inviter client and the invitee client are
coupled to the game
server;
the inviter client further comprises an inviter messenger client, an inviter
game client
and an inviter game client plug-in;
the invitee client further comprises an invitee messenger client, an invitee
game client
and an invitee game client plug-in;
the inviter game client plug-in is configured to (i) implement communications
between
the inviter messenger client, the inviter game client and the game server,
(ii) generate an
invitation message, (iii) send the invitation message to the invitee game
client plug-in, and (iv)
receive a response message sent by the invitee game client plug-in;
the invitee game client plug-in is configured to (i) implement communications
between the invitee messenger client, the invitee game client and the game
server, (ii) receive
the invitation message sent by the inviter game client plug-in, and (iii) send
the response
message after the invitation is accepted; wherein the inviter client and the
invitee client
generates a service group;
the game server is configured to select a game position, configure the game
position as
accessible to only the clients in the service group, and send game position
information to the
inviter game client and the invitee game client; wherein the game position is
a game table, the
game server is further configured to select, among all game tables, a game
table with most
seats currently available as the game position;
the inviter game client and the invitee game client are configured to join in
the game
position;
wherein the server is further adapted to allow all clients including the
clients in the
service group and clients not in the service group to access the game position
after
determining that User Identifiers (UIDs) of clients currently accessing the
game position
comprises UIDs of all the clients in the service group.
6. The system of claim 5, wherein the inviter game client is further
configured to obtain a
16

game list from the game server;
the inviter game client plug-in is further configured to determine game
information
according to the game list and generate the invitation message in a fixed
format according to
the game information.
7. The
system of claim 5, wherein the inviter game client and the invitee game client
are
further configured to respectively start, after the inviter game client and
the invitee game
client join in the game position, an inviter sub-game end and an invitee sub-
game end to start
a game.
17

Description

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


CA 02690731 2012-04-27
METHOD, SYSTEM FOR CONTROLLING SERVICE ACCESS AND
SERVER
FIELD OF THE INVENTION
[0001] The present invention relates to Instant Messaging (IM) technologies,
and more
particularly to a method, system for controlling service access and server.
BACKGROUND OF THE INVENTION
[0002] In current Internet applications, along with rapid development of
Instant
Messaging (IM), various applications and services based on the IM, such as
multi-player
online game, etc., are widely used. The multi-player online game refers that a
user sends
an invitation through his/her IM client to invite two or more users to
participant in the
same game to implement the multi-player online game.
[0003] In the prior art, there are relatively mature solutions to implement
the multi-player
online game. Take a scenario where two users participant in the same game as
an example,
an existing system for implementing the online game includes: an inviter
messenger client,
a Game Server, a messenger Server, an invitee messenger client, an inviter
game client and
an invitee game client, etc. Usually, a game client is also referred to as a
game hall. On the
Game Server, there are multiple threads or components to implement a game. The
threads
and components can be accessed by multiple users (clients) to implement the
function of
multi-player online game. This kind of thread is usually referred to as a game
table. The
accessing to the game thread or component of the clients is referred to as the
user joining
in the game table or occupying a game position. Further, for facilitating
management,
similar game threads or components in the same Game Server are divided into
multiple
groups, each group is called as a game room, and each game room may have
multiple
game tables. In some cases, a game thread or component may also be called as a
game
room.
[00041 In the prior art, the game position is selected by the inviter game
client and is
informed to the invitee game client by the system automatically. It is
unnecessary for the
invitee game client to acknowledge. As such, a problem arises: if a game
position, such as
1

CA 02690731 2012-04-27
seats to a game table, has been seized by other players before the invitee
joins, the invitee
cannot join in the same table but only joins the same room. In other words, in
the existing
game invitation procedure, after selecting the game table, the inviter game
client cannot
ensure that there is an available seat when the invitee game client joins. It
is quite possible
that all available seats of the game table corresponding to the inviter game
client have
been occupied by other players before the invitee game client joins, thus the
invitation
cannot be implemented.
[0005] Moreover, in the existing procedure, the game position is selected by
the inviter
game client. Then the messenger Server forwards information of all the game
tables such
as room and seat information. Finally, subsequent operations of the inviter
game client and
the invitee game client are invoked and initiated. In this way, the invitation
procedure is
relatively complicated.
[0006] In the prior art, the invitation request is generated through the
inviter messenger
client and the inviter game client will be started directly after the
invitation information is
acknowledged. In this way, the game invitation and response functions must be
integrated
in the messenger Client during development, which increases workload for
developing the
messenger Client and results in a bad extensibility.
SUMMARY OF THE INVENTION
[0007] Embodiments of the present invention provides a method, system for
controlling
service access and a server, so as to solve the problem that the service
invitation cannot be
really implemented in the prior art.
[0008] According to an embodiment of the present invention, a method for
controlling
service access is provided. The method includes: creating a service group
comprising more
than one client; searching, by a server, for a service component, wherein the
number of
users allowed to access the service component is larger than or equal to the
number of the
clients in the service group; configuring the service component as being
accessible to only
the clients in the service group; and informing the clients in the service
group that the
service component is accessible; and accessing, by the clients in the service
group, the
service component;
2

CA 02690731 2012-04-27
wherein configuring the service component as being accessible to only the
clients in
the service group comprises:
storing UIDs of all the clients in the service group;
writing the UIDs of all the clients in the service group into an access
control list; and
configuring an access control parameter of the service component as access
according
to the UIDs in the access control list;the method further comprises: after
determining that
UIDs of clients currently access the service component comprises the UIDs of
all the
clients in the service group, configuring, by the server, the access control
parameter of the
service component as accessible to all clients.
[0009] According to another embodiment of the present invention, a control
server for
controlling service access is provided. The control server includes: A server
for controlling
service access, including: a first unit, adapted to manage at least one
service component; a
second unit, adapted to search the first unit for a service component when a
service group
comprising more than one client has a service access requirement, wherein the
number of
users allowed to access the service component being searched for is larger
than or equal to
the number of clients in the service group; and a third unit, adapted to
configure the
service component searched out by the second unit as accessible to only the
clients in the
service group; wherein the third unit is further adapted to allow all the
clients to access the
service component after determining that User Identifiers (UIDs) of clients
currently
accessing the service component comprises UIDs of all the clients in the
service group.
[0010] According to another embodiment of the present invention, a system for
controlling service access is provided. The system includes: a server, adapted
to manage
service components, search for a service component wherein the number users
allowed to
access the service component is larger than or equal to the number of clients
in a service
group, configure the service component as accessible to only the clients in
the service
group, and inform the clients in the service group that the service component
is accessible;
and at least two clients in the service group, adapted to access the service
component
searched out by the server; wherein the server is further adapted to allow all
clients to
access the service component after determining that User Identifiers (UIDs) of
clients
currently accessing the service component comprises UIDs of all the clients in
the service
group.
3

CA 02690731 2012-04-27
=
[00111 In the present invention, the server selects a service component which
is able to
hold all members in a service group. Through restricting the service component
as being
accessible to only the clients in the service group, all the clients in the
service group can
access the service component and perform service operations, which increases
the success
ration of the invitation during creation of the service group and
implementation of the
service invitation.
BRIEF DESCRIPTION OF THE DRAWINGS
[0012] FIG 1 is a flowchart illustrating a procedure of implementing an
invitation
according to the prior art.
[0013] FIG 2 is a block diagram illustrating a structure of an online game
invitation
system according to an embodiment of the present invention.
[0014] FIG 3 is a flowchart illustrating a procedure of implementing an online
game
invitation according to a preferred embodiment of the present invention.
DETAILED DESCRIPTION OF THE INVENTION
[0015] An existing invitation procedure is as shown in FIG.1, which includes
the
following steps.
[0016] Step 101: an inviter messenger client triggers a game button on an IM
interface to
send a game invitation request to an invitee messenger client through a
messenger Server.
[0017] Step 102: after receiving the invitation sent from the inviter
messenger client, the
invitee messenger client prompts that an invitation is received and determines
whether to
accept the invitation. If the invitation is not accepted, the invitation
procedure is finished.
If the invitation is accepted, step 103 is performed.
[0018] Step 103: the invitee messenger client accepts the invitation and sends
a response
message to the inviter messenger client through the messenger Server.
[0019] Step 104: after receiving the response message, the inviter messenger
client
automatically starts an inviter game client.
[0020] Step 105: the inviter game client logs on a Game Server to authenticate
user
4

CA 02690731 2012-04-27
information.
[0021] Step 106: after the authentication is passed, the inviter game client
selects and joins
in a game position, wherein the game position, such as game room, game table,
etc. is
selected by the inviter game client itself.
[0022] Step 107: after selecting the game position, the inviter game client
sends game
information to the inviter messenger client. The game information includes but
is not
limited to: Game Server ID, Game room ID and relevant game data, etc.
[0023] Step 108: after receiving the game information, the inviter messenger
client sends
the game information to the invitee messenger client through the messenger
Server.
[0024] Step 109: the invitee messenger client receives the game information.
[0025] Step 110: the invitee messenger client automatically starts an invitee
game client
according to the game information received.
[0026] Step 111: the invitee game client logs on the Game Server to
authenticate user
information
[0027] Step 112: after the authentication is passed, the invitee game client
joins in the
game position selected by the inviter game client.
[0028] In the above procedure, the game position is selected by the inviter
game client and
is informed to the invitee game client by the system automatically. It is
unnecessary for the
invitee game client to acknowledge. As such, a problem arises: if a game
position, such as
a seat to a game table, has been seized by another player before the invitee
joins, the
invitee cannot join in the same table but only joins the same room. In other
words, in the
existing game invitation procedure, after selecting the game table, the
inviter game client
cannot ensure that there is an available seat when the invitee game client
joins. It is quite
possible that all available seats of the game table corresponding to the
inviter game client
have been occupied by other players before the invitee game client joins, thus
the
invitation cannot be implemented.
[0029] Moreover, in the existing procedure, the game position is selected by
the inviter
5

CA 02690731 2012-04-27
game client. Then the messenger Server forwards information of all game tables
such as
room and seat information. Finally, subsequent operations of the inviter game
client and
the invitee game client are invoked and initiated. In this way, the invitation
procedure is
relatively complicated.
[0030] In addition, in the procedure shown in FIG.1, the invitation request is
generated
through the inviter messenger client and the inviter game client will be
started directly
after the invitation information is acknowledged. In this way, the game
invitation and
response functions must be integrated in the messenger Client during
development, which
increases workload for developing the messenger Client and results in a bad
extensibility.
[0031] The core idea of the present invention relies in that, the Game Server
implements
the selection of a final game position for the game position of the inviter
game client and
the invitee game client; after the game position is determined, the inviter
and the invitee
are informed to join in the same game position and proceed with subsequent
procedure, so
as to guarantee the success rate of the invitation.
[0032] For facilitating the communications between the messenger clients and
the game
clients respectively, and between the messenger clients and the Game Server,
and for
extension of the messenger clients, a game client Plug-in may be respectively
configured
in the inviter and the invitee in the present invention. The game client Plug-
in is adapted to
generate messages, such as the invitation message and the response message. As
such, a
uniform management can be performed. Further, in the present invention, when
the inviter
messenger client initiates the invitation, online friend information and Game
Server
related information are obtained through an invitation interface of the game
client Plug-in
to generate relevant invitation information. Thus it is unnecessary to start
the inviter game
client, which is more convenient and efficient.
[0033] In the embodiments of the present invention, the inviter game client
may be started
immediately after the invitee messenger client receives the invitation message
and
determines to accept the invitation. In this way, better experience is
obtained, and
WYTIWYG (What You Think Is What You Get) is implemented.
[0034] As shown in FIG.2, the system for implementing online game invitation
according
to an embodiment of the present invention includes: an inviter 10, an invitee
20, a
6

CA 02690731 2012-04-27
messenger server 30 and a game server 40. The inviter 10 and the invitee 20
are both
connected with the messenger server 30 and the game server 40. The inviter 10
is a
collection of hardware and software used by a user initiating the invitation;
it may also be
called as inviter client 10. The invitee 20 is a collection of hardware and
software used by
a user being invited and may also be called as invitee client 20. The
messenger server 30 is
adapted to connect messenger clients of all users and implement functions such
as user
status query, friend list management, message forwarding, etc. The game server
40 is
adapted to connect game management clients of all users and implement
functions such as
game distribution, game rule configuration and implementation, user status
query, game
information forwarding, game account authentication and management, bill
recording,
advertisement pushing, etc. More importantly, the game server 40 is further
adapted to
implement selection of a game position, i.e. pair game players.
[0035] The inviter 10 further includes an inviter messenger client 11, an
inviter game
client 12, an inviter sub-game end 13 and an inviter game client Plug-in 14.
The inviter
messenger client 11 is adapted to receive and send information of the inviter
10. The
inviter game client 12 is adapted to implement function management of various
games of
the inviter 10, such as download, installation, configuration,
friend/blacklist, group
organization, communication, property purchase, advertisement. The inviter sub-
game end
13 is adapted to implement multi-player game of the inviter 10. The inviter
game client
Plug-in 14 is a program Plug-in compiled as required by an IM software
interface and is
adapted to generate messages, implement communications between the inviter
messenger
client 11, the inviter game client 12 and the game server 40, and is further
adapted to
implement interaction operations and content display of a user invitation
interface of the
inviter 10. Information contents generated and forwarded by the inviter game
client
Plug-in includes but is not limited to: user account, user password, game
server
information, friend information, game position information of the user, game
content
information of the user, game position information of a friend, and game
content
information of the friend.
[0036] The invitee 20 further includes an invitee messenger client 21, an
invitee game
client 22, an invitee sub-game end 23 and an invitee game client Plug-in 24.
The invitee
messenger client 21 is adapted to receive and send information of the invitee
20. The
7

CA 02690731 2012-04-27
invitee game client 22 is adapted to implement function management of various
games of
the invitee 20, such as download, installation, configuration,
friend/blacklist, group
organization, communication, property purchase, advertisement, etc. The
invitee sub-game
end 23 is adapted to implement multi-player game of the invitee 20. The
invitee game
client Plug-in 24 is a program Plug-in compiled as required by the IM software
interface,
and is adapted to generate messages, implement communications between the
invitee
messenger client 21, the invitee game client 22 and the game server 40, and is
further
adapted to implement interaction operations and content display of a user
invitation
interface of the invitee 20. Information contents generated and forwarded by
the invitee
game client Plug-in includes but is not limited to: user account, user
password, game
server information, friend information, game position information of the user,
game
content information of the user, game position information of a friend and
game content
information of the friend.
[0037] In the system as shown in FIG.2, the inviter game client Plug-in 14 and
the invitee
game client Plug-in 24 are optional. If the inviter game client Plug-in and
the invitee game
client Plug-in are not configured in the inviter or the invitee, the
generation and the
reception of the invitation message and the response message, the interaction
operations
and the contents display of the user invitation interface can be implemented
by the inviter
messenger client and the invitee messenger client respectively.
[0038] Based on the system shown in FIG2, a method for implementing an online
game
invitation in accordance with a preferred embodiment of the present invention
is shown in
FIG.3, which includes the following steps.
[0039] Step 301: when desiring to send a game invitation to the invitee 20,
the inviter 10
firstly starts the inviter messenger client 11 and starts the inviter game
client Plug-in 14
embedded in the inviter messenger client 11 to generate an invitation
interface.
[0040] Step 302: the inviter game client Plug-in 14 obtains a game list
directly from the
game server 40 and presents the game list to the inviter 10.
[0041] Step 303: the inviter messenger client 11 obtains an online status of
the invitee 20
through the messenger server 30. If the invitee 20 is online, the inviter 10
generates an
invitation message through the inviter game client Plug-in 14 to initiate a
game invitation
8

CA 02690731 2012-04-27
and create a service group.
[0042] The step of generating the invitation message includes: the inviter
game client
Plug-in 14 selects and determines game information such as game type and game
room etc.
according to a game list obtained, and generates the invitation message in a
fixed format
according to the game information.
[0043] Step 304: the inviter messenger client 11 sends the generated
invitation message to
the invitee game client Plug-in 24 through the messenger server 30. The
invitation
message includes but is not limited to: inviter identity (UID), game
information, game area
information, game room information and network environment information, etc.
[0044] Step 305: after receiving the invitation message of the inviter
messenger client 11,
the invitee game client Plug-in 24 prompts that an invitation is received and
determines
whether to accept the invitation. If the invitation is not accepted, the
invitation procedure
will be finished directly; if the invitation is accepted, step 306 is
performed, and the
invitee game client Plug-in 24 joins in the service group.
[0045] Before step 305, the invitee 20 may firstly start the invitee messenger
client 21 and
the invitee game client Plug-in 24 embedded in the invitee messenger client
21, so that the
invitee game client Plug-in 24 is in a working state.
[0046] Step 306: the invitee messenger client 21 accepts the invitation, sends
a response
message to the inviter game client Plug-in 14 through the messenger server 30
to indicate
that the invitation is accepted, and starts the invitee game client 22. In
this way, the inviter
10 and the invitee 20 generates a service group for performing game services.
The service
group includes more than one client. Afterwards, the inviter 10 and the
invitee 20
respectively perform steps 307a-307d and steps 308a-308b.
[0047] Steps 307a-307b: the inviter game client Plug-in 14 receives the
response message
and starts the inviter game client 12. The inviter game client 12 logs on the
game server 40
to authenticate user information. The information used in the authentication
includes
invitation-related information, such as an ID assigned for the invitation and
a LAD which
accepts the invitation. After the authentication is passed, join in a
determined game area or
room according to the game room selected in step 303, and wait the game server
to
9

CA 02690731 2012-04-27
determine a final game position.
[0048] Steps 308a-308b: the invitee game client 22 logs on the game server 40
to
authenticate user information. The information used in the authentication
includes
invitation-related information, such as an ID assigned for the invitation and
a UID which
initiating the invitation. After the authentication is passed, the invitee
game client 22 joins
in the game area or room designed by the inviter 10 according to the
invitation message,
and waits the game server to determine the final game position.
[0049] In the above steps 307a-307d and 308a-308b, if the inviter game client
12 has
already logged on the game server before sending the invitation message, the
invitation-related information such as the ID assigned for the invitation and
the UID which
accepts the invitation may be sent to the game server by the inviter game
client Plug-in 14.
If the inviter 10 is not equipped with the inviter game client Plug-in 14, the

invitation-related information may be sent to the game server by the inviter
messenger
client 11.
[0050] Step 309: the game server 40 stores the invitation-related information
such as the
ID assigned for the invitation, the UID which initiates the invitation and the
UID which
accepts the invitation, etc., and determines the final game position according
to an
available seat preferable principle. The game server 40 automatically sends
pair
information, i.e. the selected final game position, to the inviter game client
12 and the
invitee game client 22.
[0051] The available seat preferable principle means that: when selecting
seats, the game
server 40 most preferably selects a game table with all seats currently
available for the
inviter game client and the invitee game client to join in; less preferably,
select the game
table with one seat occupied. And then, select the game table with two seats
occupied. In
the same way, until select the game table with only two seats available. As
such, the
success of the invitation may be ensured. Certainly, if multiple users are
invited, the game
table with multiple available seats may be selected according to the available
seat
preferable principle to guarantee the success of the invitation. In the
embodiments of the
present invention, the final game position is obtained by a following manner:
according to
the available seat preferable principle, the game server searches for a game
thread or

CA 02690731 2012-04-27
component which allows a number of users to access, wherein the number is
larger than or
equal to the number of users in the invitation. If such game thread or the
component is
found, the game thread or component is taken as a target game table, i.e. the
final game
position.
[0052] Step 310: the game server 40 sends the determined final game position
to the
inviter game client 12 and the invitee game client 22. After receiving the
final game
position, the inviter game client 12 and the invitee game client 22
respectively join in the
determined game position.
[0053] After determining the final game position, the game server 40 may
temporarily
lock the game position to prevent the position from being occupied by other
users before
the inviter and the invitee join. Specifically, it is possible to configure an
access control
parameter of the game position, i.e. the game thread or the component, as
access according
to an Access Control List, i.e. according to the UIDs in a white list. When
determining that
all the clients corresponding to the UIDs in the white list have accessed the
game thread or
the component, the game server 10 configures the access control parameter as
accessible
to all clients. The white list is a table in an access attribute of the game
thread or
component. Only the client whose UID is in the white list is allowed to access
the game
thread or component.
[0054] Step 311: the inviter sub-game end 13 and the invitee sub-game end 23
are
respectively started to play the game.
[0055] In the procedure shown in FIG.3, if the inviter game client Plug-in and
the invitee
game client Plug-in are not configured in the inviter and the invitee, the
generation and
reception of the invitation message and response message, the interaction
operations and
content display of the user invitation interface may be implemented by the
inviter
messenger client and the invitee messenger client respectively.
[0056] In practical applications, the inviter game client Plug-in may start
the inviter game
client before sending the invitation message or before generating the
invitation message.
The inviter game client logs on the game server to authenticate the user
information. After
the authentication, the inviter game Plug-in sends the invitation message to
the invitee
through the messenger server, or generates the invitation message and sends
the generated
11

CA 02690731 2012-04-27
invitation message to the invitee through the messenger server. In this case,
after receiving
the response message returned by the invitee, the inviter game client Plug-in
informs the
inviter game client to join in the game room selected in advance and to join
in the final
game position after the game server determines the final game position.
[0057] The present invention has the following advantages and characteristics:
1) in the present invention, the game server implements the final game pair
and
determines the final game position, which increases the success ratio of the
invitation;
2) in the present invention, the inviter game client Plug-in and the
invitee game
client Plug-in are configured in the inviter and the invitee to integrate the
information forwarding between the messenger clients and their respective
game clients and between the messenger clients and the game server,
generate the invitation message and response message, etc., so as to
facilitate
management of communication information. Further, the usage of the
Plug-ins meets the extension requirements of the messenger clients.
3) in the present invention, related information in the game server, such
as the
game list, may be directly obtained by the inviter game client Plug-in without

opening the inviter game client, which improves response sensitivity for user
operates; further, the inviter may implement further selection according to
the
related information obtained, which is flexible and convenient.
4) in the present invention, after the invitee accepts the invitation the
invitee
game client rather than that of the inviter may be started first, which
provides
the user with better experience and is simple and more efficient.
[0058] In view of the above, the present invention optimizes the whole
invitation
procedure and automatically generates complete invitation data according to
the inviter's
will by the client program or background server. Meanwhile, the present
invention ensures
that the invitation procedure is not affected by actions of other external
users, which not
only increases the success ratio of the invitation but also brings better
experience for the
user.
12

CA 02690731 2012-04-27
[0059] The foregoing are only preferred embodiments of the present invention
and are not
for use for limiting the protection scope of the present invention.
13

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

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 , Administrative Status , Maintenance Fee  and Payment History  should be consulted.

Administrative Status

Title Date
Forecasted Issue Date 2016-01-19
(86) PCT Filing Date 2008-03-20
(87) PCT Publication Date 2008-12-18
(85) National Entry 2009-12-14
Examination Requested 2009-12-14
(45) Issued 2016-01-19

Abandonment History

There is no abandonment history.

Maintenance Fee

Last Payment of $473.65 was received on 2023-12-07


 Upcoming maintenance fee amounts

Description Date Amount
Next Payment if small entity fee 2025-03-20 $253.00
Next Payment if standard fee 2025-03-20 $624.00

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.

Payment History

Fee Type Anniversary Year Due Date Amount Paid Paid Date
Request for Examination $800.00 2009-12-14
Application Fee $400.00 2009-12-14
Maintenance Fee - Application - New Act 2 2010-03-22 $100.00 2010-02-24
Maintenance Fee - Application - New Act 3 2011-03-21 $100.00 2011-02-14
Maintenance Fee - Application - New Act 4 2012-03-20 $100.00 2012-02-21
Maintenance Fee - Application - New Act 5 2013-03-20 $200.00 2013-02-19
Maintenance Fee - Application - New Act 6 2014-03-20 $200.00 2014-02-12
Maintenance Fee - Application - New Act 7 2015-03-20 $200.00 2015-02-12
Final Fee $300.00 2015-11-10
Maintenance Fee - Patent - New Act 8 2016-03-21 $200.00 2016-03-09
Maintenance Fee - Patent - New Act 9 2017-03-20 $200.00 2017-02-22
Maintenance Fee - Patent - New Act 10 2018-03-20 $250.00 2018-03-01
Maintenance Fee - Patent - New Act 11 2019-03-20 $250.00 2019-02-27
Maintenance Fee - Patent - New Act 12 2020-03-20 $250.00 2020-02-26
Maintenance Fee - Patent - New Act 13 2021-03-22 $250.00 2020-12-22
Maintenance Fee - Patent - New Act 14 2022-03-21 $254.49 2022-01-27
Maintenance Fee - Patent - New Act 15 2023-03-20 $458.08 2022-12-14
Maintenance Fee - Patent - New Act 16 2024-03-20 $473.65 2023-12-07
Owners on Record

Note: Records showing the ownership history in alphabetical order.

Current Owners on Record
TENCENT TECHNOLOGY (SHENZHEN) COMPANY LIMITED
Past Owners on Record
HU, LIANG
YAN, MIN
YANG, CAISHI
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 2009-12-15 3 111
Description 2009-12-15 12 531
Representative Drawing 2010-02-23 1 17
Abstract 2009-12-14 1 17
Claims 2009-12-14 3 98
Drawings 2009-12-14 3 58
Description 2009-12-14 12 528
Cover Page 2010-02-26 2 56
Claims 2012-04-27 3 116
Description 2012-04-27 13 640
Claims 2013-08-09 3 124
Description 2014-03-03 4 159
Claims 2015-06-29 4 157
Representative Drawing 2015-12-29 1 15
Cover Page 2015-12-29 1 51
PCT 2009-12-14 6 198
Assignment 2009-12-14 6 155
Prosecution-Amendment 2009-12-14 5 197
Prosecution-Amendment 2011-11-07 5 234
Correspondence 2012-01-06 3 87
Assignment 2009-12-14 8 209
Prosecution-Amendment 2014-11-27 4 262
Prosecution-Amendment 2012-04-27 22 1,091
Prosecution-Amendment 2013-05-16 4 188
Prosecution-Amendment 2013-08-09 9 427
Prosecution-Amendment 2014-01-29 3 105
Prosecution-Amendment 2014-03-03 15 730
Prosecution-Amendment 2014-06-02 3 134
Prosecution-Amendment 2015-02-17 4 276
Amendment 2015-06-29 12 580
Final Fee 2015-11-10 1 36