WO2019062687A1 - 基于app应用的鉴权方法、绑定方法、系统及设备 - Google Patents

基于app应用的鉴权方法、绑定方法、系统及设备 Download PDF

Info

Publication number
WO2019062687A1
WO2019062687A1 PCT/CN2018/107228 CN2018107228W WO2019062687A1 WO 2019062687 A1 WO2019062687 A1 WO 2019062687A1 CN 2018107228 W CN2018107228 W CN 2018107228W WO 2019062687 A1 WO2019062687 A1 WO 2019062687A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
app
short
binding
communication device
Prior art date
Application number
PCT/CN2018/107228
Other languages
English (en)
French (fr)
Inventor
贾海军
朱碧军
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2019062687A1 publication Critical patent/WO2019062687A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/725—Cordless telephones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Definitions

  • the present application relates to the field of computer technologies, and in particular, to an authentication method, a binding method, a system, and a device based on an APP application.
  • a work card is generally a card issued by a company with a work number and wearer information.
  • the work card is not only used to display employee information, but also used to brush the door, for attendance and so on.
  • work cards such as IC card badges, two-dimensional code cards, and so on.
  • the manager needs to manually enter the employee's information and badge information and perform the binding operation, and then manually configure the corresponding authority for the staff to manage the personnel. These tasks are all done by the management staff, which is heavy and time consuming.
  • the present application has been made in order to provide an APP application-based authentication method, apparatus, device and system that solve the above problems or at least partially solve the above problems.
  • an APP application-based authentication method including:
  • the user right is determined according to the first APP account information bound to the information of the first short-range communication device.
  • an APP application-based authentication method including:
  • Reading information of the short-range communication device
  • the information of the short-range communication device is sent to the APP server;
  • the authentication result includes: a user identity and a user right when the user identity is legal; the user identity is determined according to a binding relationship between the information of the short-range communication device and the APP account information; the user The authority is determined based on the APP account information bound to the information of the short-range communication device.
  • an authentication system based on an APP application includes:
  • a first APP server configured to acquire information of the first short-range communication device; determine a user identity according to a binding relationship between the information of the first short-range communication device and the first APP account information; When it is legal, the user right is determined according to the first APP account information bound to the information of the first short-range communication device;
  • An execution end configured to read information of the first short-range communication device; when the network is normal, send information of the first short-range communication device to the first APP server; according to the first APP server The result of the authentication of the feedback, the corresponding logical operation is performed;
  • the authentication result includes: the user identity and the user right when the user identity is legal.
  • an APP application-based binding method including:
  • an APP application-based binding method including:
  • Binding operation of the scan code information and the APP account information
  • a binding system based on an APP application including:
  • a second APP client configured to acquire a scan code object on the short-range communication device to identify the scan code information in response to the scan code request triggered by the user; acquire the APP account information of the user; and scan the code information and the location The upload of the APP account information;
  • the second APP server is configured to obtain scan code information and APP account information uploaded by the second APP client, and perform binding operations on the scan code information and the APP account information.
  • a server device including: a first memory and a first processor;
  • the first memory is configured to store a program
  • the first processor is coupled to the first memory, and configured to execute the program stored in the first memory, for:
  • the user right is determined according to the first APP account information bound to the information of the first short-range communication device.
  • an executive device including: a second memory and a second processor;
  • the second memory is configured to store a program
  • the second processor is coupled to the second memory, and configured to execute the program stored in the second memory, for:
  • Reading information of the short-range communication device
  • the information of the short-range communication device is sent to the APP server;
  • the authentication result includes: a user identity and a user right when the user identity is legal; the user identity is determined according to a binding relationship between the information of the short-range communication device and the APP account information; the user The authority is determined based on the APP account information bound to the information of the short-range communication device.
  • a client device including a third memory and a third processor, where
  • the third memory is configured to store a program
  • the third processor coupled to the third memory, is configured to execute the program stored in the third memory, for:
  • a client device including a fourth memory and a fourth processor, where
  • the fourth memory is configured to store a program
  • the fourth processor coupled to the fourth memory, is configured to execute the program stored in the fourth memory, for:
  • Binding operation of the scan code information and the APP account information
  • the employee can use the APP (Application) application to realize the binding of the information of the short-distance communication device and the employee APP account information, and the APP application platform can utilize the binding information and the account information on the platform, which simplifies the application.
  • the workload of the administrator, and the convenience of the authentication accuracy is also effectively improved.
  • FIG. 1 is a schematic flowchart of an APP-based authentication method according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of an APP-based authentication method according to another embodiment of the present application.
  • FIG. 3 is a schematic flowchart of an APP-based authentication method according to another embodiment of the present disclosure.
  • FIG. 4 is a schematic flowchart of a binding method based on an APP application according to an embodiment of the present disclosure
  • FIG. 5 is a schematic flowchart of a binding method based on an APP application according to another embodiment of the present disclosure
  • FIG. 6 is a schematic flowchart of a binding method based on an APP application according to another embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram of a work card involved in an APP application-based binding method according to an embodiment of the present disclosure
  • FIG. 8 is a schematic diagram of an interface of an APP client involved in an APP application-based binding method according to an embodiment of the present disclosure
  • FIG. 9 is another schematic diagram of an interface of an APP client involved in an APP application-based binding method according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic diagram of another interface of an APP client involved in an APP application-based binding method according to an embodiment of the present disclosure
  • FIG. 11 is a schematic structural diagram of an APP-based authentication system according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of a binding system based on an APP application according to an embodiment of the present disclosure
  • FIG. 13 is a schematic structural diagram of an APP-based authentication device according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic structural diagram of a server device according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic structural diagram of a server device according to another embodiment of the present disclosure.
  • FIG. 16 is a schematic structural diagram of an APP-based authentication device according to another embodiment of the present disclosure.
  • FIG. 17 is a schematic structural diagram of an apparatus of an execution end according to an embodiment of the present disclosure.
  • FIG. 18 is a schematic structural diagram of a binding device based on an APP application according to an embodiment of the present disclosure.
  • FIG. 19 is a schematic structural diagram of a client device according to an embodiment of the present disclosure.
  • FIG. 20 is a schematic structural diagram of an APP application-based binding apparatus according to another embodiment of the present disclosure.
  • FIG. 21 is a schematic structural diagram of a server device according to another embodiment of the present disclosure.
  • the administrator needs to manually brush each employee's short-range communication device (such as a badge), and then manually bind the information of the read short-range communication device to the information of the employee of the short-range communication device. Then configure the appropriate permissions for the employee.
  • the administrator is very likely to have problems with binding and/or privilege configuration errors due to heavy workload.
  • the embodiment of the present application provides an APP-based authentication scheme, which does not require an administrator to manually input related information, simplifies the administrator's work, and facilitates the accuracy of the authentication. Also got an effective upgrade.
  • FIG. 1 is a schematic flowchart diagram of an APP application-based authentication method according to an embodiment of the present application. As shown in FIG. 1 , the method provided in this embodiment includes:
  • the execution body of the method provided by this embodiment may be an APP server.
  • the APP can directly select an existing Instant Messaging Application (EIM), for example, "Enterprise WeChat” or the like.
  • EIM Instant Messaging Application
  • the APP server is the application platform corresponding to the APP, such as a regular server, a cloud server, a cloud host, a virtual center, and the like.
  • the short-range communication device may be an independent short-distance communication card, or a terminal having a short-distance communication function (such as a mobile phone, a wearable device, etc.), which is not specifically limited in the embodiment of the present application.
  • the execution end (such as the attendance device, the access control device, etc.) sends the information read to the first short-range communication device to the APP server. That is, the specific implementation process of this step may be: receiving information of the first short-range communication device sent by the execution end.
  • the binding relationship between the information of the first short-range communication device and the first APP account information may be determined based on the binding information. Specifically, the information of the short-range communication device with the binding relationship and the APP account information are recorded in the binding information.
  • the user can upload the information of the short-distance communication device to be bound by the APP client and the APP account information, and the APP server binds the information of the received short-range communication device and the APP account information to be tied. The associated storage in the information.
  • the user uses the enterprise WeChat client to complete the binding setting of the information of the short-range communication device and the APP account information, and the enterprise WeChat client sends a binding request to the enterprise WeChat server after responding to the binding confirmation operation of the user, the enterprise WeChat The server associates the received information of the short-range communication device with the APP account information and stores the information in the binding information.
  • the binding relationship between the information of the first short-range communication device and the first APP account information is bound, determining that the user identity is legal;
  • the binding relationship between the information of the first short-range communication device and the first APP account information is unbound, it is determined that the user identity is illegal.
  • the first APP account information may include one or more of user attribute information, such as work team information, job information, and belonging permission group information, in addition to the login name. These attribute information can be edited and set by the user after logging in to the APP (such as Enterprise WeChat); after the user setting is completed, it is uploaded to the APP server.
  • the user attribute information may not be included in the APP account information, but is stored as an independent information and associated with the corresponding APP account information.
  • the foregoing 103 may include: acquiring user attribute information according to the first APP account information; and determining the user authority according to the user attribute information.
  • Different work teams correspond to different user rights, or different positions correspond to different user rights, or different permission groups correspond to different user rights, etc.; these correspondences can be preset.
  • the correspondence between the user attribute information and the user authority is established; correspondingly, determining the user authority according to the user attribute information may be specifically: according to the correspondence between the user attribute information and the user authority And searching for the user right corresponding to the user attribute information.
  • the user authority may be a privilege level or the like, which is not specifically limited in this embodiment of the present application.
  • the technical solution provided by the embodiment of the present application uses the APP application platform (ie, the server or the cloud) to determine the identity and authority of the employee using the short-range communication device; since the APP application platform stores various information uploaded by the employee, for example, , login information, bound badge information and user information, employee-owned workgroups, positions, etc. This information can be used as the basis for authentication. Managers do not need to input this information repeatedly, which simplifies the workload of the administrator, and the convenience is also improved under the premise of ensuring the accuracy of authentication.
  • the APP application platform ie, the server or the cloud
  • the method provided by the foregoing embodiment may further include the following steps:
  • 105 Receive a binding request sent by the user by using the APP client, where the binding request carries information about a second short-range communication device to be bound and second APP account information.
  • the binding process may be specifically: determining whether the information of the second short-range communication device has been bound to other APP account information except the second APP account information; if not, the The information of the two short-range communication devices is associated with the second APP account information and stored in the binding information.
  • the technical solution provided by the foregoing embodiment may further include:
  • the process of unbinding may be specifically: deleting the information of the third short-range communication device with the binding relationship recorded in the binding information and the third APP account information.
  • the method provided by the foregoing embodiment requires that the network connection between the execution end and the server end is normal.
  • the executor can send information, receive information, and the like to the server through the network.
  • the embodiment of the present application further provides the following method for the execution end to cache the binding information. And/or application account information.
  • the method provided by the foregoing embodiment may further include:
  • the binding information records the information of the short-range communication device with the binding relationship and the APP account information, and the authentication result includes the user identity and the user right when the user identity is legal.
  • FIG. 2 is a schematic flowchart diagram of an APP application-based authentication method provided by another embodiment of the present application. As shown in FIG. 2, the method provided in this embodiment includes:
  • the authentication result includes: a user identity and a user authority when the user identity is a legal identity; the user identity is determined according to a binding relationship between the information of the short-range communication device and the APP account information; The user rights are determined based on APP account information bound to the information of the short-range communication device.
  • the execution body of the method provided by this embodiment may be an execution end.
  • the executor may be a specific physical device, such as an access control device, an attendance device, or an application program installed on the terminal device, which is not specifically limited in this embodiment of the present application.
  • the badge information is sent to the APP server through the network.
  • the APP server determines whether the information of the short-range communication device has a binding relationship with an APP account information to determine the user identity, and if the user identity is legal, according to the short distance
  • the APP account information bound by the communication device determines the user authority.
  • a specific implementation manner of the foregoing 203 may be specifically: if the user identity is illegal, the illegal prompt information is output; if the user identity is legal, and the user authority is higher than or equal to the preset permission level, performing the attendance operation And / or control access control to open the door.
  • the technical solution provided by the embodiment of the present application uses the APP application platform (ie, the server or the cloud) to determine the identity and authority of the employee using the short-range communication device; since the APP application platform stores various information uploaded by the employee, for example, , login information, bound badge information and user information, employee-owned workgroups, positions, etc. This information can be used as the basis for authentication. Managers do not need to input this information repeatedly, which simplifies the workload of the administrator, and the convenience is also improved under the premise of ensuring the accuracy of authentication.
  • the APP application platform ie, the server or the cloud
  • the implementation method provided by the foregoing embodiment is based on the premise that the network is normal; when the network is abnormal (broken network), the foregoing method cannot be performed.
  • the method provided by the embodiment of the present application further includes the following steps:
  • the binding information is cached locally.
  • the binding information records the information of the short-range communication device with the binding relationship and the APP account information.
  • the purpose of the above steps is to deliver the binding information to the executor when the network is normal.
  • the network exception is unpredictable, so the APP server can be delivered periodically, for example, once every N hours; or when the binding information is updated, the APP server sends the binding to synchronize the execution cache. Information.
  • the corresponding method provided by this embodiment may adopt the following methods for authentication when the network is abnormal:
  • the information of the read short-range communication device is authenticated according to the binding information, and corresponding logical operations are performed according to the authentication result.
  • FIG. 3 is a schematic flowchart diagram of an APP application-based authentication method according to an embodiment of the present application. This embodiment substitutes the execution subject of each step. As shown in FIG. 3, the method includes:
  • the APP client reads the information of the short-range communication device in response to the user-triggered read operation.
  • the APP client obtains the user account information of the user, and displays the information of the APP account and the information of the short-range communication device in the binding setting interface.
  • the APP client listens to the binding confirmation event, uploads the APP account information and the information of the short-range communication device to the APP server.
  • the APP server determines whether the information of the short-range communication device is bound to other APP account information except the APP account information, and if not, the information of the short-range communication device and the APP account. Information is associated and stored in the binding information.
  • the execution device reads information of the short-range communication device.
  • the executor device monitors that the network is normal, the information of the short-range communication device is sent to the APP server.
  • the APP server determines whether the information of the short-range communication device has a binding relationship with the APP account information; if yes, determines that the user identity is legal; otherwise, determines that the user identity is illegal.
  • the APP server determines the user right according to the APP account information that is bound to the information of the short-range communication device.
  • the APP server feeds back the authentication result to the execution device.
  • the authentication result includes the user identity and the user authority when the user identity is a legal identity.
  • the execution end If the user identity is illegal, the execution end outputs an illegal prompt message; if the user identity is legal, and the user authority is higher than or equal to the preset permission level, the execution end performs the attendance operation and/or controls the access control. Open the door.
  • the user can trigger the information reading operation of the short-distance communication device by using the control on the touch APP client interface.
  • a Near Field Communication (NFC) function of a terminal device installed with an APP client is started to read information of the short-range communication device.
  • the camera of the terminal device installed with the APP client is scanned to obtain the information of the short-range communication device.
  • enterprise WeChat an instant messaging application
  • a short-range communication device with two-dimensional code information the user can enter the client interface after logging in to the enterprise WeChat.
  • the client interface displays a scan code control "sweep"; the user touches the "sweep” control, that is, enters the scan code interface, the camera of the mobile device is activated, and the scan in the scan code interface Scanning objects in the code area (such as the QR code on the badge) are collected and identified.
  • the APP account information may be obtained by the APP automatically according to the login information when the user logs in to the application.
  • the APP account information can also be entered by the user.
  • the method provided in this embodiment may be specifically: after reading the information of the short-range communication device, displaying a binding setting interface including information of the short-range communication device; the binding setting a filling box for prompting the user to fill in the information is displayed in the interface; in response to the touch operation of the user for the filling frame, an editing interface is displayed on the binding setting interface; the user may be in the display editing interface. Edit the APP account information you want to enter.
  • the user can input the APP account information through the keyboard, or input the APP account information by means of voice, and the like, and the specific input mode is not specifically limited in the present application.
  • the method provided in this embodiment may be specifically: obtaining the APP account information according to the login information when the user logs in to the application, and entering the location after reading the information of the short-distance communication device.
  • the binding setting interface is displayed, and the information of the short-range communication device and the APP account information are simultaneously displayed in the binding setting interface.
  • the information of the short-distance communication device in 302 and the APP account information may be displayed in the binding setting interface in succession or in the binding setting interface.
  • the information and the APP account information of the short-distance communication device may be specifically:
  • binding setting interface displaying information of the short-range communication device, APP account information, and a page element indicating that the information of the short-range communication device and the APP account information have a binding relationship;
  • the page element that displays the information indicating that the short-distance communication device and the APP account information have a binding relationship may be: displaying text information, pattern information, animation information, and the like having a prompting function in the binding setting interface, and the present application
  • the embodiment does not specifically limit this.
  • the two associated display areas can be two display areas having the same design elements (such as the same color, the same size and shape, etc.), or two display areas that are close to each other.
  • the purpose of the association display here is to highlight the relationship between the two data, so that the user can easily notice the binding information and then confirm.
  • the binding confirmation event may be triggered by the confirmation control button on the user touch binding setting interface.
  • the information of the uploaded short-range communication device and the APP account information may be carried in the binding request and sent to the APP server.
  • the information of the short-range communication device and the APP account information may be compressed and packaged, and then uploaded as a binding file to the office. Said APP server.
  • the method further includes the following steps: the APP server feeds back information about the short-distance communication device and the binding result of the APP account information to the client when the binding operation is completed; the APP client The terminal displays the binding result fed back by the server.
  • the binding result may be automatically fed back after the binding operation is performed on the APP server, or may be fed back by the APP server after the APP client sends the query request.
  • the binding result can be directly displayed in the binding setting interface, or in the floating setting manner in the binding setting interface, or displayed in a new interface.
  • FIG. 4 is a schematic flowchart diagram of an APP application-based binding method according to an embodiment of the present application. As shown in FIG. 4, the method includes:
  • the scan code object may be a barcode, a two-dimensional code, or the like, which is not specifically limited in the present application.
  • the identification of the scan code object can be implemented by referring to the codec algorithm corresponding to the corresponding type code in the prior art, and the details are not described herein again.
  • the user can trigger the scan code request by using a scan code control on the touch APP client interface.
  • the method provided in this embodiment may further include the following steps:
  • the scan code request is generated in response to a user's touch operation on the scan code control.
  • the company's WeChat interface displays a scan code control "sweep"; the user touches the "sweep" control, that is, enters the scan code interface, the enterprise WeChat client device (such as mobile phone, tablet, wearable device, etc.)
  • the camera is activated and the scan code object (such as the QR code on the badge) in the scan code interface is collected and identified.
  • the APP account information that is, the information of the user login APP application, for example, may include, but is not limited to, one or more of a user name, a nickname, a mailbox, a mobile phone number, and the like.
  • the scan code information and the APP account information may be triggered to be sent to the APP server after the APP client listens to the user binding confirmation event.
  • the user binding confirmation event may be a confirmation voice sent by the user, or may be an operation of the user's touch confirmation control, etc., which is not specifically limited in this embodiment.
  • the APP application-based binding method provided by the embodiment of the present application may further include:
  • the jump to the binding setting interface displaying the scan code information and the APP account information is displayed.
  • the user can trigger a binding confirmation event by binding a confirmation control on the settings interface. That is, the above-mentioned scanning code information and the APP account information are sent to the APP server to perform a binding operation on the APP server.
  • the embodiment of the present application provides a scheme for actively uploading binding information by an employee, which simplifies the work of the administrator; in addition, the employee independently uploads the binding information and independently confirms the accuracy, and can effectively reduce the error of the binding information. Probability.
  • the binding result may be automatically fed back after the binding operation is performed on the APP server, or may be fed back by the APP server after the APP client sends the query request.
  • the binding result can be directly displayed in the binding setting interface, or in the floating setting manner in the binding setting interface, or displayed in a new interface.
  • the APP application-based binding method provided by the foregoing embodiment may further include an unbinding step.
  • an unbinding step may further include:
  • the scan code information and the APP account information to be unbound are sent to the APP server to perform the unbinding operation on the APP server.
  • FIG. 5 is a schematic flowchart diagram of an APP application-based binding method according to another embodiment of the present application. As shown in FIG. 5, the method includes:
  • the scan code information and the APP account information may be obtained from the binding request uploaded by the APP client, or may be obtained by extracting the binding data package uploaded by the APP client.
  • the scan code information may be collected and recognized by the APP client by starting a camera on the client device.
  • the foregoing 211 may specifically include:
  • the scan code information and the APP account information are associated and stored in the binding information.
  • the foregoing 211 may further include: if yes, feeding back a binding failure prompt result.
  • the binding success prompt result may also be fed back to the client. That is, the method provided by the foregoing embodiment may further include:
  • the binding result of the scan code information and the APP account information is fed back to the APP client.
  • the binding result is the result of the binding failure prompt or the binding success prompt result.
  • the APP server can automatically feed back the binding result to the client after the binding operation is completed, and can also provide feedback after the receiving APP client sends the query request, which is not specifically limited in this embodiment of the present application. .
  • the method provided by the foregoing embodiment may further include:
  • the embodiment of the present application provides a scheme for actively uploading binding information by an employee, which simplifies the work of the administrator.
  • the employee automatically uploads the binding information and independently confirms the accuracy, which can effectively reduce the error rate of the binding information. Improve the efficiency of importing binding information.
  • FIG. 6 is a schematic flowchart diagram of an APP application-based binding method according to another embodiment of the present application. As shown in Figure 6, the binding process is as follows:
  • the APP client acquires a scan code object on the short-range communication device to identify the scan code information in response to the user-triggered scan code request.
  • the APP client acquires the APP account information of the user.
  • the APP client sends the scan code information and the APP account information to the APP server.
  • the APP server determines whether the scan code information is bound to other APP account information except the APP account information; if not, the scan code information and the APP account information are associated and stored in In the binding information, otherwise, the binding fails.
  • the embodiment of the present application provides a scheme for actively uploading binding information by an employee, which simplifies the work of the administrator.
  • the employee automatically uploads the binding information and independently confirms the accuracy, which can effectively reduce the error rate of the binding information. Improve the efficiency of importing binding information.
  • the binding application authentication method based on the APP application provided by the embodiment of the present application is described below by taking the two-dimensional code card as an example.
  • the APP application is Enterprise WeChat
  • the employee badge is a two-dimensional code badge (as shown in Figure 7);
  • the execution end is an access control device.
  • the employee can scan the two-dimensional code card through the “sweep” control displayed on the enterprise WeChat interface to read the scan code information (ie, the information of the badge).
  • the scan code page is jumped to the binding setting interface; the user can fill in the APP account information in the binding setting interface, or the enterprise WeChat directly displays the currently registered APP account information in the binding.
  • Set the interface The user triggers a binding confirmation event through the "Submit" control on the touch binding settings interface.
  • the enterprise WeChat client uploads the information of the badge and the APP account information to the enterprise WeChat server in response to the binding confirmation event.
  • the enterprise WeChat server binds the scan code information and the APP account information, and feeds back the binding result (such as the binding success prompt information shown in FIG. 10).
  • the employee places the badge in the scan code area of the access control device.
  • the access control device reads the information of the badge through the scan code operation
  • the access control device uploads the information of the badge to the enterprise WeChat server
  • the enterprise WeChat server queries and binds Determining the binding relationship between the information of the badge and the APP account information in the information; if the binding relationship between the information of the badge and the APP account is bound, determining the identity of the user as a legal identity; otherwise, determining User identity is illegal.
  • the enterprise WeChat server obtains the user attribute information (such as the work team, the job information, the belonging permission group, and the like) of the employee based on the account information stored by the enterprise, and determines the user authority according to the user attribute information. .
  • the enterprise WeChat server feeds back the authentication result to the access control device. If the authentication result is illegal, the access control device outputs the illegal prompt information by using voice, text or video. If the authentication result is legal and the user authority is higher than or equal to the permission level preset by the access control device, the access device performs a door opening action.
  • FIG. 11 is a schematic structural diagram of an APP application-based authentication system according to an embodiment of the present application. As shown in FIG. 11, the system provided in this embodiment includes:
  • the first APP server 401 is configured to acquire information of the first short-range communication device; and determine a user identity according to the binding relationship between the information of the first short-range communication device and the first APP account information; When the user identity is legal, the user right is determined according to the first APP account information bound to the information of the first short-range communication device;
  • the first execution end 402 is configured to read information of the first short-range communication device; when the network is normal, the information of the first short-range communication device is sent to the first APP server 401; according to the first The authentication result fed back by the APP server 401 performs a corresponding logical operation;
  • the authentication result includes: the user identity and the user right when the user identity is legal.
  • the foregoing system further includes: a first APP client 403.
  • the first APP client 403 is configured to send a binding request to the first APP server 401, where the binding request carries the information of the second short-range communication device to be bound and the second APP account information.
  • the first APP server 401 is further configured to perform a binding operation on the information of the second short-range communication device and the second APP account information.
  • the first APP client 403 in the foregoing system is further configured to send an unbinding request to the APP server, where the unbinding request carries information about a third short-range communication device to be unbound and
  • the third APP account information is further configured to perform the unbinding operation on the information of the third short-range communication device and the third APP account information.
  • first APP client 403 and the first execution terminal 402 may be the same application software or the same hardware entity, or may be application software installed on different hardware devices, or may be two different hardware.
  • the device may also be two different application softwares installed on the same hardware device, which is not specifically limited in this embodiment.
  • the first APP server 401 may be a conventional server, a cloud, a virtual center, or the like, which is not specifically limited in this embodiment of the present application.
  • the APP application-based authentication system provided by the foregoing embodiment may implement the technical solution described in the foregoing method embodiment shown in FIG. 3, and the principles of the foregoing various modules or units may be referred to the foregoing method embodiments. The corresponding content in the content will not be described here.
  • the technical solution provided by the embodiment of the present application utilizes an APP application platform (ie, a server or a cloud) to determine the identity and authority of an employee who uses a short-range communication device (such as a badge); since the APP application platform stores an employee-uploaded
  • a short-range communication device such as a badge
  • the APP application platform stores an employee-uploaded
  • FIG. 12 is a schematic structural diagram of an APP application-based binding system according to an embodiment of the present application.
  • the APP application-based binding system includes: a second APP client 411 and a second APP server 412.
  • the second APP client 411 is configured to acquire a scan code object on the short-range communication device to identify the scan code information in response to the scan code request triggered by the user, and acquire the APP account information of the user;
  • the code information and the APP account information are uploaded.
  • the second APP server 412 is configured to obtain scan code information and APP account information uploaded by the APP client, and perform binding operations on the scan code information and the APP account information.
  • the APP client and the APP server in the APP-based binding system can implement the technical solutions described in the foregoing method embodiments shown in FIG. 4 and FIG. 5, respectively.
  • the APP client and the APP server in the APP-based binding system can implement the technical solutions described in the foregoing method embodiments shown in FIG. 4 and FIG. 5, respectively.
  • the APP client and the APP server in the APP-based binding system can implement the technical solutions described in the foregoing method embodiments shown in FIG. 4 and FIG. 5, respectively.
  • FIG. 4 and FIG. 5 For details, refer to the corresponding content in the foregoing method embodiments, and details are not described herein again.
  • the second APP server 412 may be a conventional server, a cloud, a virtual center, or the like; the second APP client 411 may be an application software (such as an enterprise WeChat) or a hardware entity, which is not specifically limited in this embodiment of the present application.
  • the embodiment of the present application provides a scheme for actively uploading binding information by an employee, which simplifies the work of the administrator.
  • the employee automatically uploads the binding information and independently confirms the accuracy, which can effectively reduce the error rate of the binding information. Improve the efficiency of importing binding information.
  • FIG. 13 is a schematic structural diagram of an APP application-based authentication apparatus according to an embodiment of the present application.
  • the information binding apparatus includes: a first obtaining module 501, a first determining module 502, and a second determining module 503.
  • the first obtaining module 501 is configured to acquire information about the first short-range communication device
  • the first determining module 502 is configured to use, according to the binding relationship between the information of the first short-range communication device and the first APP account information, Determining the user identity
  • the second determining module 503 is configured to determine the user right according to the first APP account information bound to the information of the first short-range communication device when the user identity is legal.
  • the first determining module 502 is further configured to: if the binding relationship between the information of the first short-range communication device and the first APP account information is bound, determine that the user identity is legal; If the binding relationship between the information of the first short-range communication device and the first APP account information is unbound, it is determined that the user identity is illegal.
  • the second determining module 503 is further configured to obtain user attribute information according to the first APP account information, and determine the user right according to the user attribute information.
  • the user attribute information includes one or more of work team information, job information, and belonging permission group information.
  • the APP application-based authentication device may further include: a first receiving module and a binding module.
  • the first receiving module is configured to receive a binding request sent by the user by using the APP client, where the binding request carries information about a second short-range communication device to be bound and a second APP account.
  • the binding module is configured to perform binding operation on the information of the second short-range communication device and the second APP account information.
  • the binding module is further configured to determine whether information of the second short-range communication device has been bound to other APP account information except the second APP account information; The information of the two short-range communication devices is associated with the second APP account information and stored in the binding information.
  • the APP application-based authentication device may further include: a second receiving module and an unbinding module.
  • the second receiving module is configured to receive the unbinding request sent by the user by using the APP client, where the unbinding request carries the information of the third short-range communication device to be untied and the third APP account information;
  • the unbinding module is configured to perform unbinding operation on the information of the third short-range communication device and the third APP account information.
  • the APP application-based authentication device further includes: a sending module.
  • the sending module is configured to send binding information to the executing end, so that the executing end caches the binding information locally, and reads short-distance communication according to the binding information when the network is abnormal.
  • the information of the device is authenticated, and the corresponding logical operation is performed according to the authentication result; wherein the binding information records information of the short-range communication device with binding relationship and APP account information, and the authentication result includes the user.
  • User rights when identity and user identity are legal.
  • the APP application-based authentication device provided by the foregoing embodiment can implement the technical solution described in the foregoing method embodiment shown in FIG. 1.
  • the specific implementation principles of the foregoing modules or units can be found in the foregoing method embodiment. The corresponding content will not be described here.
  • the technical solution provided by the embodiment of the present application uses the APP application platform (ie, the server or the cloud) to determine the identity and authority of the employee using the short-range communication device; since the APP application platform stores various information uploaded by the employee, for example, , login information, bound badge information and user information, employee-owned workgroups, positions, etc. This information can be used as the basis for authentication. Managers do not need to input this information repeatedly, which simplifies the workload of the administrator, and the convenience is also improved under the premise of ensuring the accuracy of authentication.
  • the APP application platform ie, the server or the cloud
  • FIG. 14 is a schematic structural diagram of a server device according to an embodiment of the present disclosure.
  • the server device includes a first memory 601 and a first processor 602.
  • the first memory 601 can be configured to store other various data to support operations on the server device. Examples of such data include instructions for any application or method operating on a server device.
  • the first memory 601 can be implemented by any type of volatile or non-volatile memory device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable In addition to Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Disk or Optical Disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk or Optical Disk.
  • the first processor 602 is coupled to the first memory 601 for executing a program stored in the first memory 601 for:
  • the user right is determined according to the first APP account information bound to the information of the first short-range communication device.
  • the first processor 602 can implement other functions in addition to the above functions when performing the program in the first memory 601. For details, refer to the description of the foregoing embodiments.
  • the server device further includes: a first communication component 603, a first display 604, a first power component 605, a first audio component 606, and the like. Only some of the components are schematically illustrated in FIG. 15, and it is not meant that the electronic device includes only the components shown in FIG.
  • the embodiment of the present application further provides a computer readable storage medium storing a computer program, which can implement the steps or functions of the cloud virtual machine creation method provided by the foregoing embodiments when the computer program is executed by the computer.
  • FIG. 16 is a schematic structural diagram of an APP application-based authentication apparatus according to another embodiment of the present application.
  • the APP-based authentication device includes a reading module 701, a sending module 702, and an executing module 703.
  • the reading module 701 is configured to send information of the short-range communication device to the APP server when the network is normal, and the execution module 703 is configured to serve according to the APP.
  • the authentication result of the end feedback performs a corresponding logical operation; wherein the authentication result includes: a user identity and a user authority when the user identity is a legal identity; the user identity is based on the information of the short-range communication device The binding relationship with the APP account information is determined; the user right is determined according to the APP account information bound to the information of the short-range communication device.
  • the APP application-based authentication device may further include: a third receiving module and a storage module.
  • the third receiving module is configured to receive the binding information that is sent by the APP server, and the storage module is configured to cache the binding information locally.
  • the APP application-based authentication device may further include:
  • the third determining module is configured to authenticate the information of the short-range communication device according to the binding information when the network is abnormal, and perform a corresponding logical operation according to the authentication result.
  • execution module 703 is further configured to: if the user identity is illegal, output illegal prompt information; if the user identity is legal, and the user authority is higher than or equal to a preset permission level, performing the attendance operation and / or control the access control to open the door.
  • the APP application-based authentication device provided by the foregoing embodiment may implement the technical solution described in the foregoing method embodiment shown in FIG. 2, and the principles of the foregoing various modules or units may be referred to the foregoing method embodiments. The corresponding content in the content will not be described here.
  • the technical solution provided by the embodiment of the present application uses the APP application platform (ie, the server or the cloud) to determine the identity and authority of the employee using the short-range communication device; since the APP application platform stores various information uploaded by the employee, for example, , login information, bound badge information and user information, employee-owned workgroups, positions, etc. This information can be used as the basis for authentication. Managers do not need to input this information repeatedly, which simplifies the workload of the administrator, and the convenience is also improved under the premise of ensuring the accuracy of authentication.
  • the APP application platform ie, the server or the cloud
  • FIG. 17 is a schematic structural diagram of an apparatus of an execution end according to an embodiment of the present disclosure.
  • the executor device includes a second memory 801 and a second processor 802.
  • the second memory 801 can be configured to store other various data to support operations on the execution end device. Examples of such data include instructions for any application or method operating on an execution end device.
  • the second memory 801 can be implemented by any type of volatile or non-volatile memory device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable In addition to Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Disk or Optical Disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk or Optical
  • the second processor 802 is coupled to the second memory 801 for executing a program stored in the second memory 801 for:
  • Reading information of the short-range communication device
  • the information of the short-range communication device is sent to the APP server;
  • the authentication result includes: a user identity and a user right when the user identity is legal; the user identity is determined according to a binding relationship between the information of the short-range communication device and the APP account information; the user The authority is determined based on the APP account information bound to the information of the short-range communication device.
  • the second processor 802 can implement other functions in addition to the above functions when performing the program in the second memory 801. For details, refer to the description of the foregoing embodiments.
  • the execution device further includes: a second communication component, a second display, a third power component, a third audio component, and the like.
  • the embodiment of the present application further provides a computer readable storage medium storing a computer program, which can implement the steps or functions of the cloud virtual machine creation method provided by the foregoing embodiments when the computer program is executed by the computer.
  • FIG. 18 is a schematic structural diagram of a binding device based on an APP application according to an embodiment of the present disclosure. As shown, the device includes:
  • the second obtaining module 511 is configured to obtain a scan code object on the short-range communication device to identify the scan code information in response to the user-triggered scan code request;
  • the third obtaining module 512 is configured to acquire APP account information of the user.
  • the sending module 513 is configured to send the scan code information and the APP account information to the APP server to perform a binding operation on the APP server.
  • the device may further include:
  • a display module after the scan code is successful, jumps to a binding setting interface that displays the scan code information and the APP account information;
  • the sending module 513 is further configured to send the scan code information and the APP account information to the APP server in response to a binding confirmation event triggered by the user through the binding setting interface.
  • the display module is further configured to display a binding result fed back by the server.
  • the third obtaining module 512 is further configured to: in response to the unbinding request of the user, obtain scan code information and APP account information to be unbound;
  • the sending module 513 is further configured to send the scan code information and the APP account information to be unbound to the APP server to perform an unbinding operation on the APP server.
  • the APP application-based binding device provided by the foregoing embodiment may implement the technical solution described in the foregoing method embodiment shown in FIG. 4, and the principles of the foregoing various modules or units may be referred to the foregoing method embodiments. The corresponding content in the content will not be described here.
  • the embodiment of the present application provides a scheme for actively uploading binding information by an employee, which simplifies the work of the administrator.
  • the employee automatically uploads the binding information and independently confirms the accuracy, which can effectively reduce the error rate of the binding information. Improve the efficiency of importing binding information.
  • FIG. 19 is a schematic structural diagram of a client device according to an embodiment of the present disclosure.
  • the client device includes a third memory 811 and a third processor 812.
  • the third memory 811 can be configured to store other various data to support operations on the client device. Examples of such data include instructions for any application or method operating on a client device.
  • the third memory 811 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable In addition to Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Disk or Optical Disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk or Optical Disk.
  • the third processor 812 is coupled to the third memory 811 for executing a program stored in the third memory 811 for:
  • the third processor 812 can implement other functions in addition to the above functions when performing the program in the third memory 811. For details, refer to the description of the foregoing embodiments.
  • the execution device further includes: a third communication component, a third display, a third power component, a third frequency component, and the like.
  • the embodiment of the present application further provides a computer readable storage medium storing a computer program, which can implement the steps or functions of the cloud virtual machine creation method provided by the foregoing embodiments when the computer program is executed by the computer.
  • FIG. 20 shows an APP application-based binding apparatus provided by another embodiment of the present application. As shown in FIG. 20, the device includes:
  • the fourth obtaining module 522 is configured to obtain scan code information and APP account information uploaded by the APP client.
  • the binding module 523 is configured to perform a binding operation on the scan code information and the APP account information.
  • binding module 523 is further configured to:
  • the scan code information and the APP account information are associated and stored in the binding information.
  • the APP application-based binding device provided by the foregoing embodiment can implement the technical solution described in the foregoing method embodiment shown in FIG. 5, and the principles of the foregoing various modules or units can be referred to the foregoing method embodiments. The corresponding content in the content will not be described here.
  • the embodiment of the present application provides a scheme for actively uploading binding information by an employee, which simplifies the work of the administrator.
  • the employee automatically uploads the binding information and independently confirms the accuracy, which can effectively reduce the error rate of the binding information. Improve the efficiency of importing binding information.
  • FIG. 21 is a schematic structural diagram of a server device according to an embodiment of the present disclosure.
  • the server device includes a fourth memory 611 and a fourth processor 612.
  • the fourth memory 611 can be configured to store other various data to support operations on the server device. Examples of such data include instructions for any application or method operating on a server device.
  • the fourth memory 611 can be implemented by any type of volatile or non-volatile memory device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable In addition to Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Disk or Optical Disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk or Optical Disk.
  • the fourth processor 612 is coupled to the fourth memory 611 for executing a program stored in the fourth memory 611 for:
  • Binding operation of the scan code information and the APP account information
  • the fourth processor 612 can implement other functions in addition to the above functions when performing the program in the fourth memory 611. For details, refer to the description of the foregoing embodiments.
  • the server device further includes: a fourth communication component, a fourth display, a fourth power component, a fourth audio component, and the like.
  • the embodiment of the present application further provides a computer readable storage medium storing a computer program, which can implement the steps or functions of the cloud virtual machine creation method provided by the foregoing embodiments when the computer program is executed by the computer.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without deliberate labor.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Human Computer Interaction (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请实施例提供一种基于APP应用的鉴权方法、绑定方法、系统及设备。其中，信息绑定方法包括：获取第一短距离通信装置的信息；根据所述第一短距离通信装置的信息与第一APP账号信息之间的绑定关系，确定用户身份；用户身份合法时，根据与所述第一短距离通信装置的信息绑定的所述第一APP账号信息，确定用户权限。本申请实施例提供的技术方案，员工可使用APP应用实现短距离通信装置的信息与员工APP账号信息的绑定，APP应用平台可利用平台上的绑定信息及账号信息，对使用短距离通信装置的员工进行身份和权限的确定，简化了管理员的工作量，且在保证了鉴权准确性的前提下便捷性也得到了有效的提升。

Description

基于APP应用的鉴权方法、绑定方法、系统及设备
本申请要求2017年09月30日递交的申请号为201710944518.4、发明名称为“基于APP应用的鉴权方法、绑定方法、系统及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，尤其涉及一种基于APP应用的鉴权方法、绑定方法、系统及设备。
背景技术
工作牌一般是由企业发行的，带有工作号及佩戴人信息的卡牌。工作牌不仅用来展示员工信息外，还可用于刷门禁，用于考勤等等。目前，工牌有很多种类，例如IC卡工牌、二维码工牌等等。员工将工牌靠近门禁/考勤机，门禁/考勤机读取或扫描工牌的信息后，即可刷开门禁或完成考勤。
但实现上述过程的前提是，管理人员需人工录入员工的信息及工牌信息并执行绑定操作，然后再人工为员工配置相应的权限，以便人员管理。这些工作都需管理人员完成，工作量大，且费时费力。
发明内容
鉴于上述问题，提出了本申请以便提供一种解决上述问题或至少部分地解决上述问题的基于APP应用的鉴权方法、装置、设备及系统。
在本申请的一个实施例中，提供了一种基于APP应用的鉴权方法，包括：
获取第一短距离通信装置的信息；
根据所述第一短距离通信装置的信息与第一APP账号信息之间的绑定关系，确定用户身份；
用户身份合法时，根据与所述第一短距离通信装置的信息绑定的所述第一APP账号信息，确定用户权限。
在本申请的另一个实施例中，提供了一种基于APP应用的鉴权方法，包括：
读取短距离通信装置的信息；
网络正常时，将所述短距离通信装置的信息发送至APP服务端；
根据所述APP服务端反馈的鉴权结果，执行相应的逻辑操作；
其中，所述鉴权结果包括：用户身份及在用户身份合法时的用户权限；所述用户身份是根据所述短距离通信装置的信息与APP账号信息之间的绑定关系确定；所述用户权限是根据与所述短距离通信装置的信息绑定的APP账号信息确定。
在本申请的又一个实施例中，提供了一种基于APP应用的鉴权系统。该系统包括：
第一APP服务端，用于获取第一短距离通信装置的信息；根据所述第一短距离通信装置的信息与第一APP账号信息之间的绑定关系，确定用户身份；所述用户身份合法时，根据与所述第一短距离通信装置的信息绑定的第一APP账号信息，确定用户权限；
执行端，用于读取所述第一短距离通信装置的信息；网络正常时将所述第一短距离通信装置的信息发送至所述第一APP服务端；根据所述第一APP服务端反馈的鉴权结果，执行相应的逻辑操作；
其中，所述鉴权结果包括：所述用户身份以及在所述用户身份合法时的所述用户权限。
在本申请的又一个实施例中，提供了一种基于APP应用的绑定方法，包括：
响应于用户触发的扫码请求，获取短距离通信装置上的扫码对象以识别扫码信息；
获取所述用户的APP账号信息；
将所述扫码信息及所述APP账号信息发送至APP服务端，以在所述APP服务端执行绑定操作。
在本申请的又一个实施例中，提供了一种基于APP应用的绑定方法，包括：
获取APP客户端上传的扫码信息及APP账号信息；
对所述扫码信息及所述APP账号信息进行绑定操作。
在本申请的又一个实施例中，提供了一种基于APP应用的绑定系统，包括：
第二APP客户端，用于响应于用户触发的扫码请求，获取短距离通信装置上的扫码对象以识别扫码信息；获取所述用户的APP账号信息；将所述扫码信息及所述APP账号信息上传；
第二APP服务端，用于获取所述第二APP客户端上传的扫码信息及APP账号信息；对所述扫码信息及所述APP账号信息进行绑定操作。
在本申请的又一个实施例中，提供了一种服务端设备，包括：第一存储器以及第一处理器；
所述第一存储器，用于存储程序；
所述第一处理器，与所述第一存储器耦合，用于执行所述第一存储器中存储的所述程序，以用于：
获取第一短距离通信装置的信息；
根据所述第一短距离通信装置的信息与第一APP账号信息之间的绑定关系，确定用户身份；
用户身份合法时，根据与所述第一短距离通信装置的信息绑定的第一APP账号信息，确定用户权限。
在本申请的又一个实施例中，提供了一种执行端设备，包括：第二存储器以及第二处理器；
所述第二存储器，用于存储程序；
所述第二处理器，与所述第二存储器耦合，用于执行所述第二存储器中存储的所述程序，以用于：
读取短距离通信装置的信息；
网络正常时，将所述短距离通信装置的信息发送至APP服务端；
根据所述APP服务端反馈的鉴权结果，执行相应的逻辑操作；
其中，所述鉴权结果包括：用户身份及在用户身份合法时的用户权限；所述用户身份是根据所述短距离通信装置的信息与APP账号信息之间的绑定关系确定；所述用户权限是根据与所述短距离通信装置的信息绑定的APP账号信息确定。
在本申请的又一个实施例中，提供了一种客户端设备，包括第三存储器和第三处理器，其中，
所述第三存储器，用于存储程序；
所述第三处理器，与所述第三存储器耦合，用于执行所述第三存储器中存储的所述程序，以用于：
响应于用户触发的扫码请求，获取短距离通信装置上的扫码对象以识别扫码信息；
获取所述用户的APP账号信息；
将所述扫码信息及所述APP账号信息发送至APP服务端，以在所述APP服务端执行绑定操作。
在本申请的又一个实施例中，提供了一种客户端设备，包括第四存储器和第四处理器，其中，
所述第四存储器，用于存储程序；
所述第四处理器，与所述第四存储器耦合，用于执行所述第四存储器中存储的所述程序，以用于：
获取APP客户端上传的扫码信息及APP账号信息；
对所述扫码信息及所述APP账号信息进行绑定操作。
本申请实施例提供的技术方案，员工可使用APP(Application)应用实现短距离通信装置的信息与员工APP账号信息的绑定，APP应用平台可利用平台上的绑定信息及账号信息，简化了管理员的工作量，且在保证了鉴权准确性的前提下便捷性也得到了有效的提升。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请一实施例提供的基于APP应用的鉴权方法的流程示意图；
图2为本申请另一实施例提供的基于APP应用的鉴权方法的流程示意图；
图3为本申请又一实施例提供的基于APP应用的鉴权方法的流程示意图；
图4为本申请一实施例提供的基于APP应用的绑定方法的流程示意图；
图5为本申请另一实施例提供的基于APP应用的绑定方法的流程示意图；
图6为本申请又一实施例提供的基于APP应用的绑定方法的流程示意图；
图7为本申请实施例提供的基于APP应用的绑定方法中涉及的工牌的示例图；
图8为本申请实施例提供的基于APP应用的绑定方法中涉及的APP客户端的一个界面示意图；
图9为本申请实施例提供的基于APP应用的绑定方法中涉及的APP客户端的另一个界面示意图；
图10为本申请实施例提供的基于APP应用的绑定方法中涉及的APP客户端又一个界面示意图；
图11为本申请一实施例提供的基于APP应用的鉴权系统的结构示意图；
图12为本申请一实施例提供的基于APP应用的绑定系统的结构示意图；
图13为本申请一实施例提供的基于APP应用的鉴权装置的结构示意图；
图14为本申请一实施例提供的服务端设备的结构示意图；
图15为本申请另一实施例提供的服务端设备的结构示意图；
图16为本申请另一实施例提供的基于APP应用的鉴权装置的结构示意图；
图17为本申请一实施例提供的执行端设备的结构示意图；
图18为本申请一实施例提供的基于APP应用的绑定装置的结构示意图；
图19为本申请一实施例提供的客户端设备的结构示意图；
图20为本申请另一实施例提供的基于APP应用的绑定装置的结构示意图；
图21为本申请又一实施例提供的服务端设备的结构示意图。
具体实施方式
现有技术中，管理员需手动的刷每个员工的短距离通信装置(如工牌)，然后再人工将读入的短距离通信装置的信息与短距离通信装置所属员工的信息进行绑定，再为该员工配置相应的权限。数量较大时，管理员极易因为工作量大出现绑定和/或权限配置错误的问题。针对上述问题，本申请实施例提供了一种基于APP应用的鉴权方案，该方案无需管理员手动输入相关信息，简化了管理员的工作，且在保证鉴权的准确性的前提下便捷性也得到了有效的提升。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
图1示出了本申请一实施例提供的基于APP应用的鉴权方法的流程示意图。如图1所示，本实施例提供的所述方法包括：
101、获取第一短距离通信装置的信息。
102、根据所述第一短距离通信装置的信息与第一APP账号信息之间的绑定关系，确定用户身份。
103、用户身份合法时，根据与所述第一短距离通信装置的信息绑定的所述第一APP账号信息，确定用户权限。
这里需要说明的是：本实施例提供的所述方法的执行主体可以是APP服务端。具体实施时，APP可以直接选用现有的即时通信应用(Enterprise Instant Messaging，EIM)， 例如，“企业微信”等。APP服务端即该APP对应的应用平台，如常规服务器、云服务器、云主机、虚拟中心等。
上述101中，短距离通信装置可以是独立的短距离通信卡，或具有短距离通信功能的终端(如手机、穿戴设备等)，本申请实施例对此不作具体限定。执行端(如考勤设备、门禁设备等)将读取到第一短距离通信装置的信息发送至APP服务端。即本步骤的具体实现过程可以是：接收执行端发送的第一短距离通信装置的信息。
上述102中，可基于绑定信息来判定第一短距离通信装置的信息与第一APP账号信息之间的绑定关系。具体的，绑定信息内记录有具有绑定关系的短距离通信装置的信息及APP账号信息。用户可通过APP客户端上传的欲绑定的短距离通信装置的信息及APP账号信息，APP服务端即会对接收到的短距离通信装置的信息及APP账号信息进行绑定操作，以在绑定信息中关联的存储。例如，用户使用企业微信客户端完成短距离通信装置的信息与APP账号信息的绑定设置，企业微信客户端响应用户的绑定确认操作后，即向企业微信服务端发送绑定请求，企业微信服务端将接收到的短距离通信装置的信息与APP账号信息进行关联并存储在绑定信息中。
具体的，若所述第一短距离通信装置的信息与所述第一APP账号信息之间的绑定关系为已绑定，则确定用户身份合法；
若所述第一短距离通信装置的信息与所述第一APP账号信息之间的绑定关系为未绑定，则确定用户身份非法。
上述103中，所述第一APP账号信息除包含有登录名外，还可包含有用户属性信息，如工作团队信息、职务信息及所属权限组信息等中的一项或多项。这些属性信息，用户可在登录APP(比如企业微信)后进行编辑设置；用户设置完成后即被上传至APP服务端。当然，用户属性信息也可不包含在APP账号信息内，而作为一个独立的信息存储并与其对应的APP账号信息关联。具体的，上述103可包括：根据所述第一APP账号信息，获取用户属性信息；根据所述用户属性信息，确定所述用户权限。
不同工作团队对应不同的用户权限、或不同职务对应不同的用户权限、或不同权限组对应不同的用户权限等等；这些对应关系可预先设置。例如，在一可实施的示例中，建立用户属性信息与用户权限的对应关系；相应地，根据所述用户属性信息，确定所述用户权限可具体为：根据用户属性信息与用户权限的对应关系，查找所述用户属性信息对应的用户权限。
另外，用户权限可以是权限等级或其他，本申请实施例对此不作具体限定。
本申请实施例提供的技术方案，利用APP应用平台(即服务端或云端)对使用短距离通信装置的员工进行身份和权限的确定；由于APP应用平台上存储有员工上传的多种信息，比如，登录信息、绑定的工牌信息与用户信息、员工所属的工作组、职位等等。这些信息都可作为鉴权的依据，管理人员无需重复输入这些信息，简化了管理员的工作量，且在保证了鉴权的准确性的前提下便捷性也得到了有效的提升。
进一步的，上述实施例提供的所述方法还可包括如下步骤：
105、接收用户通过所述APP客户端发送的绑定请求，所述绑定请求中携带有欲绑定的第二短距离通信装置的信息及第二APP账号信息。
106、对所述第二短距离通信装置的信息及第二APP账号信息进行绑定操作。
上述106中，绑定过程可具体为：判断所述第二短距离通信装置的信息是否已与除所述第二APP账号信息以外的其他APP账号信息绑定；若否，则将所述第二短距离通信装置的信息与所述第二APP账号信息进行关联并存储在绑定信息中。
在一种可实现的技术方案中，上述实施例提供的技术方案还可包括：
107、接收用户通过所述APP客户端发送的解绑请求，所述解绑请求中携带有欲解绑的第三短距离通信装置的信息及第三APP账号信息。
108、对所述第三短距离通信装置的信息及所述第三APP账号信息进行解绑操作。
其中，解绑的过程可具体为：将绑定信息中记录的具有绑定关系的第三短距离通信装置的信息及第三APP账号信息删除。
这里需要说明的是：上述实施例提供的所述方法需要执行端与服务端之间的网络连接正常。执行端可通过网络向服务端发送信息，接收信息等等。但当执行端与服务端之间的网络连接异常(如断网)时，上述实施例提供的方法就无法正常执行，为此本申请实施例还提供了如下方法以让执行端缓存绑定信息和/或应用账号信息。
即在一种可实现的技术方案中，上述实施例提供的所述方法还可包括：
向执行端下发所述绑定信息，以使所述执行端将所述绑定信息缓存在本地，在网络异常时根据所述绑定信息对读取到的短距离通信装置的信息进行鉴权，并根据鉴权结果执行相应的逻辑操作；
其中，所述绑定信息记录有具有绑定关系的短距离通信装置的信息及APP账号信息，所述鉴权结果包括用户身份及用户身份合法时的用户权限。
图2示出了本申请又一实施例提供的基于APP应用的鉴权方法的流程示意图。如图 2所示，本实施例提供的所述方法包括：
201、读取短距离通信装置的信息。
202、网络正常时，将所述短距离通信装置的信息发送至APP服务端。
203、根据所述APP服务端反馈的鉴权结果，执行相应的逻辑操作。
其中，所述鉴权结果包括：用户身份及在用户身份为合法身份时的用户权限；所述用户身份是根据所述短距离通信装置的信息与APP账号信息之间的绑定关系确定；所述用户权限是根据与所述短距离通信装置的信息绑定的APP账号信息确定。
这里需要说明的是：本实施例提供的所述方法的执行主体可以是执行端。该执行端可以是一具体物理设备，如门禁设备、考勤设备；或者是一安装在终端设备上的应用程序，本申请实施例对此不作具体限定。
上述202中，网络正常时通过网络将工牌信息发送至APP服务端。APP服务端在接收到该短距离通信装置的信息后，即判定该短距离通信装置的信息是否与一APP账号信息具有绑定关系来确定用户身份，若用户身份合法，则根据与该短距离通信装置绑定的APP账号信息确定用户权限。
其中，用户权限的确定可参见上述实施例中的相关内容，此处不再赘述。
上述203的一种具体实现方式可具体为：若所述用户身份非法，则输出非法提示信息；若所述用户身份合法，且所述用户权限高于或等于预设权限等级，则执行考勤操作和/或控制门禁做出开门动作。
本申请实施例提供的技术方案，利用APP应用平台(即服务端或云端)对使用短距离通信装置的员工进行身份和权限的确定；由于APP应用平台上存储有员工上传的多种信息，比如，登录信息、绑定的工牌信息与用户信息、员工所属的工作组、职位等等。这些信息都可作为鉴权的依据，管理人员无需重复输入这些信息，简化了管理员的工作量，且在保证了鉴权的准确性的前提下便捷性也得到了有效的提升。
上述实施例提供的方法的实现前提是网络正常；当网络异常(断网)时，上述方法就无法执行。为此，本申请实施例提供的方法还包括如下步骤：
接收所述APP服务端下发的绑定信息；
将所述绑定信息缓存在本地。
其中，绑定信息记录有具有绑定关系的短距离通信装置的信息及APP账号信息。
增加上述步骤的目的就是在网络正常时，将绑定信息下发至执行端。网络异常是无法预测的，因此APP服务端可周期性的下发，比如，间隔N小时下发一次；或者，在绑 定信息有更新时，APP服务端即下发以同步执行端缓存的绑定信息。
有了上述技术的支持，相应的本实施例提供的方法在网络异常时，可采用如下方法来进行鉴权：
网络异常时，根据所述绑定信息对读取到的短距离通信装置的信息进行鉴权，并根据鉴权结果执行相应的逻辑操作。
其中，用户身份与用户权限的确定过程可参见上述各实施例中的相应内容，从此处不再赘述。
图3示出了本申请一实施例提供的基于APP应用的鉴权方法的流程示意图。本实施例代入了各步骤的执行主体。如图3所示，所述方法包括：
301、APP客户端响应于用户触发的读取操作，读取短距离通信装置的信息。
302、APP客户端获取用户的APP账号信息，并将APP账号信息及短距离通信装置的信息显示在绑定设置界面中。
303、APP客户端监听到绑定确认事件时，将APP账号信息及短距离通信装置的信息上传至APP服务端。
304、APP服务端判断所述短距离通信装置的信息是否已与除所述APP账号信息外的其他APP账号信息绑定，若否，则将所述短距离通信装置的信息及所述APP账号信息进行关联并存储在绑定信息中。
305、执行端设备读取短距离通信装置的信息。
306、执行端设备监测到网络正常时，将所述短距离通信装置的信息发送至APP服务端。
307、APP服务端判断所述短距离通信装置的信息是否与APP账号信息具有绑定关系；若是，则确定用户身份合法；否则确定用户身份非法。
308、APP服务端根据与短距离通信装置的信息绑定的所述APP账号信息确定用户权限。
309、APP服务端向执行端设备反馈鉴权结果。
其中，该鉴权结果包括用户身份以及在用户身份为合法身份时的用户权限。
310、若所述用户身份非法，则执行端输出非法提示信息；若所述用户身份合法，且所述用户权限高于或等于预设权限等级，则执行端执行考勤操作和/或控制门禁做出开门动作。
上述301中，用户可通过触控APP客户端界面上的控件来触发短距离通信装置的信息读取操作。例如，启动安装有APP客户端的终端设备的短距离通信(Near Field Communication，NFC)功能，以读取短距离通信装置的信息。或者，启动安装有APP客户端的终端设备的摄像头扫码二维码来获取短距离通信装置的信息。以企业微信(一种即时通信应用)及带有二维码信息的短距离通信装置为例，用户可在登录企业微信后进入客户端界面。该客户端界面上显示有扫码控件“扫一扫”；用户通过触控该“扫一扫”控件，即进入扫码界面，移动设备的摄像头被启动，并对处于扫码界面中的扫码区域内的扫码对象(如工牌上的二维码)进行采集并识别。
上述302中，APP账号信息可以是APP自动根据用户登录应用时的登录信息得到。当然，APP账号信息也可以是用户自行输入的。
对于用户自行输入的场景，本实施例提供的所述方法可具体为：在读取到短距离通信装置的信息后，显示包含有短距离通信装置的信息的绑定设置界面；该绑定设置界面中还显示有一用于提示用户填入信息的填充框；响应于用户针对所述填充框的触控操作，在所述绑定设置界面上显示编辑界面；用户可在所述显示编辑界面中编辑欲输入的APP账号信息。具体实施时，用户可通过键盘输入APP账号信息，或通过语音的方式输入APP账号信息，等等，本申请对具体输入方式不作具体限定。
对于APP账号信息自动确定的场景，本实施例提供的所述方法可具体为：根据用户登录应用时的登录信息得到所述APP账号信息，在对读取完短距离通信装置的信息后进入所述绑定设置界面，并在绑定设置界面中同时显示所述短距离通信装置的信息及所述APP账号信息。
基于上述内容可知，302中短距离通信装置的信息及APP账号信息可以是先后显示在绑定设置界面中，或者是同步显示在绑定设置界面中。具体实施时，上述显示短距离通信装置的信息及APP账号信息，可具体为：
在绑定设置界面中，显示短距离通信装置的信息、APP账号信息以及提示所述短距离通信装置的信息及所述APP账号信息具有绑定关系的页面元素；或者
在所述绑定设置界面的两关联显示区域内，分别显示短距离通信装置的信息及APP账号信息。
其中，显示提示所述短距离通信装置的信息及APP账号信息具有绑定关系的页面元素可以是，显示在绑定设置界面中具有提示作用的文字信息、图案信息、动画信息等等，本申请实施例对此不作具体限定。两关联显示区可以是两个具有相同设计元素(比如颜 色相同、尺寸形状相同等)的显示区，或是两个位置紧挨的显示区等等。这里进行关联地显示的目的是为了突出两个数据的关系，以让用户比较容易的注意到绑定信息然后进行确认。
上述303中，绑定确认事件可以是用户触控绑定设置界面上的确认控键触发的。上传的短距离通信装置的信息及APP账号信息可携带在绑定请求中发送至APP服务端；也可将所述短距离通信装置的信息及APP账号信息压缩打包后作为绑定文件上传至所述APP服务端。
进一步的，上述304之后，还可包括如下步骤：APP服务端在绑定操作执行完毕时，向客户端反馈有关所述短距离通信装置的信息及所述APP账号信息的绑定结果；APP客户端显示所述服务端反馈的绑定结果。
其中，绑定结果可以是在APP服务端执行绑定操作后自动反馈的，也可以是APP客户端在发送询问请求后APP服务端再反馈的。绑定结果可直接显示在绑定设置界面中，或以浮框的方式现实在绑定设置界面中，或显示在一新界面中。
上述305～310的各步骤的具体实现可参见上述实施例中的相应内容，此处不再赘述。
图4示出了本申请一实施例提供的基于APP应用的绑定方法的流程示意图。如图4所示，所述方法包括：
110、响应于用户触发的扫码请求，获取短距离通信装置上的扫码对象以识别扫码信息。
111、获取所述用户的APP账号信息。
112、将所述扫码信息及所述APP账号信息发送至APP服务端，以在所述APP服务端执行绑定操作。
上述110中其中，扫码对象可以是条形码、二维码等等，本申请对此不作具体限定。扫码对象的识别可参见现有技术中相应类型码对应的编解码算法来实现，本申请在此不再赘述。
具体实施时，用户可通过触控APP客户端界面上的扫码控件来触发该扫码请求。在一种可实现的技术方案中，本实施例提供的所述方法还可包括如下步骤：
显示APP客户端界面，所述APP客户端界面上包含有扫码控件；
响应于用户针对所述扫码控件的触控操作，生成所述扫码请求。
以企业微信为例，用户可在登录企业微信后进入企业微信界面。该企业微信界面上 显示有扫码控件“扫一扫”；用户通过触控该“扫一扫”控件，即进入扫码界面，企业微信客户端设备(如手机、平板电脑、穿戴设备等)的摄像头被启动，并对扫码界面中的扫码对象(如工牌上的二维码)进行采集并识别。
上述111中，APP账号信息即用户登录APP应用的信息，例如，可以包括但不限于：用户名、昵称、邮箱、手机号等中的一种或多种。
上述112中，所述扫码信息及所述APP账号信息，可在APP客户端监听到用户绑定确认事件后被触发发送至APP服务端。其中，用户绑定确认事件可以是用户发出的确认语音，也可以是用户触控确认控件的操作等等，本申请实施例对此对不作具体限定。
在一种可实现的技术方案中，本申请实施例提供的基于APP应用的绑定方法还可包括：
扫码成功后，跳转至显示有所述扫码信息及所述APP账号信息的绑定设置界面。
相应地，用户即可通过绑定设置界面上的确认控件来触发绑定确认事件。即，上述将所述扫码信息及所述APP账号信息发送至APP服务端，以在所述APP服务端执行绑定操作，可具体为：
响应于用户通过所述绑定设置界面触发的绑定确认事件，将所述扫码信息及所述APP账号信息发送至APP服务端。
本申请实施例提供了一种由员工主动上传绑定信息的方案，简化了管理员的工作；此外，由员工自主上传绑定信息并自主确认其准确性，能有效的降低绑定信息出错的概率。
进一步的，上述实施例提供的技术方案还可包括如下步骤：
113、显示所述服务端反馈的绑定结果。
其中，绑定结果可以是在APP服务端执行绑定操作后自动反馈的，也可以是APP客户端在发送询问请求后APP服务端再反馈的。绑定结果可直接显示在绑定设置界面中，或以浮框的方式现实在绑定设置界面中，或显示在一新界面中。
进一步的，上述实施例提供的基于APP应用的绑定方法还可包括解绑步骤。例如，还包括：
响应于用户的解绑请求，获取欲解绑的扫码信息和APP账号信息；
将欲解绑的扫码信息及APP账号信息发送至APP服务端，以在所述APP服务端执行解绑操作。
图5示出了本申请另一实施例提供的基于APP应用的绑定方法的流程示意图。如图5所示，所述方法包括：
210、获取APP客户端上传的扫码信息及APP账号信息。
211、对所述扫码信息及所述APP账号信息进行绑定操作。
上述210中，扫码信息及APP账号信息可从APP客户端上传的绑定请求中获取，也可以通过解压APP客户端上传的绑定数据包得到。其中，扫码信息可以是APP客户端通过启动客户端设备上的摄像头采集并识别得到。
上述211中，绑定操作之前，需判断扫码信息是否为未绑定信息，即判断是否已有除所述APP账号信息以外的APP账号信息绑定。具体的，在一种可实现的技术方案中，上述211可具体包括：
判断所述扫码信息是否已与除所述APP账号信息以外的其他APP账号信息绑定；
若否，则将所述扫码信息及所述APP账号信息进行关联并存储在绑定信息中。
进一步的，上述211还可包括：若是，则反馈绑定失败提示结果。
进一步的，将所述扫码信息及所述APP账号信息绑定成功后，也可向客户端反馈绑定成功提示结果。即，上述实施例提供的所述方法还可包括：
绑定操作执行完毕时，向所述APP客户端反馈有关所述扫码信息及所述APP账号信息的绑定结果。
其中，绑定结果为上述绑定失败提示结果或绑定成功提示结果。
这里需要说明的是：APP服务端可在绑定操作执行完毕后自动的向客户端反馈绑定结果，也可在接收APP客户端发送询问请求后再反馈，对此本申请实施例不作具体限定。
进一步的，上述实施例提供的所述方法还可包括：
接收APP客户端发送的欲解绑的扫码信息及APP账号信息；
对欲解绑的扫码信息及APP账号信息进行解绑操作。
本申请实施例提供了一种由员工主动上传绑定信息的方案，简化了管理员的工作；此外，由员工自主上传绑定信息并自主确认其准确性，能有效的降低绑定信息出错率，提高绑定信息的导入效率。
图6示出了本申请又一实施例提供的基于APP应用的绑定方法的流程示意图。如图6所示，绑定过程如下：
310、APP客户端响应于用户触发的扫码请求，获取短距离通信装置上的扫码对象以 识别扫码信息。
311、APP客户端获取所述用户的APP账号信息。
312、APP客户端将所述扫码信息及所述APP账号信息发送至APP服务端。
313、APP服务端判断所述扫码信息是否已与除所述APP账号信息以外的其他APP账号信息绑定；若否，则将所述扫码信息及所述APP账号信息进行关联并存储在绑定信息中，否则，绑定失败。
314、向所述APP客户端反馈有关所述扫码信息及所述APP账号信息的绑定结果。
上述310～314的各步骤的具体实现可参见上述实施例中的相应内容，此处不再赘述。
本申请实施例提供了一种由员工主动上传绑定信息的方案，简化了管理员的工作；此外，由员工自主上传绑定信息并自主确认其准确性，能有效的降低绑定信息出错率，提高绑定信息的导入效率。
下面以二维码工牌为例，对本申请实施例提供的基于APP应用的绑定鉴权方法进行说明。本示例中APP应用为企业微信，员工工牌为二维码工牌(如图7所示)；执行端为门禁设备。
如图8所示，员工可通过企业微信界面上显示的“扫一扫”控件，对二维码工牌进行扫码操作，以读取扫码信息(即工牌的信息)。读取完成后，如图9所示，从扫码页面跳转至绑定设置界面；用户可在绑定设置界面中填写APP账号信息，或者企业微信直接将当前登录的APP账号信息显示在绑定设置界面中。用户通过触控绑定设置界面上的“提交”控件触发绑定确认事件。企业微信客户端响应于该绑定确认事件，将工牌的信息和APP账号信息上传至企业微信服务端。企业微信服务端对扫码信息和APP账号信息进行绑定操作，并反馈绑定结果(如图10所示的绑定成功的提示信息)。
员工将工牌放置在门禁设备的扫码区域内，门禁设备通过扫码操作读取到工牌的信息后，门禁设备将该工牌的信息上传至企业微信服务端，企业微信服务端查询绑定信息中该工牌的信息与APP账号信息之间的绑定关系；若该工牌的信息与APP账号之间的绑定关系为已绑定，则确定用户身份为合法身份；否则，确定用户身份非法。若用户身份合法，则企业微信服务端基于其自身存储的账号信息，获取该员工的用户属性信息(如所在工作团队、职务信息、所属权限组等等)，根据所述用户属性信息确定用户权限。企业微信服务端将鉴权结果反馈至门禁设备。若鉴权结果为身份非法，则门禁设备采用语音、文本或视频的方式输出非法提示信息。若鉴权结果为身份合法，且用户权限高于或等于门禁设备预设的权限等级，则门禁设备做出开门动作。
在本申请的说明书、权利要求书及上述附图中描述的一些流程中，包含了按照特定顺序出现的多个操作，这些操作可以不按照其在本文中出现的顺序来执行或并行执行。操作的序号如101、102等，仅仅是用于区分各个不同的操作，序号本身不代表任何的执行顺序。另外，这些流程可以包括更多或更少的操作，并且这些操作可以按顺序执行或并行执行。需要说明的是，本文中的“第一”、“第二”等描述，是用于区分不同的消息、设备、模块等，不代表先后顺序，也不限定“第一”和“第二”是不同的类型。
图11示出了本申请一实施例提供的基于APP应用的鉴权系统的结构示意图。如图11所示，本实施例提供的系统包括：
第一APP服务端401及第一执行端402。其中，第一APP服务端401用于获取第一短距离通信装置的信息；根据所述第一短距离通信装置的信息与第一APP账号信息之间的绑定关系，确定用户身份；所述用户身份合法时，根据与所述第一短距离通信装置的信息绑定的所述第一APP账号信息，确定用户权限；
第一执行端402用于读取所述第一短距离通信装置的信息；网络正常时将所述第一短距离通信装置的信息发送至所述第一APP服务端401；根据所述第一APP服务端401反馈的鉴权结果，执行相应的逻辑操作；
其中，所述鉴权结果包括：所述用户身份以及在所述用户身份合法时的所述用户权限。
进一步的，如图11所示，上述系统还包括：第一APP客户端403。第一APP客户端403用于向所述第一APP服务端401发送绑定请求，所述绑定请求中携带有欲绑定的第二短距离通信装置的信息及第二APP账号信息；所述第一APP服务端401还用于对所述述第二短距离通信装置的信息及第二APP账号信息进行绑定操作。
进一步的，上述系统中所述第一APP客户端403，还用于向所述APP服务端发送解绑请求，所述解绑请求中携带有欲解绑的第三短距离通信装置的信息及第三APP账号信息；所述第一APP服务端401，还用于对所述第三短距离通信装置的信息及第三APP账号信息进行解绑操作。
这里需要说明的是：上述第一APP客户端403与第一执行端402可以是同一应用软件或同一硬件实体，也可以是安装在不同硬件设备上的应用软件、也可以是两个不同的硬件设备，还可以是安装在同一硬件设备上的不同的两个应用软件，对此本申请实施例不作具体限定。第一APP服务端401可以是常规服务器、云端、虚拟中心等，本申请实施例对此不作具体限定。
这里需要说明的是：上述实施例提供的基于APP应用的鉴权系统可实现上述图3所示方法实施例中描述的技术方案，上述各模块或单元具体实现的原理可参见上述各方法实施例中的相应内容，此处不再赘述。
本申请实施例提供的技术方案，利用APP应用平台(即服务端或云端)对使用短距离通信装置(如工牌)的员工进行身份和权限的确定；由于APP应用平台上存储有员工上传的多种信息，比如，登录信息、绑定的工牌信息与用户信息、员工所属的工作组、职位等等。这些信息都可作为鉴权的依据，管理人员无需重复输入这些信息，简化了管理员的工作量，且在保证了鉴权的准确性的前提下便捷性也得到了有效的提升。
图12示出了本申请一实施例提供的基于APP应用的绑定系统的结构示意图。如图12所示，所述基于APP应用的绑定系统包括：第二APP客户端411及第二APP服务端412。其中，所述第二APP客户端411用于响应于用户触发的扫码请求，获取短距离通信装置上的扫码对象以识别扫码信息；获取所述用户的APP账号信息；将所述扫码信息及所述APP账号信息上传。第二APP服务端412用于获取APP客户端上传的扫码信息及APP账号信息；对所述扫码信息及所述APP账号信息进行绑定操作。
这里需要说明的是：上述实施例提供的基于APP应用的绑定系统中APP客户端及APP服务端可分别实现上述图4和图5所示方法实施例中描述的技术方案，具体实现的原理可参见上述各方法实施例中的相应内容，此处不再赘述。
第二APP服务端412可以是常规服务器、云端、虚拟中心等；上述第二APP客户端411可以是应用软件(如企业微信)或硬件实体等，本申请实施例对此不作具体限定。
本申请实施例提供了一种由员工主动上传绑定信息的方案，简化了管理员的工作；此外，由员工自主上传绑定信息并自主确认其准确性，能有效的降低绑定信息出错率，提高绑定信息的导入效率。
图13示出了本申请一实施例提供的基于APP应用的鉴权装置的结构示意图。如图13所示，所述信息绑定装置包括：第一获取模块501、第一确定模块502及第二确定模块503。其中，第一获取模块501用于获取第一短距离通信装置的信息；第一确定模块502用于根据所述第一短距离通信装置的信息与第一APP账号信息之间的绑定关系，确定用户身份；第二确定模块503用于用户身份合法时，根据与所述第一短距离通信装置的信息绑定的所述第一APP账号信息，确定用户权限。
进一步的，所述第一确定模块502还用于：若所述第一短距离通信装置的信息与所述第一APP账号信息之间的绑定关系为已绑定，则确定用户身份合法；若所述第一短距 离通信装置的信息与所述第一APP账号信息之间的绑定关系为未绑定，则确定用户身份非法。
进一步的，所述第二确定模块503还用于根据所述第一APP账号信息，获取用户属性信息；根据所述用户属性信息，确定所述用户权限。
进一步的，所述用户属性信息包括：工作团队信息、职务信息及所属权限组信息中的一项或多项。
进一步的，上述基于APP应用的鉴权装置还可包括：第一接收模块及绑定模块。其中，所述第一接收模块，用于接收用户通过所述APP客户端发送的绑定请求，所述绑定请求中携带有欲绑定的第二短距离通信装置的信息及第二APP账号信息；绑定模块用于对所述第二短距离通信装置的信息及所述第二APP账号信息进行绑定操作。
进一步的，所述绑定模块还用于判断所述第二短距离通信装置的信息是否已与除所述第二APP账号信息以外的其他APP账号信息绑定；若否，则将所述第二短距离通信装置的信息与所述第二APP账号信息进行关联并存储在绑定信息中。
进一步的，上述基于APP应用的鉴权装置还可包括：第二接收模块及解绑模块。其中，第二接收模块，用于接收用户通过所述APP客户端发送的解绑请求，所述解绑请求中携带有欲解绑的第三短距离通信装置的信息及第三APP账号信息；解绑模块用于对所述第三短距离通信装置的信息及所述第三APP账号信息进行解绑操作。
进一步的，上述基于APP应用的鉴权装置还包括：下发模块。所述下发模块用于向执行端下发绑定信息，以使所述执行端将所述绑定信息缓存在本地，在网络异常时根据所述绑定信息对读取到的短距离通信装置的信息进行鉴权，并根据鉴权结果执行相应的逻辑操作；其中，所述绑定信息记录有具有绑定关系的短距离通信装置的信息及APP账号信息，所述鉴权结果包括用户身份及用户身份合法时的用户权限。
这里需要说明的是：上述实施例提供的基于APP应用的鉴权装置可实现上述图1所示方法实施例中描述的技术方案，上述各模块或单元具体实现的原理可参见上述方法实施例中的相应内容，此处不再赘述。
本申请实施例提供的技术方案，利用APP应用平台(即服务端或云端)对使用短距离通信装置的员工进行身份和权限的确定；由于APP应用平台上存储有员工上传的多种信息，比如，登录信息、绑定的工牌信息与用户信息、员工所属的工作组、职位等等。这些信息都可作为鉴权的依据，管理人员无需重复输入这些信息，简化了管理员的工作量，且在保证了鉴权的准确性的前提下便捷性也得到了有效的提升。
图14为本申请一实施例提供的服务端设备的结构示意图。该服务端设备包括：第一存储器601以及第一处理器602。第一存储器601可被配置为存储其它各种数据以支持在服务端设备上的操作。这些数据的示例包括用于在服务端设备上操作的任何应用程序或方法的指令。第一存储器601可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
第一处理器602与第一存储器601耦合，用于执行第一存储器601中存储的程序，以用于：
获取第一短距离通信装置的信息；
根据所述第一短距离通信装置的信息与第一APP账号信息之间的绑定关系，确定用户身份；
用户身份合法时，根据与所述第一短距离通信装置的信息绑定的所述第一APP账号信息，确定用户权限。
其中，第一处理器602在执行第一存储器601中的程序时，除了上面的功能之外，还可实现其它功能，具体可参见前面各实施例的描述。
进一步，如图15所示，服务端设备还包括：第一通信组件603、第一显示器604、第一电源组件605、第一音频组件606等其它组件。图15中仅示意性给出部分组件，并不意味着电子设备只包括图15所示组件。
相应地，本申请实施例还提供一种存储有计算机程序的计算机可读存储介质，所述计算机程序被计算机执行时能够实现上述各实施例提供的云端虚拟机创建方法步骤或功能。
图16示出了本申请另一实施例提供的基于APP应用的鉴权装置的结构示意图。如图16所示，所述基于APP应用的鉴权装置包括：读取模块701、发送模块702及执行模块703。其中，读取模块701用于短距离通信装置的信息；发送模块702用于在网络正常时，将所述短距离通信装置的信息发送至APP服务端；执行模块703用于根据所述APP服务端反馈的鉴权结果，执行相应的逻辑操作；其中，所述鉴权结果包括：用户身份及在用户身份为合法身份时的用户权限；所述用户身份是根据所述短距离通信装置的信息与APP账号信息之间的绑定关系确定；所述用户权限是根据与所述短距离通信装置的信息绑定的APP账号信息确定。
进一步的，上述基于APP应用的鉴权装置还可包括：第三接收模块及存储模块。其中，第三接收模块，用于接收所述APP服务端下发的绑定信息；存储模块，用于将所述绑定信息缓存在本地。
再进一步的，上述基于APP应用的鉴权装置还可包括：
第三确定模块用于在网络异常时，根据所述绑定信息对所述短距离通信装置的信息进行鉴权，并根据鉴权结果执行相应的逻辑操作。
进一步的，所述执行模块703还用于若所述用户身份非法，则输出非法提示信息；若所述用户身份合法，且所述用户权限高于或等于预设权限等级，则执行考勤操作和/或控制门禁做出开门动作。
这里需要说明的是：上述实施例提供的基于APP应用的鉴权装置可实现上述图2所示方法实施例中描述的技术方案，上述各模块或单元具体实现的原理可参见上述各方法实施例中的相应内容，此处不再赘述。
本申请实施例提供的技术方案，利用APP应用平台(即服务端或云端)对使用短距离通信装置的员工进行身份和权限的确定；由于APP应用平台上存储有员工上传的多种信息，比如，登录信息、绑定的工牌信息与用户信息、员工所属的工作组、职位等等。这些信息都可作为鉴权的依据，管理人员无需重复输入这些信息，简化了管理员的工作量，且在保证了鉴权的准确性的前提下便捷性也得到了有效的提升。
图17为本申请一实施例提供的执行端设备的结构示意图。该执行端设备包括：第二存储器801以及第二处理器802。第二存储器801可被配置为存储其它各种数据以支持在执行端设备上的操作。这些数据的示例包括用于在执行端设备上操作的任何应用程序或方法的指令。第二存储器801可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
第二处理器802与第二存储器801耦合，用于执行第二存储器801中存储的程序，以用于：
读取短距离通信装置的信息；
网络正常时，将所述短距离通信装置的信息发送至APP服务端；
根据所述APP服务端反馈的鉴权结果，执行相应的逻辑操作；
其中，所述鉴权结果包括：用户身份及在用户身份合法时的用户权限；所述用户身 份是根据所述短距离通信装置的信息与APP账号信息之间的绑定关系确定；所述用户权限是根据与所述短距离通信装置的信息绑定的所述APP账号信息确定。
其中，第二处理器802在执行第二存储器801中的程序时，除了上面的功能之外，还可实现其它功能，具体可参见前面各实施例的描述。
进一步，执行端设备还包括：第二通信组件、第二显示器、第三电源组件、第三音频组件等其它组件。
相应地，本申请实施例还提供一种存储有计算机程序的计算机可读存储介质，所述计算机程序被计算机执行时能够实现上述各实施例提供的云端虚拟机创建方法步骤或功能。
图18为本申请一实施例提供的基于APP应用的绑定装置的结构示意图。如图所示，所述装置包括：
第二获取模块511用于响应于用户触发的扫码请求，获取短距离通信装置上的扫码对象以识别扫码信息；
第三获取模块512用于获取所述用户的APP账号信息；
发送模块513用于将所述扫码信息及所述APP账号信息发送至APP服务端，以在所述APP服务端执行绑定操作。
进一步的，所述装置还可包括：
显示模块，用于扫码成功后，跳转至显示有所述扫码信息及所述APP账号信息的绑定设置界面；以及
所述发送模块513还用于响应于用户通过所述绑定设置界面触发的绑定确认事件，将所述扫码信息及所述APP账号信息发送至APP服务端。
进一步的，所述显示模块，还用于显示所述服务端反馈的绑定结果。
进一步的，所述第三获取模块512，还用于响应于用户的解绑请求，获取欲解绑的扫码信息和APP账号信息；
所述发送模块513还用于将欲解绑的扫码信息及APP账号信息发送至APP服务端，以在所述APP服务端执行解绑操作。
这里需要说明的是：上述实施例提供的基于APP应用的绑定装置可实现上述图4所示方法实施例中描述的技术方案，上述各模块或单元具体实现的原理可参见上述各方法实施例中的相应内容，此处不再赘述。
本申请实施例提供了一种由员工主动上传绑定信息的方案，简化了管理员的工作；此外，由员工自主上传绑定信息并自主确认其准确性，能有效的降低绑定信息出错率，提高绑定信息的导入效率。
图19为本申请一实施例提供的客户端设备的结构示意图。该客户端设备包括：第三存储器811以及第三处理器812。第三存储器811可被配置为存储其它各种数据以支持在客户端设备上的操作。这些数据的示例包括用于在客户端设备上操作的任何应用程序或方法的指令。第三存储器811可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
第三处理器812与第三存储器811耦合，用于执行第三存储器811中存储的程序，以用于：
响应于用户触发的扫码请求，获取短距离通信装置上的扫码对象以识别扫码信息；
获取所述用户的APP账号信息；
将所述扫码信息及所述APP账号信息发送至APP服务端，以在所述APP服务端执行绑定操作。
其中，第三处理器812在执行第三存储器811中的程序时，除了上面的功能之外，还可实现其它功能，具体可参见前面各实施例的描述。
进一步，执行端设备还包括：第三通信组件、第三显示器、第三电源组件、第三频组件等其它组件。
相应地，本申请实施例还提供一种存储有计算机程序的计算机可读存储介质，所述计算机程序被计算机执行时能够实现上述各实施例提供的云端虚拟机创建方法步骤或功能。
图20示出了本申请另一实施例提供的基于APP应用的绑定装置。如图20所示，所述装置包括：
第四获取模块522用于获取APP客户端上传的扫码信息及APP账号信息；
绑定模块523用于对所述扫码信息及所述APP账号信息进行绑定操作。
进一步的，所述绑定模块523还用于：
判断所述扫码信息是否已与除所述APP账号信息以外的其他APP账号信息绑定；
若否，则将所述扫码信息及所述APP账号信息进行关联并存储在绑定信息中。
这里需要说明的是：上述实施例提供的基于APP应用的绑定装置可实现上述图5所示方法实施例中描述的技术方案，上述各模块或单元具体实现的原理可参见上述各方法实施例中的相应内容，此处不再赘述。
本申请实施例提供了一种由员工主动上传绑定信息的方案，简化了管理员的工作；此外，由员工自主上传绑定信息并自主确认其准确性，能有效的降低绑定信息出错率，提高绑定信息的导入效率。
图21为本申请一实施例提供的服务端设备的结构示意图。该服务端设备包括：第四存储器611以及第四处理器612。第四存储器611可被配置为存储其它各种数据以支持在服务端设备上的操作。这些数据的示例包括用于在服务端设备上操作的任何应用程序或方法的指令。第四存储器611可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
第四处理器612与第四存储器611耦合，用于执行第四存储器611中存储的程序，以用于：
获取APP客户端上传的扫码信息及APP账号信息；
对所述扫码信息及所述APP账号信息进行绑定操作。
其中，第四处理器612在执行第四存储器611中的程序时，除了上面的功能之外，还可实现其它功能，具体可参见前面各实施例的描述。
进一步，服务端设备还包括：第四通信组件、第四显示器、第四电源组件、第四音频组件等其它组件。
相应地，本申请实施例还提供一种存储有计算机程序的计算机可读存储介质，所述计算机程序被计算机执行时能够实现上述各实施例提供的云端虚拟机创建方法步骤或功能。
以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性的劳动的情况下，即可以理解并实施。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到各实施方式可借 助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件。基于这样的理解，上述技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行各个实施例或者实施例的某些部分所述的方法。
最后应说明的是：以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (25)

  1. 一种基于APP应用的鉴权方法，其特征在于，包括：
    获取第一短距离通信装置的信息；
    根据所述第一短距离通信装置的信息与第一APP账号信息之间的绑定关系，确定用户身份；
    用户身份合法时，根据与所述第一短距离通信装置的信息绑定的所述第一APP账号信息，确定用户权限。
  2. 根据权利要求1所述的方法，其特征在于，根据所述第一短距离通信装置的信息及第一APP账号信息之间的绑定关系，确定用户身份，包括：
    若所述第一短距离通信装置的信息与所述第一APP账号信息之间的绑定关系为已绑定，则确定用户身份合法；
    若所述第一短距离通信装置的信息与所述第一APP账号信息之间的绑定关系为未绑定，则确定用户身份非法。
  3. 根据权利要求1所述的方法，其特征在于，根据与所述第一短距离通信装置的信息绑定的所述第一APP账号信息，确定用户权限，包括：
    根据所述第一APP账号信息，获取用户属性信息；
    根据所述用户属性信息，确定所述用户权限。
  4. 根据权利要求3所述的方法，其特征在于，所述用户属性信息包括：工作团队信息、职务信息及所属权限组信息中的一项或多项。
  5. 根据权利要求1至4任一项所述的方法，其特征在于，还包括：
    接收用户通过所述APP客户端发送的绑定请求，所述绑定请求中携带有欲绑定的第二短距离通信装置的信息及第二APP账号信息；
    对所述第二短距离通信装置的信息及所述第二APP账号信息进行绑定操作。
  6. 根据权利要求5所述的方法，其特征在于对所述第二短距离通信装置的信息及所述第二APP账号信息进行绑定操作，包括：
    判断所述第二短距离通信装置的信息是否已与除所述第二APP账号信息以外的其他APP账号信息绑定；
    若否，则将所述第二短距离通信装置的信息与所述第二APP账号信息进行关联并存储在绑定信息中。
  7. 根据权利要求1至4中任一项所述的方法，其特征在于，还包括：
    接收用户通过所述APP客户端发送的解绑请求，所述解绑请求中携带有欲解绑的第三短距离通信装置的信息及第三APP账号信息；
    对所述第三短距离通信装置的信息及所述第三APP账号信息进行解绑操作。
  8. 根据权利要求1至4中任一项所述的方法，其特征在于，还包括：
    向执行端下发绑定信息，以使所述执行端将所述绑定信息缓存在本地，在网络异常时根据所述绑定信息对读取到的短距离通信装置的信息进行鉴权，并根据鉴权结果执行相应的操作；
    其中，所述绑定信息记录有具有绑定关系的短距离通信装置的信息及APP账号信息，所述鉴权结果包括用户身份及用户身份合法时的用户权限。
  9. 一种基于APP应用的鉴权方法，其特征在于，包括：
    读取短距离通信装置的信息；
    网络正常时，将所述短距离通信装置的信息发送至APP服务端；
    根据所述APP服务端反馈的鉴权结果，执行相应的逻辑操作；
    其中，所述鉴权结果包括：用户身份及在用户身份合法时的用户权限；所述用户身份根据所述短距离通信装置的信息与APP账号信息之间的绑定关系确定；所述用户权限根据与所述短距离通信装置的信息绑定的APP账号信息确定。
  10. 根据权利要求9所述的方法，其特征在于，还包括：
    接收所述APP服务端下发的绑定信息；
    将所述绑定信息缓存在本地；
    其中，所述绑定信息记录有具有绑定关系的短距离通信装置的信息及APP账号信息。
  11. 根据权利要求10所述的方法，其特征在于，还包括：
    网络异常时，根据所述绑定信息对所述短距离通信装置的信息进行鉴权，并根据鉴权结果执行相应的逻辑操作。
  12. 根据权利要求9至11任一项所述的方法，其特征在于，根据所述APP服务端反馈的鉴权结果，执行相应的逻辑操作，包括：
    若所述用户身份非法，则输出非法提示信息；
    若所述用户身份合法，且所述用户权限高于或等于预设权限等级，则执行考勤操作和/或控制门禁做出开门动作。
  13. 一种基于APP应用的鉴权系统，其特征在于，包括：
    第一APP服务端，用于获取第一短距离通信装置的信息；根据所述第一短距离通信装置的信息与第一APP账号信息之间的绑定关系，确定用户身份；所述用户身份合法时，根据与所述第一短距离通信装置的信息绑定的所述第一APP账号信息，确定用户权限；
    执行端，用于读取所述第一短距离通信装置的信息；网络正常时将所述第一短距离通信装置的信息发送至所述第一APP服务端；根据所述第一APP服务端反馈的鉴权结果，执行相应的逻辑操作；
    其中，所述鉴权结果包括：所述用户身份以及在所述用户身份合法时的所述用户权限。
  14. 根据权利要求13所述的系统，其特征在于，还包括：
    第一APP客户端，用于向所述第一APP服务端发送绑定请求，所述绑定请求中携带有欲绑定的第二短距离通信装置的信息及第二APP账号信息；
    所述第一APP服务端，还用于对所述第二短距离通信装置的信息及第二APP账号信息进行绑定操作。
  15. 根据权利要求14所述的系统，其特征在于，还包括：
    所述第一APP客户端，还用于向所述APP服务端发送解绑请求，所述解绑请求中携带有欲解绑的第三短距离通信装置的信息及第三APP账号信息；
    所述第一APP服务端，还用于对所述第三短距离通信装置的信息及第三APP账号信息进行解绑操作。
  16. 一种基于APP应用的绑定方法，其特征在于，包括：
    响应于用户触发的扫码请求，获取短距离通信装置上的扫码对象以识别扫码信息；
    获取所述用户的APP账号信息；
    将所述扫码信息及所述APP账号信息发送至APP服务端，以在所述APP服务端执行绑定操作。
  17. 根据权利要求16所述的方法，其特征在于，还包括：
    扫码成功后，跳转至显示有所述扫码信息及所述APP账号信息的绑定设置界面；以及
    将所述扫码信息及所述APP账号信息发送至APP服务端，包括：
    响应于用户通过所述绑定设置界面触发的绑定确认事件，将所述扫码信息及所述APP账号信息发送至APP服务端。
  18. 根据权利要求17所述的方法，其特征在于，还包括：
    显示所述服务端反馈的绑定结果。
  19. 一种基于APP应用的绑定方法，其特征在于，包括：
    获取APP客户端上传的扫码信息及APP账号信息；
    对所述扫码信息及所述APP账号信息进行绑定操作。
  20. 根据权利要求19所述的方法，其特征在于，对所述扫码信息及所述APP账号信息进行绑定操作，包括：
    判断所述扫码信息是否已与除所述APP账号信息以外的其他APP账号信息绑定；
    若否，则将所述扫码信息及所述APP账号信息进行关联并存储在绑定信息中。
  21. 一种基于APP应用的绑定系统，其特征在于，包括：
    第二APP客户端，用于响应于用户触发的扫码请求，获取短距离通信装置上的扫码对象以识别扫码信息；获取所述用户的APP账号信息；将所述扫码信息及所述APP账号信息上传；
    第二APP服务端，用于获取所述第二APP客户端上传的所述扫码信息及所述APP账号信息；对所述扫码信息及所述APP账号信息进行绑定操作。
  22. 一种服务端设备，其特征在于，包括第一存储器和第一处理器，其中，
    所述第一存储器，用于存储程序；
    所述第一处理器，与所述第一存储器耦合，用于执行所述第一存储器中存储的所述程序，以用于：
    获取第一短距离通信装置的信息；
    根据所述第一短距离通信装置的信息与第一APP账号信息之间的绑定关系，确定用户身份；
    用户身份合法时，根据与所述第一短距离通信装置的信息绑定的所述第一APP账号信息，确定用户权限。
  23. 一种执行端设备，其特征在于，包括第二存储器和第二处理器，其中，
    所述第二存储器，用于存储程序；
    所述第二处理器，与所述第二存储器耦合，用于执行所述第二存储器中存储的所述程序，以用于：
    读取短距离通信装置的信息；
    网络正常时，将所述短距离通信装置的信息发送至APP服务端；
    根据所述APP服务端反馈的鉴权结果，执行相应的逻辑操作；
    其中，所述鉴权结果包括：用户身份及在用户身份合法时的用户权限；所述用户身份是根据所述短距离通信装置的信息与APP账号信息之间的绑定关系确定；所述用户权限是根据与所述短距离通信装置的信息绑定的APP账号信息确定。
  24. 一种客户端设备，其特征在于，包括第三存储器和第三处理器，其中，
    所述第三存储器，用于存储程序；
    所述第三处理器，与所述第三存储器耦合，用于执行所述第三存储器中存储的所述程序，以用于：
    响应于用户触发的扫码请求，获取短距离通信装置上的扫码对象以识别扫码信息；
    获取所述用户的APP账号信息；
    将所述扫码信息及所述APP账号信息发送至APP服务端，以在所述APP服务端执行绑定操作。
  25. 一种客户端设备，其特征在于，包括第四存储器和第四处理器，其中，
    所述第四存储器，用于存储程序；
    所述第四处理器，与所述第四存储器耦合，用于执行所述第四存储器中存储的所述程序，以用于：
    获取APP客户端上传的扫码信息及APP账号信息；
    对所述扫码信息及所述APP账号信息进行绑定操作。
PCT/CN2018/107228 2017-09-30 2018-09-25 基于app应用的鉴权方法、绑定方法、系统及设备 WO2019062687A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710944518.4 2017-09-30
CN201710944518.4A CN109600734A (zh) 2017-09-30 2017-09-30 基于app应用的鉴权方法、绑定方法、系统及设备

Publications (1)

Publication Number Publication Date
WO2019062687A1 true WO2019062687A1 (zh) 2019-04-04

Family

ID=65900567

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/107228 WO2019062687A1 (zh) 2017-09-30 2018-09-25 基于app应用的鉴权方法、绑定方法、系统及设备

Country Status (2)

Country Link
CN (1) CN109600734A (zh)
WO (1) WO2019062687A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111538596A (zh) * 2020-04-23 2020-08-14 北京字节跳动网络技术有限公司 一种资源处理的方法、装置、计算机设备及存储介质
WO2021017208A1 (zh) * 2019-07-30 2021-02-04 广东美的制冷设备有限公司 设备绑定方法、装置和电子设备
CN113792285A (zh) * 2021-08-05 2021-12-14 广东核电合营有限公司 一种核电站业务权限控制方法、装置及终端设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103188238A (zh) * 2011-12-30 2013-07-03 上海博泰悦臻电子设备制造有限公司 支付账号的激活方法及系统
US20130179352A1 (en) * 2011-03-12 2013-07-11 Mocapay, Inc. Secure wireless transactions when a wireless network is unavailable
CN105577607A (zh) * 2014-10-08 2016-05-11 腾讯科技（深圳）有限公司 用户身份鉴权方法及装置
CN105610796A (zh) * 2015-12-17 2016-05-25 深圳市屹石科技股份有限公司 转移用户身份识别信息的方法、服务器及系统
CN105791268A (zh) * 2016-02-17 2016-07-20 深圳市屹石科技股份有限公司 服务器、健身设备用户登录方法及用户登录方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103150800A (zh) * 2013-03-22 2013-06-12 李凯 在门禁系统中添加权限设备
CN104143056A (zh) * 2013-12-31 2014-11-12 腾讯科技（深圳）有限公司 身份验证方法及系统
CN106981107A (zh) * 2016-01-19 2017-07-25 福建省光速达物联网科技股份有限公司 蓝牙门禁的手机开锁方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130179352A1 (en) * 2011-03-12 2013-07-11 Mocapay, Inc. Secure wireless transactions when a wireless network is unavailable
CN103188238A (zh) * 2011-12-30 2013-07-03 上海博泰悦臻电子设备制造有限公司 支付账号的激活方法及系统
CN105577607A (zh) * 2014-10-08 2016-05-11 腾讯科技（深圳）有限公司 用户身份鉴权方法及装置
CN105610796A (zh) * 2015-12-17 2016-05-25 深圳市屹石科技股份有限公司 转移用户身份识别信息的方法、服务器及系统
CN105791268A (zh) * 2016-02-17 2016-07-20 深圳市屹石科技股份有限公司 服务器、健身设备用户登录方法及用户登录方法

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021017208A1 (zh) * 2019-07-30 2021-02-04 广东美的制冷设备有限公司 设备绑定方法、装置和电子设备
US11792865B2 (en) 2019-07-30 2023-10-17 Gd Midea Air-Conditioning Equipment Co., Ltd. Device binding method and apparatus, and electronic device
CN111538596A (zh) * 2020-04-23 2020-08-14 北京字节跳动网络技术有限公司 一种资源处理的方法、装置、计算机设备及存储介质
CN111538596B (zh) * 2020-04-23 2023-06-27 北京字节跳动网络技术有限公司 一种资源处理的方法、装置、计算机设备及存储介质
CN113792285A (zh) * 2021-08-05 2021-12-14 广东核电合营有限公司 一种核电站业务权限控制方法、装置及终端设备
CN113792285B (zh) * 2021-08-05 2024-01-26 广东核电合营有限公司 一种核电站业务权限控制方法、装置及终端设备

Also Published As

Publication number Publication date
CN109600734A (zh) 2019-04-09

Similar Documents

Publication Publication Date Title
US10572857B2 (en) Mobile check-in with push notification services
JP6883612B2 (ja) カスタマイズ可能なファイルリクエストを介したファイル提出物を収集するための収集フォルダ
US11783059B2 (en) Collection folder for collecting file submissions
CN107430666B (zh) 租户锁箱
JP6543725B2 (ja) ファイル提出物を収集するための収集フォルダ
US8204949B1 (en) Email enabled project management applications
US9817833B2 (en) System and method for processing an electronic image file
US20190342753A1 (en) Device configuration method, apparatus and system
CN108351771A (zh) 维持对于在部署到云计算环境期间的受限数据的控制
US9514291B2 (en) Information processing system, information processing device, and authentication information management method
WO2019062687A1 (zh) 基于app应用的鉴权方法、绑定方法、系统及设备
CN106940643A (zh) 警民通app系统
US11263324B2 (en) Monitoring source code repository data in real-time to protect sensitive information and provide entity-specific alerts
JP2017091157A (ja) 情報処理装置、情報処理システム、情報処理方法及びプログラム
CN107180457A (zh) 基于移动终端的考勤方法及移动终端及考勤服务器及系统
AU2013200453B2 (en) Methods and Systems for Increasing the Security of Electronic Messages
US20230033027A1 (en) Workflow management via a communication platform
JP6588306B2 (ja) 情報処理装置、情報処理方法、及びプログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18860306

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18860306

Country of ref document: EP

Kind code of ref document: A1