Internet of Things operation information management system

Abstract

The invention relates to the technical field of Internet of Things, in particular to an Internet of Things operation information management system which establishes communication connection with a financial system and an Internet of Things equipment management system. The system is characterized in that a data acquisition module acquires equipment operation data of the equipment of the Internet of Things, and sends the equipment operation data to a charging event screening module; the charging event screening module screens out charging event data from the equipment operation data according to a screening parameter and a charging rule corresponding to a pre-configured charging event, and sends the charging event data to the account management module; and the account management module generates a service fee list based on the account information, the charging rule and the charging event data, and calls a deduction and payment service interface of the financial system based on the service fee list to complete fee settlement of the service fee list. According to the invention, the problems of high code coupling, low development efficiency and small service intensity after an existing Internet of Things equipment management platform realizes a financial service function can be solved.

Description

Technical Field

[0001] The present application relates to the technical field of Internet of Things, and in particular to an Internet of Things operation information management system. Background Art

[0002] In the prior art, the IoT device management platform only has the ability to manage IoT devices but not to provide financial services, while financial institutions only have the ability to provide financial services but not to manage IoT devices.

[0003] In order to enable the IoT device management platform to have financial service capabilities, some manufacturers develop financial service interfaces in the business code of the IoT device management platform according to the bank's interface specifications and rules, so as to call the payment interface of the financial institution to realize the payment function. However, this method leads to a lot of logical modifications to the business code of the original IoT device management platform, and the business code of the IoT device management platform is highly coupled with the financial service interface and is not easy to maintain. In addition, each IoT device management platform project needs to develop an additional financial service interface, which is a large workload and low overall development efficiency. Some IoT device management platforms use third-party payment platforms, but this method reduces the service strength of the IoT device management platform, and the service is not flexible enough. Summary of the invention

[0004] In view of this, an embodiment of the present application provides an Internet of Things operation information management system, which can effectively solve the problems of high code coupling, low development efficiency, and weak service strength after the existing Internet of Things device management platform realizes the financial service function.

[0005] In a first aspect, an embodiment of the present application provides an Internet of Things operation information management system, wherein the Internet of Things operation information management system establishes a communication connection with a financial system and an Internet of Things device management system; the Internet of Things operation information management system comprises: a data collection module, a billing event screening module and an account management module;

[0006] The data collection module collects device operation data of the IoT device and sends the device operation data to the billing event screening module;

[0007] The billing event screening module obtains screening parameters and billing rules corresponding to pre-configured billing events, screens billing event data from the device operation data based on the screening parameters and billing rules, and sends the billing event data to the account management module;

[0008] The account management module obtains account information and the billing rules, generates a service fee list based on the account information, the billing rules and the billing event data, and calls the withholding service interface of the financial system based on the service fee list to complete the fee settlement of the service fee list.

[0009] In some embodiments, the data collection module collects device operation data of the IoT device, including:

[0010] The data collection module collects the device operation data from the user's Internet of Things device; or, the data collection module obtains the device operation data of the user's Internet of Things device from the Internet of Things device management system.

[0011] In some embodiments, the account management module specifically includes a billing unit, a bill management unit, and a withholding payment interface;

[0012] The account management module obtains the account information and the charging rules, generates a service fee list based on the account information, the charging rules and the charging event data, and calls the withholding service interface of the financial system based on the service fee list to complete the fee settlement of the service fee list, including:

[0013] The billing unit generates a service fee list based on the account information, the billing rules and the billing event data, and sends the service fee list to the bill management unit;

[0014] The bill management unit obtains account information from the service fee list, stores the service fee list under the account information, and calls the withholding payment interface based on the service fee list;

[0015] The withholding payment interface calls the withholding service interface of the financial system based on the service fee list, and receives fee settlement information returned by the withholding service interface.

[0016] In some embodiments, the account management module further includes: an account points management unit;

[0017] Before the step of generating a service fee list based on the account information, the billing rules and the billing event data by the billing unit, the billing unit is further configured to send the account information to the account points management unit;

[0018] The account points management unit obtains the account level corresponding to the account information, determines the discount strength corresponding to the account information based on the account level, and sends the discount strength to the billing unit;

[0019] The billing unit generates a service fee list based on the account information, the billing rules and the billing event data, specifically including:

[0020] The billing unit generates a service fee list based on the account information, the discount level, the billing rules and the billing event data.

[0021] In some embodiments, the account management module further includes: a risk control management unit;

[0022] The risk control management unit identifies risks based on the account information, the device operation data, and at least one of the device life management information and device failure management information obtained from the IoT device management system, and outputs risk warning information;

[0023] And / or, the risk control management unit collects statistics on all service fee lists to be paid by the user in the bill management unit to identify the financial risk of the user and output risk warning information.

[0024] In some embodiments, the IoT operation information management system further includes: a device user management module and a basic data management module;

[0025] The device user management module allocates and binds a target device to the user according to the acquired user information and the device information of the IoT device acquired from the IoT device management system to obtain device binding information;

[0026] The basic information management module is used to collect and manage user information and user bank information, and generate the account information according to the user's device binding information, user information, and user bank account information obtained from the device user management module.

[0027] In some embodiments, the IoT operation information management system further includes: a financial system;

[0028] The financial system is used to provide a withholding service interface for automatically deducting the fees in the service fee list from the user's bank account and paying the fees to the corresponding payee in the service fee list on the user's behalf.

[0029] In some embodiments, the bill management unit is further used to update the payment completion status in the service fee list according to the fee settlement information, and output the service fee list corresponding to the account information that meets the query conditions according to the list query command.

[0030] In some embodiments, the bill management unit obtains account information from the service fee list, stores the service fee list under the account information, and calls the withholding payment interface based on the service fee list, including:

[0031] The bill management unit periodically calls the withholding payment interface based on the unpaid service fee list according to the periodic payment authorization information signed by the user in the account information.

[0032] In some embodiments, the IoT operation information management system further includes: an IoT device management system;

[0033] The IoT device management system is used to collect the device operation data of the user's IoT devices;

[0034] And / or, the IoT device management system is used to monitor the life attributes and fault attributes of the user's IoT devices, and obtain device life management information and device fault management information based on the life attributes and fault attribute analysis.

[0035] The embodiments of the present application have the following beneficial effects:

[0036] This application constructs an IoT operation information management system that can establish communication connections with financial systems and IoT device management systems. The IoT operation information management system can be installed in a plug-in manner on the financial system or IoT device management system, or it can be run independently as a platform, which not only enables the IoT operation information management system to have financial payment functions, but also enables the financial system to have the ability to obtain data from IoT devices. In addition, there is no coupling between the codes of each system, which reduces the workload of code development and effectively solves the problems of high code coupling, low development efficiency, and low service intensity after the existing IoT device management platform realizes the financial service function. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0038] Figure 1 A first structural block diagram of the Internet of Things operation information management system according to an embodiment of the present application is shown;

[0039] Figure 2 A second structural block diagram of the Internet of Things operation information management system according to an embodiment of the present application is shown;

[0040] Figure 3 A timing diagram of the Internet of Things operation information management system according to an embodiment of the present application is shown;

[0041] Figure 4A third structural block diagram of the Internet of Things operation information management system according to an embodiment of the present application is shown;

[0042] Figure 5 A fourth structural block diagram of the Internet of Things operation information management system according to an embodiment of the present application is shown.

[0043] Description of main component symbols:

[0044] 100-IoT operation information management system; 110-data collection module; 120-billing event screening module; 130-account management module; 131-billing unit; 132-bill management unit; 133-withholding payment interface; 134-account points management unit; 135-risk control management unit; 140-device user management module; 150-basic information management module; 160-customer service module; 200-IoT device management system; 300-financial system; 400-IoT devices. DETAILED DESCRIPTION

[0045] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments.

[0046] The components of the embodiments of the present application generally described and shown in the drawings herein may be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0047] Hereinafter, the terms "including", "having" and their cognates that can be used in various embodiments of the present application are intended only to indicate specific features, numbers, steps, operations, elements, components or a combination of the foregoing items, and should not be understood as first excluding the existence of one or more other features, numbers, steps, operations, elements, components or a combination of the foregoing items or increasing the possibility of one or more features, numbers, steps, operations, elements, components or a combination of the foregoing items. In addition, the terms "first", "second", "third" and the like are only used to distinguish descriptions and cannot be understood as indicating or implying relative importance.

[0048] Unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meanings as those generally understood by those skilled in the art to which the various embodiments of the present application belong. The terms (such as those defined in generally used dictionaries) will be interpreted as having the same meanings as the contextual meanings in the relevant technical field and will not be interpreted as having idealized meanings or overly formal meanings unless clearly defined in the various embodiments of the present application.

[0049] In conjunction with the accompanying drawings, some embodiments of the present application are described in detail below. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.

[0050] In the prior art, in the IoT device management system with specific payment functions, some financial service interfaces are coupled with the codes of the IoT device management system, resulting in high code coupling, difficult maintenance, and low development efficiency. For example, an additional financial service interface is set in the parking management system. Some IoT device management systems use third-party payment platforms, but this reduces the service strength of the IoT device management system. Therefore, the present application provides an IoT operation information management system that can effectively solve the problems of high code coupling, low development efficiency, and low service strength after the existing IoT device management platform realizes the financial service function.

[0051] Figure 1 A structural block diagram of the Internet of Things operation information management system of the embodiment of the present application is shown. The Internet of Things operation information management system 100 can be pluggably embedded in the Internet of Things device management system 200 or the financial system 300, or can be operated independently. When operating independently, the Internet of Things operation information management system 100 establishes a communication connection with the financial system 300 and the Internet of Things device management system 200.

[0052] The IoT device management system 200 includes a plurality of IoT devices 400 and various sensors; the sensors are used to detect the operating status of the devices and obtain device operating data and device status data. Furthermore, the IoT device management system 200 also includes: an IoT device management component. The IoT device management component includes a device inventory management module, a device software and hardware version management module, and a device monitoring and maintenance module;

[0053] The equipment inventory management module is used to manage the storage information of the equipment. For example, the equipment inventory management module is used to manage the storage information and storage information of the equipment. The storage information includes inventory information, such as the equipment's entry, exit, and remaining inventory quantity.

[0054] The device software and hardware version management module is used to manage the software and hardware version information of the device. Manage the software and hardware version information of the device to ensure the compatibility of the device hardware version and software version, and update the software version of the device when the software version is incompatible. Version compatibility means that a certain hardware version needs to match the correct software version to run efficiently. In actual operation, the hardware is upgraded through a series of iterative upgrades, tests, and releases of the software version. The upgrade of the software version is used to give the IoT device more functions or fix bugs in the previous version. Therefore, the device software and hardware version management module ensures that various IoT hardware devices in a product are running corresponding versions of software.

[0055] Exemplarily, in the embodiment of the present application, a unique version number is assigned to each hardware device and software version to ensure that each update can be accurately tracked. Then, a central database is established to record the software and hardware version information of each device for easy query and management. Finally, OTA (Over-The-Air) is used to update the software version. That is, software updates are pushed through wireless networks to ensure that all devices can receive the latest version in a timely manner.

[0056] The equipment monitoring and maintenance module is used to monitor the running status of the equipment and provide equipment fault handling functions. The equipment monitoring and maintenance module is specifically used to monitor the running status of the equipment and provide maintenance and fault handling functions. Among them, the monitoring and information collection mode of the equipment monitoring and maintenance module includes: active mode and passive mode.

[0057] The active mode refers to a method of actively detecting the device status by triggering from the server, such as using websocket, mqtt and other technologies to actively query and detect the status of the IoT device 400, so as to ensure that the IoT device 400 can be discovered as early as possible when it is operating abnormally.

[0058] Passive mode refers to reporting the operating status from the device to the server. Common reporting methods include http, socket, SMS, email, etc. Through regular reporting or fault reporting, the device operation status can be monitored in a timely manner.

[0059] Each device is equipped with various sensors to collect the device operation information of the device in real time, including device operation data and device status data, etc. Then, wireless communication technology (such as Wi-Fi, 4G / 5G, etc.) is used to transmit the collected device operation information in real time to the remote monitoring platform, cloud server or the Internet of Things operation information management system 100 in this application. Finally, engineers can remotely program, debug, upload and download programs, etc. on the device through the remote maintenance platform.

[0060] Exemplarily, the financial system 300 (also referred to as a financial institution) mainly provides withholding services for the Internet of Things Operation Information Management System 100. The withholding services of financial institutions generally refer to the technical interface provided by the bank that enables the third-party service system (such as the Internet of Things Operation Information Management System 100 in this application) to automatically deduct the specified amount from the user's bank account and pay it to the corresponding payee by connecting with the financial institution. Specifically, the withholding service includes the following functional characteristics:

[0061] 1) Docking service, supporting data exchange and payment instruction transmission between third-party service systems and bank systems.

[0062] 2) Automatic deduction: With the user's authorization, the bank can automatically deduct the amount agreed in the payment instruction from the user's bank account in accordance with the payment instruction sent by the third-party service system.

[0063] 3) Payment on behalf of the payee. After the deduction is completed, the bank will transfer the agreed amount to the payee agreed in the payment instruction.

[0064] 4) Transaction processing: The interface in the withholding and payment service can handle a series of transaction operations including deduction, inquiry, reconciliation, refund, etc.

[0065] 5) Security and convenience. The bank’s withholding service interface usually has high security standards to ensure the security of transactions and the confidentiality of data. It provides users with a convenient payment method without the need for customers to pay in person at various institutions, thereby improving efficiency and saving time.

[0066] The Internet of Things operation information management system 100 is described below in conjunction with some specific embodiments.

[0067] Figure 2 A structural block diagram of an Internet of Things operation information management system 100 according to an embodiment of the present application is shown. Exemplarily, the Internet of Things operation information management system 100 includes: a data collection module 110, a billing event screening module 120 and an account management module 130.

[0068] S100, the data collection module 110 collects the device operation data of the IoT device 400, and sends the device operation data to the billing event screening module 120, such as Figure 3 The equipment operation data includes equipment operation data and equipment status.

[0069] Furthermore, the data collection module 110 collects the device operation data of the IoT device 400, including:

[0070] The data collection module 110 collects device operation data from the user's Internet of Things device 400; or, the data collection module 110 obtains the device operation data of the user's Internet of Things device from the Internet of Things device management system 200. In other words, the collection of device operation data of the Internet of Things device 400 can be directly collected by the data collection module 110 of the present application, or the Internet of Things device management system 200 can be responsible for the collection work. When the Internet of Things device management system 200 is responsible for collecting the device operation data, the data collection module 110 of the present application obtains the device operation data from the Internet of Things device management system 200.

[0071] S200 , the billing event screening module 120 obtains screening parameters and billing rules corresponding to pre-configured billing events, screens out billing event data from device operation data based on the screening parameters and billing rules, and sends the billing event data to the account management module 130 .

[0072] In order to facilitate the Internet of Things device management system 200 to serve more business types, the present application pre-sets various types of billing events, screening parameters corresponding to each billing event, and billing rules. For example, the Internet of Things device management system 200 in the embodiment of the present application includes but is not limited to a parking management system and a charging pile management system. If the Internet of Things device management system 200 is a charging pile management system, the billing events include user charging, installation of charging piles, etc. The relevant screening parameters include charging start time, charging end time, charging duration, and charging usage. The corresponding billing rules include: billing based on usage duration, billing based on usage, etc. For example, when charging according to the charging usage, different charging standards are configured in different time periods such as peak periods and trough periods.

[0073] For user charging billing events, the screening parameters include charging start time and charging end time. The corresponding billing rule is billing based on usage time, and then the billing event data is screened out from the device operation data based on the screening parameters such as charging start time and charging end time.

[0074] For charging according to charging time, the billing unit 131 needs to count the user's charging time according to the device operation information; for charging according to the number of charging degrees, the billing unit 131 needs to count the number of charging degrees according to the device operation information. Therefore, the embodiment of the present application configures different billing events and corresponding billing rules according to different device operation parameters (such as charging time, charging degrees) of interest.

[0075] It is understandable that the Internet of Things device management system 200 configures different charging rules for different service types. For example, the charging rules for different service types include one or more of the following:

[0076] 1) Usage-based billing: such as water, electricity, and telephone charges, the fees are calculated based on the user's actual usage.

[0077] 2) Time-based billing, such as parking lots, phone calls, etc., is charged according to the length of use.

[0078] 3) Fixed-fee billing, where users pay a fixed fee regardless of usage or time, such as membership fees.

[0079] 4) Hybrid billing: Combining the above methods to provide more flexible billing rules.

[0080] S300, the account management module 130 obtains account information and billing rules, generates a service fee list based on the account information, billing rules and billing event data, and calls the withholding service interface of the financial system 300 based on the service fee list to complete the fee settlement of the service fee list. The account information includes the user ID, the device ID bound to the user, the payer's bank account information, the payee's bank account information, etc.

[0081] The account management module 130 generates a withholding payment instruction based on the service fee list. Then, the account management module 130 calls the withholding service interface of the financial system 300 based on the withholding payment instruction to deduct the corresponding service fee from the payer's bank account and transfer it to the payee's bank account. For example, the withholding payment instruction uses a data message in json format, which includes user identification, deduction date, payment method, list number, service fee, payer bank account information, payee bank account information, instruction type, etc. The instruction type is used to clarify that the instruction is a deduction instruction, and contains the specific type of deduction, such as regular deduction, one-time deduction, etc. The payment method is the payment method selected by the user, such as bank transfer, credit card, third-party payment platform, etc.

[0082] Furthermore, if Figure 4 As shown, the account management module 130 specifically includes a billing unit 131 , a bill management unit 132 and a withholding payment interface 133 .

[0083] The account management module 130 obtains account information and billing rules, generates a service fee list based on the account information, billing rules and billing event data, and calls the withholding service interface of the financial system 300 based on the service fee list to complete the fee settlement of the service fee list, including:

[0084] The billing unit 131 generates a service fee list based on account information, billing rules and billing event data, and sends the service fee list to the bill management unit 132. For example, for charging piles, the billing is based on the charging time, and the billing rule is 0.5 yuan per hour. The billing unit 131 needs to obtain the charging start time and charging end time corresponding to the device used by the user ID from the device operation information according to the device ID bound to the user, and obtain the service fee that the user needs to pay according to the charging time and billing rules. At the same time, combined with account information (user bank information, bank account number of the party to which the Internet of Things device management system belongs, etc.), a service fee list is generated. Among them, the service fee list usually includes detailed service usage, service fee calculation process and total service fees payable.

[0085] Furthermore, the billing event screening module 120 is also used to configure the rate so that the billing unit 131 can calculate the final service fee for each user based on the service fee. The rate varies according to factors such as service type, time, user category, etc. In addition, the billing rules also include basic fees, pay-as-you-go, discounts, package fees, etc.

[0086] The bill management unit 132 obtains the account information from the service expense list, stores the service expense list under the account information, and calls the withholding payment interface 133 based on the service expense list.

[0087] The withholding payment interface 133 calls the withholding service interface of the financial system 300 based on the service fee list, and receives the fee settlement information returned by the withholding service interface.

[0088] Furthermore, the bill management unit 132 obtains account information from the service fee list, stores the service fee list under the account information, and calls the withholding payment interface 133 based on the service fee list, including:

[0089] The bill management unit 132 periodically calls the withholding payment interface 133 based on the unpaid service fee list according to the periodic payment authorization information signed by the user in the account information.

[0090] Among them, the periodic payment authorization information includes user authorization to settle fees according to the natural month. The bill management unit 132 retrieves the service fee list of the current natural month according to the agreement, and obtains the total service fee list by counting. Based on the total service fee list, the withholding service interface of the financial system 300 is called to complete the fee settlement of the total service fee list. For example, for a charging pile user, the user spends 10 yuan on charging on the 1st, 20 yuan on the 7th, and 50 yuan on the 30th. The bill management unit 132 generates a service fee list after each charging and stores it with the bill management unit 132. At the agreed date at the end of the month, all service fee lists to be paid this month are counted to obtain a total service fee list.

[0091] Further, the bill management unit 132 is also used to update the payment completion status in the service fee list according to the fee settlement information, and output the service fee list corresponding to the account information that meets the query conditions according to the list query command. The withholding payment interface 133 calls the withholding service interface of the financial system 300 based on the service fee list, and receives the fee settlement information returned by the withholding service interface. Specifically, the withholding and payment interface calls the withholding service interface of the financial institution, and the withholding service interface will return the payment receipt information to the withholding and payment interface. The withholding and payment interface is then fed back to the bill management unit 132, so that the bill management unit 132 can update the payment status of the corresponding service fee list. For example, the withholding payment instruction includes the list number, the withholding service interface returns the payment receipt information according to the list number, and the bill management unit 132 matches the corresponding service fee list according to the list number and updates the payment status. The bill management unit 132 is also used to send detailed information on whether the payment is successful or not to the user according to the payment receipt information.

[0092] The bill management unit 132 stores service fee lists including service fee lists that have been paid and those to be paid. When a list query command is received, a corresponding service fee list is provided according to the query conditions, and a user interface is provided to display the queried service fee list. For example, the bill details can be displayed, including the specific composition of each fee. Among them, the query conditions include the user ID and the identification of the party to which the Internet of Things operation information management system belongs. It can be understood that the bill management unit 132 in this application can classify each service fee list according to the user ID and the identification of the party to which the Internet of Things operation information management system belongs, so that the user can query the corresponding service fee list. Further, the query conditions also include time periods, that is, querying a service fee list for a certain user according to time periods. Further, the service fee list can also be classified according to the payment status of the service fee list, so that the user can query the service fee list according to the payment status, wherein the payment status includes completed and to be paid. This application includes but is not limited to querying the service fee list according to the payment status, time period, user ID, and identification of the party to which the Internet of Things operation information management system belongs.

[0093] The bill management unit 132 is also used to detect and process abnormal service fee lists and provide a solution process for abnormal service fee lists, such as refunding and adjusting bills.

[0094] The bill management unit 132 is also used for data analysis and generating income and expenditure reports, analyzing service expense list data to optimize rates and market strategies, and providing income and expenditure reports to management.

[0095] The bill management unit 132 is also used to manage the user's prepaid balance, that is, to manage the user's prepaid balance according to the user identifier, and to implement credit management and overdraft control for post-paid users.

[0096] Furthermore, if Figure 5 As shown, the account management module 130 further includes: an account points management unit 134;

[0097] Before the step of the billing unit 131 generating a service fee list based on the account information, the billing rules and the billing event data, the billing unit 131 is further configured to send the account information to the account points management unit 134;

[0098] The account points management unit 134 obtains the account level corresponding to the account information, determines the discount strength corresponding to the account information based on the account level, and sends the discount strength to the billing unit 131. The account points management unit 134 is used to store and manage the user's points according to the preset points rules. For example, the user's points can be added, deleted, modified, and checked according to the points rules. Among them, for example, the points can be set according to the user's frequency of use, the cost of consumption, the recharge amount, etc. By giving users points, user behavior is encouraged, user stickiness is increased, and user activity is improved. Points management includes:

[0099] 1) Points acquisition: users can earn points by purchasing goods, participating in activities, completing specific tasks, etc.

[0100] 2) Points usage: Users can use points to redeem goods, services or participate in lucky draws, etc.

[0101] 3) Points validity period: Points are usually valid for a certain period of time and may become invalid after that.

[0102] 4) Points rules, clearly define the points acquisition ratio, usage rules and redemption standards.

[0103] The functions of the account points management unit 134 specifically include the following:

[0104] 1) User management: record and manage user points information based on user ID.

[0105] 2) Points records, which record the acquisition, use and expiration of points.

[0106] 3) Rule management, management of points accumulation strategy and redemption strategy.

[0107] 4) Backstage operations for administrators to adjust points policies and handle abnormal situations.

[0108] 5) Users are divided into account levels according to their points, and the corresponding discount levels are divided for different account levels.

[0109] Furthermore, in order to improve user experience, the account points management unit 134 is also used to set discount rules according to points. For example, according to the points, the user's level is set, and different proportions of discounts are given to users according to different levels.

[0110] It can be understood that the billing unit 131 is specifically used to generate a service fee list based on the device operation information, the acquired user information, the billing events, the corresponding billing rules, the user's current points and the preset discount rules.

[0111] The billing unit 131 generates a service fee list based on the account information, billing rules and billing event data, specifically including:

[0112] The billing unit 131 generates a service fee list based on the account information, discount strength, billing rules and billing event data.

[0113] Furthermore, in order to improve service intensity and reduce the burden of the IoT device management system 200, as Figure 5 As shown, the account management module 130 also includes: a risk control management unit 135.

[0114] The risk control management unit 135 performs risk identification based on the account information, the device operation data, and at least one of the device life management information and the device failure management information obtained from the IoT device management system 200, and outputs risk warning information.

[0115] Among them, the account information includes the user's points information and the information stored in the basic information management module 150; the device operation data includes the device operation data and device status data issued by the Internet of Things device management system 200. In order to reduce the burden, some Internet of Things device management systems 200 focus on functions such as device collection, and no risk prediction module is set in them. In this case, the risk control management unit 135 of this application needs to realize the identification of potential risks of the Internet of Things device 400. For example, a user's use request for a certain device can be received, but the device status of the device has been in a non-working state, then it is determined that the device has a fault, and it is necessary to issue the risk information corresponding to the device. For another example, if the device operation data of a device indicates that the voltage of the device is higher than the set threshold, it is determined that the voltage of the device is faulty, and it is necessary to issue the voltage risk information of the device. For another example, it is identified whether the information in the basic information management module 150 and the points management module has security risks, whether it has been tampered with, etc. Finally, the device life management information, device failure information, etc. are obtained, and risks are identified based on the device life management information and device failure information.

[0116] The risk control management unit 135 is also used to send alarm information to the management personnel of the Internet of Things device management system 200 based on the risk information received from the Internet of Things device management system 200. The risk control management unit 135 receives the risk information sent by the risk prediction module in the Internet of Things device management system 200. Some Internet of Things device management systems 200 are provided with a risk prediction module, which can identify potential risks based on device operation information and device monitoring information, and send risk information. For example, if the device fault code #000 sent by the risk prediction module is received, the risk control management unit 135 sends the device fault code #000 to the above-mentioned person in charge. This reduces the burden on the Internet of Things device management system 200.

[0117] In order to improve the risk monitoring and identification capabilities, the risk control management unit 135 compiles statistics on all service fee lists to be paid by users in the bill management unit 132 to identify the financial risks of users and output risk warning information to prevent users from owing too much and being unable to afford it.

[0118] In summary, the risk management unit 135 is mainly used to identify, evaluate, monitor and control potential risks, and take a series of measures and processes to ensure the safety, compliance and business continuity of users and equipment. Among them, risks may come from many aspects, including market changes, operational errors, system failures, legal compliance issues, fraud, etc. The core elements of risk management include: risk identification, risk assessment, risk control, risk monitoring, risk response, etc.

[0119] Furthermore, the IoT operation information management system 100 further includes: a device user management module 140 and a basic data management module 150;

[0120] The device user management module 140 allocates and binds the target device to the user based on the acquired user information and the device information of the IoT device obtained from the IoT device management system 200 to obtain device binding information; the device user management module 140 is also used to store the device usage record. Among them, the user information includes the user ID. The device binding information includes the user ID and the device ID bound to the user. For example, the device user management module 140 is used to allocate devices to users according to the following rules:

[0121] Assign devices to users based on device type and usage period. For example, assign the corresponding type of device to the user based on user needs. Determine the length of time the device is assigned to the user based on needs, and set the device usage period for the user. For example, some leases are long-term, some are short-term, and some are one-time buyouts. Allocation: refers to setting the device's ownership attributes in the IoT operation information management system, such as attribution to a partner, a region, a community, an agent, etc. The device vendor sets the ownership attributes, that is, the device is assigned to the first-level attribution object, the second-level attribution object, ..., and finally to the user who uses the device.

[0122] Binding: It is the association relationship established between the final user (user ID) and the physical identification number of the device (device ID), that is, the binding of the user and the device to obtain the device binding information.

[0123] The basic information management module 150 is used to collect and manage user information and user bank information, and generate account information based on the user's device binding information, user information, and user bank account information obtained from the device user management module 140 .

[0124] Specifically, the basic information management module 150 is used to collect user payment information and usage records, and determine user service plans based on the user payment information and usage records. It is also used to store the information of the owner of the Internet of Things device management system 200; the information of the owner of the Internet of Things device management system includes the name of the owner, the bank account of the owner, etc. User information includes the user's device binding information (the correspondence between the device identifier and the user identifier) ​​and bank binding information (the correspondence between the user's bank account and the user identifier). The basic information management module 150 is specifically a process of managing user information, including the effective collection, storage, updating, protection and use of user information. Understand the user based on the user's payment information and usage records. The user's payment information and usage records are the basis for ensuring compliance operations, thereby improving service quality and providing users with accurate service plans that meet user needs.

[0125] Furthermore, in order to improve the user experience of multiple users, the information management system also includes a customer service module 160 .

[0126] The customer service module 160 is used to support audio, video and text information communication between the user and the system, and to query the service fee list corresponding to the user in the bill management unit 132. The text information includes user evaluation and device problems reported by the user. For example, a rating function is provided on the charging pile user end APP, and the customer service module 160 receives the user's evaluation, or a rating button is set on the charging pile device.

[0127] In one embodiment, the Internet of Things operation information management system 100 further includes: a financial system 300;

[0128] The financial system 300 is used to provide a withholding service interface for automatically deducting the fees in the service fee list from the user's bank account and paying the fees to the corresponding payee in the service fee list on the user's behalf.

[0129] In one implementation, the Internet of Things operation information management system 100 further includes: an Internet of Things device management system 200 .

[0130] The Internet of Things device management system 200 is used to collect device operation data of the user's Internet of Things devices;

[0131] The IoT device management system 200 is used to monitor the life attributes and fault attributes of the user's IoT device 400, and obtain device life management information and device fault management information based on the life attributes and fault attributes.

[0132] In a specific example, the Internet of Things operation information management system 100 is used for parking lot management.

[0133] The charging event screening module 120 pre-configures charging events and charging rules, for example, the charging event is vehicle parking, and the charging rule is charging based on parking duration. The IoT device 400 detects the parking space usage status, and the IoT operation information management system 100 is used for parking space query and reservation.

[0134] The vehicle enters the parking lot through the IoT device 400 (such as an automatic gate). The IoT device 400 automatically detects and identifies the vehicle and records the time of entering the parking lot. Specifically, after the user enters the parking lot, the vehicle is identified and the corresponding account information is obtained. The data acquisition module 110 automatically obtains the device operation data such as the parking time of the vehicle from the IoT device 400, and uploads the device operation data to the billing event screening module 120.

[0135] The data collection module 110 collects the device operation status of the parking lot IoT device 400 in real time. The parking lot IoT device 400 monitors the parking space status and usage in real time to ensure the normal operation of the equipment, and sends the monitoring equipment life management information and equipment failure management information to the risk control management unit 135. If the risk control management unit 135 is detected that a certain device needs maintenance, it will prompt the management personnel to perform maintenance.

[0136] When the vehicle leaves the parking lot, the IoT device 400 identifies the vehicle again, obtains the account information corresponding to the vehicle (the owner's account and bank account information), and records the time when the vehicle leaves.

[0137] The billing unit 131 obtains the account level corresponding to the account information from the account points management unit 134 based on the account information, and determines the discount strength corresponding to the account information based on the account level;

[0138] The billing unit 131 generates a service fee list based on the account information corresponding to the vehicle, the discount level, the billing rules, and the parking duration corresponding to the parking event, and sends the service fee list to the bill management unit 132 .

[0139] The bill management unit 132 obtains the account information from the service expense list, stores the service expense list under the account information, and calls the withholding payment interface 133 based on the service expense list.

[0140] The withholding payment interface 133 calls the withholding service interface of the financial system 300 based on the service fee list, and receives the fee settlement information returned by the withholding service interface.

[0141] In addition, users can query parking records, fee details, and obtain usage assistance through the customer service module 160.

[0142] The present application also provides a terminal device. Exemplarily, the terminal device includes a processor and a memory, wherein the memory stores a computer program, and the processor runs the computer program corresponding to the Internet of Things operation information management system 100, thereby enabling the terminal device to execute the functions of each module in the above-mentioned Internet of Things operation information management system 100.

[0143] Among them, the processor can be an integrated circuit chip with signal processing capabilities. The processor can be a general-purpose processor, including a central processing unit (CPU), a graphics processing unit (GPU) and a network processor (NP), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or at least one of other programmable logic devices, discrete gates or transistor logic devices, and discrete hardware components. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc., which can implement or execute the disclosed methods, steps and logic block diagrams in the embodiments of the present application.

[0144] The memory may be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), etc. The memory is used to store a computer program, and the processor may execute the computer program accordingly after receiving an execution instruction.

[0145] The present application also provides a computer-readable storage medium for storing a computer program corresponding to the Internet of Things operation information management system 100 used in the above-mentioned terminal device. For example, the computer-readable storage medium may include, but is not limited to, various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0146] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and structure diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in an alternative implementation, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the structure diagram and / or the flow diagram, and the combination of boxes in the structure diagram and / or the flow diagram, can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0147] In addition, the functional modules or units in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0148] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a smart phone, a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application.

[0149] The above description is only a specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application.

Claims

1. An Internet of Things operation information management system, characterized in that: The IoT operation information management system establishes a communication connection with the financial system and the IoT device management system; The Internet of Things operation information management system includes: a data collection module, a billing event screening module and an account management module; The data collection module collects device operation data of the IoT device and sends the device operation data to the billing event screening module; The billing event screening module obtains screening parameters and billing rules corresponding to pre-configured billing events, screens billing event data from the device operation data based on the screening parameters and billing rules, and sends the billing event data to the account management module; The account management module obtains account information and the billing rules, generates a service fee list based on the account information, the billing rules and the billing event data, and calls the withholding service interface of the financial system based on the service fee list to complete the fee settlement of the service fee list.

2. The Internet of Things operation information management system according to claim 1, characterized in that: The data acquisition module collects device operation data of the IoT device, including: The data collection module collects the device operation data from the user's Internet of Things device; or, the data collection module obtains the device operation data of the user's Internet of Things device from the Internet of Things device management system.

3. The Internet of Things operation information management system according to claim 1, characterized in that: The account management module specifically includes a billing unit, a bill management unit and a withholding payment interface; The account management module obtains the account information and the charging rules, generates a service fee list based on the account information, the charging rules and the charging event data, and calls the withholding service interface of the financial system based on the service fee list to complete the fee settlement of the service fee list, including: The billing unit generates a service fee list based on the account information, the billing rules and the billing event data, and sends the service fee list to the bill management unit; The bill management unit obtains account information from the service fee list, stores the service fee list under the account information, and calls the withholding payment interface based on the service fee list; The withholding payment interface calls the withholding service interface of the financial system based on the service fee list, and receives fee settlement information returned by the withholding service interface.

4. The Internet of Things operation information management system according to claim 3, characterized in that: The account management module also includes: an account points management unit; Before the step of generating a service fee list based on the account information, the billing rules and the billing event data by the billing unit, the billing unit is further configured to send the account information to the account points management unit; The account points management unit obtains the account level corresponding to the account information, determines the discount strength corresponding to the account information based on the account level, and sends the discount strength to the billing unit; The billing unit generates a service fee list based on the account information, the billing rules and the billing event data, specifically including: The billing unit generates a service fee list based on the account information, the discount level, the billing rules and the billing event data.

5. The Internet of Things operation information management system according to claim 3, characterized in that: The account management module also includes: a risk control management unit; The risk control management unit identifies risks based on the account information, the device operation data, and at least one of the device life management information and the device failure management information obtained from the IoT device management system, and outputs risk warning information; And / or, the risk control management unit collects statistics on all service fee lists to be paid by the user in the bill management unit to identify the financial risk of the user and output risk warning information.

6. The Internet of Things operation information management system according to claim 1, characterized in that: The Internet of Things operation information management system also includes: a device user management module and a basic data management module; The device user management module allocates and binds a target device to the user according to the acquired user information and the device information of the IoT device acquired from the IoT device management system to obtain device binding information; The basic information management module is used to collect and manage user information and user bank information, and to generate the account information according to the user's device binding information, user information, and user bank account information obtained from the device user management module.

7. The Internet of Things operation information management system according to claim 1, characterized in that: The Internet of Things operation information management system also includes: a financial system; The financial system is used to provide a withholding service interface for automatically deducting the fees in the service fee list from the user's bank account and paying the fees to the corresponding payee in the service fee list on the user's behalf.

8. The Internet of Things operation information management system according to claim 4, characterized in that: The bill management unit is further used to update the payment completion status in the service fee list according to the fee settlement information, and output the service fee list corresponding to the account information that meets the query conditions according to the list query command.

9. The Internet of Things operation information management system according to claim 5, characterized in that: The bill management unit obtains account information from the service fee list, stores the service fee list under the account information, and calls the withholding payment interface based on the service fee list, including: The bill management unit periodically calls the withholding payment interface based on the unpaid service fee list according to the periodic payment authorization information signed by the user in the account information.

10. The Internet of Things operation information management system according to claim 5, characterized in that: The Internet of Things operation information management system also includes: an Internet of Things equipment management system; The IoT device management system is used to collect the device operation data of the user's IoT devices; And / or, the IoT device management system is used to monitor the life attributes and fault attributes of the user's IoT devices, and obtain device life management information and device fault management information based on the life attributes and fault attributes analysis.

Images