WO2021244474A1 - 登录数据处理方法、装置、设备及系统 - Google Patents

登录数据处理方法、装置、设备及系统 Download PDF

Info

Publication number
WO2021244474A1
WO2021244474A1 PCT/CN2021/097259 CN2021097259W WO2021244474A1 WO 2021244474 A1 WO2021244474 A1 WO 2021244474A1 CN 2021097259 W CN2021097259 W CN 2021097259W WO 2021244474 A1 WO2021244474 A1 WO 2021244474A1
Authority
WO
WIPO (PCT)
Prior art keywords
login
request
hardware device
user
code
Prior art date
Application number
PCT/CN2021/097259
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 WO2021244474A1 publication Critical patent/WO2021244474A1/zh

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31User authentication
    • G06F21/36User authentication by graphic or iconic representation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/45Structures or tools for the administration of authentication

Definitions

  • This manual belongs to the field of computer technology, and particularly relates to login data processing methods, devices, equipment and systems.
  • an embodiment of the present disclosure provides a login data processing method, the method includes: returning a login code to a hardware device according to a received login code request; configuring services for the hardware device according to a received user configuration request Manage users; receive a login request sent by a user terminal by scanning the login code in the hardware device; grant login authority to the login request according to the login user information corresponding to the login request and the service management user configured by the hardware device Audit; if the audit is passed, the login state of the login code is modified to be logged in, and the hardware device is associated with the logged-in user information.
  • this specification provides a login data processing method, the method includes: sending a login code request to the server through a login code interface opened by the server; receiving a login code issued by the server based on the login code request Code; receives the login request sent by the user terminal by scanning the displayed login code, and sends the login request to the server, so that the server can modify the login code after reviewing the login authority of the login request State; poll the login state of the login code every preset time, if the login state of the login code is logged in, the login code is no longer displayed.
  • this specification provides a login data processing method, including: sending a device binding request to a server, the device binding request including a hardware device identifier and device management user information, so that the server is based on the The device binding request is for the hardware device to associate the device management user information; receive the device binding success information returned by the server, and send a user configuration request to the server based on the device management user information, the user configuration request Includes service management user information, so that the server associates the service management user information with the hardware device based on the user configuration request; and sends a login request by scanning the login code displayed by the hardware device.
  • the login user information is included, so that the hardware device sends the login request to the server, and the server verifies the hardware device and the login user information based on the login request.
  • this specification provides a login data processing device, including: a login code return module, used to return a login code to the hardware device according to the received login code request; a user configuration module, used to configure according to the received user Request to configure a service management user for the hardware device; a login request receiving module, used to receive a login request sent by a user terminal by scanning the login code in the hardware device; a login authority review module, used to log in according to the corresponding login request The login user information and the business management user of the hardware device configuration review the login authorization of the login request; the login status modification module is used to modify the login code of the login code when the login authorization of the login request is approved The status is logged in, and the hardware device is associated with the logged-in user information.
  • a login code return module used to return a login code to the hardware device according to the received login code request
  • a user configuration module used to configure according to the received user Request to configure a service management user for the hardware device
  • a login request receiving module used to receive a login request sent by
  • this specification provides a login data processing device, including: a login code request module, configured to send a login code request to the server through a login code interface opened by the server; and a login code receiving module, configured to receive the The server sends the login code based on the login code request; the login request sending module is used to receive the login request sent by the user terminal by scanning the displayed login code, and send the login request to the server, so that the The server modifies the login state of the login code after reviewing the login authority of the login request; the login state polling module is used to poll the login state of the login code every preset time, if the login code is logged in If the status is logged in, the login code will no longer be displayed.
  • this specification provides a login data processing apparatus, including: a device binding request module, configured to send a device binding request to a server, and the device binding request includes hardware device identification and device management user information, So that the server associates the device management user information for the hardware device based on the device binding request; the device configuration module is used to receive the device binding success information returned by the server, and manage the user information based on the device Send a user configuration request to the server, where the user configuration request includes service management user information, so that the server associates the service management user information with the hardware device based on the user configuration request; the login request module uses Sending a login request by scanning the login code displayed by the hardware device, the login request including login user information, so that the hardware device sends the login request to the server, and the server is based on the login request Verify the hardware device and the logged-in user information.
  • a device binding request module configured to send a device binding request to a server, and the device binding request includes hardware device identification and device management user information, So that the server associates the device
  • embodiments of the present disclosure provide a login data processing device, including at least one processor and a memory for storing processor-executable instructions.
  • the processor implements the first aspect or the first aspect when the instructions are executed.
  • embodiments of the present disclosure provide a login data processing system, including: a device management server, a hardware device, and at least one user terminal; wherein, the device management server includes at least one processor and a storage processor A memory that can execute instructions, the processor implements the method described in the first aspect when the instructions are executed, and is used to issue a login code for the hardware device, and manage the hardware device based on the login code;
  • the hardware device includes at least one processor and a memory for storing processor-executable instructions. When the processor executes the instructions, the method described in the second aspect is implemented and used to display the information provided by the device management server.
  • Login code for the user terminal to scan to log in to the hardware device includes at least one processor and a memory for storing processor-executable instructions, and the processor implements the third The method described in the aspect is used to log in to the hardware device by scanning the login code displayed by the hardware device.
  • the login data processing method, device, equipment and system provided in this manual by issuing the login code for the hardware device, the user can quickly log in to the hardware device by scanning the login code displayed in the hardware device without complicated login procedures.
  • the verification of login authority can be performed based on the business management user and the login user configured by the hardware device to ensure the safe use of the hardware device and realize the safe and fast login of the hardware management device.
  • users can quickly log in to the hardware device and use the hardware device for business processing, which facilitates and quickly realizes the digitization of business processing.
  • the hardware devices that have issued the login code can be managed in a unified manner, and the login code can be directly issued through the open interface.
  • the hardware device itself does not need to be modified, which reduces the cost and is more applicable.
  • FIG. 1 is a schematic flowchart of an embodiment of a login data processing method provided by an embodiment of the present disclosure
  • FIG. 2 is a schematic flowchart of a method for processing login data in another embodiment of this specification.
  • FIG. 3 is a schematic flowchart of a method for processing login data in another embodiment of this specification.
  • Fig. 4 is a schematic diagram of a flow diagram of hardware device login management based on a login code in an example of this specification
  • FIG. 5 is a schematic diagram of the module structure of an embodiment of the login data processing device provided in this specification.
  • FIG. 6 is a schematic diagram of the module structure of an embodiment of the login data processing device provided in this specification.
  • FIG. 7 is a schematic diagram of the module structure of an embodiment of the login data processing device provided in this specification.
  • Fig. 8 is a block diagram of the hardware structure of the login data processing server in an embodiment of this specification.
  • FIG. 1 is a schematic flowchart of an embodiment of a login data processing method provided by an embodiment of the present disclosure.
  • the method or device may include more or partly combined fewer operation steps based on conventional or no creative labor. Or modular unit.
  • steps or structures where there is no necessary causal relationship logically the execution order of these steps or the module structure of the device is not limited to the execution order or module structure shown in the embodiments of the present disclosure or the drawings.
  • the described method or module structure is applied to an actual device, server, or terminal product, it can be executed sequentially or in parallel according to the method or module structure shown in the embodiments or drawings (for example, parallel processor or multi-threaded processing).
  • the environment even including the implementation environment of distributed processing and server clusters).
  • Step 102 Return the login code to the hardware device according to the received login code request.
  • the hardware devices in the embodiments of the present disclosure include not only computers and tablet computers, but also other terminal devices, generally terminal devices with screens, for example: POS (point of sale, with screens) Sales terminal) equipment such as: face-scanning equipment at the cashier of a supermarket, etc.; it can also include ordering equipment, shopping mall advertising display equipment, self-service equipment (such as self-service ticketing equipment), vehicle-mounted equipment, and so on.
  • the hardware device in the embodiment of the present disclosure is generally used by multiple users, and each user needs to log in first when using the hardware device.
  • the hardware device can access the device management server by calling the interface opened by the device management server, and send a login code request to the device management server, that is, request the device management server to issue a login code for the hardware device.
  • the device management server can be understood as a platform or server that can provide a login code interface for hardware devices and perform unified management of connected hardware devices, but it is a service that is open to some more powerful network platforms.
  • the manufacturer of the hardware device can request a login code for the hardware device through the interface opened by the device management server before the hardware device leaves the factory.
  • the login code may include the jump link of the user terminal after scanning the login code and the login code identification, and may also include the code value state of the login code, that is, the login state, that is, whether the login code is in the logged-in state or the unlogged-in state.
  • the specific form of the login code can be a two-dimensional code, a barcode, or other pictures that can include a designated meaning.
  • the login code returned by the device management server to the hardware device may be a code value generated by the device management server according to the received request, and the hardware device may map the code value returned by the device management server to the corresponding login code, and Render and display the login code.
  • the device management server can also directly generate a login code picture according to the received request, and return the generated login code picture to the hardware device for the hardware device to display the received login code picture.
  • the process of generating the login code includes but is not limited to the above explanation, and the embodiment of the present disclosure does not specifically limit it.
  • Step 104 Configure a service management user for the hardware device according to the received user configuration request.
  • the user before the user uses the hardware device, the user can send a user configuration request to the device management server through the small program of the user terminal or directly click the page in the hardware device, that is, request to configure the service management user for the hardware device.
  • the configuration request may include the device identification of the hardware device and the user information of the service management user configured for the hardware device.
  • the device management server may associate the user information of the service management user in the user configuration request with the hardware device according to the received user configuration request, that is, configure the service management user for the hardware device.
  • the user information of the service management user may include: at least one of the user's name, mobile phone number, identification, and user name of the designated application.
  • Step 106 Receive a login request sent by the user terminal by scanning the login code in the hardware device.
  • the logged-in user can scan the log-in code displayed in the hardware device through his user terminal such as a smart phone, and send a log-in request to the device management server.
  • the logged-in user can scan the login code in the hardware device through the specified application in the user terminal.
  • the hardware terminal can send the user request login information to the device management server.
  • the user terminal scans the login code of the hardware device, it automatically triggers a login request to the device management server.
  • the login code can also be directly pasted on the outside of the hardware device, and the user can directly scan the hardware device pasted on the hardware device.
  • Step 108 According to the login user information corresponding to the login request and the service management user configured by the hardware device, audit the login authority of the login request.
  • the login request received by the device management server may include the login user information of the login user requesting to log in and the device identification of the hardware device requesting login.
  • the login user information may include the name, mobile phone number, and At least one of the identity identifier, the user name of the specified application, etc.
  • the device identifier can be the product serial number of the hardware device (such as: SN, Serial Number) or the mobile device identification code (such as: International Mobile Equipment Identity, IMEI), which can be determined by the device Upload when the manufacturer requests the login code for the hardware device.
  • the device management server can match the login user information in the login request with the user information of the service management user associated with the hardware device, and determine whether the login user is the service management user configured by the hardware device. If so, it determines that the login request is legal. If it is not, it is determined that the login request is illegal and the request is rejected.
  • Step 110 If the verification is passed, modify the login status of the login code to be logged in, and associate the hardware device with the logged-in user information.
  • the device management server audits the login request based on the login user information of the logged-in user and the service management user of the hardware device configuration, it determines that the login user belongs to the service management user of the hardware device configuration, and the login request After the review is passed, the login state of the login code of the hardware device can be modified to logged in in the database of the device management server.
  • the hardware device can be associated with the logged-in user information, and the logged-in user information can be recorded.
  • Log-in users can perform business processing on the hardware device, such as setting the home page configuration items of the hardware device, refund processing, and payment processing.
  • the cash register at the cashier counter of a supermarket is a POS device with a screen.
  • Users such as manufacturers or supermarket equipment administrators can request a login code for the POS device through the interface opened by the device management server.
  • the screen of the POS device The login code can be displayed.
  • the supermarket equipment administrator can also configure business management users for the POS device, for example, by sending a user configuration request to the device management server, requesting that the POS device be configured with business management user A and business management user B.
  • Business management user A can scan the login code displayed in the POS device through his mobile terminal and send a login request to the device management server.
  • the device management server can perform identity verification on the logged-in user in the login request.
  • the login user is a business management user of the POS device, that is, whether the login user has the login authority.
  • the login status of the POS device's login code can be modified to be logged in, and the business administrator A can use the POS device to collect money or Business operations such as refunds.
  • the business management user B can also use the same method to log in to the POS device.
  • the device management server can record the business processing data of the business management users A and B after logging in to the POS device, so that the administrator can query the business processing of each business management user Situation and so on.
  • the hardware device can poll every preset time, such as 1 second. For example, send a request to the device management server to query the login status of the login code.
  • the hardware device determines that the login status of the login code is logged in, it can no longer display the login code, such as : Exit the display interface of the login code and display its homepage directly.
  • the hardware device determines that the login status of the login code is not logged in, it can continue to display the login code in the interface and wait for the user to log in. For example, if the logged-in user logs out and the hardware device polls and finds that the login status of the login code has changed from logged in to not logged in, the login code will be displayed on the interface again.
  • the logged-in user can log-out through the hardware device, or can choose to log-out through the mobile terminal scanned by the logged-in mobile phone. The specifics may be determined by the actual situation, and the embodiment of the present disclosure does not specifically limit it.
  • the user can quickly log in to the hardware device by scanning the login code displayed in the hardware device without complicated login procedures.
  • the verification of login authority can be performed based on the business management user and the login user configured by the hardware device to ensure the safe use of the hardware device and realize the safe and fast login of the hardware management device.
  • users can quickly log in to the hardware device and use the hardware device for business processing, which facilitates and quickly realizes the digitization of business processing.
  • the hardware devices that have issued the login code can be managed in a unified manner, and the login code can be directly issued through the open interface.
  • the hardware device itself does not need to be modified, which reduces the cost and is more applicable.
  • the configuring service management users for the hardware device according to the received user configuration request includes: configuring the service for the hardware device according to the received user configuration request Management user and management authority corresponding to the service management user; the method further includes: receiving a service request sent by the hardware device; obtaining the login user information corresponding to the hardware device according to the service request; The management authority of the logged-in user corresponding to the user information is checked for the business authority of the business request.
  • the hardware device when configuring business management users for hardware devices, you can also configure the management rights of each business management user, such as: whether to have the refund processing authority, whether to set the refund password, and whether to modify the price Permissions and so on.
  • the hardware device After the user logs in successfully by scanning the login code in the hardware device, the hardware device can be used for business processing, such as refund processing.
  • the hardware device When a logged-in user uses a hardware device for service processing, the hardware device can be triggered to send a service request to the device management server.
  • the service request may include the device identification of the hardware device and specific service content, etc.
  • the device management server After receiving the service request, the device management server can obtain the logged-in user information of the logged-in user in the hardware device and the management authority corresponding to the logged-in user.
  • the acquired management authority of the logged-in user and the specific business content in the business request determine whether the currently logged-in user has the authority to handle the business content of the business request. If so, allow the business request to be processed and continue the subsequent business processing process. If not, the business request is rejected.
  • the management authority of the service management user when the service management user uses the hardware device to conduct the service, it is verified whether the service management user has the service authority for the service, thereby ensuring the safe use of the hardware device.
  • the method further includes: receiving a device binding request, and managing user information for the hardware device binding device according to the device binding request;
  • the service request includes: a device identification;
  • the method further includes: judging whether the hardware device is bound to device management user information according to the device identification, and if so, determining that the hardware device has passed the verification, and obtaining the The login user information of the hardware device.
  • the device management user before configuring the service management user for the hardware device, you can perform device binding, that is, bind a device management user to the hardware device, and the device management user can manage the user information of the hardware device business management user And management authority to edit and modify.
  • a supermarket is preparing to digitally transform the POS equipment it owns. After requesting a login code for the POS device through the interface opened by the device management server, the supermarket administrator can use the designated applet in his mobile client or directly through The POS device sends a device binding request to the device management server.
  • the device binding request can include the device identification and the device management user information that needs to be bound.
  • the device management server can bind the corresponding device management user for the POS device, that is, the POS device belongs to The right or management right is owned by the device management user.
  • the device management user can configure the business management user and the management authority of the business management user for the hardware device. Specifically, the business management user and The configuration of its management authority, or directly enter the configured business management user and its management authority in the hardware device after verifying the identity in the hardware device.
  • the hardware device When a business management user logs in to a hardware device and uses the hardware device for business processing, the hardware device is triggered to send a business request to the device management server.
  • the business request may include the device identification and corresponding business content.
  • the device management server can determine whether the hardware device is bound to the device management user according to the device identifier in the service request, that is, whether the hardware device has bound device management user information. If so, it is determined that the hardware device is legal and can be used normally, and then obtains the login user information of the hardware device based on the device identification, performs management authority inspection on the login user information, and determines whether the login user has the business authority to handle the service request. If it is determined that the hardware device is not bound to the device management user, it can be considered that the hardware device is currently illegal and cannot be used normally, that is, the hardware device does not currently have a user, and the service request can be directly rejected.
  • the hardware device in the embodiments of the present disclosure can bind the device management user before using it. During business processing, it can be determined whether the hardware device performs the device management user binding based on the device identification, and the identity verification of the hardware device is performed. Only hardware devices bound to device management users are allowed to conduct business processing, laying a data foundation for subsequent risk identification of hardware devices, ensuring the safe use of hardware devices, and facilitating safe management of hardware devices.
  • the method further includes: after the login request is approved, issuing a login ID to the logged-in user, and returning the login ID to the hardware device , And associating the login identifier with the login user information of the login user; the received service request includes: the login identifier; and the login user information corresponding to the hardware device is obtained according to the service request , Including: obtaining login user information associated with the login identifier according to the login identifier.
  • a login ID can be issued to the login user, the login ID is associated with the login user information of the login user, and the login ID is returned at the same time To the hardware device.
  • the service request may include the login ID and the device ID.
  • the device management server can perform identity verification on the hardware device based on the device identification, and determine whether the hardware device is bound to the device management user.
  • the login user information of the logged-in user of the current hardware device can be obtained based on the login ID, and then the log-in user's business authority verification is performed based on the logged-in user information to determine whether the logged-in user has the business content requested by the business Handle the authority, if there is, continue to handle the business, if not, then refuse the request.
  • the embodiments of the present disclosure issue a login ID to the logged-in user after the hardware device is successfully logged in.
  • the login ID can be associated with the logged-in user information, so that the logged-in user's information can be quickly obtained, and the logged-in user's identity and management authority can be determined Verification, a substitute for data processing efficiency.
  • Fig. 2 is a schematic flowchart of a login data processing method in another embodiment of this specification. As shown in Fig. 2, some embodiments of this specification may provide a login data processing method applied to a hardware device side. The method includes:
  • Step 202 Send a login code request to the server through the login code interface opened by the server.
  • the hardware devices in the embodiments of the present disclosure include not only computers and tablet computers, but also other terminal devices, generally terminal devices with screens, for example: POS (point of sale, with screens) Sales terminal) equipment such as: face-scanning equipment at the cashier of a supermarket, etc.; it can also include ordering equipment, shopping mall advertising display equipment, self-service equipment (such as self-service ticketing equipment), vehicle-mounted equipment, and so on.
  • the server can be understood as the device management server in the above embodiment.
  • the hardware device can access the device management server by calling the interface opened by the device management server, and send a login code request to the device management server, that is, request the device management server to be a hardware device Issue a login code.
  • the device management server can be understood as a platform or server that can provide a login code interface for hardware devices and perform unified management of connected hardware devices, but it is a service that is open to some more powerful network platforms.
  • the manufacturer of the hardware device can request a login code for the hardware device through the interface opened by the device management server before the hardware device leaves the factory.
  • Step 204 Receive a login code issued by the server based on the login code request.
  • the device management server may return a login code to the hardware device.
  • the login code may include a jump link to the user terminal after scanning the login code, and may also include the code value state of the login code, that is, the login state, that is, whether the login code is in the logged-in state or the unlogged-in state.
  • the specific form of the login code can be a two-dimensional code, a barcode, or other pictures that can include a designated meaning.
  • the login code returned by the device management server to the hardware device may be a code value generated by the device management server according to the received request.
  • the hardware device may map the code value returned by the device management server to the corresponding login code, and render and display the login code.
  • the device management server can also directly generate a login code picture according to the received request, and return the generated login code picture to the hardware device, so that the hardware device can display the received login code picture.
  • the process of generating the login code includes but is not limited to the above explanation, and the embodiment of the present disclosure does not specifically limit it.
  • the hardware device After the hardware device receives the login code, it can be directly displayed on its display screen for the user to scan and log in.
  • Step 206 Receive the login request sent by the user terminal by scanning the displayed login code, and send the login request to the server, so that the server can modify the login code after reviewing the login authority of the login request. Login state.
  • the logged-in user can scan the log-in code displayed in the hardware device through his user terminal such as a smart phone, and send a log-in request to the device management server.
  • the logged-in user can scan the login code in the hardware device through the specified application in the user terminal.
  • the hardware terminal can send the user request login information to the device management server.
  • the user terminal scans the login code of the hardware device, it automatically triggers a login request to the device management server.
  • the login request may include the login user information of the login user requesting to log in and the device identification of the hardware device requesting to log in.
  • the device management server can match the login user information in the login request with the user information of the business management user configured in association with the hardware device , Determine whether the logged-in user is the business management user of the hardware device configuration, if it is, then determine that the login request is legal, the login request is approved, and the login status of the hardware device's login code is changed to logged in in the database of the device management server At the same time, it can also associate hardware devices with logged-in user information, and record the logged-in user's information. If the login request is not approved, the login request is determined to be illegal and the request is rejected.
  • Step 208 Polling the login status of the login code every preset time, and if the login status of the login code is logged in, the login code is no longer displayed.
  • the hardware device may poll every preset time, such as 1 second, such as sending a request to the device management server to query the login status of the login code.
  • the request may include information such as device identification, login code identification, and so on.
  • the hardware device determines that the login status of its login code is logged in, it can no longer display the login code, for example, log out of the login code display interface and directly display its homepage. If the hardware device determines that the login status of the login code is not logged in, it can continue to display the login code in the interface and wait for the user to log in.
  • the login code will be displayed on the interface again.
  • the logged-in user can log-out through the hardware device, or can choose to log-out through the mobile terminal scanned by the logged-in mobile phone.
  • the specifics may be determined by the actual situation, and the embodiment of the present disclosure does not specifically limit it.
  • the user by issuing a login code to the hardware device, the user can quickly log in to the hardware device by scanning the login code displayed in the hardware device without complicated login procedures.
  • the verification of login authority can be performed based on the business management user and the login user configured by the hardware device to ensure the safe use of the hardware device and realize the safe and fast login of the hardware management device.
  • users can quickly log in to the hardware device and use the hardware device for business processing, which facilitates and quickly realizes the digitization of business processing.
  • the hardware devices that have issued the login code can be managed uniformly, and the hardware devices themselves do not need to be modified, which reduces the cost and is more applicable.
  • the server changes the login status of the login code to logged in after passing the login permission review of the login request, and issues a login ID to the logged-in user
  • the login identifier is associated with the login user information of the login user, and the login identifier is returned to the hardware device;
  • the method further includes: receiving a service request, wherein the service request includes: a device identifier, Login ID; send the service request to the server, so that the server verifies the hardware device according to the device ID, and after the verification is passed, the server obtains the hardware based on the login ID
  • the login of the device is associated with the login user information of the login identifier, and the service authority verification of the login user is performed.
  • a login ID can be issued to the logged-in user, the login ID is associated with the login user information of the logged-in user, and the login ID is returned at the same time To the hardware device.
  • the service request may include the login ID and the device ID.
  • the device management server can perform identity verification on the hardware device based on the device identification, and determine whether the hardware device is bound to the device management user.
  • the login user information of the logged-in user of the current hardware device can be obtained based on the login ID, and then the log-in user's business authority verification is performed based on the logged-in user information to determine whether the logged-in user has the business content requested by the business Handle the authority, if there is, continue to handle the business, if not, then refuse the request.
  • the embodiments of the present disclosure issue a login ID to the logged-in user after the hardware device is successfully logged in.
  • the login ID can be associated with the logged-in user information, so that the logged-in user's information can be quickly obtained, and the logged-in user's identity and management authority can be determined Verification, a substitute for data processing efficiency.
  • Fig. 3 is a schematic flowchart of a login data processing method in another embodiment of this specification. As shown in Fig. 3, some embodiments of this specification may provide a login data processing method applied on the user terminal side, and the method includes:
  • Step 302 Send a device binding request to the server.
  • the device binding request includes hardware device identification and device management user information, so that the server associates the hardware device with the device management based on the device binding request.
  • User Info includes hardware device identification and device management user information, so that the server associates the hardware device with the device management based on the device binding request.
  • a login code request may be sent to the server, that is, the device management server, and a login code may be requested for the hardware device before the hardware device leaves the factory.
  • the user can bind the hardware device through the user terminal, that is, bind a device management user to the hardware device, and the device management user can manage the business of the hardware device. Edit and modify user information and management authority. For example, a supermarket is preparing to digitally transform the POS equipment it owns. After requesting a login code for the POS device through the interface opened by the device management server, the supermarket administrator can use the designated applet in his mobile client or directly through The POS device sends a device binding request to the device management server.
  • the device binding request can include the device identification and the device management user information that needs to be bound.
  • the device management server can bind the corresponding device management user for the POS device, that is, the POS device belongs to The right or management right is owned by the device management user.
  • Step 304 Receive the device binding success information returned by the server, and send a user configuration request to the server based on the device management user information.
  • the user configuration request includes the service management user information, so that the server is based on the device management user information.
  • the user configuration request associates the service management user information with the hardware device.
  • the user terminal can receive the information that the device is successfully bound, and the device management user can configure the business management user and the management authority of the business management user for the hardware device , Specifically, you can configure the business management user and its management authority through the small program designated in the user terminal of the device management user, or directly enter the configured business management user and its management authority in the hardware device after verifying the identity in the hardware device .
  • the device management server can record the device management user information and business management user information bound to the hardware device in the database or cache.
  • Device management users can also configure management rights for each business management user, and different business management users have different business rights when using hardware devices.
  • Step 306 Send a login request by scanning the login code displayed by the hardware device, the login request includes login user information, so that the hardware device sends the login request to the server, and the server is based on the The login request verifies the hardware device and the login user information.
  • both the device management user and the business management user can scan the login code displayed in the hardware device to trigger the hardware device to send a login request to the device management server.
  • the login request may include the login user of the logged-in user requesting to log in Information and the device ID of the hardware device requesting login.
  • the device management server can match the login user information in the login request with the user information of the service management user associated with the hardware device, and determine whether the login user is the service management user configured by the hardware device. If so, it determines that the login request is legal.
  • the login request is approved and the login state of the login code of the hardware device is modified to logged in in the database of the device management server.
  • the hardware device can be associated with the logged-in user information, and the logged-in user information is recorded. If the login request is not approved, the login request is determined to be illegal and the request is rejected.
  • the user terminal may be a user terminal of a device management user such as a merchant, or a user terminal of a business management user such as a shop assistant.
  • the login data processing method by issuing a login code to the hardware device, the user can quickly log in to the hardware device by scanning the login code displayed in the hardware device without complicated login procedures.
  • the verification of login authority can be performed based on the business management user and login user configured by the hardware device to ensure the safe use of the hardware device and realize the safe and fast login of the hardware management device.
  • users can quickly log in to the hardware device and use the hardware device for business processing, which facilitates and quickly realizes the digitization of business processing.
  • the hardware devices that have issued the login code can be managed uniformly, and the hardware devices themselves do not need to be modified, which reduces the cost and is more applicable.
  • Figure 4 is a schematic diagram of the process of hardware device login management based on the login code in an example of this manual. The following describes the process of login data processing in some examples of this manual in conjunction with Figure 4:
  • the device side ie, hardware device
  • the device management server such as cloud payment platform, pre-payment can be understood as a payment mode based on cloud computing architecture, relying on the Internet and mobile Internet
  • login code initialization interface to pull the login code .
  • the authentication center of the cloud payment platform can issue a qrcodeid to the login code, that is, the login code identifier, and the login code identifier can be stored in the cache system.
  • the merchant administrator the device management user
  • the merchant can bind the device with the information of the merchant on the device.
  • merchants can bind business information first, and then add and bind business management users, that is, shop assistants. It can be connected to the device center of the cloud payment platform through a small program or hardware device of the user terminal, and the hardware device can be bound with business information.
  • the cloud payment platform After the cloud payment platform receives the login code 1 request of the hardware device, it can issue the login code url (Uniform Resource Locator).
  • the login code is a QR code
  • the device When the login code is a QR code, the device will complete the QR code according to the URL
  • the code value content of the QR code can include qrcodeid (login code identification), miniappurl (redirect address), qrcodestatus (login status), etc.
  • the device can poll the status of the QR code every 1s to determine whether the QR code is successfully logged in. If the login is successful, the QR code will be invalid and the QR code will no longer be displayed; if the login is unsuccessful, the QR code will continue to be displayed.
  • the clerk scans the login code through the designated application that has been logged in in the user terminal, which can evoke the cloud payment merchant applet, which can realize the function of silently authorizing and obtaining the user's mobile phone number.
  • the cloud payment platform will modify the QR code status of the authentication center of the cloud payment platform to be logged in. At the same time, it will issue a login token, which is the login logo, and record the user's mobile phone number. Login ID for association, etc.
  • the device side obtains the login token of the login code in the device side by polling the status of the QR code and saves it locally for persistence. At the same time, the device side can send business requests to the cloud payment platform when the user conducts business transactions, such as obtaining configuration items on the homepage.
  • the service request may include device identity information such as: deviceid device identification, login token login identification, etc.
  • the cloud payment platform can exchange phonenum (identity information such as the user's mobile phone number) in the authentication center according to the login token in the business request, and then go to the cloud payment authorization center to obtain the permission of the logged-in user according to the phonenum.
  • phonenum identity information such as the user's mobile phone number
  • the authentication center can return user information, that is, the user information of the logged-in user.
  • the user can log in by scanning the login code in the hardware device, avoiding the complexity of offline operations such as issuing passwords and entering passwords.
  • the login code can be directly requested for the hardware device, and it can be adapted to the login code opening scheme of a variety of smart devices, and the device binding can be completed through the user terminal, and the device management user and business management can be realized
  • User binding enables both device management users and business management users to scan the code to log in to the device, which has low requirements for the equipment's original system and software transformation, and has strong applicability, which reduces the cost of digital equipment transformation.
  • one or more embodiments of this specification also provide a system for log-in data processing.
  • the system may include systems (including distributed systems), software (applications), modules, components, servers, clients, etc., which use the methods described in the embodiments of the present disclosure, combined with necessary implementation hardware devices.
  • the devices in one or more embodiments provided in the embodiments of the present disclosure are as described in the following embodiments. Since the implementation scheme of the device to solve the problem is similar to the method, the implementation of the specific device in the embodiment of the present disclosure can refer to the implementation of the foregoing method, and the repetition will not be repeated.
  • the term "unit” or "module” can realize a combination of software and/or hardware with predetermined functions.
  • the devices described in the following embodiments are preferably implemented by software, implementation by hardware or a combination of software and hardware is also possible and conceived.
  • FIG. 5 is a schematic diagram of the module structure of an embodiment of the login data processing device provided in this specification.
  • the device can immediately be the device management server in the above embodiment.
  • the login data provided in this specification The processing device may include: a login code return module 51, which can be used to return a login code to the hardware device according to the received login code request; the user configuration module 52, which can be used to configure a service management user for the hardware device according to the received user configuration request
  • the login request receiving module 53 which can be used to receive the login request sent by the user terminal by scanning the login code in the hardware device; the login authority review module 54, which can be used to log in user information and the hardware device corresponding to the login request
  • the configured business management user reviews the login authority of the login request; the login state modification module 55 can be used to modify the login state of the login code to be logged in when the login authority of the login request is approved.
  • the hardware device is associated with the logged-in user information.
  • the login data processing apparatus can issue a login code to the hardware device, and the user can quickly log in to the hardware device by scanning the login code displayed in the hardware device without complicated login procedures.
  • the verification of login authority can be performed based on the business management user and the login user configured by the hardware device to ensure the safe use of the hardware device and realize the safe and fast login of the hardware management device.
  • users can quickly log in to the hardware device and use the hardware device for business processing, which facilitates and quickly realizes the digitization of business processing.
  • the hardware devices that have issued the login code can be managed in a unified manner, and the login code can be directly issued through the open interface.
  • the hardware device itself does not need to be modified, which reduces the cost and is more applicable.
  • the user configuration module is specifically configured to configure a service management user and the management authority corresponding to the service management user for the hardware device according to the received user configuration request; the device also includes a service request
  • the receiving module is configured to: receive the service request sent by the hardware device; obtain the login user information corresponding to the hardware device according to the service request; The business requests for business authority verification.
  • the login data processing device provided by the embodiment of the present disclosure, by configuring the management authority of the business management user, when the business management user uses the hardware device for business processing, it is verified whether he has the business authority to handle the business, thereby ensuring the safety of the hardware device use.
  • the apparatus further includes a device binding module for: receiving a device binding request, and managing user information for the hardware device binding device according to the device binding request; the service request receiving module The received service request includes: a device identifier; the service request receiving module is further configured to: according to the device identifier, determine whether the hardware device is bound to device management user information, and if so, determine the hardware The device verification is passed, and the login user information of the hardware device is obtained.
  • the hardware device can be bound to the device management user before being used.
  • it can be determined whether the hardware device is bound to the device management user based on the device identifier.
  • the device performs identity verification. Only hardware devices bound to device management users are allowed to conduct business processing, laying a data foundation for subsequent risk identification of hardware devices, ensuring the safe use of hardware devices, and facilitating safe management of hardware devices.
  • the login status modification module is further used to: after the login request is approved, issue a login ID to the logged-in user, return the login ID to the hardware device, and send all the login IDs to the hardware device.
  • the login identifier is associated with the login user information of the login user;
  • the service request sent by the received hardware device includes: the login identifier;
  • the service request receiving module is specifically configured to: obtain the login identifier according to the login identifier, and The login user information associated with the login ID.
  • the embodiments of the present disclosure issue a login ID to the logged-in user after the hardware device is successfully logged in.
  • the login ID can be associated with the logged-in user information, so that the logged-in user's information can be quickly obtained, and the logged-in user's identity and management authority can be determined Verification, a substitute for data processing efficiency.
  • FIG. 6 is a schematic diagram of the module structure of an embodiment of the login data processing device provided in this specification.
  • the device can immediately be the hardware device in the above embodiment.
  • the login data processing device provided in this specification may include : Login code request module 61, configured to send a login code request to the server through a login code interface opened by the server; login code receiving module 62, configured to receive a login code issued by the server based on the login code request; login The request sending module 63 is configured to receive a login request sent by the user terminal by scanning the displayed login code, and send the login request to the server, so that the server can review the login authority of the login request and modify the login request.
  • the login state of the login code; the login state polling module 64 is used to poll the login state of the login code every preset time. If the login state of the login code is logged in, the login state is no longer displayed code.
  • the login data processing apparatus by issuing a login code to the hardware device, the user can quickly log in to the hardware device by scanning the login code displayed in the hardware device without complicated login procedures.
  • the verification of login authority can be performed based on the business management user and the login user configured by the hardware device to ensure the safe use of the hardware device and realize the safe and fast login of the hardware management device.
  • users can quickly log in to the hardware device and use the hardware device for business processing, which facilitates and quickly realizes the digitization of business processing.
  • the hardware devices that have issued the login code can be managed uniformly, and the hardware devices themselves do not need to be modified, which reduces the cost and is more applicable.
  • the server modifies the login status of the login code to logged in, and issues a login ID to the logged-in user.
  • the login user information of the login user is associated, and the login ID is returned to the hardware device;
  • the device further includes a service processing module for receiving a service request, wherein the service request includes: a device ID and a login ID;
  • the service request is sent to the server, so that the server verifies the hardware device according to the device identifier.
  • the server obtains the login of the hardware device based on the login identifier. Login user information associated with the login identifier, and perform business authority verification on the login user.
  • the login data processing device issues a login ID to the logged-in user after the hardware device logs in successfully.
  • the login ID can be associated with the logged-in user information of the logged-in user, so that the information of the logged-in user can be obtained quickly, and the log-in user information can be quickly obtained.
  • the user's identity and management authority verification is a substitute for data processing efficiency.
  • FIG. 7 is a schematic diagram of the module structure of an embodiment of the login data processing device provided in this specification.
  • the device can immediately be the user terminal in the above embodiment.
  • the login data processing device provided in this specification may include :
  • the device binding request module 71 is configured to send a device binding request to the server, the device binding request includes the hardware device identification and device management user information, so that the server serves the device based on the device binding request
  • the hardware device is associated with the device management user information;
  • the device configuration module 72 is configured to receive the device binding success information returned by the server, and send a user configuration request to the server based on the device management user information, the user configuration request Includes service management user information, so that the server associates the service management user information with the hardware device based on the user configuration request;
  • the login request module 73 is configured to send login by scanning the login code displayed by the hardware device Request, the login request includes login user information, so that the hardware device sends the login request to the server, and the server checks the hardware device and the login user information
  • the login data processing apparatus by issuing a login code to the hardware device, the user can quickly log in to the hardware device by scanning the login code displayed in the hardware device without complicated login procedures.
  • the verification of login authority can be performed based on the business management user and the login user configured by the hardware device to ensure the safe use of the hardware device and realize the safe and fast login of the hardware management device.
  • users can quickly log in to the hardware device and use the hardware device for business processing, which facilitates and quickly realizes the digitization of business processing.
  • the hardware devices that have issued the login code can be managed uniformly, and the hardware devices themselves do not need to be modified, which reduces the cost and is more applicable.
  • the above-mentioned device may also include other implementation manners according to the description of the corresponding method embodiment.
  • specific implementation manners reference may be made to the descriptions of the corresponding method embodiments above, which are not repeated here.
  • An embodiment of the present disclosure also provides a login data processing device, including: at least one processor and a memory for storing processor-executable instructions, and the processor implements the information recommendation data processing method of the foregoing embodiment when the processor executes the instructions , Such as: returning the login code to the hardware device according to the received login code request; configuring the service management user for the hardware device according to the received user configuration request; receiving the login sent by the user terminal by scanning the login code in the hardware device Request; according to the login user information corresponding to the login request and the business management user configured by the hardware device, audit the login permission of the login request; if the audit is passed, modify the login status of the login code to be logged in, And associate the hardware device with the logged-in user information.
  • send a device binding request to a server where the device binding request includes a hardware device identifier and device management user information, so that the server associates the device management user with the hardware device based on the device binding request Information; receiving the device binding success information returned by the server, and sending a user configuration request to the server based on the device management user information, the user configuration request including service management user information, so that the server is based on the
  • the user configuration request is for the hardware device to associate the business management user information; scan the login code displayed by the hardware device to send a login request, the login request includes the login user information, so that the hardware device will log in The request is sent to the server, and the server verifies the hardware device and the logged-in user information based on the log-in request.
  • the embodiment of the present disclosure also provides a login data processing system, which includes a device management server, a hardware device, and at least one user terminal.
  • the device management server includes at least one processor and a memory for storing executable instructions of the processor.
  • the device issues a login code to manage the hardware device based on the login code;
  • the hardware device includes at least one processor and a memory for storing processor-executable instructions, and when the processor executes the instructions
  • the method for implementing the foregoing hardware device side execution is used to display the login code provided by the device management server for the user terminal to scan to log in to the hardware device;
  • the user terminal includes at least one processor and a storage processor A memory that can execute instructions, when the processor executes the instructions, implements the method executed on the user terminal side, and is used to log in to the hardware device by scanning the login code displayed by the hardware device.
  • the user terminal of the equipment management user can also be the user terminal of the service management user.
  • the login data processing device provided in this manual can also be applied to a variety of data analysis and processing systems.
  • the system or server or terminal or device can be a separate server, or it can include a server cluster or system using one or more of the methods or one or more embodiments of this specification or the server or terminal or device ( Including distributed systems), software (applications), actual operation devices, logic gate circuit devices, quantum computers, etc., combined with necessary terminal devices for implementing hardware.
  • the detection system for checking difference data may include at least one processor and a memory storing computer-executable instructions, and the processor implements the steps of the method in any one or more of the foregoing embodiments when executing the instructions.
  • FIG. 8 is a hardware structural block diagram of a login data processing server in an embodiment of this specification.
  • the computer terminal may be the login data processing server or a login data processing device in the foregoing embodiment.
  • the server 10 may include one or more (only one is shown in the figure) processor 100 (the processor 100 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), and The non-volatile memory 200 for storing data, and the transmission module 300 for communication functions.
  • the structure shown in FIG. 8 is only for illustration, and does not limit the structure of the above-mentioned electronic device.
  • the server 10 may also include more or fewer components than those shown in FIG. 8, for example, may also include other processing hardware, such as a database or multi-level cache, GPU, or have a configuration different from that shown in FIG. 8.
  • the non-volatile memory 200 can be used to store software programs and modules of application software, such as program instructions/modules corresponding to the login data processing method in the embodiment of the present disclosure.
  • the processor 100 runs the programs and modules stored in the non-volatile memory 200 Software programs and modules to perform various functional applications and update resource data.
  • the non-volatile memory 200 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memories.
  • the non-volatile memory 200 may further include a memory remotely provided with respect to the processor 100, and these remote memories may be connected to a computer terminal through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, offices and networks, mobile communication networks, and combinations thereof.
  • the transmission module 300 is used to receive or send data via a network.
  • the above-mentioned specific examples of the network may include a wireless network provided by a communication provider of a computer terminal.
  • the transmission module 300 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet.
  • the transmission module 300 may be a radio frequency (RF) module, which is used to communicate with the Internet in a wireless manner.
  • RF radio frequency
  • the method or device described in the above-mentioned embodiments provided in this specification can implement business logic through a computer program and be recorded on a storage medium, and the storage medium can be read and executed by a computer to achieve the effects of the solution described in the embodiments of the present disclosure.
  • a login code For example: return a login code to the hardware device according to the received login code request; configure a service management user for the hardware device according to the received user configuration request; receive a login request sent by the user terminal by scanning the login code in the hardware device According to the login user information corresponding to the login request and the business management user configured by the hardware device, audit the login authority of the login request; if the audit is passed, modify the login status of the login code to be logged in, and Associating the hardware device with the logged-in user information.
  • send a device binding request to a server where the device binding request includes a hardware device identifier and device management user information, so that the server associates the device management user with the hardware device based on the device binding request Information; receiving the device binding success information returned by the server, and sending a user configuration request to the server based on the device management user information, the user configuration request including service management user information, so that the server is based on the
  • the user configuration request is for the hardware device to associate the business management user information; scan the login code displayed by the hardware device to send a login request, the login request includes the login user information, so that the hardware device will log in The request is sent to the server, and the server verifies the hardware device and the logged-in user information based on the log-in request.
  • the storage medium may include a physical device for storing information, and usually the information is stored in a medium using electric, magnetic, or optical methods after digitizing the information.
  • the storage medium may include: devices that use electrical energy to store information, such as various types of memory, such as RAM, ROM, etc.; devices that use magnetic energy to store information, such as hard disks, floppy disks, magnetic tapes, magnetic core memory, bubble memory, U disk; a device that uses optical means to store information, such as CD or DVD.
  • devices that use electrical energy to store information such as various types of memory, such as RAM, ROM, etc.
  • devices that use magnetic energy to store information such as hard disks, floppy disks, magnetic tapes, magnetic core memory, bubble memory, U disk
  • a device that uses optical means to store information such as CD or DVD.
  • quantum memory graphene memory, and so on.
  • the aforementioned login data processing method or device provided by the embodiments of the present disclosure can be implemented in a computer by a processor executing corresponding program instructions, such as using the c++ language of the windows operating system on the PC side, linux system implementation, or other such as using android , IOS system programming language is implemented in smart terminals, and processing logic based on quantum computers is implemented, etc.
  • the device, computer storage medium, and system described above in the specification can also include other implementation manners according to the description of the related method embodiments.
  • specific implementation manners please refer to the description of the corresponding method embodiments, which will not be repeated here. .
  • the embodiments of the present disclosure are not limited to those that must comply with industry communication standards, standard computer resource data update and data storage rules, or the conditions described in one or more embodiments of this specification. Certain industry standards or implementations described in custom methods or examples with slight modifications can also achieve the same, equivalent or similar implementation effects of the foregoing examples, or predictable implementation effects after modification. Examples obtained by applying these modified or deformed data acquisition, storage, judgment, processing methods, etc., may still fall within the scope of the optional implementation of the embodiments of the present disclosure.
  • a programmable logic device Programmable Logic Device, PLD
  • PLD Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • HDL Hardware Description Language
  • ABEL Advanced Boolean Expression Language
  • AHDL Altera Hardware Description Language
  • HDCal JHDL
  • Lava Lava
  • Lola MyHDL
  • PALASM RHDL
  • VHDL Very-High-Speed Integrated Circuit Hardware Description Language
  • Verilog Verilog
  • the controller can be implemented in any suitable manner.
  • the controller can take the form of, for example, a microprocessor or a processor and a computer-readable medium storing computer-readable program codes (such as software or firmware) executable by the (micro)processor. , Logic gates, switches, application specific integrated circuits (ASICs), programmable logic controllers and embedded microcontrollers.
  • controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicon Labs C8051F320, the memory controller can also be implemented as a part of the memory control logic.
  • controllers in addition to implementing the controller in a purely computer-readable program code manner, it is completely possible to program the method steps to make the controller use logic gates, switches, application specific integrated circuits, programmable logic controllers, and embedded logic.
  • the same function can be realized in the form of a microcontroller or the like. Therefore, such a controller can be regarded as a hardware component, and the devices included in it for realizing various functions can also be regarded as a structure within the hardware component. Or even, a device for realizing various functions can be regarded as both a software module for realizing a method and a structure within a hardware component.
  • a typical implementation device is a computer.
  • the computer can be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, and a tablet.
  • Computers, wearable devices, or any combination of these devices are examples of these devices.
  • the functions are divided into various modules and described separately.
  • the function of each module can be realized in the same one or more software and/or hardware, or the module that realizes the same function can be realized by a combination of multiple sub-modules or sub-units, etc. .
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or integrated. To another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable resource data update equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the instruction device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable resource data update equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, which can be executed on the computer or other programmable equipment.
  • the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.
  • the computing device includes one or more processors (CPU), input/output interfaces, network interfaces, and memory.
  • the memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM).
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash memory
  • Computer-readable media includes permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology.
  • Information can be computer readable instructions, data structures, program modules, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical storage, Magnetic cassettes, magnetic tape magnetic disk storage, graphene storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.
  • PRAM phase change memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • RAM random access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory or other memory technology
  • CD-ROM compact disc
  • DVD digital versatile disc
  • Magnetic cassettes magnetic tape magnetic disk storage
  • one or more embodiments of this specification can be provided as a method, a system, or a computer program product. Therefore, one or more embodiments of this specification may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, one or more embodiments of this specification may adopt a computer program implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes. The form of the product.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • One or more embodiments of this specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules.
  • program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types.
  • One or more embodiments of this specification can also be practiced in distributed computing environments. In these distributed computing environments, tasks are performed by remote devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

一种登录数据处理方法、装置、设备及系统,该方法包括:根据接收到的登录码请求向硬件设备返回登录码(102);根据接收到的用户配置请求为所述硬件设备配置业务管理用户(104);接收用户终端通过扫描所述硬件设备中的登录码发送的登录请求(106);根据所述登录请求对应的登录用户信息和所述硬件设备配置的业务管理用户,对所述登录请求进行登录权限审核(108);若审核通过,则修改所述登录码的登录态为已登录,并将所述硬件设备与所述登录用户信息进行关联(110)。通过为硬件设备下发登录码,用户通过扫描硬件设备中展示的登录码可快速安全登录硬件设备,不需要复杂的登录手续。

Description

登录数据处理方法、装置、设备及系统 技术领域
本说明书属于计算机技术领域,尤其涉及登录数据处理方法、装置、设备及系统。
背景技术
随着计算机互联网技术的发展,数字化业务逐渐进入人们的工作和生活。在使用电子设备办公或处理业务时,常常需要账户登录。一般的登录是通过输入用户名、密码或手机号、动态验证码等方式进行的,操作比较繁琐。或,有些需要对设备进行改造,使用指定系统的设备才能够实现快速登录的功能,成本较高,不利于退关使用。
发明内容
第一方面,本公开实施例提供了一种登录数据处理方法,所述方法包括:根据接收到的登录码请求向硬件设备返回登录码;根据接收到的用户配置请求为所述硬件设备配置业务管理用户;接收用户终端通过扫描所述硬件设备中的登录码发送的登录请求;根据所述登录请求对应的登录用户信息和所述硬件设备配置的业务管理用户,对所述登录请求进行登录权限审核;若审核通过,则修改所述登录码的登录态为已登录,并将所述硬件设备与所述登录用户信息进行关联。
第二方面,本说明书提供了一种登录数据处理方法,所述方法包括:通过服务器开放的登录码接口向所述服务器发送登录码请求;接收所述服务器基于所述登录码请求下发的登录码;接收用户终端通过扫描展示的登录码发送的登录请求,并将所述登录请求发送至所述服务器,以使得所述服务器对所述登录请求进行登录权限审核后修改所述登录码的登录态;每隔预设时间轮询所述登录码的登录态,若所述登录码的登录态为已登录,则不再展示所述登录码。
第三方面,本说明书提供了一种登录数据处理方法,包括:向服务器发送设备绑定请求,所述设备绑定请求中包括硬件设备标识和设备管理用户信息,以使得所述服务器基于所述设备绑定请求为所述硬件设备关联所述设备管理用户信息;接收所述服务器返回的设备绑定成功信息,基于所述设备管理用户信息向所述服务器发送用户配置请求,所述用户配置请求中包括业务管理用户信息,以使得所述服务器基于所述用户配置请求为所述硬件设备关联所述业务管理用户信息;通过扫描所述硬件设备展示的登录码发送登录请求,所述登录请求中包括登录用户信息,以使得所述硬件设备将所述登录请求发送至所述服务器,所述服务器基于所述登录请求对所述硬件设备和所述登录用户信息进行校验。
第四方面,本说明书提供了一种登录数据处理装置,包括:登录码返回模块,用于根据接收到的登录码请求向硬件设备返回登录码;用户配置模块,用于根据接收到的用户配置请求为所述硬件设备配置业务管理用户;登录请求接收模块,用于接收用户终端通过扫描所述硬件设备中的登录码发送的登录请求;登录权限审核模块,用于根据所述登录请求对应的登录用户信息和所述硬件设备配置的业务管理用户,对所述登录请求进行登录权限审核;登录态修改模块,用于在所述登录请求的登录权限审核通过时,修改所述登录码的登录态为已登录,并将所述硬件设备与所述登录用户信息进行关联。
第五方面,本说明书提供了一种登录数据处理装置,包括:登录码请求模块,用于 通过服务器开放的登录码接口向所述服务器发送登录码请求;登录码接收模块,用于接收所述服务器基于所述登录码请求下发的登录码;登录请求发送模块,用于接收用户终端通过扫描展示的登录码发送的登录请求,并将所述登录请求发送至所述服务器,以使得所述服务器对所述登录请求进行登录权限审核后修改所述登录码的登录态;登录态轮询模块,用于每隔预设时间轮询所述登录码的登录态,若所述登录码的登录态为已登录,则不再展示所述登录码。
第六方面,本说明书提供了一种登录数据处理装置,包括:设备绑定请求模块,用于向服务器发送设备绑定请求,所述设备绑定请求中包括硬件设备标识和设备管理用户信息,以使得所述服务器基于所述设备绑定请求为所述硬件设备关联所述设备管理用户信息;设备配置模块,用于接收所述服务器返回的设备绑定成功信息,基于所述设备管理用户信息向所述服务器发送用户配置请求,所述用户配置请求中包括业务管理用户信息,以使得所述服务器基于所述用户配置请求为所述硬件设备关联所述业务管理用户信息;登录请求模块,用于通过扫描所述硬件设备展示的登录码发送登录请求,所述登录请求中包括登录用户信息,以使得所述硬件设备将所述登录请求发送至所述服务器,所述服务器基于所述登录请求对所述硬件设备和所述登录用户信息进行校验。
第七方面,本公开实施例提供了一种登录数据处理设备,包括至少一个处理器以及用于存储处理器可执行指令的存储器,所述处理器执行所述指令时实现上述第一方面或第二方法或第三方面所述的登录数据处理方法。
第八方面,本公开实施例提供了一种登录数据处理系统,包括:设备管理服务器、硬件设备、至少一个用户终端;其中,所述设备管理服务器中包括至少一个处理器以及用于存储处理器可执行指令的存储器,所述处理器执行所述指令时实现第一方面所述的方法,用于为所述硬件设备下发登录码,基于所述登录码对所述硬件设备进行管理;所述硬件设备中包括至少一个处理器以及用于存储处理器可执行指令的存储器,所述处理器执行所述指令时实现上述第二方面所述的方法,用于展示所述设备管理服务器提供的登录码,供所述用户终端扫描以登录所述硬件设备;所述用户终端包括至少一个处理器以及用于存储处理器可执行指令的存储器,所述处理器执行所述指令时实现上述第三方面所述的方法,用于通过扫描所述硬件设备展示的登录码,登录所述硬件设备。
本说明书提供的登录数据处理方法、装置、设备及系统,通过为硬件设备下发登录码,用户通过扫描硬件设备中展示的登录码可快速登录硬件设备,不需要复杂的登录手续。并且,可基于硬件设备配置的业务管理用户和登录用户进行登录权限的校验,确保硬件设备的安全使用,实现硬件管理设备的安全快速登录。通过下发登录码的方式,使得用户可快速登录硬件设备,使用硬件设备进行业务办理,方便快捷的实现业务办理的数字化。同时,对于下发了登录码的硬件设备可统一管理,并且直接通过开放的接口下发登录码,硬件设备本身不需要做改造,降低了成本,更具有适用性。
附图说明
图1是本公开实施例提供的登录数据处理方法实施例的流程示意图;
图2是本说明书又一个实施例中登录数据处理方法的流程示意图;
图3是本说明书又一个实施例中登录数据处理方法的流程示意图;
图4是本说明书一个示例中基于登录码进行硬件设备登录管理的流程示意图;
图5是本说明书提供的登录数据处理装置一个实施例的模块结构示意图;
图6是本说明书提供的登录数据处理装置一个实施例的模块结构示意图;
图7是本说明书提供的登录数据处理装置一个实施例的模块结构示意图;
图8是本说明书一个实施例中登录数据处理服务器的硬件结构框图。
具体实施方式
随着计算机互联网技术的发展,办公设备数字化成为一种趋势。有些数字化的办公设备需要登录才能使用,对于多名员工共用的账户,办公设备的快速安全登录成为数字化办公的需求。例如:线下商家在做门店数字化改造时发现,新引入安装部分智能设备后,原有收银台自带的店员登录功能不可用。导致发现在设备上发起的支付交易无法归属到具体的店员等,从而无法实现店员的交接班、店员交易激励、店长退款管理等商家数字化经营方案。一般对于这种设备的登录采用的是输入用户名、密码的方式,操作比较麻烦,若忘记密码,可能还需要身份验证等复杂的操作过程。
图1是本公开实施例提供的登录数据处理方法实施例的流程示意图。虽然本说明书提供了如下述实施例或附图所示的方法操作步骤或装置结构,但基于常规或无需创造性的劳动在所述方法或装置中可包括更多或部分合并后更少的操作步骤或模块单元。在逻辑性上不存在必要因果关系的步骤或结构中,这些步骤的执行顺序或装置的模块结构不限于本公开实施例或附图所示的执行顺序或模块结构。所述的方法或模块结构的在实际中的装置、服务器或终端产品应用时,可按照实施例或附图所示的方法或模块结构进行顺序执行或并行执行(例如并行处理器或多线程处理的环境、甚至包括分布式处理、服务器集群的实施环境)。
具体的一个实施例如图1所示,本说明书提供的登录数据处理方法的一个实施例中,所述方法可应用在设备管理服务器侧,设备管理服务器可为计算机、平板电脑等终端,所述方法可包括如下步骤:步骤102、根据接收到的登录码请求向硬件设备返回登录码。
在具体的实施过程中,本公开实施例中的硬件设备不仅仅包括计算机、平板电脑,还可包括其他终端设备,一般可是带有屏幕的终端设备,例如:带屏幕的POS(point of sale,销售终端)设备如:超市收银台处的扫脸设备等;还可包括点餐设备、商场广告展示设备、自助设备(如:自助购票设备)、车载设备等等。本公开实施例中的硬件设备一般会有多名用户共同使用,各个用户在使用硬件设备时需要先进行登录。硬件设备可通过调用设备管理服务器开放的接口接入到设备管理服务器中,向设备管理服务器发送登录码请求,即请求设备管理服务器为硬件设备下发一个登录码。设备管理服务器可理解为能够为硬件设备提供登录码接口,对于接入的硬件设备进行统一管理的平台或服务器,可是一些功能比较强大的网络平台开放的服务。通常情况下,硬件设备的厂商在该硬件设备出厂前,即可通过设备管理服务器开放的接口为该硬件设备请求一个登录码。登录码可包括扫描该登录码后的用户终端的跳转链接、登录码标识,还可包括该登录码的码值状态即登录态,即该登录码是处于登录状态还是未登录状态。登录码的具体形式可是二维码、条形码或其他能够包括指定含义的图片。
本说明书一些实施例中,设备管理服务器返回给硬件设备的登录码可是设备管理服务器根据接收到的请求生成的码值,硬件设备可将设备管理服务器返回的码值映射为对应的登录码,并渲染和展示该登录码。设备管理服务器也可直接根据接收到的请求生成 登录码图片,将生成的登录码图片返回给硬件设备,以供硬件设备展示接收到的登录码图片。当然,根据实际使用需要,登录码的生成过程包括但不限于上述解释,本公开实施例不作具体限定。
步骤104、根据接收到的用户配置请求为所述硬件设备配置业务管理用户。
在具体的实施过程中,当用户使用硬件设备之前,可通过用户终端的小程序或直接点击硬件设备中的页面向设备管理服务器发送用户配置请求,即请求为该硬件设备配置业务管理用户,用户配置请求中可包括硬件设备的设备标识以及为该硬件设备配置的业务管理用户的用户信息。设备管理服务器可根据接收到的用户配置请求,将用户配置请求中的业务管理用户的用户信息与该硬件设备进行关联,即为该硬件设备配置好了业务管理用户。业务管理用户的用户信息可包括:用户的姓名、手机号、身份标识、指定应用程序的用户名等中的至少一个。在有用户通过扫描硬件设备上的登录码以请求登录该硬件设备时,可基于该硬件设备配置的业务管理用户,判断当前请求登录的用户是否有登录权限。
步骤106、接收用户终端通过扫描所述硬件设备中的登录码发送的登录请求。
在具体的实施过程中,登录用户可通过自己的用户终端如:智能手机扫描硬件设备中展示的登录码,向设备管理服务器发送登录请求。一般的,登录用户可通过用户终端中指定的应用程序扫描硬件设备中的登录码,当用户终端扫描硬件设备的登录码时,硬件终端可向设备管理服务器发送有用户请求登录信息。或,当用户终端扫描硬件设备的登录码时,自动向设备管理服务器触发登录请求。
当然,若硬件设备没有显示屏,登录码也可直接粘贴在硬件设备的设备外侧,用户可直接扫描硬件设备上粘贴的硬件设备。
步骤108、根据所述登录请求对应的登录用户信息和所述硬件设备配置的业务管理用户,对所述登录请求进行登录权限审核。
在具体的实施过程中,设备管理服务器接收到的登录请求中可包括请求登录的登录用户的登录用户信息以及请求登录的硬件设备的设备标识,登录用户信息可包括登录用户的姓名、手机号、身份标识、指定应用程序的用户名等中的至少一个,设备标识可是硬件设备的产品序列号(如:SN,Serial Number)或移动设备识别码(如:International Mobile Equipment Identity,IMEI),可由设备厂商在为硬件设备请求登录码时上传。设备管理服务器可将登录请求中的登录用户信息与硬件设备关联配置的业务管理用户的用户信息进行匹配,判断登录用户是否是该硬件设备配置的业务管理用户,若是,则确定该登录请求合法,若不是,则确定该登录请求不合法,拒绝请求。
步骤110、若审核通过,则修改所述登录码的登录态为已登录,并将所述硬件设备与所述登录用户信息进行关联。
在具体的实施过程中,当设备管理服务器基于登录用户的登录用户信息和硬件设备配置的业务管理用户对登录请求进行登录权限审核时,确定登录用户属于该硬件设备配置的业务管理用户,登录请求审核通过后,可在设备管理服务器的数据库中将该硬件设备的登录码的登录态修改为已登录,同时,还可将硬件设备与登录用户信息进行关联,并记录了登录用户的信息。登录用户可在硬件设备上进行业务办理如:设置硬件设备的首页配置项、退款处理、收款处理等。
例如:某超市的收银台的收银设备为带有屏幕的POS设备,用户如:厂商或超市设 备管理员等可通过设备管理服务器开放的接口为该POS设备请求一个登录码,POS设备的屏幕中可展示该登录码。超市设备管理员还可为该POS设备配置业务管理用户,如:通过向设备管理服务器发送用户配置请求,请求为该POS设备配置业务管理用户A、业务管理用户B。业务管理用户A可通过其手机终端扫描POS设备中展示的登录码,向设备管理服务器发送登录请求,设备管理服务器接收到登录请求后,可对登录请求中的登录用户进行身份校验,校验登录用户是否是POS设备的业务管理用户,即登录用户是否有登录权限。通过校验登录用户即为该POS设备配置的业务管理员A,登录请求通过,可修改该POS设备的登录码的登录态为已登录,业务管理员A即可使用该POS设备进行收款或退款等业务操作。同样的,业务管理用户B也可采用相同的方法登录该POS设备,设备管理服务器可分别记录业务管理用户A、B登录POS设备后的业务处理数据,以便管理员查询各个业务管理用户的业务处理情况等。
硬件设备可每隔预设时间如1秒轮询如向设备管理服务器发送请求查询登录码的登录态,当硬件设备确定其登录码的登录态为已登录时,可不再展示该登录码,如:退出登录码的展示界面,直接展示其首页。若硬件设备确定登录码的登录态为未登录,则可继续在界面中展示登录码,等待用户登录。如:若登录用户退出登录,硬件设备轮询发现其登录码的登录态由已登录变为未登录,则重新在界面中展示登录码。登录用户可通过硬件设备退出登录,也可通过其扫描登录的手机终端选择退出登录,具体可由实际情况而定,本公开实施例不作具体限定。
本公开实施例提供的登录数据处理方法,通过为硬件设备下发登录码,用户通过扫描硬件设备中展示的登录码可快速登录硬件设备,不需要复杂的登录手续。并且,可基于硬件设备配置的业务管理用户和登录用户进行登录权限的校验,确保硬件设备的安全使用,实现硬件管理设备的安全快速登录。通过下发登录码的方式,使得用户可快速登录硬件设备,使用硬件设备进行业务办理,方便快捷的实现业务办理的数字化。同时,对于下发了登录码的硬件设备可统一管理,并且直接通过开放的接口下发登录码,硬件设备本身不需要做改造,降低了成本,更具有适用性。
在上述实施例的基础上,本说明书一些实施例中,所述根据接收到的用户配置请求为所述硬件设备配置业务管理用户,包括:根据接收到的用户配置请求为所述硬件设备配置业务管理用户以及所述业务管理用户对应的管理权限;所述方法还包括:接收所述硬件设备发送的业务请求;根据所述业务请求,获取所述硬件设备对应的登录用户信息;根据所述登录用户信息对应的登录用户的管理权限,对所述业务请求进行业务权限校验。
在具体的实施过程中,在为硬件设备配置业务管理用户时,还可配置各个业务管理用户的管理权限,如:是否有退款处理权限、是否有设置退款密码的权限、是否有修改价格的权限等等。当用户通过扫描硬件设备中的登录码登录成功后,可使用硬件设备进行业务办理,如:退款处理。当登录用户使用硬件设备进行业务办理时,可触发硬件设备向设备管理服务器发送业务请求,业务请求中可包括硬件设备的设备标识以及具体业务内容等。设备管理服务器接收到业务请求后,可获取该硬件设备中的登录用户的登录用户信息以及登录用户对应的管理权限。根据获取到的登录用户的管理权限和业务请求中的具体业务内容,判断当前登录用户是否有办理该业务请求的业务内容的权限,若有,则允许业务请求办理,继续后面的业务办理流程,若没有,则拒绝业务请求。
本公开实施例,通过配置业务管理用户的管理权限,在业务管理用户使用硬件设备 进行业务办理时,校验其是否具有该业务办理的业务权限,确保了硬件设备的安全使用。
在上述实施例的基础上,本说明书一些实施例中,所述方法还包括:接收设备绑定请求,根据所述设备绑定请求为所述硬件设备绑定设备管理用户信息;接收到的所述业务请求中包括:设备标识;所述方法还包括:根据所述设备标识,判断所述硬件设备是否绑定有设备管理用户信息,若是,则确定所述硬件设备校验通过,获取所述硬件设备的登录用户信息。
在具体的实施过程中,在为硬件设备配置业务管理用户之前,可进行设备绑定,即为该硬件设备绑定一个设备管理用户,该设备管理用户可对硬件设备的业务管理用户的用户信息以及管理权限进行编辑、修改。如:某超市准备对其拥有的POS设备进行数字化改造,通过连接设备管理服务器开放的接口为POS设备请求了一个登录码后,超市管理员可利用其手机客户端中的指定小程序或直接通过POS设备向设备管理服务器发送设备绑定请求。设备绑定请求中可包括设备标识以及需要绑定的设备管理用户信息,设备管理服务器接收到该设备绑定请求后,可为该POS设备绑定对应的设备管理用户,即该POS设备的所属权或管理权为设备管理用户拥有。硬件设备的设备管理用户绑定成功后,设备管理用户可为该硬件设备配置业务管理用户以及业务管理用户的管理权限,具体可通过设备管理用户的用户终端中指定的小程序进行业务管理用户及其管理权限的配置,或直接在硬件设备中验证身份后在硬件设备中直接输入配置的业务管理用户及其管理权限。
当业务管理用户登录硬件设备,并使用硬件设备进行业务办理时,触发硬件设备向设备管理服务器发送业务请求,业务请求中可包括设备标识以及对应的业务内容。设备管理服务器接收到业务请求后,可根据业务请求中的设备标识,确定该硬件设备是否进行设备管理用户的绑定,即该硬件设备是否有绑定的设备管理用户信息。若有,则确定该硬件设备合法,可正常使用,接着基于该设备标识获取该硬件设备的登录用户信息,对登录用户信息进行管理权限检验,确定登录用户是否有办理该业务请求的业务权限。若确定硬件设备没有绑定设备管理用户,则可认为该硬件设备目前不合法,还不能正常使用,即该硬件设备目前没有归属用户,可直接拒绝该业务请求。
本公开实施例硬件设备在使用前可进行设备管理用户的绑定,在进行业务办理时,可基于设备标识确定该硬件设备是否进行设备管理用户的绑定,对硬件设备进行身份校验。只有绑定了设备管理用户的硬件设备才允许进行业务办理,为后续硬件设备的风险识别等奠定了数据基础,确保硬件设备安全使用,便于对硬件设备进行安全管理。
在上述实施例的基础上,本说明书一些实施例中,所述方法还包括:对所述登录请求审核通过后,为所述登录用户颁发登录标识,将所述登录标识返回至所述硬件设备,并将所述登录标识与所述登录用户的登录用户信息进行关联;接收到的所述业务请求中包括:登录标识;所述根据所述业务请求,获取所述硬件设备对应的登录用户信息,包括:根据所述登录标识,获取与所述登录标识关联的登录用户信息。
在具体的实施过程中,当用户扫描硬件设备登录码,并审核通过登录成功后,可为该登录用户颁发一个登录标识,将登录标识与登录用户的登录用户信息进行关联,同时将登录标识返回给硬件设备。当登录用户使用硬件设备进行业务办理,触发硬件设备向设备管理服务器发送业务请求时,业务请求中可包括登录标识、设备标识。设备管理服务器基于设备标识可对该硬件设备进行身份校验,确定硬件设备是否进行设备管理用户 的绑定。当硬件设备校验成功后,可基于登录标识获取当前硬件设备的登录用户的登录用户信息,再基于登录用户信息进行登录用户的业务权限的校验,确定登录用户是否具有业务请求的业务内容的办理权限,若有,继续业务办理,若无,则拒绝请求。
本公开实施例在硬件设备登录成功后,为登录用户颁发登录标识,该登录标识可与登录用户的登录用户信息进行关联,以便能够快速获取登录用户的信息,对登录用户进行身份以及管理权限的校验,替身了数据处理效率。
图2是本说明书又一个实施例中登录数据处理方法的流程示意图,如图2所示,本说明书一些实施例中可提供一种应用于硬件设备侧的登录数据处理方法,该方法包括:
步骤202、通过服务器开放的登录码接口向所述服务器发送登录码请求。
在具体的实施过程中,本公开实施例中的硬件设备不仅仅包括计算机、平板电脑,还可包括其他终端设备,一般可是带有屏幕的终端设备,例如:带屏幕的POS(point of sale,销售终端)设备如:超市收银台处的扫脸设备等;还可包括点餐设备、商场广告展示设备、自助设备(如:自助购票设备)、车载设备等等。服务器即可理解为上述实施例中的设备管理服务器,硬件设备可通过调用设备管理服务器开放的接口接入到设备管理服务器中,向设备管理服务器发送登录码请求,即请求设备管理服务器为硬件设备下发一个登录码。设备管理服务器可理解为能够为硬件设备提供登录码接口,对于接入的硬件设备进行统一管理的平台或服务器,可是一些功能比较强大的网络平台开放的服务。通常情况下,硬件设备的厂商在该硬件设备出厂前,即可通过设备管理服务器开放的接口为该硬件设备请求一个登录码。
步骤204、接收所述服务器基于所述登录码请求下发的登录码。
在具体的实施过程中,设备管理服务器接收到登录码请求后,可向硬件设备返回一个登录码。登录码可包括扫描该登录码后的用户终端的跳转链接,还可包括该登录码的码值状态即登录态,即该登录码是处于登录状态还是未登录状态。登录码的具体形式可是二维码、条形码或其他能够包括指定含义的图片。设备管理服务器返回给硬件设备的登录码可是设备管理服务器根据接收到的请求生成的码值,硬件设备可将设备管理服务器返回的码值映射为对应的登录码,并渲染和展示该登录码。设备管理服务器也可直接根据接收到的请求生成登录码图片,将生成的登录码图片返回给硬件设备,以供硬件设备展示接收到的登录码图片。当然,根据实际使用需要,登录码的生成过程包括但不限于上述解释,本公开实施例不作具体限定。硬件设备接收到登录码后,可直接在其显示屏中进行展示,以供用户扫描登录。
步骤206、接收用户终端通过扫描展示的登录码发送的登录请求,并将所述登录请求发送至所述服务器,以使得所述服务器对所述登录请求进行登录权限审核后修改所述登录码的登录态。
在具体的实施过程中,登录用户可通过自己的用户终端如:智能手机扫描硬件设备中展示的登录码,向设备管理服务器发送登录请求。一般的,登录用户可通过用户终端中指定的应用程序扫描硬件设备中的登录码,当用户终端扫描硬件设备的登录码时,硬件终端可向设备管理服务器发送有用户请求登录信息。或,当用户终端扫描硬件设备的登录码时,自动向设备管理服务器触发登录请求。登录请求中可包括请求登录的登录用户的登录用户信息以及请求登录的硬件设备的设备标识,设备管理服务器可将登录请求中的登录用户信息与硬件设备关联配置的业务管理用户的用户信息进行匹配,判断登录 用户是否是该硬件设备配置的业务管理用户,若是,则确定该登录请求合法,登录请求审核通过,在设备管理服务器的数据库中将该硬件设备的登录码的登录态修改为已登录,同时,还可将硬件设备与登录用户信息进行关联,并记录了登录用户的信息。若登录请求审核不通过,则确定该登录请求不合法,拒绝请求。
步骤208、每隔预设时间轮询所述登录码的登录态,若所述登录码的登录态为已登录,则不再展示所述登录码。
在具体的实施过程中,硬件设备可每隔预设时间如1秒轮询如向设备管理服务器发送请求查询登录码的登录态,请求中可包括设备标识、登录码标识等信息。当硬件设备确定其登录码的登录态为已登录时,可不再展示该登录码,如:退出登录码的展示界面,直接展示其首页。若硬件设备确定登录码的登录态为未登录,则可继续在界面中展示登录码,等待用户登录。如:若登录用户退出登录,硬件设备轮询发现其登录码的登录态由已登录变为未登录,则重新在界面中展示登录码。登录用户可通过硬件设备退出登录,也可通过其扫描登录的手机终端选择退出登录,具体可由实际情况而定,本公开实施例不作具体限定。
本公开实施例提供的登录数据处理方法,通过为硬件设备下发登录码,用户通过扫描硬件设备中展示的登录码可快速登录硬件设备,不需要复杂的登录手续。并且,可基于硬件设备配置的业务管理用户和登录用户进行登录权限的校验,确保硬件设备的安全使用,实现硬件管理设备的安全快速登录。通过下发登录码的方式,使得用户可快速登录硬件设备,使用硬件设备进行业务办理,方便快捷的实现业务办理的数字化。同时,对于下发了登录码的硬件设备可统一管理,并且硬件设备本身不需要做改造,降低了成本,更具有适用性。
在上述实施例的基础上,本说明书一些实施例中,所述服务器对所述登录请求进行登录权限审核通过后,将所述登录码的登录态修改为已登录,并为登录用户颁发登录标识,所述登录标识与所述登录用户的登录用户信息进行关联,并将所述登录标识返回至硬件设备;所述方法还包括:接收业务请求,其中,所述业务请求中包括:设备标识、登录标识;将所述业务请求发送给所述服务器,以使得所述服务器根据所述设备标识对所述硬件设备进行校验,校验通过后,所述服务器基于所述登录标识获取所述硬件设备的登录与所述登录标识关联的登录用户信息,并对登录用户进行业务权限校验。
在具体的实施郭程程中,当用户扫描硬件设备登录码,并审核通过登录成功后,可为该登录用户颁发一个登录标识,将登录标识与登录用户的登录用户信息进行关联,同时将登录标识返回给硬件设备。当登录用户使用硬件设备进行业务办理,触发硬件设备向设备管理服务器发送业务请求时,业务请求中可包括登录标识、设备标识。设备管理服务器基于设备标识可对该硬件设备进行身份校验,确定硬件设备是否进行设备管理用户的绑定。当硬件设备校验成功后,可基于登录标识获取当前硬件设备的登录用户的登录用户信息,再基于登录用户信息进行登录用户的业务权限的校验,确定登录用户是否具有业务请求的业务内容的办理权限,若有,继续业务办理,若无,则拒绝请求。
本公开实施例在硬件设备登录成功后,为登录用户颁发登录标识,该登录标识可与登录用户的登录用户信息进行关联,以便能够快速获取登录用户的信息,对登录用户进行身份以及管理权限的校验,替身了数据处理效率。
图3是本说明书又一个实施例中登录数据处理方法的流程示意图,如图3所示,本 说明书一些实施例中可提供一种应用在用户终端侧的登录数据处理方法,该方法包括:
步骤302、向服务器发送设备绑定请求,所述设备绑定请求中包括硬件设备标识和设备管理用户信息,以使得所述服务器基于所述设备绑定请求为所述硬件设备关联所述设备管理用户信息。
在具体的实施过程中,可先向服务器即设备管理服务器发送登录码请求,可在硬件设备出厂前为硬件设备请求一个登录码。当硬件设备被用户购买使用时,使用之前,用户可通过用户终端对硬件设备进行设备绑定,即为该硬件设备绑定一个设备管理用户,该设备管理用户可对硬件设备的业务管理用户的用户信息以及管理权限进行编辑、修改。如:某超市准备对其拥有的POS设备进行数字化改造,通过连接设备管理服务器开放的接口为POS设备请求了一个登录码后,超市管理员可利用其手机客户端中的指定小程序或直接通过POS设备向设备管理服务器发送设备绑定请求。设备绑定请求中可包括设备标识以及需要绑定的设备管理用户信息,设备管理服务器接收到该设备绑定请求后,可为该POS设备绑定对应的设备管理用户,即该POS设备的所属权或管理权为设备管理用户拥有。
步骤304、接收所述服务器返回的设备绑定成功信息,基于所述设备管理用户信息向所述服务器发送用户配置请求,所述用户配置请求中包括业务管理用户信息,以使得所述服务器基于所述用户配置请求为所述硬件设备关联所述业务管理用户信息。
在具体的实施过程中,硬件设备的设备管理用户绑定成功后,用户终端上可接收到设备绑定成功的信息,设备管理用户可为该硬件设备配置业务管理用户以及业务管理用户的管理权限,具体可通过设备管理用户的用户终端中指定的小程序进行业务管理用户及其管理权限的配置,或直接在硬件设备中验证身份后在硬件设备中直接输入配置的业务管理用户及其管理权限。设备管理服务器即可在数据库或缓存中记录硬件设备绑定的设备管理用户信息以及业务管理用户信息。设备管理用户还可为各个业务管理用户配置管理权限,不同的业务管理用户使用硬件设备时有不同的业务权限。
步骤306、通过扫描所述硬件设备展示的登录码发送登录请求,所述登录请求中包括登录用户信息,以使得所述硬件设备将所述登录请求发送至所述服务器,所述服务器基于所述登录请求对所述硬件设备和所述登录用户信息进行校验。
在具体的实施过程中,设备管理用户以及业务管理用户均可通过扫描硬件设备中展示的登录码,触发硬件设备向设备管理服务器发送登录请求,登录请求中可包括请求登录的登录用户的登录用户信息以及请求登录的硬件设备的设备标识。设备管理服务器可将登录请求中的登录用户信息与硬件设备关联配置的业务管理用户的用户信息进行匹配,判断登录用户是否是该硬件设备配置的业务管理用户,若是,则确定该登录请求合法,登录请求审核通过,在设备管理服务器的数据库中将该硬件设备的登录码的登录态修改为已登录,同时,还可将硬件设备与登录用户信息进行关联,并记录了登录用户的信息。若登录请求审核不通过,则确定该登录请求不合法,拒绝请求。
需要说明的是,用户终端可是设备管理用户如商家的用户终端,也可是业务管理用户如店员的用户终端。
本公开实施例提供的登录数据处理方法,通过为硬件设备下发登录码,用户通过扫描硬件设备中展示的登录码可快速登录硬件设备,不需要复杂的登录手续。并且,可基于硬件设备配置的业务管理用户和登录用户进行登录权限的校验,确保硬件设备的安全 使用,实现硬件管理设备的安全快速登录。通过下发登录码的方式,使得用户可快速登录硬件设备,使用硬件设备进行业务办理,方便快捷的实现业务办理的数字化。同时,对于下发了登录码的硬件设备可统一管理,并且硬件设备本身不需要做改造,降低了成本,更具有适用性。
图4是本说明书一个示例中基于登录码进行硬件设备登录管理的流程示意图,下面结合图4,介绍本说明书一些示例中登录数据处理的过程:
1、设备端(即硬件设备)可调用设备管理服务器(如:云支付平台,预支付可理解为一种基于云计算架构,依托互联网和移动互联网的支付模式)登录码初始化接口拉取登录码。
1.1、云支付平台的鉴权中心,可给登录码下发一个qrcodeid即登录码标识,登录码标识可存入缓存系统。
1.2、同时,商家管理员即设备管理用户可在用户终端中的小程序进行业务管理用户的绑定,可通过小程序进入云支付平台的权限中心,增加店员,如:输入店员的手机号,并且设置店员权限,如退款密码设置权限等。
1.3、同时,商家可通过绑定设备,可在设备上绑定商家的信息。一般商家可先进行商家信息的绑定,再进行业务管理用户即店员的添加绑定。可通过用户终端的小程序或硬件设备接入到云支付平台的设备中心,为硬件设备绑定商家信息。
2、云支付平台在接收到硬件设备的登录码1请求后,可下发登录码url(Uniform Resource Locator,统一资源定位符),登录码为二维码时,设备端根据url完成二维码的渲染,二维码的码值内容可包括qrcodeid(登录码标识)、miniappurl(跳转地址)、qrcodestatus(登录态)等。
3、设备端可每1s轮询二维码的状态,判断二维码是否登录成功。如果登录成功,则二维码失效,不再展示二维码;如果登录未成功,则继续展示展示二维码。
4、店员通过用户终端中已经登录的指定的应用程序扫描登录码,可唤起云支付商家小程序,小程序可实现静默授权获取用户手机号功能。
5、店员静默确认登录后,云支付平台则修改云支付平台的鉴权中心的二维码状态为已登录,同时颁发一个logintoken即登录标识,且记录用户手机号,将登录用户的手机号与登录标识进行关联等。
6、设备端通过轮询二维码状态,获取到设备端中的登录码的登录标识logintoken且保存在本地做持久化。同时设备端在用户进行业务办理时,可向云支付平台发送业务请求,如首页配置项获取等。
7、业务请求中可包括设备身份信息如:deviceid设备标识、logintoken登录标识等。
8.1、云支付平台可根据业务请求中的logintoken在鉴权中心换取phonenum(用户的手机号码等身份信息),再根据phonenum去到云支付权限中心获取登录用户的权限。
8.2、根据deviceid去到设备绑定中心校验设备。
8.3、鉴权中心校验完成后,可返回用户信息即登录用户的用户信息。
9、如果业务请求为退款请求,带上用户信息,可在云支付平台的支付中心对用户信息做权限校验。
本公开实施例,通过下发登录码,用户可通过扫描硬件设备中的登录码进行登录,避免了下发密码、输入密码等线下操作复杂度的情况。通过调用开放的登录码接口,可 直接为硬件设备请求登录码,可适配多种智能设备的登录码开放方案,并且通过用户终端即可完成设备绑定,即可实现设备管理用户、业务管理用户的绑定,实现设备管理用户、业务管理用户均可扫码登录该设备,对设备原有系统及软件改造诉求低,适用性强,降低了数字化设备改造的成本。
本说明书中上述方法的各个实施例均采用递进的方式描述,各个实施例之间相同相似的部分互相参考即可,每个实施例重点说明的都是与其他实施例的不同之处。相关之处参考方法实施例的部分说明即可。
基于上述所述的登录数据处理方法,本说明书一个或多个实施例还提供一种用于登录数据处理的系统。所述系统可包括使用了本公开实施例所述方法的系统(包括分布式系统)、软件(应用)、模块、组件、服务器、客户端等并结合必要的实施硬件的装置。基于同一创新构思,本公开实施例提供的一个或多个实施例中的装置如下面的实施例所述。由于装置解决问题的实现方案与方法相似,因此本公开实施例具体的装置的实施可参考前述方法的实施,重复之处不再赘述。以下所使用的,术语“单元”或“模块”可实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现,但是硬件,或软件和硬件的组合的实现也是可能并被构想的。
具体地,图5是本说明书提供的登录数据处理装置一个实施例的模块结构示意图,该装置即可立即为上述实施例中的设备管理服务器,如图5所示,本说明书中提供的登录数据处理装置可包括:登录码返回模块51,可用于根据接收到的登录码请求向硬件设备返回登录码;用户配置模块52,可用于根据接收到的用户配置请求为所述硬件设备配置业务管理用户;登录请求接收模块53,可用于接收用户终端通过扫描所述硬件设备中的登录码发送的登录请求;登录权限审核模块54,可用于根据所述登录请求对应的登录用户信息和所述硬件设备配置的业务管理用户,对所述登录请求进行登录权限审核;登录态修改模块55,可用于在所述登录请求的登录权限审核通过时,修改所述登录码的登录态为已登录,并将所述硬件设备与所述登录用户信息进行关联。
本公开实施例提供的登录数据处理装置,过为硬件设备下发登录码,用户通过扫描硬件设备中展示的登录码可快速登录硬件设备,不需要复杂的登录手续。并且,可基于硬件设备配置的业务管理用户和登录用户进行登录权限的校验,确保硬件设备的安全使用,实现硬件管理设备的安全快速登录。通过下发登录码的方式,使得用户可快速登录硬件设备,使用硬件设备进行业务办理,方便快捷的实现业务办理的数字化。同时,对于下发了登录码的硬件设备可统一管理,并且直接通过开放的接口下发登录码,硬件设备本身不需要做改造,降低了成本,更具有适用性。
本说明书一些实施例中,所述用户配置模块具体用于:根据接收到的用户配置请求为所述硬件设备配置业务管理用户以及所述业务管理用户对应的管理权限;所述装置还包括业务请求接收模块,用于:接收所述硬件设备发送的业务请求;根据所述业务请求,获取所述硬件设备对应的登录用户信息;根据所述登录用户信息对应的登录用户的管理权限,对所述业务请求进行业务权限校验。
本公开实施例提供的登录数据处理装置,通过配置业务管理用户的管理权限,在业务管理用户使用硬件设备进行业务办理时,校验其是否具有该业务办理的业务权限,确保了硬件设备的安全使用。
本说明书一些实施例中,所述装置还包括设备绑定模块用于:接收设备绑定请求, 根据所述设备绑定请求为所述硬件设备绑定设备管理用户信息;所述业务请求接收模块接收到的所述业务请求中包括:设备标识;所述业务请求接收模块还用于:根据所述设备标识,判断所述硬件设备是否绑定有设备管理用户信息,若是,则确定所述硬件设备校验通过,获取所述硬件设备的登录用户信息。
本公开实施例提供的登录数据处理装置,硬件设备在使用前可进行设备管理用户的绑定,在进行业务办理时,可基于设备标识确定该硬件设备是否进行设备管理用户的绑定,对硬件设备进行身份校验。只有绑定了设备管理用户的硬件设备才允许进行业务办理,为后续硬件设备的风险识别等奠定了数据基础,确保硬件设备安全使用,便于对硬件设备进行安全管理。
本说明书一些实施例中,所述登录态修改模块还用于:对所述登录请求审核通过后,为所述登录用户颁发登录标识,将所述登录标识返回至所述硬件设备,并将所述登录标识与所述登录用户的登录用户信息进行关联;接收到硬件设备发送的所述业务请求中包括:登录标识;所述业务请求接收模块具体用于:根据所述登录标识,获取与所述登录标识关联的登录用户信息。
本公开实施例在硬件设备登录成功后,为登录用户颁发登录标识,该登录标识可与登录用户的登录用户信息进行关联,以便能够快速获取登录用户的信息,对登录用户进行身份以及管理权限的校验,替身了数据处理效率。
图6是本说明书提供的登录数据处理装置一个实施例的模块结构示意图,该装置即可立即为上述实施例中的硬件设备,如图6所示,本说明书中提供的登录数据处理装置可包括:登录码请求模块61,用于通过服务器开放的登录码接口向所述服务器发送登录码请求;登录码接收模块62,用于接收所述服务器基于所述登录码请求下发的登录码;登录请求发送模块63,用于接收用户终端通过扫描展示的登录码发送的登录请求,并将所述登录请求发送至所述服务器,以使得所述服务器对所述登录请求进行登录权限审核后修改所述登录码的登录态;登录态轮询模块64,用于每隔预设时间轮询所述登录码的登录态,若所述登录码的登录态为已登录,则不再展示所述登录码。
本公开实施例提供的登录数据处理装置,通过为硬件设备下发登录码,用户通过扫描硬件设备中展示的登录码可快速登录硬件设备,不需要复杂的登录手续。并且,可基于硬件设备配置的业务管理用户和登录用户进行登录权限的校验,确保硬件设备的安全使用,实现硬件管理设备的安全快速登录。通过下发登录码的方式,使得用户可快速登录硬件设备,使用硬件设备进行业务办理,方便快捷的实现业务办理的数字化。同时,对于下发了登录码的硬件设备可统一管理,并且硬件设备本身不需要做改造,降低了成本,更具有适用性。
本说明书一些实施例中,所述服务器对所述登录请求进行登录权限审核通过后,将所述登录码的登录态修改为已登录,并为登录用户颁发登录标识,所述登录标识与所述登录用户的登录用户信息进行关联,并将所述登录标识返回至硬件设备;所述装置还包括业务处理模块用于:接收业务请求,其中,所述业务请求中包括:设备标识、登录标识;将所述业务请求发送给所述服务器,以使得所述服务器根据所述设备标识对所述硬件设备进行校验,校验通过后,所述服务器基于所述登录标识获取所述硬件设备的登录与所述登录标识关联的登录用户信息,并对登录用户进行业务权限校验。
本公开实施例提供的登录数据处理装置,在硬件设备登录成功后,为登录用户颁发 登录标识,该登录标识可与登录用户的登录用户信息进行关联,以便能够快速获取登录用户的信息,对登录用户进行身份以及管理权限的校验,替身了数据处理效率。
图7是本说明书提供的登录数据处理装置一个实施例的模块结构示意图,该装置即可立即为上述实施例中的用户终端,如图7所示,本说明书中提供的登录数据处理装置可包括:设备绑定请求模块71,用于向服务器发送设备绑定请求,所述设备绑定请求中包括硬件设备标识和设备管理用户信息,以使得所述服务器基于所述设备绑定请求为所述硬件设备关联所述设备管理用户信息;设备配置模块72,用于接收所述服务器返回的设备绑定成功信息,基于所述设备管理用户信息向所述服务器发送用户配置请求,所述用户配置请求中包括业务管理用户信息,以使得所述服务器基于所述用户配置请求为所述硬件设备关联所述业务管理用户信息;登录请求模块73,用于通过扫描所述硬件设备展示的登录码发送登录请求,所述登录请求中包括登录用户信息,以使得所述硬件设备将所述登录请求发送至所述服务器,所述服务器基于所述登录请求对所述硬件设备和所述登录用户信息进行校验。
本公开实施例提供的登录数据处理装置,通过为硬件设备下发登录码,用户通过扫描硬件设备中展示的登录码可快速登录硬件设备,不需要复杂的登录手续。并且,可基于硬件设备配置的业务管理用户和登录用户进行登录权限的校验,确保硬件设备的安全使用,实现硬件管理设备的安全快速登录。通过下发登录码的方式,使得用户可快速登录硬件设备,使用硬件设备进行业务办理,方便快捷的实现业务办理的数字化。同时,对于下发了登录码的硬件设备可统一管理,并且硬件设备本身不需要做改造,降低了成本,更具有适用性。
需要说明的,上述所述的装置根据对应方法实施例的描述还可包括其他的实施方式。具体的实现方式可参照上述对应的方法实施例的描述,在此不作一一赘述。
本公开实施例还提供一种登录数据处理设备,包括:至少一个处理器以及用于存储处理器可执行指令的存储器,所述处理器执行所述指令时实现上述实施例的信息推荐数据处理方法,如:根据接收到的登录码请求向硬件设备返回登录码;根据接收到的用户配置请求为所述硬件设备配置业务管理用户;接收用户终端通过扫描所述硬件设备中的登录码发送的登录请求;根据所述登录请求对应的登录用户信息和所述硬件设备配置的业务管理用户,对所述登录请求进行登录权限审核;若审核通过,则修改所述登录码的登录态为已登录,并将所述硬件设备与所述登录用户信息进行关联。
或,通过服务器开放的登录码接口向所述服务器发送登录码请求;接收所述服务器基于所述登录码请求下发的登录码;接收用户终端通过扫描展示的登录码发送的登录请求,并将所述登录请求发送至所述服务器,以使得所述服务器对所述登录请求进行登录权限审核后修改所述登录码的登录态;每隔预设时间轮询所述登录码的登录态,若所述登录码的登录态为已登录,则不再展示所述登录码。
或,向服务器发送设备绑定请求,所述设备绑定请求中包括硬件设备标识和设备管理用户信息,以使得所述服务器基于所述设备绑定请求为所述硬件设备关联所述设备管理用户信息;接收所述服务器返回的设备绑定成功信息,基于所述设备管理用户信息向所述服务器发送用户配置请求,所述用户配置请求中包括业务管理用户信息,以使得所述服务器基于所述用户配置请求为所述硬件设备关联所述业务管理用户信息;通过扫描所述硬件设备展示的登录码发送登录请求,所述登录请求中包括登录用户信息,以使得 所述硬件设备将所述登录请求发送至所述服务器,所述服务器基于所述登录请求对所述硬件设备和所述登录用户信息进行校验。
本公开实施例还提供一种登录数据处理系统,包括设备管理服务器、硬件设备、至少一个用户终端。其中,所述设备管理服务器中包括至少一个处理器以及用于存储处理器可执行指令的存储器,所述处理器执行所述指令时实现上述设备管理服务器侧执行的方法,用于为所述硬件设备下发登录码,基于所述登录码对所述硬件设备进行管理;所述硬件设备中包括至少一个处理器以及用于存储处理器可执行指令的存储器,所述处理器执行所述指令时实现上述硬件设备侧执行的方法,用于展示所述设备管理服务器提供的登录码,供所述用户终端扫描以登录所述硬件设备;所述用户终端包括至少一个处理器以及用于存储处理器可执行指令的存储器,所述处理器执行所述指令时实现上述用户终端侧执行的方法,用于通过扫描所述硬件设备展示的登录码,登录所述硬件设备。可是设备管理用户的用户终端,也可是业务管理用户的用户终端。
需要说明的,上述所述的设备和系统根据方法实施例的描述还可包括其他的实施方式。具体的实现方式可参照相关方法实施例的描述,在此不作一一赘述。
本说明书提供的登录数据处理装置,也可应用在多种数据分析处理系统中。所述系统或服务器或终端或设备可为单独的服务器,也可包括使用了本说明书的一个或多个所述方法或一个或多个实施例系统或服务器或终端或设备的服务器集群、系统(包括分布式系统)、软件(应用)、实际操作装置、逻辑门电路装置、量子计算机等并结合必要的实施硬件的终端装置。所述核对差异数据的检测系统可包括至少一个处理器以及存储计算机可执行指令的存储器,所述处理器执行所述指令时实现上述任意一个或多个实施例中所述方法的步骤。
本公开实施例所提供的方法实施例可在移动终端、计算机终端、服务器或类似的运算装置中执行。以运行在服务器上为例,图8是本说明书一个实施例中登录数据处理服务器的硬件结构框图,该计算机终端可是上述实施例中的登录数据处理服务器或登录数据处理装置。如图8所示服务器10可包括一个或多个(图中仅示出一个)处理器100(处理器100可包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)、用于存储数据的非易失性存储器200、以及用于通信功能的传输模块300。本领域普通技术人员可理解,图8所示的结构仅为示意,其并不对上述电子装置的结构造成限定。例如,服务器10还可包括比图8中所示更多或更少的组件,例如还可包括其他的处理硬件,如数据库或多级缓存、GPU,或具有与图8所示不同的配置。
非易失性存储器200可用于存储应用软件的软件程序及模块,如本公开实施例中的登录数据处理方法对应的程序指令/模块,处理器100通过运行存储在非易失性存储器200内的软件程序以及模块,从而执行各种功能应用以及资源数据更新。非易失性存储器200可包括高速随机存储器,还可包括非易失性存储器,如一个或多个磁性存储装置、闪存、或其他非易失性固态存储器。在一些实例中,非易失性存储器200可进一步包括相对于处理器100远程设置的存储器,这些远程存储器可通过网络连接至计算机终端。上述网络的实例包括但不限于互联网、企业内部网、局与网、移动通信网及其组合。
传输模块300用于经由一个网络接收或发送数据。上述的网络具体实例可包括计算机终端的通信供应商提供的无线网络。在一个实例中,传输模块300包括一个网络适配器(Network Interface Controller,NIC),其可通过基站与其他网络设备相连从而可与 互联网进行通讯。在一个实例中,传输模块300可为射频(Radio Frequency,RF)模块,其用于通过无线方式与互联网进行通讯。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下,在权利要求书中记载的动作或步骤可按照不同于实施例中的顺序来执行并且仍然可实现期望的结果。另外,在附图中描绘的过程不一定要求示出的特定顺序或连续顺序才能实现期望的结果。在某些实施方式中,多任务处理和并行处理也是可的或可能是有利的。
本说明书提供的上述实施例所述的方法或装置可通过计算机程序实现业务逻辑并记录在存储介质上,所述的存储介质可计算机读取并执行,实现本公开实施例所描述方案的效果,如:根据接收到的登录码请求向硬件设备返回登录码;根据接收到的用户配置请求为所述硬件设备配置业务管理用户;接收用户终端通过扫描所述硬件设备中的登录码发送的登录请求;根据所述登录请求对应的登录用户信息和所述硬件设备配置的业务管理用户,对所述登录请求进行登录权限审核;若审核通过,则修改所述登录码的登录态为已登录,并将所述硬件设备与所述登录用户信息进行关联。
或,通过服务器开放的登录码接口向所述服务器发送登录码请求;接收所述服务器基于所述登录码请求下发的登录码;接收用户终端通过扫描展示的登录码发送的登录请求,并将所述登录请求发送至所述服务器,以使得所述服务器对所述登录请求进行登录权限审核后修改所述登录码的登录态;每隔预设时间轮询所述登录码的登录态,若所述登录码的登录态为已登录,则不再展示所述登录码。
或,向服务器发送设备绑定请求,所述设备绑定请求中包括硬件设备标识和设备管理用户信息,以使得所述服务器基于所述设备绑定请求为所述硬件设备关联所述设备管理用户信息;接收所述服务器返回的设备绑定成功信息,基于所述设备管理用户信息向所述服务器发送用户配置请求,所述用户配置请求中包括业务管理用户信息,以使得所述服务器基于所述用户配置请求为所述硬件设备关联所述业务管理用户信息;通过扫描所述硬件设备展示的登录码发送登录请求,所述登录请求中包括登录用户信息,以使得所述硬件设备将所述登录请求发送至所述服务器,所述服务器基于所述登录请求对所述硬件设备和所述登录用户信息进行校验。
所述存储介质可包括用于存储信息的物理装置,通常是将信息数字化后再以利用电、磁或光学等方式的媒体加以存储。所述存储介质有可包括:利用电能方式存储信息的装置如,各式存储器,如RAM、ROM等;利用磁能方式存储信息的装置如,硬盘、软盘、磁带、磁芯存储器、磁泡存储器、U盘;利用光学方式存储信息的装置如,CD或DVD。当然,还有其他方式的可读存储介质,例如量子存储器、石墨烯存储器等等。
本公开实施例提供的上述登录数据处理方法或装置可在计算机中由处理器执行相应的程序指令来实现,如使用windows操作系统的c++语言在PC端实现、linux系统实现,或其他例如使用android、iOS系统程序设计语言在智能终端实现,以及基于量子计算机的处理逻辑实现等。
需要说明的是说明书上述所述的装置、计算机存储介质、系统根据相关方法实施例的描述还可包括其他的实施方式,具体的实现方式可参照对应方法实施例的描述,在此不作一一赘述。
本说明书中的各个实施例均采用递进的方式描述,各个实施例之间相同相似的 部分互相参考即可,每个实施例重点说明的都是与其他实施例的不同之处。尤其,对于硬件+程序类实施例而言,由于其基本相似于方法实施例,所以描述的比较简单,相关之处参考方法实施例的部分说明即可。
本公开实施例并不局限于必须是符合行业通信标准、标准计算机资源数据更新和数据存储规则或本说明书一个或多个实施例所描述的情况。某些行业标准或使用自定义方式或实施例描述的实施基础上略加修改后的实施方案也可实现上述实施例相同、等同或相近、或变形后可预料的实施效果。应用这些修改或变形后的数据获取、存储、判断、处理方式等获取的实施例,仍然可属于本公开实施例的可选实施方案范围之内。
在20世纪90年代,对于一个技术的改进可很明显地区分是硬件上的改进(例如,对二极管、晶体管、开关等电路结构的改进)还是软件上的改进(对于方法流程的改进)。然而,随着技术的发展,当今的很多方法流程的改进已经可视为硬件电路结构的直接改进。设计人员几乎都通过将改进的方法流程编程到硬件电路中来得到相应的硬件电路结构。因此,不能说一个方法流程的改进就不能用硬件实体模块来实现。例如,可编程逻辑器件(Programmable Logic Device,PLD)(例如现场可编程门阵列(Field Programmable Gate Array,FPGA))就是这样一种集成电路,其逻辑功能由用户对器件编程来确定。由设计人员自行编程来把一个数字系统“集成”在一片PLD上,而不需要请芯片制造厂商来设计和制作专用的集成电路芯片。而且,如今,取代手工地制作集成电路芯片,这种编程也多半改用“逻辑编译器(logic compiler)”软件来实现,它与程序开发撰写时所用的软件编译器相类似,而要编译之前的原始代码也得用特定的编程语言来撰写,此称之为硬件描述语言(Hardware Description Language,HDL),而HDL也并非仅有一种,而是有许多种,如ABEL(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description Language)、Confluence、CUPL(Cornell University Programming Language)、HDCal、JHDL(Java Hardware Description Language)、Lava、Lola、MyHDL、PALASM、RHDL(Ruby Hardware Description Language)等,目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description Language)与Verilog。本领域技术人员也应该清楚,只需要将方法流程用上述几种硬件描述语言稍作逻辑编程并编程到集成电路中,就可很容易得到实现该逻辑方法流程的硬件电路。
控制器可按任何适当的方式实现,例如,控制器可采取例如微处理器或处理器以及存储可由该(微)处理器执行的计算机可读程序代码(例如软件或固件)的计算机可读介质、逻辑门、开关、专用集成电路(Application Specific Integrated Circuit,ASIC)、可编程逻辑控制器和嵌入微控制器的形式,控制器的例子包括但不限于以下微控制器:ARC 625D、Atmel AT91SAM、Microchip PIC18F26K20以及Silicone Labs C8051F320,存储器控制器还可被实现为存储器的控制逻辑的一部分。本领域技术人员也知道,除了以纯计算机可读程序代码方式实现控制器以外,完全可通过将方法步骤进行逻辑编程来使得控制器以逻辑门、开关、专用集成电路、可编程逻辑控制器和嵌入微控制器等的形式来实现相同功能。因此这种控制器可被认为是一种硬件部件,而对其内包括的用于实现各种功能的装置也可视为硬件部件内的结构。或甚至,可将用于实现各种功能的装置视为既可是实现方法的软件模块又可是硬件部件内的结构。
上述实施例阐明的系统、装置、模块或单元,具体可由计算机芯片或实体实现,或由具有某种功能的产品来实现。一种典型的实现设备为计算机。具体的,计算机例如 可为个人计算机、膝上型计算机、车载人机交互设备、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件设备、游戏控制台、平板计算机、可穿戴设备或这些设备中的任何设备的组合。
虽然本说明书一个或多个实施例提供了如实施例或流程图所述的方法操作步骤,但基于常规或无创造性的手段可包括更多或更少的操作步骤。实施例中列举的步骤顺序仅仅为众多步骤执行顺序中的一种方式,不代表唯一的执行顺序。在实际中的装置或终端产品执行时,可按照实施例或附图所示的方法顺序执行或并行执行(例如并行处理器或多线程处理的环境,甚至为分布式资源数据更新环境)。术语“包括”、“包含”或其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、产品或设备不仅包括那些要素,而且还包括没有明确列出的其他要素,或是还包括为这种过程、方法、产品或设备所固有的要素。在没有更多限制的情况下,并不排除在包括所述要素的过程、方法、产品或设备中还存在另外的相同或等同要素。第一,第二等词语用来表示名称,而并不表示任何特定的顺序。
为了描述的方便,描述以上装置时以功能分为各种模块分别描述。当然,在实施本说明书一个或多个时可把各模块的功能在同一个或多个软件和/或硬件中实现,也可将实现同一功能的模块由多个子模块或子单元的组合实现等。以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可有另外的划分方式,例如多个单元或组件可结合或可集成到另一个系统,或一些特征可忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可是通过一些接口,装置或单元的间接耦合或通信连接,可是电性,机械或其它的形式。
本发明是参照根据本发明实施例的方法、装置(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程资源数据更新设备的处理器以产生一个机器,使得通过计算机或其他可编程资源数据更新设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程资源数据更新设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程资源数据更新设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中,计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。内存可能包括计算机可读介质中的非永久性存储器,随机存取存储器(RAM)和/或非易失性内存等形式,如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可由任何方法或技术来实现信息存储。信息可是计算机可读指令、数据结构、程序的模 块或其他数据。计算机的存储介质的例子包括,但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带,磁带磁磁盘存储、石墨烯存储或其他磁性存储设备或任何其他非传输介质,可用于存储可被计算设备访问的信息。按照本文中的界定,计算机可读介质不包括暂存电脑可读媒体(transitory media),如调制的数据信号和载波。
本领域技术人员应明白,本说明书一个或多个实施例可提供为方法、系统或计算机程序产品。因此,本说明书一个或多个实施例可采用完全硬件实施例、完全软件实施例或结合软件和硬件方面的实施例的形式。而且,本说明书一个或多个实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本说明书一个或多个实施例可在由计算机执行的计算机可执行指令的一般上下文中描述,例如程序模块。一般地,程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可在分布式计算环境中实践本本说明书一个或多个实施例,在这些分布式计算环境中,由通过通信网络而被连接的远程设备来执行任务。在分布式计算环境中,程序模块可位于包括存储设备在内的本地和远程计算机存储介质中。
本说明书中的各个实施例均采用递进的方式描述,各个实施例之间相同相似的部分互相参考即可,每个实施例重点说明的都是与其他实施例的不同之处。尤其,对于系统实施例而言,由于其基本相似于方法实施例,所以描述的比较简单,相关之处参考方法实施例的部分说明即可。在本说明书的描述中,参考术语“一个实施例”、“一些实施例”、“示例”、“具体示例”、或“一些示例”等的描述意指结合该实施例或示例描述的具体特征、结构、材料或特点包含于本说明书的至少一个实施例或示例中。在本说明书中,对上述术语的示意性表述不必须针对的是相同的实施例或示例。而且,描述的具体特征、结构、材料或特点可在任一个或多个实施例或示例中以合适的方式结合。此外,在不相互矛盾的情况下,本领域的技术人员可将本说明书中描述的不同实施例或示例以及不同实施例或示例的特征进行结合和组合。
以上所述仅为本说明书一个或多个实施例的实施例而已,并不用于限制本说明书一个或多个实施例。对于本领域技术人员来说,本说明书一个或多个实施例可有各种更改和变化。凡在本说明书的精神和原理之内所作的任何修改、等同替换、改进等,均应包含在权利要求范围之内。

Claims (16)

  1. 一种登录数据处理方法,所述方法包括:
    根据接收到的登录码请求向硬件设备返回登录码;
    根据接收到的用户配置请求为所述硬件设备配置业务管理用户;
    接收用户终端通过扫描所述硬件设备中的登录码发送的登录请求;
    根据所述登录请求对应的登录用户信息和所述硬件设备配置的业务管理用户,对所述登录请求进行登录权限审核;
    若审核通过,则修改所述登录码的登录态为已登录,并将所述硬件设备与所述登录用户信息进行关联。
  2. 如权利要求1所述的方法,
    所述根据接收到的用户配置请求为所述硬件设备配置业务管理用户,包括:根据接收到的用户配置请求为所述硬件设备配置业务管理用户以及所述业务管理用户对应的管理权限;
    所述方法还包括:
    接收所述硬件设备发送的业务请求;
    根据所述业务请求,获取所述硬件设备对应的登录用户信息;
    根据所述登录用户信息对应的登录用户的管理权限,对所述业务请求进行业务权限校验。
  3. 如权利要求2所述的方法,所述方法还包括:
    接收设备绑定请求,根据所述设备绑定请求为所述硬件设备绑定设备管理用户信息;
    接收到的所述业务请求中包括:设备标识;
    所述方法还包括:
    根据所述设备标识,判断所述硬件设备是否绑定有设备管理用户信息,若是,则确定所述硬件设备校验通过,获取所述硬件设备的登录用户信息。
  4. 如权利要求2所述的方法,所述方法还包括:
    对所述登录请求审核通过后,为所述登录用户颁发登录标识,将所述登录标识返回至所述硬件设备,并将所述登录标识与所述登录用户的登录用户信息进行关联;
    接收到的所述业务请求中包括:登录标识;
    所述根据所述业务请求,获取所述硬件设备对应的登录用户信息,包括:
    根据所述登录标识,获取与所述登录标识关联的登录用户信息。
  5. 一种登录数据处理方法,所述方法包括:
    通过服务器开放的登录码接口向所述服务器发送登录码请求;
    接收所述服务器基于所述登录码请求下发的登录码;
    接收用户终端通过扫描展示的登录码发送的登录请求,并将所述登录请求发送至所述服务器,以使得所述服务器对所述登录请求进行登录权限审核后修改所述登录码的登录态;
    每隔预设时间轮询所述登录码的登录态,若所述登录码的登录态为已登录,则不再展示所述登录码。
  6. 如权利要求5所述的方法,所述服务器对所述登录请求进行登录权限审核通过后,将所述登录码的登录态修改为已登录,并为登录用户颁发登录标识,所述登录标识 与所述登录用户的登录用户信息进行关联,并将所述登录标识返回至硬件设备;
    所述方法还包括:
    接收业务请求,其中,所述业务请求中包括:设备标识、登录标识;
    将所述业务请求发送给所述服务器,以使得所述服务器根据所述设备标识对所述硬件设备进行校验,校验通过后,所述服务器基于所述登录标识获取所述硬件设备的登录与所述登录标识关联的登录用户信息,并对登录用户进行业务权限校验。
  7. 一种登录数据处理方法,包括:
    向服务器发送设备绑定请求,所述设备绑定请求中包括硬件设备标识和设备管理用户信息,以使得所述服务器基于所述设备绑定请求为所述硬件设备关联所述设备管理用户信息;
    接收所述服务器返回的设备绑定成功信息,基于所述设备管理用户信息向所述服务器发送用户配置请求,所述用户配置请求中包括业务管理用户信息,以使得所述服务器基于所述用户配置请求为所述硬件设备关联所述业务管理用户信息;
    通过扫描所述硬件设备展示的登录码发送登录请求,所述登录请求中包括登录用户信息,以使得所述硬件设备将所述登录请求发送至所述服务器,所述服务器基于所述登录请求对所述硬件设备和所述登录用户信息进行校验。
  8. 一种登录数据处理装置,包括:
    登录码返回模块,用于根据接收到的登录码请求向硬件设备返回登录码;
    用户配置模块,用于根据接收到的用户配置请求为所述硬件设备配置业务管理用户;
    登录请求接收模块,用于接收用户终端通过扫描所述硬件设备中的登录码发送的登录请求;
    登录权限审核模块,用于根据所述登录请求对应的登录用户信息和所述硬件设备配置的业务管理用户,对所述登录请求进行登录权限审核;
    登录态修改模块,用于在所述登录请求的登录权限审核通过时,修改所述登录码的登录态为已登录,并将所述硬件设备与所述登录用户信息进行关联。
  9. 如权利要求8所述的装置,
    所述用户配置模块具体用于:根据接收到的用户配置请求为所述硬件设备配置业务管理用户以及所述业务管理用户对应的管理权限;
    所述装置还包括业务请求接收模块,用于:
    接收所述硬件设备发送的业务请求;
    根据所述业务请求,获取所述硬件设备对应的登录用户信息;
    根据所述登录用户信息对应的登录用户的管理权限,对所述业务请求进行业务权限校验。
  10. 如权利要求9所述的装置,所述装置还包括:设备绑定模块,用于:接收设备绑定请求,根据所述设备绑定请求为所述硬件设备绑定设备管理用户信息;
    所述业务请求接收模块接收到的所述业务请求中包括:设备标识;
    所述业务请求接收模块还用于:根据所述设备标识,判断所述硬件设备是否绑定有设备管理用户信息,若是,则确定所述硬件设备校验通过,获取所述硬件设备的登录用户信息。
  11. 如权利要求9所述的装置,所述登录态修改模块还用于:对所述登录请求审核 通过后,为所述登录用户颁发登录标识,将所述登录标识返回至所述硬件设备,并将所述登录标识与所述登录用户的登录用户信息进行关联;
    接收到硬件设备发送的所述业务请求中包括:登录标识;
    所述业务请求接收模块具体用于:根据所述登录标识,获取与所述登录标识关联的登录用户信息。
  12. 一种登录数据处理装置,包括:
    登录码请求模块,用于通过服务器开放的登录码接口向所述服务器发送登录码请求;
    登录码接收模块,用于接收所述服务器基于所述登录码请求下发的登录码;
    登录请求发送模块,用于接收用户终端通过扫描展示的登录码发送的登录请求,并将所述登录请求发送至所述服务器,以使得所述服务器对所述登录请求进行登录权限审核后修改所述登录码的登录态;
    登录态轮询模块,用于每隔预设时间轮询所述登录码的登录态,若所述登录码的登录态为已登录,则不再展示所述登录码。
  13. 如权利要求12所述的装置,所述服务器对所述登录请求进行登录权限审核通过后,将所述登录码的登录态修改为已登录,并为登录用户颁发登录标识,所述登录标识与所述登录用户的登录用户信息进行关联,并将所述登录标识返回至硬件设备;
    所述装置还包括业务处理模块用于:
    接收业务请求,其中,所述业务请求中包括设备标识、登录标识;
    将所述业务请求发送给所述服务器,以使得所述服务器根据所述设备标识对所述硬件设备进行校验,校验通过后,所述服务器基于所述登录标识获取所述硬件设备的登录与所述登录标识关联的登录用户信息,并对登录用户进行业务权限校验。
  14. 一种登录数据处理装置,包括:
    设备绑定请求模块,用于向服务器发送设备绑定请求,所述设备绑定请求中包括硬件设备标识和设备管理用户信息,以使得所述服务器基于所述设备绑定请求为所述硬件设备关联所述设备管理用户信息;
    设备配置模块,用于接收所述服务器返回的设备绑定成功信息,基于所述设备管理用户信息向所述服务器发送用户配置请求,所述用户配置请求中包括业务管理用户信息,以使得所述服务器基于所述用户配置请求为所述硬件设备关联所述业务管理用户信息;
    登录请求模块,用于通过扫描所述硬件设备展示的登录码发送登录请求,所述登录请求中包括登录用户信息,以使得所述硬件设备将所述登录请求发送至所述服务器,所述服务器基于所述登录请求对所述硬件设备和所述登录用户信息进行校验。
  15. 一种登录数据处理设备,包括至少一个处理器及用于存储处理器可执行指令的存储器,所述处理器执行所述指令时实现权利要求1至7任一项所述的方法。
  16. 一种登录数据处理系统,包括设备管理服务器、硬件设备、至少一个用户终端,
    所述设备管理服务器中包括至少一个处理器以及用于存储处理器可执行指令的存储器,所述处理器执行所述指令时实现权利要求1至4任一项所述的方法,用于为所述硬件设备下发登录码,基于所述登录码对所述硬件设备进行管理;
    所述硬件设备中包括至少一个处理器以及用于存储处理器可执行指令的存储器,所述处理器执行所述指令时实现权利要求5至6任一项所述的方法,用于展示所述设备管理服务器提供的登录码,供所述用户终端扫描以登录所述硬件设备;
    所述用户终端包括至少一个处理器以及用于存储处理器可执行指令的存储器,所述处理器执行所述指令时实现权利要求7所述的方法,用于通过扫描所述硬件设备展示的登录码,登录所述硬件设备。
PCT/CN2021/097259 2020-06-01 2021-05-31 登录数据处理方法、装置、设备及系统 WO2021244474A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010484895.6 2020-06-01
CN202010484895.6A CN111651746B (zh) 2020-06-01 2020-06-01 登录数据处理方法、装置、设备及系统

Publications (1)

Publication Number Publication Date
WO2021244474A1 true WO2021244474A1 (zh) 2021-12-09

Family

ID=72349741

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/097259 WO2021244474A1 (zh) 2020-06-01 2021-05-31 登录数据处理方法、装置、设备及系统

Country Status (2)

Country Link
CN (1) CN111651746B (zh)
WO (1) WO2021244474A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114499946A (zh) * 2021-12-22 2022-05-13 新华三信息技术有限公司 一种登录管理方法、装置、设备及机器可读存储介质
CN114565066A (zh) * 2021-12-24 2022-05-31 国能日新科技股份有限公司 基于电力市场交易系统隔离网数据采集方法和装置

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111651746B (zh) * 2020-06-01 2023-03-10 支付宝(杭州)信息技术有限公司 登录数据处理方法、装置、设备及系统
CN112667985A (zh) * 2020-12-31 2021-04-16 深兰盛视科技(苏州)有限公司 巴枪控制方法、装置、巴枪及计算机可读存储介质
CN112948800B (zh) * 2021-02-26 2024-04-12 北京北大千方科技有限公司 一种二维码登录信号机管理平台方法、装置、设备及介质
CN114547569A (zh) * 2022-02-11 2022-05-27 支付宝(杭州)信息技术有限公司 账户登录处理方法及装置
CN116436707B (zh) * 2023-06-14 2023-08-25 北京创新乐知网络技术有限公司 基于小程序的登录方法、装置、介质及计算机设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107580002A (zh) * 2017-10-24 2018-01-12 杭州安恒信息技术有限公司 双因子认证安全管理机登录系统及方法
US20190320080A1 (en) * 2018-04-11 2019-10-17 Canon Kabushiki Kaisha Information processing system and control method
CN110730153A (zh) * 2018-07-16 2020-01-24 阿里巴巴集团控股有限公司 云设备的账号配置方法、装置和系统、数据处理方法
CN111651746A (zh) * 2020-06-01 2020-09-11 支付宝(杭州)信息技术有限公司 登录数据处理方法、装置、设备及系统

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103001975B (zh) * 2012-12-26 2016-12-28 百度在线网络技术(北京)有限公司 基于二维码的登录控制方法、系统和装置
CN103001973B (zh) * 2012-12-26 2016-08-31 百度在线网络技术(北京)有限公司 基于二维码的登录控制方法、系统和装置
CN104639549B (zh) * 2015-02-05 2018-09-04 小米科技有限责任公司 设备绑定方法和装置
CN106341233A (zh) * 2015-07-08 2017-01-18 阿里巴巴集团控股有限公司 客户端登录服务器端的鉴权方法、装置、系统及电子设备
CN106936803B (zh) * 2015-12-31 2020-12-29 亿阳安全技术有限公司 二维码扫描认证登录方法及相关装置
CN106339623B (zh) * 2016-08-26 2019-05-10 金蝶软件(中国)有限公司 登录方法和装置
CN107241431A (zh) * 2017-07-04 2017-10-10 深圳市青葡萄科技有限公司 基于二维码实现的扫码登录虚拟桌面的方法及系统
CN109842600B (zh) * 2017-11-29 2021-08-17 中国移动通信集团山西有限公司 一种实现移动办公的方法、终端设备及mdm设备
CN108200040A (zh) * 2017-12-28 2018-06-22 北京奇虎科技有限公司 移动客户端免密登录的方法、系统、浏览器及移动终端
CN110166427B (zh) * 2019-04-11 2020-06-02 口碑(上海)信息技术有限公司 商家管理设备使用的安全处理方法、装置及系统
CN111159673B (zh) * 2019-12-31 2022-09-02 海南老白健康科技有限公司 身份信息验证方法、装置和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107580002A (zh) * 2017-10-24 2018-01-12 杭州安恒信息技术有限公司 双因子认证安全管理机登录系统及方法
US20190320080A1 (en) * 2018-04-11 2019-10-17 Canon Kabushiki Kaisha Information processing system and control method
CN110730153A (zh) * 2018-07-16 2020-01-24 阿里巴巴集团控股有限公司 云设备的账号配置方法、装置和系统、数据处理方法
CN111651746A (zh) * 2020-06-01 2020-09-11 支付宝(杭州)信息技术有限公司 登录数据处理方法、装置、设备及系统

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114499946A (zh) * 2021-12-22 2022-05-13 新华三信息技术有限公司 一种登录管理方法、装置、设备及机器可读存储介质
CN114499946B (zh) * 2021-12-22 2024-02-09 新华三信息技术有限公司 一种登录管理方法、装置、设备及机器可读存储介质
CN114565066A (zh) * 2021-12-24 2022-05-31 国能日新科技股份有限公司 基于电力市场交易系统隔离网数据采集方法和装置

Also Published As

Publication number Publication date
CN111651746A (zh) 2020-09-11
CN111651746B (zh) 2023-03-10

Similar Documents

Publication Publication Date Title
WO2021244474A1 (zh) 登录数据处理方法、装置、设备及系统
US10904239B2 (en) Secure permissioning of access to user accounts, including secure deauthorization of access to user accounts
US10861000B2 (en) Method, system, and apparatus for application loading
US11392907B2 (en) Service request messaging
US20150039452A1 (en) Consolidated Retailer-Operated Electronic Payment System
US20230237457A1 (en) Systems and methods for payment processing on platforms
US10853786B2 (en) Multi-factor identity authentication
US20220108309A1 (en) Systems and methods for securely opening apis with cardholder authentication and consent
US20160335675A1 (en) Binding social account interactions to a master agnostic identity
WO2015148457A1 (en) Device commerce using trusted computing system
CN112119416A (zh) 经由移动设备对访问信息的安全传递
CN113114720B (zh) 关联业务数据的处理方法、装置、设备及系统
US10860983B2 (en) Cloud based platform for workplace services management
US10826886B2 (en) Techniques for authentication using push notifications
TWI741555B (zh) 顯示數位物件唯一識別符的方法及裝置
US20230120160A1 (en) Authentication aggregator
US20180089677A1 (en) Scalable credit card system
US20170221067A1 (en) Secure electronic transaction
KR102462614B1 (ko) 가맹점 모바일 신청 서비스 방법 및 관리 서버
US20140115683A1 (en) Systems and methods for peer-to-peer online verification using third party authentication
JP6155348B1 (ja) ユーザー認証及び信頼度提供方法とユーザー認証及び信頼度提供システム
US20190356647A1 (en) Multilevel sign-on
US20190073700A1 (en) Virtual home mail box driven communication system and methods employed thereof
CN114900299A (zh) 数字证书管理方法、系统、计算机设备和可读存储介质

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: 21817144

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: 21817144

Country of ref document: EP

Kind code of ref document: A1