Patent Grant
10389726
This application is a national phase application of International Application No. PCT/CN2015/086613, filed on Aug. 11, 2015, which claims priority to and benefits of Chinese Patent Application No. 201410416166.1, filed on Aug. 21, 2014. The contents of the above-referenced applications are incorporated herein by reference in their entirety.
The present application relates to the field of communication technologies, and in particular, to a service processing method, apparatus and server.
With the development of smart terminals and the popularity of network applications, a user can implement various service operations, such as social instant messaging services and shopping payment services, using various application clients installed on a terminal. To implement the above services, a terminal user usually needs to register a service account on a server, and implement certain service operations based on the service account.
However, in the prior art, the terminal user can only accomplish various service operations based on his/her own account. Therefore, the way of implementing services is relatively simple, and the interactive efficiency of service information is low.
The present application provides a service processing method, apparatus and server, to solve the problems in the prior art that the way of implementing services is relatively simple and the interactive efficiency of service information is low.
According to a first aspect of embodiments of the present application, a service processing method applied to a service processing server is provided, the method including:
when a first user logs on a client device based on a first account, receiving an operation request for requesting a service operation from the first user;
according to the first account, searching account binding relationship which has been stored;
if a second account of a second user bound with the first account is found, permitting the first user to accomplish the service operation by the second account authority of the second account; and
after the first user accomplishes the service operation by the second account authority, updating the second account information of the second account according to the operation result of the service operation.
According to a second aspect of the embodiments of the present application, a service processing apparatus applied to a service processing server is provided, the apparatus including:
a receiving unit, configured to, when a first user logs on a client device based on a first account, receive an operation request for requesting a service operation from the first user;
a searching unit, configured to, according to the first account, search account binding relationship which has been stored;
a control unit, configured to, if a second account of a second user bound with the first account is found, permit the first user to accomplish the service operation by the second account authority of the second account; and
an update unit, configured to, after the first user accomplishes the service operation by the second account authority, update the second account information of the second account according to the operation result of the service operation.
According to a third aspect of the embodiments of the present application, a server is provided, including:
a processor; and a memory configured to store executable instructions of the processor;
wherein the processor is configured to:
when a first user logs on a client device based on a first account, receive an operation request for requesting a service operation from the first user;
according to the first account, search account binding relationship which has been stored;
if a second account of a second user bound with the first account is found, permit the first user to accomplish the service operation by the second account authority of the second account; and
after the first user accomplishes the service operation by the second account authority, update the second account information of the second account according to the operation result of the service operation.
By use of the technical solutions provided in the embodiments of the present application, when a first user logs based on a first account, an application server, if finding a binding relationship between the first account and a second account in an account binding relationship, permits the first user to accomplish service operation using the second account authority of a second user, and directly updates second account information of the second account after the service operation is accomplished. By use of the embodiments of the present application, the second user can authorize the first user having an intimate relationship with the second user to use the second account authority of the second user, such that the first user can accomplish various service operations on the basis of the account authorities of multiple bound accounts, thus expanding the way of implementing services. Moreover, as the second account information is directly updated after a service operation is accomplished, the times of transmission of service data among different accounts can be reduced, thus improving the interactive efficiency of service information.
It should be understood that the general description above and the detailed description hereinafter are merely exemplary and explanatory, but cannot limit the present application.
The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments in line with the present application, and are used for explaining the principle of the present application together with the specification.
Exemplary embodiments will be described in detail here, which are illustrated in the accompanying drawings. When the accompanying drawings are involved in the following description, unless otherwise indicated, the same numbers in different accompanying drawings represent the same or similar elements. Implementations described in the following exemplary embodiments do not represent all the implementations consistent with the present application. On the contrary, they are merely examples of apparatuses and methods consistent with some aspects of the present application as detailed in the appended claims.
The terms used in the present application are merely for the purpose of describing specific embodiments, instead of being aimed to limit the present application. The singular forms “one”, “said” and “the” used in the present application and the appended claims are also intended to include plural forms, unless other meanings are clearly indicated in the context. It should also be understood that the term “and/or” used herein refers to and includes any or all possible combinations of one or more associated listed items.
It should be understood that, although the present application may use the terms such as first, second and third to describe various kinds of information, the information should not be limited to the terms. The terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the present application, first information may also be referred to as second information, and similarly, the second information may also be referred to as the first information. Depending upon the context, the word “if” as used herein may be explained as “while . . . ” or “when . . . ” or “in response to determining”.
Referring to
A user illustrated in
In the embodiment of the present application, it is possible to, based on an intimate relationship between users, expand the way of implementing services and improve the interactive efficiency of service information. As shown in
Referring to
Step 201: When a first user logs on a client device based on a first account, receive an operation request for requesting a service operation from the first user.
In the embodiment of the present application, after registering a first account on a server, the first user can log on the server based on the first account, to accomplish various service operations. The first account is information according to which the server can uniquely identify the first user, including a user name of the first user, for example, the first account is user1@ABC.com, and the second account is “user2@ABC.com”; the service operations mainly refer to various application functions provided by the server for the user, for example, a payment function provided by a third party payment server for the user to accomplish a payment operation on an online shopping item, or a download function provided by an instant messaging server for the user to accomplish a download operation on a multimedia file in a network storage space, and so on.
Step 202: According to the first account, search account binding relationship which has been stored.
In the embodiment of the present application, based on an intimate relationship between users, a binding relationship between several different accounts is pre-stored in a list of account binding relationships of the server. When the first user sends a service operation request to the server, the server can search the list of account binding relationships according to the first account to determine whether there is another account bound with the first account, in order that the first user can accomplish the service operation by using the account authority of the another account.
Step 203: If a second account of a second user bound with the first account is found, permit the first user to accomplish the service operation using the second account authority of the second account.
In the embodiment of the present application, when the server finds a second account bound with the first account in the list of account binding relationships, a list of optional accounts can be output on a current service operation interface of the first user. The list of optional accounts, in addition to including the first account, may also include the second account bound with the first account. If the first user selects the second account from the list of optional accounts to accomplish the service operation and inputs a service password, the server, when verifying that the input service password is consistent with a first service password in the case that the first user registers the first account, releases the first user to accomplish the service operation by using the second authority of the second account.
Step 204: After the first user accomplishes the service operation using the second account authority, update the second account information of the second account according to the operation result of the service operation.
In the embodiment of the present application, as the first user accomplishes the service operation using the second account authority, after the service operation is accomplished, account information of the first account may not change, and the server can directly update the second account information of the second account according to the operation result of the service operation. For example, after the first user accomplishes a certain payment operation by using a payment account of the second account, the server updates the account balance in the payment account. For another example, after the first user downloads a multimedia file from a storage space of the second account by using the account authority of the second account, the server updates a download record of the multimedia file in the storage space of the second account.
In addition, while being compatible with possible service scenarios of various service operations, in order to further improve the security of the service operations and ensure that user information of bound accounts during the service operations may not be stolen by a malicious third party, in the above embodiment, a correspondence relationship between different service scenarios and security attributes of the service operations may be preset, after the server finds the second account of the second user bound with the first account, it is possible to first determine a security attribute of a service scenario corresponding to a current service operation, when the security attribute is secure, the first user can be permitted to accomplish the service operation using the second account authority, and when the security attribute is insecure, the first user can be prohibited from accomplishing the service operation using the second account authority. At this point, the first user can only accomplish the service operation using the first account authority. For example, for a payment operation, when the service scenario thereof is domestic commodity trading, the corresponding security attribute is secure, and when the service scenario thereof is overseas purchasing trading, the corresponding security attribute is insecure.
It is thus clear from the above embodiment that the second user can authorize the first user having an intimate relationship with the second user to use the second account authority of the second user, such that the first user can accomplish various service operations on the basis of the account authorities of multiple bound accounts, thus expanding the way of implementing services. Moreover, as the second account information is directly updated after a service operation is accomplished, the times of transmission of service data among different accounts can be reduced, thus improving the interactive efficiency of service information.
Referring to
Step 301: A server sends a list of recommended accounts to a second user, the list of recommended accounts including at least one account of a user whose intimate relationship with the second user has a value exceeding a preset relationship threshold.
In the embodiment of the present application, for each registered user, the server can provide a list of recommended accounts for the user according to intimate relationships between the user and other users, the list of recommended accounts including several accounts that can be authorized to be bound with the user's account.
The server can calculate values of the intimate relationships between the user and other users based on various relationship indexes between the user and other users according to a preset algorithm, and for a user whose intimate relationship with the user has a value greater than a preset relationship threshold, his/her account is added to the list of recommended accounts. For example, if a list of friends of the second user includes several users, the server can calculate values of intimate relationships between the second user and different users according to instant messaging time, the number of instant messaging messages and so on between the second user and different users in the list of friends.
Step 302: The second user sends an authorization message to the server, the authorization message including a first account selected from the list of recommended accounts by the second user, and a set using condition of the second account authority.
After receiving the list of recommended accounts sent by the server, the second user can select one or more accounts authorized to be bound from the list of recommended accounts. In the embodiment of the present application, it is assumed that the second user selects the first account from the list of recommended accounts. As shown in
Further, after selecting the first account authorized to be bound, the second user can set a using condition under which the first account can use the second account authority, for example, for a payment service operation, the using condition of the second account authority may be the upper limit of the amount of the payment operation accomplished using the second account authority; for another example, for an instant messaging service operation, the using condition of the second account authority may be download time, the number of downloads and so on for downloading a multimedia file using the second account authority.
The second user, after selecting the first account and further setting the using condition of the second account authority, can carry the above information in the authorization message to be sent to the server. It should be noted that the second user may not select an account authorized to be bound based on the list of recommended accounts, but directly send an account that he/she wants to authorize to be bound and a using condition of the account authority of the account to the server by an authorization message, which is not limited in the embodiment of the present application.
Step 303: The server stores a binding relationship between the first account and the second account in the account binding relationship according to the authorization message.
In the embodiment of the present application, the server obtains the first account from the received authorization message, and stores a binding relationship between the first account and the second account in the account binding relationship. When the authorization message further carries a using condition, the server can further store the using condition in the above binding relationship.
When the server stores the binding relationship, the following two manners may be employed:
The first manner is as follows: the server can maintain a list of account binding relationships, and each entry in the list is used for storing a binding relationship between accounts, as shown in Table 1 below:
The second manner is as follows: the server can maintain a list of account binding relationships separately for each account, each entry of the list is used for storing a binding relationship between one bound account and another authorized account, and Table 2 below illustrates a list of account binding relationships maintained for the first user user1:
Step 304: After a first user logs on a client device based on the first account, the first user sends an operation request for requesting a service operation to the server.
Step 305: The server searches an account binding relationship according to the first account of the first user.
In the embodiment of the present application, the server can query the list of account binding relationships as described in step 303, and in combination with the above Table 1, the server can search a “bound account” field according to the first account “user1@ABC.com”, to obtain a second account “user2@ABC.com” included in the “authorized account” corresponding to “user1@ABC.com”; alternatively, in combination with the above Table 2, the server can find a list of account binding relationships maintained for user1 according to the first account “user1@ABC.com”, to directly obtain all authorized accounts of the first account user1@ABC.com from the list, including the second account user2@ABC.com.
Step 306: The server, when finding a second account bound with the first account, permits the first user, under the using condition of the second account, to accomplish the service operation using the second account authority of the second account.
When the server finds a second account bound with the first account in the list of account binding relationships, a list of optional accounts can be output on a current service operation interface of the first user. The list of optional accounts, in addition to including the first account, may also include the second account bound with the first account.
If the first user selects the second account from the list of optional accounts to accomplish the service operation and inputs a service password, the server, when verifying that the input service password is consistent with a first service password in the case that the first user registers the first account, releases the first user to accomplish the service operation by using the second authority of the second account. As shown in
It should be noted that the first user, in addition to selecting the second account to accomplish the service operation, can also select multiple other accounts from the list of optional accounts to accomplish the service operation at the same time, and the multiple accounts may also include the first account of the first user, which is not limited in the embodiment of the present application. For example, when performing a payment operation, the first user may accomplish the payment operation jointly using the money in a payment account under the first account and the money in a payment account under the second account.
Step 307: After the first user accomplishes the service operation using the second account authority, the server updates second account information of the second account according to the operation result of the service operation.
In the embodiment of the present application, as the first user accomplishes the service operation using the second account authority, after the service operation is accomplished, account information of the first account may not change, and the server can directly update the second account information of the second account according to the operation result of the service operation.
Step 308: The second user sends an authorization release message to the server, the authorization release message including the first account.
It can be known in combination with step 302 that the second user, by sending an authorization message to the server, authorizes the first user to use the second account authority of the second account. Similarly, in this step, the second user may also, by sending an authorization release message to the server, prohibit the first user from using the second account authority of the second account. The authorization release message carries the first account of the first user from which the binding is to be released.
Step 309: The server deletes the binding relationship between the first account and the second account from the account binding relationships according to the authorization release message.
After receiving the authorization release message from the second user, the server can query the list of account binding relationships as described in step 303. In combination with the above Table 1, the server can search the second account “user2@ABC.com” under the authorized account, and when finding “user2@ABC.com” and the authorized account corresponding thereto being the first account “user1@ABC.com”, delete the binding relationship between the first account and the second account from Table 1. In combination with the above Table 2, the server can find a list 2 of account binding relationships maintained for user1 according to the first account “user1@ABC.com”, and after finding the second account “user2@ABC.com” from the list 2, delete the second account “user2@ABC.com” from the list 2.
It can be seen from the above embodiment that the second user can authorize the first user having an intimate relationship with the second user to use the second account authority of the second user, such that the first user can accomplish various service operations on the basis of the account authorities of the multiple bound accounts, thus expanding the way of implementing services. As the second account information is directly updated after a service operation is accomplished, the times of transmission of service data among different accounts can be reduced, thus improving the interactive efficiency of service information. Moreover, the user can flexibly authorize or release authorizing another user to use the account authority of the user to accomplish the service operation according to requirements, thus ensuring the security of the authorized account while expanding the way of implementing services.
Referring to
Step 401: A first user registers a first account to a server.
Step 402: The server stores a correspondence relationship between the first account and a first service password in a user account.
When a user wants to use various services provided by the server, he/she first needs to register on the server. At this point, the server presents a registration interface to the user, and the user inputs an account name and a service password. It should be noted that the service password in the embodiment of the present application can be consistent with the login password of the user, and can also be a service password dedicated to accomplishing a service operation set independent of the login password, which is not limited in the embodiment of the present application. As the embodiment of the present application focuses on describing the service operation process, merely the service password related to the service operation is described, and the login password may be set together in the registration interface, which is not elaborated in the embodiment of the present application.
In the embodiment of the present application, the server can store, in a list of user accounts, a correspondence relationship between accounts and service passwords when users register, and account information of each account, and the Table 3 below illustrates a list of user accounts including registration information of the first user and the second user:
Step 403: When the first user logs on a client device based on the first account, the first user sends an operation request for requesting a service operation to the server.
Step 404: The server, according to the first account, searches account binding relationship which has been stored.
Step 405: The server, when finding a second account bound with the first account, outputs the second account as an optional account on a service operation interface of the first user.
The server, when finding a second account bound with the first account in the list of account binding relationships, can output a list of optional accounts on a current service operation interface of the first user. The list of optional accounts, in addition to including the first account, may also include other accounts bound with the first account, for example, the second account in this embodiment.
Step 406: The first user, after selecting the second account to accomplish the service operation, sends an input service password to the server.
Step 407: The server, when verifying that the input service password is consistent with the first service password stored in the account information, releases the first user to accomplish the service operation using the second account authority.
In this step, the first user, when selecting the second account to accomplish the service operation, can still use the service password when the first user registers, the server finds the account information of the first user from Table 3, and acquires therefrom that the service password of the first account “user1@ABC.com” is “user1abcde”, and if the service password input by the first user is the same as “user1abcde”, the server releases the second account authority to accomplish the service operation of the first account.
Step 408: After the first user accomplishes the service operation using the second account authority, the server updates second account information of the second account according to the operation result of the service operation.
In the embodiment of the present application, as the first user accomplishes the service operation using the second account authority, after the service operation is accomplished, account information of the first account may not change, and the server can directly update the second account information of the second account according to the operation result of the service operation.
Step 409: The server sends a notification message to the second user, to notify the second user of updated contents of the second account information.
In the embodiment of the present application, the notification message sent by the server to the second user may be a short message sent to a terminal device on which the user registers, or an instant messaging message sent to the second account.
Step 410: The first user sends a reverse operation request for the service operation to the server.
Step 411: After the reverse operation of the service operation is accomplished, the server updates the second account information according to the operation result of the reverse operation.
Suppose that, after the first user accomplishes a payment operation of purchasing a commodity using a payment account of the second account by a third party payment server in step 408, if the commodity has a quality problem, the first user conducts handling of return goods on the commodity, at this point, the first user sends a refunding request to the third party payment server, and the third party payment server directly returns the deducted fund of the commodity to the payment account of the second account, and after the refunding ends, directly updates account balance information in the payment account.
It can be seen from the above embodiment that the second user can authorize the first user having an intimate relationship with the second user to use the second account authority of the second user, such that the first user can accomplish various service operations on the basis of the account authorities of multiple bound accounts, thus expanding the way of implementing services. Moreover, as the second account information is directly updated after the service operation and the reverse service operation are accomplished, the times of transmission of service data among different accounts can be reduced, thus improving the interactive efficiency of service information.
Corresponding to the embodiment of the service processing method described above, the present application further provides an embodiment of a service processing apparatus.
The embodiment of the service processing apparatus of the present application can be applied to a server. The apparatus embodiment may be implemented by software, or may be implemented by hardware or a combination of software and hardware. For the implementation by software, as a logical apparatus, it is formed by reading a corresponding computer program instruction in a non-volatile memory into the memory by a processor of a server where the apparatus is located and running the computer program instruction. In terms of the hardware level, as shown in
Referring to
The receiving unit 610 is configured to, when a first user logs on a client device based on a first account, receive an operation request for requesting a service operation from the first user;
The searching unit 620 is configured to, according to the first account, search account binding relationship which has been stored;
The control unit 630 is configured to, if a second account of a second user bound with the first account is found, permit the first user to accomplish the service operation using the second account authority of the second account;
The update unit 640 is configured to, after the first user accomplishes the service operation using the second account authority, update the second account information of the second account according to the operation result of the service operation.
Referring to
The sending unit 710 is configured to send a list of recommended accounts to a second user, the list of recommended accounts including at least one account of a user whose intimate relationship with the second user has a value exceeding a preset relationship threshold;
The receiving unit 720 is configured to receive an authorization message of the second user, the authorization message including a first account selected from the list of recommended accounts by the second user;
The first storage unit 730 is configured to store a binding relationship between the first account and the second account of the second user in the account binding relationship according to the authorization message;
The receiving unit 720 is further configured to, when the first user logs on a client device based on the first account, receive an operation request for requesting a service operation from the first user;
The searching unit 740 is configured to, according to the first account, search account binding relationship which has been stored;
The control unit 750 is configured to, if a second account bound with the first account is found, permit the first user to accomplish the service operation using the second account authority of the second account;
The update unit 760 is configured to, after the first user accomplishes the service operation using the second account authority, update the second account information of the second account according to the operation result of the service operation;
The receiving unit 720 is further configured to receive an authorization release message sent by the second user, the authorization release message including the first account;
The deletion unit 770 is configured to delete the binding relationship between the first account and the second account from the account binding relationship according to the authorization release message.
In one optional implementation manner:
the authorization message received by the receiving unit 720 may further include a using condition of the second account authority; and
the control unit 750 may be specifically configured to permit the first user, under the using condition, to accomplish the service operation using the second account authority of the second account.
Referring to
The second storage unit 810 is configured to, when the first user registers the first account, store a correspondence relationship between the first account and a first service password;
The receiving unit 820 is configured to, when the first user logs on a client device based on the first account, receive an operation request for requesting a service operation from the first user
The searching unit 830 is configured to, according to the first account, search account binding relationship which has been stored;
The control unit 840 is configured to, if a second account bound with the first account is found, permit the first user to accomplish the service operation using the second account authority of the second account;
The update unit 850 is configured to update the second account information of the second account according to the operation result of the service operation;
The notification unit 860 is configured to, after the second account information of the second account is updated, send a notification message to the second user, to notify the second user of updated contents of the second account information.
In one optional implementation manner:
the control unit 840 may include (not shown in
an account outputting sub-unit, configured to output the second account as an optional account on a service operation interface of the first user;
a password receiving sub-unit, configured to receive a service password input after the first user selects the second account for accomplishing the service operation; and
an authority release sub-unit, configured to, when it is verified that the input service password is consistent with the first service password stored in the correspondence relationship, release the first user to accomplish the service operation using the second account authority.
In another optional implementation manner:
the receiving unit 820 may be further configured to receive a reverse operation request for the service operation sent by the first user; and
the update unit 850 may be further configured to, after the reverse operation of the service operation is accomplished, update the second account information according to the operation result of the reverse operation.
Referring to
The receiving unit 910 is configured to, when a first user logs on a client device based on a first account, receive an operation request for requesting a service operation from the first user;
The searching unit 920 is configured to, according to the first account, search account binding relationship which has been stored;
The determination unit 930 is configured to, if a second account bound with the first account is found, determine a security attribute of a service scenario corresponding to the service operation;
The execution unit 940 is configured to, when the security attribute is secure, trigger the control unit to execute a corresponding function; when the security attribute is insecure, prohibit the first user from accomplishing the service operation using the second account authority.
The control unit 950 is configured to, after receiving a trigger instruction from the execution unit, permit the first user to accomplish the service operation using the second account authority of the second account;
The update unit 960 is configured to update the second account information of the second account according to the operation result of the service operation.
Reference can be made to the implementation processes of the corresponding steps in the above method for implementation processes of the functions and effects of the units in the apparatus, which are not repeated herein.
The apparatus embodiment is basically corresponding to the method embodiment, and thus reference can be made to the description in the method embodiment for the related contents. The apparatus embodiment described above is merely schematic. The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the present application. Those of ordinary skill in the art can understand and implement the present application without making creative efforts.
It is thus clear from the above embodiments that the second user can authorize the first user having an intimate relationship with the second user to use the second account authority of the second user, such that the first user can accomplish various service operations on the basis of the account authorities of multiple bound accounts, thus expanding the way of implementing services. Moreover, as the second account information is directly updated after a service operation is accomplished, the times of transmission of service data among different accounts can be reduced, thus improving the interactive efficiency of service information.
After considering the specification and practicing the invention disclosed here, those skilled in the art can easily think of other implementation solutions of the present application. The present application is aimed to cover any variations, uses or adaptive changes of the present application, and the variations, uses or adaptive changes conform to the general principle of the present application and include the common sense or common technical means in the technical field not disclosed in the present application. The specification and the embodiments are merely considered as exemplary. The real scope and spirit of the present application are indicated by the following claims.
It should be understood that the present application is not limited to the precise structure that has been described above and illustrated in the accompanying drawings, and various modifications and changes can be made thereto without departing from the scope thereof. The scope of the present application is merely limited by the appended claims.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2014 1 0416166 | Aug 2014 | CN | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/CN2015/086613 | 8/11/2015 | WO | 00 |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2016/026399 | 2/25/2016 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 6714791 | Friedman | Mar 2004 | B2 |
| 7204412 | Foss | Apr 2007 | B2 |
| 8121945 | Rackley et al. | Feb 2012 | B2 |
| 8326769 | Weisman | Dec 2012 | B1 |
| 8662384 | Dodin | Mar 2014 | B2 |
| 8666834 | Kamimaeda et al. | Mar 2014 | B2 |
| 9665864 | Prakash et al. | May 2017 | B2 |
| 9864991 | Beasley et al. | Jan 2018 | B2 |
| 20040015702 | Mercredi et al. | Jan 2004 | A1 |
| 20070011104 | Leger et al. | Jan 2007 | A1 |
| 20080250026 | Linden et al. | Oct 2008 | A1 |
| 20080277465 | Pletz et al. | Nov 2008 | A1 |
| 20100138344 | Wong et al. | Jun 2010 | A1 |
| 20110093520 | Doyle et al. | Apr 2011 | A1 |
| 20110131077 | Tan | Jun 2011 | A1 |
| 20110289004 | Prakash et al. | Nov 2011 | A1 |
| 20110320347 | Tumminaro et al. | Dec 2011 | A1 |
| 20120197754 | Kalin | Aug 2012 | A1 |
| 20120197794 | Grigg et al. | Aug 2012 | A1 |
| 20120221420 | Ross | Aug 2012 | A1 |
| 20120254021 | Wohied et al. | Oct 2012 | A1 |
| 20130159173 | Sivaraman | Jun 2013 | A1 |
| 20140129959 | Battles et al. | May 2014 | A1 |
| 20150073994 | Nagayama | Mar 2015 | A1 |
| 20150134116 | Li | May 2015 | A1 |
| 20150142658 | Li | May 2015 | A1 |
| 20150215261 | Zhang | Jul 2015 | A1 |
| 20150237029 | Zhang | Aug 2015 | A1 |
| 20160098791 | Huang | Apr 2016 | A1 |
| 20160345166 | Hou | Nov 2016 | A1 |
| 20170026316 | Li | Jan 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 101093567 | Dec 2007 | CN |
| 101226616 | Jul 2008 | CN |
| 102254259 | Nov 2011 | CN |
| 102289754 | Dec 2011 | CN |
| 102831518 | Dec 2012 | CN |
| 103530766 | Jan 2014 | CN |
| 2006-239500 | Oct 2006 | JP |
| 2006-283500 | Oct 2006 | JP |
| 2006293500 | Oct 2006 | JP |
| 2008-129860 | Jun 2008 | JP |
| 2009-163706 | Jul 2009 | JP |
| 2012-003349 | Jan 2012 | JP |
| 2012-003359 | Jan 2012 | JP |
| Entry |
|---|
| International Preliminary Report on Patentability Chapter I for Application No. PCT/CN2015/086613, dated Feb. 21, 2017, 11 pages. |
| First Search Report for Chinese Application No. 201410416166.1, dated Feb. 24, 2018, 1 page. |
| First Office Action for Chinese Application No. 201410416166.1, dated Mar. 5, 2018, 8 pages. |
| International Search Report and Written Opinion for Application No. PCT/CN2015/086613, dated Nov. 11, 2015, 11 pages. |
| Final Office Action dated Sep. 4, 2018, issued in related Japanese Application No. 2017-510299 (3 pages). |
| First Office Action dated Aug. 20, 2018, issued in related Korean Application No. 10-2017-7004748 (5 pages). |
| Hayes, J., “Policy-based Authentication and Authorization: Secure Access to the Network Infrastructure,” Computer Security Applications, Dec. 11, 2000, 16th Annual Conference New Orleans, XP010529830, p. 328-333. |
| European Search Report for Application No. 15834266.7, dated Dec. 4, 2017, 8 pages. |
| Office Action for Japanese Application No. 2017-510299, dated May 22, 2018, 5 pages. |
| Decision of a patent grant for Japan Patent Application No. 2017-510299, dated Oct. 30, 2018, 1 page. |
| Number | Date | Country | |
|---|---|---|---|
| 20170272447 A1 | Sep 2017 | US |
