An asset management platform suitable for movable property mortgages

Abstract

This invention provides an asset management platform suitable for movable property mortgages, belonging to the field of credit management technology. This asset management platform consists of four modules: an equipment management module, a system management module, a customer management module, and an asset management module. The equipment management module is further divided into three sub-modules: equipment management, monitoring and maintenance, and alarm management. Each sub-module performs its corresponding management function. The system management module is divided into four sub-modules: user management, role management, access control, and log management. The asset management module is divided into two sub-modules: asset transfer management and equipment binding. This platform can monitor, collect, and analyze location data in real time, thereby enabling more accurate and timely control of business risks.

Description

Technical Field

[0001] This invention belongs to the field of credit management technology, and specifically relates to an asset management platform suitable for movable property mortgage. Background Technology

[0002] A movable property mortgage is a credit transaction using movable property as collateral. The debtor legally transfers ownership of the movable property to the creditor, but the creditor does not possess the property. Once the debt secured by the movable property is repaid, the transfer of ownership immediately becomes invalid. Therefore, although the movable property is conditionally transferred when the debt is incurred, ownership is immediately regained after all debts are settled.

[0003] Currently, due to the lack of effective regulatory methods for movable property mortgages, especially in the area of ​​equipment mortgages, there may be situations such as double mortgaging of equipment, unauthorized movement of equipment, and misattribution of equipment, which may lead to significant business risks. Summary of the Invention

[0004] In view of this, the purpose of this invention is to overcome the shortcomings of the prior art and propose an asset management platform suitable for movable property mortgage.

[0005] The objective of this invention can be achieved through the following technical solution: an asset management platform suitable for movable property mortgage, characterized in that it comprises:

[0006] The device management module displays a list of all added terminal devices. It supports searching by device number, device name, and whether the device is enabled or disabled. Users can add, modify, enable, disable, bind, and unbind terminal devices to assets on the page.

[0007] The system management module displays a list of all user information, supporting searches by employee name and mobile phone number. Users can add, modify, enable, disable, and change passwords for user information on the page. Administrators can reset passwords and add new authorizations.

[0008] The customer management module displays a list of all added customer information. It supports searching by customer ID, customer name, and contact person's mobile phone number. Customer information can be added, modified, enabled, or disabled on the page.

[0009] The asset management module displays a list of all added asset information. Its data permissions are limited to the current business manager. It supports querying by asset number, asset name, customer name, associated device number, whether enabled or disabled, and business manager. Users can add, modify, enable, disable, bind, and unbind asset information to terminal devices, and set the radius of electronic fences on the page.

[0010] Preferably, the device management module does not support modification after device information is entered, and the device status is automatically set by the system based on whether the terminal has successfully connected to the cloud server. The device is only allowed to be enabled and start collecting device operation logs after it has successfully connected to the cloud. The device can only be bound to the asset after it is enabled. If the device is scrapped or lost, it must be unbound from the asset before it can be disabled.

[0011] Preferably, the binding of the device to the asset is restricted to one terminal device being bound to only one asset. After the terminal positioning device is bound to and unbound from the asset, the device number information will be recorded in the corresponding device number field of the asset record. Only when the asset and the device are bound will the terminal device trigger the corresponding alarm based on its own working status, power level, or location information. The device can be set with the following parameters: removal alarm enabled / disabled, vibration alarm enabled / disabled, low power alarm enabled / disabled, working mode, and reporting interval.

[0012] Preferably, the working mode and time interval are as follows:

[0013] Timed positioning mode, with a time interval of 30 to 3600 seconds. Text description: Timed reporting of positioning data, ranging from 30 to 3600 seconds.

[0014] Intelligent positioning mode, with an interval of 10 to 180 seconds, is the default mode. The text description is: when stationary, location data will not be reported, with a range of 10 to 180 seconds and a default of 30 seconds.

[0015] Super power saving mode, time interval 1-24 hours, text description: wake up the device at time intervals, report location data and then the device will turn off. The range is 1-24 hours. In this mode, it is not possible to locate immediately.

[0016] Preferably, the device management module further includes a monitoring and maintenance submodule and an alarm management submodule. The monitoring and maintenance submodule integrates GPS positioning with Gaode Map. Clicking on the device number in the asset management module opens a link to display the device's location on the map. Clicking the location icon opens a layer displaying device information and asset information. The monitoring and maintenance submodule is also used to display device count statistics and device locations. Device count statistics include: number of created devices, number of online devices, and regional distribution. The alarm management submodule only triggers corresponding alarms based on the terminal device's working status, power consumption, or location information after the asset and device are bound.

[0017] Preferably, the system management module generates a random password after adding a user by default. The customer can change the password after logging in. The password storage requirement is an MD5 hash with the mobile phone number as the salt value. The system management does not allow modification of the mobile phone number or user number. The administrator's password reset operation is performed by automatically resetting the random password through the system and sending it to the user via SMS. The administrator can enable or disable users. Once a user is disabled, they cannot log in to the system. Before disabling a user, the system will determine whether the user is the business manager to whom the asset belongs. If there is a situation where the ownership has not been transferred, the disabling will fail. Please perform the ownership transfer operation first.

[0018] Preferably, when a new user is added, the system management module can view the list of roles to which the current user belongs, and can perform operations to add or delete associated roles. The relationship between users and roles is many-to-many, and the platform does not provide direct authorization operations for users and permissions.

[0019] Preferably, the role list is used to display a list of all role information, supports querying by role name, and allows adding, modifying, enabling, and disabling role information on the page. Administrators can perform role addition authorization operations, which can also include adding and deleting associated permissions. Roles and permissions have a many-to-many relationship.

[0020] Preferably, the system management module further includes a log management submodule, which displays a list of all module operation log information, excluding terminal device-related operation and alarm logs. It supports querying by log module, log creation start date, and log creation end date. The system management module only records logs for critical operations, including all modification behaviors.

[0021] Preferably, when the asset management module adds an asset, the system automatically records the current user account in the business manager field. Afterwards, only the business manager and the administrator have the authority to perform any operations on this customer information; however, modification of the asset number, business manager, and associated device number is not allowed in the asset information modification window. The asset management module also allows the current business manager or administrator to open a specific window by clicking the "Asset Transfer" button, granting the current user the authority to transfer assets to other business managers.

[0022] Compared with existing technologies, this invention has the following advantages: it combines terminal device hardware (GPS positioning device) and software (management terminal device, abnormal situation alarm, etc.). The terminal device is installed by business personnel on the assets that have been mortgaged to Party A as a mortgage identification identifier, and is monitored in real time through the platform. The collected and location data is analyzed, thereby enabling more accurate and timely control of business risks, while effectively saving labor costs. Attached Figure Description

[0023] Figure 1 This is a schematic diagram illustrating the structural principle of the asset management platform in this embodiment.

[0024] Figure 2 This is a deployment architecture diagram of the asset management platform in the embodiment. Detailed Implementation

[0025] Embodiments of the present invention are described in detail below. Examples of these embodiments are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain the present invention, and should not be construed as limiting the present invention.

[0026] like Figure 1-2 As shown, this invention provides an asset management platform suitable for movable property mortgages. Its deployment architecture includes external and internal deployments. The external deployment includes customer terminals and user management terminals, while the internal deployment includes a device terminal service gateway, a business system front-end, and an asset management platform business system. The customer terminal has wireless communication and information collection functions, installed on the corresponding device for binding and monitoring. The user management terminal includes smart mobile devices such as smartphones, computers, and smart tablets, carried by the business manager, who can manage customers and assets through the user management terminal. The asset management platform of this invention manages and monitors business operations through the asset management platform business system, which consists of four modules: a device management module, a system management module, a customer management module, and an asset management module. The device management module is divided into three sub-modules: device management, monitoring and maintenance, and alarm management, each performing corresponding management functions. The system management module is divided into four sub-modules: user management, role management, permission management, and log management. The asset management module is divided into two sub-modules: asset transfer management and device binding.

[0027] Specifically, the device management page displays a paginated list of all added terminal devices, supporting searches by device number, device name, and whether it is enabled or disabled. Users can add, modify, enable, disable, bind, and unbind terminal devices to assets on the page. Device information (as shown in Table 1) cannot be modified once entered. Device status is automatically set by the system based on whether the terminal has successfully connected to the cloud server. Only after a device has successfully connected can it be enabled, and only then will the corresponding device operation logs be collected. The corresponding management tables are as follows:

[0028] 1. device_info (device information)

[0029]

[0030]

[0031] The device can only be bound to an asset after it is enabled. If the device is damaged or lost, it must be unbound from the asset before it can be disabled. It should be noted that one terminal device can only be bound to one asset. After the terminal positioning device is bound to and unbound from the asset, the device number information will be recorded in the corresponding device number field of the asset record. Only when the asset and device are bound will the terminal device trigger corresponding alarms based on its working status, battery level, or location information.

[0032] The device settings include: removal alarm enabled / disabled (described as: when enabled, a removal alarm will be received if the device is removed), vibration alarm enabled / disabled (described as: when enabled, a vibration alarm will be received if the device detects external vibration), low battery alarm enabled / disabled (described as: when the battery level is below 20%, a low battery reminder message will be received (once a day)), operating mode, and reporting interval; specifically, the operating mode and reporting interval include:

[0033] 1. Timed positioning mode, with a time interval of 30 to 3600 seconds. Text description: Timed reporting of positioning data, ranging from 30 to 3600 seconds.

[0034] 2. Intelligent positioning mode, with an interval of 10 to 180 seconds. This is the default mode. Description: No positioning data is reported when stationary. The interval is 10 to 180 seconds, with a default of 30 seconds.

[0035] 3. Super power saving mode, time interval 1-24 hours. Description: The device will be woken up at time intervals and will be turned off after reporting the location data. The range is 1-24 hours. Location cannot be located immediately in this mode.

[0036] The device management details page displays the device's basic information, current configuration, current battery level, charging status, and the device's location (integrated with Amap) and last location time. An "Immediate Location" button is also added to the details page; clicking it will send the device's latest location information in approximately one minute (Note: This function is unavailable in Super Power Saving Mode). The corresponding management tables are as follows:

[0037] 2. device_last_location (device's most recent location information)

[0038]

[0039]

[0040] The monitoring and maintenance sub-module integrates GPS positioning with Amap (Gaode Maps). Clicking on the device number in the asset management module opens a link that displays the device's location on the map. Clicking the location icon opens a layer displaying device and asset information. It also displays device statistics and locations, including the number of created devices, the number of online devices, and their regional distribution (displayed on Amap). The log service module supports paginated queries of cloud-based device operation logs, which can be searched by device number, asset number, reporting start date, and reporting end date, with a maximum time span of 6 months. The corresponding management tables are as follows:

[0041] 3. device_run_log (Device operation log)

[0042] Field Type Null Key Default Extra id bigint(20) NO PRI Primary key (auto-increment) report_time datetime NO Reporting time message_id varchar(56) NO Message Number message_content json NO Message content device_code varchar(90) NO MUL Equipment Number create_time datetime NO CURRENT_TIMESTAMP Creation time modify_time datetime NO CURRENT_TIMESTAMP Modified time

[0043] The alarm management module will only trigger corresponding alarms based on the terminal device's own working status, power consumption, or location information after the asset and device are bound together, as detailed below:

[0044] When the current GPS location of the terminal device exceeds the activity radius (in meters) of the electronic fence area centered on the location coordinates when the asset is bound, a location anomaly alarm will be triggered.

[0045] When the built-in battery is low (<=20%, an alarm will be triggered once a day), a low battery alarm will be triggered, and the alarm information page will include the percentage of the built-in battery power.

[0046] Removal alarm (light sensor alarm): This alarm will be triggered when the terminal device is removed or detached from the asset. Business managers should unbind the terminal device from the asset and disable it before regular replacement of the terminal device or normal removal upon mortgage expiration to avoid false alarms.

[0047] Vibration alarm: This alarm is triggered when the terminal device's sensor detects external vibration. If possible, please activate this alarm after device installation to assist in determining if the device has been removed (light-sensor alarm). Business managers should unbind this terminal device from the asset before disabling it, such as during regular terminal device replacements or normal removal upon mortgage expiration, to avoid false alarms.

[0048] Disconnection alarm: This alarm is triggered when a terminal device loses connection to the server due to malfunctions such as damage, power outage, insufficient bandwidth, or weak signal. After the terminal disconnects, the system will wait for the device to automatically attempt to reconnect. If a connection to the server is not established within 5 minutes, this alarm will be triggered. The corresponding management table is as follows:

[0049] 4. customer_info (Customer Information)

[0050]

[0051]

[0052] Alarm configuration: Configure the recipient's name and mobile phone number corresponding to the alarm type. By default, alarms will be uniformly notified to the business manager corresponding to the bound asset. Please ensure that the mobile phone number is real and valid. The purpose here is to prevent alarm reception from being missed. A copy of the alarm will be uniformly sent to the configured personnel according to the alarm type.

[0053] 5. alarm_configuration

[0054]

[0055]

[0056] This function requires pre-payment and uses Alibaba Cloud's SMS service for pay-as-you-go billing. A pre-set SMS template is also required. The template should include the customer name, contact information, asset ID, asset name, and device ID for easy confirmation by the business manager. For example: "[Device ID] Behavior abnormal! From [Customer Name] [Asset Name] ([Asset ID]), please confirm immediately! Contact Information: [Contact Information]."

[0057] The system management module displays a list of all user information, supporting searches by employee name and mobile phone number. Users can add, modify, enable, disable, and change passwords for user information. Administrators can reset passwords and add new authorizations. The corresponding management tables are as follows:

[0058] 6. system_user (system user)

[0059] Field Type Null Key Default Extra id bigint(20)unsigned NO PRI Primary key (auto-increment) mobile phone varchar(11) NO UNI Contact mobile phone password varchar(32) NO password name varchar(90) NO Name job varchar(90) NO Position department varchar(90) NO department enabled_status bit(1) NO b'1' Enabled status (Yes / No) admin bit(1) NO b'0' Administrator (Yes / No) create_time datetime NO CURRENT_TIMESTAMP Creation time modify_time datetime NO CURRENT_TIMESTAMP Modified time create_operator_id bigint(20)unsigned NO Creator modify_operator_id bigint(20)unsigned NO Modified by

[0060] This module does not allow modification of the mobile phone number (account) or user ID. If a password is forgotten, only the administrator can reset it. The system will automatically reset a random password and send it to the user via SMS (whether an SMS is sent is determined by system configuration; the password reset page will display the plaintext password after the administrator resets it for easy copying; the plaintext will not be displayed after the window is closed). By default, the system generates a random password after adding a user. Customers can change their passwords after logging in. Passwords must be at least 8 characters long and include uppercase and lowercase letters, numbers, and special characters. Passwords are stored as MD5 hashes with the mobile phone number (account) as the salt value. Only the administrator can enable or disable a user; administrators are not allowed to disable their own accounts. Disabling a user will prevent login. Before disabling a user, the system will determine if the user is the business manager to whom the asset belongs. If the account has not been transferred, disabling will fail; please complete the transfer process first.

[0061] The user authorization page displays a list of roles to which the current user belongs. Users can add or delete associated roles. There is a many-to-many relationship between users and roles. The platform does not provide direct authorization operations between users and permissions.

[0062] The role management page displays a paginated list of all role information, supports searching by role name, and allows users to add, modify, enable, and disable role information. Administrators can also perform new authorization operations. The system automatically creates administrator privileges, and the administrator role includes all system permissions. The corresponding management table is as follows:

[0063] 7. system_user_role (User role association table)

[0064] Field Type Null Key Default Extra id bigint(20)unsigned NO PRI Primary key (auto-increment) system_user_id bigint(20)unsigned NO MUL System User ID system_role_id bigint(20)unsigned NO MUL System Role Number create_time datetime NO CURRENT_TIMESTAMP Creation time create_operator_id bigint(20)unsigned NO Creator

[0065] The new authorization page for a role displays a list of permissions currently held by the role, allowing users to add or delete associated permissions. There is a many-to-many relationship between roles and permissions.

[0066] The permission management page displays a paginated list of all permissions available to the system. All permissions are initialized upon system deployment; the page does not offer add, modify, or manage options. The corresponding management table is as follows:

[0067] 8. system_role_permission (role permission association table)

[0068] Field Type Null Key Default Extra id bigint(20)unsigned NO PRI Primary key (auto-increment) system_role_id bigint(20)unsigned NO MUL System Role Number system_permission_id bigint(20)unsigned NO MUL System permission number create_time datetime NO CURRENT_TIMESTAMP Creation time create_operator_id bigint(20)unsigned NO Creator

[0069] The log management page displays a paginated list of all module operation logs, excluding terminal device-related operation and alarm logs. It supports querying by log module, log creation start date, and log creation end date, with a maximum time span of 3 months. Logs are automatically recorded by the system and no other operations besides querying are provided. The system only logs critical operations, including all modification actions (modification, binding, unbinding, enabling, disabling, asset transfer), and the corresponding management tables are as follows:

[0070] 9. system_operation_log (System operation log)

[0071]

[0072]

[0073] Example of a log entry: When binding or unbinding devices on the asset management page, the following will also be recorded in the operation log: Log content: "Asset ID, Asset Name, Device ID, Device Name, Binding or Unbinding", Log creation time (operation time), Log creator (operator).

[0074] The customer management module displays a list of all added customer information and supports searching by customer ID, customer name, and contact person's mobile phone number. Customer information can be added, modified, enabled, or disabled on the page. Disabling a customer is only allowed after all associated assets have been disabled in the asset management section.

[0075] Modification of customer IDs is not allowed; only activated customers can be designated as custodians in asset management. The corresponding management table is as follows:

[0076] 10. customer_info (Customer Information)

[0077]

[0078]

[0079] The asset management module displays a list of all added asset information. Data access is limited to the current business manager. It supports searching by asset number, asset name, customer name, associated device number, whether enabled / disabled, and business manager. Users can add, modify, enable, disable, bind / unbind assets to terminal devices, and set the geofence radius (range 100-10000 meters). The corresponding management tables are as follows.

[0080] 11. asset_info (Asset Information)

[0081]

[0082]

[0083] When adding (new) assets, the system will automatically record the current user account in the business manager field. After that, only the business manager and the administrator have the right to perform any operations on the customer information.

[0084] Modification of asset number, business manager, and associated device number is not allowed in the asset information modification window. The system allows the current business manager or administrator to open a specific window by clicking the "Asset Transfer" button, granting the current user the authority to transfer assets to other business managers (users). Clicking the "Device Binding" button opens a specific window where the system supports binding and unbinding assets and devices. An asset can only be bound to one terminal device, and a terminal device can only be bound to one asset. Once bound, an asset cannot be bound to other terminal devices until it is unbound from the original terminal device.

[0085] The default electronic fence for each asset system is an activity radius of 100 meters centered on the asset's location coordinates. Users can adjust the fence radius (in meters) for each asset on the platform according to the actual situation. Once the terminal device's location coordinates exceed this area, a location anomaly alarm will be triggered.

[0086] On the asset management page, each asset that has been bound to a device can be located immediately to obtain the device's current location. This location (latitude and longitude) will be used as the center point for judging abnormal geofence locations.

[0087] The asset management platform for movable property mortgage of this invention analyzes data collected and located in real time through monitoring, thereby enabling more accurate and timely control of business risks. It also provides an API interface for integration by third-party software, thereby improving the system's practicality and applicability.

[0088] The specific embodiments described herein are merely illustrative of the spirit of the invention. Those skilled in the art to which this invention pertains may make various modifications or additions to the described specific embodiments or use similar methods to replace them, without departing from the spirit of the invention or exceeding the scope defined by the appended claims.

Claims

1. An asset management platform suitable for movable property mortgage, characterized in that, include: The device management module displays a list of all added terminal positioning devices. It supports searching by device number, device name, and whether the device is enabled. Users can add, modify, enable, disable, bind, and unbind terminal positioning devices to assets on the page. The device management module does not support modification of device information after it has been entered. Device status is automatically set by the system based on whether the terminal has successfully connected to the cloud server. Devices are only allowed to be enabled and begin collecting device operation logs after successfully connecting to the cloud. Devices can only be bound to assets after being enabled. If a device is scrapped or lost, it must be unbound from the asset before it can be disabled. The system management module displays a list of all user information and supports searching by employee name and mobile phone number. Users can add, modify, enable, disable, and change passwords for user information on the page. Administrators can reset passwords and add new authorizations. The customer management module displays a list of all added customer information. It supports searching by customer ID, customer name, and contact person's mobile phone number, and allows users to add, modify, enable, and disable customer information on the page. The asset management module displays a list of all added asset information. Data access is limited to the current business manager. It supports searching by asset number, asset name, customer name, associated device number, whether enabled, and business manager. Users can add, modify, enable, disable, bind / unbind, and set geofence radii for asset information on the page. When an asset is added, the system automatically records the current user account in the business manager field. Afterward, only the business manager and administrators have the authority to perform any operations on that customer information. Modification of the asset number, business manager, and associated device number is not allowed in the asset information modification window. The asset management module also allows the current business manager or administrator to transfer assets to other business managers. The system management module generates a random password after adding a user by default. Customers can change their passwords after logging in. Password storage requires an MD5 hash with the phone number as the salt value. The system management module does not allow modification of phone numbers or user IDs. The administrator resets the password automatically by sending a random password to the user via SMS. The administrator can enable or disable users. Disabled users cannot log in. Before disabling a user, the system checks if the user is the business manager of the asset. If the transfer of ownership is not completed, disabling will fail; the transfer must be performed first. When adding a user, the system management module can view the current user's role list and add or delete associated roles. The relationship between users and roles is many-to-many; the platform does not provide direct authorization of users and permissions. The system management module also includes a log management submodule, which displays a list of all module operation log information, excluding operation and alarm logs related to terminal positioning devices. It supports querying by log module, log creation start date, and log creation end date. The system management module only records logs for critical operations, including all modification behaviors.

2. The asset management platform for movable property mortgage according to claim 1, characterized in that, The binding of the device to the asset is restricted to one terminal positioning device being bound to only one asset. After the terminal positioning device is bound to or unbound from the asset, the device number information will be recorded in the corresponding device number field of the asset record. Only when the asset and the device are bound will the terminal positioning device trigger the corresponding alarm based on its own working status, power level, or location information. The device is set with the following parameters: removal alarm enabled / disabled, vibration alarm enabled / disabled, low power alarm enabled / disabled, working mode, and reporting interval.

3. The asset management platform for movable property mortgage according to claim 2, characterized in that, The specific working mode and reporting time interval are as follows: Timed positioning mode, with a time interval of 30 to 3600 seconds. Text description: Timed reporting of positioning data, ranging from 30 to 3600 seconds. Intelligent positioning mode, with an interval of 10 to 180 seconds, is the default mode. The text description is: when stationary, location data will not be reported, with a range of 10 to 180 seconds and a default of 30 seconds. Super power saving mode, time interval 1-24 hours, text description: wake up the device at time intervals, report location data and then the device will turn off. The range is 1-24 hours. In this mode, it is not possible to locate immediately.

4. An asset management platform suitable for movable property mortgage according to any one of claims 1-3, characterized in that, The device management module also includes a monitoring and maintenance submodule and an alarm management submodule. The monitoring and maintenance submodule integrates GPS positioning with Gaode Map. Clicking on the device number in the asset management module opens a link that displays the device's location on the map. Clicking the location icon opens a layer displaying device and asset information. The monitoring and maintenance submodule is also used to display device statistics and device locations. Device statistics include: number of created devices, number of online devices, and regional distribution. The alarm management submodule only triggers corresponding alarms based on the terminal positioning device's working status, battery level, or location information after the asset and device are bound together.

5. An asset management platform suitable for movable property mortgage according to any one of claims 1-3, characterized in that, The role list is used to display all role information. It supports searching by role name and allows users to add, modify, enable, and disable role information on the page. Administrators can perform new role authorization operations, which can also add and delete associated permissions. Roles and permissions have a many-to-many relationship.

Images