CN111651746A

CN111651746A - Login data processing method, device, equipment and system

Info

Publication number: CN111651746A
Application number: CN202010484895.6A
Authority: CN
Inventors: 张远鹏
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2020-06-01
Filing date: 2020-06-01
Publication date: 2020-09-11
Anticipated expiration: 2040-06-01
Also published as: WO2021244474A1; CN111651746B

Abstract

The present specification provides a login data processing method, device, equipment and system, wherein the method comprises the following steps: returning a login code to the hardware equipment according to the received login code request; configuring a service management user for the hardware equipment according to the received user configuration request; receiving a login request sent by a user terminal through scanning a login code in the hardware equipment; according to login user information corresponding to the login request and a service management user configured by the hardware equipment, performing login authority verification on the login request; and if the verification is passed, modifying the login state of the login code to be logged in, and associating the hardware equipment with the login user information. By issuing the login code for the hardware equipment, a user can quickly and safely login the hardware equipment by scanning the login code displayed in the hardware equipment without complex login procedures.

Description

Login data processing method, device, equipment and system

Technical Field

The present specification belongs to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a system for processing login data.

Background

With the development of computer internet technology, digital services gradually enter people's work and life. When working with electronic devices or handling business, account logins are often required. The general login is performed by inputting a user name, a password or a mobile phone number, a dynamic verification code and the like, and the operation is complicated. Or, some devices need to be modified, and the device using the designated system can realize the function of fast login, so that the cost is high, and the device is not beneficial to being used for clearance.

Disclosure of Invention

An embodiment of the present specification aims to provide a login data processing method, device, equipment and system, which implement fast login management of hardware equipment.

In a first aspect, an embodiment of the present specification provides a login data processing method, where the method includes:

returning a login code to the hardware equipment according to the received login code request;

configuring a service management user for the hardware equipment according to the received user configuration request;

receiving a login request sent by a user terminal through scanning a login code in the hardware equipment;

according to login user information corresponding to the login request and a service management user configured by the hardware equipment, performing login authority verification on the login request;

and if the verification is passed, modifying the login state of the login code to be logged in, and associating the hardware equipment with the login user information.

In a second aspect, the present specification provides a login data processing method, including:

sending a login code request to a server through a login code interface opened by the server;

receiving a login code issued by the server based on the login code request;

receiving a login request sent by a user terminal through a login code displayed by scanning, and sending the login request to the server, so that the server modifies the login state of the login code after verifying the login authority of the login request;

polling the login state of the login code at preset time intervals, and if the login state of the login code is logged in, not displaying the login code.

In a third aspect, the present specification provides a login data processing method, including:

sending a device binding request to a server, wherein the device binding request comprises a hardware device identifier 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;

receiving equipment binding success information returned by the server, and sending a user configuration request to the server based on the equipment management user information, wherein the user configuration request comprises service management user information, so that the server associates the service management user information for the hardware equipment based on the user configuration request;

and sending a login request by scanning a login code displayed by the hardware equipment, wherein the login request comprises login user information, so that the hardware equipment sends the login request to the server, and the server checks the hardware equipment and the login user information based on the login request.

In a fourth aspect, the present specification provides a login data processing apparatus comprising:

the login code returning module is used for returning the login code to the hardware equipment according to the received login code request;

the user configuration module is used for configuring a service management user for the hardware equipment according to the received user configuration request;

the login request receiving module is used for receiving a login request sent by a user terminal through scanning a login code in the hardware equipment;

the login permission auditing module is used for auditing the login permission of the login request according to login user information corresponding to the login request and a service management user configured by the hardware equipment;

and the login state modification module is used for modifying the login state of the login code into a logged state when the verification of the login authority of the login request is passed, and associating the hardware equipment with the login user information.

In a fifth aspect, the present specification provides a login data processing apparatus comprising:

the login code request module is used for sending a login code request to the server through a login code interface opened by the server;

the login code receiving module is used for receiving a login code issued by the server based on the login code request;

the login request sending module is used for receiving a login request sent by a user terminal through a login code displayed by scanning, and sending the login request to the server so that the server revises the login state of the login code after verifying the login authority of the login request;

and the login state polling module is used for polling the login state of the login code at preset time intervals, and if the login state of the login code is logged in, the login code is not displayed any more.

In a sixth aspect, the present specification provides a login data processing apparatus comprising:

the device binding request module is used for sending a device binding request to a server, wherein the device binding request comprises a hardware device identifier 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 for receiving device binding success information returned by the server, and sending a user configuration request to the server based on the device management user information, wherein the user configuration request comprises service management user information, so that the server associates the service management user information for the hardware device based on the user configuration request;

and the login request module is used for sending a login request by scanning a login code displayed by the hardware equipment, wherein the login request comprises login user information, so that the hardware equipment sends the login request to the server, and the server verifies the hardware equipment and the login user information based on the login request.

In a seventh aspect, an embodiment of the present specification provides a login data processing apparatus, including at least one processor and a memory for storing processor-executable instructions, where the processor executes the instructions to implement the login data processing method according to the first aspect, the second method, or the third aspect.

In an eighth aspect, an embodiment of the present specification provides a login data processing system, including: the system comprises an equipment management server, hardware equipment and at least one user terminal; the device management server comprises at least one processor and a memory for storing processor executable instructions, and the method of the first aspect is implemented when the processor executes the instructions, and is used for issuing a registration code for the hardware device and managing the hardware device based on the registration code;

the hardware device comprises at least one processor and a memory for storing processor executable instructions, and the processor implements the method of the second aspect when executing the instructions, and is configured to display a login code provided by the device management server for the user terminal to scan to log in the hardware device;

the user terminal comprises at least one processor and a memory for storing processor-executable instructions, and the processor, when executing the instructions, implements the method according to the third aspect, and is configured to log in to the hardware device by scanning a login code displayed by the hardware device.

According to the login data processing method, device, equipment and system provided by the specification, the login code is issued to the hardware equipment, and a user can quickly login the hardware equipment by scanning the login code displayed in the hardware equipment without a complicated login procedure. Moreover, the login authority can be verified based on the service management user and the login user configured by the hardware equipment, so that the safe use of the hardware equipment is ensured, and the safe and quick login of the hardware management equipment is realized. By means of issuing the login codes, a user can quickly log in the hardware equipment and use the hardware equipment to conduct service handling, and digitalization of service handling is conveniently and quickly achieved. Meanwhile, the hardware equipment which issues the login codes can be managed in a unified mode, the login codes are issued directly through the open interface, the hardware equipment does not need to be modified, cost is reduced, and the method and the system are more applicable.

Drawings

In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.

Fig. 1 is a schematic flowchart of an embodiment of a login data processing method provided in an embodiment of the present specification;

FIG. 2 is a flow chart illustrating a method for processing login data according to another embodiment of the present disclosure;

FIG. 3 is a flow chart illustrating a method for processing login data according to another embodiment of the present disclosure;

FIG. 4 is a flowchart illustrating an example of hardware device login management based on a login code;

FIG. 5 is a block diagram of an embodiment of a login data processing apparatus provided in the present specification;

FIG. 6 is a block diagram of an embodiment of a login data processing apparatus provided in the present specification;

FIG. 7 is a block diagram of an embodiment of a login data processing apparatus provided in the present specification;

fig. 8 is a block diagram showing a hardware configuration of the login data processing server in one embodiment of the present specification.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all of the embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step should fall within the scope of protection of the present specification.

With the development of computer internet technology, the digitization of office equipment becomes a trend. Some digital office equipment can be used only by logging in, and for an account shared by multiple employees, the rapid and safe logging in of the office equipment becomes the demand of digital office. For example: when an offline merchant conducts digital modification of stores, the fact that after the intelligent device of the installation part is newly introduced is discovered that the self-carried clerk login function of the original cashier desk is unavailable. The payment transaction initiated on the device cannot belong to a specific clerk, and the like, so that the digital business management schemes of merchants such as shift of the clerk, clerk transaction incentive, store clerk refund management and the like cannot be realized. Generally, the login of such a device adopts a method of inputting a user name and a password, which is troublesome to operate, and if the user forgets the password, a complicated operation process such as authentication may be required.

Fig. 1 is a schematic flowchart of an embodiment of a login data processing method provided in an embodiment of the present specification. Although the present specification provides the method steps or apparatus structures as shown in the following examples or figures, more or less steps or modules may be included in the method or apparatus structures based on conventional or non-inventive efforts. In the case of steps or structures which do not logically have the necessary cause and effect relationship, the execution order of the steps or the block structure of the apparatus is not limited to the execution order or the block structure shown in the embodiments or the drawings of the present specification. When the described method or module structure is applied to a device, a server or an end product in practice, the method or module structure according to the embodiment or the figures may be executed sequentially or in parallel (for example, in a parallel processor or multi-thread processing environment, or even in an implementation environment including distributed processing and server clustering).

In a specific embodiment of the login data processing method provided in this specification, as shown in fig. 1, the method may be applied to a device management server side, where the device management server may be a computer, a tablet computer, or another terminal, and the method may include the following steps:

and step 102, returning a login code to the hardware equipment according to the received login code request.

In a specific implementation process, the hardware device in this embodiment of the present disclosure may include not only a computer and a tablet computer, but also other terminal devices, which may generally be terminal devices with a screen, for example: POS (point of sale) equipment with screen such as: a face-sweeping device at a checkout counter of a supermarket, etc.; and the system also can comprise ordering equipment, market advertisement display equipment, self-service equipment (such as self-service ticket purchasing equipment), vehicle-mounted equipment and the like. In general, a plurality of users may use the hardware device in this embodiment, 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 open interface of the device management server, and sends a login code request to the device management server, namely, the device management server is requested to issue a login code for the hardware device. The device management server may be understood as a platform or a server that can provide a login code interface for the hardware device and perform unified management on the accessed hardware device, and may be a service that is open to some network platforms with relatively strong functions. In general, before the hardware device leaves the factory, the manufacturer of the hardware device may request a registration code for the hardware device through an interface opened by the device management server. The login code may include a jump link of the user terminal after scanning the login code, a login code identifier, and may further include a code value state of the login code, i.e., a login state, i.e., whether the login code is in a login state or an unregistered state. The specific form of the registration code can be a two-dimensional code, a bar code or other pictures which can include designated meanings.

In some embodiments of this specification, 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 a corresponding login code and render and display the login code. The device management server can also directly generate the login code picture according to the received request, and the generated login code picture is returned to the hardware device so that the hardware device can display the received login code picture. Of course, the generation process of the registration code includes, but is not limited to, the above explanation according to the actual use requirement, and the embodiment of the present specification is not particularly limited.

And 104, configuring a service management user for the hardware equipment according to the received user configuration request.

In a specific implementation process, before the user uses the hardware device, a user configuration request may be sent to the device management server through an applet of the user terminal or by directly clicking a page in the hardware device, that is, a service management user is requested to be configured for the hardware device, and the user configuration request may include a device identifier of the hardware device and 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, the service management user is configured for the hardware device. The user information of the service management user may include: at least one of a user's name, phone number, identification, username specifying an application, etc. When a user requests to log in the hardware device by scanning the login code on the hardware device, whether the user currently requesting to log in has login authority can be judged based on the service management user configured by the hardware device.

And 106, receiving a login request sent by the user terminal through scanning the login code in the hardware equipment.

In a specific implementation process, the login user may use its own user terminal such as: the smart phone scans the login code displayed in the hardware equipment and sends a login request to the equipment management server. Generally, a login user may scan a login code in a hardware device through an application program designated in a user terminal, and when the user terminal scans the login code of the hardware device, the hardware terminal may send a user request login information to the device management server. Or when the user terminal scans the login code of the hardware equipment, a login request is automatically triggered to the equipment management server.

Of course, if the hardware device does not have a display screen, the login code may also be directly pasted on the device outer side of the hardware device, and the user may directly scan the hardware device pasted on the hardware device.

And 108, performing login authority verification on the login request according to login user information corresponding to the login request and a service management user configured by the hardware equipment.

In a specific implementation process, the login request received by the device management server may include login user information of a login user requesting login and a device identifier of the hardware device requesting login, the login user information may include at least one of a name, a Mobile phone Number, an Identity identifier, a user name of a specified application program, and the like of the login user, and the device identifier may be a product Serial Number (e.g., SN) or a Mobile device identification code (e.g., International Mobile Equipment Identity) of the hardware device, and may be uploaded by a device manufacturer when requesting 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 configured in association with the hardware device, judge whether the login user is the service management user configured by the hardware device, determine that the login request is legal if the login user is the service management user configured by the hardware device, and determine that the login request is illegal if the login user is not the service management user configured by the hardware device, and reject the request.

And step 110, if the verification is passed, modifying the login state of the login code to be logged in, and associating the hardware equipment with the login user information.

In a specific implementation process, when the device management server performs login permission verification on a login request based on login user information of a login user and a service management user configured by the hardware device, it is determined that the login user belongs to the service management user configured by the hardware device, and after the login request verification is passed, a login state of a login code of the hardware device can be modified into a logged state in a database of the device management server, and meanwhile, the hardware device can be associated with the login user information, and the information of the login user is recorded. The login user can perform business transaction on the hardware equipment, such as: setting the home page configuration items, the refund processing, the collection processing and the like of the hardware equipment.

For example: the cash register device of the cash register table of a supermarket is a POS device with a screen, and users such as: the manufacturer or supermarket device administrator can request a login code for the POS device through an interface opened by the device management server, and the login code can be displayed in a screen of the POS device. The supermarket device administrator can also configure a service management user for the POS device, such as: and sending a user configuration request to the equipment management server to request to configure a service management user A and a service management user B for the POS equipment. The business management user A can scan the login code displayed in the POS equipment through the mobile phone terminal and send a login request to the equipment management server, and after receiving the login request, the equipment management server can check the identity of the login user in the login request and check whether the login user is the business management user of the POS equipment, namely whether the login user has login authority. The login user is verified to be the service manager A configured for the POS equipment, the login state of the login code of the POS equipment can be modified to be logged in when the login request passes, and the service manager A can use the POS equipment to perform service operations such as collection or refund. Similarly, the service management user B may also log in the POS device by the same method, and the device management server may record service processing data of the service management user A, B after logging in the POS device, so that the administrator may query the service processing conditions of each service management user, and the like

The hardware device may poll every preset time, such as 1 second, for example, to send a request to the device management server to query the login status of the login code, and when the hardware device determines that the login status of the login code is logged in, the login code may not be displayed any more, for example: and exiting the display interface of the registration code and directly displaying the home page of the registration code. If the hardware equipment determines that the login state of the login code is not logged in, the login code can be continuously displayed in the interface to wait for the user to log in. Such as: if the login user logs out of the login, the hardware equipment polls to find that the login state of the login code is changed from logged in to logged out, and the login code is displayed in the interface again. The login user may log out through the hardware device, or may select to log out through the mobile phone terminal that the login user scans, which may be determined by actual conditions, and embodiments of this specification are not limited specifically.

According to the login data processing method provided by the embodiment of the specification, the login code is issued to the hardware equipment, and a user can quickly login the hardware equipment by scanning the login code displayed in the hardware equipment without a complex login procedure. Moreover, the login authority can be verified based on the service management user and the login user configured by the hardware equipment, so that the safe use of the hardware equipment is ensured, and the safe and quick login of the hardware management equipment is realized. By means of issuing the login codes, a user can quickly log in the hardware equipment and use the hardware equipment to conduct service handling, and digitalization of service handling is conveniently and quickly achieved. Meanwhile, the hardware equipment which issues the login codes can be managed in a unified mode, the login codes are issued directly through the open interface, the hardware equipment does not need to be modified, cost is reduced, and the method and the system are more applicable.

On the basis of the foregoing embodiments, in some embodiments of this specification, the configuring, according to a received user configuration request, a service management user for the hardware device includes:

configuring a service management user and a management authority corresponding to the service management user for the hardware equipment according to a received user configuration request;

the method further comprises the following steps:

receiving a service request sent by the hardware equipment;

acquiring login user information corresponding to the hardware equipment according to the service request;

and performing service authority verification on the service request according to the management authority of the login user corresponding to the login user information.

In a specific implementation process, when configuring a service management user for a hardware device, the management authority of each service management user may also be configured, for example: whether a refund processing authority exists, whether an authority for setting a refund password exists, whether an authority for modifying price exists, and the like. When the user successfully logs in by scanning the login code in the hardware device, the hardware device can be used for conducting business handling, such as: and (4) refund processing. When a logged-on user uses hardware equipment to perform service handling, the hardware equipment may be triggered to send a service request to the equipment management server, where the service request may include an equipment identifier of the hardware equipment, specific service content, and the like. After receiving the service request, the device management server may obtain login user information of a login user in the hardware device and a management authority corresponding to the login user. And judging whether the current login user has the authority for handling the service content of the service request according to the acquired management authority of the login user and the specific service content in the service request, if so, allowing the service request to be handled, continuing the subsequent service handling process, and if not, rejecting the service request.

In the embodiment of the description, by configuring the management authority of the service management user, when the service management user uses the hardware device to perform service handling, whether the service management user has the service authority for the service handling is checked, so that the safe use of the hardware device is ensured.

On the basis of the above embodiments, in some embodiments of the present specification, 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 received service request comprises: a device identification;

the method further comprises the following steps:

and judging whether the hardware equipment is bound with equipment management user information or not according to the equipment identification, if so, determining that the hardware equipment passes the verification, and acquiring login user information of the hardware equipment.

In a specific implementation process, before configuring a service management user for a hardware device, device binding may be performed, that is, a device management user is bound to the hardware device, and the device management user may edit and modify user information and management permissions of the service management user of the hardware device. Such as: after a supermarket prepares to carry out digital transformation on POS equipment owned by the supermarket and requests a registration code for the POS equipment through an open interface connected with an equipment management server, a supermarket administrator can send an equipment binding request to the equipment management server by using a specified applet in a mobile phone client of the supermarket or directly through the POS equipment. The device binding request may include a device identifier and device management user information to be bound, and after receiving the device binding request, the device management server may bind the corresponding device management user to the POS device, that is, the right the POS device belongs to or the right to manage is owned by the device management user. After the device management user of the hardware device is successfully bound, the device management user may configure the service management user and the management authority of the service management user for the hardware device, and specifically, the configuration of the service management user and the management authority thereof may be performed through an applet specified in a user terminal of the device management user, or the configured service management user and the management authority thereof may be directly input in the hardware device after the identity is directly verified in the hardware device.

When a service management user logs in the hardware device and uses the hardware device to perform service handling, the hardware device is triggered to send a service request to the device management server, and the service request may include a device identifier and corresponding service content. After receiving the service request, the device management server may determine whether the hardware device performs binding of the device management user according to the device identifier in the service request, that is, whether the hardware device has device management user information bound. If yes, determining that the hardware equipment is legal and can be normally used, then acquiring login user information of the hardware equipment based on the equipment identification, carrying out management authority check on the login user information, and determining whether the login user has a service authority for handling the service request. If it is determined that the hardware device is not bound with the device management user, the hardware device is considered to be currently illegal and cannot be normally used, that is, the hardware device does not have a home subscriber currently, and the service request can be directly rejected.

The hardware device in the embodiments of the present description may perform binding of a device management user before use, and may determine whether the hardware device performs binding of the device management user based on a device identifier when performing service handling, and perform identity verification on the hardware device. Only the hardware equipment bound with the equipment management user is allowed to perform business handling, a data base is laid for risk identification and the like of subsequent hardware equipment, the safe use of the hardware equipment is ensured, and the safe management of the hardware equipment is facilitated.

after the login request is approved, a login identification is issued to the login user, the login identification is returned to the hardware equipment, and the login identification is associated with login user information of the login user;

the received service request comprises: a login identifier;

the obtaining of the login user information corresponding to the hardware device according to the service request includes:

and obtaining login user information associated with the login identification according to the login identification.

In a specific implementation process, when a user scans a login code of the hardware device and successfully verifies that the login is passed, a login identifier can be issued to the login user, the login identifier is associated with login user information of the login user, and meanwhile, the login identifier is returned to the hardware device. When the login user uses the hardware device to perform service handling and triggers the hardware device to send a service request to the device management server, the service request may include a login identifier and a device identifier. The device management server can perform identity verification on the hardware device based on the device identifier to determine whether the hardware device binds to the device management user. After the hardware equipment is successfully verified, login user information of a login user of the current hardware equipment can be obtained based on the login identification, then the service authority of the login user is verified based on the login user information, whether the login user has the service content handling authority of the service request is determined, if yes, the service handling is continued, and if not, the request is rejected.

After the hardware equipment successfully logs in, the embodiment of the specification issues a login identification for the login user, and the login identification can be associated with login user information of the login user so as to quickly acquire the information of the login user and verify the identity and the management authority of the login user, thereby replacing the data processing efficiency.

Fig. 2 is a schematic flowchart of a login data processing method in another embodiment of the present specification, and as shown in fig. 2, some embodiments of the present specification may provide a login data processing method applied to a hardware device side, where the method includes:

step 202, sending a login code request to the server through a login code interface opened by the server.

In a specific implementation process, the hardware device in this embodiment of the present disclosure may include not only a computer and a tablet computer, but also other terminal devices, which may generally be terminal devices with a screen, for example: POS (point of sale) equipment with screen such as: a face-sweeping device at a checkout counter of a supermarket, etc.; and the system also can comprise ordering equipment, market advertisement display equipment, self-service equipment (such as self-service ticket purchasing equipment), vehicle-mounted equipment and the like. The server may be understood as the device management server in the above embodiment, and the hardware device may access to the device management server by calling an open interface of 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 may be understood as a platform or a server that can provide a login code interface for the hardware device and perform unified management on the accessed hardware device, and may be a service that is open to some network platforms with relatively strong functions. In general, before the hardware device leaves the factory, the manufacturer of the hardware device may request a registration code for the hardware device through an interface opened by the device management server.

And step 204, receiving a login code issued by the server based on the login code request.

In a specific implementation process, after receiving 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 of the user terminal after scanning the login code, and may further include a code value state of the login code, i.e., a login state, i.e., whether the login code is in a login state or an unregistered state. The specific form of the registration code can be a two-dimensional code, a bar code or other pictures which can include designated meanings. The login code returned to the hardware device by the device management server 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 the login code picture according to the received request, and the generated login code picture is returned to the hardware device so that the hardware device can display the received login code picture. Of course, the generation process of the registration code includes, but is not limited to, the above explanation according to the actual use requirement, and the embodiment of the present specification is not particularly limited. After the hardware equipment receives the login code, the login code can be directly displayed in a display screen of the hardware equipment so that a user can scan and log in.

And step 206, receiving a login request sent by the user terminal through the login code displayed by scanning, and sending the login request to the server, so that the server modifies the login state of the login code after verifying the login authority of the login request.

In a specific implementation process, the login user may use its own user terminal such as: the smart phone scans the login code displayed in the hardware equipment and sends a login request to the equipment management server. Generally, a login user may scan a login code in a hardware device through an application program designated in a user terminal, and when the user terminal scans the login code of the hardware device, the hardware terminal may send a user request login information to the device management server. Or when the user terminal scans the login code of the hardware equipment, a login request is automatically triggered to the equipment management server. The login request can include login user information of a login user requesting login and a device identifier of a hardware device requesting login, the device management server can match the login user information in the login request with user information of a service management user configured in association with the hardware device, judge whether the login user is the service management user configured by the hardware device, if yes, determine that the login request is legal, verify the login request, modify the login state of a login code of the hardware device into logged in a database of the device management server, and simultaneously, associate the hardware device with the login user information and record the information of the login user. And if the login request is not approved, determining that the login request is illegal, and rejecting the request.

And 208, polling the login state of the login code at preset time intervals, and if the login state of the login code is logged in, not displaying the login code.

In a specific implementation process, the hardware device may poll, for example, to send a request to the device management server for querying a login status of the login code at preset time intervals, for example, every 1 second, where the request may include information such as a device identifier and a login code identifier. When the hardware device determines that the login state of the login code is logged in, the login code may not be displayed any more, such as: and exiting the display interface of the registration code and directly displaying the home page of the registration code. If the hardware equipment determines that the login state of the login code is not logged in, the login code can be continuously displayed in the interface to wait for the user to log in. Such as: if the login user logs out of the login, the hardware equipment polls to find that the login state of the login code is changed from logged in to logged out, and the login code is displayed in the interface again. The login user may log out through the hardware device, or may select to log out through the mobile phone terminal that the login user scans, which may be determined by actual conditions, and embodiments of this specification are not limited specifically.

According to the login data processing method provided by the embodiment of the specification, the login code is issued to the hardware equipment, and a user can quickly login the hardware equipment by scanning the login code displayed in the hardware equipment without a complex login procedure. Moreover, the login authority can be verified based on the service management user and the login user configured by the hardware equipment, so that the safe use of the hardware equipment is ensured, and the safe and quick login of the hardware management equipment is realized. By means of issuing the login codes, a user can quickly log in the hardware equipment and use the hardware equipment to conduct service handling, and digitalization of service handling is conveniently and quickly achieved. Meanwhile, the hardware equipment which issues the login code can be managed in a unified mode, the hardware equipment does not need to be modified, cost is reduced, and the method is more applicable.

On the basis of the above embodiments, in some embodiments of the present specification, after the server passes the verification of the login permission of the login request, the server modifies the login state of the login code to be logged in, issues a login identifier for the login user, associates the login identifier with the login user information of the login user, and returns the login identifier to the hardware device;

the method further comprises the following steps:

receiving a service request, wherein the service request comprises: equipment identification and login identification;

and sending the service request to the server so that the server checks the hardware equipment according to the equipment identifier, and after the check is passed, the server acquires login user information of the hardware equipment and login user information associated with the login identifier based on the login identifier and checks service permission of the login user.

In a specific implementation process, when a user scans a hardware device login code and successfully verifies that the login is passed, a login identifier can be issued to the login user, the login identifier is associated with login user information of the login user, and the login identifier is returned to the hardware device. When the login user uses the hardware device to perform service handling and triggers the hardware device to send a service request to the device management server, the service request may include a login identifier and a device identifier. The device management server can perform identity verification on the hardware device based on the device identifier to determine whether the hardware device binds to the device management user. After the hardware equipment is successfully verified, login user information of a login user of the current hardware equipment can be obtained based on the login identification, then the service authority of the login user is verified based on the login user information, whether the login user has the service content handling authority of the service request is determined, if yes, the service handling is continued, and if not, the request is rejected.

Fig. 3 is a schematic flowchart of a login data processing method in another embodiment of the present specification, and as shown in fig. 3, some embodiments of the present specification may provide a login data processing method applied to a user terminal side, where the method includes:

step 302, sending 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 information for the hardware device based on the device binding request.

In a specific implementation process, a login code request may be sent to a server, that is, an equipment management server, and a login code may be requested for a hardware device before the hardware device leaves a factory. When the hardware equipment is purchased and used by a user, the user can perform equipment binding on the hardware equipment through the user terminal before the hardware equipment is used, namely an equipment management user is bound for the hardware equipment, and the equipment management user can edit and modify the user information and the management authority of the service management user of the hardware equipment. Such as: after a supermarket prepares to carry out digital transformation on POS equipment owned by the supermarket and requests a registration code for the POS equipment through an open interface connected with an equipment management server, a supermarket administrator can send an equipment binding request to the equipment management server by using a specified applet in a mobile phone client of the supermarket or directly through the POS equipment. The device binding request may include a device identifier and device management user information to be bound, and after receiving the device binding request, the device management server may bind the corresponding device management user to the POS device, that is, the right the POS device belongs to or the right to manage is owned by the device management user.

Step 304, 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, where the user configuration request includes service management user information, so that the server associates the service management user information for the hardware device based on the user configuration request.

In a specific implementation process, after the device management user of the hardware device is successfully bound, the user terminal may receive information that the device binding is successful, the device management user may configure the service management user and the management authority of the service management user for the hardware device, specifically, the service management user and the management authority thereof may be configured through an applet specified in the user terminal of the device management user, or the configured service management user and the management authority thereof may be directly input in the hardware device after the identity is directly verified in the hardware device. The device management server may record the device management user information and the service management user information bound to the hardware device in a database or a cache. The equipment management user can also configure management authority for each service management user, and different service management users have different service authorities when using the hardware equipment.

Step 306, sending a login request by scanning a login code displayed by the hardware device, wherein the login request comprises login user information, 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.

In a specific implementation process, both the device management user and the service management user may trigger the hardware device to send a login request to the device management server by scanning a login code displayed in the hardware device, where the login request may include login user information of a login user requesting login and a device identifier 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 configured by the association of the hardware device, judge whether the login user is the service management user configured by the hardware device, if so, determine that the login request is legal, verify the login request, modify the login state of the login code of the hardware device into the logged-in state in the database of the device management server, and simultaneously, associate the hardware device with the login user information and record the information of the login user. And if the login request is not approved, determining that the login request is illegal, and rejecting the request.

It should be noted that the user terminal may be a user terminal of a device management user such as a merchant, or may be a user terminal of a business management user such as a clerk.

Fig. 4 is a schematic flowchart of a hardware device login management based on a login code in an example of the present specification, and the following describes a process of login data processing in some examples of the present specification with reference to fig. 4:

1. the device side (namely the hardware device) can call a device management server (such as a cloud payment platform, pre-payment can be understood as a payment mode based on a cloud computing architecture and relying on the Internet and the mobile Internet) to initialize the interface pull login code.

1.1, an authentication center of the cloud payment platform can issue a qrcodeid, namely a login code identifier, to the login code, and the login code identifier can be stored in a cache system.

1.2, simultaneously, a merchant administrator, namely an equipment management user, can bind service management users in the applet in the user terminal, and can enter the authority center of the cloud payment platform through the applet to add the merchant administrator, for example: and inputting the mobile phone number of the clerk, and setting the clerk authority, such as the refund password setting authority.

1.3, the merchant can bind the information of the merchant on the device through the binding device. Generally, a merchant can bind merchant information first and then add and bind a business management user, i.e., a clerk. The method can be accessed to an equipment center of the cloud payment platform through an applet or hardware equipment of the user terminal, and merchant information is bound for the hardware equipment.

2. The cloud payment platform can issue a registration code url (uniform resource Locator) after receiving a login code 1 request of the hardware device, when the registration code is a two-dimensional code, the device end completes rendering of the two-dimensional code according to the url, and the code value content of the two-dimensional code can include qrcodeid (registration code identifier), miniappurl (jump address), qrcodetatus (login state) and the like.

3. The equipment terminal can poll the state of the two-dimensional code every 1s and judge whether the two-dimensional code is successfully logged in. If the login is successful, the two-dimension code is invalid and is not displayed any more; and if the login is not successful, continuing to display the two-dimensional code.

4. The salesclerk scans the login code through the appointed application program logged in the user terminal, so that the cloud payment merchant applet can be called, and the applet can realize the function of obtaining the mobile phone number of the user through silent authorization.

5. After the salesman confirms login in a silent mode, the cloud payment platform modifies the two-dimensional code state of the authentication center of the cloud payment platform into the logged-in state, issues a logintoken, namely a login identification, records the mobile phone number of the user, associates the mobile phone number of the login user with the login identification and the like.

6. The device side obtains the login identification logintken of the login code in the device side by polling the state of the two-dimensional code and stores the login identification logintken in the local for persistence. Meanwhile, when the user transacts the service, the device side can send a service request to the cloud payment platform, such as acquisition of home page configuration items.

7. The service request may include device identity information such as: deviceid device identification, logintken login identification, and the like.

8.1, the cloud payment platform can exchange phonnum (identity information such as a mobile phone number of a user) from the authentication center according to the logitoken in the service request, and then go to the cloud payment authority center according to the phonnum to acquire the authority of the login user.

8.2, verifying the equipment according to the deviceid to the equipment binding center.

8.3, after the verification of the authentication center is finished, the user information, namely the user information of the login user, can be returned.

9. And if the service request is a refund request, the user information is carried, and authority verification can be performed on the user information in a payment center of the cloud payment platform.

In the embodiment of the specification, by issuing the login code, the user can log in by scanning the login code in the hardware device, so that the situation of complicated online operation such as password issuing and password inputting is avoided. The open login code interface is called, login codes can be directly requested for hardware equipment, the open login code interface can be adapted to open schemes of login codes of various intelligent equipment, equipment binding can be completed through a user terminal, binding of equipment management users and service management users can be achieved, the equipment management users and the service management users can login the equipment in a code scanning mode, original system and software modification requirements of the equipment are low, applicability is high, and the cost of digital equipment modification is reduced.

In the present specification, each embodiment of the method is described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. The relevant points can be obtained by referring to the partial description of the method embodiment.

Based on the above login data processing method, one or more embodiments of the present specification further provide a system for processing login data. The system may include systems (including distributed systems), software (applications), modules, components, servers, clients, etc. that use the methods described in embodiments of the present specification in conjunction with any necessary hardware-implemented devices. Based on the same innovative conception, embodiments of the present specification provide an apparatus as described in the following embodiments. Since the implementation scheme of the apparatus for solving the problem is similar to that of the method, the specific apparatus implementation in the embodiment of the present specification may refer to the implementation of the foregoing method, and repeated details are not repeated. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.

Specifically, fig. 5 is a schematic block diagram of an embodiment of a login data processing apparatus provided in this specification, which may be immediately used as the device management server in the foregoing embodiment, and as shown in fig. 5, the login data processing apparatus provided in this specification may include:

a login code returning module 51, which may be configured to return a login code to the hardware device according to the received login code request;

a user configuration module 52, configured to configure a service management user for the hardware device according to the received user configuration request;

a login request receiving module 53, configured to receive a login request sent by a user terminal by scanning a login code in the hardware device;

the login permission verifying module 54 may be configured to perform login permission verification on the login request according to login user information corresponding to the login request and a service management user configured by the hardware device;

the login state modification module 55 may be configured to modify the login state of the login code to be logged in when the verification of the login authority of the login request is passed, and associate the hardware device with the login user information.

In the login data processing apparatus provided in the embodiment of the present specification, after issuing the login code for the hardware device, the user can quickly login the hardware device by scanning the login code displayed in the hardware device, and a complicated login procedure is not required. Moreover, the login authority can be verified based on the service management user and the login user configured by the hardware equipment, so that the safe use of the hardware equipment is ensured, and the safe and quick login of the hardware management equipment is realized. By means of issuing the login codes, a user can quickly log in the hardware equipment and use the hardware equipment to conduct service handling, and digitalization of service handling is conveniently and quickly achieved. Meanwhile, the hardware equipment which issues the login codes can be managed in a unified mode, the login codes are issued directly through the open interface, the hardware equipment does not need to be modified, cost is reduced, and the method and the system are more applicable.

In some embodiments of the present description, the user configuration module is specifically configured to:

the apparatus further comprises a service request receiving module configured to:

receiving a service request sent by the hardware equipment;

The login data processing apparatus provided in this specification embodiment, by configuring the management authority of the service management user, when the service management user performs service handling using a hardware device, checks whether the service management user has the service authority for the service handling, and ensures safe use of the hardware device.

In some embodiments of the present description, the apparatus further includes a device binding module configured to: receiving a device binding request, and managing user information for the hardware device binding device according to the device binding request;

the service request received by the service request receiving module includes: a device identification;

the service request receiving module is further configured to:

In the login data processing apparatus provided in the embodiment of the present specification, the hardware device may perform binding of the device management user before use, and when performing service handling, may determine whether the hardware device performs binding of the device management user based on the device identifier, and perform identity verification on the hardware device. Only the hardware equipment bound with the equipment management user is allowed to perform business handling, a data base is laid for risk identification and the like of subsequent hardware equipment, the safe use of the hardware equipment is ensured, and the safe management of the hardware equipment is facilitated.

In some embodiments of the present description, the login state modification module is further configured to: after the login request is approved, a login identification is issued to the login user, the login identification is returned to the hardware equipment, and the login identification is associated with login user information of the login user;

the service request received from the hardware device includes: a login identifier;

the service request receiving module is specifically configured to:

Fig. 6 is a schematic block diagram of an embodiment of a login data processing apparatus provided in this specification, which may be immediately a hardware device in the above embodiment, as shown in fig. 6, the login data processing apparatus provided in this specification may include:

a login code request module 61, configured to send a login code request to the server through a login code interface opened by the server;

a login code receiving module 62, configured to receive a login code issued by the server based on the login code request;

a login request sending module 63, configured to receive a login request sent by a user terminal through a login code displayed by scanning, and send the login request to the server, so that the server modifies a login state of the login code after checking login authority of the login request;

and the login state polling module 64 is used for polling the login state of the login code at preset time intervals, and if the login state of the login code is logged in, the login code is not displayed any more.

The login data processing device provided in the embodiment of the present specification issues the login code for the hardware device, and the user can quickly login the hardware device by scanning the login code displayed in the hardware device without a complicated login procedure. Moreover, the login authority can be verified based on the service management user and the login user configured by the hardware equipment, so that the safe use of the hardware equipment is ensured, and the safe and quick login of the hardware management equipment is realized. By means of issuing the login codes, a user can quickly log in the hardware equipment and use the hardware equipment to conduct service handling, and digitalization of service handling is conveniently and quickly achieved. Meanwhile, the hardware equipment which issues the login code can be managed in a unified mode, the hardware equipment does not need to be modified, cost is reduced, and the method is more applicable.

In some embodiments of the present specification, after the server verifies the login permission of the login request, the server modifies the login state of the login code into a logged-in state, issues a login identifier to the login user, associates the login identifier with login user information of the login user, and returns the login identifier to the hardware device;

the device further comprises a service processing module for:

The login data processing device provided in the embodiment of the present specification issues a login identifier to a login user after a hardware device successfully logs in, where the login identifier may be associated with login user information of the login user, so as to quickly obtain information of the login user, and verify the identity and management authority of the login user, which replaces data processing efficiency.

Fig. 7 is a schematic block diagram of an embodiment of a login data processing apparatus provided in this specification, which may be immediately used as a user terminal in the above embodiment, as shown in fig. 7, the login data processing apparatus provided in this specification may include:

a device binding request module 71, configured to 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 information for the hardware device based on the device binding request;

a device configuration module 72, configured to receive device binding success information returned by the server, and send a user configuration request to the server based on the device management user information, 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;

a login request module 73, configured to send a login request by scanning a login code displayed by the hardware device, where the login request includes login user information, 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.

It should be noted that the above-mentioned apparatus may also include other embodiments according to the description of the corresponding method embodiment. The specific implementation manner may refer to the description of the above corresponding method embodiment, and is not described in detail herein.

An embodiment of the present specification further provides a login data processing apparatus, including: at least one processor and a memory for storing processor-executable instructions, the processor implementing the information recommendation data processing method of the above embodiment when executing the instructions, such as:

Or, a login code request is sent 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;

Or, sending 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 information for the hardware device based on the device binding request;

An embodiment of the present specification further provides a login data processing system, including: the system comprises an equipment management server, hardware equipment and at least one user terminal;

the device management server comprises at least one processor and a memory for storing executable instructions of the processor, and the processor realizes the method executed by the device management server side when executing the instructions, and is used for issuing registration codes for the hardware device and managing the hardware device based on the registration codes;

the hardware equipment comprises at least one processor and a memory for storing executable instructions of the processor, and when the processor executes the instructions, the method executed by the hardware equipment side is realized, and the method is used for displaying login codes provided by the equipment management server for the user terminal to scan so as to log in the hardware equipment;

the user terminal comprises at least one processor and a memory for storing executable instructions of the processor, and when the processor executes the instructions, the method executed by the user terminal is realized, and the user terminal is used for logging in the hardware equipment by scanning the login code displayed by the hardware equipment. The user terminal may be a user terminal of a device management user, or a user terminal of a service management user.

It should be noted that the above description of the apparatus and system according to the method embodiments may also include other embodiments. The specific implementation manner may refer to the description of the related method embodiment, and is not described in detail herein.

The login data processing device provided by the present specification can also be applied to various data analysis processing systems. The system or server or terminal or device may be a single server, or may include a server cluster, a system (including a distributed system), software (applications), actual operating devices, logical gate devices, quantum computers, etc. using one or more of the methods described herein or one or more embodiments of the system or server or terminal or device, in combination with necessary end devices implementing hardware. The system for checking for discrepancies may comprise at least one processor and a memory storing computer-executable instructions that, when executed by the processor, implement the steps of the method of any one or more of the embodiments described above.

The method embodiments provided by the embodiments of the present specification can be executed in a mobile terminal, a computer terminal, a server or a similar computing device. Taking the example of the operation on the server, fig. 8 is a block diagram of the hardware structure of the login data processing server in one embodiment of the present description, and the computer terminal may be the login data processing server or the login data processing apparatus in the above embodiment. As shown in fig. 8, the server 10 may include one or more (only one shown) processors 100 (the processors 100 may include, but are not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA, etc.), a non-volatile memory 200 for storing data, and a transmission module 300 for communication functions. It will be understood by those skilled in the art that the structure shown in fig. 8 is only an illustration and is not intended to limit the structure of the electronic device. For example, the server 10 may also include more or fewer components than shown in FIG. 8, and may also include other processing hardware, such as a database or multi-level cache, a GPU, or have a different configuration than shown in FIG. 8, for example.

The non-volatile memory 200 may 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 embodiments of the present specification, and the processor 100 executes various functional applications and resource data updates by executing the software programs and modules stored in the non-volatile memory 200. Non-volatile memory 200 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the non-volatile memory 200 may further include memory located remotely from the processor 100, which may be connected to a computer terminal through a network. Examples of such networks include, but are not limited to, the internet, intranets, office-to-network, mobile communication networks, and combinations thereof.

The transmission module 300 is used for receiving or transmitting data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the computer terminal. In one example, the transmission module 300 includes a Network adapter (NIC) that can be connected to other Network devices through a base station so as to communicate with the internet. In one example, the transmission module 300 may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The method or apparatus provided in this specification and described in the foregoing embodiments may implement service logic through a computer program and record the service logic on a storage medium, where the storage medium may be read and executed by a computer, and implement the effects of the solutions described in the embodiments of this specification, such as:

receiving a login code issued by the server based on the login code request;

The storage medium may include a physical device for storing information, and typically, the information is digitized and then stored using an electrical, magnetic, or optical media. The storage medium may include: devices that store information using electrical energy, such as various types of memory, e.g., RAM, ROM, etc.; devices that store information using magnetic energy, such as hard disks, floppy disks, tapes, core memories, bubble memories, and usb disks; devices that store information optically, such as CDs or DVDs. Of course, there are other ways of storing media that can be read, such as quantum memory, graphene memory, and so forth.

The login data processing method or apparatus provided in the embodiments of the present specification may be implemented by a processor executing corresponding program instructions in a computer, for example, implemented by using a c + + language of a windows operating system on a PC side, a linux system, or implemented by using android and iOS system programming languages on an intelligent terminal, or implemented by using processing logic based on a quantum computer.

It should be noted that descriptions of the apparatus, the computer storage medium, and the system described above according to the related method embodiments may also include other embodiments, and specific implementations may refer to descriptions of corresponding method embodiments, which are not described in detail herein.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the hardware + program class embodiment, since it is substantially similar to the method embodiment, the description is simple, and the relevant points can be referred to only the partial description of the method embodiment.

The embodiments of the present description are not limited to what must be consistent with industry communications standards, standard computer resource data updating and data storage rules, or what is described in one or more embodiments of the present description. Certain industry standards, or implementations modified slightly from those described using custom modes or examples, may also achieve the same, equivalent, or similar, or other, contemplated implementations of the above-described examples. The embodiments using the modified or transformed data acquisition, storage, judgment, processing and the like can still fall within the scope of the alternative embodiments of the embodiments in this specification.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardsradware (Hardware Description Language), vhjhd (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

Although one or more embodiments of the present description provide method operational steps as described in the embodiments or flowcharts, more or fewer operational steps may be included based on conventional or non-inventive approaches. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When the device or the end product in practice executes, it can execute sequentially or in parallel according to the method shown in the embodiment or the figures (for example, in the environment of parallel processors or multi-thread processing, even in the environment of distributed resource data update). The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, the presence of additional identical or equivalent elements in a process, method, article, or apparatus that comprises the recited elements is not excluded. The terms first, second, etc. are used to denote names, but not any particular order.

For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, when implementing one or more of the present description, the functions of each module may be implemented in one or more software and/or hardware, or a module implementing the same function may be implemented by a combination of multiple sub-modules or sub-units, etc. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable resource data updating apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable resource data updating apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable resource data update apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable resource data update apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile 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). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage, graphene storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

As will be appreciated by one skilled in the art, one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the present specification can also be practiced in distributed computing environments where tasks are performed by remote devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, and the relevant points can be referred to only part of the description of the method embodiments. In the description of the specification, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the specification. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.

The above description is merely exemplary of one or more embodiments of the present disclosure and is not intended to limit the scope of one or more embodiments of the present disclosure. Various modifications and alterations to one or more embodiments described herein will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement or the like made within the spirit and principle of the present specification should be included in the scope of the claims.

Claims

1. A method of processing login data, the method comprising:

2. The method of claim 1, the configuring a service management user for the hardware device according to the received user configuration request, comprising:

the method further comprises the following steps:

receiving a service request sent by the hardware equipment;

3. The method of claim 2, further comprising:

the received service request comprises: a device identification;

the method further comprises the following steps:

4. The method of claim 2, further comprising:

the received service request comprises: a login identifier;

5. A method of processing login data, the method comprising:

receiving a login code issued by the server based on the login code request;

6. The method as claimed in claim 5, after the login request is approved by the server, modifying the login state of the login code to be logged in, issuing a login identifier for the login user, associating the login identifier with the login user information of the login user, and returning the login identifier to the hardware device;

the method further comprises the following steps:

7. A login data processing method comprises the following steps:

8. A login data processing apparatus, comprising:

9. The apparatus of claim 8, the user configuration module to:

receiving a service request sent by the hardware equipment;

10. The apparatus of claim 9, the apparatus further comprising a device binding module to: 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 is further configured to:

11. The apparatus of claim 9, the entry state modification module further to: after the login request is approved, a login identification is issued to the login user, the login identification is returned to the hardware equipment, and the login identification is associated with login user information of the login user;

the service request receiving module is specifically configured to:

12. A login data processing apparatus, comprising:

13. The apparatus according to claim 12, after the login request is approved by the server for the login authority, modifying the login state of the login code to be logged in, issuing a login identifier for the login user, associating the login identifier with login user information of the login user, and returning the login identifier to the hardware device;

the device further comprises a service processing module for:

14. A login data processing apparatus, comprising:

15. A login data processing apparatus comprising: at least one processor and a memory for storing processor-executable instructions, the processor implementing the method of any one of claims 1-7 when executing the instructions.

16. A logon data processing system comprising: the system comprises an equipment management server, hardware equipment and at least one user terminal; the device management server comprises at least one processor and a memory for storing processor-executable instructions, wherein the processor implements the method of any one of claims 1 to 4 when executing the instructions, and is used for issuing a registration code for the hardware device and managing the hardware device based on the registration code;

the hardware device comprises at least one processor and a memory for storing processor-executable instructions, and when the processor executes the instructions, the processor implements the method of any one of claims 5 to 6, and is used for displaying a login code provided by the device management server, and the login code is scanned by the user terminal to log in the hardware device;

the user terminal comprises at least one processor and a memory for storing processor-executable instructions, which when executed by the processor implement the method of claim 7 for logging onto the hardware device by scanning a registration code presented by the hardware device.