Product Feature Description Manual
The product feature description is maintained separately for the Max and Standard versions. Use the tabs below to switch and view the corresponding version.
- Max
- Standard
Product Overview
PalmAI Max is a Palm Application Platform service built on world-leading "palm print + palm vein" recognition technology, providing end-to-end capabilities from palm registration, palm scan recognition, and identity verification to user and device management. At the algorithm level, it supports three modes: Cloud Recognition, On-device Recognition, and Hybrid Recognition. At the application level, it covers the complete business loop across the admin console, the device side, the mobile side, and the open API.
The platform supports palm databases of tens of thousands of palms or more: when the palm database exceeds 50,000, the device side downloads only 50,000 palm features under a time-first policy, and hybrid recognition latency is kept within 2 seconds. The A3 module achieves an average palm scan comparison time of less than 800 ms, reaching algorithm metrics of FRR=0.1% and FAR=0.01% at a 50k database scale. The platform is compatible with M3, M4, M3B, and M4B devices and A3/A3B modules, supports the rv1126b chip platform, and applies to business scenarios such as membership eKYC, passage, access control, attendance, meetings, and visitors.
The platform delivers the server side, device side, mobile side, API, SDK, and other deliverables: the server side provides the admin console and open APIs for customers to integrate with their own business systems; the device side provides M3/M4 series device software and Host supporting capabilities; the mobile side provides the Mobile Palm Registration SDK (Android/iOS/Flutter/WeChat Mini Program) and the Palm Scan app. The mobile-side Mobile Palm Registration capability is a value-added optional service; the palm scan attendance, meeting, and visitor applications are offered as add-on options.
Feature Description
Note: This table is based on the latest version (v2.5) and cumulatively presents the full feature set of the product across all sides (server side, device side, and mobile side).
| Module | Feature | Description | Remark |
| Palm Registration Applications | Mobile Palm Registration | Provides the Mobile Palm Registration SDK (Android/iOS native, Flutter, and Mini Program versions), allowing users to complete palm registration on their phones. The Flutter version is feature-aligned with the native SDK and supports registration, verification (1:1), and identification (1:N) modes. The Mini Program version supports palm registration and palm scan recognition within the Mini Program, device discovery and connection (Bluetooth/BLE), result display, and error prompts with retry, and ships with type definitions, integration documentation, and sample projects, supporting integration and operation in WeChat Mini Programs. Supports multi-tenant registration and configuration, so different tenants can use independent Mobile Palm Registration flows and parameters. Supports dual-palm pre-registration. The Mobile Palm Registration SDK and the server-side liveness detection algorithm are continuously upgraded; optimal feature selection for Mobile Palm Registration is performed by a dedicated server-side selection SDK | Value-added optional service |
| Provides Android/iOS test apps for customers to experience Mobile Palm Registration | This app must not be used for formal delivery | ||
| H5 Palm Registration | Supports H5 QR Code Palm Registration: users fill in registration information on a mobile H5 page and generate a registration QR code; after the device scans the code, palm collection begins directly, with real-time tracking of registration progress. Supports customized H5 palm registration, which can display a customer-specified URL after palm scan | Users can develop their own registration UI | |
| Device-Side Palm Registration | Supports registering palms directly on devices. M3/M4 devices support dual palm registration: after entering the UserID, the device automatically queries the registered palm status and supports adding a second palm, automatically marking the primary/secondary palm roles. Supports external device palm registration, with Windows/Mac experience applications provided | External devices require user-side development | |
| Host Palm Registration | Supports dual-palm enrollment and management via the Host, with the result page showing the user's dual-palm registration status. Supports registration status display and registration result confirmation, with an entry to delete users. Duplicate registration detection displays registered user IDs and user names for quick location of existing registration records. Supports the Device Scan QR registration flow, returning user ID and user name when the device reports registration results | ||
| Palm Scan Applications | Palm Scan Recognition | Supports three modes: On-device Recognition, Cloud Recognition, and Hybrid Recognition. Hybrid search supports distributing part of the palm database to devices according to verification rules, and devices can pull required user features in advance per verification rules. When the palm database exceeds 50,000, the device side downloads only 50,000 palm features under a time-first policy, and overall hybrid recognition latency is kept within 2 seconds. Supports recognition in scenarios where the palm approaches from far to near. Supports stable verification in scenarios where devices are bound to a large number of verification rules and synchronize a large number of user features | |
| High Similarity Handling | Supports a high-similarity palm handling strategy: under pure On-device Recognition, high-similarity palms are rejected directly; under Hybrid/Cloud strategies, Additional Verification is pushed to verify identity. During registration, high-similarity palms are allowed into the database and tagged; registration is not rejected. Provides a high-similarity deduplication switch for registration, allowing per-scene selection of whether to reject duplicate registration when high similarity is detected. Provides a dedicated algorithm optimization for elderly users to improve palm scan recognition for the elderly | ||
| Additional Verification | Supports Additional Verification after palm scan to verify identity, including verification by the last four digits of the phone number, custom numeric field verification (custom numeric fields such as employee ID or device number, supporting length rules of 4-8 digits), and CPM device scan code verification (after palm scan passes, the device scans an authentication QR code on the mobile side; the QR code validity follows the console configuration, with a 60-second scan timeout). Compatible with scan code verification for legacy users not registered via Mobile Palm Registration. When high-similarity users scan palms, the auxiliary background images are compared against all background images on demand, and Additional Verification is pushed if the comparison fails. Supports verification by third-party systems: after palm scan, a request is made to the third-party system to determine whether verification passes | ||
| Offline Verification | Supports palm scan verification in offline state, with verification records uploaded after the network recovers. In Cloud mode, a network exception prompt is displayed within 3 seconds when scanning palms while offline. In Hybrid mode, the system automatically degrades to On-device Recognition when the network is down. Provides granular network Error Codes to distinguish between network disconnection and unregistered users | ||
| Mobile-Side Verification | Supports completing 1:1 identity verification by scanning palms on the phone. The H5 version supports 1:1/1:N palm comparison in a mobile browser environment. The mobile side reports success/failure verification records, completing the mobile-side verification data chain | ||
| Blocklist | Supports adding user palms to the Blocklist; palms on the Blocklist are denied passage during verification. When a user registers both palms, adding only one palm to the Blocklist still blocks correctly. Blocklist API performance and local encryption of cached data are continuously maintained | ||
| Device Settings | System Settings | Supports viewing About This Device (device MAC address, local version, SN information, associated scenes). Supports setting the daily automatic restart time of the device. Supports clearing the local palm database manually. Supports wireless and wired network configuration, with Wi-Fi password length up to 32 characters. Supports Developer Mode log upload, password management, and module scan code activation | |
| Multi-Language Switching | Supports multi-language switching on M3/M4 devices: after selecting a language in the Settings module, device text and voice packages take effect immediately. Supports Simplified Chinese, English, Cantonese, and French; content missing a translation falls back to English | ||
| Mode Switching | Supports switching the device between Registration Mode and Recognition Mode via commands | ||
| Wiegand Access Control Integration | Supports Wiegand output of physical card numbers after palm scan. M3 supports 64-bit Wiegand protocol adaptation for integrating with access control systems to enable palm scan passage. The physical card number field in user management supports 0-66 bits, compatible with extended Wiegand protocol bit lengths | 64-bit Wiegand only on M3 devices | |
| Remote Door Opening | Supports the remote door opening feature on M3 devices, implemented via the MQTT protocol for remote control | M3 devices only | |
| 4G Network | M3B devices support 4G cellular network connection. Supports remotely operating module files and simulating license expiration via whole-device commands, avoiding device and module disassembly | 4G only on M3B devices | |
| Admin Console | Multi-Tenant Management | Supports a multi-tenant architecture: the super admin can create, edit, and delete tenants, allocate tenant quotas (palm database capacity/device capacity), and switch tenant views. Supports creating and assigning tenant admins, who can only manage data of their own tenant. Supports data isolation and business/permission isolation between tenants. Supports layered management of tenant-level and platform-level configurations. Access links carrying a tenant APPID prefix automatically switch to the corresponding tenant, and a single browser can access different tenants independently in multiple tabs, compatible with existing links and single-tenant access patterns | |
| Data Cockpit | Provides a Dashboard data board: data overview (total devices/total registered users/total palms/palm database capacity); real-time display of today's data (today's palm scans/palm scan users/new activations/online devices); user data trend charts (daily new activated users/palms, daily active users, user status distribution); device data and palm scan data trend charts, with data export for up to 180 days; verification statistics covering all verification records, with filtering by time and export | ||
| User Management | Supports creating, editing, and deleting users (individually on the page or in batch via Excel), with batch user deletion and secondary confirmation. Supports modifying the UserID of registered users. Supports unified management of dual palms (left palm/right palm) under a single UserID, providing user status (no valid palm/left palm available/right palm available/both palms available) and a primary palm field. Provides a user registration method field (device input registration, Mobile Palm Registration via phone, phone QR Code Palm Registration, device scan QR registration, and Host registration). Supports querying user access scope by user. Supports batch export of user information. Phone number entry supports fuzzy country search in English. Sensitive information such as phone numbers and names can be displayed encrypted | ||
| User Tags | Supports creating, editing, deleting, and batch importing user tags. Supports organization/department hierarchical structures. The user list supports filtering by tag. Supports setting verifiable personnel by tag. Provides same-name tag prompts and creation permission control | ||
| Device Management | Supports device registration, editing, deletion (individually on the page or in batch via Excel), and batch export. The device list displays complete information including device SN, device name, device Type, module Type, device status, module validity, application version, module version, system version, algorithm version, and associated scenes, with fuzzy search, filtering by status, filtering by resource-level health, and export. Provides a device list statistics module showing online/offline/abnormal device counts and status overview. Device time zones are synchronously configured from the cloud | ||
| Device Monitoring | Provides a full-device monitoring panel with views including data overview, health trends and distribution, resource levels, camera status, risk rankings, and OTA upgrade trends; data auto-refreshes every 5 minutes with permission control. Supports M3/M4 module and camera status monitoring and reporting (5-minute cycle); abnormalities are reported after automatic restart. Issue reporting supports module abnormality and camera abnormality scenarios | ||
| Scene Management | Supports creating, editing, and deleting scenes (individually on the page or in batch via Excel), batch association of devices, and manual input of the scene ID at creation. Provides scene group management. Supports combined configuration of open and closed scenes, automatically adjusting recognition strategy and security level by scene Type. Provides 4 scene strategy templates, supports binding scene strategies and distributing configurations to devices per scene. Scene configuration supports verification mode selection (Strict Mode/Convenience Mode); Strict Mode allows only the primary palm to pass | ||
| Verification Rules | Supports verification rule management to restrict who can scan palms on different devices, as well as counts and time windows, with settings by user tag, specified users, or time periods. Supports distributing the device-side palm database by verification rules and synchronizing user information. Provides tenant-level default passage behavior configuration when no verification rule is hit (allow passage/deny passage), defaulting to allow passage; configuration changes are recorded in operation logs | ||
| Verification Records | Supports viewing, filtering, and batch export of verification records. Successful and failed palm scan records are displayed separately, and failure reasons can be viewed for failed records. Supports filtering by device-side/mobile-side end Type. Cloud and device-side Error Codes prompts are aligned. After a scene or scene group is deleted, the scene name and scene group still display correctly in verification records. Supports disabling asynchronous push of palm scan records. Provides palm scan result page time configuration to customize how long the result page displays after a successful palm scan | ||
| Verification Record Push | Supports configuring verification record push addresses (Webhook), providing add/delete/update/query of addresses. Supports configuring the push scope; verification records are pushed to the specified address per configuration | ||
| Application Management | Palm scan attendance, meeting, and visitor applications are integrated into the Application Management module of the admin console and listed as add-on options, displaying deployment, purchase, and activation status of applications, with single sign-on redirect from the console into the application management systems. A three-layer management model is established: system-level purchase and deployment, tenant-level activation and deactivation, and user-level display based on activation status. Provides a unified user-side H5 entry supporting both generic links and tenant-specific links, with displayed content consistent with the current tenant's application activation status | Add-on option | |
| Scene Applications | Provides visitor, meeting, and attendance scene applications: the visitor application supports issuing visitor passes in on-site/appointment modes, working with the platform to complete palm print verification and passage. The attendance application integrates with platform accounts, providing H5 leave pages, holiday management, attendance group tags, abnormal attendance punch management, Host registration support, and data export capabilities | Add-on option | |
| Compliance Information Signing | When an admin of the Indonesia demo environment first logs in to the admin console, the completeness of enterprise full name, contact name, and contact email is verified; entry to the admin console is blocked until the compliance agreement is signed. The compliance agreement is displayed in both Chinese and English versions, and signing information is persisted to the database for traceability | ||
| Permission Management | Provides role and permission management with 5 built-in roles; supports creating administrators and assigning account permissions. All types of administrators can change their own passwords in the admin console (length 8-100 characters, containing at least three of uppercase letters, lowercase letters, digits, and special symbols; must not contain 4 or more consecutive ascending or descending characters; the new password must not repeat the old password). Login sessions support sliding renewal, and the frontend provides session keep-alive heartbeats to avoid login expiration when submitting long forms | ||
| Audit Logs | Provides an operation log module recording administrators' system operations (IP address, user name, operation time, operation Type, operation result). Records audit logs for API request processing to support call tracing. Covers operations in IoT device management and scene management modules (upgrade package management, upgrade campaign management, upgrade tasks, device management, device log management, remote commands, etc.). Supports log backup and forwarding to third-party systems. The audit log list supports exporting the current filtered results to Excel | ||
| Multi-Timezone Display | Server time is uniformly aligned via NTP. System management provides timezone settings and status display with daylight saving time marking. The web side supports switching display according to the local browser/server timezone, and page times are uniformly labeled with the current timezone | ||
| System Settings | Supports display of system version information and viewing of upgrade records. Supports switching among Chinese, Japanese, and English. Supports uploading the admin console logo. Fields such as device SN, scene, tenant, and verification rule support fuzzy search, with results ranked by exact/prefix/suffix/middle matching; user name, user ID, and similar fields support exact matching; grouped dropdown selection of search fields is supported | ||
| Authorization Management | The platform authorization file can be bound to the Max or Standard version, with different versions corresponding to different feature scopes. Supports a tenant count authorization dimension, limiting the number of tenants that can be created per License. Palm database capacity is strictly calculated by palm count; feature upgrades/dual writes do not consume palm capacity License | ||
| Deployment & Operations | Deployment Adaptation | Provides standalone and TKE cluster deployment solutions with O&M guidance. Supports pure CPU-based service deployment. Supports upgrade and data migration from Standard to Max versions. Supports delivery on the TCS base. Supports O&M monitoring and log analysis for Azure cluster versions. O&M configurations are consolidated into a single copy to reduce multi-environment maintenance costs | |
| Upgrade Management | Supports OTA upgrades; firmware, module, application, and algorithm can be upgraded independently with version dependencies set; supports upgrading specified devices, silent upgrade, and repeated upgrade, with upgrade configuration output per package. OTA upgrade tasks use an immediate push mechanism: after a task is created, the device is notified by command to pull immediately. Pre-checks are provided when adding devices to an upgrade task (device not registered, upgrade Type mismatch, already in another upgrade task), with one-click clearing of invalid devices; batch adding devices supports directly entering multiple device SNs. Provides an upgrade ledger showing upgrade records for all devices at the granularity of upgrade tasks (task creation time, device SN, upgrade Type, versions before and after upgrade, upgrade status, last failure reason, etc.), with query, filtering, and export; viewing permissions can be associated with super admin, tenant admin, and device admin roles | ||
| Remote Commands | Supports issuing remote operation commands to devices from the admin console over the MQTT protocol. Supports batch dispatch and device validity check. Supports remotely issuing Wi-Fi configuration with command detail viewing; the device side supports Wi-Fi configuration cache management (up to 10 entries, with add/delete and reorder), automatically polling and reconnecting to cached Wi-Fi after network disconnection. The standalone version supports retrieving device logs via remote commands. Under weak network conditions, the timeout for device commands and logs is extended to 12 hours | ||
| Resource Level Alarms | Device-side data reporting includes resource usage and resource level alarm information, supporting monitoring of CPU, memory, storage, and other resources | ||
| Data Backup | Provides a daily automatic data backup tool for the standalone version; when backup space is full, the earliest backups are automatically cleaned up; non-disruptive data backup is supported | ||
| Service Self-Check Tool | Supports automatically running full feature verification and API interface tests after system installation and configuration. Supports internationalization, adapting prompts and error messages for multiple languages. Self-check reports display service version numbers in a format aligned with device batch self-check reports; check item numbers are unified as numeric and support one-click copy | ||
| Device Self-Check Tool | Supports the device side automatically running full feature verification, API interface tests, performance tests, and other cases, outputting run result reports. Provides a deep diagnosis entry for abnormal results, supporting detection of local IP, DNS, routing, and other network configurations | ||
| Troubleshooting | Supports device-side and server-side log collection and analysis, completing an end-to-end problem analysis chain. Event details in troubleshooting tools support liveness detection RGB image display (optional reporting) to facilitate verification problem analysis. Provides an end-to-end acceptance automation tool covering automated verification of the full chain of device registration, feature synchronization, and palm scan verification, with batch execution of acceptance cases and HTML acceptance reports. Provides a resource estimation tool to size standalone resources by palm database/device scale, automatically extending the resource list when exceeded and prompting a switch to the cluster version when standalone cannot support it. Provides scripts for success/failure verification count statistics, license expiration monitoring and alerting, dashboard monitoring, and weekly/daily O&M report email push configuration | ||
| M4 O&M Capabilities | M4 devices support parsing the latest system version number. M3 devices support communication with the system-level daemon, enabling application upgrades through the daemon. Module firmware upgrades can carry the latest algorithm package and upgrade together | ||
| API | User Management APIs | Provides APIs to create, edit, delete, and query users, with returned fields subject to mandatory server-side masking. User creation and editing APIs support the tag field. Provides APIs to create, edit, and delete user tags. Provides a batch palm registration status sync API supporting batch query of user registration status by user ID list. Provides user status and palm status APIs for fine-grained dual-palm status management. The user information query API supports returning the full set of admin console user information, including the registration method field | |
| Palm Print Management APIs | Provides the palm print unbinding API and the API to query user palm registration status. Registration/recognition APIs support returning the palm direction field | The palm direction field is for the open-source community edition | |
| Verification Record APIs | Provides the verification record retrieval API and the verification record push API. Provides an API to create verification records. The query verification record list API supports a scene group name return field and a sort-by-verification-time parameter | ||
| Verification Rule APIs | Provides verification rule create, edit, and delete APIs and the query verification rule list API | ||
| Scene Management APIs | Provides scene management APIs. Provides the query scene group list API and the query scene list API | ||
| Device Management APIs | Provides device management APIs. The query device list API supports filtering by device SN, device name, online status, scene ID, and device model. The device query API returns the Module SN field, visible in device details, lists, and exported Excel. The device query API provides a domain certificate validation switch field. Provides palm database capacity and device validity queries | ||
| Access & Authentication | OpenAPI supports user authentication mode with fine-grained user-level permission control. Supports gateway authentication transformation, configurable to use token authentication from the customer's environment. Provides the CPM Device Scan QR registration OpenAPI, supporting masking SMS verification code checks in private cloud environments | ||
| Hardware | A3 Module | The A3 module supports standard QR code recognition, recognizing as the code approaches. A3B supports FEC distortion correction, improving palm print image quality on M4 devices. Average palm scan comparison time is less than 800 ms, reaching algorithm metrics of FRR=0.1% and FAR=0.01% at a 50k database scale | |
| New Hardware Platforms | Supports the rv1126b chip platform, outputting application software versions adapted to M3B and M4B devices. Supports the full palm scan flow (palm registration, verification, query, management), with palm database algorithm compatibility between new and old devices | ||
| Card Swipe Module | Supports reading M1 cards | M3 devices only |
Product Overview
PalmAI Standard is a Palm Application Platform service built on world-leading "palm print + palm vein" recognition technology, providing end-to-end capabilities from palm registration, palm scan recognition, and identity verification to user and device management. At the algorithm level, it supports fully on-device recognition; at the application level, it covers a complete business loop across the Admin Console, device side, mobile side, and open APIs.
The platform supports palm databases of tens of thousands of records: when the palm database exceeds 50,000 records, the device side delivers only 50,000 palm features based on a time-first policy. The average palm scan comparison time on the A3 module is less than 800ms, achieving algorithm metrics of FRR=0.1% and FAR=0.01% at a 50k database scale. The platform adapts to M3, M4, M3B, and M4B devices and A3/A3B modules, supports the rv1126b chip platform, and is suitable for business scenarios such as member eKYC, access passage, access control, attendance, meetings, and visitors.
The platform includes server-side, device-side, mobile-side, API, and SDK deliverables: the server side provides the Admin Console and open APIs, supporting integration with customers' own business systems; the device side provides M3/M4 series device software and host companion capabilities; the mobile side provides the Mobile Palm Registration SDK (Android/iOS/Flutter/mini program) and the Palm Scan APP. The mobile Mobile Palm Registration capability is a value-added optional service; the palm scan attendance, meeting, and visitor applications are provided as add-on options.
Feature Description
Note: This table is based on the latest version (v2.5) and cumulatively presents the full feature set of the product across all sides (server side, device side, and mobile side).
| Module | Feature | Description | Remark |
| Palm Registration Applications | Mobile Palm Registration | Provides the Mobile Palm Registration SDK (Android/iOS native, Flutter, and mini program versions), allowing users to complete palm registration on their phones. The Flutter version aligns its features with the Native SDK and supports registration mode. The mini program version supports palm registration within the mini program, providing device discovery and connection (Bluetooth/BLE), result display, and error prompts with retry capability, along with type definitions, integration documentation, and a sample project, and supports integration and operation in WeChat mini programs. Multi-tenant registration and configuration are supported, and different tenants can use independent Mobile Palm Registration processes and parameters. Dual palm pre-registration is supported. The Mobile Palm Registration SDK and the server-side liveness detection algorithm are continuously upgraded, and optimal selection for Mobile Palm Registration is performed by the dedicated server-side selection SDK. | Value-added optional service |
| Provides Android/iOS test APPs for customers to experience the Mobile Palm Registration feature. | This APP cannot be used for formal delivery | ||
| H5 Palm Registration | Supports H5 QR Code Palm Registration: users fill in registration information on a mobile H5 page and generate a registration QR code; after the device scans the code, it directly enters the palm collection step, and the registration progress status can be tracked in real time. Custom H5 palm registration is supported, and a customer-specified URL can be displayed after palm scanning. | Users can develop their own registration interface | |
| Device-Side Palm Registration | Supports direct palm registration on the device. M3/M4 devices support dual palm registration: after entering the UserID, the registered palm status is automatically queried, and a second palm can be added with automatic labeling of primary/secondary palm roles. Registration via external devices is supported, with Windows/Mac experience applications provided. | External devices require user development | |
| Host Palm Registration | Supports dual palm enrollment and management on the host, with the result page displaying the user's dual palm registration status. Supports registration status display and registration result confirmation, with an entry for deleting users. Duplicate registration detection displays the registered user ID and username, making it easy to quickly locate existing registration records. Supports the Device Scan QR registration process, and the device returns the user ID and username when reporting registration results. | ||
| Palm Scan Applications | Palm Scan Recognition | Supports fully on-device recognition. When the palm database exceeds 50,000 records, the device side delivers only 50,000 palm features based on a time-first policy. Supports recognition in scenarios where the palm is scanned from far to near. Supports stable verification in scenarios where a device is bound to a large number of verification rules and synchronizes a large number of user features. | |
| Offline Verification | Supports palm scan verification in offline state, with verification records uploaded after the network is restored. Provides granular network Error Codes to distinguish between network disconnection and unregistered users. | ||
| Blocklist | Supports adding a user's palm to the blocklist; blocklisted palms are denied passage during verification. When a user has registered both palms, adding only one palm to the blocklist still correctly blocks passage. Blocklist API performance and local encryption of cached data are continuously ensured. | ||
| Device Settings | System Settings | Supports viewing About This Device (device MAC address, device version, SN information, associated scenes). Supports setting the daily automatic restart time of the device. Supports clearing the local palm database manually. Supports wireless and wired network configuration, with Wi-Fi passwords up to 32 characters. Supports developer mode log upload, password management, and module activation via QR code scanning. | |
| Multi-language Switching | Supports multi-language switching on M3/M4 devices: after selecting a language in the settings module, device text and voice packs take effect immediately. Supports Simplified Chinese, English, Cantonese, and French, and falls back to English when translated content is missing. | ||
| Mode Switching | Supports switching the device between registration and recognition working states via commands. | ||
| Wiegand Access Control Integration | Supports Wiegand output of the physical card number after palm scanning. M3 supports adaptation to the Wiegand 64-bit protocol and can integrate with access control systems to enable palm scan passage. The physical card number field in user management supports 0-66 bits, compatible with extended Wiegand protocol bit lengths. | Wiegand 64-bit only on M3 devices | |
| Remote Door Opening | Supports the remote door opening feature on M3 devices, integrating the MQTT protocol for remote control. | M3 devices only | |
| 4G Network | M3B devices support 4G cellular network connection. Supports remote operations on module files and remote simulation of authorization expiration via device-level commands, avoiding device and module disassembly. | 4G only on M3B devices | |
| Admin Console | Multi-tenant Management | Supports a multi-tenant architecture: super administrators can create, edit, and delete tenants, allocate tenant quotas (palm database capacity/device capacity), and switch tenant views. Supports creation and assignment of tenant administrators, who can only manage data of their own tenants. Supports data isolation and business/permission isolation between tenants. Supports layered management of tenant-level configurations and platform-level configurations. Supports access links carrying a tenant APPID prefix to automatically switch to the corresponding tenant, supports independent access to different tenants in multiple browser tabs, and is compatible with existing links and single-tenant user access methods. | |
| Data Dashboard | Provides a Dashboard data board: data overview (total devices/total registered users/total palms/palm database capacity); real-time display of today's data (today's palm scans/palm scan users/newly activated users/online devices); user data trend charts (daily newly activated users/palms, daily active users, user status distribution); device data and palm scan data trend charts, supporting data export for up to 180 days. Verification statistics cover all verification records and support filtering by time and export. | ||
| User Management | Supports creating, editing, and deleting users (individually on the page or in batch via Excel), and supports batch deletion of users with secondary confirmation. Registered users can modify their UserID. Supports unified management of dual palms (left palm/right palm) under a single UserID, providing user status (no valid palm/left palm available/right palm available/both palms available) and a primary palm field. Provides a user registration method field (device input registration, Mobile Palm Registration, phone QR Code Palm Registration, Device Scan QR registration, host registration). Supports querying the user access scope by user dimension. Supports batch export of user information. Phone number entry supports fuzzy search of countries in English. Sensitive information such as phone numbers and names can be displayed encrypted. | ||
| User Tags | Supports creating, editing, deleting, and batch importing user tags. Supports organization/department management hierarchy. The user list supports filtering by tags. Supports setting verifiable personnel by tag. Provides duplicate-name tag prompts and creation permission control. | ||
| Device Management | Supports device registration, editing, and deletion (individually on the page or in batch via Excel) and batch export. The device list displays complete information including device SN, device name, device type, module type, device status, module validity period, application version, module version, system version, algorithm version, and associated scenes, and supports fuzzy search, filtering by status, filtering by resource utilization health, and export. Provides a device list statistics module showing the number and status overview of online/offline/abnormal devices. Device time zones are configured by cloud-side synchronization. | ||
| Device Monitoring | Provides a full device monitoring panel, including data overview, health trends and distribution, resource utilization, camera status, risk ranking, OTA upgrade trends, and other views. Data is automatically refreshed every 5 minutes and permission control is supported. Supports M3/M4 module and camera status monitoring and reporting (5-minute cycle), with exception information reported after automatic restart. Issue reporting supports module exception and camera exception scenarios. | ||
| Scene Management | Supports creating, editing, and deleting scenes (individually on the page or in batch via Excel), supports batch association of devices, and allows users to enter a scene ID when creating a scene. Provides scene group management. Supports combined configuration of open scenes and closed scenes, automatically adjusting recognition strategies and security levels according to scene type. Provides 2 scene strategy templates (on-device recognition strategy A/B), supports binding scene strategies, and delivers configurations to devices by scene to take effect. Scene configuration supports Strict Mode/Convenience Mode selection; Strict Mode only allows the primary palm to pass. | ||
| Verification Rules | Supports verification rule management, which can restrict the personnel, number of times, and time periods allowed for palm scanning on different devices, and supports settings by user tag or specified users and by time period. Supports delivering the device-side palm database according to verification rules and synchronizing user information. Provides tenant-level configuration of the default passage behavior when no verification rule is hit (allow passage/deny passage); the default is allow passage, and configuration changes are recorded in operation logs. | ||
| Verification Records | Supports viewing, filtering, and batch export of verification records. Successful and failed palm scan records are displayed separately, and failure reasons can be viewed for failed records. Supports filtering by device-side/mobile-side type. Cloud-side and device-side Error Codes prompts are aligned. After a scene or scene group is deleted, the scene name and scene group in verification records are still displayed properly. Supports disabling asynchronous push of palm scan records. Provides result page time configuration, allowing customization of the display duration of the result page after a successful palm scan. | ||
| Verification Record Push | Supports configuration of verification record push addresses (Webhook), providing add, delete, modify, and query operations for addresses. Supports configuring the push scope, and verification records are pushed to the specified addresses according to the configuration. | ||
| Application Management | The palm scan attendance, meeting, and visitor applications are integrated into the application management module of the Admin Console and listed as add-on options, displaying the deployment, purchase, and activation status of each application, and supporting login-free redirection from the console to the application management system. A three-layer management model is established: system-level purchase and deployment, tenant-level activation and deactivation, and user-level display based on activation status. A unified user-side H5 entry is provided, supporting both generic links and tenant-specific links, with displayed content consistent with the current tenant's application activation status. | Add-on option | |
| Scenario Applications | Provides visitor, meeting, and attendance scenario applications: the visitor application supports issuing visitor passes in on-site and appointment modes, working with the platform to complete palm print verification and passage. The attendance application is integrated with platform accounts, providing an H5 leave request interface, leave management, attendance group tags, abnormal clock-in management, host registration support, and data export capabilities. | Add-on option | |
| Compliance Information Signing | In the Indonesia demo environment, when an administrator logs in to the Admin Console for the first time, the completeness of the company full name, contact name, and contact email is verified, and the Admin Console cannot be accessed until the compliance agreement is signed. The compliance agreement is displayed in both Chinese and English versions, and signing information is stored in the database with traceability. | ||
| Permission Management | Provides role and permission management, with 5 built-in role types, supporting creating administrators and assigning account permissions. All types of administrators can change their own passwords in the Admin Console (8-100 characters in length, containing at least three of uppercase letters, lowercase letters, digits, and special symbols, not containing 4 or more consecutive ascending or descending characters, and the new password must not be the same as the old one). Login sessions support sliding renewal, and the frontend provides a session keep-alive heartbeat to prevent login expiration when submitting long-filled forms. | ||
| Audit Logs | Provides an operation log module that records administrators' system operations (IP address, username, operation time, operation type, operation result). Audit logs are recorded for the API request processing, supporting API call traceability. Covers operations in the IoT device management and scene management modules (upgrade package management, upgrade campaign management, upgrade tasks, device management, device log management, remote commands, etc.). Supports log backup and forwarding to third-party systems. The audit log list supports exporting the current filtered results to Excel. | ||
| Multi-timezone Display | Server-side time is uniformly aligned via NTP. System management provides timezone settings and status display, with daylight saving time identification supported. The web side supports display switching following the local browser/server timezone, and page time displays are uniformly labeled with the current timezone. | ||
| System Settings | Supports display of system version information and viewing of upgrade records. Supports switching between Chinese, Japanese, and English. Supports uploading the Admin Console logo. Fields such as device SN, scene, tenant, and verification rule support fuzzy search, with results ranked by exact/prefix/suffix/partial match levels; fields such as username and user ID support exact match, and grouped drop-down selection of search fields is supported. | ||
| License Management | Platform license files support binding to the Max or Standard edition, with different editions corresponding to different feature scopes. Supports the tenant quantity license dimension, allowing the number of tenants that can be created to be limited by License. Palm database capacity is calculated strictly by the number of palms; feature updates and dual-write do not consume palm capacity License. | ||
| Deployment & O&M | Deployment Adaptation | Provides standalone and TKE cluster deployment solutions with O&M guidance. Supports pure CPU-based service deployment. Supports the upgrade and data migration solution from Standard to Max edition. O&M configurations are consolidated into a single file, reducing multi-environment maintenance costs. | |
| Upgrade Management | Supports OTA upgrades: firmware, modules, applications, and algorithms can be upgraded independently with version dependencies configurable, and designated device upgrades, silent upgrades, and repeated upgrades are supported; upgrade configuration orders are output by package. OTA upgrade tasks adopt a timely push mechanism: after a task is created, the device side is notified by command to pull immediately. Pre-checks are provided when devices join an upgrade task (three dimensions: device not registered, upgrade type mismatch, already in another upgrade task), and one-click removal of invalid devices is supported; batch device addition supports directly entering multiple device SNs. Provides an upgrade ledger that displays upgrade records of all devices at the granularity of upgrade tasks (task creation time, device SN, upgrade type, pre- and post-upgrade versions, upgrade status, last failure reason, etc.), supporting query, filtering, and export, with view permissions associable to super administrator, tenant administrator, and device administrator roles. | ||
| Remote Commands | Supports delivering remote operation commands to devices from the Admin Console, with commands integrating the MQTT protocol. Supports batch delivery and device validity verification. Supports remote delivery of Wi-Fi configurations and viewing command details; the device side supports Wi-Fi configuration cache management (up to 10 entries, supporting add, delete, and sorting), and automatically polls and reconnects to cached Wi-Fi networks after disconnection. The standalone edition supports retrieving device logs via remote commands. In weak network environments, the timeout for device commands and logs is extended to 12 hours. | ||
| Resource Utilization Alerts | Device-side data reporting includes resource usage and resource utilization alert information, supporting CPU, memory, storage, and other resource monitoring. | ||
| Data Backup | Provides a daily automatic data backup tool for the standalone edition, which automatically cleans up the earliest backups when backup space is full, and supports data backup without service interruption. | ||
| Service Self-Check Tool | Supports automatic full-feature verification and API interface testing after system installation and configuration are completed. Supports internationalization, adapting prompts and error messages to multiple languages. The self-check report displays the service version number, with a display format aligned with the device batch self-check report; check items use unified numeric IDs and support one-click copying. | ||
| Device Self-Check Tool | Supports automatic execution of full-feature verification, API interface testing, performance testing, and other test cases on the device side, with a run result report output. Provides a deep diagnosis entry for abnormal results, supporting network configuration checks such as local IP, DNS, and routing. | ||
| Troubleshooting | Supports log collection and analysis on both device side and server side, establishing an end-to-end issue analysis chain. Event details in the troubleshooting tool support display of liveness detection RGB images (optional reporting), facilitating verification issue location and analysis. Provides an end-to-end acceptance automation tool covering full-link automated verification of device registration, feature synchronization, and palm scan verification, supporting batch execution of acceptance cases and output of HTML acceptance reports. Provides a resource estimation tool that can estimate standalone edition resources based on palm database/device scale, automatically expanding the resource list when exceeded, and prompting a switch to the cluster edition when the standalone edition cannot support the scale. Provides verification success/failure count statistics scripts, license expiration monitoring and alerting, dashboard monitoring, and O&M weekly/daily report email push configuration. | ||
| M4 O&M Capabilities | M4 devices support the capability to parse the latest system version number. M3 devices support communication with the system-layer daemon, allowing applications to be upgraded through the daemon. Module firmware upgrades can carry the latest algorithm package for joint upgrade. | ||
| API | User Management APIs | Provides APIs for creating, editing, deleting, and querying users, with returned fields subject to mandatory server-side desensitization. User creation and editing APIs support the tag field. Provides APIs for creating, editing, and deleting user tags. Provides a batch synchronization interface for user palm registration status, supporting batch query of user palm registration status by user ID list. Provides user status and palm status APIs, supporting fine-grained dual palm status management. The user information query interface supports returning all Admin Console user information, including the registration method field. | |
| Palm Print Management APIs | Provides a palm print unbinding API and an API for querying user palm registration status. Registration/recognition interfaces support returning the palm direction field. | The palm direction field is for the open-source community edition | |
| Verification Record APIs | Provides a verification record retrieval API and a verification record push API, and provides an API for creating verification records. The verification record list query interface supports the scene group name return field and a parameter for sorting by verification time. | ||
| Verification Rule APIs | Provides APIs for creating, editing, and deleting verification rules, and an interface for querying the verification rule list. | ||
| Scene Management APIs | Provides scene management APIs, an interface for querying the scene group list, and an interface for querying the scene list. | ||
| Device Management APIs | Provides device management APIs. The device list query interface supports filtering by device SN, device name, online status, scene ID, and device model. The device query API returns the Module SN field, viewable in device details, lists, and exported Excel files. The device query API provides a domain certificate verification switch field. Provides palm database capacity and device validity period queries. | ||
| Access & Authentication | OpenAPI supports the user authentication mode, enabling fine-grained user-level permission control. Supports gateway authentication transformation, configurable to use token authentication from the customer environment. Provides a CPM Device Scan QR registration OpenAPI interface, supporting shielding SMS verification code checks in privatized environments. | ||
| Hardware | A3 Module | The A3 module supports standard QR code recognition, recognizing codes as they approach. A3B supports FEC distortion correction, improving palm print collection image quality on M4 devices. The average palm scan comparison time is less than 800ms, achieving algorithm metrics of FRR=0.1% and FAR=0.01% at a 50k database scale. | |
| New Hardware Platform | Supports the rv1126b chip platform, delivering application software versions adapted to M3B and M4B devices. Supports the full palm scan process (registration, verification, query, management), with palm database algorithm interoperability between new and legacy devices. | ||
| Card Reading Module | Supports reading M1 cards. | M3 devices only |
Conversion Records (Max → Standard)
| No. | Section | Operation Type | Before | After | Rule |
|---|---|---|---|---|---|
| 1 | Title | Modify | PalmAI Max | PalmAI Standard | A |
| 2 | Product Overview | Modify | Supports three recognition modes at the algorithm level: fully on-device / fully cloud / hybrid | Supports fully on-device recognition at the algorithm level | D/I |
| 3 | Product Overview | Delete | "Hybrid recognition time controlled within 2 seconds" | (Deleted; "palm databases of tens of thousands of records" retained with the original wording per the owner's decision) | I |
| 4 | Mobile Palm Registration | Modify | Flutter supports registration, verification (1:1), and recognition (1:N) modes; the mini program supports palm registration and palm scan recognition | Flutter supports registration mode; the mini program supports palm registration | F |
| 5 | Palm Scan Recognition | Modify | Three modes: fully on-device / fully cloud / hybrid; hybrid retrieval delivers features according to verification rules; hybrid recognition within 2 seconds | Fully on-device recognition; removed hybrid retrieval delivery and hybrid recognition time descriptions | D/G/I |
| 6 | Similar Palm Handling | Delete | The entire row on secondary verification and registration labeling under Max hybrid/cloud strategies | (Entire row deleted; for Standard, similar palm registration is always rejected and recognition is directly refused; whether a separate feature item is needed in the feature description is to be confirmed) | E |
| 7 | Palm Scan Applications - Additional Verification | Delete | The entire row on the Max-exclusive post-scan additional verification capability (three verification methods) | (Deleted) | C |
| 8 | Palm Scan Applications - Mobile Verification | Delete | The entire row on phone-side 1:1 verification and H5 1:1/1:N comparison | (Deleted) | F |
| 9 | Offline Verification | Modify | Included fully cloud mode disconnection prompts and hybrid degradation descriptions | Only offline verification and Error Codes descriptions retained | D/I |
| 10 | Scene Management | Modify | Provides 4 scene strategy templates | Provides 2 scene strategy templates (on-device recognition strategy A/B) | D |
| 11 | Deployment Adaptation | Delete | Supports TCS base delivery; supports O&M monitoring and log analysis for the Azure cluster edition | (Deleted) | H |
| 12 | Multi-tenant Management | Retain | (Original text) | A feature shared by Standard and Max, retained unchanged | J |
Converted by: Agent A (automatic) Conversion date: 2026-09-28