Method, system for controlling service access and server
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.
Claims
exact text as granted — not AI-modified1 . A method for controlling service access, comprising:
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 . The method of claim 1 , wherein the creating the service group comprising more than one client comprises:
sending, by a first client, a service invitation to at least one second client to create the service group; and responding, by the at least one second client, the service invitation and joining in the service group.
3 . The method of claim 2 , wherein the searching for the service component comprises:
obtaining, by the server, the number of the clients in the service group; and searching, by the server, for the service component according to an available seat preferable principle.
4 . The method of claim 3 , wherein the obtaining the number of the clients in the service group comprises:
obtaining, by the server, the number of the clients in the service group when the clients log on the server.
5 . The method of claim 3 , wherein the clients are messenger clients, and the obtaining the number of the clients in the service group comprises:
if the clients have logged on the server before the service group is created, sending, by an inviter messenger client, User Identifiers (UIDs) of the clients in the service group to the server; and obtaining, by the server, the number of the clients in the service group according to the UIDs.
6 . The method of claim 3 , wherein the clients are messenger clients and each messenger client comprises a service function Plug-in, the obtaining the number of the clients in the service group comprises:
if the clients have logged on the server before the service group is created, sending, by the service function Plug-in of an inviter, UIDs of the clients in the service group to the server; and obtaining, by the server, the number of the clients in the service group according to the UIDs.
7 . The method of claim 1 , 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.
8 . The method of claim 7 , further comprising:
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.
9 . A server for controlling service access, comprising:
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.
10 . The server of claim 9 , further comprising:
a fourth unit, adapted to inform the clients in the service group that the service component searched out by the second unit is accessible.
11 . The server of claim 9 , 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 access the service component comprises UIDs of all the clients in the service group.
12 . A system for controlling service access, comprising:
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.
13 . The system of claim 12 , wherein the server is further adapted to allow all clients to access the service component after determining that User Identifiers (UIDs) of clients currently access the service component comprises UIDs of all the clients in the service group.
14 . The system of claim 12 , wherein each of the clients is further adapted to send a service invitation to create the service group or adapted to respond to a service invitation sent by another client to join in the service group.Join the waitlist — get patent alerts
Track US2010093443A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.