Device management methods and apparatuses, device and medium

Abstract

A device management method, which is executed by a second device and comprises: in response to a scenario addition operation in a device management platform, acquiring device form information and service scenario configuration information corresponding to the scenario addition operation, the device form information indicating a first device (S101); determining a device operation type for the first device (S102); and, on the basis of the device form information, the service scenario configuration information and the device operation type, generating a device operation code corresponding to the first device, the device operation code being used for instructing the first device to execute, on the basis of the service scenario configuration information, an operation procedure matching the device operation type (S103).

Description

Equipment management methods, devices, equipment and media

[0001] Related applications

[0002] This application claims priority to Chinese patent application filed on October 31, 2024, with application number 202411552754.8, entitled "Equipment Management Method, Apparatus, Equipment and Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of Internet technology, and in particular to a device management method, apparatus, device, and medium. Background Technology

[0004] Palm recognition, a technology service based on hand features, eliminates the need for cards, mobile phones, or other additional devices. It allows for identity verification and payment solely through palm recognition, offering greater convenience and speed. Applicable to multiple fields such as payment, access control, and identity verification, it possesses significant expansion potential. Electronic devices with palm recognition functionality play a crucial role in enabling this service.

[0005] Currently, many electronic devices with palm-swiping functionality lack an operable screen. For these devices, it's typically necessary to connect them to other devices with operable screens, such as computers, mobile phones, or dedicated terminals, using data cables. Management of these devices, such as device activation and parameter configuration, is then performed through the operable screens of these other devices. In essence, the activation and maintenance of each such electronic device requires connection to another device, reducing the efficiency of electronic device management. Summary of the Invention

[0006] This application provides a device management method, apparatus, device, and medium.

[0007] One embodiment of this application provides a device management method, including:

[0008] In response to a scene addition operation in the device management platform, the device form information and service scene configuration information corresponding to the scene addition operation are obtained; the device form information indicates the first device.

[0009] Determine the device operation type for the first device; and

[0010] Based on the device form information, service scenario configuration information, and device operation type, a device operation code corresponding to the first device is generated; the device operation code is used to instruct the first device to execute an operation process that matches the device operation type based on the service scenario configuration information.

[0011] One embodiment of this application provides a device management method, including:

[0012] The device operation code is identified by the camera component in the first device to obtain the device form information, service scenario configuration information and device operation type carried by the device operation code; the device operation code is generated in the device management platform.

[0013] If the first device meets the device form information and service scenario configuration information, then based on the service scenario configuration information, the operation process matching the device operation type is executed in the first device.

[0014] One embodiment of this application provides a device management apparatus, including:

[0015] The information acquisition module is used to respond to scene addition operations in the device management platform, and to acquire the device form information and service scene configuration information corresponding to the scene addition operation; the device form information indicates the first device;

[0016] The information acquisition module is also used to determine the type of device operation for the first device; and

[0017] The operation code generation module is used to generate a device operation code corresponding to the first device based on the device form information, service scenario configuration information and device operation type. The device operation code is used to instruct the first device to execute an operation process that matches the device operation type based on the service scenario configuration information.

[0018] One embodiment of this application provides a device management apparatus, comprising:

[0019] The operation code recognition module is used to recognize the device operation code through the camera component in the first device, and to obtain the device form information, service scenario configuration information, and device operation type carried by the operation code; the device operation code is generated in the device management platform; and

[0020] The device configuration module is used to execute an operation process that matches the device operation type in the first device based on the service scenario configuration information if the first device meets the device form information and service scenario configuration information.

[0021] One aspect of this application provides a computer device, including a memory and a processor. The memory is connected to the processor, the memory is used to store computer programs, and the processor is used to call the computer programs so that the computer device executes the method provided in one aspect of this application.

[0022] One aspect of this application provides a computer-readable storage medium storing a computer program adapted to be loaded and executed by a processor, so that a computer device having a processor performs the method provided in one aspect of this application.

[0023] According to one aspect of this application, a computer program product is provided, which may include a computer program stored in a computer-readable storage medium. A processor of a computer device reads the computer program from the computer-readable storage medium, and executes the computer program, causing the computer device to perform the method provided in the above aspect.

[0024] Details of one or more embodiments of this application are set forth in the following drawings and description. Other features, objects, and advantages of this application will become apparent from the specification, drawings, and claims. Attached Figure Description

[0025] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the published drawings without creative effort.

[0026] Figure 1 is a schematic diagram of a system architecture provided in an embodiment of this application;

[0027] Figure 2 is a schematic flowchart of an equipment management method provided in an embodiment of this application;

[0028] Figure 3a is a schematic diagram of an interface for generating device operation codes provided in an embodiment of this application;

[0029] Figure 3b is a schematic diagram of an interface for generating device operation codes provided in an embodiment of this application;

[0030] Figure 4 is a schematic flowchart of a device management method provided in an embodiment of this application;

[0031] Figure 5 is a schematic diagram of the reverse scanning identification process of a palm-scanning device provided in an embodiment of this application;

[0032] Figure 6 is a schematic flowchart of the device activation process of a palm-swiping device provided in an embodiment of this application;

[0033] Figure 7 is a schematic diagram of a palm payment service scenario provided by an embodiment of this application;

[0034] Figure 8 is a flowchart illustrating a device management method based on reverse scanning identification of device operation codes provided in an embodiment of this application;

[0035] Figure 9 is a schematic diagram of the structure of a device management device provided in an embodiment of this application;

[0036] Figure 10 is a schematic diagram of the structure of a device management device provided in an embodiment of this application;

[0037] Figure 11 is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0038] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0039] For ease of understanding, the basic technologies involved in the embodiments of this application are described below.

[0040] Palm Scan Service: Palm scan service is a technology service based on palm feature recognition. By collecting and analyzing the unique features of the palm, such as its shape and texture, and matching them with stored information, it can verify, identify, or authorize an individual's identity, thereby completing related operations and services such as access control, identity authentication, and payment transactions.

[0041] Palm scanning device: The palm scanning device is the hardware carrier that enables palm scanning services and is responsible for collecting relevant information about the palm, such as palm prints and palm shape.

[0042] Device activation: The process of connecting a new electronic device to the network and initializing it. The purpose of device activation is to ensure the electronic device functions properly and provides a personalized user experience. This process typically includes the following steps: ① Network connection: The electronic device needs to connect to the internet, usually via Wi-Fi (wireless network communication technology) or mobile data network. ② Authentication of the managed object (e.g., the merchant holding the electronic device): The managed object can authenticate itself by entering an object identifier (e.g., merchant number) and service application information to ensure the legitimate use of the electronic device. ③ Software update: During the activation process, the electronic device may automatically download and install the latest software updates to ensure its performance and security. ④ Settings configuration: Basic device settings, such as language and time zone, can be configured according to individual needs. ⑤ Function activation: After successful activation, all functions and services of the electronic device will be officially available.

[0043] Please refer to Figure 1, which is a schematic diagram of a system architecture provided in an embodiment of this application. This system architecture may include a device cluster and second devices. The system architecture may include one or more second devices, and the device cluster may include one or more first devices. The number of second devices included in the system architecture and the number of first devices included in the device cluster are not limited here. As shown in Figure 1, the system architecture includes a second device 10a, and the device cluster may include first devices 10c, 10d, and 10e, etc.

[0044] The second device 10a shown in Figure 1 can be any electronic device with an operable screen. The operable screen can be a touchscreen, or a screen operated via a remote control, mouse, keyboard, gamepad, or other similar tool; this application does not limit its scope. The second device 10a can include, but is not limited to, electronic devices with operable screens such as smartphones, tablets, laptops, PDAs, desktop computers, wearable devices (e.g., smartwatches, smart bracelets), smart home appliances (e.g., smart TVs), and in-vehicle devices; this application does not limit the type of the second device.

[0045] The first device included in the device cluster shown in Figure 1 can be any electronic device with a camera component (e.g., a camera); for example, the first device can be a palm-scanning device with a scanning function (the scanning function is implemented through the camera component in the first device), a smart barcode scanner, a smart doorbell, a mobile phone, a wearable device, an in-vehicle device, a smart home device (e.g., a smart speaker, etc.), etc. This application does not limit the type of the first device.

[0046] For new first devices, activation is typically required to ensure proper operation. When a first device has a barcode scanning function, the device operation code, carrying operation parameters (the parameters corresponding to each operation command), can be scanned in reverse to identify the next operation and procedure to be performed. In other words, the first device can obtain the next operation and procedure by scanning the device operation code carrying operation parameters, thereby completing the initialization, activation, and subsequent maintenance of the first device. This eliminates the need for direct interaction with the first device; management can be achieved through the device operation code. Furthermore, multiple first devices can be managed simultaneously using the same device operation code. For example, the same device operation code can be displayed to multiple first devices for reverse scanning, allowing them to execute the same operation and procedure concurrently, thus improving management efficiency.

[0047] The reverse barcode scanning and identification involved in this application embodiment refers to the process by which a first device scans and identifies the device operation code provided by another device (e.g., the second device 10a shown in FIG1), obtains the operation parameters carried by the device operation code, and executes the operation and process indicated by these operation parameters; the "reverse" here refers to the first device, and the operation parameters identified by scanning the barcode are used to inform what operation and process needs to be performed next.

[0048] As shown in Figure 1, the managed object can access the management backend of the first device through the second device 10a. This management backend provides a device management platform. Within this platform, the operation to be performed by the first device can be selected, and a corresponding device operation code 10b is generated. This device operation code 10b can be displayed to the first device in the device cluster shown in Figure 1. The device operation code generated in the device management platform is then scanned and identified using a camera component integrated within the first device (e.g., camera 10f in the first device 10c), revealing the next operation and process to be performed by the first device. It is understood that each first device in the device cluster shown in Figure 1 can contain a camera component, which enables the scanning and identification function of the first device. This camera component can include one or more cameras, such as ordinary optical cameras, 3D (three-dimensional) cameras, infrared cameras, etc. This application does not limit the type of camera component integrated in the first device.

[0049] The managed objects can be buyers who have purchased the first device (such as merchants, access control administrators, etc.), or swipe-enabled service providers who offer a range of related services such as swipe technology support, device maintenance, system integration, and data management. This application does not limit the type of managed object. The management backend can refer to a system platform used for centralized management and control of the first device. Through the management backend, operations such as device configuration, parameter setting, user information management, permission allocation, data statistical analysis, device status detection, and fault diagnosis can be performed. The device management platform can refer to a platform used to process and provide swipe-enabled related service scenarios. This platform can generate device operation codes corresponding to various operation instructions for the first device, informing the first device of the next operation and process to be performed. The device operation code can refer to a QR code, barcode, or barcode carrying the operation parameters corresponding to various operation instructions of the first device. This application does not limit the type of device operation code. The various operation instructions of the first device can include, but are not limited to, device activation, network configuration, factory reset, and service activation. This application does not limit the type of operation instruction.

[0050] Please refer to Figure 2, which is a flowchart illustrating a device management method according to an embodiment of this application. It can be understood that this device management method can be executed by a second device, such as the second device 10a in the system architecture shown in Figure 1. As shown in Figure 2, the device management method may include the following steps S101 to S103:

[0051] Step S101: Respond to the scene addition operation in the device management platform, obtain the device form information and service scene configuration information corresponding to the scene addition operation; the device form information indicates the first device.

[0052] In this embodiment, if object A purchases a new first device, object A can register and log in to the management backend of the first device. This management backend can provide object A with a device management platform, and object A can be referred to as a managed object. The device management platform may include a scene management area, which may include scene addition controls and service scene details information corresponding to the first device managed by the managed object.

[0053] The scene addition control can be used to trigger a scene addition operation, adding a new service scene to the first device managed by the managed object. Each service scene detail may include, but is not limited to, the scene name, scene template, and number of devices. The scene name can be a campus cafeteria, dormitory access control, library book borrowing, or attendance tracking, etc. The scene name can be preset according to the actual application requirements, and this embodiment does not limit this. The scene template refers to the template used when activating a service scene for the first device, used to quickly activate the service scene for the first device; the scene template can be an asynchronous deduction template or an identity recognition template, etc. Different service scenes can use different scene templates or the same scene template, depending on the actual application requirements.

[0054] Optionally, in the scene management area of ​​the device management platform, each service scene detail can be managed. For example, a "management" control can be set for each service scene detail. By executing a trigger operation on the "management" control, one or more of the scene name, scene template, and device quantity in each service scene detail can be modified. This application does not limit this.

[0055] Device form information can be used to represent information such as the device type and model of the first device managed by the managed object; for example, device form information may include, but is not limited to: hardware device form with an integrated operable screen, hardware device form with an integrated non-operable screen, and hardware device form without an integrated screen. Service scenario configuration information can refer to the configuration information set for a newly added service scenario for the first device; for example, the service scenario configuration information may include, but is not limited to, scenario name, scenario template, operating mode, and scenario applicable scope, etc., which are not limited in this application.

[0056] Operating modes can include, but are not limited to, integrated activation and usage mode and usage-only mode. Integrated activation and usage mode means that the device can be used directly upon activation of the service scenario; usage-only mode means that the device enters the usage state directly after the service scenario has been activated. The scope of application of a scenario can refer to the first device selected by the managed object to add a new service scenario. For example, the device management platform can select the device identifier (e.g., device number) of a specific first device managed by the managed object, or select information such as the store number where the first device is located. These selected first devices can correspond to the same device operation code; for example, one device operation code can correspond to one or more first devices. Optionally, the geographical area where the new service scenario needs to be added can be selected in the device management platform, such as a province, city, county, or district. All first devices managed by the managed object that are located within the selected geographical area can correspond to the same device operation code. By using the same device operation code to inform multiple first devices of the next steps and procedures, simultaneous management of multiple first devices can be achieved, improving the management efficiency of first devices.

[0057] In one or more embodiments, when a management object performs a trigger operation on the scene addition control in the scene management area (this trigger operation can be referred to as a scene addition operation), the second device can respond to the scene addition operation in the device management platform and display a service scene addition interface. This service scene addition interface may include a device selection area and a scene input area. In response to a selection operation on the device selection area, the device form information determined by the selection operation is obtained; in response to an input operation on the scene input area, the service scene configuration information determined by the input operation is obtained. In other words, if a new service scene is to be added to the first device (e.g., to perform specific operations such as device activation or network configuration on the first device), a trigger operation can be performed on the scene addition control to display the service scene addition interface; the management object can input the device form information of the first device in the device selection area of ​​the service scene addition interface and input the service scene configuration information in the scene input area.

[0058] The service scenario addition interface can be an independent interface displayed on the current interface of the device management platform, a portion of the current interface of the device management platform, or another interface accessed from the current interface of the device management platform. This application does not limit the presentation method of the service scenario addition interface. The device selection area can be used to select the hardware form of the first device to be operated. For example, you can select a first device with an integrated operable screen, or a first device with a built-in small screen (such as a first device with an integrated non-operable screen), or a first device without a screen, etc. This application does not limit the form of the first device. The scenario input area can be used to input service scenario configuration information for the first device.

[0059] In one or more embodiments, setting the service scenario configuration information may include: responding to an input operation in the scenario input area, obtaining the scenario name, scenario template, and scenario scope determined by the input operation; and then determining the scenario name, scenario template, and scenario scope as the service scenario configuration information. In other words, the service scenario configuration information at this time may include the scenario name, scenario template, and scenario scope.

[0060] Step S102: Determine the device operation type for the first device.

[0061] Specifically, when the managed object inputs service scenario configuration information and device form information into the device management platform, it can submit this information. The second device can then respond to the submission of the device form information and service scenario configuration information, displaying an operation code configuration page matching the device form information, responding to parameter configuration operations on the operation code configuration page, and displaying the device operation type for the first device. The device operation type can also be considered the code type of the device operation code for the first device. The device operation type can refer to the type of operation the first device needs to perform, such as including but not limited to: device initialization, device activation, factory reset, network configuration, and opening a new service scenario. This application does not limit the types of device operation types. The operation code configuration page can also set the validity period of the device operation code, such as 1 day, 7 days, or one month.

[0062] In one or more embodiments, the operation code configuration page may be an independent interface displayed on the service scenario addition interface in the device management platform, or it may be a part of the service scenario addition interface, or it may be another interface that jumps from the service scenario addition interface. This application does not limit the presentation method of the operation code configuration page.

[0063] Step S103: Generate a device operation code corresponding to the first device based on the device form information, service scenario configuration information, and device operation type; the device operation code is used to instruct the first device to execute an operation process that matches the device operation type based on the service scenario configuration information.

[0064] Specifically, based on the device form information and service scenario configuration information set in the service scenario addition interface, as well as the device operation type set in the operation code configuration page, a device operation code can be generated for the first device managed by the managed object. The device operation code can be used to instruct the first device to execute an operation process matching the device operation type based on the service scenario configuration information; that is, the device operation code informs the first device of the next operation process to be performed.

[0065] In a specific example, the QR code encoding principle is used to generate a device operation code C for the first device managed by the managed object, based on the device form information D, service scenario configuration information S, and device operation type T set in the service scenario addition interface and the operation code configuration page. First, the device form information D, service scenario configuration information S, and device operation type T are preprocessed to convert them into a suitable encoding format. Data preprocessing refers to the process of converting raw data such as device form information, service scenario configuration information, and device operation type into a suitable encoding format, for example, converting text information into binary data according to ASCII encoding rules. For example, converting text information into binary data according to ASCII encoding rules. For device form information D, assuming it contains character information such as device type and model, the converted result is a binary string B. D Service scenario configuration information S is converted into binary string B. S Device operation type T is converted to binary string B. T Then, these binary strings are concatenated in order to form a complete binary data string B=B D +B S +B T("+" indicates binary string concatenation). Next, according to the QR code encoding standard, the binary data string B is divided into blocks and encoded. For example, in digital mode, every 3 digits are encoded into 10 binary bits. Then, error correction codes are added according to the selected error correction level. The error correction level is a parameter used when generating QR codes and other device operation codes, and is divided into four levels: L (low), M (medium), Q (high), and H (highest). Different levels correspond to different lengths of error correction codes, which are used to add error correction codes to the encoded data to improve the error tolerance of the device operation code during scanning and recognition. Taking L-level error correction as an example, an error correction code is calculated according to a specific algorithm and added to the encoded data. Finally, a QR code matrix is ​​generated based on the encoded data and the error correction code. Each binary bit in the matrix corresponds to a module (black or white square) in the QR code, thus obtaining the device operation code C.

[0066] In one or more embodiments, the operation code configuration page may include an operation code display area, which can be used to display the generated device operation code. The device operation code generation process may include, but is not limited to: creating an operation code object corresponding to a first device; filling the operation code object with device form information, service scenario configuration information, and device operation type to generate the device operation code corresponding to the first device; and displaying the device operation code in the operation code display area of ​​the operation code configuration page.

[0067] An opcode object is a data structure that encapsulates data and related operations. An opcode object has attributes and methods. Attributes can be data describing the opcode object, and methods can be functions that operate on the opcode object. An opcode object can be an object created using a programming language, such as a Python (a high-level programming language), a JavaScript (a web page programming language), a C++ (a high-level computer programming language), or a Java (a high-level programming language), etc. This application does not limit this. During the generation of the device opcode, service scenario configuration information and device operation type can be used as the information to be encoded. An opcode object (e.g., a QR code object) can be created, and the service scenario configuration information and device operation type can be filled into the opcode object to generate the device opcode. This device opcode can be displayed in the opcode display area of ​​the opcode configuration page, and the device opcode can be presented in the form of an image.

[0068] For ease of understanding, this application describes the first device as a palm-scanning device as an example. The palm-scanning device can include, but is not limited to, stand-alone palm-scanning devices, integrated palm-scanning devices, and handheld palm-scanning devices. A stand-alone palm-scanning device refers to a stand-alone device used for palm-scanning recognition, which can be placed in specific locations, such as access control points or payment points. An integrated palm-scanning device can refer to an electronic device that integrates a palm-scanning module, i.e., an electronic device that integrates palm-scanning functionality; for example, integrated palm-scanning devices can include, but are not limited to: supermarket / convenience store POS machines, subway turnstiles, automatic ticket vending machines, access control equipment, attendance machines, ticket gates, vehicle-mounted card readers, shared vehicles, and shared charging station cabinets with integrated palm-scanning functionality. A handheld palm-scanning device can refer to a palm-scanning device that supports handheld operation, facilitating palm-scanning recognition in mobile scenarios, such as some mobile payment devices with palm-scanning functionality. A module can refer to a collection of modules or components with independent functions, formed by combining multiple components or devices with specific functions; for example, a palm-scanning module can refer to a collection of modules or components with palm-scanning functionality.

[0069] Please refer to Figures 3a and 3b. Figure 3a is a schematic diagram of an interface for generating device operation codes provided in an embodiment of this application. This embodiment of the application uses a merchant who has completed registration in a payment system (which can be a payment system provided by any platform) as an example. At this time, the merchant can be referred to as the management object of the swipe device (a type of device in the first device). The swipe device managed by the merchant is illustrated using the swipe campus card of XX University as an example. The merchant can log in to the merchant platform in the payment system. In this merchant platform, a device management platform (which can be referred to as the swipe service platform) can be provided for the merchant. The swipe service platform corresponding to the merchant can be represented by interface 20a as shown in Figure 3a.

[0070] As shown in Figure 3a, interface 20a may include a first menu bar and a second menu bar. The first menu bar may include options such as service provider search, help center, message center, and my account. The service provider search option can be used to search for the service providers that the merchant wants to query; the help center option can provide the merchant with help instructions related to various functions in the payment system merchant platform; the message center option can be used to display all messages received by the merchant in the payment system merchant platform; and the my account option can be used to display the merchant's account information in the payment system merchant platform.

[0071] The second menu bar may include options such as Home, Option A, Business Center, and Option B. This application does not limit the number of options included in the second menu bar. Each option in the second menu bar can correspond to a channel page, and each channel page can display the page content corresponding to its respective option; for example, interface 20a can be the channel page corresponding to the Business Center option in the second menu bar. The channel page corresponding to the Business Center option can include a third menu bar, which can include first-level options such as Merchant Management Tools, Merchant Smart Marketing, and Marketing Applications; each first-level option can include one or more second-level options, such as the Merchant Management Tools option can include second-level tags such as Shuazhang Service, xxx1, xxx2, xxx3, and xxx4, Merchant Smart Marketing can include second-level options such as xxx5, and Marketing Applications can include second-level options such as xx5. When a merchant selects the Shuazhang Service option in the third menu bar, the current interface 20a of the merchant's Shuazhang Service platform can be displayed.

[0072] Within the merchant's corresponding mobile payment service platform, interface 20a can include areas 20c and 20d (also known as the scene management area). Area 20c displays the operational data of the mobile payment devices (XX University mobile payment campus cards) managed by the merchant. This operational data can be the operational data of XX University mobile payment campus cards within the most recent period (e.g., the last day, the last 7 days, the last month, etc., which merchants can customize). The operational data may include, but is not limited to, the number of transactions for XX University mobile payment campus cards (unit: transactions), the number of mobile payment transactions (unit: transactions), the number of newly bound mobile payment users (unit: people), the number of connected devices per day (unit: units), the number of devices with transactions (unit: units), and the number of mobile payment devices with transactions (unit: units). The operational data in area 20c can be continuously updated. For example, if the operational data in area 20c is updated at xxxx / xx / xx 12:00, the changes in the updated data compared to the previous update (xxxx / xx / xx 12:00) can also be displayed. For example, in the latest updated operational data, the number of transactions using the mobile payment app is B1, which is an increase of b2 transactions compared to the previous update. Optionally, the operational data may also include a line graph showing the number of transactions for the XX University mobile payment app campus cards managed by the merchant over a recent period (the last 7 days), to facilitate the display of changes in the number of transactions by the merchant over a continuous period.

[0073] As shown in Figure 3a, area 20c may include an "Export Data" control 20b. When a merchant performs a trigger operation on the "Export Data" control 20b, the merchant can set the time range of the operational data to be exported (e.g., the previous day, the last 7 days, and the last month). At this time, the second device (e.g., the second device 10a shown in Figure 1) can respond to the trigger operation on the "Export Data" control 20b and export all the operational data of XX University's mobile campus card swiping within the time range selected by the merchant.

[0074] As shown in Figure 3a, area 20d can be used to display details of service scenarios available on the XX University campus. Each service scenario detail can include, but is not limited to, scenario name, scenario template, and number of devices. Merchants can interact with each service scenario detail displayed in area 20d; for example, each service scenario detail can correspond to a "Manage" control. By triggering the "Manage" control, merchants can manage the corresponding service scenario details, such as modifying one or more of the following: scenario name, scenario template, and number of devices.

[0075] The area 20d may also include an "Add Scene" control 20e (also called a scene addition control). When a merchant performs a trigger operation on the "Add Scene" control 20e in area 20d, a service scene addition interface can be displayed in the swipe service platform. Please refer to Figure 3b, which is a schematic diagram of an interface for generating device operation codes provided in an embodiment of this application. After the merchant performs a trigger operation on the "Add Scene" control 20e, the service scene addition interface displayed is interface 20f as shown in Figure 3b. This interface 20f can be used to provide the addition of swipe service scenes.

[0076] The interface 20f can include a device selection area 20g and a scene input area 20h. The device selection area 20g provides merchants with multiple selectable hardware device types, such as the official screen-equipped palm-swipe device O1 (e.g., a palm-swipe device with an operable screen) and the built-in small-screen palm-swipe module O2 (e.g., a palm-swipe device without an operable screen). The scene input area 20h can include a scene name input area, a scene template input area, and a running mode selection area. As shown in Figure 3b, when the merchant selects the built-in small-screen palm-swipe module O2 as the hardware device type (device type information) in the device selection area 20g, sets the scene name to dormitory access control, the scene template to identity recognition, and the running mode to integrated activation and use mode, the "Submit" control 20i in the interface 20f can be triggered to display the operation code configuration page 20j.

[0077] The operation code configuration page 20j can include area 20k, area 20m, and operation code display area 20n. Area 20k can be used to input the device operation type (also called code type) for the swipe-enabled device, such as "device activation" in area 20k. It is understood that the code type can be entered in area 20k by text editing or by directly selecting the device operation type from a list; this application does not limit the input method for the device operation type. Area 20m can be used to input the validity period of the device operation code, such as a 7-day validity period. After the merchant completes the input of the device operation type and validity period, a device operation code can be generated for the swipe-enabled device based on the device operation type (e.g., device activation) entered in area 20k, the validity period (e.g., 7 days) entered in area 20m, the scene name (e.g., dormitory access control) entered in the scene input area, the scene template (e.g., identity recognition), and the operating mode (e.g., integrated activation and use mode). This device operation code can be a device activation code.

[0078] The generated device operation code can be displayed in the operation code display area 20n of the operation code configuration page 20j. In addition to displaying the device operation code, the operation code display area 20n can also display the type of the device operation code (such as device activation code), the name of the swiping device (such as xx university swiping campus card), the scene name (such as dormitory access control), the generation time of the device operation code (displayed in the form of xxxx / xx / xx), and the validity period of the device operation code (for example, valid for 7 days).

[0079] Optionally, the operation code configuration page 20j may also include a "Download Image" control 20p and a "Reset Operation Code" control 20q. When a merchant performs a trigger operation (e.g., click) on the "Download Image" control 20p in the operation code configuration page 20j, the device operation code image in the operation code display area 20n can be downloaded and saved locally or to another storage location. When a merchant performs a trigger operation on the "Reset Operation Code" control 20q in the operation code configuration page 20j, the device operation code can be regenerated and the new device operation code can overwrite the currently displayed device operation code in the operation code display area 20n; after the merchant performs a trigger operation on the "Reset Operation Code" control 20q, the previously generated device operation code will be marked as an invalid operation code.

[0080] This application embodiment allows selecting device form information for a first device managed by a managed object (e.g., a merchant, a scanning service provider, etc.) and setting service scenario configuration information for it within a device management platform corresponding to the managed object. The device operation type is input for the first device indicated by the device form information. Based on the device form information, service scenario configuration information, and device operation type, a device operation code can be generated for the first device in the device management platform. This device operation code is used to provide the first device with reverse scanning identification, indicating the operation process that the first device needs to perform. Therefore, by generating a device operation code in the device management platform and informing the first device of the next operation process, the management efficiency of the first device can be improved.

[0081] Please refer to Figure 4, which is a schematic flowchart of a device management method provided in an embodiment of this application. It can be understood that this device management method can be executed by a first device, such as any of the first devices in the system architecture shown in Figure 1; this application does not limit this. As shown in Figure 4, the device management method may include the following steps S201 to S202:

[0082] Step S201: The device operation code is identified by the camera component in the first device to obtain the device form information, service scenario configuration information and device operation type carried by the device operation code.

[0083] The first devices involved in the embodiments of this application are all electronic devices that integrate camera components and can realize barcode scanning functions through their integrated camera components. After generating a device operation code in the device management platform of the managed object, the device operation code can be aligned with the camera component of the first device. The camera component in the first device identifies the device operation code and determines the valid time range corresponding to the device operation code. If the device operation code is detected to be within the valid time range, the device form information, service scenario configuration information, and device operation type carried by the device operation code are obtained; if the device operation code is detected to be outside the valid time range, it can be determined that the device operation code has expired, the first device fails to scan the code, and an expiration prompt message for the device operation code can be output in the first device.

[0084] The device operation code can carry the generation time and validity period of the corresponding operation code. The validity period range can be determined by the generation time and validity period of the device operation code. For example, if the generation time of the device operation code is xxxx / xx / 01 and the validity period is 7 days, then the validity period range of the device operation code can be from xxxx / xx / 01 to xxxx / xx / 07. Failure prompts can be output in the form of text display, voice playback, or a specific ringtone or indicator light flashing. This application does not limit the output method of failure prompts. For example, when the first device integrates a non-operable screen, the failure prompt can be displayed on the screen of the first device; when the first device does not integrate a screen, the failure prompt can be output in the form of voice playback, or through a specific flashing indicator light, etc.

[0085] Step S202: If the first device meets the device form information and service scenario configuration information, then based on the service scenario configuration information, execute the operation process that matches the device operation type in the first device.

[0086] In one or more embodiments, after the first device uses a camera component to scan and identify the device operation code, and obtains the device form information, service scenario configuration information, and device operation type carried by the device operation code, it can obtain the hardware form information and device identification information corresponding to the first device. If the hardware form information of the first device belongs to the device form information carried by the device operation code, it can be determined that the first device satisfies the device form information. For example, if the device form information carried by the device operation code includes a built-in small screen brush palm module O2 and a screenless brush palm module, and the hardware form information corresponding to the first device includes a built-in small screen brush palm module O2, then it can be determined that the hardware form information of the first device belongs to the device form information carried by the device operation code, that is, the first device satisfies the device form information carried by the device operation code.

[0087] Based on the service scenario configuration information and the device identification information, configuration permission verification is performed on the first device. Specifically, the configuration permission verification for the first device can be performed based on the scenario application scope and device identification information in the service scenario configuration information. Assume that the scenario application scope includes the geographical area range set by the merchant in the device management platform, and the device identification information includes the geographical location of the first device. If the geographical location of the first device falls within the geographical area range indicated by the scenario application scope, then it can be determined that the first device has configuration permission for device operation codes; if the geographical location of the first device does not fall within the geographical area range indicated by the scenario application scope, then it can be determined that the first device does not have configuration permission for device operation codes.

[0088] If the device identification information falls within the applicable scope of the service scenario configuration information, it can be determined that the first device possesses the configuration permissions associated with the device operation code, and thus, the first device meets the service scenario configuration information. If the hardware form information of the first device does not fall within the device form information carried by the device operation code, it can be determined that the first device does not meet the device form information carried by the device operation code, and no further configuration permission verification is required; a recognition failure message can be directly output on the first device. If the hardware form information of the first device falls within the device form information carried by the device operation code, but the device identification information does not fall within the applicable scope of the service scenario configuration information, it can be determined that the first device does not possess the configuration permissions associated with the device operation code, and a recognition failure message will be output on the first device. When the first device meets the device form information and service scenario configuration information carried by the device operation code, it can automatically execute the process operation matching the device operation type based on the service scenario configuration information, without any human intervention.

[0089] The output method for the failure message can be found in the aforementioned output method for the failure message, and will not be repeated here. Device identification information can refer to relevant information describing the first device, such as, but not limited to, the device's serial number, geographical location, and store number. The scenario scope can be used to indicate the first device with the permission to perform reverse scanning of the device's operation code. This reverse scanning permission can also be called configuration permission. For example, assuming the scenario scope includes the geographical area set by the merchant in the device management platform, and the first device's device identification information includes its geographical location; if the first device's geographical location falls within the geographical area indicated by the scenario scope, then it can be determined that the first device has configuration permission for the device operation code, meaning the first device needs to execute the operation process indicated by the device operation code, and the service scenario configuration information and device operation type carried by the device operation code can be identified. If the first device's geographical location does not fall within the geographical area indicated by the scenario scope, then it can be determined that the first device does not have configuration permission for the device operation code, meaning it does not need to execute the operation process indicated by the device operation code.

[0090] In one or more embodiments, if the first device is a newly purchased device or a device that has not yet been started, the first device can be started and its network connection can be detected. If a network connection failure is detected, a network configuration prompt message can be output on the first device. This network configuration prompt message can be used to instruct a second device (e.g., a mobile phone) to generate a network configuration code corresponding to the first device. The network configuration prompt message can be a QR code, barcode, barcode, numeric code, etc., and this application does not limit the type of network configuration prompt message. For example, when the network configuration prompt message is a QR code, the second device can scan and recognize the QR code, displaying a network list (e.g., a Wi-Fi list). This network list can include one or more connectable networks. A connectable network can be selected for the first device from the network list, and a network configuration code corresponding to that network can be generated.

[0091] The network configuration code generated by the second device can be used as a device operation code for the first device. When the device operation code includes the network configuration code, the service scenario configuration information can include network connection parameters, and the device operation type can include network configuration, i.e., performing network configuration operations on the first device. The first device scans and identifies the network configuration code using a camera component to obtain the network connection parameters of the first device during network configuration. Based on the network connection parameters, a communication connection is established between the first device and the router associated with the network configuration code; if a communication connection is successfully established between the first device and the router, it is determined that the network configuration of the first device is successful. The network connection parameters can include one or more of the following: network name, network password, channel, encryption method, etc. This application does not limit the type of network connection parameters; if a network password is set, then after entering the correct network password in the second device, a network configuration code corresponding to the network can be generated.

[0092] In a specific example, based on network connection parameters (including network name N, network password P, channel Ch, encryption method E, etc.), the first device establishes a communication connection with the router associated with the network configuration code. First, the first device enables Wi-Fi and searches for nearby wireless networks on channel Ch. When a wireless network with network name N is found, the first device processes the network password P according to encryption method E. If encryption method E is WPA2-PSK, the first device generates a pairwise master key (PMK) based on the pre-shared key (i.e., network password P) and network name N using a specific key derivation function (such as PBKDF2). Then, the first device sends an association request frame to the router. This frame contains information such as network name N, the first device's MAC address, and supported encryption methods. Upon receiving the association request frame, the router checks if the network name N matches and requests authentication from the first device based on encryption method E. For WPA2-PSK encryption, the router initiates a four-way handshake process. In the initial handshake, the router sends a random number ANonce to the first device. Upon receiving ANonce, the first device combines its own generated random number SNonce and the paired master key PMK to calculate a portion of the temporary key (PTK) and sends a message containing SNonce to the router. The router, upon receiving SNonce, also calculates its temporary key PTK. In subsequent handshakes, both parties exchange messages to verify the consistency and integrity of the temporary keys. If the first device and the router successfully verify each other during the four-way handshake, the first device sends an acknowledgment message to the router. Upon receiving the acknowledgment message, the router allows the first device to access the network. At this point, a communication connection is successfully established between the first device and the router, confirming that the first device's network configuration is successful.

[0093] It is understood that the first device involved in this application embodiment can have Wi-Fi connectivity, and the wireless router can broadcast wireless signals, including information such as the network name. When the first device enables Wi-Fi, it can scan and identify the network configuration code using a camera component to obtain the network connection parameters carried by the network configuration code. Based on these network connection parameters, the first device can perform a series of handshake and verification processes with the router. When the verification is successful, it indicates that a communication connection has been successfully established between the first device and the router, meaning that the network configuration of the first device is successful.

[0094] In one or more embodiments, when the device operation code includes a device activation code, the service scenario configuration information may include device activation operation parameters, and the device operation type may include device activation, i.e., performing device activation on the first device. The first device scans and identifies the device activation code using a camera component to obtain the device activation operation parameters for the first device during device activation. Based on the device activation operation parameters, the first device is activated; if the configuration of the device activation operation parameters is completed on the first device, the activation of the first device can be determined to be successful. Specifically, the device activation process can be performed on the first device based on the device activation operation parameters (including object information of the managed object, the serial number of the software to be installed, the basic configuration information of the first device, service scenario activation parameters, etc.). First, the first device authenticates itself based on the object information of the managed object to ensure the legitimate use of the device. Then, the corresponding software is downloaded and installed according to the software serial number. During the installation process, the basic settings of the device, such as language and time zone, are configured according to the basic configuration information. After installation, the corresponding service scenario is activated according to the service scenario activation parameters. Finally, after all configurations are completed, the first device is successfully activated.

[0095] Among them, the device activation operation parameters can refer to the operation parameters of the first device during the device activation process. These device activation operation parameters may include, but are not limited to, one or more of the following: object information of the managed object (such as merchant number, application service information, etc.), software serial number to be installed, basic configuration information of the first device (such as language, time zone, etc.), service scenario activation parameters, etc.

[0096] The following example illustrates the process using a swipe-enabled device as the first example. Please refer to Figure 5, which is a flowchart illustrating the reverse scanning identification process of a swipe-enabled device according to an embodiment of this application. As shown in Figure 5, if a device activation code 30a (which can be considered a type of device operation code) is generated in the device management platform (which can be a swipe-enabled service platform), then the device activation code 30a can be reverse-scanned using the camera component integrated in the swipe-enabled device 30b to obtain the device activation operation parameters and device operation type (the device operation type here can be the device activation type). The swipe-enabled device 30b can download and install an application package based on the device activation operation parameters, and perform initialization activation processing on the installed application to complete the device activation process. During the device activation process of the swipe-enabled device 30b, a general-purpose ROM (Read Only Memory) can be used for device activation. Here, a general-purpose ROM can refer to system firmware with broad compatibility, which can be flashed and installed across different models or brands of devices, providing some basic system functions and features.

[0097] Please refer to Figure 6, which is a flowchart illustrating the device activation process of a swipe-to-activate device according to an embodiment of this application. As shown in Figure 6, assuming the swipe-to-activate device is one with an inoperable screen, it can be started. At this time, the screen of the swipe-to-activate device can display the text "Starting". If the network connection of the swipe-to-activate device is detected to be normal, the screen of the swipe-to-activate device can display the text "Please scan the device activation code" to prompt the user (e.g., the merchant managing the swipe-to-activate device, or a subordinate member assigned by the merchant) to scan the device activation code generated in the device management platform (e.g., the swipe-to-activate service platform) against the camera component of the swipe-to-activate device.

[0098] If the network connection of the swipe device is detected to be disconnected, the text "Network connection failed" will be displayed on the screen of the swipe device. Subsequently, the text "Scan to configure network" and a network QR code will be displayed on the screen. Users can scan the network QR code on the swipe device's screen using a second device 40a, such as a mobile phone or tablet. The second device 40a will then display a list 40b of networks that the swipe device can connect to. This list 40b may include one or more Wi-Fi networks that the swipe device can connect to, such as Network 1, Network 2, and Network 3. When the user selects Network 1 from the network list 40b, the "Next" control displayed on the second device 40a will be triggered, generating a network configuration code 40c corresponding to Network 1 for the swipe device. This network configuration code 40c can then be displayed on the second device 40a. The user can align the network configuration code displayed on the second device 40a with the camera component of the swipe device. After the swipe device scans the code in reverse and identifies the network 1 indicated by the network configuration code, it can display the text "Network device in progress" on the screen of the swipe device. When the swipe device successfully connects to the network 1 indicated by the network configuration code 40c, it can display the text "Wi-Fi setup successful" on the screen of the swipe device, and then display the text "Please enter the device activation code".

[0099] When a user scans the device activation code generated in the device management platform against the camera component of the swipe device, the swipe device can recognize the device activation parameters carried in the code. Based on these parameters, the swipe device can be activated. During this process, the screen will display "Activating Device" and a progress bar will show the activation progress in real time. Once activation is complete, the screen will display "Activation Successful," and the swipe device's homepage will then be displayed.

[0100] In one or more embodiments, when the device operation code includes a factory reset code, the service scenario configuration information may include factory reset instruction parameters, and the device operation type may include factory reset, i.e., performing a factory reset operation on the first device. The first device scans and identifies the factory reset code using a camera component to obtain the factory reset instruction parameters for the first device during the factory reset. The initial system state and default configuration information indicated by the factory reset instruction parameters are obtained; the system state in the first device is replaced with the initial system state, and the configuration information in the first device is replaced with the default configuration information. Specifically, the pre-stored initial system state and default configuration information can be found in the storage area of ​​the first device; this information is written to a specific storage location when the device is manufactured. When the factory reset instruction parameters are received, the location storing the initial system state and default configuration information is located based on the identification information in the parameters, thereby obtaining this information.

[0101] Here, "factory reset command parameters" can refer to the parameters of the factory reset command for the first device, such as an identifier confirming the factory reset. "Initial system state" can refer to the initial state of the operating system of the first device at the factory, and "default configuration information" can refer to the initial settings of the operating system of the first device at the factory.

[0102] In one or more embodiments, when the first device includes a palm-scanning device that activates an access control service scenario (i.e., the palm-scanning device is applied to the access control service scenario), a first palmprint image of the palm verification object can be captured through the camera component in the palm-scanning device, and a second palmprint image pre-stored by the palm verification object can be obtained. The palmprint similarity between the first and second palmprint images is obtained. If the palmprint similarity is greater than a similarity threshold, it can be determined that the palm-scanning recognition of the palm verification object is successful. Here, the palm verification object can refer to a user who has activated the palm-scanning access control service and wants to open the access control; the first palmprint image can refer to the palmprint image of the palm verification object captured in real time by the palm-scanning device; and the second palmprint image can refer to the palmprint image stored during the authentication of the palm verification object.

[0103] A similarity algorithm can be used to calculate the similarity between the first and second palmprint images, referred to here as palmprint similarity. This similarity algorithm can include, but is not limited to, histogram algorithms, grayscale image algorithms, hash algorithms, cosine similarity, Euclidean distance, Manhattan distance, Pearson correlation coefficient, etc. The similarity threshold can be a pre-set value, such as 80% or 85%, depending on the specific application requirements; this application does not impose any limitations on this. The similarity threshold can be determined based on extensive experimental data and practical application scenarios. Specifically, by collecting palmprint image data from different users and conducting multiple recognition experiments under different environmental conditions, the relationship between recognition accuracy and similarity values ​​can be statistically analyzed to determine a suitable similarity threshold, achieving the optimal balance between accuracy and security in palmprint recognition. Furthermore, the similarity threshold can be dynamically adjusted according to the different security and convenience requirements of different application scenarios (such as access control systems, payment systems, etc.). When the palm print similarity is greater than a preset similarity threshold, it can be confirmed that the palm print verification object has passed the access control service system's authorization, and the door lock can be opened for the palm print verification object. For ease of understanding, this similarity threshold can be called the first threshold; that is, in this application embodiment, the similarity threshold set by the first device in the access control service scenario can be called the first threshold.

[0104] The cosine similarity algorithm can be used to calculate the similarity between the first palmprint image I1 and the second palmprint image I2. This similarity can be called the palmprint similarity Sim. First, the first palmprint image I1 and the second palmprint image I2 are converted into vector form. For a grayscale image of size m×n, the grayscale value of each pixel is used as an element of the vector. The vector corresponding to the first palmprint image I1 is... The vector corresponding to the second palmprint image I2 Then, calculate the vector. and dot product Next, calculate the vectors respectively. model sum vector model Finally, according to the cosine similarity formula Calculate the palmprint similarity Sim. The closer the Sim value is to 1, the more similar the two palmprint images are.

[0105] In one or more embodiments, when the palm-scanning device activates the palm-scanning payment service scenario, i.e., when the palm-scanning device is applied to the palm-scanning payment service scenario, please refer to the aforementioned description of applying the palm-scanning device to the access control service scenario, which will not be repeated here. The palm verification object in the palm-scanning payment service scenario can refer to a user who has enabled the palm-scanning payment service and wants to make a palm-scanning payment. The first palm print image of the palm verification object is captured by the camera component in the palm-scanning device (here, the first palm print image can be regarded as the first palm-scanning image in the palm-scanning payment service scenario), and the second palm print image pre-stored by the palm verification object is obtained (here, the second palm print image can be regarded as the second palm-scanning image in the palm-scanning payment service scenario); the palm-scanning similarity between the first palm print image and the second palm print image is obtained. If the palm-scanning similarity is greater than a second threshold, it can be determined that the palm-scanning recognition of the palm verification object is successful; then, the payment account of the palm verification object in the payment system can be determined according to the second palm print image, and the asset amount of this payment is deducted from the payment account of the palm verification object, indicating that the palm-scanning payment of the palm verification object is successful. The second threshold can be a value set according to the specific requirements of the actual application scenario. The second threshold and the first threshold can be the same value or different values; this application does not limit this. A mapping relationship between the second palmprint image and the payment account in the payment system can be pre-established and stored in a database. When palm recognition is successful, the database is queried to find the associated payment account based on the unique identifier corresponding to the second palmprint image, thereby determining the payment account of the palm verification object in the payment system.

[0106] Please refer to Figure 7, which is a schematic diagram of a palm payment service scenario provided in an embodiment of this application. This embodiment uses a palm-scanning device as an example of its application in the palm payment service scenario. As shown in Figure 7, after the palm-scanning device has completed device activation and enabled the palm payment service, if the palm-scanning device receives a transaction pending confirmation, it can switch states and display the text "Palm Confirm Payment s1" on its screen. This "Palm Confirm Payment s1" text prompts the palm verification target (the user who has enabled the palm payment service and wants to make a palm payment) to align their palm with the camera component of the palm-scanning device.

[0107] When the palm-scanning device captures the first palm print image of the palm verification object through the camera component, it can compare the captured first palm print image with the pre-stored second palm print image. If the palm print similarity between the first palm print image and the second palm print image is greater than a second threshold, then the door lock can be opened for the palm verification object. Then, s1 can be deducted from the palm verification object's payment account. After successfully deducting s1, it means that the palm verification object has successfully paid. The service result of the palm-scanning payment service can be displayed on the screen of the palm-scanning device. The service result can be the text "Payment successful s1".

[0108] Please refer to Figure 8, which is a flowchart illustrating a device management method based on reverse scanning identification of device operation codes provided in this application embodiment. It is understood that this device management method can be implemented through interaction between merchants, installation service providers, payment system operators, payment system swiping tools, swiping devices (e.g., the swiping module O2 with a built-in small screen in Figure 3b, a type of the first device), and the payment system merchant platform (specifically, a swiping service platform). As shown in Figure 8, this device management method may include the following steps S301 to S314:

[0109] Step S301: Register as a direct-connect merchant to the payment system.

[0110] Step S302: Register as a payment system service provider.

[0111] Step S303: Sign the self-procurement and installation service provider agreement and activate the swipe-to-installation permission.

[0112] Step S304: Invite merchants to authorize.

[0113] Step S305: Send messages (internal message & mobile template message).

[0114] Step S306: Confirm the authorization of the palm-swiping service.

[0115] Step S307: Apply for services on behalf of authorized merchants.

[0116] Step S308: Review the merchant's application for services (qualifications, etc.).

[0117] Step S309: Sign the self-procurement merchant agreement and activate the swipe service.

[0118] Step S310: Generate device activation code (service identifier + scenario configuration identifier).

[0119] Step S311: Return the device activation code.

[0120] Step S312: Reverse the code and activate the palm-scanning device.

[0121] Step S313: Generate operation codes for various devices (factory reset / network configuration, etc.).

[0122] Step S314: Reverse the code and update the configuration of the palm-swiping device.

[0123] Among these, "directly connected merchants" refers to merchants directly connected to the payment system. "Payment system service providers" refers to enterprises or institutions that provide a range of related services, including connectivity, technical support, and service integration, between merchants and the payment system. "Infrastructure deployment service providers" refers to service providers responsible for the deployment of infrastructure, networks, and channels. "Payment system operators" refers to personnel responsible for the daily operation and management of the payment system. "Payment system swipe tool" refers to a tool used to generate device operation codes, which the payment system merchant platform can call upon.

[0124] Merchants who purchase the mobile payment device can register as direct-connect merchants to the payment system, and deployment service providers can register as payment system service providers. Deployment service providers can sign a self-procurement deployment service provider agreement and activate mobile payment device deployment permissions on the payment system merchant platform. Deployment service providers can invite merchants to authorize the service on the payment system merchant platform. At this time, the payment system merchant platform can send messages to merchants (e.g., in-platform messages, mobile template messages, etc.), and merchants can confirm the mobile payment device service authorization based on the received messages. Once a merchant confirms the authorization for the deployment service provider to use the mobile payment device on the payment system merchant platform, the merchant can apply for the mobile payment device service on behalf of the authorized merchant on the payment system merchant platform. Payment system operators can review the merchant's application for the mobile payment device service (qualifications, etc.). If the review is approved, the merchant can sign a self-procurement merchant agreement and activate the mobile payment device service on the payment system merchant platform. In other words, steps S301 to S309 can represent the relevant parameter configuration during the merchant's application for the swipe service, and the parameters that generate the device operation code.

[0125] Steps S310 to S314 indicate that after the merchant or installation service provider obtains the device operation code, they can use the palm-scanning device to reverse the code (which can be represented as reverse scanning to identify the device operation code) to instruct the palm-scanning device to automatically configure according to the operation parameters. It should be understood that the device activation code in the embodiment corresponding to Figure 8 can also be called the device operation code. The specific implementation process of steps S310 to S314 can be found in the relevant descriptions in steps S201 to S202 above, and will not be repeated here.

[0126] This application embodiment allows selecting device form information for a first device managed by a managed object (e.g., a merchant, a scanning service provider, etc.) and setting service scenario configuration information for it within a device management platform corresponding to the managed object. The device operation type is input for the first device indicated by the device form information. Based on the device form information, service scenario configuration information, and device operation type, a device operation code can be generated for the first device in the device management platform. This device operation code is used to provide the first device with reverse scanning identification, indicating the operation process that the first device needs to perform. Therefore, by generating a device operation code in the device management platform and informing the first device of the next operation process, the management efficiency of the first device can be improved.

[0127] It is understood that, in the specific implementation of this application, information such as the registration information and login account of the managed object in the device management platform, the operation data of the first device, and the activated palm-scanning service scenarios may be involved, as well as the user's account and identity information (e.g., palm print / palm shape image) in systems such as payment systems and access control systems. When the above embodiments of this application are applied to specific products or technologies, permission or consent from relevant institutions or departments, or the user himself or himself, is required, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant regions.

[0128] Please refer to Figure 9, which is a schematic diagram of the structure of a device management device according to an embodiment of this application. This device management device can be applied to the second device 10a shown in Figure 1. As shown in Figure 9, the device management device 1 may include: an information acquisition module 91 and an operation code generation module 92;

[0129] Information acquisition module 91 is used to respond to scene addition operations in the device management platform, and to acquire device form information and service scene configuration information corresponding to the scene addition operation; the device form information indicates the first device;

[0130] The information acquisition module 91 is also used to determine the type of device operation for the first device;

[0131] The operation code generation module 92 is used to generate a device operation code corresponding to the first device based on the device form information, service scenario configuration information and device operation type; the device operation code is used to instruct the first device to execute an operation process that matches the device operation type based on the service scenario configuration information.

[0132] In one or more embodiments, the information acquisition module 91 responds to a scene addition operation in the device management platform, acquires the device form information and service scene configuration information corresponding to the scene addition operation, and performs the following steps:

[0133] In response to the scene addition operation in the device management platform, the service scene addition interface is displayed; the service scene addition interface includes a device selection area and a scene input area;

[0134] In response to a selection operation targeting a device selection area, obtain the device configuration information determined by the selection operation;

[0135] Respond to input operations targeting the scene input area and obtain the service scene configuration information determined by the input operation.

[0136] In one or more embodiments, the information acquisition module 91 responds to an input operation targeting the scene input area, acquires the service scene configuration information determined by the input operation, and performs the following steps:

[0137] Respond to input operations targeting the scene input area and obtain the scene name, scene template, and applicable scope determined by the input operation;

[0138] The scene name, scene template, and scope of application are defined as the service scene configuration information.

[0139] In one or more embodiments, the information acquisition module 91 is further configured to respond to a submission operation for device form information and service scenario configuration information, display an operation code configuration page that matches the device form information; and respond to a parameter configuration operation in the operation code configuration page, display the device operation type for the first device.

[0140] In one or more embodiments, the operation code configuration page includes an operation code display area;

[0141] The operation code generation module 92 is also used to create an operation code object corresponding to the first device; fill the operation code object with device form information, service scenario configuration information and device operation type to generate the device operation code corresponding to the first device; and display the device operation code in the operation code display area of ​​the operation code configuration page.

[0142] In one or more embodiments, the device management platform includes a scene management area, which includes a scene addition control and service scene details information corresponding to the first device managed by the management object; the scene addition control is used to trigger a scene addition operation.

[0143] According to one embodiment of this application, the relevant steps involved in the device management method shown in FIG2 above can be executed by various modules in the device management device 1 shown in FIG9. For example, steps S101 and S102 shown in FIG2 can be executed by the information acquisition module 91 shown in FIG9, and step S103 shown in FIG2 can be executed by the operation code generation module 92 shown in FIG9, etc.

[0144] According to one embodiment of this application, the modules in the device management device 1 shown in FIG9 can be individually or entirely merged into one or more modules, or some of the modules can be further divided into at least two functionally smaller units to achieve the same operation without affecting the technical effect of the embodiment of this application. The above modules are based on logical function division. In practical applications, the function of one module can also be implemented by at least two units, or the function of at least two modules can be implemented by one module. In other embodiments of this application, the device management device 1 may also include other modules or units. In practical applications, these functions can also be implemented with the assistance of other modules, and can be implemented by at least two modules working together.

[0145] In this embodiment, device form information can be selected for the first device managed by the managed object in the device management platform corresponding to the managed object, and service scenario configuration information can be set for it. The device operation type is input for the first device indicated by the device form information. Based on the device form information, service scenario configuration information, and device operation type, a device operation code can be generated for the first device in the device management platform. That is, configuration information for various swipe service scenarios and device operation types can be set in the device management platform, thereby generating various types of device operation codes. By reverse scanning and recognizing various types of device operation codes, the next operation process to be performed on the first device can be communicated, such as device initialization, device activation, and subsequent device maintenance, thereby improving the management efficiency of the first device.

[0146] Please refer to Figure 10, which is a second structural schematic diagram of a device management device provided in an embodiment of this application. This device management device can be applied to any of the second devices shown in Figure 1. As shown in Figure 10, the device management device 2 may include: an operation code recognition module 101 and a device configuration module 102;

[0147] The operation code recognition module 101 is used to recognize the device operation code through the camera component in the first device, and obtain the device form information, service scenario configuration information and device operation type carried by the device operation code; the device operation code is generated on the device management platform.

[0148] The device configuration module 102 is used to execute an operation process that matches the device operation type in the first device based on the service scenario configuration information if the first device meets the device form information and service scenario configuration information.

[0149] In one or more embodiments, the operation code recognition module 101 recognizes the device operation code through the camera component in the first device, and obtains the device form information, service scenario configuration information and device operation type carried by the device operation code, for use in performing the following steps:

[0150] The device operation code is identified by the camera component in the first device, and the valid time range corresponding to the device operation code is determined.

[0151] If the device operation code is detected to be within the valid time range, the device form information, service scenario configuration information, and device operation type carried by the device operation code are obtained.

[0152] In one or more embodiments, the device management apparatus further includes: an authorization verification module 103;

[0153] The permission verification module 103 is used to obtain the hardware form information and device identification information corresponding to the first device;

[0154] The permission verification module 103 is also used to determine that the first device satisfies the device form information if the hardware form information belongs to the device form information.

[0155] The permission verification module 103 is also used to verify the configuration permissions of the first device based on the service scenario configuration information and device identification information;

[0156] The permission verification module 103 is also used to determine that the first device has the configuration permission associated with the device operation code and that the first device meets the service scenario configuration information if the device identification information belongs to the scenario application scope in the service scenario configuration information.

[0157] In one or more embodiments, the operation code recognition module 101 in the device management device is further configured to:

[0158] If the device identification information does not fall within the scope of application of the service scenario configuration information, it is determined that the first device does not have the configuration permission associated with the device operation code, and the identification failure prompt message is output in the first device.

[0159] In one or more embodiments, the device operation code includes a network configuration code, the service scenario configuration information includes network connection parameters, and the device operation type includes network configuration.

[0160] Based on the service scenario configuration information, the device configuration module 102 executes an operation process matching the device operation type in the first device, which is used to perform the following steps:

[0161] Based on the network connection parameters, establish a communication connection between the first device and the router associated with the network configuration code;

[0162] If a communication connection is successfully established between the first device and the router, then the network configuration of the first device is considered successful.

[0163] In one or more embodiments, the device management device 2 further includes: a network detection module 104;

[0164] Network detection module 104 is used to start the first device and detect the network connection of the first device;

[0165] The network detection module 104 is also used to output network configuration prompt information in the first device if the network connection of the first device is detected to fail; the network configuration prompt information is used to instruct the second device to generate the network configuration code corresponding to the first device.

[0166] In one or more embodiments, the device operation code includes the device activation code, the service scenario configuration information includes the device activation operation parameters, and the device operation type includes device activation.

[0167] Based on the service scenario configuration information, the device configuration module 102 executes an operation process matching the device operation type in the first device, which is used to perform the following steps:

[0168] According to the equipment activation operation parameters, the first equipment is activated.

[0169] If the device activation parameters are configured in the first device, then the first device is confirmed to be successfully activated.

[0170] In one or more embodiments, the device operation code includes a factory reset code, the service scenario configuration information includes factory reset instruction parameters, and the device operation type includes factory reset.

[0171] Based on the service scenario configuration information, the device configuration module 102 executes an operation process matching the device operation type in the first device, which is used to perform the following steps:

[0172] Retrieve the initial system state and default configuration information indicated by the factory reset command parameters;

[0173] Replace the system state in the first device with the initial system state, and replace the configuration information in the first device with the default configuration information.

[0174] In one or more embodiments, the first device includes a palm-swiping device for use in access control service scenarios;

[0175] The device management device 2 also includes: a palmprint acquisition module 105, a palmprint matching module 106, a door lock opening module 107;

[0176] The palmprint acquisition module 105 is used to acquire a first palmprint image of the palm verification object and obtain a second palmprint image pre-stored by the palm verification object through the camera component in the palm-scanning device.

[0177] The palmprint matching module 106 is used to obtain the palmprint similarity between the first palmprint image and the second palmprint image;

[0178] The door lock opening module 107 is used to open the door lock for the palm verification object if the palm print similarity is greater than the similarity threshold.

[0179] According to one embodiment of this application, the relevant steps involved in the device management method shown in FIG4 above can be executed by various modules in the device management device 2 shown in FIG10. For example, step S201 shown in FIG4 can be executed by the operation code recognition module 101 shown in FIG10, and step S202 shown in FIG4 can be executed by the device configuration module 102 shown in FIG10, etc.

[0180] According to one embodiment of this application, the modules in the device management device 2 shown in FIG10 can be individually or entirely merged into one or more modules, or some of the modules can be further divided into at least two functionally smaller units to achieve the same operation without affecting the technical effect of the embodiment of this application. The above modules are based on logical function division. In practical applications, the function of one module can also be implemented by at least two units, or the function of at least two modules can be implemented by one module. In other embodiments of this application, the device management device 2 may also include other modules or units. In practical applications, these functions can also be implemented with the assistance of other modules, and can be implemented by at least two modules working together.

[0181] In this embodiment, device form information can be selected for the first device managed by the managed object in the device management platform corresponding to the managed object, and service scenario configuration information can be set for it. The device operation type is input for the first device indicated by the device form information. Based on the device form information, service scenario configuration information, and device operation type, a device operation code can be generated for the first device in the device management platform. That is, configuration information for various swipe service scenarios and device operation types can be set in the device management platform, thereby generating various types of device operation codes. By reverse scanning and recognizing various types of device operation codes, the next operation process to be performed on the first device can be communicated, such as device initialization, device activation, and subsequent device maintenance, thereby improving the management efficiency of the first device.

[0182] Please refer to Figure 11, which is a schematic diagram of the structure of a computer device provided in an embodiment of this application. As shown in Figure 11, the computer device 1000 can be a second device (such as a terminal device with an operable screen), for example, the second device 10a in the embodiment corresponding to Figure 1 above, or it can be a first device, for example, any of the first devices in the embodiment corresponding to Figure 1 above (such as a palm-swiping device). For ease of understanding, the following description uses the computer device as a second device as an example. The computer device 1000 may include: a processor 1001, a network interface 1004, and a memory 1005. In addition, the computer device 1000 may also include: a user interface 1003, and at least one communication bus 1002. The communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a Wi-Fi interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory, such as at least one disk storage device. Alternatively, the memory 1005 may be at least one storage device located remotely from the aforementioned processor 1001. As shown in FIG11, the memory 1005, as a computer-readable storage medium, may include an operating system, a network communication module, a user interface module, and a device control application program.

[0183] The network interface 1004 in the computer device 1000 can also provide network communication functions, and the optional user interface 1003 can also include a display screen and a keyboard. In the computer device 1000 shown in Figure 11, the network interface 1004 provides network communication functions; the user interface 1003 is mainly used to provide an input interface for the user; and the processor 1001 can be used to call the device control application stored in the memory 1005 to achieve:

[0184] Responding to the scene addition operation in the device management platform, it obtains the device form information and service scene configuration information corresponding to the scene addition operation; the device form information indicates the first device;

[0185] Determine the type of device operation for the first device;

[0186] Based on the device form information, service scenario configuration information, and device operation type, a device operation code corresponding to the first device is generated; the device operation code is used to instruct the first device to execute an operation process that matches the device operation type based on the service scenario configuration information.

[0187] Alternatively, the processor can be used to invoke the device control application stored in memory 1005 to achieve the following:

[0188] The device operation code is identified by the camera component in the first device to obtain the device form information, service scenario configuration information and device operation type carried by the device operation code; the device operation code is generated on the device management platform.

[0189] If the first device meets the device form information and service scenario configuration information, then based on the service scenario configuration information, the operation process matching the device operation type is executed in the first device.

[0190] It should be understood that the computer device 1000 described in the embodiments of this application can execute the device management method described in any of the embodiments of Figures 2, 4 and 8 above, and can also execute the device management device 1 described in the embodiment corresponding to Figure 9 above or the device management device 2 described in the embodiment corresponding to Figure 10 above, which will not be repeated here. In addition, the beneficial effects of using the same method will not be repeated here.

[0191] Furthermore, it should be noted that this application embodiment also provides a computer-readable storage medium, which stores a computer program executed by the aforementioned device management device 1 or device management device 2. The computer program includes computer instructions, and when the processor executes the computer instructions, it can execute the device management method described in any of the embodiments of Figures 2, 4, and 8. Therefore, it will not be repeated here. Additionally, the beneficial effects of using the same method will not be repeated. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc. For technical details not disclosed in the embodiments of the computer-readable storage medium involved in this application, please refer to the description of the method embodiments of this application. As an example, the program instructions can be deployed and executed on a computer device, or on multiple computer devices located in one location, or on multiple computer devices distributed in multiple locations and interconnected through a communication network. Multiple computer devices distributed in multiple locations and interconnected through a communication network can form a blockchain system.

[0192] Furthermore, it should be noted that this application also provides a computer program product, which may include a computer program stored in a computer-readable storage medium. The processor of a computer device reads the computer program from the computer-readable storage medium and executes the computer program, causing the computer device to perform the device management method described in any of the embodiments of Figures 2, 4, and 8 above. Therefore, these descriptions will not be repeated here. Additionally, the beneficial effects of using the same method will not be repeated here either. For technical details not disclosed in the computer program product or computer program embodiments involved in this application, please refer to the description of the method embodiments of this application.

[0193] In summary, this application provides a device management method, apparatus, computer device, computer-readable storage medium, and computer program product. By having a second device respond to a scene addition operation in the device management platform, it obtains device form information and service scene configuration information corresponding to the scene addition operation, enabling precise location of the characteristics and service scene requirements of the first device to be managed. The device form information clarifies the device's type, model, and other basic attributes, while the service scene configuration information specifies the device's usage scenario and related parameters, providing an accurate basis for subsequent operations. Determining the device operation type for the first device makes management instructions more targeted; different operation types correspond to different device management needs, such as initialization and activation. Based on the device form information, service scene configuration information, and device operation type, a device operation code corresponding to the first device is generated, integrating multiple key information into a single operation code. This reduces the complexity of information transmission, improves the efficiency and accuracy of information delivery, avoids the cumbersome and error-prone multi-step operations of traditional management methods, and thus improves the overall efficiency of device management.

[0194] Furthermore, when responding to scene addition operations in the device management platform, a service scene addition interface is displayed, including a device selection area and a scene input area. By responding to selection operations in the device selection area, device form information is obtained. This intuitive selection method reduces information acquisition errors, avoids errors that may occur due to manual input, and improves the accuracy of device form information acquisition. Responding to input operations in the scene input area retrieves service scene configuration information, enabling managed objects to flexibly set service scenes according to actual needs, enhancing the flexibility and personalization of service scene configuration, and improving the adaptability of device management.

[0195] Furthermore, in response to input operations targeting the scene input area, the system obtains the scene name, scene template, and applicable scope determined by the input operation, and identifies these as service scene configuration information. The scene name clarifies the specific content of the service scene, the scene template provides a standardized pattern for configuring the service scene, and the applicable scope defines the target audience and scope of the service scene. This explicit information identification method makes the service scene configuration information more complete and accurate, and the generated device operation codes can more accurately reflect management needs, improving the relevance and effectiveness of device operations and reducing unnecessary operations and resource waste.

[0196] Furthermore, when determining the device operation type for the first device, in response to the submission of device form information and service scenario configuration information, an operation code configuration page matching the device form information is displayed. This ensures that the operation code configuration page is compatible with the actual form of the device, avoiding information input errors or operational inconveniences caused by page mismatch. Responding to parameter configuration operations on the operation code configuration page displays the device operation type for the first device, making the determination of the device operation type more scientific and reasonable, matching the device form information and service scenario configuration information, improving the adaptability of device operations, and thus improving the efficiency and accuracy of device management.

[0197] Furthermore, the operation code configuration page includes an operation code display area. An operation code object corresponding to the first device is created, and this object is populated with device type information, service scenario configuration information, and device operation type to generate the device operation code for the first device, which is then displayed in the operation code display area. The creation of the operation code object encapsulates relevant information, improving information security and integrity, and preventing information from being tampered with or lost during transmission and storage. The operation code display area allows management entities to intuitively view and use device operation codes, improving the accessibility and efficiency of operation codes.

[0198] Furthermore, the device management platform includes a scene management area, which contains scene addition controls and service scene details for the first device managed by the managed object. The scene addition controls are used to trigger scene addition operations. This layout design provides a convenient entry point for managed objects, making scene addition operations more intuitive and easier to execute. Simultaneously, the display of service scene details allows managed objects to promptly understand the service scene status of the device, facilitating management and adjustments, and improving the operability and real-time performance of device management.

[0199] Furthermore, the first device uses its camera component to identify the device operation code, determine the valid time range corresponding to the operation code, and if the operation code is detected to be within the valid time range, acquire the device form information, service scenario configuration information, and device operation type carried by the operation code. This time range detection mechanism ensures that the first device only processes valid operation codes, avoids the execution of invalid operations, reduces device resource consumption and processing burden, and improves the security and reliability of device operation. At the same time, identification via the camera component eliminates the need for additional complex equipment or interfaces, improving the convenience and versatility of device operation code identification.

[0200] Furthermore, the hardware form factor information and device identification information corresponding to the first device are obtained. If the hardware form factor information belongs to the device form factor information, then the first device is determined to meet the device form factor requirements. This step ensures the matching of device form factor information, avoids mismatched devices performing incorrect operations, and improves the accuracy of device operation. Based on the service scenario configuration information and device identification information, the configuration permission of the first device is verified. If the device identification information falls within the applicable scope of the service scenario configuration information, then the first device is determined to have the configuration permission associated with the device operation code, and the first device is determined to meet the service scenario configuration information. This strict permission verification mechanism ensures that only the first device that meets the conditions can execute the operation indicated by the device operation code, preventing unauthorized or unpermitted devices from performing operations, and improving the security and accuracy of device management.

[0201] Furthermore, if the device identification information does not fall within the scope of application of the service scenario configuration information, it is determined that the first device does not have the configuration permission associated with the device operation code, and a recognition failure message is output on the first device. This provides timely feedback on the operation result, allowing the managed object to understand the device status in a timely manner, avoiding the continued execution of invalid operations, reducing waste of device resources and processing time, and improving the efficiency of device management. At the same time, the output methods of the recognition failure message are diversified, such as text display, voice playback, and indicator light flashing, which can adapt to different types of devices and improve the accessibility of the message.

[0202] Furthermore, when the device operation code includes a network configuration code, the service scenario configuration information includes network connection parameters, and the device operation type includes network configuration, a communication connection is established between the first device and the router associated with the network configuration code based on the network connection parameters. If a communication connection is successfully established between the first device and the router, the network configuration of the first device is considered successful. This automatic network configuration method avoids manual intervention, reduces the time and workload of network configuration, and improves the efficiency and stability of device network connections. Simultaneously, by carrying network connection parameters through the network configuration code, errors that may occur when manually entering parameters are avoided, thus improving the accuracy of network configuration.

[0203] Furthermore, the first device is activated, and its network connectivity is checked. If a network connection failure is detected, a network configuration prompt message is output on the first device, instructing the second device to generate the corresponding network configuration code for the first device. This provides an automatic error correction and guidance mechanism for the network configuration of the first device, ensuring that the device can connect to the network in a timely manner and improving device availability. The output of the network configuration prompt message allows the management entity to understand the network status of the device in a timely manner and take corresponding measures, improving the real-time performance of device management.

[0204] Furthermore, when the device operation code includes a device activation code, the service scenario configuration information includes device activation operation parameters, and the device operation type includes device activation, the first device is activated according to the device activation operation parameters. If the configuration of the device activation operation parameters is completed in the first device, then the activation of the first device is considered successful. This achieves automatic activation of the first device, simplifies the device initialization process, reduces the complexity and error rate of manual operation, and improves the deployment efficiency of the device. At the same time, the unified management and configuration of the device activation operation parameters ensures the consistency and accuracy of device activation.

[0205] Furthermore, when the device operation code includes a factory reset code, the service scenario configuration information includes factory reset command parameters, and the device operation type includes factory reset, the system retrieves the initial system state and default configuration information indicated by the factory reset command parameters, replaces the system state in the first device with the initial system state, and replaces the configuration information in the first device with the default configuration information. This provides the first device with the function of restoring to its initial state, facilitating device maintenance and management. When the device malfunctions or has a configuration error, it can quickly return to a normal state, reducing device downtime and improving device maintainability and reliability.

[0206] Furthermore, when the first device includes a palm-scanning device and is used in an access control service scenario, the camera component in the palm-scanning device captures a first palmprint image of the palm verification object, obtains a pre-stored second palmprint image of the palm verification object, and calculates the palmprint similarity between the first and second palmprint images. If the palmprint similarity is greater than a similarity threshold, the door lock is opened for the palm verification object. The application of palmprint recognition technology improves the security of the access control system because palmprints are unique and stable, making them difficult to forge. Simultaneously, image acquisition via a camera component eliminates the need for additional contactless devices, improving the convenience and hygiene of access control. The similarity threshold setting allows for adjustment of access control security and pass rate according to actual needs, improving the adaptability of the access control system.

[0207] Furthermore, the device operation code is generated using QR code encoding principles. Device form information, service scenario configuration information, and device operation type are preprocessed and converted into a suitable encoding format. Then, the data is concatenated, segmented, encoded, and error-correcting codes are added to generate a QR code matrix. This encoding method improves the information carrying capacity of the device operation code, allowing it to accommodate more management information. Adding error-correcting codes enhances the fault tolerance of the device operation code during scanning and recognition. Even if the device operation code is partially damaged or interfered with, the information can still be accurately read, reducing recognition failures caused by scanning environment or equipment problems, and improving the success rate and stability of device operation code recognition.

[0208] Furthermore, the swiping device uses a universal ROM for activation. This universal ROM offers broad compatibility, allowing flashing and installation across different models and brands of devices, providing basic system functions and features. This lowers the technical barrier to device activation, reduces the need for different activation methods and tools depending on the device model, and improves the universality and convenience of activation. This makes it easier to activate and configure different types of swiping devices, while also reducing activation costs and time.

[0209] The terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish different media content, not to describe a specific order. Furthermore, the term "comprising," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, apparatus, product, or device that includes a series of steps or units is not limited to the listed steps or modules, but may optionally include steps or modules not listed, or may optionally include other step units inherent to these processes, methods, apparatuses, products, or devices.

[0210] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0211] The methods and related apparatus provided in this application are described with reference to the method flowcharts and / or structural diagrams provided in this application. Specifically, each block of the method flowcharts and / or structural diagrams, as well as combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing device, create means for implementing the functions specified in one or more blocks of the flowcharts and / or one or more blocks of the structural diagrams. These computer program instructions can also be stored in a computer-readable storage medium capable of directing a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more blocks of the flowcharts and / or one or more blocks of the structural diagrams. These computer program instructions may also be loaded onto a computer or other programmable data processing 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 one or more flowcharts and / or one or more blocks in the structural diagram.

[0212] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0213] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0214] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A device management method, executed by a second device, comprising: In response to a scene addition operation in the device management platform, obtain the device form information and service scene configuration information corresponding to the scene addition operation; The device configuration information indicates the first device; Determine the device operation type for the first device; and Based on the device form information, the service scenario configuration information, and the device operation type, a device operation code corresponding to the first device is generated; the device operation code is used to instruct the first device to execute an operation process that matches the device operation type based on the service scenario configuration information.

2. The method according to claim 1, wherein the step of responding to a scene addition operation in the device management platform and obtaining the device form information and service scene configuration information corresponding to the scene addition operation includes: In response to the scene addition operation in the device management platform, the service scene addition interface is displayed; The service scenario addition interface includes a device selection area and a scenario input area; In response to a selection operation on the device selection area, obtain the device form information determined by the selection operation; In response to an input operation targeting the scene input area, obtain the service scene configuration information determined by the input operation.

3. The method according to claim 2, wherein the response to an input operation in the scene input area, obtaining service scene configuration information determined by the input operation, includes: In response to an input operation targeting the scene input area, obtain the scene name, scene template, and scene applicable scope determined by the input operation; The scenario name, the scenario template, and the scope of application of the scenario are determined as the service scenario configuration information.

4. The method according to any one of claims 1 to 3, wherein determining the device operation type for the first device includes: In response to the submission operation for the device form information and the service scenario configuration information, an operation code configuration page matching the device form information is displayed; In response to parameter configuration operations on the operation code configuration page, the device operation type for the first device is displayed.

5. The method according to claim 4, wherein the operation code configuration page includes an operation code display area; The step of generating a device operation code corresponding to the first device based on the device form information, the service scenario configuration information, and the device operation type includes: Create the opcode object corresponding to the first device; The device operation code corresponding to the first device is generated by filling the device form information, the service scenario configuration information and the device operation type into the operation code object. The device operation code is displayed in the operation code display area of ​​the operation code configuration page.

6. The method according to any one of claims 1 to 5, wherein the device management platform includes a scene management area, the scene management area includes a scene adding control, and service scene details information corresponding to the first device managed by the management object; the scene adding control is used to trigger the scene adding operation.

7. A device management method, executed by a first device, comprising: The device operation code is identified by the camera component in the first device, and the device form information, service scenario configuration information and device operation type carried by the device operation code are obtained. The device operation code is generated on the device management platform; If the first device satisfies the device form information and the service scenario configuration information, then based on the service scenario configuration information, an operation process matching the device operation type is executed in the first device.

8. The method according to claim 7, wherein the step of identifying the device operation code through the camera component in the first device and obtaining the device form information, service scenario configuration information, and device operation type carried by the device operation code includes: The device operation code is identified by the camera component in the first device, and the valid time range corresponding to the device operation code is determined. If the device operation code is detected to be within the valid time range, the device form information, service scenario configuration information, and device operation type carried by the device operation code are obtained.

9. The method according to claim 7 or 8, further comprising: Obtain the hardware configuration information and device identification information corresponding to the first device; If the hardware form information belongs to the device form information, then the first device is determined to satisfy the device form information; Based on the service scenario configuration information and the device identification information, the first device is configured with permission verification. If the device identification information falls within the scope of application of the service scenario configuration information, then it is determined that the first device has the configuration permissions associated with the device operation code, and that the first device satisfies the service scenario configuration information.

10. The method according to claim 9, further comprising: If the device identification information does not fall within the scope of application of the service scenario configuration information, it is determined that the first device does not have the configuration permission associated with the device operation code, and an identification failure prompt message is output in the first device.

11. The method according to any one of claims 7 to 10, wherein the device operation code includes a network configuration code, the service scenario configuration information includes network connection parameters, and the device operation type includes network configuration; The step of executing an operation process matching the device operation type in the first device based on the service scenario configuration information includes: Based on the network connection parameters, establish a communication connection between the first device and the router associated with the network configuration code; If the first device successfully establishes a communication connection with the router, then the network configuration of the first device is determined to be successful.

12. The method according to claim 11, further comprising: Start the first device and check its network connectivity. If the network connection of the first device is detected to be unsuccessful, a network configuration prompt message is output in the first device; the network configuration prompt message is used to instruct the second device to generate a network configuration code corresponding to the first device.

13. The method according to any one of claims 7 to 12, wherein the device operation code includes a device activation code, the service scenario configuration information includes device activation operation parameters, and the device operation type includes device activation; The step of executing an operation process matching the device operation type in the first device based on the service scenario configuration information includes: According to the device activation operation parameters, the first device is activated. If the device activation operation parameters are configured in the first device, then the first device is determined to be successfully activated.

14. The method according to any one of claims 7 to 13, wherein the device operation code includes a factory reset code, the service scenario configuration information includes factory reset instruction parameters, and the device operation type includes factory reset; The step of executing an operation process matching the device operation type in the first device based on the service scenario configuration information includes: Obtain the initial system state and default configuration information indicated by the factory reset command parameters; Replace the system state in the first device with the initial system state, and replace the configuration information in the first device with the default configuration information.

15. The method according to any one of claims 7 to 14, wherein the first device includes a palm-swiping device, the palm-swiping device being used in an access control service scenario; The method further includes: The first palm print image of the palm verification object is captured by the camera component in the palm scanning device, and the second palm print image pre-stored by the palm verification object is obtained. Obtain the palmprint similarity between the first palmprint image and the second palmprint image; If the palm print similarity is greater than the similarity threshold, then the door lock is opened for the palm verification object.

16. An equipment management device, comprising: The information acquisition module is used to respond to the scene addition operation in the device management platform and acquire the device form information and service scene configuration information corresponding to the scene addition operation; The device configuration information indicates the first device; The information acquisition module is also used to determine the type of device operation for the first device; and The operation code generation module is used to generate a device operation code corresponding to the first device based on the device form information, the service scenario configuration information, and the device operation type; the device operation code is used to instruct the first device to execute an operation process that matches the device operation type based on the service scenario configuration information.

17. An equipment management device, comprising: The operation code recognition module is used to recognize the device operation code through the camera component in the first device, and obtain the device form information, service scenario configuration information and device operation type carried by the device operation code; the device operation code is generated in the device management platform; and The device configuration module is used to execute an operation process matching the device operation type in the first device based on the service scenario configuration information if the first device meets the device form information and the service scenario configuration information.

18. A computer device, comprising a memory and a processor; The memory is connected to the processor, the memory is used to store computer programs, and the processor is used to invoke the computer programs so that the computer device performs the method according to any one of claims 1 to 6, or performs the method according to any one of claims 7 to 15.

19. A computer-readable storage medium storing a computer program adapted to be loaded and executed by a processor to cause a computer device having the processor to perform the method of any one of claims 1 to 6, or to perform the method of any one of claims 7 to 15.

20. A computer program product comprising a computer program that, when executed by a processor, implements the method of any one of claims 1 to 6, or implements the method of any one of claims 7 to 15.

Images